Database Info

[Q] Help Desperately Needed - Need to reroot and USB doesn't work

I think I put myself in a bad situation here...
I spent all day trying to figure out how to root my 5 week old Nexus as it's tethering ability is my only access to the web.
So - step one, I did the one-click method, as the instructions I was finding for "the long way" were written by people who know what they're doing FOR people who know what they're doing.
Once that was accomplished, I downloaded Rom Manager. Unfortunately Rom Manager didn't seem to want to work with One-Click's style of rooting, locking me on the boot screen every time I tried using it.
So, I finally worked out how to root my phone the "normal" way and Rom Manager was working.
Here's where my mistake came in... I was one part frustrated from how long it took me to figure it all out, one part elated that I finally DID figure it out, so I immediately put Cyanogenmod on my phone... without backing it up. I played with it a bit, but realized my mistake, so downloaded the 2.3.3 Stock Rom.
That totally futzed things up for me... First, my USB connection isn't working anymore. The USB cable still powers my phone, and the USB ports on my PC still work, but I can't get a phone to pc connection through USB anymore.
Second, my cell radio isn't working anymore, I can only get anything over wifi. The OTA 2.3.4 update was pushed and installed to me that way (The current version my phone is on now...)
Third, apparently my phone was no longer rooted, so Rom Manager wouldn't work anymore for me. When I go to the bootloader menu and try to Recover, it brings me to an android with a triangle and exclamation point symbol.
Once there, some trial and error brought up a menu that I'd hoped would have let me reroot or reinstall a working Rom, but every one I try gives me a Signature Verification error and aborts the install...
So, I'm stuck... Without my USB connection working, I can reroot my phone, and without rerooting, I can't get a working ROM back in place. If ANYBODY can help me with this, it will be greatly appreciated. If any additional information is needed, I'll do my best to give it. Thank you...

Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.

Can you see the phone in fast boot by usb also have you course factory reset and then try to flash
Sent from my Nexus S 4G using Tapatalk

The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.

TBoarder said:
The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.
Click to expand...
Click to collapse
Can you answer my question about fastboot? I want to help you.

matt2053 said:
Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.
Click to expand...
Click to collapse
I did that and nothing came up.

TBoarder said:
I did that and nothing came up.
Click to expand...
Click to collapse
ok can you please install PDAnet on your computer?
http://junefabrics.com/android/download.php
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"

matt2053 said:
ok can you please install PDAnet on your computer?
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"
Click to expand...
Click to collapse
It was already installed, but I reinstalled it. I got to the end of the process where it asked me to go into USB Debugging mode and won't finish the install because it's not reading the USB connection.
(Sorry for any delays here... Being a newbie, I have a 5 minute delay between when I can post)

No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here: http://forum.xda-developers.com/showthread.php?t=947950

matt2053 said:
No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here:
Click to expand...
Click to collapse
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...

TBoarder said:
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...
Click to expand...
Click to collapse
Can you post a link to the stock image you installed?

Was there ever a 2.3.3 for the nexus s 4g? Seems like it shipped with 2.3.4
Sent from my SPH-P100 using XDA App

matt2053 said:
Can you post a link to the stock image you installed?
Click to expand...
Click to collapse
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.

My suggestion is to try and use Odin to flash it back to stock, I don't think Odin needs any drivers to see the phone...
Sent from my Nexus S 4G using XDA Premium App

TBoarder said:
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.
Click to expand...
Click to collapse
Yeah see the thing is there is no 2.3.3 for NS4G. If you flashed 2.3.3 that means you flashed a GSM Rom on your CDMA phone. Oops! not the first time it has happened I'm sure.
Sent from my Nexus S using XDA App

Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!

How did you find astock 233 rom in rom manager, I only see cyanogen nighties oxygen, peter alphonso, extras etc everything is for the nexus a 4g
Sent from my Nexus S 4G using Tapatalk

TBoarder said:
Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!
Click to expand...
Click to collapse
Yeah. I have the T-Mobile version. When I download through Rom Manager I get a popup that says "select your phone model" or something similar and then two choices: "Nexus S" or "Nexus S 4G". It would be really easy to mess that up.
The good news is that I believe your phone can still be recovered, you're definitely not the first person with this exact issue, and at worst, it sounds like you have a Sprint rep who is willing to work with you. I think Odin is your only chance for a software solution. I can't walk you through Odin though, because I've never used it myself.

