Develop Bugs

[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work

[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work
Hi guys,
I've watched the n00b video and been googling for the last few hours as well as reading through various pages on the XDA forum. I've found a lot of problems that are kinda similar and tried various solutions but don't seem to be quite getting there.
Basically I had Virtuous Affinity as the OS and clockworkmod installed (should be the most up to date versions of both, they were put on no more than a week ago) as well. I also had a backup of current OS and so on on the SD card, as well as the original zip of the rom.
I decide I want to give ICS a go and so I downloaded the betamod ICS and then loaded it. It asked me if I wanted to do a dalvik cache wipe, a dalvik cache + data wipe and a third option I don't recall. I went with the dalvik cache wipe (at the time I was under the impression that was the correct course of action) then put it back in my pocket while ICS installed.
I get my phone out of my pocket later and it's kinda stuck on what looks like (but logically isn't, I'm guessing it was meant to be a splash screen type thing while ICS installed or some such) a screensaver which just loops endlessly. The only thing you can really do is take the battery out and turn her on again, in which case you once again end up in the endless screensaver loop.
I've tried booting to recovery using volume - and the power button and unfortunately it just boots straight into the looping screensaver again.
Getting a bit worried and feeling adventurous I tried seeing what I could do with ADB, however the computer seemed unable to recognise that any device was connected with ADB devices not listing anything.
I've read up a lot and I'm at a loss as to what to do - there's a rom on the SD card and there also should have been a backup but I just can't get it into recovery.
I do have the ability to view the SD card on another device and interact with it, so if there's a potential SD fix, that's certainly not out the window.
But yeah, I'm clueless how to proceed here and very green at the whole rom business. Can anyone advise what I might try to do from here? I don't care what state I end up going back to, or if I lose my data, I can get all that back, I just want the phone in some semblance of basic operation.
I'll be keeping an eye on the thread, if I've left out any pertinent data ask away and thanks in advance for anyone with a clue how I can fix this mess .
EDIT: Post may be better off in ICS thread above and I do apologise if so, I would move it but I seem unable to delete it.

Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.

ik222 said:
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
Click to expand...
Click to collapse
I have, it doesn't work. I've left the battery out for a fairly long period. Volume - + power still just brings it back to the "screensaver" loop.
Thanks for the suggestion though.

Turn the phone off completely; pull the battery out for a bit then replace it and don't touch anything. Don't try to turn it on. Plug the phone by usb to your pc (still turned off). At the command prompt in the folder containing adb.exe type "adb reboot recovery" - the phone should power on and go to recovery where you can wipe properly and reflash whatever you want.
You should be able to boot to recovery using the volume down + power button combo (hold the volume-down key, then press and hold the power button and keep both held until you get to the bootloader menu); the only thing that's wrong with your phone is that you've flashed one ROM over another without wiping it first, so the ROM can't load but this shouldn't affect your bootloader or recovery.
Worst case you can flash a RUU which will restore it to the official firmware; you'll then need to re-root and re-install a recovery image to be able to flash custom ROMs again.

Very helpful post, thanks! I'll try all that and see how I go, I'll post if I still have trouble.
Yeah I dunno why I can't boot to recovery it's weird. The volume button wasn't working, so I removed it and am pressing in the volume down portion of the volume button with a pen while holding down the power button. It's possible perhaps I'm not successfully depressing volume down, but I'm 99% sure I am and that that's not it. I am however doing it as you and other guides advise, depress volume down, hold it and then depress power and hold both for about three seconds, no joy!
Anyway, as said, I'll try what you're recommending and see how I go. Thanks!

hopscotchjunkie said:
At the command prompt in the folder containing adb.exe type "adb reboot recovery"
Click to expand...
Click to collapse
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.

Ethicistabdiel said:
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Click to expand...
Click to collapse
Yeah that was what I meant; I've got a feeling that that only works when the phone is powered off if you had USB debugging activated on the phone beforehand, so if that's not working that might be why.

c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.

Accidental double post, sorry.

You need to try get into recovery mode, where you can do a full wipe and see if that fixes anything.
Firstly, remove your battery then re-install it, your phone should still be turned off at this stage. Press and hold the volume down button, then additionally press and hold the power butter, until something appears on the screen. If the bootloader appears, you can then boot into recovery from there.
If the above fails to work, report back with your results and hopefully something else will be suggested.

Ethicistabdiel said:
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Click to expand...
Click to collapse
Your only other option to get into recovery is the volume-down/power-on combination. Like I said, I can't think why that's not working unless it's related to your missing volume button (maybe it's not maintaining a constant pressure on the button when you're using whatever to press through the hole).
If you still can't get that to work, I would suggest finding a stock RUU and flashing that. It's an .exe file that runs from your PC and will return your ROM, bootloader and radio back to stock. Obviously that means you'll lose root and your custom recovery so you'll need to do all that again from scratch. There's a sticky in the dev section with a link to a thread with various RUUs (it's named something along the lines of "shipped & test ROMs" - I'll check that and link to it once I've dragged myself out of bed to the computer). You'll lose all your data, but if you took a backup beforehand you can restore that once you're back up and running.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.

Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.

http://forum.xda-developers.com/showthread.php?t=824357&page=5
Guessing you mean that as far as the ruu thread. Am downloading a stock rom atm, with shaped internet till tomorrow, meh! Will see how I go. Have a feeling phone was probably Vodafone branded at stock though, so that could make for extra fiddling but yeah, fingers crossed.

If you are able too install a stock-rom you can work from their than install 4EXT recovery
touch than you doen't need the volume buttons.

I downloaded the most recent stock rom on the link above. When I try to install it though, phone off or on, it advises a USB connection error. Is this likely to be because I originally had vodafone stock and need to make a gold card, or should it still at least be recognising it? It does advise not to run any programs on the phone or anything when while installing the update, but of course, as long as my phones turned on it's stuck on the damned screensaver loop.

http://forum.xda-developers.com/archive/index.php/t-841890.html
Gonna give that a go, fingers crossed!
D'oh, just found out my mobile was Three at stock and not Vodafone, the search continues .

Gah, I'm about tearing my hair out here, I want my damned phone back . Stuck using a $79 Huwawei Vodafone thing at the moment and it's so so so awful.
Anyway. I was under the impression that making a goldcard would mean I could RUU a non-Three stock rom on the phone. I made a goldcard following these instructions; http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then I turned the phone on as the RUU advises, (meaning it's scrolling through the feckin' "screensaver") and start the process and once again get a USB connection error.
What's the better process at this stage, try and take it back to Three stock? I don't see how I can at the moment, the only Three stock I can find seems to be rom, not RUU, meaning I'd need to load from the phone, which I can't due to no recovery. Or should I keep trying to get the goldcard thing to work, maybe try some different RUU's or something?
I'm open to any other suggestions as well. Had a bit more of a fiddle around with my volume down button, no matter what I do though, I can't get recovery mode. Always boots first to the white HTC screen and then starts the infernal "screensaver" loop.

Ethicistabdiel said:
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
Click to expand...
Click to collapse
How come the volume down button be broken. When you were using Affinity Rom weren't you able to use your volume button for music. Remove SD card from phone then press "First - Volume down gently for 2 sec" & press-hold power button when it goes into bootload place your sd card back select option "REBOOT RECOVERY". I think your panicking too much just be patient nothing is wrong, i think your just hurrying it up...

The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .

Ethicistabdiel said:
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Click to expand...
Click to collapse
The only option i can think of is "Fix your volume button from your nearest Service centre". Without that you cant do anything. I am Sorry....

HELP! Cracked screen, can't unlock to recover photos, etc.

Hello smart people. Hoping someone there has an idea for me...
This morning I dropped my GN and killed the screen. The display kinda-sorta works, but the touch sensor is non-op. OK, no problem, I've got in contact with Samsung and they'll fix it for the same price I can buy a replacement lcd/digitizer assembly anywhere I've found. Only problem: They'll be wiping the phone.
90% of what I need on the phone is synced to the cloud in one way or another, so I'm not too worried, but I WOULD very much like to recover some recent video and pictures that haven't been archived yet (daughter's dance recital). Phone is still working, except that it's pin-locked now (company policy) and I can't see the file tree to pull the stuff out.
Then I thought I'd play with the GN Toolkit. Only problem there is I guess I need USB debugging turned on, or something else I need enabled is disabled and I can't twiddle the menus to enable it.
Let's start with the obvious easy question: Any way to sync to the file system without unlocking via the touchscreen?
Failing that, is there any way to unlock/enable whatever I need to use the toolkit to pull the images out of the media directory?
I have a little time before I need to send the phone to Samsung for repair, so I'm willing to mess with this a bit and learn whatever I need to learn, but I'm not sure if what I need to do is even possible.
Thanks.

Can't just plug the phone in to a computer and it appear as a media device? Should be able to just pull the internal data.
Sent from my sprint galaxy nexus

ÜBER™ said:
Can't just plug the phone in to a computer and it appear as a media device? Should be able to just pull the internal data.
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
If the phone is pin-locked, the file system shows as empty when you connect as a media device (until you unlock it).

Herbie555 said:
If the phone is pin-locked, the file system shows as empty when you connect as a media device (until you unlock it).
Click to expand...
Click to collapse
Sorry wasnt aware of that. If you cant get it unlocked.. and USB debugging isnt enabled... then your outta luck.

You could get an MHL adapter and plug in a mouse, then use that to enter your pin at the lock screen. You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.

Is there another way for enable debugging on Nexus?
I guess we can't enable debugging via adb, right?
If you just find a way around to do that, maybe you can use the line "adb pull"
(If you search for "adb commands" on Google you will find a list commands to use on developer.android.com)

Stadsport said:
You could get an MHL adapter and plug in a mouse, then use that to enter your pin at the lock screen. You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.
Click to expand...
Click to collapse
If he's on stock then yeah that will delete his internal. If he's on a custom recovery no.
Sent from my sprint galaxy nexus

There's a plug in for the SDK called screencast which let's you use your computer screen a duplicate screen to your Android device. You can select things with your mouse. We used to use it in the early gingerbread days of my old vibrant when recovery was hidden behind the double rainbow
Sent from my Sprint Galaxy Nexus CDMA using xda premium

mnoguti said:
I guess we can't enable debugging via adb, right?
If you just find a way around to do that, maybe you can use the line "adb pull"
(If you search for "adb commands" on Google you will find a list commands to use on developer.android.com)
Click to expand...
Click to collapse
Debugging has to be enabled for ADB to be able to interact with the phone.

Glad I ran across this thread. I have a colleague in the same situation.

Stadsport said:
You could also go into recovery and factory reset, as that shouldn't touch your /sdcard contents.
Click to expand...
Click to collapse
Ahh, this might be a path to victory. Didn't realize I'd be able to do a factory reset and have stuff stay intact. Might be my best approach...

ÜBER™ said:
If he's on stock then yeah that will delete his internal. If he's on a custom recovery no.
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
Oops, got excited. Yeah, stock ROM. So a factory reset will wipe everything?

Herbie555 said:
Oops, got excited. Yeah, stock ROM. So a factory reset will wipe everything?
Click to expand...
Click to collapse
Yes. And the only way to get anything to work is to have USB debugging enabled. Screen cast only works with adb enabled.

Looks like I might be boned on this one. Thanks much for everyone who had suggestions. Sounds like leaving USB debugging enabled might be a best practice from now on, eh? (Or at least making sure EVERYTHING syncs to the cloud automatically...)
Looking at the google policy manager, I can remotely: Lock the device (duh), Reset the Pin, make it ring, or "Wipe", which I'm guessing is a factory reset. Might try that as a last resort, but I'll remain hopefull.

I'm sure you've tried this - but if you''re on stock you may be able to boot into recovery using voldown + power (or is it volup+voldown + power? Not sure, can't remember). THEN plug it into your machine and see if it shows up in the toolbox as a connected device...

adb should be enabled in recovery. reboot to recovery [power + vol up and down] mount sdcard and then adb pull whatever files.

ipfreelytech said:
adb should be enabled in recovery. reboot to recovery [power + vol up and down] mount sdcard and then adb pull whatever files.
Click to expand...
Click to collapse
Feel like I'm getting closer. I can see enough screen to scroll through to "Recovery Mode" and hit enter. It seems to reboot at that point, but then I can't see enough of the screen to navigate any additional menus. Should I be able to connect at that point?

Herbie555 said:
Feel like I'm getting closer. I can see enough screen to scroll through to "Recovery Mode" and hit enter. It seems to reboot at that point, but then I can't see enough of the screen to navigate any additional menus. Should I be able to connect at that point?
Click to expand...
Click to collapse
Plug it in via USB and see if the Toolkit picks it up...

thepatman said:
Plug it in via USB and see if the Toolkit picks it up...
Click to expand...
Click to collapse
I've apparently managed to get it mounted in the Bootloader interface and in fastboot mode, but can't figure out how to get it into adb mode, which is apparently what I need to do the pull.
The LCD has gotten worse, I have almost no visibility now. If I knew now many down or up strokes to make at each menu stage, I could probably do it blind...

Herbie555 said:
I've apparently managed to get it mounted in the Bootloader interface and in fastboot mode, but can't figure out how to get it into adb mode, which is apparently what I need to do the pull.
The LCD has gotten worse, I have almost no visibility now. If I knew now many down or up strokes to make at each menu stage, I could probably do it blind...
Click to expand...
Click to collapse
Can't do adb in Fastboot mode. While in flastboot mode. Hit the volume up twice and hit the power button. This will boot into recovery. Then try using the
Code:
adb devices
command. If you get a gibberish code next do device ID. Then your good. Go ahead and
Code:
adb pull /sdcard/
Sent from my sprint galaxy nexus

[Q] Help desperately needed - Galaxy Nexus not booting after installing Jelly Belly!

I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?

bluroot said:
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
Click to expand...
Click to collapse
the proper term to use here is bootloop
ur phone bootlooped and u need to flash back the stock firware via odin
go back in the dev section and find somethng relatd to odin
remmbr bfre flashing any rom u shud always backup ur rom via clockworkmod
u must have done something wrng while flashng jellybean mod...take the steps crrctly
EDIT:- http://forum.xda-developers.com/showthread.php?t=1827685
heres the link to fix ur phone
properly take the steps plzz

bluroot said:
I really hate to join under such a condition (it's an amazing site which I thought I would join for better reasons when time permitted), but my new Galaxy Nexus just went to hell on me after flashing the (apparently) popular Jelly Belly mod.
I started with a rooted 4.1.1 Jelly Bean OS with ClockworkMod Recovery, and now it looks like disaster after using that to flash Jelly Belly - what happens now is my phone boots up to the point where it flashes that colored Google "X", but it never proceeds beyond this point. I cannot put a different mod on my phone because there is no connection with my computer, and I can't stop my device from thrashing without a battery-pull. Is there any way save this phone and put plain Jelly Bean back on it?
Click to expand...
Click to collapse
Are u able to boot into CWM recovery, Power and both volume up and down?

garner said:
Are u able to boot into CWM recovery, Power and both volume up and down?
Click to expand...
Click to collapse
When I do, I have that "Downloading..do not turn off the target!" message. Why this - I did remove the supersu file, although I think I left my clockworkmod file on the root because now you have to re-flash that every time you use it. Now I have no option other than "Start" - any chance of breaking through now?

bluroot said:
When I do, I have that "Downloading..do not turn off the target!" message. Why this - I did remove the supersu file, although I think I left my clockworkmod file on the root because now you have to re-flash that every time you use it. Now I have no option other than "Start" - any chance of breaking through now?
Click to expand...
Click to collapse
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone

Zepius said:
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Click to expand...
Click to collapse
Do you mean that I need to continually rock the Volume key up and down while holding the Power button? Volume Up with Power put it in boot mode, and when I tried rocking it a couple of times I got the same result. It I understand you correctly, the idea sounds tricky. Is this supposed to work on a Galaxy Nexus?

press and hold both ends of the volume button and the power button... its really not that hard.

Zepius said:
thats not fastboot, thats odin mode. use vol up and down and power button to get to fastboot mode
the entire reason your phone is behaving the way it did is because you didnt wipe data/cache before flashing the rom.
you really need to do some reading before you start modifying your phone
Click to expand...
Click to collapse
What I really should have done was slow down, or quit while I was ahead to get some rest last night! I had researched the root process for my phone ad nauseum, which I know is why I succeeded at getting ClockworkMod safely installed. By the time that was done I was tired, but I counldn't stand the thought of living without my files loaded on my phone - I was in the bad state of needing too much to complete what I had intended to do. I see I had the wrong impression that ClockworkMod would take care of the whole process once I had that working, guess it didn't. When you've been through the process of installing a hundred versions of Windows and Linux on a PC, which never needs to be pre-wiped (the new OS does that), who would have thunk it's that much different with a phone computer?

Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.

bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
This is another thing I never would have guessed without being told specifically, that it's even possible to hold down both ends of a rocker switch and have it do a different function - I tried this, and now it works! I had used my PC to root my phone last night, and right now I'm at work, where there will be time to go through this in a couple of hours. I took a brief look at the tutorial recommended by Zepius, and am wondering if I am set to proceed. I plan on using my work PC, not the one at home with the drivers I used to root my phone. Nobody else uses it and I have never used it for anything phone-related. Can I presume any drivers which I'm warned should be uninstalled would be on the PC which is used, and not the phone?

bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
Sorry, I had to work, but now there's time and I thought I would try my work PC, which is virgin (so to speak) of mobile devices and drivers. It's a Windows XP system, and right now it's not looking good because when my phone is plugged in, there isn't a "Portable Devices" or "Mobile" category under Device Manager. Do I have a better chance of this working on my home Windows 7 system?

bluroot said:
Sorry, I had to work, but now there's time and I thought I would try my work PC, which is virgin (so to speak) of mobile devices and drivers. It's a Windows XP system, and right now it's not looking good because when my phone is plugged in, there isn't a "Portable Devices" or "Mobile" category under Device Manager. Do I have a better chance of this working on my home Windows 7 system?
Click to expand...
Click to collapse
I guess that's a never-mind, I should have had my phone on! It's in Fastboot mode now, but I still don't know if what I see in Device Manager is good for what I'm trying to do. No portable device, phone, nor galaxy nexus, but what did change is I have "Broadcom Nextreme 57xx Gigabit Controller" appearing under "Network Adapters". Is this a problem to be dealt with differently when your phone is bricked?

bluroot said:
I guess that's a never-mind, I should have had my phone on! It's in Fastboot mode now, but I still don't know if what I see in Device Manager is good for what I'm trying to do. No portable device, phone, nor galaxy nexus, but what did change is I have "Broadcom Nextreme 57xx Gigabit Controller" appearing under "Network Adapters". Is this a problem to be dealt with differently when your phone is bricked?
Click to expand...
Click to collapse
1) your phone is not bricked. dont call it that
2) best way to check if your drivers are installed correctly
open a command prompt in the folder where your fastboot.exe is and type: fastboot devices
if you get a device ID, your drivers are setup properly for fastboot
3) at this point, just return to stock: http://forum.xda-developers.com/showthread.php?t=1626895

Zepius said:
1) your phone is not bricked. dont call it that
2) best way to check if your drivers are installed correctly
open a command prompt in the folder where your fastboot.exe is and type: fastboot devices
if you get a device ID, your drivers are setup properly for fastboot
3) at this point, just return to stock: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
I got a device ID (long string of characters) on that fastboot command, but I'm still concerned that my phone won't talk to Device Manager at all. Windows 7 doesn't pop up a connection window when it's plugged in, should that be expected?
What I mean by "not talking to Device Manager" is that the only item under Portable devices is just E:\ - no device listed here! The tutorial in your signature hinges on there being a device listed "without thde yellow exclamation point", for the installation of new drivers, therefore I don't know how to follow it from here. The adk drivers which were used to root my phone (they were good, the problem began when I tried to flash a rom and missed a step or three) are stil there, but I'll replace them if I can find a process which can talk to my phone in it's present state.
On a side note (and only because it held me up in responding tonight from my Windows system), is this site partial to Firefox? I am able for the first time to login, and I wonder if it isn't because I quit trying to through my Windows 7 system. It has only Windows IE, and Chrome (which couldn't even browse this site). I am currently on my Ubuntu system with Firefox.

