Database Info

Phone keeps looping the hero boot screeen help please

Hey guys
Been having a problem with my phone.
I have just bought a magic from someone off craigslist and it was rooted with the hero rom installed on it. I was using the phone till I got home. Once I was home I did a factory reset on the phone because the guy who sold it to me still had some information on it such as contacts and applications that i didn't want so I performed a factory reset from within the settings of the phone. Now here is the problem. After the factory reset the phone doesn't load into the OS anymore. I turn it on and the rogers logo shows up for a few seconds then the HTC magic logo comes up for a few seconds after that the hero logo comes up with the android robot animation. After the hero animation the screen goes black but the backlight is still on and the hero screen comes up again and it would go through the animation and the screen would go black again. It would keep looping this hero screen over and over again. I left the phone on for like 10 mins thinking maybe it takes a few mins to load the OS and stuff but I don't think that is the case.
I am not really sure which version of magic this is. Just from looking at it, it is an HTC branded magic. No carrier logo just HTC on the front and on the back. When I go into the fastboot screen it reads
SAPPHIRE UNKNOWN 32B SHIP S-OFF H
HBOOT-1.33.0009 (SAP50000)
CPLD-11
RADIO-3.22.20.17
May 8 2009,21:02:32
The top part says it is an 32B board the 192MB version but the rest of the info underneath it is like the 288MB version one.
How come mine says UNKNOWN and not PVT like everyone else?
Please any insight on this would be very much appreciated. So sad just got the phone and didn't even get to play with it yet.
Thanks!

Try this: http://forum.xda-developers.com/showthread.php?t=523680

did this sort it?
I had the same problem and really did panick!
The way i got around it was to install engineering hspl, Flash recovery 1.1RA-H boot that same recovery then flash the update wipe data.

I haven't gotten around to trying it out yet. I'll take a look at this when I get home. Is this method good for the 32A and 32B boards? I can't determine if mine is the 32A or 32B board. I wanna make sure which board I am working with before I flash and update. Anyone help me out?

I found on the memory card some nandroid files. Is it possible to use the lastest backup to do a restore on the phone to get rid of the looping the hero screen problem?

You might find the wiki useful. It sounds like you've installed a rom that's not meant for your hardware.
See the link to the Sapphire Hacking Wiki in my sig below.

bonesy said:
did this sort it?
I had the same problem and really did panick!
The way i got around it was to install engineering hspl, Flash recovery 1.1RA-H boot that same recovery then flash the update wipe data.
Click to expand...
Click to collapse
Oh eeks! Please don't flash that recovery image - you'll screw your phone up good - the -H recovery roms are for PVT32A (HTC Branded devices) and you have a PVT32B (Google Branded) so you'll want the RA-1.1.2-G recovery rom.
Read the wiki - it explains all this and that's why I wrote it!!!

thanks i'll have a look

still no dice guys
I am not able to flash the phone with the recovery file. I can't install the USB drivers to use ADB. I tried manually installing the driver from the SDK files from the usb driver folder but it wouldn't let me. I read the wiki that Radix999 suggested. The part about Installing the drivers and SDK utilities you need to connect your PC to your phone. I followed that till it asked me to enable debugging mode on the phone. I cannot put the phone into debugging mode because i cannot turn on the phone to get into the OS. I also tried to edit the driver's .ini file too but still can't install this usb driver.
any solutions guys?

I read somewhere that someone said something bout replacing an update file on the phone's memory card so you can erase and update again. Will this be able to help me with my problem? Can I recover without using a computer?
sorry for all the questions but I am a total newbie at this. I just bought the phone used it for like 2 hrs and did a factory reset and now the phone doesnt work.