Let me know what happens.
Sent from my Nexus S using XDA App

matt2053 said:
Let me know what happens.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I just got my warranty replacement phone due to an abnormally long backorder. Thank you very much for your help (And well, I would've more appreciated it if you hadn't shown me that the problem was all my fault... ). Being my only phone and being poor, I won't be trying to root again, no matter what I learned from this problem. Anyway, thanks again, the help was, in all seriousness, greatly appreciated.

How can I get back to the stock rom in AT&T HTC One X

Hello every one,
since HOX from AT&T was sim locked I thought maybe one of the customroms have the ability to unlock the sim but non of them does that.
So now I want to go back to the original "Stock rom" that the HOX from AT&T came with if that possible and how?
I would really appreciate the help.
thanks a lot in advance.

Well unlocking sim has nothing to do with any rom whatsoever.
There are several threads already covering this topic of going back to stock with an RUU
Sent from my HTC One X using Tapatalk 2

Pirateghost said:
Well unlocking sim has nothing to do with any rom whatsoever.
There are several threads already covering this topic of going back to stock with an RUU
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Thanks, but can you guide me to one of these threads related the the HOX, because I was looking for one but I seem not to find them, Sorry

shakash3obd said:
Thanks, but can you guide me to one of these threads related the the HOX, because I was looking for one but I seem not to find them, Sorry
Click to expand...
Click to collapse
Download RUU
Plug phone in
Relock bootloader
Run RUU.exe
That's pretty much it. Its not rocket science.
Sent from my HTC One X using Tapatalk 2

Pirateghost said:
Download RUU
Plug phone in
Relock bootloader
Run RUU.exe
That's pretty much it. Its not rocket science.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I know it's not rocket science, but even before I created this thread, I knew that I need to do what you just said but my problems were the following:
When I was trying to relock the bootloader using the windows command line, I got the following message
< waiting for device >
and that stayed there forever, I mean I was waiting for 2 hours just to make sure wither something working or not but it wasn't doing anything.
I got the previous message when I typed the following command
fastboot oem lock
-------
I thought maybe I need to run the RUU first, then I should relock the bootloader but even doing that ended up with error.
By the way, the RUU I used is
RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17.32.09.12_10.86.32.08L_release_262092_signed
and I am currently downloading
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
and I will see if this one works or not.
I hope you can see that I didn't post this thread without doing some search first but in fact it was the time to ask for help so it is not laziness.
Thanks

waiting for device indicates it doesnt see your phone. are you in fastboot USB when you run the command?
do you have FAST BOOT disabled in the OS (settings, power)
there are a couple of tutorials already available on this exact subject...not sure what it is you are looking for at this point, but it sounds like you need to get your computer to see the device
there is zero need to wait 2 hours for fastboot to show up on computer, it should happen immediately assuming you are actually in FASTBOOT USB mode
remember UNLOCKING the phone with HTCDEV?
you pretty much follow those guidelines to get
fastboot oem lock
to work
then you can run the RUU, any RUU made for your device (CINGULAR RUU is correct)

[Q] no bootloader, s-off, root under android 4.1.1

Hello,
I bought me a used evo shift 4g with android 4.1.1. Is there a possibility, to get s-off or root? I can't even get into bootloader (volume down and power). I already tried different methods, but nothing seems to work. Can anybody help me please?

derkleinebroicher said:
Hello,
I bought me a used evo shift 4g with android 4.1.1. Is there a possibility, to get s-off or root? I can't even get into bootloader (volume down and power). I already tried different methods, but nothing seems to work. Can anybody help me please?
Click to expand...
Click to collapse
Yes you can get s-off, look in the development section, there is a one click root. Since you have 4.1 on there I am guessing you are S-ON rooted?

derkleinebroicher said:
Hello,
I bought me a used evo shift 4g with android 4.1.1. Is there a possibility, to get s-off or root? I can't even get into bootloader (volume down and power). I already tried different methods, but nothing seems to work. Can anybody help me please?
Click to expand...
Click to collapse
If you can't get into bootloader, try enabling usb debugging ( Settings > Development), then connect your phone to your computer and download the Android Debug Bridge (ADB) from HERE
Open a command window in the place where you extracted the adb files and type "adb devices"
If your device is not recognized, download and install the drivers from HERE
After that, try "adb devices" again, if something like "HT8472JW76 device" shows up, then that's good
Now type "adb reboot-bootloader" and see if that gets you into bootloader
This is kind of a lot of work, but it definitely helps in the long run. Also, I would not run my utility until you have downgraded to 2.2 by running an RUU (all of them can be found HERE, 2.2 is the one that has the number "1.17.651") or by flashing a PG06IMG.zip through bootloader. The utility checks what version you are using, and if its anything other than 2.2 or 2.3.4 it throws an error, so just downgrade to 2.2 directly and then use the utility.
If you have any questions or if anything does not make sense, don't be afraid to ask
Sent from my PG06100 using xda premium

