Database Info

Recovery console

Hey guys, here is the deal. I did toasts instructions but forgot to wipe the cache/data so it was just looping along the 4g screen. So I reboot using volume down key and reflash the original PC36IMG.zip, then I do "adb reboot recover" and restore my nandroid backup. Now I can't connect to my phone with my computer in any way. I can reboot using volume down and go to recovery, but when I try to run the script (I'm on a mac, so I'm running recovery-mac.sh) it just says "error: device not found". Furthermore, if I boot back in to android and try to send the "adb reboot recover" command from my macbook I get the same error. Any ideas?

For the record I have installed the SDK.
Also, I've just noticed that it won't even charge when plugged in to my macbook or my girlfriends win7 machine.

sambow said:
For the record I have installed the SDK.
Also, I've just noticed that it won't even charge when plugged in to my macbook or my girlfriends win7 machine.
Click to expand...
Click to collapse
ive only briefly played with the phone. i noticed settings to tell it what action to take when connected via USB. perhaps review these settings, also make sure ADB is turned on in the applications, usb debugging section.
this should at least get you a USB connection in normal android mode.
if you flash the userdebug RUU PC36IMG.zip and reboot into recovery, adb connection should work, otherwise something is wrong and i dont think its the software on the EVO because it seems to work fine for everybody else. perhaps try plugging/unplugging USB, switching USB ports, etc, the usual troubleshooting steps.
let us know how it works out!

No luck, I even tried the exe to reflash to stock (ran while HTC logo was up) and that was a no go.
Any more ideas?

Try a different USB cable. I had a cable suddenly go out on me, and wouldn't charge or act anything like a USB cable should. This was 'not' a cable that came with an EVO... but, worth a shot.

[Q] Sensation won't boot up or charge

I've seen a couple of threads about this but none of them have the same issues as I have or they remain unanswered.
My HTC Sensation (EU version) won't boot up at all. I can't boot it into recovery or bootloader and when charging the light doesn't turn on.
It recently started to randomly reboot and at one point it completely corrupted all files on my SD card. However, it worked ok after I bought a new SD card and the random reboots didn't bother me that much. Today when I woke up however, I saw that it wouldn't respond to me pressing the power button. I also noticed that the charging light wasn't on (it was plugged into the wall overnight).
I tried removing/reinserting the battery, I tried booting into recovery and bootloader, I tried connecting it to my PC and forcing it to boot into bootloader but nothing works. To clear things up, when I try to boot it up nothing happens. The screen stays black and doesn't power on.
The only thing that leads me to believe there's still a chance of it working is that when I plug it into the PC, my PC detects it (although it's unable to install the required drivers for it).
I'd appreciate any help I can get.

intestro said:
I've seen a couple of threads about this but none of them have the same issues as I have or they remain unanswered.
My HTC Sensation (EU version) won't boot up at all. I can't boot it into recovery or bootloader and when charging the light doesn't turn on.
It recently started to randomly reboot and at one point it completely corrupted all files on my SD card. However, it worked ok after I bought a new SD card and the random reboots didn't bother me that much. Today when I woke up however, I saw that it wouldn't respond to me pressing the power button. I also noticed that the charging light wasn't on (it was plugged into the wall overnight).
I tried removing/reinserting the battery, I tried booting into recovery and bootloader, I tried connecting it to my PC and forcing it to boot into bootloader but nothing works. To clear things up, when I try to boot it up nothing happens. The screen stays black and doesn't power on.
The only thing that leads me to believe there's still a chance of it working is that when I plug it into the PC, my PC detects it (although it's unable to install the required drivers for it).
I'd appreciate any help I can get.
Click to expand...
Click to collapse
open a cmd window in your adb and fastboot folder and try this command
adb boot bootloader

rzr86 said:
open a cmd window in your adb and fastboot folder and try this command
adb boot bootloader
Click to expand...
Click to collapse
That command didn't work for me and displayed a wall of text. After looking through it I found a similar command which I tried
adb reboot-bootloader
When I entered that it said that it was starting the daemon on port, that the daemon had started succesfully and then it gives me the error: device not found.

intestro said:
That command didn't work for me and displayed a wall of text. After looking through it I found a similar command which I tried
adb reboot-bootloader
When I entered that it said that it was starting the daemon on port, that the daemon had started succesfully and then it gives me the error: device not found.
Click to expand...
Click to collapse
opps i mean reboot
i don't know why i forgot that
previously you said that it detects it
how it detects it?

When I connect the phone to my PC I hear the sound that windows makes when you connect a USB device.

