Database Info

soft brick plus phone not recognised by adb

--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.

sadrulez said:
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
Click to expand...
Click to collapse
Does QHSUSB_DLOAD appear in device manager?

I looked up d device manager could not find anything like this. Anywhere specific I need to look at ?

sadrulez said:
--------------------------------------------------------------------------------
M new to android. Bought this HTC one s T-Mobile which is rooted and runs cm10 and and android 4.1.2. I have updated it to 10-20121012-nightly-villw in d hope that the WiFi tethering would work. Well it never did. But that is not my prob right now.
I tried a hard reset from bootloader screen and now it says safe to remove SD card. I installed SDK ADT bundle. But the command 'ADT devices ' returns blank. Does not recognise my phone. I downloaded all in one kit and also installed htc drivers given on the same post. Even all in one kit does not recognise my phone. Says device not found. M running vista home premium. I have followed all d steps like putting d phone in debug mode. M I missing something. Pl help. M really stuck now.
Click to expand...
Click to collapse
Your description is confusing to me. Your thread title says it is softbricked but then you say that you put the phone in debug mode? Does your rom boot fully?
Are you trying to toolkit from the Rom, bootloader or fastboot?

If you typed adt devices it won't show anything lol
Sent from my HTC VLE_U using xda app-developers app

Spastic909 said:
If you typed adt devices it won't show anything lol
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Sorry I meant adb devices. I thought the SD card error means soft brick. Sorry for my ignorance. M able to boot and use my phone. Just that sd card won't work and I am not able to connect to adb or all in one kit to fix my issue. I tried connecting after normal boot and from recovery mode and even from boot loader screen. No luck with either of them.

I had an issue with softbricking my phone. A good last resort is to flash the RUU (thats what i was told to do and it worked like a charm). It will totally reset your phone to factory settings...and you will need to re-lock your bootloader (just use the All-In-One Toolkit) but besides that, you will once again have a working phone and can just re-root it. If you need the RUU file I can supply the link to it with a little bit of searching. Good Luck!

sadrulez said:
Sorry I meant adb devices. I thought the SD card error means soft brick. Sorry for my ignorance. M able to boot and use my phone. Just that sd card won't work and I am not able to connect to adb or all in one kit to fix my issue. I tried connecting after normal boot and from recovery mode and even from boot loader screen. No luck with either of them.
Click to expand...
Click to collapse
Everyone's so ready to have a guy run a RUU. Even if he did that it he still would be stuck.
If the toolkit isn't working then you have done something wrong.
Check in device manager and look if you see a category that says "android usb devices"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it's not there you don't have the driver installed correctly. If it is there, double check that you have developer options enabled. In the develop options menu check for something that say enable android debugging.
While you phone is booted normally, plug it into your computer. Can you see something in the notification area that says something about debugging mode?
If you got all that done is the toolkit still not working?

I recommend using a Windows 7 PC to install HTC Sync, then copying the folder to your computer. Then install the drivers manually through device manager, selecting the previous folder that you copied. The drivers should detect your phone then.
@dc211 I can't believe your still using XP lol
Sent from my HTC One S using Tapatalk 2

I connected my phone to a Windows 7 computer and it recognised my phone.
I downloaded All-in-One.
I did not know what is flashing stock recovery. So here is what I did :
I flashed CWM 5.8.3.1(S4).
Then i booted in bootloader and did 'clear storage'. then i did wipe data/factory reset
then i reflashed CWM 5.8.3.1(s4)
Now my phone goes directly into cwm recovery screen automatically.
My SD card still does not mount.
when i try to get into bootloader using All-in-one kit it keeps saying 'waiting for device' on the computer screen and the phone reboots and goes back to CWM recovery screen.
As you are aware there is no removable battery in this phone. I am stuck now. If I hold down the power and Vol down button for as long as one minute nothing happens. Phone eventually comes back to CWM recovery screen.
I tried everything possible from CWM recovery screen. Wiped cache/dalmik cache. Format system/data. Cant format SD card it says unable to mount.
Please HELP !!

sadrulez said:
I connected my phone to a Windows 7 computer and it recognised my phone.
I downloaded All-in-One.
I did not know what is flashing stock recovery. So here is what I did :
I flashed CWM 5.8.3.1(S4).
Then i booted in bootloader and did 'clear storage'. then i did wipe data/factory reset
then i reflashed CWM 5.8.3.1(s4)
Now my phone goes directly into cwm recovery screen automatically.
My SD card still does not mount.
when i try to get into bootloader using All-in-one kit it keeps saying 'waiting for device' on the computer screen and the phone reboots and goes back to CWM recovery screen.
As you are aware there is no removable battery in this phone. I am stuck now. If I hold down the power and Vol down button for as long as one minute nothing happens. Phone eventually comes back to CWM recovery screen.
I tried everything possible from CWM recovery screen. Wiped cache/dalmik cache. Format system/data. Cant format SD card it says unable to mount.
Please HELP !!
Click to expand...
Click to collapse
Try holding volume down and power. Out should boot into the bootloader.
Sent from my HTC One S using Tapatalk 2