bilgerryan said:
Yes you can get s-off, look in the development section, there is a one click root. Since you have 4.1 on there I am guessing you are S-ON rooted?
Click to expand...
Click to collapse
Nevr heard about s-on rooted - but i'm no expert. What I can say is, that i have no super-user rights.

CNexus said:
If you can't get into bootloader, try enabling usb debugging ( Settings > Development), then connect your phone to your computer and download the Android Debug Bridge (ADB) from HERE
Open a command window in the place where you extracted the adb files and type "adb devices"
If your device is not recognized, download and install the drivers from HERE
After that, try "adb devices" again, if something like "HT8472JW76 device" shows up, then that's good
Now type "adb reboot-bootloader" and see if that gets you into bootloader
This is kind of a lot of work, but it definitely helps in the long run. Also, I would not run my utility until you have downgraded to 2.2 by running an RUU (all of them can be found HERE, 2.2 is the one that has the number "1.17.651") or by flashing a PG06IMG.zip through bootloader. The utility checks what version you are using, and if its anything other than 2.2 or 2.3.4 it throws an error, so just downgrade to 2.2 directly and then use the utility.
If you have any questions or if anything does not make sense, don't be afraid to ask
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
OK! Thanks a lot. I will tell you, if I was sussesful.

derkleinebroicher said:
Nevr heard about s-on rooted - but i'm no expert. What I can say is, that i have no super-user rights.
Click to expand...
Click to collapse
Do you have superuser installed? Or ROM Manager? You're problem is strange. Check out ROM Manager after you install superuser and see if it will let you install a recovery... I have never had S-On root I just know it's out there and you have to have some kind of root because you are not on stock. I am S-Off and most of the people on here are, so root that baby and get to flashing.

bilgerryan said:
Do you have superuser installed? Or ROM Manager? You're problem is strange. Check out ROM Manager after you install superuser and see if it will let you install a recovery... I have never had S-On root I just know it's out there and you have to have some kind of root because you are not on stock. I am S-Off and most of the people on here are, so root that baby and get to flashing.
Click to expand...
Click to collapse
well, I know these things from my wildfire. I have installed superuser and also ROM manager but can'tget superuser permissions or install a recovery. But when I start the phone, there is not the original HTC-screen, but a custom-screen. So I agree with you, that I am not on stock - some kind of very strange. It seems to me, that all the root-tools only work with 2.3.x, so if i could downgrade, that might help as well.

derkleinebroicher said:
well, I know these things from my wildfire. I have installed superuser and also ROM manager but can'tget superuser permissions or install a recovery. But when I start the phone, there is not the original HTC-screen, but a custom-screen. So I agree with you, that I am not on stock - some kind of very strange. It seems to me, that all the root-tools only work with 2.3.x, so if i could downgrade, that might help as well.
Click to expand...
Click to collapse
The shift was shipped with 2.2 and 2.3.x so if you have anything other then that it was rooted to get to where you are. How you lost root is beyond any of us. And maybe beyond the guy that sold it to you. Pull the battery and place it back in hold volume down and power, that should be a sure shot at getting to bootloader, then take a picture and post that
Sent from my myTouch_4G_Slide using Tapatalk 2

He said he couldn't get to the bootloader with power and volume down