intestro said:
When I connect the phone to my PC I hear the sound that windows makes when you connect a USB device.
Click to expand...
Click to collapse
charge the device without battery,sim and sdcard for 4-5 hours
put them back and switch it on
see how it goes
if that fails then try to switch on the device with a different battery

rzr86 said:
charge the device without battery,sim and sdcard for 4-5 hours
put them back and switch it on
see how it goes
if that fails then try to switch on the device with a different battery
Click to expand...
Click to collapse
I tried the charging method but it didn't seem to do anything.
I don't have a different battery that fits in there. Can I use a smaller and lower capacity battery as well and just connect the contacts? I don't wanna shortcut anything

intestro said:
I tried the charging method but it didn't seem to do anything.
I don't have a different battery that fits in there. Can I use a smaller and lower capacity battery as well and just connect the contacts? I don't wanna shortcut anything
Click to expand...
Click to collapse
No. Don't even try connecting other battery.
Sent from my HTC Sensation Z710e

MrJukeHardbane said:
No. Don't even try connecting other battery.
Click to expand...
Click to collapse
So are there any options left for me? I've read some stuff about Jtagging but I'm not planning on getting a box or paying someone to do it for me.

[Q] Stuck at bootlogo

Hi,
I got this tablet from a friend, and it's stuck at the boot logo. I've tried hard reset, reset via recovery, nothing seems to work.
How can I flash the latest official rom?
Can't seem to find a tool for it, and Asus suggest to flash with the tablet itself, but that's not possible for now.
Anyone?
Thx!

http://forum.xda-developers.com/showthread.php?t=1688012
Easyflasher to flash TWRP recovery > copy ROM to MicroSD card, flash ROM

Thanks! I can't seem to get him into APX mode, what is the exact procedure?

Connect the tab to USB > PC first
Power Off the Tab
Hold Volume Up & Power
Nothing will appear on the Tab screen, but the PC should sound the USB connect noise / device manager will show it has connected - only takes a few seconds to enter APX mode

I've tried that, doesn't seem to recognize it . Would you help me via IM of some sort?

It`ll be the drivers most likely, open device manager when its connected and in APX mode, and manually update the drivers using the Universal Naked Driver from the Easyflasher site
I don't have any IM installed unfortunately but I`ll help you out here

Ok, that would be wonderful. The problem is, I don't know when it's off. I can't get it to shut down, it keeps rebooting. I'm monitoring dev manager with sound high, but it's not coming up. Cable is working, because it will charge. Using the original cable. (Windows 7 x64)

Best thing to do would be connect it to the PC, then press and hold Power until it shuts off, then try for APX mode - you might even be able to enter APX from a powered on state by holding the same button combo, but Ive not tested that myself
And a cable that charges doesn't automatically mean it will work for Data, they use different pins, some for power and some for data, if the data pins are damaged, it will still charge

I can't seem to get it working . Any other ways to flash it?

Not without being able to get it to boot - you'll need APX mode to do anything in the state it's in now
A bad cable is a common problem though, might be worth grabbing another one from eBay

To bad. I'll try and let it drain till it's empty, and fully charge it then. Just ordered another cable.
Thx for the help!

If the System / Data partitions are corrupted, which generally causes the boot loop, then draining and recharging won't help
Plus be careful not to drain the battery to 0%, their design prevents them from recharging if they hit 0% - many people have had to buy new batteries after not using their tab for a few months and letting it drain completely
Good luck, so long as there is no hardware damage, once you have a working cable it should be pretty straight forward to get TWRP recovery and a new ROM flashed to it
Might be worth trying your current cable on another PC too

Thanks for the headsup! Will try!

Hello everyone,
Not to thread jack but I have a similar problem and instead of opening a new thread I decided to revive this one.
I have a similar problem that my TF101 has been working flawlessly for many years. It is rooted and was running 4.3 ROM. As of a couple of days ago it just won't boot at all. It has been stuck at the NVidia screen and just sits there. I tried to enter recovery mode by using volume(-) + power and the unit presents the TEAMWIN logo and just loops as well by showing the TWRP screen (3 seconds) then going blank for a second then showing TWRP screen again in a cycle.
I downloaded and tried Easyflasher and Brks toolkit and nothing can complete the flash. Tried different installed drivers as well. I can enter MTP mode which the computer can see the device but the manufacturer name and model are not-recognized. I can also enter APX mode but while trying to flash anything I get an error message (error, cannot flash bootloader) and the computer dings (device disconnects).
I have been trying for a days now and have run out of ideas.
Has the unit finally bit the dust? Does any one out there have any more ideas or suggestions on what to try next?
TIA for any help provided.