I already tried that. Holding vol button down + power button restarts the phone in CWM recovery mode

i tried it least 20 times and was finally able to get the phone to boot to bootloader mode
can you guide me to the next set of steps ..
I am totally relying on this forum at the moment.

sadrulez said:
i tried it least 20 times and was finally able to get the phone to boot to bootloader mode
can you guide me to the next set of steps ..
I am totally relying on this forum at the moment.
Click to expand...
Click to collapse
Run an RUU, whichever suits your CID /bootloader version.
Sent from my HTC One S using Tapatalk 2

[Q] PLz Help Google logo Stuck

My nexus s m200 ( Korean) phone is stuck with google logo . i was talking on a call when phone hung. I tried to restart it but none of the buttons (Power, Up and Down) worked. so i pulled of my battery reinserted and there it was the horrible google logo sign. I tried every thing i tried to recover by going into recovery but recovery failed then i format wipe user data/ sd card but it didn't resolve my issue i even wiped the cache files as well.....
The Bootloader is locked i have tried everything but it just doesn't unlock... i cannot root from sd card because i have no access on it. i gave it to couple of repairmen but they also failed to understand the issue..........??
I cannot root from any software because the bootloader is locked... i even tried in command by typing "fastboot oem unlock" it does give caution the screen but it when i accept it.. it simply says unlock failed..........??????
i even use Nexus Root Toolkit v.1.6.1 . after unlocking when it reboots the cell phone it again hang up on the google logo. and again i have to pull out the battery inorder to go to bootloader menu... and then it is again locked.. kit has also failed to unlock and resolve my issue...
PLz Helpppppp
What SHould I do...........?? Plz can anyone poit me in the right direction.
Plz help its my first time that i hav bought anything this expensive out of my own hard earned moneu :crying:

Faizan.Waheed said:
My nexus s m200 ( Korean) phone is stuck with google logo . i was talking on a call when phone hung. I tried to restart it but none of the buttons (Power, Up and Down) worked. so i pulled of my battery reinserted and there it was the horrible google logo sign. I tried every thing i tried to recover by going into recovery but recovery failed then i format wipe user data/ sd card but it didn't resolve my issue i even wiped the cache files as well.....
The Bootloader is locked i have tried everything but it just doesn't unlock... i cannot root from sd card because i have no access on it. i gave it to couple of repairmen but they also failed to understand the issue..........??
I cannot root from any software because the bootloader is locked... i even tried in command by typing "fastboot oem unlock" it does give caution the screen but it when i accept it.. it simply says unlock failed..........??????
i even use Nexus Root Toolkit v.1.6.1 . after unlocking when it reboots the cell phone it again hang up on the google logo. and again i have to pull out the battery inorder to go to bootloader menu... and then it is again locked.. kit has also failed to unlock and resolve my issue...
PLz Helpppppp
What SHould I do...........?? Plz can anyone poit me in the right direction.
Plz help its my first time that i hav bought anything this expensive out of my own hard earned moneu :crying:
Click to expand...
Click to collapse
First off, CALM DOWN. The fact that you can see the google logo means your phone isn't dead.
Second, do not pull off the battery when you're stuck. Use Nexus root toolkit if you want to do a reboot. Go to Advanced Utilities, Click "Launch", then click Reboot, Reboot Bootloader, or Reboot Recovery.
Make sure you installed the correct drivers for your specific phone model (m200).
Try using the toolkit and set-up your phone correctly. Use PdaNet drivers. Then try to unlock the bootloader again.

Plz Help
ej8989 said:
First off, CALM DOWN. The fact that you can see the google logo means your phone isn't dead.
Second, do not pull off the battery when you're stuck. Use Nexus root toolkit if you want to do a reboot. Go to Advanced Utilities, Click "Launch", then click Reboot, Reboot Bootloader, or Reboot Recovery.
Make sure you installed the correct drivers for your specific phone model (m200).
Try using the toolkit and set-up your phone correctly. Use PdaNet drivers. Then try to unlock the bootloader again.
Click to expand...
Click to collapse
Yes i did install the PdaNet Drivers and then unlocked it that but still it is somehow locked... The thing is that when i simply turn on phone it stucks with the google logo on it. Then any command that i may type is just ineffective.. Command windows says "Device searching" but if i start the phone in bootloader menu then computer recognizes the device.....?? i just cant figure out what to do.......I have been trying to sort this issue since last monday but all in vein...
So any solution that might entertain this problem

Go to bootloader, flash a custom recovery, then flash a new rom.

