Database Info

[Q] Bricked Nexus S that doesn't seem to respond to any of the unbricking methods

[EDIT] Just to avoid confusion, I have the 9023 model [EDIT]
So I've tried all the unbricking methods I could find via Google.
Tried this: http://forum.xda-developers.com/showthread.php?t=1447040
The adam tool doesn't work and Odin doesn't see the phone regardless of what state it's in.
Here are the only two screens I can get on the thing. If I allow it to boot into Android it just starts having to force close everything until it reboots.
It does get detected by my computers (tried to rule out computer's USB ports), but only with the little audio notification you get when a device is connected. Windows has the SDK installed with USB drivers as does my Linux drive. I've tried basically everything I can think of short of tossing it in a blender.
Any ideas?
If it at least boots to those screens, tries to boot into Android, and gives me an audio notification for USB connectivity, I figured someone might have insight as to whether or not it's fixable.
Otherwise it goes in the trash.

kgk888 said:
So I've tried all the unbricking methods I could find via Google.
Tried this: http://forum.xda-developers.com/showthread.php?t=1447040
The adam tool doesn't work and Odin doesn't see the phone regardless of what state it's in.
Here are the only two screens I can get on the thing. If I allow it to boot into Android it just starts having to force close everything until it reboots.
It does get detected by my computers (tried to rule out computer's USB ports), but only with the little audio notification you get when a device is connected. Windows has the SDK installed with USB drivers as does my Linux drive. I've tried basically everything I can think of short of tossing it in a blender.
Any ideas?
If it at least boots to those screens, tries to boot into Android, and gives me an audio notification for USB connectivity, I figured someone might have insight as to whether or not it's fixable.
Otherwise it goes in the trash.
Click to expand...
Click to collapse
no need to use linux. go to a windows pc, install the drivers and do this via fastboot commands: http://forum.xda-developers.com/showthread.php?t=1572307

Cascabreu said:
no need to use linux. go to a windows pc, install the drivers and do this via fastboot commands: http://forum.xda-developers.com/showthread.php?t=1572307
Click to expand...
Click to collapse
Thanks a lot for the suggestion. I will attempt this in the next hour or so and report back.

kgk888 said:
Thanks a lot for the suggestion. I will attempt this in the next hour or so and report back.
Click to expand...
Click to collapse
if your fastboot mode works just fine, u will be successful

It just says device not found (and yes I'm in the right directory) or if I skip the adb reboot and go straight to fastboot flash, it says "< waiting for device >"
I hear the sound the plays when something connects via USB and then also a quick 3 tone sound of the same note.

kgk888 said:
It just says device not found (and yes I'm in the right directory) or if I skip the adb reboot and go straight to fastboot flash, it says "< waiting for device >"
I hear the sound the plays when something connects via USB and then also a quick 3 tone sound of the same note.
Click to expand...
Click to collapse
unplug all other usbs and reinstall the drivers? and dont know how to help you more

Cascabreu said:
unplug all other usbs and reinstall the drivers? and dont know how to help you more
Click to expand...
Click to collapse
That didn't work either.
When I the phone is in recovery mode and I plug it into my computer I hear the USB sound notification but nothing shows up on my computer. It doesn't list as a disk or anything.
No idea where to go from here. I went into diskpart and it doesn't list it either.
It's weird that I get the USB sound notification from the computer but it can't show the device to me.....

kgk888 said:
That didn't work either.
When I the phone is in recovery mode and I plug it into my computer I hear the USB sound notification but nothing shows up on my computer. It doesn't list as a disk or anything.
No idea where to go from here. I went into diskpart and it doesn't list it either.
It's weird that I get the USB sound notification from the computer but it can't show the device to me.....
Click to expand...
Click to collapse
at least u can get into fastboot. since an hour ago, mine dont even vibrate when i try to turn it on

Cascabreu said:
at least u can get into fastboot. since an hour ago, mine dont even vibrate when i try to turn it on
Click to expand...
Click to collapse
Oh jeez that would suck.
I was thinking of buying a JTAG setup or whatever it's called. There's some polish site there that delivers in the EU. I just don't know what all parts I need for a Nexus S. There's a YouTube video by the company showing them resetting a Nexus S but they don't list the part numbers or tell us what the parts are, which is kind of annotying. So I'm trying to go through their website and add all the parts that seem right from the description/picture. I figured having the JTAG parts would be good for any other of my phones in the future (assuming they're compatible)
Anyone know what JTAG parts I would need? Here's the website and they have an English version.
http://www.multi-com.pl/

What did u do to you phone to get in into that kind of state?

Can't get Linux to recognize my bricked Sensation

Before anyone tells me to ask on the specific thread or go on irc to get help, please know that I did all of those and thats why I'm opening a thread
So, I bricked my HTC Sensation a couple of months back while trying to update firmware from http://forum.xda-developers.com/showthread.php?t=1412618
But it didn't work properly, and then it didnt have a ROM and it needed a firmware too, and nothing worked. So anyways, i kept trying and all of a sudden my phone wouldn't turn on, charge or anything at all. I realised it was bricked. So recently I saw this thread
http://forum.xda-developers.com/showthread.php?t=1522351
So I decided to give it a try, but my problem is that when i type the command in the terminal, it said device wasn't connected.
Then i came across this http://www.youtube.com/watch?v=_Pcxt6nKI10
So after much effort, I got my sensation to become QHSUSB_DLOAD mode on my computer in Windows. But I realised after I take out my battery and sdcard and plug it into my linux computer, the same thing happens. And when i plug it back into my windows, it doesnt get recognized as QHSUSB_DLOAD anymore.
And it's really hard to get my sensation to show qhsusb_dload mode too.
Any advice on my problem? Thanks. Really wanna get my sensation alive again.

[Q] HTC One S S3 Dead

After countless of weeks trying to figure out what's wrong and how to fix it, I might as well ask help from the masters,
I bought this phone in a non-working condition and was only told it just needed charging.
Here's what I know about it so far:
Z560e
PJ40200
so it's an S3
the phone does not boot up
I cannot get into hboot
the phone shows an amber light when connected to a power source, so I'm assuming it's charging.
sometimes gets detected by the computer as qhsusb_dload but I can't seem to reproduce the condition that it does get detected.
I have taken the phone apart, connected it without the battery to see if qhsusb_dload is detected to no avail
I don't know how it got into this situation and haven't tried any of the methods to fix this as it might worsten the situation.
i have tried to get this checked by a local shop to get it jtagged but he failed and I'm not entirely sure if he put any effort it
I wanna know what's wrong with it and if or how I can fix it?
Any help would be greatly appreciated :highfive:

Is the mode displayed qhusb or qhusb_dload on PC?

it's displayed as qhsusb_dload.
what are the differences exactly? Just so I'd know so I could help out others.

Qhusb is totally bricked and can only be repaired with jtag. Normally qhusb happens by flashing wrong hoot, or recovery etc.
Qhusb_dload can be repaired with PC. Most of the time.
Did you used unlimited.io tool?
Ps I live in Germany, so I won't respond anymore today. Too late here .

wew, well that's a relief. :cyclops:
I haven't yet but I'll try unlimited.io's solution, see if that fixes it.
thanx for your time, it's 5am where I'm from right now and I'll keep working on this till i pass out. :victory:
update: tried unlimited.io's QHSUSB_DLOAD fix but to no avail either, any other suggestions?

No no. Don't try it . Oh damn... Now it's definitely bricked...
I asked if you used it not tried to use it.
Don't wanted you to use it.

hm.. so, what do I do now?

Replied on pm

ok.. so just charge it until Monday?

Yes

@tecardo
my one s s3 too is also bricked like agili, i tried to update to jellybean via OTA and the phone suddenly shutsdown. and now it is bricked. pls help me thanks

Still report back on Monday.

alright, monday is here. what's next?

I would need one of your One S. The reason i had you wait: The battery discharges in this state. If it's empty it's hard to repair.
So someone of you needs to check this: Run a RUU. When Phone is connected.

i ran the ruu, i get an error 170?
so uh, where do i send the phone?
also, would you like me remove the battery so it doesn't discharge on the way there? ill also have it disassembled to save you the trouble

same here tecardo, pls also tell me where i will send my phone im kinda desperate. thanks.

I only need 1 device to look if I can fix it

HTC One Mini (M4_U4) Softbricked, OEM not unlocked, USB debug not enabled, bootloop

Hi all,
My HTC One Mini crashed one month after warranty (Boo!). I can get to the FASTBOOT and BOOTLOADER screen and select options. However, the Factory reset and recovery just cause a vibration and get be back to FASTBOOT menu. The phone is *** LOCKED ***.
After a few false starts on linux and mac machines, I've installed WinDroid Toolkit v3.1 on Windows 7. I have gotten the Token ID and used it to get an Unlock_code.bin via email from the HTC developers website (Cannot link as newb). However, when I follow the instructions in WinDroid it recommends that newer devices require "Enable OEM Unlock" to be set:
I cannot do this now. I continue but when it says a menu will appear on the phone, the menu does not and the phone remains in *** LOCKED *** state. I tried continuing with step 2 "Flashing a TWRP" but it does nothing.
TL;DR Am I screwed with having previously unlocked OEM on my HTC One Mini, now that it is soft-bricked?

I'm not that good at this stuff, but managed to get mine unlocked and a recovery on it via this link
sadly mine still has a problem in that it's now stuck in a boot loop, so don't use Oneclickroot as I did in my post here
hopefully you will get yours to work ok, but when you get to instruction 17 you may find that HTC website is quite fussy with the code you copy/paste
when you copy the Identifier block into Notepad or whatever, ensure you don't get any leading blank spaces before you submit it to HTC.
this excerpt from mine had blank spaces where I have inserted red X's, but it worked with them removed and HTC then emailed me the Unlock_code.bin file
XX<<<< Identifier Token Start >>>>
XX36ADF279412BE14D5002935236B24913
XXetc
XXetc
XX<<<<< Identifier Token End >>>>>
I hope this is of some use mate
---------- Post added at 02:39 PM ---------- Previous post was at 02:26 PM ----------
sorry,
lost the plot on my first reply and forget about the OEM unlock bit ...
to get that OEM unlock bit you would normally
first Enable Developer Modeon your phone by Launching the Settings Application -
Scroll Down and Tap on About Phone(or About Device) - Locate the Build Number Section - Tap on the Build Number Option 7 Times -
Go Back to the Main Settings Page - Scroll Down and Tap on Developer Options and it's found there
but given that you are in is bad a place as me in that we cannot get a bootup, I'm afraid I can't offer any more info,
but it's worth knowing anyway in case you do get booted up

Hi, i have the same issue, but a little different.
My phone was in a box for like 2 months, and then i decide to turn it on again, and i faced the same problem as the OP, but my One Mini is UNLOCKED, and i can't lock it again because i get an error in ADB. I try to enter on recovery (and flashed three differents recoveries without sucess), and reboot in bootloader, then try to factory reset, and reboot bootloader again. It don't do anything, only turn on when i plug the usb and enter in bootloader but no more than that. i've try to flash a RUU too, but it give me the error 171. i tried too the method with the rubber band pressing the power button to cause a reboot loop and get enough charge to launch the system but nothing, i don't see any results. I'm one step closer to give up, please help, i tried everything and nothing has worked for me. If need more information don't doubt on asking me. I really appreciate any help you can provide.

I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen

carkev said:
I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen
Click to expand...
Click to collapse
i don't need to press vol down and power together, the phone enter in bootloader once you plug the usb cable. it do that alone.
This is what i get
C:\adb>adb devices
List of devices attached
C:\adb>
the phone is recognized by HTC Sync manager but i can't see it in ADB.

a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here

carkev said:
a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
Click to expand...
Click to collapse
Hahaha, i know, i have the replacement here, i'll change it once i solve this problem.
carkev said:
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here
Click to expand...
Click to collapse
2. I will leave you down here exactly what i get when i type "adb devices" (with an attached image)
3. i have installed the latest HTC drivers, and i tried connecting my phone to front an rear usb ports, both of them. No results.
4. Down here i'll leave you an attached image of what i get when i try to install a recovery by typing "fastboot flash recovery recovery.img" (i changed the name to recovery.img of course) and the phone seems installing the recovery in fastboot but it gave me that error in adb and when i try to enter in recovery it reboots on bootloader.

your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here

carkev said:
your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here
Click to expand...
Click to collapse
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers

Little Snevil said:
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers
Click to expand...
Click to collapse
Hello guys, I've been following this thread and I'm having same issue. Adb does not sees my phone.
Fastboot does, but when I run ruu , it disconnects and give error 171
Tried usb 2 instead of 3.nothing.
I also think it's the drivers, but I can't seem to find the correct one for this phone. Any help is appreciated

my phone only starts in bootloader it have s-on and i cant use the toolkit cause usb debugging isnt active
adb writes waiting for device
can anyone help me?

My HTC Sensation won't power on or show led or anything

Just out of no where my sensation stopped powering on and doesn't display the led light when charging either.
It does not have water damage and wasn't dropped or anything.
This just happened out of no where.
Does anyone know what I should do or anyone else have this problem?
My ROM is cm-10-20131006-NIGHTLY-pyramid.
Please help me.
s-off
rooted
Note: See the attach picture
When I connect my HTC to my laptop and going to device management

kajaman7 said:
Just out of no where my sensation stopped powering on and doesn't display the led light when charging either.
It does not have water damage and wasn't dropped or anything.
This just happened out of no where.
Does anyone know what I should do or anyone else have this problem?
My ROM is cm-10-20131006-NIGHTLY-pyramid.
Please help me.
s-off
rooted
Note: See the attach picture
When I connect my HTC to my laptop and going to device management
Click to expand...
Click to collapse
do you have access to the bootloader?
also see this
https://forum.xda-developers.com/showthread.php?t=1522351
but i don't think you will have any success

thank you
I tried whit it but didn't work
I used one of Linux live CD, because I can't find PHtoolz-QND.iso
$ ./brickdetect.sh
Searching for bricked device...
./brickdetect.sh: line 4: dmesg: command not found
Device can't be detected. Check connections

kajaman7 said:
thank you
I tried whit it but didn't work
I used one of Linux live CD, because I can't find PHtoolz-QND.iso
$ ./brickdetect.sh
Searching for bricked device...
./brickdetect.sh: line 4: dmesg: command not found
Device can't be detected. Check connections
Click to expand...
Click to collapse
maybe you can try this if you have any experience with jtag method
https://forum.xda-developers.com/showthread.php?t=2775115