Hi 2long,
From your fastboot info, it looks like you have the same phone as I do. Is yours a white HTC Magic with HTC on the back cover?
{
"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 haven't rooted my phone yet but I have been reading lots to see what I have here. I'm not convinced 100% that it is a 32B.
I tested booted the recovery-RAv1.1.2G.img, which was listed as being the recovery image for the 32B phones but it didn't work. When I tested it (fastboot boot recovery-RAv1.1.2G.img), the phone would hang on the "Rogers" logo (the first thing to come on the screen).
I then test booted the recovery-RAv1.1.2H.img for the 32A phone but using (fastboot boot recovery-RAv1.1.2H.img) and I got in. I performed the Nandroid backup 2.1.1 and left it at that. I still haven't flashed this image onto the phone yet, but it seems that this is the one that you should be using if your phone is indeed like mine.
BTW, do you happen to live in the GTA? Just curious as I am wondering where my phone came from and if there are more floating around.
Marc

Hey Marc I have exactly the same phone as yours! I am also located in Toronto too. I bought my phone from a guy off craigslist who lives in Brampton but meet up with him at the Rogers center. Hmm from what you are saying sounds very interesting. I haven't got that far into fixing my phone been reading up more info before I take the plunge, don't want to make it worse and not being able to boot into fastboot. I'll keep that info in mind i am going to flash the recovery rom now hope it fixes the rebooting issue

2long said:
Hey Marc I have exactly the same phone as yours! I am also located in Toronto too. I bought my phone from a guy off craigslist who lives in Brampton but meet up with him at the Rogers center. Hmm from what you are saying sounds very interesting. I haven't got that far into fixing my phone been reading up more info before I take the plunge, don't want to make it worse and not being able to boot into fastboot. I'll keep that info in mind i am going to flash the recovery rom now hope it fixes the rebooting issue
Click to expand...
Click to collapse
I had the same problem with yours.I just flash and solved this problem.I did factory reset after that it can't pass hero screen.

I had the same problem as yours. The reason is that I was using 32B rom on 32A Magic (Rogers Magic - HTC Branded). As everyone is saying just wipe the data and reflash your phone and you will be fine.

I have been trying to flash my ROM all day now. I keep getting messages in the command prompt about cannot load recovery.img when i type in "fastboot boot recovery.img", cannot load boot.img from typing in "fastboot flash boot boot.img" whats the deal with that?
I am pretty sure the computer detects my phone tho cause when i type in "adb devices" it returns with the serial number of the phone. I type in "adb root" it says it adab is already running as root, I type in fastboot devices it comes up with the serial number too.
how do i wipe the data? My phones doesn't turn on tho.
what am i doing wrong guys? So frustrating haha

oh wow i finally managed to get the fastboot boot recovery-rav1.1.2.g.img to work!!!
I am getting the same problem as glhturbo did. I tried booting with the rav1.1.2g.img and it hanged at the rogers logo. I tried it with the rav1.1.2h.img and i got into the htc android system recovery utility screen. hmmm i am scared to continue now, as i was told and the phone also says it is a 32b version but the 32a version seems to work on it. What would happen if i flash it to the rav1.1.2h? What should i do now?

You can't restore nandroid backups without a modded or engeneering SPL.
To use fasboot commands you have to have the phone in fastboot mode. If you boot the recovery image fastboot commands will not work. So.
adb commands work in recovery mode or normal mode (when booted properly)
fastboot commands work when phone is in fastboot mode.
If you have a nandroid backup on your sdcard, then just boot the Amon RA recovery image by putting the phone in fastboot mode, and write fastboot boot recovery-RAv1.1.2H.img (if you haven't set your PATH, then copy the recovery image to the tools folder in the android-sdk folder and run the command from there) then restore the backup or flash a new update.zip which is on the sdcard.

ahhhh finally fix my phone. It turns out that it is not a 32b board cause when i flashed the ROM to ones made for 32b boards it would just hang at the rogers splash screen. I went over to HOFO and loaded one of there Rogers ION firmwares and it works flawless now. Thanks for all who helped out!!

Sorry for the necrobump, but I'm having the EXACT same issue you guys did (and I'm in Burlington... fancy that!).
2long, what guide did you follow to get it recovered? Also, now that Eclare is out, is there a way to put it on the Magic instead of Hero?
I'm really in a hurry to get this fixed... this happened once before to me but I thought I fixed it by redoing the Hero flash right And now I'm without a phone!

[Q] lost password / New SD Card

Ok so my brother bought this I believe to be an Inspire 4g from someone on Craigslist, he said she showed it to him and everything was fine.
When he got it home the password screen was on and he couldnt get into it.
I had him try removing the battery and then going into the HBOOT screen and doing factory restore, when this happens it vibrates once then 7 times really quick and stays on the HTC screen. I checked and he doesn't have the SD Card that came with the phone. I gave him one of mine that was formatted to fat32, then when he booted it there is a couple folders on it from the phone but still unable to set it back to defaults. Would I be able to put a factory image on the SD Card and do a restore? If so where can I find a factory image? I don't belive this phone has been rooted yet so it would have to be a AT&T image. Someone please advise, also before you say email her for the password, she wont respond idk if she did this on purpose or what.

Search for the stock ruu, version 1.80 and try running that if you don't want to root.
Sent from my Inspire 4G using Tapatalk

I dont mind rooting it but as far as using RUU none of them will recognize phone because the settings are for USB to be charge only and I cannot get past the pin code screen to change it.
Is it possible to get a stock image, put it on the SD card and change it like that?
Or how can I root it without access to install anything on it?

Can you get it into HBOOT? You can install a stock ROM as a PD98IMG.zip, but you need to be able to get into HBOOT. Try pulling the battery for a few minutes, then hold VOL-UP and hit POWER to get to HBOOT.
Try here for the image file:
http://forum.xda-developers.com/showthread.php?t=952224
Near the bottom: "STOCK ROM IN ZIP FORMAT"

I can get it to this screen
(not my image but similar)
{
"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 just put the whole zip on the SD card?

jjackson81281 said:
I can get it to this screen
(not my image but similar)
I just put the whole zip on the SD card?
Click to expand...
Click to collapse
Yes put the whole zip in the SD card. Do not unzip it. Boot into that screen and it'll ask you if youwant to apply the file just say yes
No Hay de Queso No Mas de Papa

awesome, ill give it a shot after work this evening. Thanks!!

no dice, it went through the process (failed first time on user data so i ran it again and it was successful) then it said push power button to reboot, it vibrates 7 times then stays on the screen that just says HTC, eventually i removed the battery and powered up to find the stupid password screen still there, tried doing factory reset again and same thing 7 vibrations and htc screen indefinitly. Any other ideas or image files i could try???

If it is worth anything to know
ACE PVT SHIP S-ON RL
HBOOT-0.85.0019
MICROP-0483
RADIO-26.06.04.06_M
eMMC-boot
Dec 27 2010,14:47:30

The pd98img file should have wiped everything, not sure how the password remained.
Idk maybe try the file again, thirds time the charm.
The only other file I can think of is the gingerbread ruu leak
No Hay de Queso No Mas de Papa

will that work even though I'm not rooted?

Its completely stock, so your fine. Its the update that inspires are suppose to get anyday now. I just have to figure out how to pullthe pd98img zip from the ruu.
I think it puts it in a temp folder somewhere when you run the ruu. Hopefully I can find it, or someone already has it pulled for you
No Hay de Queso No Mas de Papa

so the RUU worked except now when I boot it up .... SAME THING! still asking for password. Same background, nothing has changed!

i ran the ruu again and it says it still has the old version on it wtf?

ok im stumped!!!
you ran the gingerbread RUU?
ive seen this one other time where running the PD98img files said it flashed but it still said the old one. Unfortunately we never got an answer to that

Yea the one on HTC's site fr e the desire failed but the one here worked
http://driphter.com/index.php?topic=3872.0
but once it completed and tries to reboot the phone it vibrates seven times and freezes on the HTC screen again.
I manually remove battery to reboot and back to square one.
Ive tried it both with sd card in and out.
marsdta said:
ok im stumped!!!
you ran the gingerbread RUU?
ive seen this one other time where running the PD98img files said it flashed but it still said the old one. Unfortunately we never got an answer to that
Click to expand...
Click to collapse

EDIT- heres is the link to the gingerbread PD98IMG
http://www.multiupload.com/P13PZJ2JBN
try this one, and see if this one works

same deal, update complete, press power to reboot. Vibrate once, HTC screen vibrates 7 times and freezes. Remove battery, battery in, power on, same password screen it boots to.
I hate to tell my brother he got ripped off but it is starting to look that way.

Can you upload some sort of video of you trying to go through the process, for us to see if you are making any errors?
Sent from my HTC Desire HD using XDA Premium App

No best I can do is walk through word for word, I'm not new to this by any means I've had a fuse and a tilt 2 that I've unlocked and put custom ROM's on, as well as jailbreaking an Iphone.
So here is what is going on.
Ive done this step with and without SD card in.
1) Removed battery
2) Placed battery back in
3)held down vol, and power until the HBOOT screen comes on.
My options are recovery, factory reset, sim lock, crc img or whatever
4) Vol down to Factory Reset
5) phone reboots with a vibrate like normal, then vibrates 7 times and stays on the HTC screen (white with green letters) until either phone dies or I remove battery.
6) reboot it hoping the factory reset took and no back to the lock screen
-----------------------------------
Didnt work that way lets try putting either the factory image or the updated gingerbread version on!
1) Download the PD98img.zip file
2) put Micro SD card in laptop and format to FAT32
3) move PD98IMG.zip file to the freshly formatted Micro SD Card
4) Remove battery from Phone
5) Put Micro SD card in phone
6) Put Battery in phone
7) Hold down Vol Down and Power Buttons
8) HBOOT Screen appears then checks for PD98IMG.IMG, .nbh, .zip
9) Hboot checks PD98IMG.zip
10) This will update blah blha continue press Vol Up for yes
11) Now with the Gingerbread update it was successful every time, with the factory image it would fail then work the next time.
12) Update Complete press Power to reboot
13) PRess Power
14) reboots, vibrates, HTC screen, Vibrates 7 times and freezes
15) remove battery
16) boot it back up
17) Lock Screen again with this awful goddamn red wallpaper!!