ej8989 said:
Go to bootloader, flash a custom recovery, then flash a new rom.
Click to expand...
Click to collapse
Thank you so very much for your concerned and valuable advices.... i Really appreciate it but
PLz can u direct me through some instructions that how to flash a custom recovery and then flash a new room...? What soft wares i will be needing and wht will the procedure........??

amydacus3 said:
Central and elegant location.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Didn't get you bro.....??

[Mac Toolkit] Root, Recovery, Unroot, Stock, One-Click! [Update 12/14/2013]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not responsible for anything that happens to your Nexus 7 tablet when you use my toolkits below!!
Based on script by: 1KDS link to his script/tool: Here
What Does This Nexus 7 Toolkit Include?
* Root Nexus 7 - Now works with Android 4.4.X!
* Install ClockworkMod Recovery on Nexus 7
* Unroot/Stock on Nexus 7
* Unlock Bootloader on Nexus 7
* Lock Bootloader on Nexus 7
I Have Made Separate Scripts So You Only Have To Download The Specific Files You Need.
How Do I Use These Toolkits?
1. Download the toolkit of your choice using the links below.
2. Unzip the file and click on click on the green Android icon.
3. Enter your phone into bootloader mode:
First power off your tablet and make sure it's unplugged then,press the volume up, volume down, and power button all at the same time. When your phone vibrates let go of the power button, but keep holding onto the volume up and down button. You will now see a green start screen.
4. Follow directions on the screen.
All Toolkits Can Be Found Using The Link Below:
http://www.androidrootz.com/2013/08/nexus-7-one-click-toolkit-for-mac-2013.html
Changelog:
August 6 2013:
* Initial Release
August 11 2013:
* Added One-Click Unroot/Stock toolkit
December 14 2013
* Updated One-Click Root Toolkit to support Android KitKat
* Added ClockworkMod Recovery One-Click Toolkit to support KitKat
* Removed TWRP One-Click Toolkit - No support for KitKat yet
Please leave feedback!:
Please Hit The Thanks If You Found These Tools Helpful!
Donations Are Greatly Appreciated!
To Donate Please Click the Link Below. Thank you!

TWRP requires me to enter password when I first enter recovery mode, but I haven't set any password before, any idea? thanks

dimchan said:
TWRP requires me to enter password when I first enter recovery mode, but I haven't set any password before, any idea? thanks
Click to expand...
Click to collapse
You should just be able to slide to unlock.

I may have just soft bricked my N7. So after I completed the unlock process, I tried to flash SU and it said no such file or directory. I am able to get to TWRP, but every time I try to boot, it loops on the X logo. I am able to get to fastboot and recovery modes, and ADB sees my device, so I tried to push the SU zip, but it says device not found, even though it shows the device before. I'm at a loss here. Any help would be greatly appreciated.

Airwolf79 said:
I may have just soft bricked my N7. So after I completed the unlock process, I tried to flash SU and it said no such file or directory. I am able to get to TWRP, but every time I try to boot, it loops on the X logo. I am able to get to fastboot and recovery modes, and ADB sees my device, so I tried to push the SU zip, but it says device not found, even though it shows the device before. I'm at a loss here. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Enter into recovery mode and select "Wipe" reboot and you should be able to boot up.

I tried that, but it still sticks on the "x" logo for a long time, like 15 min +. I wiped the boot.IMG in adb, cuz I was trying to restore a fresh one but it wouldn't see my device. How long should it take to boot up?

Finally got it to work. I flashed the boot, system, and recovery img's from ATGadmin's "One click factory restore" thread through fastboot on my mac. Here's the commands I used. (My device was unlocked during process) First I downloaded and navigated to the Nexus_7_Restore_F folder in terminal (cd /users/.....), made sure it saw my device in fastboot mode (fastboot devices), then
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
I think I may not have followed the instructions the first time in this thread. I didn't reboot right after the unlock process to reenable usb debugging. I don't understand why I boot looped after that, and I'm no dev, but certainly not a noob, but it's a lesson to myself and others to take our time and follow instructions exactly! Thanks OP!!!!!

OP, thanks for this!! I haven't used the yet, but I'm going to be shortly. I fully intended to unlock and root manually, but I can't get ADB to recognize my device no matter what I try! That's on my laptop, which is an HP Envy, 64 bit, Windows 7, and i7. I've unlocked, rooted, S-Off'ed, MANY different devices using my laptop, but it just refuses to see my '13 N7 in ADB!! I've tried every driver I could find, even downloaded some of the other toolkits to see if their drivers were any different but I've still had no luck whatsoever. Anyway, my Dad has a year old Macbook Pro laptop and I'm going to borrow it from him to give this a try on his, hoping I FINALLY have some luck!! Thanks for giving everyone the option of using an Apple computer!!! I'll report back with whether this works for me or not. If I still can't get my device recognized even after trying this toolkit, then I guess an exchange at my local Best Buy will be my only other option. Really didn't want to, as this device has no dead pixels, no dust under the screen, and VERY minimal light bleed (don't think it could be much less). I guess I'll have no other choice though if it still isn't recognized even after trying an Apple computer.
EDIT : Meant to ask, is everything that I'll need to do this on his laptop included in the toolkit? Just looked at the download link, will I need the 3 separate toolkits to unlock, root, and flash TWRP? Finally, are there any commands that I'll need to type in to ADB while using your toolkits? (I have never used ADB on a Mac, so I have no experience with that)
Thanks to anyone who can answer my Mac-noob questions
SwiftKey'ed from my '13 Nexus 7 using XDA Premium HD