good lord... you have a device ID so just use the fastboot commands... start at part D

Zepius said:
good lord... you have a device ID so just use the fastboot commands... start at part D
Click to expand...
Click to collapse
I said much the same myself.
For the fastboot devices test, I have a string of characters, but no device name, only "fastboot" on the single output line with those characters. Is this a valid device ID?
"...just use fastboot" Ok, but how? Should (can I) even do this use fastboot to transfer files to my phone under it's somewhat anonymous status with Windows? Since last night's fiasco nothing was named under "Portable Devices", only "E:\" was displayed. I have no graphical display in the file manager, so how am I supposed to transfer the necessary files to the root of my phone? I don't even see a way of addressing it to install drivers now.
I will need drivers because I attempted to follow this tutorial (which doesn't account for what I am (not) seeing on my system. I got as far as uninstalling the good drivers which I used last night in favor of what was offered for use with the tutorial, and now Device Manager doesn't even have a Portable Devices category. The "Universal Naked Driver" was to replace my uninstalled drivers, and interestingly the contents of it's expanded folders don't even contain fastboot (the adb package which I used last night did). In light of this, how am I supposed to have even fastboot?
I hate to be a PIA about this, but I guess I'm more a n00b than was presumed in this tutorial - it's either that or my situation really is too different that I can use it as is. Could I please get a few clues in light of what the tutorial doesn't address? Do I have any means of installing anything and transferring files with my device-PC communications as they are, and if so how can I do it? I'll give it a run if I understand how.
Thanks.

Zepius said:
good lord... you have a device ID so just use the fastboot commands... start at part D
Click to expand...
Click to collapse
I see now that Part D calls for flashing JO03C from my PC, not the device root, ok.
Also, after rebooting my laptop, the E:\ is back under Portable Devices in Device Manager. When I double-click this I get the statement
Device: Portable Devices
Manufacturer: Generic-
Location: on UMBus Enumerator
I don't think this looks better than the Microsoft default, but is it good enough for what I need to do?
I still have the driver package android-sdk-windows, which contains adb and fastboot, so perhaps I should just use this according to Part D and see what happens?

bananagranola said:
Did you get this solved? Just reboot into recovery (hold down power, volume-up, and volume-down simultaneously to get into bootloader, choose recovery using volume buttons, select using power button), full wipe (system, data, cache), and reflash your ROM.
Click to expand...
Click to collapse
Seriously I respect the fact that your a noob we was all here once but if it your device is boot-looping all you need to do is the above

garner said:
Seriously I respect the fact that your a noob we was all here once but if it your device is boot-looping all you need to do is the above
Click to expand...
Click to collapse
Good god, I never should have read Zepius's tutorial - I didn't need my PC at all! If I understood what bananagranola had said, I could have saved a lot of time!

Oh, no, now I can't connect with the server!
Could I have possibly lost my radio from what I did earlier? I was able to boot up, and I was upgraded to 4.2.1 when I did the data wipe. Starting over, I should have had a prompt to connect with gmail and download my contacts, but this didn't happen. My People app is unpopulated, so I chose to connect to "sign into an account". While I am sure of my login input, it didn't recognize this, and then the process ended with a "couldn't finish - couldn't open connection with the server" error. Any clue where to go from here?
Some standard apps are missing too, including the Play Store app!

Options for Recovering Files & Phone Repair???

Today hasn't been one of the better ones this week. Putting aside my pride for a moment, here's what happened. In my frustration, I threw my phone into a cardboard box. Aiming for the side of the box...it ricocheted of the floor then the side. Yeah, not the best available option to vent!
So...screen spiderwebed and the screen will no longer turn on. Phone vibrates when the power button is used, yet screen is blank.
I'd like to ask for help for the following:
Retrieve several important files that weren't back yesterday: Pictures & program files not synced for privacy reasons, plus TWRP backup from a couple of days ago to internal memory b/c SD full.
Screen damage or more involved? To determine if I spend time fixing or buying a replacement phone.
Phone is the Canadian Koodo T989D running CM11 8/04 with TWRP 2.7.1
Phone Symptoms:
After removing and replacing battery
Pushing power button - Normal 'turning on' short vibrate, screen doesn't turn on (no light/pixels light up)
Recovery Mode - Normal Vibrate, release pwr button and again screen blank with exception of top Left corner showing multiple pixels, unrecognizable
Download Mode - Plugging in the USB cord causes the phone to vibrate every 2 or three seconds and the cycle repeats. vibrate...vibrate...vibrate...continuous
Any thoughts on troubleshooting to determine if retrieving files on the phone is still an option?
Would appreciate ya'll sharing your common knowledge that uncommon while I'm this frustrated. After switching to an AWS service provider (WIND) 2 weeks ago my backup phone isn't compatible - Galaxy Ace GT-S5830D. Thought it was until I tried, then realized it isn't. I'm kind of flustered that I acted so impulsively and doubly because I thought I had a backup phone, ughh!

I believe you deserve to feel bad for having acted upon anger for trivial matters! I'm glad you feel bad too because after all, that is the way we discover ourselves and learn from our mistakes! :good:
As for the phone, I had a gut feeling based on your post that there may be a power/voltage problem (maybe a short?) because the behavior in Download mode seems like the behavior when you try to boot the phone without a battery (using only usb power) and there's not enough juice to do anything useful.
My guess is either your battery is damaged, or a short somewhere in the phone (perhaps the screen?) might be draining too much power.
If you get it to boot and have usb debugging on, you can access your data using ADB. I believe CWM and TWRP both have ADB built-in also so you might have some luck there.
Can your computer recognize the device?

MASTERBLASTER69 said:
I believe you deserve to feel bad for having acted upon anger for trivial matters! I'm glad you feel bad too because after all, that is the way we discover ourselves and learn from our mistakes! :good:
As for the phone, I had a gut feeling based on your post that there may be a power/voltage problem (maybe a short?) because the behavior in Download mode seems like the behavior when you try to boot the phone without a battery (using only usb power) and there's not enough juice to do anything useful.
My guess is either your battery is damaged, or a short somewhere in the phone (perhaps the screen?) might be draining too much power.
If you get it to boot and have usb debugging on, you can access your data using ADB. I believe CWM and TWRP both have ADB built-in also so you might have some luck there.
Can your computer recognize the device?
Click to expand...
Click to collapse
Thanks for the educated guess and ADB suggestion to recover files.
Yes the computer shows 3 drives when attached in Recovery Mode. And darn it I can't remember if debugging on or off. The computer doesn't recognize the phone by default while in recovery mode. If this is the case, would ADB likely allow access to the phone? Not a tool familar with yet.
Unlikely that the battery is damaged if the phone turns on. Still stays cool while on or charging. Which is good news.
Do you suggest installing ADB and checking? If so, which version of ADB? Seems there are more than a few, plus multiple drivers and would rather not get hung up on troubleshooting installation.

the computer shows 3 drives when attached in Recovery Mode.
Click to expand...
Click to collapse
I don't understand why you see 3 drives... I'm sure Windows will ask you to insert removable storage if you try to access the drives, right? If that is the case, and you have no screen/touchscreen, only ADB will allow you full access to everything in the phone.
Do you suggest installing ADB and checking? If so, which version of ADB? Seems there are more than a few, plus multiple drivers and would rather not get hung up on troubleshooting installation.
Click to expand...
Click to collapse
Yes. Here's the tricky part though, in order to make adb work, your computer needs the right drivers for your phone.
I think you should try to follow the HOWTOS (How to Install Android ADB Interface Drivers) on installing the drivers for ADB.
If all goes well, you can check if it worked by typing 'adb devices' from the windows commandline. Then it would be possible to use adb to get your files back.

If the phone boots into the system...if, since you can't see it....you should be able to open the sd folder on your pc and simply copy/move what you want to the pc.
Just checking if you've tried this.

S4 mini with broken screen, no more data after 'blind' reboots to recovery

Dear All!
(I already searched Google and xda - However, since my problem is rather specific, I may be using the wrong keywords to come up with a solution that is also applicable here; so also links are highly appreciated!)
I will give you the whole story in order not to skip anything important:
While hiking with my family I somehow managed to break my screen (LCD and Touch, as far as I could tell). However, the phone was still powered on, which i could tell from using the volume keys and hearing the normal sounds. Also the phone was ringing when called.
Unfortunately, USB Debugging wasn't activated, so I booted to recovery (some CWM, can't be more specific, sorry) via several tries. It was a bit tricky at first, but i managed to come up with a routine that would work (Holding VolUp+Home, then Power additionally; releasing the power button after the first vibration and then holding the other two for another 3-5 sec did the trick).
I then could gain usb debugging the way described in this thread: [Tool][Windows] Control a device with a broken screen. Now with touchscreen support!!
Using a Linux machine I then used adb commands (ls; cd; pull) to copy my mmssms.db; however I had to leave my workplace for a short while. Afterwards my device wasn't shown in adb devices, because it powered off for some reason.
Here comes the crucial part: At this point I mistakenly booted into Download Mode (and wasn't aware that I did it, cofused VolUp and VolDown - I couldn't see that, so I'm not 100% sure). I pulled out the battery at this point and rebooted into recovery.
Booting into recovery still works and "adb shell" -> "ls" shows the folders, however apart from the top level folders there are no more files/folders left (e.g. "ls mnt" gives "fuse secure shell"; "ls data" gives "media"; "ls data/media" doesn't return anything)
At this point I mainly want to get the contents of my internal sd (now no files are shown).
tl;dr: Broke screen; accidentially booted into Download Mode; Pulled out battery; Can't access my files/files gone in adb shell
Is there a way to recover the file structure? I still can get into recovery and use adb but the phone won't boot to CyanogenMod (I suppose it gives me a soft brick screen, but i can't confirm that as my screen is broken).
I really hope someone could point me in the right direction!
Lukas