[Q] Can you handle this uber-debricking challenge on my HTC Desire? - General Questions and Answers

Hi,
so if you have seen of a thread directly relevant to this please post the link...
My HTC Desire is bricked to the point it won't even display anything on the screen.
I have had Cyanogen7 installed for over a month. It was working OK, then I power cycled it. It did not boot fully, restarting at the swirly arrow cyanogen screen. Next, I entered boot loader, and exited that when I removed the battery. I then required HOME and MENU buttons to be pressed in addition to VOL DOWN + POWER in order to enter boot loader.
It took 35 seconds to leave the initial splash screen.
It took an extra 10 seconds for the OS to hit the point where it restarted, and it stayed constantly restarting the swirly arrow cyanogen screen every 10 seconds.
And now the piece-de-resistance – I installed the Android SDK, hoping to run fastboot to at least recover my data. After SDK installed I connected the Desire to my PC, and now it won't even turn on. Before the SDK USB drivers were installed it would enter HBOOT. Now, absolutely nothing. Not even a splash screen. Tried all button presses when turning on, removing SD and SIM, left battery out for 1 min, still nothing.
After following the instructions here:
wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
I installed the generic USB divers, and power cycled my PC. Left the USB cable connected for 10 min in-case the battery had run down (battery sitting at 3.2V). Still no joy.
This is the worst value paperweight I have ever bought.
Any advice on how to recover this would be great.
-WT.

Related

Serious Issue with NVflash or Gtablet

Well I was screwing around with my gtab, trying to put honeycomb on it, (I was on cyanogenmod) and I knew that I needed to put build 4349 on it. Unfortunately, I put that build on it, and installed my rom, but it didn't work. I decided to do the exact same thing over again, to see if it worked the second time. Halfway through the process, while restarting my gtablet, I had a serious problem. My gtablet will turn on after holding down the power button for about 30 seconds, but the screen is completely black and blank. Also, if I hit the (+) button, it says it will boot a recovery image, but it never does. If I hit the (-) to put it in APX mode for a NVflash, it simply turns off.
PLEASE, I have no idea what to do, because I really don't know what is going on with my tablet. I am just trying to put a honeycomb rom on it, but it seems I have completely screwed it up.
To put it straight: It won't go into APX mode
The screen is supposed to go black and blank when you start up in APX mode. Plug it into your computer and check to see if it is or not.
yea but supposedly it shows the viewsonic logo for a second. Mine when I hit the power button and hold the minus and just hit the power button are both the same. Also, I plug it in and nothing happens.
I tried holding the power for 15 seconds, nothing, if I hit the power for about 5 seconds it turns on that blank screen, if I hit + it says recovery key detected and booting recovery, but nothing happens after that
the black screen is the APX screen, it is blank and black.
You don't see an android symbol first.
my computer never says anything about a tablet without drivers or anything as stated in all guides
It's not unusual for the VS Birds splash screen to get lost during flashing operations that go bad. You also might not get a missing driver message for a number of reasons (especially if the driver isn't missing). So...
If the splash screen is missing, when you turn the tablet on while holding the volume down key the backlight should come on momentarily then the screen will go black. If that happens then you are in APX mode. If you have a linux box handy you can plug it into that and issue an "lsusb" command in a terminal window to verify that. There might be an equivalent for windows but I don't use it so I can't tell you what it would be.
If you are really having that much trouble with it I'd be happy to look at it for you if you cover shipping.

[Q] ASUS TF300T - BRICKED (or not???)