stanglifemike said:
OP, thanks for this!! I haven't used the yet, but I'm going to be shortly. I fully intended to unlock and root manually, but I can't get ADB to recognize my device no matter what I try! That's on my laptop, which is an HP Envy, 64 bit, Windows 7, and i7. I've unlocked, rooted, S-Off'ed, MANY different devices using my laptop, but it just refuses to see my '13 N7 in ADB!! I've tried every driver I could find, even downloaded some of the other toolkits to see if their drivers were any different but I've still had no luck whatsoever. Anyway, my Dad has a 1 year old Macbook Pro laptop (I think that's what it's called) and I'm going to borrow it from him to give this a try on his, hoping I FINALLY have some luck!! Thanks for giving everyone the option of using an Apple computer!!! I'll report back with whether this works for me or not. If I still can't get my device recognized even after trying this toolkit, then I guess an exchange at my local Best Buy will be my only other option. Really didn't want to, as this device has no dead pixels, no dust under the screen, and VERY minimal light bleed (don't think it could be much less). I guess I'll have no other choice though if it still isn't recognized even after trying an Apple computer.
EDIT : Meant to ask, is everything that I'll need to do this on his laptop included in the toolkit? Just looked at the download link, will I need the 3 separate toolkits to unlock, root, and flash TWRP? Finally, are there any commands that I'll need to type in ADB while using your toolkits? (I have never used ADB on a Mac, so I have no experience with that)
Thanks to anyone who can answer my Mac-noob questions
SwiftKey'ed from my '13 Nexus 7 using XDA Premium HD
Click to expand...
Click to collapse
Read my post above urs. Also, make sure u have USB debugging enabled, before AND after unlocking. I don't think its just ur device that's like that. I had a hard time getting my computers to recognize my device too.

Airwolf79 said:
Read my post above urs. Also, make sure u have USB debugging enabled, before AND after unlocking. I don't think its just ur device that's like that. I had a hard time getting my computers to recognize my device too.
Click to expand...
Click to collapse
Cool, thanks!
EDIT : No commands have to be typed in by the user when using these toolkits. Everything is automated through the toolkits, so even a Mac-noob like myself can breeze right through the entire process. Couldn't be any easier!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium

Can't believe it how incredibly fast that was! I'm finally unlocked, rooted, and have TWRP installed!!!!! Can't believe how FAST your toolkits worked!! Wish I would have known that I wasn't gonna have any luck getting ADB to recognize my device with my laptop, and I woulda borrowed my Dad's Macbook Pro and used your toolkit when you first released it!!! I was gonna do it all manually, but no big deal, just glad it's FINALLY unlocked! Now I've just gotta find a driver so that my laptop recognizes my device via MTP an PTP.
I'm on the XDA app, so I don't see standard signatures. I'm assuming you have a Donate link in yours, but if not then please post it for me. You are definitely getting a donation from me!!!! I'm still just amazed that after the hours I spent trying to get ADB to recognize my device on my laptop, I borrow my Dad's Mac and your toolkits have EVERYTHING done in less than a minute (for those reading this, less than a minute is NOT an exaggeration, these toolkits have you unlocked and rooted with TWRP remarkably fast)!!!!!! You sir, are my hero tonight
SwiftKey'ed from my White Sprint Note 2 using XDA Premium

stanglifemike said:
Cool, thanks!
EDIT : No commands have to be typed in by the user when using these toolkits. Everything is automated through the toolkits, so even a Mac-noob like myself can breeze right through the entire process. Couldn't be any easier!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
Click to expand...
Click to collapse
You're right, but I forgot to reboot after unlocking and re-enable USB debugging. Then my N7 boot looped and I couldn't get any tool kits to work, so the commands I posted are really more for people that can't get their device to boot (or just can't read instructions, like me! Lol).

^^Lol! As long as you got it figured out man, that's what's important! Hopefully no one else will need those commands, but thanks for posting them in case they do!
SwiftKey'ed from my '13 Nexus 7 FHD using XDA Premium HD