Anyone with any sort of help on my previous post? Time to retire it for real this time?
TIA
Sent from my VisionX powered SM-N900T.

Jayster0966 said:
Anyone with any sort of help on my previous post? Time to retire it for real this time?
TIA
Sent from my VisionX powered SM-N900T.
Click to expand...
Click to collapse
Have you tried a different / new cable in-case that's the reason all the flashing attempts and computer recognising the unit are failing ?

[Q] USB Not Working in Bootloader

I have an old Nexus S that runs painfully slow. No amount of factory resetting helps so I want to perform a full wipe with a clean factory image install and unlock the bootloader while I am at it. I am using the Nexus Root Toolkit and the drivers have installed and are working correctly. However, once my phone reboots into the bootloader USB does not seem to be detected and the operation fails. Starting with my phone on with USB debugging enabled, I have no problem using the ADB quick tools in the Nexus Toolkit to list devices and reboot via ADB. Performing a full driver test runs fine until the phone reboots to the bootloader, then I get a fastboot error. Also, in the bootloader beneath the boot options near the bottom of the screen is this text:
Code:
USB Control Init
USB Control Init end
Another stranger thing is that the volume buttons also don't work in the bootloader, but they work fine when the phone is on. It is weird that these two hardware functions don't work in the bootloader but work fine in the OS. Could this be a software problem in the bootloader itself?

red_skittles said:
I have an old Nexus S that runs painfully slow. No amount of factory resetting helps so I want to perform a full wipe with a clean factory image install and unlock the bootloader while I am at it. I am using the Nexus Root Toolkit and the drivers have installed and are working correctly. However, once my phone reboots into the bootloader USB does not seem to be detected and the operation fails. Starting with my phone on with USB debugging enabled, I have no problem using the ADB quick tools in the Nexus Toolkit to list devices and reboot via ADB. Performing a full driver test runs fine until the phone reboots to the bootloader, then I get a fastboot error. Also, in the bootloader beneath the boot options near the bottom of the screen is this text:
Code:
USB Control Init
USB Control Init end
Another stranger thing is that the volume buttons also don't work in the bootloader, but they work fine when the phone is on. It is weird that these two hardware functions don't work in the bootloader but work fine in the OS. Could this be a software problem in the bootloader itself?
Click to expand...
Click to collapse
(These are only suggestions)
Try another cable, another usb point on the computer, unplugging and replugging the usb into the phone while in bootloader, try pressing the power button to reload the bootloader, try installing another driver from NRTK, try booting into the bootloader from a powered off state while connected to the computer.. Good luck

Setting.Out said:
(These are only suggestions)
Try another cable, another usb point on the computer, unplugging and replugging the usb into the phone while in bootloader, try pressing the power button to reload the bootloader, try installing another driver from NRTK, try booting into the bootloader from a powered off state while connected to the computer.. Good luck
Click to expand...
Click to collapse
No luck with any of these suggestions. As a test I booted my Nexus 7 into the bootloader plugged in the USB. My PC immediately made the chime noise to let me know a USB device had been plugged in. This is not the case when the Nexus S is plugged in while in the bootloader. Windows Device Manager also doesn't recognize the NExus S when it is in the bootloader.
The fact that USB isn't a problem in the OS leads me to believe this isn't hardware related. Is there a way to update/reflash the bootloader from on the device without using fastboot?

red_skittles said:
No luck with any of these suggestions. As a test I booted my Nexus 7 into the bootloader plugged in the USB. My PC immediately made the chime noise to let me know a USB device had been plugged in. This is not the case when the Nexus S is plugged in while in the bootloader. Windows Device Manager also doesn't recognize the NExus S when it is in the bootloader.
The fact that USB isn't a problem in the OS leads me to believe this isn't hardware related. Is there a way to update/reflash the bootloader from on the device without using fastboot?
Click to expand...
Click to collapse
I don't know if there is a phone bootloader update..?? Have you tried the "bricked" option?.. I am sure that you have already backed upp all your data, as unlocking the phone wipes it..

[Q] Hard-Bricked, no boot. Failed during flash

OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
+1

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
So will the tablet not boot into the bootloader ?
Thx Josh

lj50036 said:
So will the tablet not boot into the bootloader ?
Thx Josh
Click to expand...
Click to collapse
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.

gtgeek said:
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
Click to expand...
Click to collapse
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh

lj50036 said:
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
Click to expand...
Click to collapse
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?

gtgeek said:
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
Click to expand...
Click to collapse
Nope there is just no way...
The chip is locked down ... :crying:
There is lots of info out there but its just info ...
No one to date has come back from where you are ....
Thx Josh