Related
I've seen a lot of these threads on random android forums, never with much resolution, which is frustrating.
My power button has stopped working entirely. I took it into the Sprint shop, they spent an hour with it, came back out and said they could find no reason it shouldn't be working. It's an obnoxious fix, but I downloaded "No Lock" from the marketplace and set the screen to shut off after 15 seconds. Now I press a volume key to turn on my screen...
Now, when it gets annoying is when I went to install Cyanogenmod 7 tonight. The power button obviously doesn't work. Widgetsoid's reboot button is ignored entirely if I do Shut Down, Reboot, Bootloader, or Recovery. It's A-OK with Hot Reboot. So the only way I've gotten into the bootloader to wipe/install CM7 is to pop out the battery, hold VolDown, and put the battery in. Peachy. But once I'm into the bootloader, now not only does power (which is now my "enter" button) now work, but the volume buttons are unresponsive as well. So no scrolling.
I'd love to call up HTC or Spring and see what I can do about a replacement (which might not even happen, I don't have a warranty), but I can't un-root the device to send it in.
Any insight you guys have would be greatly appreciated...
Is there an SDK or something that would allow me to remote control the phone using my computer via USB? I'm completely at a loss here.
END_OF_FLESH said:
Is there an SDK or something that would allow me to remote control the phone using my computer via USB? I'm completely at a loss here.
Click to expand...
Click to collapse
I believe you are referring to adb?
and you can unroot via adb, just search around, I'm sure you'll find something on it.
btw, does Sprint know you rooted your phone? if they didn't find out, then you still have a warranty
Samzebian said:
I believe you are referring to adb?
and you can unroot via adb, just search around, I'm sure you'll find something on it.
btw, does Sprint know you rooted your phone? if they didn't find out, then you still have a warranty
Click to expand...
Click to collapse
Yeah, I'm just not as familiar with ADB as I'd like to be.
Not so much looking to unroot, as reload HTC Sense so they don't think to look haha. And yeah, when I brought the phone in today it was very obviously modded. They restarted it and the Cyanogenmod 6 flash screen came up. The guy looked a little confused. He was more than willing to help out, but I'm not so sure it would be the same if I sent it in. They definitely wouldn't replace it.
Alright, so I have ADB up and running with no issue. Got it to give me my device's serial #. At this point, how do I hijack the phone's bootloader and force it to wipe and install the ZIP of CM7 that's on the SD card?
So, been rooting, fiddling, installing ROMs, etc for a couple years. By no means am I an expert, I can just do research and read. I've had bootloops, and crashes, and all the same issues everyone else on this forum has had over the course of learning this stuff. So, when my phone wouldn't boot up even into recovery, I didn't sweat it at first. But, well, I've tried everything and nothing works. I can't boot, I can't charge it. Nothing works.
So, here's the breakdown.
Lt28i
Was running stock
Phone was rooted
CWM recovery
Bootloader is unlockable via regular means.
Hated it since a recent update. Phone was slow and i wanted JB. So i started the process.
I installed a new kernel, was in the process of installing a new ROM, but the instructions said to delete /system. I did.
From that point on, phone would not boot. Would not charge and would not get into recovery.
I can't connect via adb/fastboot.
It's a brick sitting on my desk. I've since gotten an HTC one, which IS AWESOME guys, but I hate having a perfectly fine piece of hardware just sitting on my desk collecting dust, (not to mention hate admitting defeat) so I'd like to get it working and either give it to a friend or sell it. Can anyone help.
Symptoms. As soon as i plug it in, the red light goes on. After about 15 minutes, the sony logo comes on with the red light off for just under 10 mins or so, then black screen and red light on. So, it's in a kernel boot-loop of sorts, but never gets past it and therefore doesn't charge. I've left it unattanded for over a week to drain the battery, hoping it'll reset, but no change. Immediately the red light goes on when plugged in. No way to boot into recovery. No way to connect to fastboot.
Any ideas?
Have tried the following:
http://forum.xda-developers.com/showthread.php?t=1849170
and a bunch of others. None has worked.
So your bootloader is locked?
You can't flash any custom kernel on locked bl.
First, connect your phone to a wall charger for whole night.
Then use Update Service or PCC to repair it.
Remember: do not connect your phone to PC until it ask you to do so.
Press vol down when connecting to PC.
cities516 said:
So your bootloader is locked?
You can't flash any custom kernel on locked bl.
First, connect your phone to a wall charger for whole night.
Then use Update Service or PCC to repair it.
Remember: do not connect your phone to PC until it ask you to do so.
Press vol down when connecting to PC.
Click to expand...
Click to collapse
sorry, my mistake. The plan was to flash a kernel, but i never got around to it. I had looked into unlocking the bootloader, but wanted to see if I could get any good JB roms first. Sorry about that false info.
I have both let the phone die completely, or so I think, unless it keeps its charge for over a week and charged it for about 40 hours. Like I said, it does the bootloader boot loop which seems to keep it from charging. I never get to the screen where it shows the charging icon, so I can't tell, but I've definitely left it on a charger (not PC) for at least a day and a half. No go.No amount of pressing vol down works.
Does flashtool work on bricked phones?
lewis021 said:
Does flashtool work on bricked phones?
Click to expand...
Click to collapse
Yes, Unless your device is hard bricked meaning it wont show any led or wont do anything basically
AndroidHoneyComb said:
Yes, Unless your device is hard bricked meaning it wont show any led or wont do anything basically
Click to expand...
Click to collapse
Well, that's why I'm hopeful, cause the led does light up immediately on plugin. And the Sony logo screen shows up for a few minutes, then disappears. I have tried flashtool, but it won't connect. No go.
vijn said:
Well, that's why I'm hopeful, cause the led does light up immediately on plugin. And the Sony logo screen shows up for a few minutes, then disappears. I have tried flashtool, but it won't connect. No go.
Click to expand...
Click to collapse
Your either using flash tool wrong (Hold the down button while plugging in the usb to go in flashmode and then flash the ftf quick before flashmode restarts of being idle) The Sony logo is still there so there should be no reason to send it in until all possible repair techniques have been used
AndroidHoneyComb said:
Your either using flash tool wrong (Hold the down button while plugging in the usb to go in flashmode and then flash the ftf quick before flashmode restarts of being idle) The Sony logo is still there so there should be no reason to send it in until all possible repair techniques have been used
Click to expand...
Click to collapse
Well, I've used flashtool a whole bunch of times. Sure from time to time there's an issue with it, but I've tried different versions and none has been successful. And I'm very familiar with the "getting into flashmode" process. And yes, I would agree with you that if the sony logo shows up, then there's gotta be a way, but I'm telling you, it's just not happening. I've tried 100 times.
vijn said:
Well, I've used flashtool a whole bunch of times. Sure from time to time there's an issue with it, but I've tried different versions and none has been successful. And I'm very familiar with the "getting into flashmode" process. And yes, I would agree with you that if the sony logo shows up, then there's gotta be a way, but I'm telling you, it's just not happening. I've tried 100 times.
Click to expand...
Click to collapse
Does Flashtool show anything after you connect your phone to PC with flashmode?
"Drivers have to be installed" or somethimg?
vijn said:
Well, I've used flashtool a whole bunch of times. Sure from time to time there's an issue with it, but I've tried different versions and none has been successful. And I'm very familiar with the "getting into flashmode" process. And yes, I would agree with you that if the sony logo shows up, then there's gotta be a way, but I'm telling you, it's just not happening. I've tried 100 times.
Click to expand...
Click to collapse
If you can see the Sony Logo then it has to work, Hold the down key, while plugging it in and it will show a green led... I had the same problem as you (cause I do things that sony may not like, on my phone)
1. Make sure you have the correct drivers installed.
2. Turn your phone off and unplug USB cord.
3. Hold the VOLUME DOWN button while inserting the USB cord.
4. You should see your small notification light in the top right of the phone turn green.
AndroidHoneyComb said:
If you can see the Sony Logo then it has to work, Hold the down key, while plugging it in and it will show a green led... I had the same problem as you (cause I do things that sony may not like, on my phone)
1. Make sure you have the correct drivers installed.
2. Turn your phone off and unplug USB cord.
3. Hold the VOLUME DOWN button while inserting the USB cord.
4. You should see your small notification light in the top right of the phone turn green.
Click to expand...
Click to collapse
Ya, first of all. I can neither turn the phone on or off. I have no control of it. It "turns on" when it wants and off when it wants. But when i say turns on, it only turn onto the sony logo screen after about 20 mins of being plugged in, when I guess the charge is just enough to allow it to start the boot process. Then the sony logo screen turns on, until that tiny charge dies and the phone turns off and the red LED comes on. Process repeats over and over again. I even put a rubber band on the phone to keep the volume down button pressed so that when the charge does reach the right level for the boot process that the vol down button will trigger recovery, but no deal. If this is the only way to get this thing working, is what you've recommended above, then phone is completely bricked, cause the phone has been like this for 2 weeks and nothing has worked. I know i have the drivers, cause up until this issue, flashtool worked fine. But the PC doesn't even recognize that there's a device plugged in at all now, cause the phone never boots. So, it's like plugging in a usb HDD that is off. I didn't really expect anyone to have a solution, cause i've done extensive research and tried almost everything I've read that seemed relevant, but I still had hope. I suspect the only way to fix it is to open it and connect directly to the mobo in some other way, but i don't have the tools or resources for that. Not even sure I can send it in to be repaired cause it's rooted. Unless someone has a eureka solution, my only option is to send it in to a 3rd party repair guy. Any other thoughts?
The most important thing is: what have you done to your phone before?
Flash something or edit something?
To turn off your phone, long press power + vol up until 3 vibrations.
Then connect your phone to a wallcharger for whole night.
(Do not use PC cable... It won't charge much...)
Then flash stock ftf via Flashtool.
Sent from my LT26i using xda app-developers app
Just read my first 2 posts in the recovery thread sticky'd in the general section.
Then reinstall ALL drivers available in flashtool.
Then use the rubber band trick from my thread. Make sure that the rubber band pushes the button in.
Sit back and wait ,believe me this is the hardest step.
From my Xperia LT28at ION
ToledoJab said:
Then use the rubber band trick from my thread. Make sure that the rubber band pushes the button in.
Sit back and wait ,believe me this is the hardest step.
Click to expand...
Click to collapse
I laughed at the method simplicity, and got amazed on how effective is it.
So when you connect the phone to your PC while holding the volume down key...no green light, and its not recognized by your PC at all, right? Assuming you're using windows; does windows try to install any drivers or anything? Are you prompted in any way that a device has been connected?
and did you try the above mentioned? Hold UP and power button for like 10 seconds...you'll feel it vibrate once...then a few seconds later it should vibrate 3 times...I bricked my phone to some degree Sunday...only I had no response whatsoever...no led while charging, or otherwise...and literally no response from anything...until i tried that vibrate 3 times thing...and it booted right up after...
NO GO!
Well, I've tried it all. @ToledoJab I've read and reread that original post a bunch of times. followed all instructions, in fact, I had read that post many times before even posting in this forum with no luck, but I thought I'd be patient and try again, Used the rubber band technique. Nothing. Seems, when the rubber band is used, the phone doesn't even start the boot process, meaning never shows the sony logo screen.
@jtr what no one seems to understand is, there is absolutely no response to using the power button to turn this on or off. No vibrate, nothing. There are only 2 states. 1. When plugged into wall or PC, LED is red and after 20 mins Sony logo shows up if the vol down button isn't pressed. 2. When not plugged in no led.
Flashtool has been open for 2 days, phone has been plugged in, with rubber band. Drivers installed. Phone is never recognized because it never turns on. it's in perpetual red light on mode.
I don't know guys. I'd say this is an official brick. Not sure there's any way to fix this without opening it up. Still open to any ideas, but please read what I've posted because all the recommendations so far have been things I've already said I've tried, and numerous times. I can't imagine there's anything else to try, but thought I'd update you guys nonetheless.
cool, i understand.
If the volume down key is preventing it from going into that boot loop, though...it seems to be responding to physical input to some degree...
Have you tried any of this without a sim card? I know that sounds trivial, but after a full week of messing with mine a fresh sim-less start knocked out several bugs...and i hadn't read much of that on xda, but the AT&T return directions suggested a without sim boot up as the first thing to do? and at the time, i too, was dealing with some sort of varying degree of brick.
There are also varying ways to drain a permanent phone battery...i wouldn't say thats the best way to go about this, but a friend of mine has a screwed up car charger that does exactly this...which he's kept to bring his samsung nexus out of hard bricks multiple times...i'd say that's definitely a last resort though...the stuff you'd need would only be a couple bucks at radio shack i'd imagine haha.
If you get the Sony screen you should get in to flash mode, and I say should.
With the phone plugged in to PC with flashtool ready to flash, try to do a one vibration reset at Sony screen then immediately press and hold volume down.
Sent from my LT28i using xda app-developers app
[My device is a Sprint Galaxy S III, unrooted on STOCK 4.1 (with multi-view)]
So the previous night I plugged my phone into the charger as normal and went to bed. Strangely, when I woke up, my phone was turned off. Curious, I went to turn it back on and waited for it to boot back up, only to have it freeze up in the middle of opening an app. I wasn't worried at this point, but after a battery reseating and restart, it happened again. This time, it froze up on the 'Galaxy S III' boot logo. I tried multiple times to restart, swapping batteries, waiting, and managed somehow to get it to recovery mode. There, I managed to wipe cache and attempt to restart the phone once more. Nothing--it was still frozen on the boot logo. After waiting a while, I tried to get it back into recovery mode, popping out the battery whenever it froze. To my horror, this time, pressing and holding the power button did not get a response from the device.
Mind you in my (roughly) year's worth of time with this phone, I had never dropped it or subjected it to any form of shock or damage. Seriously--the phone looks out-of-the-box-brand-new.
Now the device is bricked(?) I'm thinking it's some sort of hardware defect, but I'm confused because it happened out of nowhere--simply overnight. Nothing I do seems to elicit a response from it and I even tried swapping in a freshly charged battery.
I really don't care about most of the data on the internal storage (cloud sync ftw!) but there are a ton of photos inside that I would give anything to save. Is there any way I could save them? I'd appreciate any input!
TL;DR: Out of nowhere, my 1yr old GSIII suddenly started acting strange and after some troubleshooting bricked itself. Need photos on internal storage.
Can you get Into download mode? If so you can just Odin it back to stock, but it will wipe everything on internal storage.
BEFORE YOU DO THAT, I know @CNexus knows some commands in adb that can probably save your photos on the internal storage. Let me see if I can find them real quick or he might see this thread first..
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Whiplashh said:
Can you get Into download mode? If so you can just Odin it back to stock, but it will wipe everything on internal storage.
BEFORE YOU DO THAT, I know @CNexus knows some commands in adb that can probably save your photos on the internal storage. Let me see if I can find them real quick or he might see this thread first..
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
You haxor, why you mention my name, I had no choice but to show up...
@cytark
The following commands will pull all the pictures from your internal storage (connect phone to computer and make sure you are in the same directory as the adb.exe folder)
Code:
adb pull /sdcard/DCIM camera <press Enter and then wait..>
adb pull /sdcard/Pictures pictures <press Enter and then wait...>
Also, was your phone rooted? Because if the above doesn't work, then we can still get your stuff for you if you can get into recovery
Note: The phone is only truly bricked if it shows "QHSUSB_DLOAD" when you connect it to the computer.
CNexus said:
The following commands will pull all the pictures from your internal storage (connect phone to computer and make sure you are in the same directory as the adb.exe folder)
Code:
adb pull /sdcard/DCIM camera <press Enter and then wait..>
adb pull /sdcard/Pictures pictures <press Enter and then wait...>
Also, was your phone rooted? Because if the above doesn't work, then we can still get your stuff for you if you can get into recovery
Note: The phone is only truly bricked if it shows "QHSUSB_DLOAD" when you connect it to the computer.
Click to expand...
Click to collapse
My phone actually won't even go into download mode. It stays off no matter what I press. Will the adb commands still work?
Additionally, my phone is not rooted.
EDIT: Actually, upon plugging my phone into my PC, it says exactly that. QQ
Well yes it is a general term, but people tend to use it loosely with meaning that the phone won't go into the OS for whatever reason. When you overwrite the bootloader, that's when you have a brick. Either that or the kernel is so messed up that it fries your EMMC. On these phones when the bootloader is overwritten it will show as QHSUSB_DLOAD when connected to a computer.
Can you try connecting it to your computer and seeing what pops up? If it shows up at all, it may still be possible to recover it.
CNexus said:
Well yes it is a general term, but people tend to use it loosely with meaning that the phone won't go into the OS for whatever reason. When you overwrite the bootloader, that's when you have a brick. Either that or the kernel is so messed up that it fries your EMMC. On these phones when the bootloader is overwritten it will show as QHSUSB_DLOAD when connected to a computer.
Can you try connecting it to your computer and seeing what pops up? If it shows up at all, it may still be possible to recover it.
Click to expand...
Click to collapse
I see.
"QHSUSB_DLOAD - No driver found" comes up as a driver installation failure message.
cytark said:
I see.
"QHSUSB_DLOAD - No driver found" comes up as a driver installation failure message.
Click to expand...
Click to collapse
No bueno. Here this can get you fixed up. http://forum.xda-developers.com/showthread.php?p=43724690
Sent from the future via Tapatalk 4
CNexus said:
You haxor, why you mention my name, I had no choice but to show up...
I don't know what that means... I hope I didn't bother you. Sorry...
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
Whiplashh said:
CNexus said:
You haxor, why you mention my name, I had no choice but to show up...
Click to expand...
Click to collapse
I don't know what that means... I hope I didn't bother you. Sorry...
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Click to expand...
Click to collapse
Dude c'mon, I'm just teasing
CNexus said:
Dude c'mon, I'm just teasing
Click to expand...
Click to collapse
Oh alright. Lol. I figured you knew more about this.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Similar issues
I had a similar issue with my phone today. I'm mostly posting to show that this isn't an isolated incident, since I have insurance and can get my phone replaced, but any suggestions for fixing it would be very welcome.
My phone is a year old Sprint SGS3 running CM10.0 or so, stock battery with plenty of juice, haven't flashed anything or even booted into recovery in quite a while, no new apps for a week or so, no recent battery pulls, no usage out of the ordinary.
The phone died in my pocket, and upon trying to boot it would display the SAMSUNG screen for ~0.5 seconds, then display the "Samsung Galaxy S III" screen for ~0.2 seconds before dying. It did not bootloop, but remained off. Similar behavior was exhibited when trying to boot into recovery and download mode:
When booting into recovery, the SAMSUNG screen with the recovery overlay would display for ~0.5 seconds, then the "Samsung Galaxy S III" screen would come up for ~0.2 seconds before it died.
When booting into download mode, the SAMSUNG screen came up for ~0.5 seconds, then the warning about running custom ROMs came up. If I was quick, I could press volume up to start going into download mode, but it would still die almost immediately either way.
When plugged into a USB cable attached to a laptop or power, the battery icon would come up with the loading circle for ~0.5 s, then it would die. If plugged in with the battery removed, the right indicator light would come on and it would vibrate, but the screen would not turn on.
After booting over and over for some time, it will no longer respond in any fashion, except when plugged in with the battery removed as described directly above. I suspect the battery has died, and cannot be charged because the phone crashes before charging begins.
Any thoughts on how to fix it, or ways to revert back to stock when the phone won't stay on for more than 2 seconds?
That is The Sudden death Syndrome. Your power button has failed. It is messed up internally. This is a known issue with the S3. You can try blowing some air in the power button area and jiggling it around to get a temporarily working. But they do replace it for this condition.
Sent from the future via Tapatalk 4
That sounds very plausible. I noticed some irregularities with the power button as well, but didn't think they were worth mentioning. When you say "they", do you mean Samsung? Or someone else?
CogDancer said:
That sounds very plausible. I noticed some irregularities with the power button as well, but didn't think they were worth mentioning. When you say "they", do you mean Samsung? Or someone else?
Click to expand...
Click to collapse
Sorry when I referred to as they i meant Sprint.
Sent from the future via Tapatalk 4
Do you know if they will replace the phone past the standard warranty? I'm out of warranty by only a few days. I figured I had a problem with my battery so I bought a new one to test before I found the power button to have failed. I'm going to be heading back over in a few minutes to return the battery kit, and hopefully they will replace my phone without making me go through insurance.
CNexus said:
You haxor, why you mention my name, I had no choice but to show up...
@cytark
The following commands will pull all the pictures from your internal storage (connect phone to computer and make sure you are in the same directory as the adb.exe folder)
Code:
adb pull /sdcard/DCIM camera <press Enter and then wait..>
adb pull /sdcard/Pictures pictures <press Enter and then wait...>
Also, was your phone rooted? Because if the above doesn't work, then we can still get your stuff for you if you can get into recovery
Note: The phone is only truly bricked if it shows "QHSUSB_DLOAD" when you connect it to the computer.
Click to expand...
Click to collapse
I haven't ever replied to these threads but I need help so I hope im doing this right. I have a galaxy note 2 that did pretty much the same thing as the original thread poster. I can get to the recovery screen but I cannot connect to a computer. I really want my pictures and possibly to fix my phone. I appreciate any help you can provide. thanks
Well the worst possible thing happened, I literally smashed my Nexus 7 (2012 - sorry couldn't find the right spot) into tiny bits.
It's kind of a weird story, no I didn't drop it. I was working on my car's engine, using my handy N7 to look up directions. I was proud of myself for fixing my car, and went to close the car's engine hood. I dropped it down. It didn't go down... my N7 was wedged in between the hood of the car and the body. *note to self: always pay attention*
The screen blasted apart (I cannot see anything on it now, and there's large chunks of glass missing), and the body is pretty mangled. My happiness was smashed just like my N7 screen. However it does still work! I was listening to music via bluetooth, and it didn't skip a beat. I was also able to press the physical keys to take a screenshot.
So, to make it a happy accident, I went out and bought the new 2013 Nexus 7.
But I would like to get all of my data, music, comics, super nintendo roms, etc, off of the smashed N7.
I've run into a couple of problems though. When I plug the N7 into some computers (a Windows 7, and 2 windows xp computers), it doesn't pull my N7 up as an explorable drive.
It fails to install the MTP drivers (it used to work a while ago when I first got the N7...), and nothing comes up. I believe I am in MTP mode. In device manager it shows the MTP device, but with a question mark in a yellow circle.
The ADB drivers do install successfully, but nothing happens. It shows up in device manager properly.
So my problem, how do I get my data off onto my computer?
Here's my other issues:
- I use a lock screen (PIN number)
- I am not rooted
- USB debugging is not enabled
Is there a way to remotely enable USB debugging?
I've tried various programs and such, but nothing has let me access it.
Hopefully I'm not totally screwed, my life has been on this thing since last November
Thanks in advance!
Since your screen is smashed you won't be able to use ADB/Titanium/Helium backup. With a custom recovery and this installed, you are able to use ADB while in recovery without USB Debugging enabled to pull files onto your computer.
Code:
adb pull /sdcard/ c:/sdcard/
I've never used ADB with the stock recovery so I'm unsure if it will work.
Username invalid said:
Since your screen is smashed you won't be able to use ADB/Titanium/Helium backup. With a custom recovery and this installed, you are able to use ADB while in recovery without USB Debugging enabled to pull files onto your computer.
Code:
adb pull /sdcard/ c:/sdcard/
I've never used ADB with the stock recovery so I'm unsure if it will work.
Click to expand...
Click to collapse
Thanks for the very quick reply back. I am very much a novice when it comes to rooting and things like this (thus why I never rooted... I will be on my new N7 though when it arrives in the mail).
Aren't "custom recoveries" for rooted devices only, and what do I do with these "Naked Drivers"?
Thanks very much and sorry if that's a dumb question.
Ivanbarker said:
Thanks for the very quick reply back. I am very much a novice when it comes to rooting and things like this (thus why I never rooted... I will be on my new N7 though when it arrives in the mail).
What is a "custom recovery", and what do I do with these "Naked Drivers"?
Thanks very much and sorry if that's a dumb question.
Click to expand...
Click to collapse
Turn off your device then reboot holding Power + Volume Down while connected to your computer. Then you should see "Nexus 7" under Unknown Devices in your computer device manager.
Username invalid said:
Turn off your device then reboot holding Power + Volume Down while connected to your computer. Then you should see "Nexus 7" under Unknown Devices in your computer device manager.
Click to expand...
Click to collapse
Thanks for the quick response!
I did what you said, and under Device Manager it now says "Google Nexus 7 Bootloader Interface", which is different than before, so I assume I did it properly.
I got into adb shell (installing platform tools through the sdk manager, and then navagating through command prompt to the platform-tools directory), and then I typed what you said, and it tells me: "error: device not found"
I'm guessing this doesn't work with the stock bootloader.
Ivanbarker said:
Thanks for the quick response!
I did what you said, and under Device Manager it now says "Google Nexus 7 Bootloader Interface", which is different than before, so I assume I did it properly.
I got into adb shell (installing platform tools through the sdk manager, and then navagating through command prompt to the platform-tools directory), and then I typed what you said, and it tells me: "error: device not found"
I'm guessing this doesn't work with the stock bootloader.
Click to expand...
Click to collapse
Power + Volume Down is actually just to get into the bootloader. To get into the recovery you need to then press the Volume Up button 2 times if I remember correctly. The options should be Power Off > Reboot > Recovery.
Username invalid said:
Power + Volume Down is actually just to get into the bootloader. To get into the recovery you need to then press the Volume Up button 2 times if I remember correctly. The options should be Power Off > Reboot > Recovery.
Click to expand...
Click to collapse
Ah great. Well I tried that, from the bootloader screen (in device manager it says bootloader interface) I hit up twice and then power button again to enter it.
The little bit of my screen that has some light, flickered a bit, but then the N7 bootloader disappeared from the device manager. Now there is nothing in the device manager, and adb still gives me no result.
Thanks very much for the help. As odd as this sounds, a silver lining is that I am learning lots, and when I get the 2013 N7 I will have no problem rooting it heh.
Ivanbarker said:
Well the worst possible thing happened, I literally smashed my Nexus 7 (2012 - sorry couldn't find the right spot) into tiny bits.
It's kind of a weird story, no I didn't drop it. I was working on my car's engine, using my handy N7 to look up directions. I was proud of myself for fixing my car, and went to close the car's engine hood. I dropped it down. It didn't go down... my N7 was wedged in between the hood of the car and the body. *note to self: always pay attention*
The screen blasted apart (I cannot see anything on it now, and there's large chunks of glass missing), and the body is pretty mangled. My happiness was smashed just like my N7 screen. However it does still work! I was listening to music via bluetooth, and it didn't skip a beat. I was also able to press the physical keys to take a screenshot.
Click to expand...
Click to collapse
At the risk of being the most unproductive comment on this thread, any chance we could see some pics of the damage? they always fascinate me.
fraz82 said:
At the risk of being the most unproductive comment on this thread, any chance we could see some pics of the damage? they always fascinate me.
Click to expand...
Click to collapse
Heh funny how many people have asked that. I will try to post a picture when I get a chance
So I've searched here AND the entire net for a fix for this but I cannot find it anywhere. I'm decently experienced in the area of androids, flashing, and rooting and currently own a rooted Moto G Play running a debloated stock rom with Xposed installed as my main device (besides the point but just so you know my level of experience.)
I was recently given a HTC Desire 526 and was told by the giver that she couldn't turn it on. So obviously my first thought was to try to enter bootloader mode. I charged the device and held the volume up and power keys to enter bootloader, and it was successful, but still no image on the screen, mind you there is zero visible damage on the phone screen or water damage on the inside so I'm guessing it can't be that the screen is broken physically. I confirmed that it was in bootloader by running fastboot and it is listed under devices when I run "fastboot devices." Vibration works and it occasionally outputs sound so I know the phone turns on (at least). I'm completely new to HTC devices and when i try to do almost anything involving flashing with fastboot I get the s-on error. Adb isn't available as I know that developer options, and furthermore, usb debugging has not been enabled on this device at all in the past.
Can I hard reset with just hardware keys (vol up, vol down, and power)? Everything online says yes and then the instructions go on to explain how to reset via the on screen bootloader menu navigation, that of which I can't see nor navigate with a black screen (I know these "solutions" to this problem make no sense considering I asked about a device with a screen that won't turn on, very frustrating haha.) If not, does anyone have any suggestions on what I could do to get the screen to work? Not sure if this matters but it is a verizon phone. Any info is appreciated as I'm coming to my last leg trying to get this going. So annoying feeling it vibrate and hearing sounds because I feel like it is definitely fixable without replacing the screen but I'm not 100% sure. Thanks.
Edit: My only solution is to see if someone who owns this device (currently I know no one with this device) can direct me on what to push, when, to reset without my screen, so I can navigate through that phone or through pictures of it.
This post can be deleted. Still don't know the cause but it turned on and all is well now. Now I'm just searching for a proper root method!