stanglifemike said:
Can't believe it how incredibly fast that was! I'm finally unlocked, rooted, and have TWRP installed!!!!! Can't believe how FAST your toolkits worked!! Wish I would have known that I wasn't gonna have any luck getting ADB to recognize my device with my laptop, and I woulda borrowed my Dad's Macbook Pro and used your toolkit when you first released it!!! I was gonna do it all manually, but no big deal, just glad it's FINALLY unlocked! Now I've just gotta find a driver so that my laptop recognizes my device via MTP an PTP.
I'm on the XDA app, so I don't see standard signatures. I'm assuming you have a Donate link in yours, but if not then please post it for me. You are definitely getting a donation from me!!!! I'm still just amazed that after the hours I spent trying to get ADB to recognize my device on my laptop, I borrow my Dad's Mac and your toolkits have EVERYTHING done in less than a minute (for those reading this, less than a minute is NOT an exaggeration, these toolkits have you unlocked and rooted with TWRP remarkably fast)!!!!!! You sir, are my hero tonight
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
Click to expand...
Click to collapse
Your welcome! :good: Glad everything worked out! Here is the donate link if you would like to donate, thanks.

Everything worked perfectly and was crazy fast and easy. Thanks! I did notice that to get into fastboot, you only need to hold down the volume down and power button, and not the up/down/power like the instructions say.

steveo11284 said:
Everything worked perfectly and was crazy fast and easy. Thanks! I did notice that to get into fastboot, you only need to hold down the volume down and power button, and not the up/down/power like the instructions say.
Click to expand...
Click to collapse
This is very true! I also noticed that the instructions were wrong, when I was reading through them. A couple times I actually tried what the OP said to do, just in case it was some new method I hadn't heard of, or something specific to Mac
No big deal, but you'll probably want make the corrections in the OP.
SwiftKey'ed from my White Sprint Note 2 using XDA Premium

Mine is stuck at < waiting for device >.
After a while the Nexus boots up and the script continues to say < waiting for device >.
Any ideas?
I was in fastboot when I started the script.

mallize said:
Mine is stuck at < waiting for device >.
After a while the Nexus boots up and the script continues to say < waiting for device >.
Any ideas?
I was in fastboot when I started the script.
Click to expand...
Click to collapse
Try it manually. In terminal, navigate to the folder where u put the script, or any folder that has adb and fastboot, make sure it sees ur device (fastboot devices), then type fastboot oem unlock. Reboot, re-enable USB debugging. Then copy the supersu.zip to ur device, reboot to recovery, and flash it.
---------- Post added at 12:12 PM ---------- Previous post was at 12:04 PM ----------
If u need help with terminal' this thread is very helpful. I wouldn't download the whole SDK, unless u plan on developing, its really not necessary. http://forum.xda-developers.com/showthread.php?t=1917237

Worked great! Thank you! The only thing I had to do on my own was drag the SuperSU zip onto my device. For some reason when the toolkit tried to apply it, it would say cannot read device for a moment. Other than that small issue the toolkit was awesome. My first time using a toolkit of any kind so thanks for a great n easy experience.
Sent from my Nexus 7 using XDA Premium HD app

Today I tried to unroot my nexus 7 with the toolkit but at the sending system I get an error saying that it failed, only thing that worked is to send the stock recovery and the boot loader after it failed any idea why?
Sent from my Nexus 4 using xda app-developers app

HTC Sensation XE Vibrate When Powered On, Black Screen

Hi I just acquired a HTC Sensation XE with a really weird problem. I couldn't get much information from the previous owner but this is how it goes.
a) Phone will vibrate after power button is pressed to power on but screen is black. No backlight, no lights on the capacitive buttons either
b) Will give a single vibration after every 10 seconds?
c) I managed to do make it detect on the PC, checked on my Device Manager ' My HTC' installed.
d) I can go to command prompt and enter Fastboot devices and it will show some serial numbers starting with an M
So if any of our renowned HTC developers or gurus can point me in the direction to analyse this problem, I would be grateful to absorb all the knowledge and listen to all suggestions and theories.
My question is :-
a) Does anyone have a reference chart for the Qualcomm Error Code Vibration. I have an experience with older HTC HD2 hardware with 7 vibrations indicating CPU hardware fault/overheating problems but this is completely different.
b) Are these symptoms leading to the conclusion of hardware issues or software bricking issues?
c) Any direction that I can start tinkering this phone ?
Thank you so much in advance. I believed alot of Sensation owners faced this problem and I've trawled the internet searching for a plausible hint but have not much luck.
Thank you in advance and may we all learn from this and keep on sharing the knowledge.