[Q] i9023 bricked. Secure: on (S-ON), radio XXXXX

The last week I have been struggling to unbrick my i9023 Nexus S. Without any luck... Let's start at the beginning, how I bricked my Nexus S. If you don't think this is relevant you can skip it.
Stay with me because it's going to be a long thread...
How I bricked my Nexus S
I was running a CM9 Nightly (from around 10 March) until a week ago, together with the matrix CFS 18.0 kernel. I had a problem with rebooting. Every time I rebooted, it would take 2 or 3 tries before it actually started. First it would just reboot again, or even freeze. So after almost a month I was kinda tired of that problem, so I decided to flash a new CM9 Nightly, the one from 7 April. I flashed the Nightly like I always do, wipe cache/dalvik, and I also flashed the new matrix CFS 18.5 kernel, + the latest gapps and the reloadedICS mod. It was working fine. I rebooted a couple of times more into recovery because I wasn't happy with the reloadedICS mod. Everything was still working fine.
The battery was draining very quickly though. I was watching TV for an hour and when I decided to go to bed the battery was already dead. So I put it in the charger because I wanted to check my facebook before I went to bed. It booted fine, but when I started loading facebook in the browser, my phone freezed. I wasn't really alarmed because, well, let's face it, that's the risk with nightlies. So I pulled out the battery, something I have done a lot of times since I started rooting/flashing. After that: dead. No reaction. No charging icon when it was plugged in the charger. No vibration when I pressed the power button, nothing. A brick...
What I've tried
Although it is uncommon, I wasn't the first to brick a Nexus S. Apparently it had something to do with updating to ICS 4.0.4, on which the april 7 nightly was based on I guess.
Luckily there was AdamOutler's Unbrickable Resurrector. After some setbacks I managed to get the Resurrector working. And against all odds I "unbricked" my Nexus S on the first try! Well, I got it into download mode (home and search button). The only problem was that I still didn't have a screen. The home and search button were lit up, but the screen was still black... And according to most people, it isn't supposed to be black...
Ignoring that fact, I downloaded fastboot and tried to flash bootloader.img, as instructed. It didn't work because my bootloader wasn't unlocked, something that struck me as very weird because it definitely was unlocked before the brick. So I tried to unlock the bootloader. But for that, you need a screen... With a lot of luck I managed to unlock the bootloader. Don't ask me how, but after a few tries I succeeded.
I was making progress. And I was happy about that . So I tried to flash the bootloader again. But it still didn't work. "Write failed". After some internet research I found out wat the problem was. It had something to do with the bootloader and radio being a different version. I used the command "fastboot getvar all" and it told me the following:
- Bootloader version: i9020XXKA3
- Radio version: i9020XXXXX
Apparently the radio version isn't supposed to be XXXXX, and that's why I couldn't flash bootloader.img or radio.img. Also, this is the reason that I couldn't boot my device in the first place.
Obviously I wasn't the only person with this problem. I found a guy that had the same problem as me. He used the command "fastboot boot recovery3101.img", using an older version of CWM recovery. If you used that command, your phone would always boot into recovery, so that you can flash a new OTA.
So I downloaded that older version of CWM, and I tried the same command. And it worked! The home and search button were off and the menu and back button were on! But, still no screen. And the guy that used the same command did have a screen...
I had no clue on what to do next, so I pressed the power button, in the hope that I could boot my device directly into recovery after that. I pressed the power button, the backlight of the soft keys went out... and that was my poor Nexus S' last breath of life...
I tried the resurrector tool after that... "failed to write"...
So, am I really f***ed?
I just can't comprehend that my Nexus S could be dead forever... The hardware is fine, it's just the software that keeps it from booting up! The idea of that is crazy... Certainly with a Nexus S for christ's sake!
So, what am I to do? I kinda gave up hope...
UPDATE: SITUATION ATM
1) With AdamOutler's Unbrickable Resurrector I can get into download mode. Sometimes it doesn't work but when I pull out the battery it works again.
Now I can flash every partition with fastboot, except for;
- the bootloader (which is XXKA3)
- the radio (which is XXXXX)
The probable cause for this is the fact that "secure: on", according to "fastboot getvar all". This is very weird because no one on the internet has a Nexus S with "secure: on". It is some security for i.a. HTC devices.
When flashing the bootloader or radio, I get the following error:
sending 'bootloader/radio' <file size>...
OKAY [time]
writing 'bootloader/radio'...
FAILED <remote: Write Fail>
finished. total time: time
Click to expand...
Click to collapse
Using "fastboot -w update image-******.zip":
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
After that the flash goes fine. When it reboots, my phone is dead again. This is because the radio didn't change with this zip. If there would be a radio in that zip, it would not have worked anyway.
The radio is booted first in android, and because of this I can't do anything (the XXXXX version is wrong). This is probably also why the recovery doesn't work properly (see below). And the "secure: on" prevents me from flashing another radio.
2) With "fastboot boot recovery.img" I can get in the recovery mode. ADB "shell" works, and so does "push" and "pull". The screen is black, though. Even with a very strong flashlight I still can't see anything. I can only see 2 or 3 lines (it is different with each recovery). When I press the volume buttons to scroll, I see no changes at all on my screen.
What I have tried in recovery:
- Installing an OTA zip. I can ADB "push" an OTA zip. I have checked that with ADB "shell". Since I can't see anything I have to guide myself using pictures from CWM menus. But nothing happens. There is no sign that the install worked. The only sign that I'm actually in recovery is that the menu and back softkey are lit up, and that when I press the power button without pressing the volume buttons first, my phone powers off (this is because "reboot system now" is on top of the list in recovery, I guess).
- ADB pushing anything on /sdcard. When I turn off my phone after that and resurrect it again, the file is gone. This could be because my memory is dead. But isn't this because the resurrector removes it? Anyway, when I push a file with ADB, it definitely is on my sdcard. Only after rebooting and resurrecting it isn't...
NOTE: Rebooting/booting in whatever mode doesn't work. The only two things I can do are listed above. The moment I plug out my device, I have to use the resurrector again. Because of this there it makes no sense to flash a recovery, since I can't boot anyway. The only way I can get into recovery is by using "fastboot boot recovery.img".
NOTE 2: Recovery.log shows some errors. I will post the whole log soon...
Possible solutions?
A) How can I flash a different radio, despite of "secure: on"?
B) Can we change "secure: on" to "secure: off"? For HTC users this is as normal as "fastboot oem unlock", but there is no one on the internet that has a Nexus S with "secure: on".

