Database Users

I think I bricked my nexus (my fault) please help!

Hello all,
I think I may have bricked my nexus one. It is completely my fault for attempting things that I knew little about, so flame away But after the flaming, if anyone is willing to help I would be sooooo thankfull...
I successfully rooted my phone following the instructions on this page: (all links edited with a double asterisk as I don't believe I can post links)
h**p://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Then successfully installed cyanogenmod (which is awesome!) following this page:
h**p://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
All was well, I even got the modaco desire rom up and running, and was happily switching back and forth using the recovery screen. I had nand backups for specific setups, etc.
Then I decided it would be good to know how to go back to stock, and found this page:
h**p://**w.androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
I followed the instructions to the letter (I think) except for erasing userdata (it said "failed: remote not allowed"). I thought that things would be ok, since I'd recently wiped, so I followed the page till the end.
The phone rebooted, and I got the original nexus boot animation - but it's in an endless loop! What's worse, it that now when I try to go to the bootloader or recovery mode, I get the exclamation triangle with the little android.
Is there any way through a command prompt (or other method) that I can fix this? I tried to re-flash the RA recovery image through the command prompt, but the response was, "waiting for device."
ANYTHING that anyone can suggest to help, I would be so thankful! I've been loving the nexus, and hate to think that I crippled it
Thanks in advance,
Randy

I doubt its bricked.
Noticed you didnt mention that fast boot doesnt work? (power button+trackball) try it.
Once you get to fastboot you can flash any ROM back. (fastboot flash **** commands from a command shell)

Did you ever perform a Nand Backup from Recovery?

It's not bricked, the only way to brick is to interrupt power when flashing a Radio image

Connect phone to PC. Open command prompt.
adb reboot recovery
Wipe, reflash.

So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One

nexus5894 said:
So far, nobody has managed to brick a Nexus. There is no way as the fastboot mode can restore the whole phone and can't be messed with. Make sure you have the latest version of the SDK with correct USB drivers and fastboot. Then try and reflash the recovery image.
-------------------------------------
Sent from my Nexus One
Click to expand...
Click to collapse
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404

Paul22000 said:
Actually...
http://forum.xda-developers.com/showpost.php?p=6320068&postcount=404
Click to expand...
Click to collapse
............................

It worked!!!!!
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
​
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!

Randy Malkoski said:
It worked!!
britoso, thank you soooooo much! The only way that I knew to get into bootloader/recovery was via power button/volume down, but power/trackball brought up the bootloader screen, and I clicked on fastboot. I was able to flash the RA recover image through the command terminal via fastboot, then able to get into recovery. I had cyan and modaco sense on the sd, and was able to flash one of them on.
​
I never thought I'd be so happy to see "quietly brilliant"!!! I WILL buy you a beer, a case in fact as soon as money clears my paypal account.
I have learned my lesson, research research research. (I did do some, but not enough to feel comfortable with what I was doing - hence my cry for help!)
Other than the phone and OS itself, the thing I like most about the nexus is the fact that one CAN root, and then customize (sold a Telus moto droid because I could not do that very thing).
I digress... thanks again so much!
And Paul, thanks for your sense ROM; I've had HTC phones from the Touch to the the diamond to the Hero, and missed the UI!
Click to expand...
Click to collapse
Glad to hear it. You learn the most by trial and error.

I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....

revonomics said:
I think i got the same problem. i tried to Unlock Bootloader and Root Google Nexus One which was successful but then i tried to superboot it and when it came to the part where you "double click the ‘install-superboot-windows.bat’ file" i clicked it but it did not go to the nnext screen where the superboot completes it just stayed at the "bootloader screen". i must hve not done something or done something wrong i dont know.
So then i unplugged the phone from the pc and rebooted it. when it reeboted i wasnt getting any network, the phone was slow and the notification bar would not slide down...also i noticed the phone restarting on itself...
/i tried all kinds of "restore to factory settings" but not solved. Can anyone tell me what to do tht will work. I coud not understand what was said in the above thread as i am new to this android n my first time rooting n stuff n i believe that solution would work for me too..if some one could please explain in simple tirms the steps i need to take would be good...
Really appreciate it....
Click to expand...
Click to collapse
Tell me what i need to download again and how to go about it...i really need my phone working again ((((

Calling a do-over (noob)

This is the first phone that I have tried any kind of rooting or flashing or etc. I followed steps where given, but I think something has gone wrong in the process because a lot of the folders that used to be on the SD card are now gone. I need to start from square one, and I'm not exactly sure how to accomplish that. I know this is a very noob-ish question, but I would appreciate the help.

I have to have screwed the pooch pretty bad, I'm caught in a loop at the HTC splash screen and then it reboots. Any helps would be very much appreciated. I know I did something, I just don't know what.

you dont give enough info..i mean what steps did you follow? when did things go wrong? what step was it? what was the last thing you did?
pull the battery and then boot into recovery (hold volume down+hold power)

EVOKeith said:
This is the first phone that I have tried any kind of rooting or flashing or etc. I followed steps where given, but I think something has gone wrong in the process because a lot of the folders that used to be on the SD card are now gone. I need to start from square one, and I'm not exactly sure how to accomplish that. I know this is a very noob-ish question, but I would appreciate the help.
Click to expand...
Click to collapse
Flash the RUU from the "All roms" thread

Everything was fine after the root guide I followed (the idiot-proof one). When I attempted to do the Nand access portion something went wrong because I got an error that the SD card was blank or had an unsupported file system. The only choice I had was to format the SD card.
Now, when I attempt to install a downloaded .zip from recovery it acts like it is going to install but goes right back to the menu after a few seconds. IF I tell it to reboot then I get caught back in the splash screen rebooting over and over again.

do a full wipe and cache wipe, reboot and see if that helps before you go any further. you do that when you boot into recovery. that will likely fix it. If not post what it does then.

What happens:
When I boot into recovery the first bit is that it tried to load PC36IMG.zip, I get the following:
Main version is older!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
I selected No and went into Recovery. I wiped all data and cache and rebooted. Once again the white HTC EVO 4G screen comes up for a few moments and then the phone powers off and restarts with the same screen over and over. I'm at a complete loss.

bumping for help

is that pc36img.zip the rom that you initially flashed that worked or is it a different one that was part of the 'nand access portion'? I figured that would be from an 'update.zip', but I barely know what I'm doing outside of the well detailed guides.
If it isn't the rom you flashed, try loading that rom back on there. I hope you have another device you can read/write micro-sd's from.
If it is the rom you flashed try flashing another rom.
...I'm a noob here too, but I'm on my second rooted/custom recovered phone so I'll help as I can.
Did you make a nandroid backup?

Whelp, it rolled over and died. Going to Sprint tomorrow. Thanks for trying to help guys.

EVOKeith said:
Whelp, it rolled over and died. Going to Sprint tomorrow. Thanks for trying to help guys.
Click to expand...
Click to collapse
Lucky for you that none a single rep I've ever spoken to in any Sprint store has any idea about anything whatsoever. I returned a Samsung Moment that I never bothered to restore to stock...hey turned it on, it booted up with a "Hacksung, XDA developers" screen, proceeded to load up a (then hours old) 2.1 lock screen and said "Okay, it still works", didn't check to see if I had kept the memory card in or even re-packed the charger and gave me a refund for everything on the receipt, even things I didn't have in the bag.
...another time before that I was asking about the Android 2.1 update and when it was being rolled out to which the sales rep stood up, turned around and yelled "Bobbyyy....what's an android and when do we get one in?"
Though I'm sure there is a way to bring your phone back...perhaps check in on the thread where you got your rom and see if anyone else has had such issues, give all the details you can in the order in which they happened.

If you can still get to the hboot screen try the zip posted here using the instructions here

G1 RADIO FLASH HANGS UP “Formatting CACHE…” (2.22.23.02) brick ?

I was rooting a G1 and was flashing the latest radio 2.22.23.02. with RA dream 1.7.0. It went through its paces:
flash-> reboot (home+back)->does it’s own thing -> boots back into recovery screen & then hangs on “formatting cache…” (at bottom of recovery screen)
It hangs up on G1 screen but will go into recovery. I’ve gone back and wiped everything, flashed (radio) from 2 different fresh sd cards, etc, etc…nada
Anything I can do? Un-root it? Re-flash recovery rom?
Thanks P-

if the phone will not boot normally but will go in to recovery, why not wipe it and flash a ROM?

pk2 said:
I was rooting a G1 and was flashing the latest radio 2.22.23.02. with RA dream 1.7.0. It went through its paces:
flash-> reboot (home+back)->does it’s own thing -> boots back into recovery screen & then hangs on “formatting cache…” (at bottom of recovery screen)
It hangs up on G1 screen but will go into recovery. I’ve gone back and wiped everything, flashed (radio) from 2 different fresh sd cards, etc, etc…nada
Anything I can do? Un-root it? Re-flash recovery rom?
Thanks P-
Click to expand...
Click to collapse
The good news is that the radio flashed successfully and you're NOT bricked.
The process goes like this:
From recovery, you SET UP your cache partition to store the radio image and set the misc partition to initiate the flashing process. It then reboots into update-radio mode, flashes the radio, and configures the misc partition to format the cache. It then does that, and theoretically, you're done.
Something screwed up in your format cache. NOT THE END OF THE WORLD!
What you've got to do is STOP flashing the radio! Its already flashed, it will either WORK or NOT WORK. There IS no IN BETWEEN.
Now recovery obviously isn't working for you, so what we need to do is this: Use FASTBOOT. WHAT SPL do you have installed? Is it a 0.95.3000 or a 1.33.2xxx? If it is, then you reboot into fastboot, perform a "fastboot -w system", and then a "fastboot update signed-dream_devphone_userdebug-img-14721.zip" (which you can download from developer.htc.com/adp.html). This will put your phone into a WORKING STOCK ADP1 state (which has root).
The instructions are all on the htc site at that link.
AND FINALLY:
DO NOT EVER UNROOT IT!!!!
You have root now, there is ABSOLUTELY NO reason to EVER "unroot" it. DO NOT EVER (no matter WHAT any RETARD ever says) write an NBH file to the thing.
If you do NOT have a fastboot SPL, then install one first.... I recommend 1.33.2003 which you can find here: http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76

AdrianK said:
if the phone will not boot normally but will go in to recovery, why not wipe it and flash a ROM?
Click to expand...
Click to collapse
Thanks for the reply,
That was my thought, sort of a "Hail Marry pass". but I was afraid to take myself any further to oblivion. The second post seems a little safer.
Thanks again, PK
IBCODER, many, many thanks,
lbcoder said:
Something screwed up in your format cache. NOT THE END OF THE WORLD!
Click to expand...
Click to collapse
Don't leave me!! This was my favorite little g1...a keeper, I've done 6 without a hitch. I need some coffee, shake some fuzz out of my head (morning here), and do some home-work. Will be back soon....
Regards, PK

Thanks very much for the reply,
lbcoder said:
The process goes like this:
From recovery, you SET UP your cache partition to store the radio image and set the misc partition to initiate the flashing process. It then reboots into update-radio mode, flashes the radio, and configures the misc partition to format the cache. It then does that,
Click to expand...
Click to collapse
O.K., that fills in some blanks. And this right here is where I’m stuck eh? Oddly, I can still navigate the RA-dream recovery screen with frozen cache thing.
lbcoder said:
and theoretically, you're done. Something screwed up in your format cache. NOT THE END OF THE WORLD!
Click to expand...
Click to collapse
Thats a relief. I thought I had followed the directions to a “T” (theunlockr.com), this is not my first.
lbcoder said:
What you've got to do is STOP flashing the radio! Its already flashed, it will either WORK or NOT WORK. There IS no IN BETWEEN.
Now recovery obviously isn't working for you, so what we need to do is this: Use FASTBOOT. WHAT SPL do you have installed? Is it a 0.95.3000 or a 1.33.2xxx?
Click to expand...
Click to collapse
As far as the SPL, on the FASTBOOT screen I have an “hroot 1.33.2995”(?). I flashed a generic G1-SPL over the bad radio install (WTF) and may have flashed Danger SPL. I don’t know how to tell if either took.
lbcoder said:
If it is, then you reboot into fastboot, perform a "fastboot -w system", and then a "fastboot update signed-dream_devphone_userdebug-img-14721.zip" (which you can download from developer.htc.com/adp.html). This will put your phone into a WORKING STOCK ADP1 state (which has root).
Click to expand...
Click to collapse
Can this cause any turmoil with Danger-SPL (if I flashed it)? Could either SPL have taken with the radio half installed or in a dubious state and are they a game changer if they did? The FASTBOOT screen idicates the "radio 2.22.23.02" i was trying to install, as if it took(?)
lbcoder said:
The instructions are all on the htc site at that link
AND FINALLY:
DO NOT EVER UNROOT IT!!!!
You have root now, there is ABSOLUTELY NO reason to EVER "unroot" it. DO NOT EVER (no matter WHAT any RETARD ever says) write an NBH file to the thing.
If you do NOT have a fastboot SPL, then install one first.... I recommend 1.33.2003 which you can find here: http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76
Click to expand...
Click to collapse
Thanks for the link, I’ve used adb and a little linux in the past but am new to FASTBOOT. The basics look a little familiar.
If any of my concerns regarding my SPL status, please do. And please elaborate if you can.
Thanks again for the direction.
PK

You're actually looking very good in most regards.
Yes, the radio flash took successfully -- of this there is no doubt. If it didn't, your phone wouldn't even turn on, it would be completely dead.
As for the SPL, you said "hroot 1.33.2995" -- I believe that you mean "hboot 1.33.2005", right? That being the case, you are actually in a VERY strong place! You have a *proper* engineering SPL installed (not the one I would pick, but a good one nevertheless... and yes, it is the infamous deathspl.)
The problem is that the thing is failing to format your cache partition and it is probably not getting to the point of clearing your misc partition.
NO PROBLEM.
In fact, you say that you are able to navigate the recovery despite the format cache failing. This is a VERY good thing! It makes thing a bit easier.
I actually just thought of something....
You say that it just keeps automatically going into recovery when you turn it on.... the SPL is designed to do that in TWO circumstances; 1) When the boot-recovery command is set in the misc partition, (2) When the BOOT partition is empty or corrupt. I assume that (1) doesn't apply since it appears that recovery IS WORKING.... which leaves (2)....
Have you tried to simply flash a ROM to the thing? I mean it. Sounds simple? Yes. Try to JUST FLASH A ROM! Put CM5.0.8's update.zip onto your sdcard and FLASH IT! See what happens. Can't hurt. If it doesn't change anything, then we just need to go back and force clean the misc partition.

Hello Ibcoder,
Thanks a lot for the follow up. I hope this prob. Is still enough of a challenge to keep you interested. Before I take the plunge I just want to clarify a few points: (I’ll guess it doesn’t matter but…):
lbcoder said:
"hroot 1.33.2995" -- I believe that you mean "hboot 1.33.2005", right?
Click to expand...
Click to collapse
Yes, at least this is indicated in the bootloader screen…corrupt or not (the lingering "formatting cache..." when I was flashing the radio).
lbcoder said:
You say that it just keeps automatically going into recovery when you turn it on....
Click to expand...
Click to collapse
Actually it boots into the “G1” screen but just hangs there. However, with the usual button combinations, I can boot into recovery and the bootloader screens, navigate around and execute stuff. Does that still sound like a corrupt partition? does it matter?
lbcoder said:
Have you tried to simply flash a ROM to the thing?
Click to expand...
Click to collapse
Not yet, but if this post doesn’t change anything I’m ready.
Regards and many thanks, PK
BTW:
lbcoder said:
Deathspl…not the one I would pick, but
Click to expand...
Click to collapse
Worth another topic I guess, but what would you use that’s compatible with CM 5.08, CM 6.0 and maybe the embryonic froyos?

pk2 said:
Not yet, but if this post doesn’t change anything I’m ready.
Click to expand...
Click to collapse
Quit stalling and do it already! Nothing important is corrupt -- if it was, it wouldn't do ANYTHING.
You installed an SPL that changed the partition mapping so that the END of the system partition is further ahead, BOTH ends of the cache partition are in different places, and the start of the userdata partition is back further. OF COURSE IT WON'T BOOT!
Worth another topic I guess, but what would you use that’s compatible with CM 5.08, CM 6.0 and maybe the embryonic froyos?
Click to expand...
Click to collapse
ALL SPLs are compatible with ALL ROMs, NO EXCEPTIONS!
This is DESPITE what is claimed by the majority of those who are technically inept.

It worked. CM 5.08
Thank you
Sorry for taking your time. I’ve done lots of roots and rom flashes with out a hitch. I’ve heard though, (after the fact) that if you screw up your radio or SPL flash you have a brick. Got me thinkn', with my symptoms, I might be on my way to one (a brick).
Thanks again much, much for all your trouble,
PK

and as a follow up, i tried flashing the same radio on an HTC T mobile G1 it kinda got stuck on the formatting cache screen too, but I can still access the recovery menu, in fact it got stuck on the recovery menu saying at the bottm "formatting cache" so I decided that I just reboot using the menu screen of the recovery and then it went through the usual booting process and I checked it so there it was the radio was updated, still have not reflashed the rom or anything won't it affect the rom flashing in anyway?

From My experience you should be able to flash your rom (can't be responsible if it bricks).
PK

Flash the Rom. Wont brick it. Same happened to me on 2 different phones. It's ok
Sent from my HTC Magic SparksMod using XDA App

Hello,
I had the same problem. i was aslso stucked in the "formating cache". a normal boot was not pissible.
i rebootet a few times and then the message did not apear anymore.after that i flashed a new rom without problems.
so i have no idea what happened but i am happy that its working.

PTG said:
Hello,
I had the same problem. i was aslso stucked in the "formating cache". a normal boot was not pissible.
i rebootet a few times and then the message did not apear anymore.after that i flashed a new rom without problems.
so i have no idea what happened but i am happy that its working.
Click to expand...
Click to collapse
That's what happened to me to yesterday night after flashing the DangerSPL. Although I was able to access to the recovery image, so all I did was to flash over the room. Hope that will work for u too..

[q] help issue flashing cwm3!phone stuck!

I'm sure there is another post about this but I don't know where it is, have looked, a little, but, just want my specifi ? answered. So, have Epic and went to flash from CWM2.5 to 3. Followed all instructions and 1st time didn't flash right, so, reflashed, again, sidenote, I followed all instructions correctly. Anyways, seemed like everything was fine until it rebooted after switching all to Ex4 and from that point only Samung bootup screen appears and nothing else. In addition, have been unable to do 3 finger startup since the reboot. Help, esn swapped to my POS Hero that's slower than slow until I get some advice. Thanks.
S-

I did the samething when I installed cwm 3. U gotta take ur microsd card out and insert it into a computer using an adapter. From there dl a rom of your choice, place it on the sd card, and then flash with cwm.

smathias503 said:
I'm sure there is another post about this but I don't know where it is, have looked, a little, but, just want my specifi ? answered. So, have Epic and went to flash from CWM2.5 to 3. Followed all instructions and 1st time didn't flash right, so, reflashed, again, sidenote, I followed all instructions correctly. Anyways, seemed like everything was fine until it rebooted after switching all to Ex4 and from that point only Samung bootup screen appears and nothing else. In addition, have been unable to do 3 finger startup since the reboot. Help, esn swapped to my POS Hero that's slower than slow until I get some advice. Thanks.
S-
Click to expand...
Click to collapse
Yeah, it sounds like the rom flash after the ext4 upgrade didn't "take". Try what the previous poster suggested and if that doesn't help, look up the Odin posts on this forum. Even if you can't "3-finger" into some form of recovery - as long as you can put the phone into download mode (holding down the "1" key while you power the phone on), you can use odin with 99% success.
If you have any questions, feel free to PM me and maybe I can try to walk you through it without you getting bashed on here! LOL

cjobanion said:
Yeah, it sounds like the rom flash after the ext4 upgrade didn't "take". Try what the previous poster suggested and if that doesn't help, look up the Odin posts on this forum. Even if you can't "3-finger" into some form of recovery - as long as you can put the phone into download mode (holding down the "1" key while you power the phone on), you can use odin with 99% success.
If you have any questions, feel free to PM me and maybe I can try to walk you through it without you getting bashed on here! LOL
Click to expand...
Click to collapse
He doesn't need odin. The CWM3 flash he did was successful. He just needed to flash an ext4 ROM to get past the Samsung Boot screen.

mattallica76 said:
He doesn't need odin. The CWM3 flash he did was successful. He just needed to flash an ext4 ROM to get past the Samsung Boot screen.
Click to expand...
Click to collapse
That's my thought as well. What rom is the OP trying to use? Is it ext4 compatible? Using a rom that isn't compatible with your file system is one way to get stuck at the Samsung screen.
Although, if ext4 didn't "take" or was partially completed, it could result in something like this. Reflashing with cwm3 might fix this if it notices a problem and tries to redo the conversion.
If flashing a good ext4 compatible rom doesn't fix it, then using Odin and starting over quickly becomes the best option. Though there is a reRFS dk28 rom that the OP could try to flash from his current situation.

Ok flashed Midnight Standard and goes straight to CWM3 startup screen & that's it. So, am I gonna have to do the whole Odin thing? I really hope not. Oh, and fyi I'm a SHE not a HE, lol!
Sent from my HERO200 using XDA App

There's a girl on our website! OMG!
Look for the reRFS dk28 rom. It will try to reformat your phone back to rfs. Then try again. Or just go ahead and jump straight to Odin. Some people seem have a hard time with Odin, but it really isn't that hard.

Ok, thanks for the input. Screw it, just going to do Odin and not mess around anymore. Not having a phone the last day in a half is driving me nuts! Can you point me to a link that has all the stuff I need to do this. I've surfed a couple links and some lead to dead link for Odin. Besides, I want to make sure I've got all the right "ish" to do this. Thanks, so much!
S-

Stuck at HTC screen, won't boot

Hello All,
I have run into a problem with my Heroc not wanting to boot. Some background:
ROM: CM7
Kernal: Jaybob's recent Kernal
Mods: Firerats
All was fine and dandy until yesterday, when I decided to reboot the phone (with a full battery charge). The phone shutoff and when restarted was stuck at the HTC screen. I've tried several times to get into recovery but it hangs at the HTC Screen.
I can enter Fastboot/Hboot. I did some digging and tried to unroot by using this method: http://forum.xda-developers.com/showthread.php?t=988741
Method 1, loading the imaging on the sd root and loading. Everything loaded fine but when I reboot it still hangs at the HTC screen. I have not tried to RUU being that I am on a Mac and don't have access to a PC at the moment. So RUU will be done later tonight hopefully, but I don't expect different results.
It seems like I have some messed up memory and its not allowing me to boot. Does anyone know of a fix? I'm not desperate because its time for an upgrade. I just wanted to hold off on using it until January when Sprint holds their press conference, assuming its an Android device. I'd like to see what I could get versus the phones on the market now.
Any help is appreciated, thanks in advance

srkmagnus said:
Hello All,
I have run into a problem with my Heroc not wanting to boot. Some background:
ROM: CM7
Kernal: Jaybob's recent Kernal
Mods: Firerats
All was fine and dandy until yesterday, when I decided to reboot the phone (with a full battery charge). The phone shutoff and when restarted was stuck at the HTC screen. I've tried several times to get into recovery but it hangs at the HTC Screen.
I can enter Fastboot/Hboot. I did some digging and tried to unroot by using this method: http://forum.xda-developers.com/showthread.php?t=988741
Method 1, loading the imaging on the sd root and loading. Everything loaded fine but when I reboot it still hangs at the HTC screen. I have not tried to RUU being that I am on a Mac and don't have access to a PC at the moment. So RUU will be done later tonight hopefully, but I don't expect different results.
It seems like I have some messed up memory and its not allowing me to boot. Does anyone know of a fix? I'm not desperate because its time for an upgrade. I just wanted to hold off on using it until January when Sprint holds their press conference, assuming its an Android device. I'd like to see what I could get versus the phones on the market now.
Any help is appreciated, thanks in advance
Click to expand...
Click to collapse
You definitely need to do an RUU. No way around it. know it sucks starting fresh again but it'll solve all these problems you have. If your s-off you can also do the RUU from Hboot but it's better to do it from PC as I have learned. Good luck man.

thanks a lot! om going to give it a try later tonight when i have access to a pc. Im not so much worried about starting fresh than I am losing the phone and using my upgrade now... I have a curve laying around and started to thing about using that for a while until I see something I like.
i will report back tonight or tomorrow when i am up and running again.

I had the same problem awhile back and it took me forever to get it fixed but I finally got it fixed. Search the forum for " stuck at HTC screen and look for the threads I started for as possible fix. I will try to find it and post the link here.
http://forum.xda-developers.com/showthread.php?t=1305479&page=3
My last post describes how I finally fixed my Hero, but you should read the whole thread.

williams1978 said:
I had the same problem awhile back and it took me forever to get it fixed but I finally got it fixed. Search the forum for " stuck at HTC screen and look for the threads I started for as possible fix. I will try to find it and post the link here.
http://forum.xda-developers.com/showthread.php?t=1305479&page=3
My last post describes how I finally fixed my Hero, but you should read the whole thread.
Click to expand...
Click to collapse
Thanks. I will give it a look.

I read through the thread and it looks like you passed the black htc screen and got to the white one. I can't get passed the black and adb doesn't pick up the phone at this point. I'm still waiting to try the RUU and see if HTC sync picks up the device.
Very resourceful thread and I'll be sure to give all the suggestions a try before giving up.

HTC sync won't pick up the device and I don't think any other option will work since I don't have ADB access. I'm just gonna bite the bullet and look into a replacement.

Ok to verify your phone does boot at least to the bootloader? If so I have a doffeemr approach for you to take
私のEVO 3Dから送信される。

dastin1015 said:
Ok to verify your phone does boot at least to the bootloader? If so I have a doffeemr approach for you to take
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
yeah. I can get into bootloader and fastboot. whatcha got?
I have a new phone on the way. Amazon has ET4G for $79, too good to pass up so I used my upgrade. Ill still be curious to know how I can get the Hero up and running.

srkmagnus said:
yeah. I can get into bootloader and fastboot. whatcha got?
I have a new phone on the way. Amazon has ET4G for $79, too good to pass up so I used my upgrade. Ill still be curious to know how I can get the Hero up and running.
Click to expand...
Click to collapse
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=804692

I used a flashable RUU based off Flipz source and still no luck. I will give your RUU a try later tonight... Thanks

No luck. The phone freezes at the HTC screen and fails to go any further. :-(

srkmagnus said:
No luck. The phone freezes at the HTC screen and fails to go any further. :-(
Click to expand...
Click to collapse
i had same kinda deal from a bad radio flash
if you still have fastboot do
"fastboot erase system -w"
"fastboot oem boot heroc.hboot-1.46.2000.zip"
you may need to rename the file to HBOOT.
if that dose not work unzip the file take the hboot img and place on sdcard and place where your fastboot files are like in android/platform-tools.
this made a deference for me.
then try fastboot flash img hboot.img
this is what i went through here
http://forum.xda-developers.com/showthread.php?t=1086125
good luck if i can help let me know.

Thanks for the help oostah. I haven't been able to get ADB to recognize the device. When I get home I'll try it again and remove the hboot as suggested and give that a try.
Now that ICS is in beta for the Heroc my phone decides to crap out on me and I can't enjoy the hard work put in by the developers. Nonetheless, I am much appreciative of all the support put into the Heroc and have learned a lot from this community
I'll report back tonight with my results.

srkmagnus said:
Thanks for the help oostah. I haven't been able to get ADB to recognize the device. When I get home I'll try it again and remove the hboot as suggested and give that a try.
Now that ICS is in beta for the Heroc my phone decides to crap out on me and I can't enjoy the hard work put in by the developers. Nonetheless, I am much appreciative of all the support put into the Heroc and have learned a lot from this community
I'll report back tonight with my results.
Click to expand...
Click to collapse
you are welcome i have been there before.
your phone may not recognize ADB but it may still take fastboot commands. that was one thing that drove me crazy is that i could fastboot but not adb. let us all know how it goes.

I did "fastboot-mac devices" and got my device to show up, so it registered. however, when I go to erase system I get an error, "remote: not allowed". The same occurred when trying to flash the .zip and img files separately as suggested . At one point the devices started vibrating like crazy and shut off, the led started to blink green. I did get it back into Fastboot, but now it won't turn on.
Thanks for the help though It was already replaced and the new phone should be here tomorrow. I'm just going to miss the Hero since it was my first Android device and I learned a lot in this forum.
Thanks!

srkmagnus said:
I did "fastboot-mac devices" and got my device to show up, so it registered. however, when I go to erase system I get an error, "remote: not allowed". The same occurred when trying to flash the .zip and img files separately as suggested . At one point the devices started vibrating like crazy and shut off, the led started to blink green. I did get it back into Fastboot, but now it won't turn on.
Thanks for the help though It was already replaced and the new phone should be here tomorrow. I'm just going to miss the Hero since it was my first Android device and I learned a lot in this forum.
Thanks!
Click to expand...
Click to collapse
i still have one of my hero's that i let people play with when the come over. it still runs off wifi so they can play games yous gtalk what ever be nice to get it up and running for experience and fun lol now that your not in a have to mode.
do you have a nan back up from a sd card any place like on your pc if so look for your clockworkmod folder look for backups and you should see your backups open one of them you will see
boot
system
data
recovery
sd-ext
cache
they will be img files you can place them on your sd card and fastboot them back to the phone
"fastboot flash img boot.img"
"fastboot flash img system.img"
and so on
or
"fastboot boot img boot.img"
"fastboot boot img system.img"
and so on
or you can let it RIP

good to know. I'll give that a try if I can get it booted. I'm thinking its dead and needs a charge to get back into fastboot. I'd love to get it back up and running as a learning experience more than anything. I wont have time until tomorrow or Thursday . I will report back when I give it a try.

srkmagnus said:
good to know. I'll give that a try if I can get it booted. I'm thinking its dead and needs a charge to get back into fastboot. I'd love to get it back up and running as a learning experience more than anything. I wont have time until tomorrow or Thursday . I will report back when I give it a try.
Click to expand...
Click to collapse
will the charge light come on when plugged in if not there is a trick take a old usb cable cut one end off on the battery there are
= and - becare full connect the red wire to + and black to - tap them down so they dont move. let it set for 2 1/2 hrs should be good to go.