zelith said:
Hi I just acquired a HTC Sensation XE with a really weird problem. I couldn't get much information from the previous owner but this is how it goes.
a) Phone will vibrate after power button is pressed to power on but screen is black. No backlight, no lights on the capacitive buttons either
b) Will give a single vibration after every 10 seconds?
c) I managed to do make it detect on the PC, checked on my Device Manager ' My HTC' installed.
d) I can go to command prompt and enter Fastboot devices and it will show some serial numbers starting with an M
So if any of our renowned HTC developers or gurus can point me in the direction to analyse this problem, I would be grateful to absorb all the knowledge and listen to all suggestions and theories.
My question is :-
a) Does anyone have a reference chart for the Qualcomm Error Code Vibration. I have an experience with older HTC HD2 hardware with 7 vibrations indicating CPU hardware fault/overheating problems but this is completely different.
b) Are these symptoms leading to the conclusion of hardware issues or software bricking issues?
c) Any direction that I can start tinkering this phone ?
Thank you so much in advance. I believed alot of Sensation owners faced this problem and I've trawled the internet searching for a plausible hint but have not much luck.
Thank you in advance and may we all learn from this and keep on sharing the knowledge.
Click to expand...
Click to collapse
Hmm. Can you list the fastboot commands available to you? Just type in fastboot h I think. Also try fastboot getvar all and post its results, bar Imei and htcserial number When sensation devices are in Qualcomm diagnostic mode its usually because of trying to s-on again so you could try the unbricking thread by dexter in the dev section.
And just to cover bases, screen definitely okay?
Sent from my HTC Sensation using Tapatalk

Hi there heavy_metal_man,I've just finished swapping with another Sensation XE LCD prior to writing this reply. Yup, tested both LCD panels are good. The issue is with the board itself. Maybe you're right, previous owner might force an S-ON back and brick it. Ok so what are the steps that I need to undertake?

zelith said:
Hi there heavy_metal_man,I've just finished swapping with another Sensation XE LCD prior to writing this reply. Yup, tested both LCD panels are good. The issue is with the board itself. Maybe you're right, previous owner might force an S-ON back and brick it. Ok so what are the steps that I need to undertake?
Click to expand...
Click to collapse
do you have access to the bootloader?
i assume you have since you can use some fastboot commands
if yes read this thread
http://forum.xda-developers.com/showthread.php?t=1672425

zelith said:
Hi there heavy_metal_man,I've just finished swapping with another Sensation XE LCD prior to writing this reply. Yup, tested both LCD panels are good. The issue is with the board itself. Maybe you're right, previous owner might force an S-ON back and brick it. Ok so what are the steps that I need to undertake?
Click to expand...
Click to collapse
really depends on what you have access to and what is still functional,. if you have access to fastboot commmands we can try the command
Code:
fastboot getvar all
and that will give us alot of information, like if the device is still s-on, its hboot version, its cid, its simlock status. lots to use if its s-off we can try using an RUU/fastboot flashing a ruu like @rz86 has linked to. if your s-on and have fastboot we can try the same but it will need to be a RUU that has the same cid and has an equal or higher hboot.
if we dont have fastboot access things get complicated Have a read at this unbricking thread. it may apply since your getting a vib code, but im a bit thrown since the device still shows as "My HTC". this serial code you stated that starts with a M may be the key, so quote it if it doesnt seem to be device identifying (similar to your htcserial but minus the date coding at the start? )

This is a screenshot i took from the PC
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So what do you think? Mine has an Asia / Singapore firmware on it I think cos' it's a local Singapore set.

Oh yeah, and one thing is that I am unable to extract rom.zip from the RUU as I encounter this weird problem. The RUU would start the progress bar and after it reaches the end, the program closes. I had no time to extract the rom.zip from the temp folder as right after the program closes, it clears the contents of the temp folder. The RUU won't even reach the second screen. Tried installing C++ Visual Redistributables 2012 but still no go.
If any kind soul, able to extract for me the ASIA 3.33 firmware's rom.zip I would be really grateful

zelith said:
Oh yeah, and one thing is that I am unable to extract rom.zip from the RUU as I encounter this weird problem. The RUU would start the progress bar and after it reaches the end, the program closes. I had no time to extract the rom.zip from the temp folder as right after the program closes, it clears the contents of the temp folder. The RUU won't even reach the second screen. Tried installing C++ Visual Redistributables 2012 but still no go.
If any kind soul, able to extract for me the ASIA 3.33 firmware's rom.zip I would be really grateful
Click to expand...
Click to collapse
did you try to install it from pc?
connected the device in fastboot mode?
if not do it and if you still have any problems then run it as administrator
did you use this one?
http://fileom.com/utfhvtg37oal/RUU_....24A.3504.31_M_release_285271_signed.exe.html

yup i used from a lot of sources still the same, if only you guys could help me extract the PG58IMG.zip rom it'll be great cos I have only one PC to try this on

