Related
I'm trying to fix a friend's G1, which he bought on ebay from US.
I've no experience whatsoever dealing with Android, so this is new. But I'm fairly capable of understanding every technical process you could use, so I think I'll understand your explanations.
Whenever I connect the device to a PC via USB, the computer detects an unknown device, but the phone just restarts at the splash screen. Notice that it has two different behaviors: When there's no cable connected, it just shuts down after 2 or 3 seconds at the Android screen; when I connect a USB cable, instead of shutting down it restarts continuously.
The first thing I did was to unroot the phone and put the official RC29 rom. Unfortunately, the problem persisted.
I have access to the recovery menu and the bootloader (I don't know if this is the correct term, it's the Camera+Power menu).
The major problem (I think) is that I don't have access to the console, as the recovery menu I have is the original one.
So, can anyone help me with this? Thank you.
Options:
Root the phone and use a custom recovery.
ADB also enables use of the terminal through the shell command. -- You could also use ADB to get a logcat and see what happens before the reboots.
But I don't see how the terminal would help, it sounds like hardware failure if it does it with a stock and custom rom.
Don't I need access to the OS in order to root the phone?
Which SPL do you have?
A boot loop or crash at startup can be caused by many, many things.
Get hold of the android sdk.. inside the /tools folder are 2 programs called ddms and adb, you can start the phone while connected by usb and use either of these programs to grab a startup log. Post the log here and we can hopefully see what's causing the crash.
You probably shouldn't have unrooted the phone.. that's going to make things more difficult.
adb and ddms can't find the device. There's an "Android Phone" in the Device Manager, but as the phone keeps restarting, I guess it isn't on enough time to be able to be detected by adb and ddms.
Edu115 said:
adb and ddms can't find the device. There's an "Android Phone" in the Device Manager, but as the phone keeps restarting, I guess it isn't on enough time to be able to be detected by adb and ddms.
Click to expand...
Click to collapse
Did you install the usb driver that's packaged with the sdk? the one windows installs by default doesn't work for adb or ddms.
If you've got this driver installed and ddms doesn't see the phone, that's pretty ominous.. it should show up there as "offline" as soon as you power it on.
goldenarmZ said:
Did you install the usb driver that's packaged with the sdk? the one windows installs by default doesn't work for adb or ddms.
If you've got this driver installed and ddms doesn't see the phone, that's pretty ominous.. it should show up there as "offline" as soon as you power it on.
Click to expand...
Click to collapse
Thanks, I fixed that and I got the ADB drivers, but the same thing happens. I can't get the attached devices, nothing appears on the list.
One note: this last time I tried to connect the phone via USB it booted, but I couldn't sign in, because as soon as I slid the keyboard, the phone shut down.
So, now I have a "Android ADB Interface", but still no devices listed with adb device.
Right now sometimes (like in 40 tries) the phone turns on and I can use the touchscreen, but when I need to sign-in, it tells me to slide the keyboard and it shuts down.
I still can't get the attached devices using adb, even after trying in other computers.
Edu115 said:
Right now sometimes (like in 40 tries) the phone turns on and I can use the touchscreen, but when I need to sign-in, it tells me to slide the keyboard and it shuts down.
I still can't get the attached devices using adb, even after trying in other computers.
Click to expand...
Click to collapse
what happens if you start with the keyboard open?
you know, it could be a hardware fault, a dry joint or loose wire
the sliding of the keyboard just jolts it.
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'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
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Never set Google to back up photos?
Sent from my Nexus 6 using XDA Free mobile app
leetonion said:
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Click to expand...
Click to collapse
first off, fastboot only connects to the device in the bootloader mode. ADB NEVER EVER connects to the device when in the bootloader. that sound you are probably hearing isnt "adb" connecting, but just the sound you hear when you connect to the computer.
I know, just didn't word it right. The chime from my computer is just it recognizing the phone, but it coincides with adb losing connection and (I'm assuming) my phone crashing or rebooting somehow...I just need some way to pull files from the sdcard folder and adb doesn't seem to work in my current situation.
If you are lucky and the mobile boot into system then try this http://www.vysor.io/
Sent from my Nexus 6 using Tapatalk
AhmadOkda said:
If you are lucky and the mobile boot into system then try this http://www.vysor.io/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Interesting app ya linked to, but wouldn't he need to be able to install the app on the device before he would be able to see it on his desktop? Just asking because it said available on Google Play.
Sent from my Nexus 6 using XDA Free mobile app
leetonion said:
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Click to expand...
Click to collapse
Does your Nexus have root access?
31ken31 said:
Interesting app ya linked to, but wouldn't he need to be able to install the app on the device before he would be able to see it on his desktop? Just asking because it said available on Google Play.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I tested dot on my mobile
You only need usb debugging enabled and it will install itself with no action from my side
Sent from my Nexus 6 using Tapatalk
You can do adb commands in recovery. if you can get into recovery you should be good to go.
Miss read OP. Thought you were trying to boot normal and not boot into recovery.
leetonion said:
I know, just didn't word it right. The chime from my computer is just it recognizing the phone, but it coincides with adb losing connection and (I'm assuming) my phone crashing or rebooting somehow...I just need some way to pull files from the sdcard folder and adb doesn't seem to work in my current situation.
Click to expand...
Click to collapse
To help troubleshoot, try holding down power when you think it has booted to feel for a vibration. If it vibrates you know it booted. From there you may need to enter a password through adb (there are guides, I can't remember of f the top of my head how). Once you are in, you can use this to help navigate your phone http://forum.xda-developers.com/showthread.php?t=2786395. There's a learning curve and high latency but, it works. I have been in a similar situation and I was able to pull it off using this method.
As far as it rebooting or crashing, or whatever else, there's not much I can do to help with that across the internet, good luck to you.
And one last thing, try playing with this. http://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html Looks like you can control TWRP through a command prompt, maybe you can get your files.
And one last, last thing. When in the bootloader menu, the options go like this. You cna also get into these optiosn through fastboot but, I figured it couldn't hurt.
START <--- First option you boot into. If you are holding it's possible to go down one extra though, be careful.
RESTART BOOTLOADER
RECOVERY MODE
POWER OFF
FACTORY MODE
BARCODES
BP TOOLS
QCOM
BOOTLOADER LOGS
5th gen 7" Kindle Fire here that I rooted using Rootjunky's tool a few years back. Running CM on it, etc. Everything fine until screen and LCD totally smashed. Main goal was to get photos and files off device, but all attempts to connect to PC failed. (I thought ADB debugging had always been set to on, but this might have been changed.) Wife put a pin code on it that was never visible. Tried an external keyboard with tongle to get past pin code - didn't work.
So I ordered another (used) 5th gen that just came in the mail. Turned on fine (has Amazon's OS). Rather than mess with a heat gun and try to replace the LCD on the broken one, I thought I'd try simply swapping motherboards. So I put the motherboard from the device w. broken screen into the one that just arrived. After some trial and error, I actually got it to turn on. But it's stuck in fastboot mode.
No Amazon splash screen, just powers straight on to fastboot mode. I tried in Windows 10 to get the OS to detect the device. The best I could do was for it to recognize an unknown android device. I installed the drivers from RootJunky, but made no progress.
Powering on, powering off makes no difference: always straight to fastboot mode. I'd love to just get access to the files. I wouldn't care if I had to put the other motherboard back in, root the whole thing all over again.
Barring that, how can I: a) get the device recognized via USB, and b) miracle of miracles, get out of fastboot mode and start using it?
Thanks.
For the record, I solved this by connecting the Kindle to the PC, using RootJunky's tool. I think either installing the ADB or fastboot drivers did it. Or just using the tool to tell it to reboot from within fastboot. Can't be sure.