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.
Related
So I've never had a problem using ADB. My path's are setup correctly, I have the most updated version of the SDK and everything that goes with it. My USB ADB drivers are up to date, but for whatever reason about 2 weeks ago, it stopped working.
I usually use programs like AndroidCommander, or something along those lines for backing up my apps on my PC. Now when I launcher them (and my phone is plugged in) they just, don't open. The program loads, it can be seen in task manager, but the program doesn't open. If I unplug my phone, I get an error code (on the pc) then the program opens. Other programs like YouADB get stuck at "loading file structure" when trying to open.
I can still do adb devices, from console, and my phone is shown, and I can shell in to the phone. However I can't use commands like adb install, it will show the "354kbs...."and w/e else is in the first line when it trys to install an app, but instead of giving me a "successful", or even an error, it just drops me back to #, and the app is not installed.
I have tried completely removing, and re downloading the entire SDK, I've tried removing the adb drivers for my phone, and reinstalling them, and I'm just at a lost for what the problem is.
Does anyone have a clue what could be going on here? This is becoming a real pain in the butt.
Bump it up
Does anyone have any idea why a Hero would for no apparent reason while sitting on a charger go into a reboot cycle only bringing up the htc sign and then the phone with triangle and exclamation point and do nothing else? the phone has never been rooted or anything just did that on its own.
Would running the Regawmod rooter exe possibly fix this?
Also i have another Hero i was given that i have tried to run the rooter on but everytime i do i get the error "Necessary HTC drivers are missing".
i have tried three different versions of HTC sync since i don't know where to get the drivers seperately. all with the same result. any help will be greatly appreciated.
Thanks in advance
Tap my avatar or search the hero dev section for my thread on how to install adb. Try those drivers and see if they work for you. If they do then try the hero rooter or run the ruu.
#Root/Hack-Mod_Always*
no luck. still have the orange triangle and exclamation point, tried the ADB thing and its not recognizing that the phone is there. but when i plug the phone into the computer it acts as though it is mounting as an external drive but when i click the drive letter it says to please insert a disk.
when i try holding the home and power button i get an error at the bottom of the screen that reads "E:Can't open /cache/recovery/command"
Tuvan03 said:
no luck. still have the orange triangle and exclamation point, tried the ADB thing and its not recognizing that the phone is there. but when i plug the phone into the computer it acts as though it is mounting as an external drive but when i click the drive letter it says to please insert a disk.
when i try holding the home and power button i get an error at the bottom of the screen that reads "E:Can't open /cache/recovery/command"
Click to expand...
Click to collapse
Ok what steps did you take?? Details please?? And when you setup adb did you type adb devices??? And how did you go about setting up adb???
#Root/Hack-Mod_Always*
i went through the steps in your post minus the mobile stream tether and i can't enable usb debugging because the phone will not boot up at all. it has been this way since last night. was just sitting charging and then went into a reboot cycle only bringing up the HTC logo then after awhile of that ended up at the screen its at now with the phone with the triangle and exclamation point.
i did type adb devices but it didn't come up with anything in the list of attached devices.
Edit: i did put the easy tether on the computer but since i can't access the usb options on the phone i can't set up the debugging. i don't know whats up with the phone
Tuvan03 said:
i went through the steps in your post minus the mobile stream tether and i can't enable usb debugging because the phone will not boot up at all. it has been this way since last night. was just sitting charging and then went into a reboot cycle only bringing up the HTC logo then after awhile of that ended up at the screen its at now with the phone with the triangle and exclamation point.
i did type adb devices but it didn't come up with anything in the list of attached devices.
Click to expand...
Click to collapse
The mobile stream steps were the android drivers I originally suggested you to try. So try those drivers and see if they work for you. I posted that thread for users who were having trouble with the htc drivers
#Root/Hack-Mod_Always*
ok well i hooked up the working hero so it would install the drivers, which it did, then i hooked up the hero that is stuck for no apparent reason on the error screen and i was finally able to run the regawMOD rooter but i guess because it doesn't have usb debugging enabled it won't allow anything to happen.
just trying to sort out what happened to this phone for it to be stuck at this error screen. nothing has ever been done to it just happened last night while it was charging
Tuvan03 said:
Does anyone have any idea why a Hero would for no apparent reason while sitting on a charger go into a reboot cycle only bringing up the htc sign and then the phone with triangle and exclamation point and do nothing else? the phone has never been rooted or anything just did that on its own.
Click to expand...
Click to collapse
What you're seeing is the stock bootable recovery image. Pulling the battery and powering it on again should make this go away. Have you already tried that?
jasonmaloney said:
What you're seeing is the stock bootable recovery image. Pulling the battery and powering it on again should make this go away. Have you already tried that?
Click to expand...
Click to collapse
yes have already tried this a couple times, now it just sits at the phone with triangle and exclamation point. won't do anything else
well took the phone to sprint and they deemed it unsalvageable so i guess this is moot. he tried all the standard resets etc. so thanks for all the help but guess the phone is a brick now. wouldn't replace it because the moisture indicators had been tripped.
youd think there would be a way to reforce the OS onto the phone to try to get it going again.
If it was sitting on the charger and went bad, perhaps your charger fried it in some way. Sorry to hear your loss, but look it as an opportunity to get an better phone
Hey guys
Last night I broke my SGS's screen. The phone is rooted and I know it still works as can hear it get texts and boot up correctly.
I wanted to just swap the phones out but I have a lot of valuable pictures etc on the phone that I hadn't backed up yet.
Is there any way to access the hard drive from the computer w/o being able to access the phone?
I tried the "Screencast" app but I cant seem to get it to work. I tried doing some searches on here but I'm not exactly sure what to look up.
I have insurance on my phone so I can get a replacement, I'd jsut like to get my pictures and any text messages i may have missed (but mainly the pics)
Any insight you guys have would be much appreciated.
Thanks in advance!
Reboot in recovery mode. That would give you adb access to the phone and you can adb pull your pictures with "adb pull sdcard/DCIM/Camera".
thanks for the reply.
sorry i'm kind of new at this stuff. my friend rooted my phone and did all the dirty work. i have no idea how to use adb or w/e
do i need a linux machine? also, how can i reboot in recovery mode if the screen is completely disabled?
do get via ADB you need to ADB kit or the Android SDK kit, theres a helpful section on how to do ADB but it shouldnt be a problem, i also recall that after ADB is installed you might be able to use Android explorer to go to the phones pciture directory and get them like that?
i'm having a horrible time trying to get this setup lol
i think a problem i'm having is i dont know if USB debugging is enabled on my phone, and since the screen is broken i can't turn it on.
anyone else have any other suggestions?
redstar2k said:
Reboot in recovery mode. That would give you adb access to the phone and you can adb pull your pictures with "adb pull sdcard/DCIM/Camera".
Click to expand...
Click to collapse
it seems i can get it into what i ~think~ is recovery mode (it didnt make the typical noise it makes when booting up, and my bottom row buttons light up if i press the power button then one of the buttons)
not sure what screen im in honestly... but even still, the computer doesnt detect that anything is plugged in and ADB doesnt detect any devices...
maybe with usb cable?
thats what im doing is using USB cable.. problem is i cant mount my usb from my phone as the screen is broken.
i cannot do it blind either i dont believe, i dont think the screen is detecting my fingerpresses at all
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