Hi friends,
this is my first post here, and that's a real honor to write on this community.
Unfortunately, I'll start with a problem...:crying::crying::crying:
I had (until yesterday) Cyanogenmod 11 on my ASUS TF300T, but lately, it started to be very slow.
I needed 3 minutes to switch it on, and over 5 minutes to be sure that all the apps were normally working, so I decided to install the Cyanogenmod 12. After a normal installation, everything was good, but I wanted to clean completely the system, and eventually reinstall only those apps really necessary to me.
So I entered in the system options and clicked on the factory reset button...after 30 secs my tablet restarted, and sadly it blocked on TWRP start. What I see, is only the "TEAMWIN" logo, that flashes every 5 secs.
I've tried with the reset button, VOL +, VOL -, switched on and off dozen times.
It shows everytime the line "The device is unlocked, the the logo ASUS, and finally the "TEAMWIN" logo.
It goes automatically to this blue logo also when I charge the tablet.
To switch it definetly off, I need to keep pushed the VOLUME +, with the power button, and release only this second button when the screen is dark.
The charge is regular.:good:
Connecting the tablet to the pc (Windows 8.1), USB 2, is useless: I only receive a message, requesting to change port or switch the tablet on (all my USB ports say the same).
What should I do? ( before I trash everything)...:crying:
Thank you in advance

Boot loop, dead battery, no recovery

Thanks for any help in advance.
My Nexus 5 device is unable to boot stock or recovery image. It's a locked bootloader, and stock ROM from my wireless carrier. I charged it with a 2 amp capable charger.
Symptoms: preceding the failure , there were strange slowdowns, apps crashing, and inability to charge the battery over the course of a day. When the battery finally died, that was the last I saw my Operating System. Now, when it's plugged in to power, it indicates full charge. If the power button is pressed it will show the Google logo, then cycle back to the battery charged icon. If the power button is held, the battery logo is skipped and Google logo displayed repeatedly. If the down volume button is pressed in addition to power, I get the screen where I can chose the recovery loader, but then the process of Google logo and reboots persist.
If nothing else, I'd like to grab built-in SD card memory contents and strip out a bitcoin key with about $40 on it that I didn't get to back up before it failed.
What have I tried so far: basically everything above to generate those symptoms. I also tried opening the back, and pulling one of the top cover and unplugging the battery entirely. No effect.
Cheers all. :good:
what happens when you connect it to your pc?
Possible power button issue? You could open the phone, remove the plastic power button from the phone housing, reconnect everything, and then try to boot the phone.
When I connect it to the PC, it goes through the same fully charged loop until I hit the power button for 2S, then it boots. If I hold power, it boot loops; if I leave it alone it fully charged loops (regardless of battery being attached or not). If I remove power button and depress it manually, I get the same loop.
This is a refurb from Google, about 8 months old.

Tablet appears to be dead

Hi
I had this tablet for about two years, ran amazon Fire toolbox on it and everything was fine.
Couple of days ago it turned off, I think the battery level was around 15%. I was not able to turn it back on.
I decided to charge it overnight. Next morning I tried to turn it on but it stuck on Amazon logo.
I tried to do Power + Volume and was able to see the menu, attempted to do restart, then factory reset - and had this bunch of errors. Then I did the power down from the menu, and after that it doesn't turn on even to recovery any more, the screen is black, no logo, no backlight.
When I connect it to computer (the same I ran amazon fire toolbox on) there is an unknown device, but that's it, adb and fastboot don't see any devices.
Update: another windows machine recognized it as a Mediatek USB port and was able to install drivers.
When connected, it appears to be in a loop - Mediatek USB port device appears and in several seconds dissappears, in cycle.
Any help will be highly appreciated!
Thank you!
undersky said:
Hi
I had this tablet for about two years, ran amazon Fire toolbox on it and everything was fine.
Couple of days ago it turned off, I think the battery level was around 15%. I was not able to turn it back on.
I decided to charge it overnight. Next morning I tried to turn it on but it stuck on Amazon logo.
I tried to do Power + Volume and was able to see the menu, attempted to do restart, then factory reset - and had this bunch of errors. Then I did the power down from the menu, and after that it doesn't turn on even to recovery any more, the screen is black, no logo, no backlight.
When I connect it to computer (the same I ran amazon fire toolbox on) there is an unknown device, but that's it, adb and fastboot don't see any devices.
Update: another windows machine recognized it as a Mediatek USB port and was able to install drivers.
When connected, it appears to be in a loop - Mediatek USB port device appears and in several seconds dissappears, in cycle.
Any help will be highly appreciated!
Thank you!
Click to expand...
Click to collapse
Your eMMC probably died (notice the input-output errors), try to use amonet. If the script reports "read error" then nothing can be done.

