Related
[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....
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
So the display is damaged but the digitizer is fine correct? As for data just pull files with adb....I believe you can do that unless you never had USB debugging on
Sent from my SGH-T989 using Tapatalk
CptCrackers said:
My T989 is rooted. I use it to log my work hours in "It's About Time". I back that app's data up every day to the box folder, and I sync with box. HOWEVER, the box syncing has aparently been pretending to work and doing nothing since february, so I'm screwed right now as the touchscreen on the phone was shattered today. It has no visuals or touch ability. the gorilla glass survived just fine, but the screen behind it is gone.
What I need to know is how can I access the data in the builtin memory. I would love to use Kies, but Kies, points out that my phone is locked (I use a pattern lock) and says I have to unlock it.
Is there someway to remotely unlock a broken phone? The phone can go be a doorstop at this point, but I HAVE to have those backup files sitting in the box folder. They aren't on the microsd card.
Click to expand...
Click to collapse
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
I have been in usb debugging. It may be in usb debugging mode right now.
When I connect it, it shows the drive, but they show as empty. Which is the same thing that happens on my GS4G when it's in debugging.
If you could tell me how to go about extracting files, that would be great, assuming there is even a way.
Is the digitizer the touch portion of the touch screen? If so, then no, that's not working. The phone boots, it receives texts, makes other sounds like it's working, but the screen is black. The LCD is cracked, and it will not accept touch input. I have haptic feedback on and it's definitely not letting me attempt to do the unlock screen.
slm4996 said:
You can always boot into recovery and pull from your data partition using ADB. Then you can restore that to another phone after you install your time tracking app.
Click to expand...
Click to collapse
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
CptCrackers said:
Could you tell me how I do this? The only time I ever booted into recovery was during the rooting process. Do I need to be able to see the screen to do it, or is there a way to get into it remotely? If so, can you either tell me what to do or point me at a tutorial or something? I wouldn't know where to start.
Click to expand...
Click to collapse
To get into recovery, pull your battery then put it back in, then hold both vol up and vol down and hit the power button.
Type "help" without quotes in ADB to get a list of commands.
Sent from my SGH-T989 using xda premium
try this http://forum.xda-developers.com/showthread.php?t=628138
It got me out of a jam once on my vibrant, when the same thing happened to me and needed some pictures for my work. USB debuggin has to be on though.
To backup the data from a damaged phone using ADB:
1) Enter Recovery mode:
Turn the phone off, remove the battery. Insert battery, hold volume up AND down while turning on. Plug in usb cable.
2)Open up your terminal/console. Enter the following commands (one command per line, press enter after each)
(this backs up the entire data partition)
Code:
mkdir phoneDataBackup
adb shell mount data
adb pull /data phoneDataBackup
You now have a copy of your phones /data folder, this contains the settings and data from your apps. Get a new phone and then install you app on it. Once you do that simply put the correct named folder from the phoneDataBackup back into your new phones /data folder.
Code:
adb push phoneDataBackup/data/com.rds.itsabouttime /data/data/
This should work just fine for you, I assume you already have ADB installed or can install it first.
THANKS ALL!!!
I am currently using the suggested Android commander to dump everything out of the phone. Lucky the usb debugging got left on when I was cleaning out bloatware last week!!!
Once it's done, or if even if it doesn't work, I'll be playing with the adb connection since it's not like I can break the phone worse... good learning opp!
Thanks for all the tips from everyone.
Quick update, and info in case someone later finds this thread in a search. The android commander did get back what I needed most. However, it also did some strange things. It can see a lot of stuff on the phone, but when pulling things from the phone, for some reason, some files and directories do not come over. I imagine this may have to do with permissions on those items.
I'm basically making thsi note here in case someone finds the thread, thinks they have dumped heir whole phone... just make sure you pick through the important directories before you think you've got everything and discard the phone.
Thanks again everyone. Ass officially saved.
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
soundwave4 said:
Hello everyone.
I also just cracked my screen and have neither touch capability nor screen lighting, so I'm effectively blind in controlling my phone.
I know I have Clockworkmod recovery 5.0.2.7 installed and rooted, but these solutions are not working for me.
I have tried removing the batt, reinserting the batt, holding UP+DOWN+POWER until the device vibrates, then let go of the POWER while holding UP+DOWN for another 10 seconds to be sure.
I then plug in the USB cable and my Windows 7 laptop does the "found USB device chime", so I know the device is on (and has not booted into Android, since the Samsung Galaxy logo jungle has not played.)
I also see that Windows 7 sees new "Removable Drives" that it adds after I plug in the device, but the drives cannot be accessed/are not available to Windows 7.
I'm definitely sure I'm in recovery because when I hit POWER, the Windows 7 "unplugged USB device" chime plays, the device vibrates and I'll hear the Galaxy S logo chime, which means I hit the 1st "reboot device" option on the recovery menu.
But when I open a console and type "adb devices" none are listed.
I have also tried Android Commander, and no devices are there either, so these 2 methods do not work. I'm wondering why adb cannot see recovery on mine if people are saying that it can.
I know that Clockworkmod recovery has a option for mounting the sdcard and data via USB. I also see that different versions of Clockworkmod have different menus.
Can someone help me by letting me know what/how many button presses I need to do to get to the "mount sdcard" and "mount data" options once I'm in recovery as I'm flying blind.
Thank you for any help.
Click to expand...
Click to collapse
If you have adb setup just do adb pulls. You can get anything that way. Slow, but a plan b if nothing else. I would count for you but I run twrp and I don't have time or battery to flash it over to cwm right now.
Edit: for whatever reason tapatalk didn't load anything past the OP...disregard.
Tapatalked from my Galaxy S II.
Coming from a phone with microSD extension, I had never encountered such an issue:
I bought this phone with a stock 4.2 Rom installed and tried to install a custom Rom. I first installed the latest version of touch recovery (tried it and it seemed to work fine) and did a backup using the default settings. Then I erroneously chose to format system and data, thinking that I could then "install from zip". Strangely, these steps deleted everything in the /sdcard directory and I couldnt select "external SD" (because the phone isnt equipped with it anyways?). Then I made a second mistake and restarted the phone, despite the message warning that I no longer had an OS installed. I took the battery out, and then held the power down while pressing the power button. The phone couldn't get into recovery, but instead showed a screen with the android logo, a large "Start" sign above it, and "Downloading...", "Do not turn off target !!" below it. Pressing the power button now got the phone to show just "Google" and a lock logo under it. The PC (windows 7) can not detect the phone throughout the process.
I tried the latest tool kit and samsung's USB driver but couldnt get the phone recognized by the PC.
Does this mean that the phone is doomed???
Please help!!!
Trent
Relax, it's not easy to 'doom' your Nexus. Especially with all the hard-workers in XDA
Try accessing Recovery mode by holding down BOTH vol up + vol down, as well as power. Holding just vol down + power is 'Download Mode', and at the least you can get to this. Means your phones far from doomed
Thanks a lot for the reply!
As a matter of fact, I also figured out how to get back to recovery (if only I had read your post earlier, my pain would've been much less!). But the problem remains that I can not get a target ROM onto the phone, since: 1. whatever I did seemed to have gotten rid of the nand backup supposedly stored in /data/media/TWRP/BACKUPS/ (I'm using TWRP V. 2.3.2.1). 2. I can not get my PC(or Mac, for that matter) to recognize the phone or the internal storage.
Any pointer from here?
Thanks again!!!
Trent
You can download a factory image and install with fastboot. It's quite easy and instructions are readily available on this forum. You can then install a custom ROM afterwards if stock is not your thing.
Found the answer finally!
It's the adb push method. Basically, it's to install adb drivers and execute a few commands via the command window. Not too bad... Don't know much about fastboot yet though ... If anyone else needs more details, please PM me (to save public bandwidth).
Thanks a lot anyways, whpnhp and jocalderone!!!
Trent
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.
I just bought a 2013 Nexus 7 today for very cheap, to use in my car as a headunit and learn a bit about flashing different roms, using the timur kernal, etc. It looks like it was used at some sort of healthcare facility though, because it has some "Optum Health" software on it, deeper than just an app it remained after a factory reset. On restart the optum health logo comes up, immediately after the google logo and says loading, well before it actually loads to the home page of the tablet. So it's pretty deep. I was thinking a fresh factory ROM would help me out.
I was following this guide to get twrp on the phone, as wifi wasn't working (most likely because I had tried to remove the optum stuff by disabling apps, and I got a little trigger happy) load via adb:
https://www.xda-developers.com/how-to-install-twrp/
Everything was cool until I went to restart it. I typed "fastboot reboot" into the command prompt, she restarted, and gets infinitely stuck at the "Optum Health" logo, and the word "Loading" pulses underneath.
I can't get it back to the bootloader by holding the volume buttons and "hold", the cmd/powershell doesn't see the device connected. However, the computer makes the chime sound of a device connecting when I try to open the bootload menu using the buttons, the power shell waits longer to say it failed, but it still doesn't work.
Do I have any options? Or did I completely brick my old, cheap, facebook marketplace, probably stolen from a hospital tablet?
solson1041 said:
I can't get it back to the bootloader by holding the volume buttons and "hold", the cmd/powershell doesn't see the device connected. However, the computer makes the chime sound of a device connecting when I try to open the bootload menu using the buttons, the power shell waits longer to say it failed, but it still doesn't work.
Do I have any options? Or did I completely brick my old, cheap, facebook marketplace, probably stolen from a hospital tablet?
Click to expand...
Click to collapse
Follow these instructions to resolve the problem and flash up-to-date Android - https://wiki.lineageos.org/devices/flo/install
"With the device powered off, hold Volume Down + Power until the bootloader appears, then release the buttons." it really works.
Then connect it to a PC and install proper USB driver - https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Once you get ADB & Fastboot installed on your PC or linux , do a command prompt with the device connected.
adb devices
It should list your device in your terminal output. If and when it does..If your a little hinky on the buttons just do a command prompt: adb reboot recovery, adb will reboot your device for you into recovery mode. Then follow the LOS instructions provided for you & you will be amazed at how great your tablet works. Just a little FYI, if you've never done this before, find the "pico" gapps, don't try to install any of the bigger ones, there is not enough room on the sys partition for the full gapps install. After & if you get pico installed you can always add to it with all the room you have left now on the rest of the device. Also when you are installing LOS, make sure you find and install the gapps at the same time you install the OS, before you reboot your device. It will save you a lot of headaches. Just follow the directions and you will be very happy.