I've never really saw a Nexus S totally bricked by software. It's often a combo of small user errors and small software bugs.
There is a bug with the SLCD version of the Nexus S where the backlight doesn't come on and thus it looks like it doesn't work but the softkeys light up. However, if you take a flashlight to the screen and look at an angle, you will see what's being displayed.
Also, you do not need to use an old version of CWM specifically.
Are you able to hold vol + and power to get into bootloader? If not, pull the battery out for at least 10 minutes, then put it back in and try again.

polobunny said:
I've never really saw a Nexus S totally bricked by software. It's often a combo of small user errors and small software bugs.
There is a bug with the SLCD version of the Nexus S where the backlight doesn't come on and thus it looks like it doesn't work but the softkeys light up. However, if you take a flashlight to the screen and look at an angle, you will see what's being displayed.
Also, you do not need to use an old version of CWM specifically.
Are you able to hold vol + and power to get into bootloader? If not, pull the battery out for at least 10 minutes, then put it back in and try again.
Click to expand...
Click to collapse
I know about that bug where the backlight doesn't work, and that's how I managed to unlock the bootloader eventually.
My phone is as dead as a brick. The resurrector doesn't work anymore, so I can't get into bootloader. I can't get into download mode, I can't get into anything.
I know you don't really need to use an old version of CWM, but it got me into recovery. Unfortunately, after I shut down my device, I can't do anything anymore... I guess the resurrector doesn't work because recovery is now on the boot partition?