Oneplus 8T bricked after dying last night

Was watching youtube videos last night before my phone died, now I can't get it to start boot into the OS. Not sure if this is relevant but my power button had been a little finnicky- rather maybe not the power button itself because it doesn't feel stuck or anything at all but I noticed that it would take an extra second or two after pressing the power button to get into my lock screen. I never really paid attention because it only happened once in a while and I would just restart my phone and be done with it. However I can't even get into the lock screen or anything now.
After my phone died last night I plugged it in right away and came back a while later to turn it on. I tried turning it on but noticed my phone just kept rebooting. It's still repeatedly rebooting and I can only get in the fastboot menu by holding down both volume buttons when rebooting. I get the options power off- which just reboots it after a while, start - which just reboots the phone, restart boot loader- which literally takes me back to the same menu, recovery mode- just reboots and show barcode which shows the barcode at the bottom of the menu.
I've tried downloading the qualcomm driver and trying to get into EDL mode but don't see it on my pc or msmtool, i'm also not even sure if i'm trying to get into EDL mode correctly. I've tried disable Driver signature Enforcement and then redownloading the qualcomm driver but still no luck. I don't know what else I should try. Someone please help me out, i'm pissed this happened just because my phone died, about to have ptsd whenever my phone is at 5% fml.
Also after seeing the 1+ logo and powered by android on the bottom, sometimes I would see like a line of color, which I would assume is text not being rendered all the way, fade out and then the phone shuts down and reboots itself.
yellownese said:
Was watching youtube videos last night before my phone died, now I can't get it to start boot into the OS. Not sure if this is relevant but my power button had been a little finnicky- rather maybe not the power button itself because it doesn't feel stuck or anything at all but I noticed that it would take an extra second or two after pressing the power button to get into my lock screen. I never really paid attention because it only happened once in a while and I would just restart my phone and be done with it. However I can't even get into the lock screen or anything now.
After my phone died last night I plugged it in right away and came back a while later to turn it on. I tried turning it on but noticed my phone just kept rebooting. It's still repeatedly rebooting and I can only get in the fastboot menu by holding down both volume buttons when rebooting. I get the options power off- which just reboots it after a while, start - which just reboots the phone, restart boot loader- which literally takes me back to the same menu, recovery mode- just reboots and show barcode which shows the barcode at the bottom of the menu.
I've tried downloading the qualcomm driver and trying to get into EDL mode but don't see it on my pc or msmtool, i'm also not even sure if i'm trying to get into EDL mode correctly. I've tried disable Driver signature Enforcement and then redownloading the qualcomm driver but still no luck. I don't know what else I should try. Someone please help me out, i'm pissed this happened just because my phone died, about to have ptsd whenever my phone is at 5% fml.
Also after seeing the 1+ logo and powered by android on the bottom, sometimes I would see like a line of color, which I would assume is text not being rendered all the way, fade out and then the phone shuts down and reboots itself.
Click to expand...
Click to collapse
Which OOS build are you on? And your device is unlocked or not?
Getting into EDL mode is tricky. Power off device completely. With the device powered off, hold down volume up and volume up at the same time, keep them pressed all the time, and during that time plug into PC (phone all the time powered off). Still hold both of the buttons. By the time you plug into PC, you should be in EDL mode, BUT it only lasts about 10 seconds. I mean you have to click start in this 10 seconds time bracket, other way phone exits EDL itself. After you click start, you can release button, obviously

Categories

Resources