zelith said:
yup i used from a lot of sources still the same, if only you guys could help me extract the PG58IMG.zip rom it'll be great cos I have only one PC to try this on
Click to expand...
Click to collapse
ok, Currently uploading the file now. you should issue this to the phone following the fastboot reboot ruu method (with the file in your fastboot folder ), if it asks to reflush the image it means just issue the same command again.
upload link added @zelith

Now i cant get the phone to detect on the pc. Normally what i do is vol down + power let it go after a few sconds n the phone wont start. Nowit just vibrates. Screen is dark. On fastboot it says waiting for device

zelith said:
Now i cant get the phone to detect on the pc. Normally what i do is vol down + power let it go after a few sconds n the phone wont start. Nowit just vibrates. Screen is dark. On fastboot it says waiting for device
Click to expand...
Click to collapse
Guys, managed to get into fastboot again and followed your procedure(s). Flashing went OKAY at the end, reboot phone. Its the same issue. Black screen, no lights on capacitive buttons, phone boots up, just vibrates once every 15 secs. I conclude that most probably the display IC or some IC inside is damaged and this is hardware failure. Thank you so much for your efforts in helping me, really appreciate it so much and I learn alot.
Regards,
We shall rest this case a 3rd level hardware issue/troubelshooting and I'm not going to spend more resources in fixing this.
Case Closed

[Q] Sensation XE Touchscreen Unresponsive/Dead

Hey,
The other morning I was using my HTC Sensation XE Z715e as normal, put it down, came back to it an hour or so later, and the touch screen is completely unresponsive. Not flakey response from it, but stone cold dead.
I can switch the phone off/on using the power button, boot into recovery mode using the power/volume buttons, and it still receives calls/messages/emails, but the touch screen is completely dead.
I'm using an Anker battery, so tried the common fix of raising the grounding pin to contact the back case better and folding up some tin foil under the ground pin, but that had no effect. Let the battery completely discharge, pushed the power button with the battery out, left overnight, then re-charged without touching it and still nothing.
I've been through the stickied [FIX] Touchscreen issues thread and haven't found any of the fixes in there have had any effect... Although I'm not sure what firmware I am running, nor how to update it as it is at the moment..
I disassembled the phone far enough to connect a new digitizer to the logic board, booted again and the new digitizer was also dead to the touch. I tried this with the new digitizer hanging loose on the ribbon cable all laid on the desk rather than completely reassembled.
I've since reassembled the phone with all the older hardware.
Problem is that I'm running one of the Cyanogen ROMs with 4EXT Recovery Touch, meaning that when I select Factory Reset from the recovery mode boot screen, it launches into a recovery screen that requires touch input :-/
Anyone know of a way to force a reset through USB? Or anything else to try?
and please treat me like a 5 year old when explaining things to me....
Many thanks!

_The_Editor_ said:
Hey,
The other morning I was using my HTC Sensation XE Z715e as normal, put it down, came back to it an hour or so later, and the touch screen is completely unresponsive. Not flakey response from it, but stone cold dead.
I can switch the phone off/on using the power button, boot into recovery mode using the power/volume buttons, and it still receives calls/messages/emails, but the touch screen is completely dead.
I'm using an Anker battery, so tried the common fix of raising the grounding pin to contact the back case better and folding up some tin foil under the ground pin, but that had no effect. Let the battery completely discharge, pushed the power button with the battery out, left overnight, then re-charged without touching it and still nothing.
I've been through the stickied [FIX] Touchscreen issues thread and haven't found any of the fixes in there have had any effect... Although I'm not sure what firmware I am running, nor how to update it as it is at the moment..
I disassembled the phone far enough to connect a new digitizer to the logic board, booted again and the new digitizer was also dead to the touch. I tried this with the new digitizer hanging loose on the ribbon cable all laid on the desk rather than completely reassembled.
I've since reassembled the phone with all the older hardware.
Problem is that I'm running one of the Cyanogen ROMs with 4EXT Recovery Touch, meaning that when I select Factory Reset from the recovery mode boot screen, it launches into a recovery screen that requires touch input :-/
Anyone know of a way to force a reset through USB? Or anything else to try?
and please treat me like a 5 year old when explaining things to me....
Many thanks!
Click to expand...
Click to collapse
see here
http://forum.xda-developers.com/showthread.php?t=2437293
but you have to be on S-OFF

rzr86 said:
see here
http://forum.xda-developers.com/showthread.php?t=2437293
but you have to be on S-OFF
Click to expand...
Click to collapse
Just got S-OFF, but get errors when I run the HBOOT to update the PG58DIAG.nbh file:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any more ideas?

_The_Editor_ said:
Just got S-OFF, but get errors when I run the HBOOT to update the PG58DIAG.nbh file:
Any more ideas?
Click to expand...
Click to collapse
i don't know man
post that screenshot in the related thread
i assume they will help you there
edit: i thought something
probably you need the patched hboot