Androyed said:
I know about that bug where the backlight doesn't work, and that's how I managed to unlock the bootloader eventually.
My phone is as dead as a brick. The resurrector doesn't work anymore, so I can't get into bootloader. I can't get into download mode, I can't get into anything.
I know you don't really need to use an old version of CWM, but it got me into recovery. Unfortunately, after I shut down my device, I can't do anything anymore... I guess the resurrector doesn't work because recovery is now on the boot partition?
Click to expand...
Click to collapse
If the phone doesn't even power on AT ALL (not even a split second) when you press the power button i'd look into a hardware problem more than a software problem. You can get into the bootload using VOL+ and power usually, not only using the ressurector.

polobunny said:
If the phone doesn't even power on AT ALL (not even a split second) when you press the power button i'd look into a hardware problem more than a software problem. You can get into the bootload using VOL+ and power usually, not only using the ressurector.
Click to expand...
Click to collapse
Well, than that hardware problem occured when I pulled out the battery after my screen freezed...
But if it really is a hardware problem, isn't it strange that I was able to get it into download mode, and that I got it to communicate with my computer using fastboot? I even got it into recovery mode for a brief moment!

Androyed said:
Well, than that hardware problem occured when I pulled out the battery after my screen freezed...
But if it really is a hardware problem, isn't it strange that I was able to get it into download mode, and that I got it to communicate with my computer using fastboot? I even got it into recovery mode for a brief moment!
Click to expand...
Click to collapse
It is very weird indeed. If I had to pick something hardware related, I'd say your battery died. Just a guts feeling, and it goes with the quick discharge scenario...