derkleinebroicher said:
well, I know these things from my wildfire. I have installed superuser and also ROM manager but can'tget superuser permissions or install a recovery. But when I start the phone, there is not the original HTC-screen, but a custom-screen. So I agree with you, that I am not on stock - some kind of very strange. It seems to me, that all the root-tools only work with 2.3.x, so if i could downgrade, that might help as well.
Click to expand...
Click to collapse
Like strapped365 said, this is definitely a weird situation and I've never come across it myself. The best option would probably be to just run a 2.2 RUU and root from there. You can also check for root by downloading "root checker" from the play store, its by joeykrim (the free version will work fine)
strapped365 said:
The shift was shipped with 2.2 and 2.3.x so if you have anything other then that it was rooted to get to where you are. How you lost root is beyond any of us. And maybe beyond the guy that sold it to you. Pull the battery and place it back in hold volume down and power, that should be a sure shot at getting to bootloader, then take a picture and post that
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
He had said earlier that that didn't work for him, that's why I suggested the adb route
derkleinebroicher said:
OK! Thanks a lot. I will tell you, if I was sussesful.
Click to expand...
Click to collapse
No problem, post if any issues :good:
Sent from my speed-y

If he can't get into boot loader its probably because fastboot is checked. In 2.3x its in settings/power at the bottom. I don't know about his though.

Chad The Pathfinder said:
If he can't get into boot loader its probably because fastboot is checked. In 2.3x its in settings/power at the bottom. I don't know about his though.
Click to expand...
Click to collapse
Hmm, my understanding was that fastboot is only on HTC roms?
Sent from my PG06100 using xda premium

Chad The Pathfinder said:
If he can't get into boot loader its probably because fastboot is checked. In 2.3x its in settings/power at the bottom. I don't know about his though.
Click to expand...
Click to collapse
He said he was on 4.1 there are only two choices for JB before yesterday... Evervolv or deck's CM10

bilgerryan said:
He said he couldn't get to the bootloader with power and volume down
Click to expand...
Click to collapse
Bootloader don't just do a houdini its there somewhere
Sent from my myTouch_4G_Slide using Tapatalk 2

I was thinking broken volume button cuz I couldn't come up with anything else lol

Bootloader don't just do a houdini its there somewhere
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
Hmm, thats interesting. So its not possible to delete the bootloader at all?
Sent from my PG06100 using xda premium

It's me again. I just connected the guy, who sold me this phone. Perhaps he can help. If not, i will try the adb-method. If I get problems with that, I'll ask for help again here - i'f never tried this method. But thanks to all you guys so far for your interest and support. i'll keep you informed.
P.S. Root checker told me "no root". And because some one asked me, this is the bootscreen. there is no HTC-screen before that. ATTACH]1532658[/ATTACH]

derkleinebroicher said:
It's me again. I just connected the guy, who sold me this phone. Perhaps he can help. If not, i will try the adb-method. If I get problems with that, I'll ask for help again here - i'f never tried this method. But thanks to all you guys so far for your interest and support. i'll keep you informed.
P.S. Root checker told me "no root". And because some one asked me, this is the bootscreen. there is no HTC-screen before that. ATTACH]1532658[/ATTACH]
Click to expand...
Click to collapse
No problem, keep us posted :good:
Sent from my PG06100 using xda premium

CNexus said:
Hmm, thats interesting. So its not possible to delete the bootloader at all?
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Check what was quoted.... Did I say that? no I did not, i said it don't just disappear. And before that I said the guy that sold it to him would know what was wrong.
Now if you delete your bootloader that's on you, and if you did it and didn't tell anyone then sold said phone, you would be the only one who could help someone in that situation. After you hangout here more you will notice a redundancy of posts because 90% of rooted users don't even deserve to have a smartphone let alone a rooted one, so they never know what their talking about so we try to push the core troubleshooting methods to get them to where they need to go. It's like calling sprint what's their first step? Factory data reset to give you a level playing field, here I just told the guy how to get into bootloader if there was a fastboot checked. Also I've seen so many users get the version of Sense mixed up with the version of Android so again we fall back to the core known methods of solving a problem. I've been with the shift since release so I've seen every failed ota by HTC and every moronic thing that can be done with this phone. But no matter how I told him to get somewhere all you new guys just take over like no oldies but goodies know......btw if bootloader is missing adb reboot bootloader wouldn't work either right? So again with the redundant instructions to get the the same place
Sent from my myTouch_4G_Slide using Tapatalk 2

bilgerryan said:
He said he was on 4.1 there are only two choices for JB before yesterday... Evervolv or deck's CM10
Click to expand...
Click to collapse
Just forget about me....
btw, there are alot more sites then XDA that may have ROMS for the shift.

[Q] Bricked??