rzr86 said:
i don't know man
post that screenshot in the related thread
i assume they will help you there
edit: i thought something
probably you need the patched hboot
Click to expand...
Click to collapse
Just patched HBOOT from 1.27000 (firmware 3.32), to 1.271100 (firmware 3.33), back down to 1.17 for the PG58DIAG to operate properly... As suggested on this thread
Now stuck on the "beatsaudio" boot screen when it boots into the ROM, as I guess the newer ROM doesn't like the older firmware
abd shows the device connected but offline, and booting into the bootloader just immediately results in the 1.17 firmware update being applied...
I need to get the PG58IMG.zip of my SDCard root, and the PG58DIAG.nbh back on... But can't do it through adb (as I have been doing with "push" and "shell" commands) as device won't boot into ROM with older firmware, and have no card reader to do it manually!
:good:
Will have to wait for the GF to arrive home so I can user her HTC Desire C as a lifeboat for my SDCard...

_The_Editor_ said:
Just patched HBOOT from 1.27000 (firmware 3.32), to 1.271100 (firmware 3.33), back down to 1.17 for the PG58DIAG to operate properly... As suggested on this thread
Now stuck on the "beatsaudio" boot screen when it boots into the ROM, as I guess the newer ROM doesn't like the older firmware
abd shows the device connected but offline, and booting into the bootloader just immediately results in the 1.17 firmware update being applied...
I need to get the PG58IMG.zip of my SDCard root, and the PG58DIAG.nbh back on... But can't do it through adb (as I have been doing with "push" and "shell" commands) as device won't boot into ROM with older firmware, and have no card reader to do it manually!
:good:
Will have to wait for the GF to arrive home so I can user her HTC Desire C as a lifeboat for my SDCard...
Click to expand...
Click to collapse
actually why did you downgrade the firmware?
use the 3.33 universal to upgrade to ics again
indeed the ics rom can't boot with gb firmware
and this guide is for unlocking the network(simcard)
nothing else

rzr86 said:
actually why did you downgrade the firmware?
use the 3.33 universal to upgrade to ics again
indeed the ics rom can't boot with gb firmware
and this guide is for unlocking the network(simcard)
nothing else
Click to expand...
Click to collapse
Was linked to the network unlocking thread from the Touch-Screen Recalibration Tool thread. The PG58DIAG.nbh tool is the same one that's used in the network unlocking apparently, and apparently only runs properly on firmwares <1.18...
A fair few people on the Touch-Screen Recalibration Tool thread had similar problems to me on version 1.27 and were suggested to roll back to 1.17 using the guide in the User-Friendly Firmware 1.17/3.12/3.24/3.30/3.32/3.33 Universal thread.
So yea, that's how deep does the rabbit hole goes at the moment.. For the moment it's soft-bricked until I can gain access to the SD card....
If nothing else, I've learned a lot today about interacting with my phone through the adb and fastboot tools!

_The_Editor_ said:
Was linked to the network unlocking thread from the Touch-Screen Recalibration Tool thread. The PG58DIAG.nbh tool is the same one that's used in the network unlocking apparently, and apparently only runs properly on firmwares <1.18...
A fair few people on the Touch-Screen Recalibration Tool thread had similar problems to me on version 1.27 and were suggested to roll back to 1.17 using the guide in the User-Friendly Firmware 1.17/3.12/3.24/3.30/3.32/3.33 Universal thread.
So yea, that's how deep does the rabbit hole goes at the moment.. For the moment it's soft-bricked until I can gain access to the SD card....
If nothing else, I've learned a lot today about interacting with my phone through the adb and fastboot tools!
Click to expand...
Click to collapse
do you have now a sdcard?
if yes put the 3.33 universal firmware(pg58img.zip) in the root of the sdcard
boot to the bootloader and it will detect it

rzr86 said:
do you have now a sdcard?
if yes put the 3.33 universal firmware(pg58img.zip) in the root of the sdcard
boot to the bootloader and it will detect it
Click to expand...
Click to collapse
I didn't, but even if I did I had no way of getting the info onto the micro-SD card.. No card reader on my PC, and the phone wasn't allowing me to copy info onto it.
My GF has just arrived home though so I can use her HTC Desire as an interface for the microSD card..
Getting more errors running the PG58DIAG tool now!
When running the TP Calibration (touch panel), I get the error "I2C read fail" pop up in red.. and no further joy...

_The_Editor_ said:
I didn't, but even if I did I had no way of getting the info onto the micro-SD card.. No card reader on my PC, and the phone wasn't allowing me to copy info onto it.
My GF has just arrived home though so I can use her HTC Desire as an interface for the microSD card..
Getting more errors running the PG58DIAG tool now!
When running the TP Calibration (touch panel), I get the error "I2C read fail" pop up in red.. and no further joy...
Click to expand...
Click to collapse
hmm,
i don't know mate
i have never used that zip file