polobunny said:
It is very weird indeed. If I had to pick something hardware related, I'd say your battery died. Just a guts feeling, and it goes with the quick discharge scenario...
Click to expand...
Click to collapse
I have used other batteries (luckily I have friends with a Nexus S), but that doesn't change anything.
The big question is, how can I get into download mode again? The resurrector worked at first, but when I flashed CWM to the boot partition and rebooted after that, I can't get any signs of life out of my Nexus S. Resurrector doesn't work anymore, nothing...
The weird thing is, the moment I used the "fastboot boot recovery.img" command, windows stopped recognising the device. But according to the soft keys, it did go from download mode into recovery mode. I still didn't see anything, but I guess that's because the SLCD bug.
I guess I should not have had rebooted when I was finally in recovery...

Hmmm... someone might have an idea. I still find it extremely strange it doesn't power on at all. Were you aware of any power button problem with your Nexus? Had to double click the power button to wake it?

polobunny said:
Hmmm... someone might have an idea. I still find it extremely strange it doesn't power on at all. Were you aware of any power button problem with your Nexus? Had to double click the power button to wake it?
Click to expand...
Click to collapse
Nope, no problem at all.
The only way I could get some life out of it, was by using the resurrector tool. But now even that isn't possible anymore...
Is it actually possible to really perma-brick a Nexus S? Or are people just saying that because they lack the knowledge to unbrick it. I'm pretty sure it can't be a hardware problem. It is the software that is preventing it to boot up. That's what a brick is, right?

WOW, GOOD NEWS!
After a few (totally random) tries, I managed to resurrect my phone again! I am now in the download mode. From here I can use fastboot boot recovery.img. I still don't have a screen though...
When I get into recovery (without screen), what should I do then? Because previous time, windows stopped recognizing my phone... Should I push an OTA to my Nexus S BEFORE I use fastboot boot recovery.img? And if so, how? And if I do so, how on earth am I going to manage to install that zip without a screen? There are a lot of files on my sd card... An option would be to wipe them all, if that's possible. Another option would be to give it something starting with a 1 or an A so that it comes up on top of the list.

The problem is that I can't flash anything because of that i9020XXXXX radio version.... Is there any way I can flash another radio? Just flashing with fastboot doesn't work because of that XXXXX version...

Got it into recovery again! Windows recognized USB mass storage for a second, but not anymore.
Using a flashlight I can see that there is SOMETHING on the screen, but when I press the volume buttons to scroll nothing changes...

Another breakthrough! I installed ADB drivers, and now I got ADB working!
Can you control CWM recovery from the computer, using ADB? Because now all I have to do is flash an OTA, but I can't see anything, not even with a flashlight...

I'm not real good at the technical stuff, but it seems like you should be able to put one of the ota's on your computer and when you connect the phone, it should take you through a flash sequence. Hopefully someone above my pay grade will jump in here and help.
Hang in there, we're all pulling for you.

wmdunn said:
I'm not real good at the technical stuff, but it seems like you should be able to put one of the ota's on your computer and when you connect the phone, it should take you through a flash sequence. Hopefully someone above my pay grade will jump in here and help.
Hang in there, we're all pulling for you.
Click to expand...
Click to collapse
I'm not really good at the technical stuff either. I'm like this dog:
{
"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"
}
But I can learn quickly. I know how to push a file to the SD Card using ADB. I also now how to wipe all user data using fastboot. Combining that, I have a SD Card with only 1 file: the OTA I want to flash. That should make thinks a lot easier since I can't see a damn on my screen.
My problem wouldn't even that bad, if it weren't three problems combined. Normally when people unbrick their phone with the resurrector, they can flash a bootloader.img. But I can't, because of that i9020XXXXX baseband version. I tried to flash another radio.img but that doesn't work either. To top this off, my screen doesn't work. Even with a flashlight I only see that there's SOMETHING on the screen, but I don't see any changes when I press the volume buttons for example.
The problem with not seeing anything is that I don't know if what I did, worked. I can't confirm anything. Maybe when I flash the OTA it says: update failed. But I can't see that so how would I know?
That's why I was hoping for a way to not only push files to the SD Card using ADB and wipe all user data using fastboot, but also for a way to install zip from SD Card using ADB/fastboot.

