Related
So after reading about a dozen or so threads, all of the FAQ's, asking in the wrong forum, and 3 other sites, I have come to a roadblock. Here is my situation in its entirety...
Got a brand new Kindle Fire HD 7" for Christmas, obviously couldn't leave it alone. I have rooted about a dozen models of Android phone, and jailbroken multiple iPhones, so I know the trials and tribulations of this process...
So I attempt to root my KF using the Bin4ry and Qemu method. I have a AWFUL time getting the drivers to properly recognise my KF. I end up finding another person's issue such as mine, and go through the LONG way of downloading the adt bundle, and installing all of the google software and drivers that way. EUREKA! Drivers work, KF recognised by my machine. First shot with Bin4ry after the driver mishap, works fine. Takes 2 attempts with the second step with the Qemu method, but again, I get there. after the first time booting up, I factory reset the Kindle. Still have SU on the apps list. Cool! Now what?
I boot the machine and shut it down about 5 times just to check stability, and hard shutdown (power button for 20+ seconds) twice. Every time all is ok, and SU is still there.
Now time to play. I again go through reading a couple threads on changing the launcher, and decide to go with the Nova launcher for now. I download it from the Play store, yet can't seem to find it on my KF. I for some god awful reason decide "well I saw it a couple threads ago, that someone had an issue with the launcher change the name of launcher.apk to launcher.apk1 and then it worked" so obviously I go and do that. Enter the final time I would boot my KF.
Upon reboot, I get the stock/standard "kindle fire" screen with no animation at full brightness. It then goes black for a split second, and comes back with the "kindle fire" screen, but now with the animated "shiny streak" that goes across the logo. I left it there multiple times for a half hour +, no change.
So I don't freak out yet, cause it turned on, and I find it can't be all that bad. So I check for it in device manager...nothing. Check My Computer just to see if its recognised for memory storage...nothing. I run the Bin4ry script again, just to see...nothing. Run Qemu just to be thorough...nothing. Restart my computer, repeat ALL above steps...nothing. Still never see's the KF, also never makes a tone at me when I plug the kindle into the cable. Change USB ports, repeat all, nothing. Back all of the drivers out, and reinstall all of them. Restart. Nothing. Download kindle unbrick utility, that still doesn't see the KF. No adb shell commands ever let me even see that it is seen somehow my my computer.
So now I am stuck. It still seems to me to be a driver issue, but I seriously cannot see how that is possible. I guess while waiting for a response from one of the guru's here, I will repeat my process of backing all of the previous drivers out and reinstalling them. There is NO other software on the kindle except for the Nova launcher and whatever the Bin4ry and Qemu methods install on it.
Sorry for the long post, but I figured it would be better than leaving you guys to ask more questions, though I'm sure you will anyways. My KF is running 7.2.3 before all of this happened...
Thanks for any help, sorry to be that guy!
Jordan
skeeter7424 said:
So after reading about a dozen or so threads, all of the FAQ's, asking in the wrong forum, and 3 other sites, I have come to a roadblock. Here is my situation in its entirety...
Thanks for any help, sorry to be that guy!
Jordan
Click to expand...
Click to collapse
Well the good news is you don't have a driver issue, Its seems you are just stuck in a boot loop and at that point in the boot process adb is not recognized. Check out this thread on how to restore it: http://forum.xda-developers.com/showthread.php?t=1951254
By the way you will need a factory cable. There is a link in the above thread for where to purchase(someone told me they've gotten them on amzon as well). Don't worry they are cheap, about $10-15.
So I see it listed all over the place, but I take it the factory cable is not the one that was supplied in the box?
edit: now i have found what everyone is talking about and have found the writeup on the cable. I am currently sitting at my desk making myself this cable now...we'll see how this goes!
So I got the factory cable made correctly, plugged it in, boom, computer recognizes it. I reload software from the kindle unbrick utility. Now it goes into straight bootloop, KF home screen, blank, KF home screen, blank. Tried with both the factory cable and the stock cable. No changes. Am letting it completely die today to attempt to plug into computer and let it recognize. Should I do this part with the stock cable or the factory modded cable?
skeeter7424 said:
I reload software from the kindle unbrick utility.
Click to expand...
Click to collapse
What are you referring as "the kindle unbrick utility"? Did you try to use KFHD System.img Restore Tool ?
Yes I am. The issue is that the KF boots to the "Kindle" opening screen, then switches to a screen that says "Fastboot" with "amazon kindle" below it. I then get a tone from my computer that is recognized, then about a quarter second later, the KF blacks out, and I get a tone from my comp that says disconnect. It then tones back and forth between connected and not. This happens with both the factory cable and the stock cable.
skeeter7424 said:
Yes I am. The issue is that the KF boots to the "Kindle" opening screen, then switches to a screen that says "Fastboot" with "amazon kindle" below it. I then get a tone from my computer that is recognized, then about a quarter second later, the KF blacks out, and I get a tone from my comp that says disconnect. It then tones back and forth between connected and not. This happens with both the factory cable and the stock cable.
Click to expand...
Click to collapse
What happens when you just turn it on with no cable hooked up. Also did you use the tool that corresponds with the system version your device was running before the problem tat started it. If you used the wrong backup then you will need to use the method to downgrade at the bottom of the restore tool post
Sent from my KFJWI using xda premium
onemeila said:
What happens when you just turn it on with no cable hooked up. Also did you use the tool that corresponds with the system version your device was running before the problem tat started it. If you used the wrong backup then you will need to use the method to downgrade at the bottom of the restore tool post
Sent from my KFJWI using xda premium
Click to expand...
Click to collapse
The same thing happens when trying to boot with no cable. Kindle fire screen, quick to Fastboot/Kindle Fire screen, black.
Also, now with a little more research, I should explain how the computer actually tones when this happens. Right when the KF boots, I get an "unplugged" tone, then right after that I get 3 tones, which after looking at different hardware forums, means that the device is not recognized. It will then go back and forth between the unplugged tone, and the 3 beeps, now with the KF being blacked out. If I then long hold the power button it gives me one "final" unplugged tone.
I used the backup for 7.2.3 which was what was on my KF before I started. Again, that tool will not recognize my KF. All I get with the KFHD_SRT tool is "waiting for device"
Thanks again guys for the help with this!
skeeter7424 said:
The same thing happens when trying to boot with no cable. Kindle fire screen, quick to Fastboot/Kindle Fire screen, black.
Also, now with a little more research, I should explain how the computer actually tones when this happens. Right when the KF boots, I get an "unplugged" tone, then right after that I get 3 tones, which after looking at different hardware forums, means that the device is not recognized. It will then go back and forth between the unplugged tone, and the 3 beeps, now with the KF being blacked out. If I then long hold the power button it gives me one "final" unplugged tone.
I used the backup for 7.2.3 which was what was on my KF before I started. Again, that tool will not recognize my KF. All I get with the KFHD_SRT tool is "waiting for device"
Thanks again guys for the help with this!
Click to expand...
Click to collapse
You made your own factory cable right? Did you use a resistor and if so what size? Sounds like you could have shorted something out, cause I've never heard of this problem but I know you can do a lot of damage to both device and pc if a factory cable is not made correctly with at least a 1k resistor(if I remember correctly).
Do you get the fastboot screen. And also I did not use resistor when I made my cable and it works just fine. Only thing weird Is That once I have fastboot screen I have to unplug my fastboot cable and use original cable in order to flash anything but I have had no other issues. Hope this helps.
Sent from my KFTT using XDA Premium HD app
Need a bandaid?
Try this.
I have an Amazon Kindle Fire HD rooted and running the stock 7.6.4 os, i rooted using Bin4ry's (sp) method found on XDA. In an attempt to change the lock screen images i moved the "frame work apk" (not sure of the exact spelling) and frame work obb file and something else that said frame work from the system/app directory to mnt/sdcard/quarantine, a file i created for just this purpose. Noob mistake I left the screen time out on 5 minutes and left. When i came back the screen was off, and some blah blah blah was not responding. I tried to move the file back but the fc window was popping up so often i was having alot of trouble doing this, so (BIG noob mistake here) i rebooted it. Now I'm stuck on the stock "Kindle Fire System Utility" window. Rebooting doesn't work and resetting to factory defaults doesn't work. My question is this;
1. How do I fix the problem using only the stock cord, Amazon approved charger and a laptop i am borrowing off my gf ?
2. How much $ am i going to have to throw at this to fix my problem?
3. If I do have to ship it back to Amazon will the know I rooted and not help?
thank you for any help. I am truly in a bind here.
With a little ingenuity, you can make your own factory cable for free.
soupmagnet said:
With a little ingenuity, you can make your own factory cable for free.
Click to expand...
Click to collapse
There is no way I can make one. I looked at the xda forum on how to do it and I can't solder, nor do I have a soldering iron.
You will need about 5-15$ then...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
JeremySwagS said:
There is no way I can make one. I looked at the xda forum on how to do it and I can't solder, nor do I have a soldering iron.
Click to expand...
Click to collapse
It's not absolutely imperative that you solder it together. I've seen some of the most janky looking factory cables without solder that have worked just fine.
What about this method?
-----------------------------------------------------------------------------------------------------------------------------------------------------
Methods for Enabling Fastboot Mode
Realistically, there are 3 potential methods of enabling fastboot mode on a working bootloader. There is a 4th method, but it should only be considered as a last ditch effort because the case must be opened for access to the motherboard. Let's cover the first 3 methods...
Factory cable - Using a factory cable is the most straightforward method of enabling fastboot mode on the Kindle Fire and it will work with any bootloader. With the device off, plug the cable into the Kindle Fire, then the computer and the device will boot up directly into fastboot mode. No other user intervention is required.
Temporary fastboot mode - The FireFirefire custom bootloader temporarily enables fastboot mode for a short amount of time. Issuing a fastboot command like...
Code:
fastboot getvar product
to the device during this time will stop the fastboot countdown and enable fastboot mode indefinitely. If the device displays a plain white and orange "kindle fire" logo, the stock bootloader is installed. The stock bootloader does not enable fastboot temporarily, so another method must be used.
Bootmode setting - The Kindle Fire has a bootmode setting that indicates to the bootloader how to proceed in its booting process. One of these bootmodes (4002) will tell the bootloader to enable fastboot mode. The bootmode setting is recognized by all bootloaders, so even the stock bootloader will go into fastboot mode when the bootmode is set to 4002. The only place this feature is likely to be used is from the system software, but there's a catch. The system must be able to provide access to a shell prompt.
------------------------------------------------------------------------------------------------------------------------
Referred to here. http://forum.xda-developers.com/showthread.php?t=1668159
While I consider myself a rather advanced android user (I rooted my 1st gen kf w/ twrp and flashed cm10, rooted my gf's nook color w/clockwork mod and flashed cm10 and cm8, and rooted this fire hd no recovery or rom yet) i know only the basics about windows and phrases like...
"The only place this feature is likely to be used is from the system software, but there's a catch. The system must be able to provide access to a shell prompt."
...have me very confused. When I'm trying to enable fastboot am I not using two systems? The windows and the fire. So which system must be able to provide access to a shell prompt? I have been up all night trying to get Android SDK up and running so I have the ability to input, to the fire, fastboot commands. I downloaded the sdk from here.
http://developer.android.com/sdk/index.html
I am, honestly, flying blind here. I'm not even certain that this is the right program I need. I have been following this guide...
http://www.youtube.com/watch?v=Yc4z-KYypgY
I like the You Tube video tutorials because they are easier for me to follow, no offence to XDA. I have used XDA extensively in the past, but this is my first "brick" and, honestly, I NEED this kindle to work! I depend on it daily! I believe that once I can get into fastboot I will be okay. I have installed recovery, and roms before, but never even heard of fastboot till yesterday. I just can't afford to wait for a modified cable to come in the mail. I really would like for this to be done by tomorrow morning if it is at all possible.
I would also like to say thank you to everyone that has helped be this far. I truly appreciate it.
-edit-
I'm attempting to use the 3rd option, Bootmode setting.
i have adb and fastboot installed on the computer but i'm stuck at putting the kindle into fastboot mode. i have a command prompt window and i know that fastboot is mode 4002 but have no idea what the command is. i downloaded commands but dont know where they go. ive been up all night working on this and im afraid im going to make a mistake and permanently brick my kindle. can any one help? please?
Those bootmodes and the tutorial you referenced are for the original Kindle Fire. You need to acquire a factory cable.
soupmagnet said:
Those bootmodes and the tutorial you referenced are for the original Kindle Fire. You need to acquire a factory cable.
Click to expand...
Click to collapse
okay. thank you.
I want to try going to my local best buy tomorrow and see if the geek squad there will let me use one of their fastboot cables. But that leads me to more questions.
1. My understanding is that I need to use the fastboot cable ONLY to get my kf hd into fastboot mode then switch to the "stock" cable to do any actual file transfers. Is this true?
2. My understanding is that once in fastboot mode my kindle will stay in that mode until I set it back to normal boot. Am I right?
3. Do I need the fastboot cable to change OUT of fastboot mode and back INTO normal boot mode?
4. Do you think I can do this with a fastboot cable I borrow from the geek squad for like 2 minutes to get into fastboot mode, then go home with kindle in fastboot, install twrp, recovery, os etc. and then boot back into normal boot WITHOUT a fastboot cable, only a stock cable?
Thank you everyone for your help! I am so great full for all this help! I live at a sober house and have been tuning up the androids of fellow residents since I got here and all this wealth of knowledge is helping far more than just me. It is helping everyone else out who lives here. From the bottom of my heart, I thank you.
Yes, it would be entirely feasible to do it that way, but you have to remember that the device will not charge in fastboot. Make sure you have a full charge, and get it done as quickly as possible. Rebooting will take the device out of fastboot once you're done. Good luck.
soupmagnet said:
Yes, it would be entirely feasible to do it that way, but you have to remember that the device will not charge in fastboot. Make sure you have a full charge, and get it done as quickly as possible. Rebooting will take the device out of fastboot once you're done. Good luck.
Click to expand...
Click to collapse
I want to have everything ready to go for this trip to best buy tomorrow (today as it's after midnight) because rebooting will take me out of fastboot, so I might not have a lot of time. Can someone please post links for the download of twrp (or something better if it exists), and for a new os? Even the stock amazon would be fine for now. I was on os 7.4.6 before the brick. I honestly don't know what os i want yet. Recommendations would be helpful, with download links hopefully. I had cm10 on my first kindle fire, and it ran great, I can only imagine it would run better on the HD kindle, but I'm open to suggestions.
----UPDATE-----
I went to Best Buy and even the "geek squad" had no idea what a fastboot cable was, so I'm ordering one from Amazon. On the plus side it comes with a free OTG cord. On the down side it will take 4 - 14 business days to get here!
JeremySwagS said:
----UPDATE-----
I went to Best Buy and even the "geek squad" had no idea what a fastboot cable was, so I'm ordering one from Amazon. On the plus side it comes with a free OTG cord. On the down side it will take 4 - 14 business days to get here!
Click to expand...
Click to collapse
Would you be willing to provide a link to the factory cable you are considering purchasing from Amazon?
I've only seen a handful of sources that provide actual factory cables and Amazon isn't one of them.
soupmagnet said:
Would you be willing to provide a link to the factory cable you are considering purchasing from Amazon?
I've only seen a handful of sources that provide actual factory cables and Amazon isn't one of them.
Click to expand...
Click to collapse
http://www.amazon.com/gp/product/B00BPDH4G4/ref=ox_sc_act_title_1?ie=UTF8&psc=1&smid=A2MQXQQFSEPIZC
Here, I haven't ordered it yet.
Factory cable.
If you're in UK - I got one 'next day' off e-bay. £4.99 free post. I see they're £3.99 now! My luck
In the body of their ad it says £6.99 internationally posted.
Sorry no link - I'm too 'young'
Good luck. Bill.
Billion123 said:
If you're in UK - I got one 'next day' off e-bay. £4.99 free post. I see they're £3.99 now! My luck
In the body of their ad it says £6.99 internationally posted.
Sorry no link - I'm too 'young'
Good luck. Bill.
Click to expand...
Click to collapse
Nope, I'm in the states. (but i do love Dr. Who)
------UPDATE------
I ordered the fastboot cable today. I believe I have all the software to finish unbricking my kfhd, although any help (and download links) would be appreciated.
Question.
From what I gather, to restore a kindle fire hd from a "bricked" state, it is important for it to have as near a full charge as possible.
1. If my kindle can't be seen or recognized by a computer, hence the need for a "fastboot" cable, will it charge when plugged into a wall outlet?
2. How do I know when it's charged as the normal battery "indicator" is absent from the kindle fire system utility screen?
3. Is there an risk of "over charging" my kindle? Since my OS has been broken do I need to worry about possibly dangerous power distribution that would normally be held in check by a functional OS? Or does the stock boot loader handle this basic task?
JeremySwagS said:
Question.
From what I gather, to restore a kindle fire hd from a "bricked" state, it is important for it to have as near a full charge as possible.
1. If my kindle can't be rear or recognized by a computer, hence the need for a "fastboot" cable, will it charge when plugged into a wall outlet?
2. How do I know when it's charged as the normal battery "indicator" is absent from the kindle fire system utility screen?
3. Is there an risk of "over charging" my kindle? Since my OS has been broken do I need to worry about possibly dangerous power distribution that would normally be held in check by a functional OS? Or does the stock boot loader handle this basic task?
Click to expand...
Click to collapse
I'm a bit of a noob myself, have no soldering skills, and KFHD7 has been the device with the ugliest bricks I've seen (just ask the first one sitting in my closet, smashed it out of frustration). Anyhow, I made my own factory cable using a Samsung USB which is rumored to be the best used, and a Trisonic $2 soldering tool from the "99 Cents" store (I live in NYC) and guess what!? Following a YouTube video, I made it. It was so easy I still remember how to make another one without a YouTube video or the need to look at the one I have. If I can do it, you can as well. I recommend finding a Samsung USB as they're good for the job and the plastic housing the micro USB side is easy to remove, going to your local "cheap objects" dealer or a hardware store that carries cheap stuff to find this Trisonic soldering iron, and making it yourself. Its pretty simple. And just in case, mini plus and minus head screw drivers to steal a small wire out of another electronic to connect the two pins with, ideally a child's toy with a speaker.
And to answer your question, when I bricked my current one while installing TWRP and a second bootloader (which BTW this is the second KFHD7 I own), the charge indicator wouldn't appear, screen would stay black, and the battery by the time I put it to charge after the brick was around 20%. When I finally recovered it the next day, battery was at 99% (meaning it did charge, lost 1% while recovering). As far as I've seen on both my KFHD7s no overcharging, I guess that's recognized by some other section of the device. Thats why the Kindle Fire logo still shows up.
Tampering with ANYTHING on stock KFHD7 as far as I've seen is an invitation to get bricked. My last one got bricked by simply rooting it believe it or not. It would turn off and on fine, but one day I let the battery die, recharged it and no go. So I would recommend installing the second bootloader and TWRP recovery, then flashing a Kindle OS based ROM or jellybean like mine. But focus on this issue first. Keep us updated I'll be following.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Good evening scholars, I am at a end with my Kindle Fire. Below is an
exact account of what I was doing and thus the end state of what is now my Kindle.
I have a rooted kindle. Basic root, nothing significant like CynMod. The boot-loader is stock and all. The only thing I really
installed that is not stock is a different Launcher since Amazon's Launcher is just horrid in my opinion.
I was in Rom Toolbox Pro uninstalling Chameleon Launcher because I wanted to run
Apex Launcher instead. So I uninstalled it. At this point there is no launcher running.
I'm using Rom Toolbox as a console so-to-speak. Simply going from one program to the next without actually ever hitting
the home button. So I go to install Apex Launcher and it says installing. However, it didn't do anything at all.
The status bar never moved; simply stayed at 0%. SO! No biggie, I've seen this before. So to make sure it is not Apex or something
I go to the stock Amazon Launcher. I had a backup and tried to install it through Rom Toolbox. Same thing happens,
No response, idle status bar, etc, etc. So at this point I assume it is Rom Toolbox. So I hit the home key on the slide menu.
Well, I have no launcher currently installed so it did nothing. Go figure. So I decide to do a hard reset. So I hold down the power button.The Kindle shuts off and then my troubles started. I hit the power button and it doesn't pass the Kindle is upgrading notice.
So I do another Hard reset adding insult to injury...but, the same thing again. Turn it off again, plug it in to my computer and attempt a fastboot with the stock cable, same results occurred.
So now my kindle shows the standard Kindle Fire Logo at the beginning of the boot cycle and then stops at the Kinde is upgrading...Starting Applications... prompt. Like the link to the photo below.
h ttp://i61.tinypic.com/2s0eeer.jp g
I try rectifying this, reading several articles.
I tried utilizing the Kindle Fire First Aid, the KFHD SRT, even looking into the android SDK a little. But they either - A. Don't recognize the device or, B. Prompts for superuser. Seeing as how my Kindle barely boots how can I check for a superuser prompt?
I go went into my device manager and looked to see if windows registers the Kindle and it does. The device manager displays Hardware ID's indicating something is there.
USB\VID_1949&PID_0007&MI_00
USB\VID_1949&PID_0007&REV_0216&MI_00
I have my hunches on what the problems could be. But I've been working this for a couple days now and have become agitated.
I have never had to many problems with this type of stuff. I won't say I'm a noob at this kind of work however, I feel like it at this point.
Worst comes to worst I would crack her open. But that is risky business. I rarely touch the inside of my devices.
Any words of wisdom are most appreciated.
If you happen to have adb access I'm guessing there's a system app that needs to be chmodd'ed to the right permissions, or if you want you could run "adb reboot bootloader" (and do what I mention next after it's in fastboot mode), however if you have no adb access then you will need to get a fastboot cable and restore with kfhd SRT or kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
As I said before the Kindle does not respond when I use KFHD SRT or the Aid Kit.
That's because for those tools to work you need to already be in fastboot mode with the fastboot drivers installed. Have you managed to get into fastboot mode?
Sent from my Amazon Kindle Fire HD using Tapatalk
As of now what you see is what you get. All I get is a never ending boot screen. I see you made a comment about fast-boot drivers. I might be missing something in the equation. I'm going to retrace my steps and start from scratch. Hopefully I will be able to get this thing working.
Well, I cannot get my Kindle to boot into fastboot. Tried reinstalling ADB drivers and everything. Even tried using the First Aid with no luck. I think the boot loader might be damaged. I keep the kindle off, plug it in, try to initiate a fastboot through the KFFA, it dims and continues normal boot operations. Stopping with the Kindle is upgrading notification.
Those commands aren't going to work unless adb was ever active in the first place, you are going to need a fastboot cable to fix it, the bootloader is behaving just as it should BTW, so it is fine, once you get a fastboot cable it will tell the device to enter fastboot when it powers on, from there kffa should work just fine outside of probably having to install Tue drivers because of how finicky it is. The ones in my signature will surface when the time comes.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I've been having issues with my phone for a while. If I let my phone battery die to the point that the phone shuts off, it is nearly impossible to get back on. I can boot into bootloader but that's it. The status will say "Battery OK (charging)" which is a lie. The battery is not OK and it is not charging, which is why I can't leave the bootloader and boot android. It also says "Connect USB Data Cable" even though it is connected but I'm not sure if that's typical. I usually have to play around with various combinations of restarting my phone/unplugging the USB cable until it finally starts accepting a charge.
Anyway, I'm trying to flash M but when I get to the point of using the bootloader, fastboot does not work. fastboot devices returns no devices and it fails. ADB works perfectly fine and can detect my device. I know my drivers are good because a) they were untouched and worked previously and b) I fully uninstalled everything and installed Android SDK and can access my filesystem.
I believe these two issues are related. I'm running 5.0.1 LMY47I and my phone is decrypted using whatever method Wug uses in his toolkit.
Addressing your points.
1) just because adb works doesn't mean fastboot will / should
2) SDK doesn't install drivers.
Do check device manager and uninstall the driver and reinstall the naked driver following instructions in my thread. Nexus general > sticky roll up > adb and fastboot.
You're probably right, they may well be related but I just wanted to point out that 1 and 2 don't necessarily point to that being the case.
well I did get further but it is not fixed. It is a driver issue possibly. I think I may have messed my phone up, its stuck on the "google" splash screen now
Each time I loaded something to my device, ie radio, it went back to "Connect Data cable" but if I disconnected it and reconnected it, it would then transfer.
RandoTheKing said:
well I did get further but it is not fixed. It is a driver issue possibly. I think I may have messed my phone up, its stuck on the "google" splash screen now
Each time I loaded something to my device, ie radio, it went back to "Connect Data cable" but if I disconnected it and reconnected it, it would then transfer.
Click to expand...
Click to collapse
This sounds dodgy and could be multiple issues.. Really.it's a case of ruling out the hardware.. Cable, USB port,.computer. .it's tricky because it could be driver related too.
So I tried again right after getting stuck on the Google screen and got Marshmellow working, but I still had to unplug the cable after every fastboot command completed. Windows would popup with an "Unrecognized device detected" window, and the device would show as Unknown Device in device manager under USB ports. After the fastboot command completed the message would go back to "Connect USB Data Cable" and would not work unless I re-plugged it..
I tried reinstalling the naked drivers but Windows says they're all the same and that there is nothing to update. I also have gone through the full uninstall using USBDeview . I have tried other cables, even with the charging fiasco. The one thing I have not tried is another PC but that doesn't explain charging issues.
Sounds like my Nexus 7's dodgy USB port. It's gotten a bump somewhere along the road and doesn't connect properly with the USB cable anymore. Only way I can flash anything is by firmly pressing the cable into the port the whole time.
What I'm trying to say is that it sounds like your USB port is broken. Possibly...
Well I'm just going to stick to stock Marshmallow so I don't have to worry about fastboot and I'm never going to let my phone battery die. I'll see how long I can go
First time posting here. And I have tried all that i can think to do. My daughter has a Google Pixel 5a, that was not backed up to the cloud, for which she dropped and the screen doesnt work...like black screen. I have tried some of the tools to back it up, but requires USB debugging on, and I am not sure she had dev tools turned on and I cannot figure out what to do. Device seems to turn on as PC can read it. Any ideas? I am stumped. I tried the button sequence to try to get into adb fastboot but i havent had any luck yet.
bskramer79 said:
First time posting here. And I have tried all that i can think to do. My daughter has a Google Pixel 5a, that was not backed up to the cloud, for which she dropped and the screen doesnt work...like black screen. I have tried some of the tools to back it up, but requires USB debugging on, and I am not sure she had dev tools turned on and I cannot figure out what to do. Device seems to turn on as PC can read it. Any ideas? I am stumped. I tried the button sequence to try to get into adb fastboot but i havent had any luck yet.
Click to expand...
Click to collapse
Check Device Manager when the device is plugged in. If it shows up as Qualcomm something or other, the only way to recover it is via a mainboard replacement, which will wipe data.
Even with ADB/fastboot, it's not possible to back up the phone without root.
Shows up as MTP...No qualcom
bskramer79 said:
First time posting here. And I have tried all that i can think to do. My daughter has a Google Pixel 5a, that was not backed up to the cloud, for which she dropped and the screen doesnt work...like black screen. I have tried some of the tools to back it up, but requires USB debugging on, and I am not sure she had dev tools turned on and I cannot figure out what to do. Device seems to turn on as PC can read it. Any ideas? I am stumped. I tried the button sequence to try to get into adb fastboot but i havent had any luck yet.
Click to expand...
Click to collapse
I just found out from my local UBreakIFix that Google has extended their warranties for all screen issues on the Pixel 5a, which means you could get a free screen replacement. My warranty expired back in Aug 22 and they gave me a free replacement for my black screen. It was done in 20 minutes. https://support.google.com/pixelphone/answer/11833075?hl=en