i recently tried to install jellybean but the rom did not work on nexus s, i stupidly removed the only working rom from my 'sd' card and now my phone only boots into a black screen, i have tried to put a known working rom on my phone but every pc i try to connect my phone to says the device has malfunctioned and windows cannot install software. i have tried to use adb but that also cannot find my device. am i looking at getting another nexus with a broken screen and using my working screen to gain a decent phone back or am i missing a vital programme that will fix my utter cockup? thanks in advance

Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app

FirePoncho86 said:
Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i am only famililar with adb to the point of rooting, i have tried to download the drivers but only can see .dll files in the driver folders no option to install said drivers. i can get into power and vol up if that is fastboot?? the problem been is i installed a rom which was meant for the nexus s and i didnt read all comments and later found out it does not work with the nexus. i now cannot access the sd storage to put a working rom onto it . when i open cmd and type adb shell it says device not found. brains ready to explode right now. any help on adb is greatly appriciated

Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app

FirePoncho86 said:
Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i do not know how to flash factory images, im am very much a noob to rooted phones and playing with software.
i can get into fastboot and at the bottom it says
usb control init
usb control init end
top says fastboot mode
product name herring
hw version rev 11
bootloader version i9020xxka3
baseband version i9020xxkd1
carier info eur
ser 33304eb5103500ec
lock state unlocked
my laptop does not recognise the phone so i dont know how to flash a factory image. this is the cmd sequence i get
adb shell
error device not found
tried mounting sd card and data but no joy
also tried mounting usb storage.
all i get is device has malfunctioned and will not run
tried downloading google usb drivers and samsung drivers all to no avail.
fingers crossed you can tell me something i dont know as i really cant afford to buy a new phone

Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app

FirePoncho86 said:
Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
much appriciated and i hope you can too. thank you thank you thanks you

Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!

FirePoncho86 said:
Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!
Click to expand...
Click to collapse
still adb cannot find device.......... any links for known drivers for nexus s on win 7 64 bit?

You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app

FirePoncho86 said:
You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
reinsalled sdk tools, still phone not recognised by laptop. gonna try get a cheaper android and flog this one on ebay as someone else might know how to repair it. thank you for your time and help but it appears its all in vain......... damn stupid phone!

[deleted]

Rodya234 said:
the phone is probably fine if you can get into fast boot.
Click to expand...
Click to collapse
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app

FirePoncho86 said:
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i wish someone could just see this, pdanet asks me to connect my phone to finnish installing the drivers, problem is the phone is NOT RECOGNISED i know exactly what you are all saying to do but my phone will not connect at all. more than happy to post it to one of you guys on here to fix but like i said ive tried everything and have pulled nearly all my hair out in the process

Samsung repair? I know what you're talking about, it happened to me, I was completely bricked, all I could so was send it to Samsung repair..
Sent from my Nexus S using xda app-developers app

Damn, if only you could get it recognized you'd probably be able to flash custom recovery through fastboot and I guess you'd be able to install from sd without data loss.
Sent from my Nexus S

[Q] It's bricked guys, and this is serious sht

Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.

Post your bootloader details
Sent from my HTC Sensation 4G using xda premium

adamagic said:
Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Click to expand...
Click to collapse
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?

anything else you should know?
ganeshp said:
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
heavy_metal_man said:
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
Click to expand...
Click to collapse
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151

adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Hi,
If you can get to bootloader,you are not bricked.

adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium

ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425

ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi,
THIS ONE?

rzr86 said:
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
Not the guide
malybru said:
Hi,
THIS ONE?
Click to expand...
Click to collapse
Yes this one
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
Not the guide
Yes this one
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.

adamagic said:
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
Click to expand...
Click to collapse
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium

still nothing
malybru said:
Hi,
Click to expand...
Click to collapse
Yeah, thanks for the link, but it doesn't work either. I've written the 'cidnum: HTC__622' (without any spaces before and after that) into the txt, but after it's checked the P58IMG.zip doesn't ask me anything, just let me be in bootloader like I'd have started the device in bootloader mode without SD.

all right
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )

adamagic said:
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
Click to expand...
Click to collapse
you can try it
you don't have to lose anything at all
if it doesn't work it will just throw you an error
see how it goes

ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Click to expand...
Click to collapse
rzr86 said:
you can try it
see how it goes
Click to expand...
Click to collapse
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.

adamagic said:
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
Click to expand...
Click to collapse
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium

ohh yes
ganeshp said:
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Some persian guy has uploaded the file I need, but unfortunately I can't register, because I can't answer the randon question during the registration process... Somebody?
http://www.fars-gsm.com/showthread.php?t=57177