Could this be a corrupt radio? There was a thread about the 4g radio that delves a little into what the radio actually does. I'll find it when I'm back home. Try flashing a radio through cwm if you can manage.

Harbb said:
Could this be a corrupt radio? There was a thread about the 4g radio that delves a little into what the radio actually does. I'll find it when I'm back home. Try flashing a radio through cwm if you can manage.
Click to expand...
Click to collapse
You think that would work? Because I can't flash via fastboot...
Anyway, it is worth a shot. I've tried flashing several OTAs through several recoveries without much luck, but at least now I have the knowledge to go back to where I was (download mode/recovery).
I don't know anything about radios, but the XXXXX baseband version isn't good, at least that's what people say. It prevents you from flashing a bootloader.img, and also from flashing another radio.img. And maybe it was the reason that my Nexus S bricked in the first place.
By the way, thank you all for your help!

[Q] i9023 very freaking bricked, lost all hope...
Pls help i am also facing same problem i have given NS to service center they said they will be changing its mother board is there any thing can b done.

Androyed said:
You think that would work? Because I can't flash via fastboot...
Anyway, it is worth a shot. I've tried flashing several OTAs through several recoveries without much luck, but at least now I have the knowledge to go back to where I was (download mode/recovery).
I don't know anything about radios, but the XXXXX baseband version isn't good, at least that's what people say. It prevents you from flashing a bootloader.img, and also from flashing another radio.img. And maybe it was the reason that my Nexus S bricked in the first place.
By the way, thank you all for your help!
Click to expand...
Click to collapse
Try installing factory images from fastboot, You dont need the screen for that just get it to download mode.
http://forum.xda-developers.com/showthread.php?t=1572307

in cmd it says waiting for device and nothing happened its blank

[Q] Help required... can not root my phone or unlock Bootloaders

hi everyone,
well i can not unlock my bootloaders with Hasoon2000's toolkit...
I have had the gray status saying "Tampered" but bootloaders are still locked... every solution is either linix based or via fastboot/adb... i m not good with the cmd stuff as yet...
Can anyone please put me in right direction please... i have found some solutions that says "1st my phone has to be rooted" its hard for me to understand, how can i root my phone if i have bootloaders locked!?
my build number is 3.18.502.6 and android version is 4.1.1 i have just motochoper done on my phone... and unable to go further to unlock bootloaders, root and flash recovery, any help in this regard will be appreciated or i will be selling my phone very soon...
p.s. i have done all the above mentioned on my previous htc phone i.e. one x plus (that was s-off) but this one is not thus giving me a hard time!
p.s.s. when i tried to get the unlock token for my device adb always stuck at (waiting for device) and wont go further (so i cud copy paste token numbers to get htc token in my email)...

Aren't you afraid of running exploits on your phone without knowing what they're doing to it? You should be.
AT&T Phones cannot unlock the bootloader through HTCDEV. As per AT&Ts request, HTCDEV checks your Carrier ID to see what carrier your phone is from and then denies or provides an unlock code accordingly.
To get around this, the exploit provides your phone with temporary root access allowing you to write a new CID and changes it to SuperCID (11111111 or 22222222) which makes HTCDEV think your phone is not in fact from AT&T.
Since your phone says tampered, this part has been successful. You no longer need root access and root was only temporary.
Now your phone has SuperCID and can be unlocked from HTCDEV but something is interfering with the driver that allows communication to your phone via ADB/Fastboot. So, to troubleshoot this: Requirements for ADB to work:
Your phone must be loaded into the ROM and connected to the PC
Your phone must have USB Debugging enabled
You must not have HTC Software Or any other phone software running.
If you already meet these requirements. Hard reboot your phone by pressing and holding power until the phone shuts off and then turn it back on and reboot your PC and then try again.
If that doesn't work, uninstall any and all phone software. Uninstall the HTC Drivers. Reboot your PC, Hard reboot your phone, reinstall the HTC drivers but not the HTC Sync software and try again.
Lastly, all this information is available within this forum through the stickies and it is my personal opinion that you have not read and understood what you were doing prior to starting. Normally I would not help someone in your situation. Please note that your approach is quite dangerous.

Very well explained @exad......:thumbup: and @Mortal Eternity .....please post your four lines under tampered text of your bootloader .....power off ur phone and then press this combo button (Vol down+power menu) and let go only power menu button when u see htc white screen while still holding vol down button........this would bring u into bootloader.
Swyped from BlueICESense_JBE

exad said:
Aren't you afraid of running exploits on your phone without knowing what they're doing to it? You should be.
AT&T Phones cannot unlock the bootloader through HTCDEV. As per AT&Ts request, HTCDEV checks your Carrier ID to see what carrier your phone is from and then denies or provides an unlock code accordingly.
To get around this, the exploit provides your phone with temporary root access allowing you to write a new CID and changes it to SuperCID (11111111 or 22222222) which makes HTCDEV think your phone is not in fact from AT&T.
Since your phone says tampered, this part has been successful. You no longer need root access and root was only temporary.
Now your phone has SuperCID and can be unlocked from HTCDEV but something is interfering with the driver that allows communication to your phone via ADB/Fastboot. So, to troubleshoot this: Requirements for ADB to work:
Your phone must be loaded into the ROM and connected to the PC
Your phone must have USB Debugging enabled
You must not have HTC Software Or any other phone software running.
If you already meet these requirements. Hard reboot your phone by pressing and holding power until the phone shuts off and then turn it back on and reboot your PC and then try again.
If that doesn't work, uninstall any and all phone software. Uninstall the HTC Drivers. Reboot your PC, Hard reboot your phone, reinstall the HTC drivers but not the HTC Sync software and try again.
Lastly, all this information is available within this forum through the stickies and it is my personal opinion that you have not read and understood what you were doing prior to starting. Normally I would not help someone in your situation. Please note that your approach is quite dangerous.
Click to expand...
Click to collapse
Never thought HTC Sync, Samsung Kies and Sony pc companion could be blocking adb access, i m uninstalling them all.... about running the exploits... i have just run the motochopper script bro and i knew that it was meant to be flashed to achieve cid for my version... there is that Xfactor xploit for 2.20 build number...
Thanks for the info bro... i didnt knew that AT&T instructed htc to cover up for them and making their phones more carrier specific...
about not helping part... well you should help bro... we noobs really appreciate and give honor and respect that you share wisdom and next time you will find me helping others with that info you gave me!

ted77usa said:
Very well explained @exad......:thumbup: and @Mortal Eternity .....please post your four lines under tampered text of your bootloader .....power off ur phone and then press this combo button (Vol down+power menu) and let go only power menu button when u see htc white screen while still holding vol down button........this would bring u into bootloader.
Swyped from BlueICESense_JBE
Click to expand...
Click to collapse
here it is bro...
{
"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"
}
and here is where i m stuck.... when i press (get token id) my phone boots in bootloader and leave me with this window... saying waiting for the device...

Sometimes the unlock token can take multiple attempts to work, you can try forcing a reboot back to bootloader by holding volume down and power and trying the token again. Keep trying until it succeeds.
Sent from my Evita

timmaaa said:
Sometimes the unlock token can take multiple attempts to work, you can try forcing a reboot back to bootloader by holding volume down and power and trying the token again. Keep trying until it succeeds.
Sent from my Evita
Click to expand...
Click to collapse
i kept on trying... even have done 20+ tries in a row but results stays the same... phone boot into bootloaders and then just stays in above pictures waiting for device thats it

Mortal Eternity said:
i kept on trying... even have done 20+ tries in a row but results stays the same... phone boot into bootloaders and then just stays in above pictures waiting for device thats it
Click to expand...
Click to collapse
You can try another PC or a virtual machine.
It's definitely driver interference but narrowing it down could take forever.

exad said:
You can try another PC or a virtual machine.
It's definitely driver interference but narrowing it down could take forever.
Click to expand...
Click to collapse
i have 2 pcs at home.. will try one which is in office tomorrow and report back... Thanks for all your time and suggestions!
whats a virtual machine though!? :/ r you referring to teamviewer and vpn services!?

A virtual machine is an os that runs inside another os.
Sent from my One Xl using xda app-developers app

exad said:
A virtual machine is an os that runs inside another os.
Sent from my One Xl using xda app-developers app
Click to expand...
Click to collapse
Bro... i have finally rooted my phone :victory: (from my office pc lolz) there was a problem with drivers on my home desktup and usb device recolonization error was poping up on my laptop... :silly:
Thanks for all your suggestions and information it has been very helpful of you! :angel:
Thanks again and best regards,
Mortal Eternity!

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