Database Users

[Q] HELP!!! Rom Manager bricked my device!!

here's the story,
i installed rom manager from the market. flashed the clockwork recovery using it, then tried to flash a new rom using rom manager. i am sure that the rom is compatible with my settings. now my phone is in the boot loop and i can't get into recovery nor the bootloader. any help?
32a s-off
radio 6.35
2007 spl
i can only remember the basics of my device since i can't get into the bootloader...
THANKSSS

Did you pull the battery and then try booting into recovery/bootloader? If you get thrown into the bootloop when you put the battery back in, try holding back/home while putting the battery in.

Thanks for helping me! I actually did try that method but I was back to boot loop again. I really hate that "Rogers" screen.
Does that mean I'm bricked for good?

as it turns out, HTC makes magical device as it cured itself from the brick!!
i basically gave up and just left it running till the battery goes out, the next day, it is booted into the rom.
truly magical!!!!

True happened to me once when I tried to load my first rom. Just let it sit there while I'm searching the forums trying to look for some answers then voila it booted up properly

too bad i semi bricked it AGAIN!!! i really am bad at this...
flashed rogers official rom over cm. should have done some research first. still trying to fix it. but its not bad, learn a lot everything time i do something wrong.

Did you wipe prior to flashing a new rom?
Sent from my HTC Magic using XDA App

I've done the same mistake and my device hanged at rogers rom with radion 3.22 and SPL 1.76 S-ON. I've briked mine very bad that time, but yours might yet be recoverable. If you have s-off, the i think you're saved. Post your hboot info here...

Hi... I have similar problem... but my phone can't power on... in have samsung galaxy gio (GT-S5660M) after using rom manager... the phone reboot and can't start... nothings appear in the screen... I have only black screen... nothings appears
I try to remove the battery and put again... but nothing... I try to remove the sd card too and restart again... nothing... the cellphone not power on... I dont see any screen of logo, boot... nothing...
When I apple rom manager... the phone are disconnected (not charging)
Anybody can help me please ??
I dont know what happend :S

HTC Magic 32B Black Screen, no response to anything

Hi there,
I have the following problem:
My cousin bought a brand new Magic 32B Vodafone.
I flashed it to latest CyanogenMod 6 for Magic.
The phone still has the Factory SPL + Radio on it,
i just put a custom recovery on it and flashed CM6.
I did the same with my Magic 32B, works fine since a year now.
It worked fine for about 2 weeks, with CM6 running stable and everything.
then suddenly after a reboot of the phone just went to black screen,
no vodafone splashscreen shows up or anything. It vibrates and then does nothing.
It doesn't show up at "fastboot devices" and "adb devices" shows no deveice either.
When i boot it up with volume down + power pressed (to get in fastboot) it doesnt vibrate (like when it works normally), but screen stays black.
I cant get in recovery either.
anyone ever had this problem? of course i googled for this problem but none of the "black screen" search results described my problem ..
is there a way to autoapply defaultrom (SAPPIMG.nhb) put on sd card (may have read something about that some time) or any other solution to this problem?
is this due to flashing the custom rom or maybe a broken device?
what are the chances to get it back from warranty?
i very much appreciate any help!
thanks

Sounds like the screen broke. If you install ANDROIDSDK you can probably grab screenshots to see what the phone is doing. That will allow you to flash the stock sappimg to get back stock and send in under warranty for repair.
Sent from my LG-P500 using Tapatalk

Does not work, phone doesn't respond to anything
ok, I'll just have to sent it to warranty then, and hope for the best
thanks anyway

did you ever fix this?

Phone possibly bricked

First of all my software facts so we know what we're talking about:
ACE PVT ENG S-OFF
HBOOT-0.85.2007 (PD9810000)
MICROP-0438
RADIO-26.04.02.17_M2
eMMC-boot
Oct 11 2010, 12:44:14
im using the latest nandroid. can't find the information for that.
I've looked in a couple places for similar problems but i couldn't find something useful for my problem.
I was at a party last night and had my phone in my jeans pocket. I think its obvious that it was pretty hot and I sweat...
After the party I checked my phone and the style and wallpaper were changed. I also found that the power button didn't work anymore. Before everything had worked just perfectly.
Since I could still use my phone I tried to backup as much as possible. I also made a backup of the current rom.
Unfortunately I restored that rom, and I think that's what causes me problems now. Please don't ask me why I did it, I just wasn't thinking a whole lot.
After reboot the phone stuck in the white screen with green htc logo.
I tried to take out the battery a couple times and rebooted it, but it didn't work. The phone always starts automatically when I put the battery in. Sometimes the colors of the screen were messed up, meaning that it was all pink or some kinda "pixel curtain" was above the image.
I also started the phone in recovery (holding just vol down and inserting the battery) In recovery the phone checks the usual things but I can’t see the results of those checks. I’m pretty sure though, that they all say “No” (no clue if that’s good or not).After that I’m stuck in recovery. The vol buttons don’t work or at least I can’t move my selection and the power button, no surprise, doesn’t work either.
So that is pretty much my problem. I hope you can help me with that.
i ran the latest ruu and it succesfully got my phone back. the power button, however, still doesn't work. anybody an idea how i could fix that? or what could cause the problem?

Update:
when i connect the phone the my pc it shows: hboot usb plug.
i'm not familiar with hboot. could someone tell me what i can do to repair my phone, i guess i have to flash a new rom, using hboot?
moreover, after some time the phone changes into fastboot usb
now i can use the vol+/- buttons again but i cant select anything since the power button doesnt work. but that probably means that i can use fastboot to flash a rom right?
could somebody please explain how i can do that?
i'm also trying to use the test ruu and change the room.zip to the latest one. i founde a thread where that worked: http://forum.xda-developers.com/showthread.php?t=835595&page=3
i hope i can fix it because i doubt htc will replace my phone because of the void warranty...

Seems that this is a hardware issue.
You said you ran a RUU, right?
What does your bootloader show now? The first line is important. It should say something like ACE PVT SHIP S-ON
If this is the case, you should get it replaced by htc because they can't figure out anymore if you had a custom rom or not
Btw: which RUU did you install?
Sent from my Desire HD using Tapatalk

[Q] Help!!

Hye all HTC Wildfire user,
i have a problem over here, since updating my set using RUU - RUU_Buzz_Froyo_hTC_Asia_WWE_2.24.707.1_Radio_13.55.55.24H_3.35.20.10_release_161113_signed.exe
Current details:
BUZZ PVT SHIP S-ON
HBOOT - 1.01.0002 (previously 0.0.82...)
When i hard reset, try to recovery mode to flash other ROM's, its start shown handphone image with alert on red color icon. then, when i try to push vol up + power button, error msg shown E:Can't open /cache/recovery/command... Also blue font text on top Reboot system now, Apply sdcard update...., Wipe data/factory reset, Wipe cache partition... thats all..
How, can i get back to normal recovery mode.. pls, help me!!

msabrifx said:
Hye all HTC Wildfire user,
i have a problem over here, since updating my set using RUU - RUU_Buzz_Froyo_hTC_Asia_WWE_2.24.707.1_Radio_13.55.55.24H_3.35.20.10_release_161113_signed.exe
Current details:
BUZZ PVT SHIP S-ON
HBOOT - 1.01.0002 (previously 0.0.82...)
When i hard reset, try to recovery mode to flash other ROM's, its start shown handphone image with alert on red color icon. then, when i try to push vol up + power button, error msg shown E:Can't open /cache/recovery/command... Also blue font text on top Reboot system now, Apply sdcard update...., Wipe data/factory reset, Wipe cache partition... thats all..
How, can i get back to normal recovery mode.. pls, help me!!
Click to expand...
Click to collapse
LOL.
WHY DID U FLASH THAT RUU_Buzz_Froyo_hTC_Asia_WWE_2.24.707.1_Radio_13.55.55.24H_3.35.20.10_release_161113_signed.exe
It updated ur hboot to 1.01 and made it unrootable. U have done a great mistake without being aware. What u have used all these days is custom recovery.
And now, what u see the red triangle one is the official recovery with which u cannot flash custom roms.

my bad.. i'm a beginner to this smartphone.. its my bad.. i didn't really notice or aware about this.. empty knowledge..
means now, i'm stuck to this ****.. someone, who is really can help, highly appreciated.. but, reading thru all those previous post, seems like, whoever had this problem, will stuck here, end of the story.. sucks!!

msabrifx said:
my bad.. i'm a beginner to this smartphone.. its my bad.. i didn't really notice or aware about this.. empty knowledge..
means now, i'm stuck to this ****.. someone, who is really can help, highly appreciated.. but, reading thru all those previous post, seems like, whoever had this problem, will stuck here, end of the story.. sucks!!
Click to expand...
Click to collapse
U must have got this phone from others. Since if u r beginner to this one, u might not have known about custom recovery.
Anyway, presently only there is one option to root, and that is with the paid xtc clip. And welcome to the crew of people waiting for froyo root.

[Q] Desire Z Stuck on HTC Logo

Hello Forum,
I bought an HTC Desire Z from ebay a few months ago. I think it's a great phone, and I'm gutted that I seem to have killed it. It was working fine on purchase, so I can't return it. The problem is: About 6 weeks ago, it decided to do an OTA update (Not sure if it was of apps only, or the OS).
It got locked up half way through, and I had to pull the battery.
Following this, it no longer boots. It gets stuck on the HTC logo. I have tried to follow all the advice on various threads, but they all seem to assume scenarios that aren't possible in my case. (eg. I can't use ADB because USB debugging was never enabled, I can't create a goldcard, because I can't boot the phone up, and my SD card adaptor doesn't seem to work with ReadCID):
As far as I know, it is completely stock, though I can't see any carrier branding. It isn't rooted, and has S-ON. I don't know what version it is, but I think the details below will help this:
I can get to the Fastboot menu.
'Factory Reset' just causes it to lock up.
'Recovery' causes it to shut down, show an icon of arrows encircling a phone, then buzzes about 7 times, then locks up, powered off.
ADB doesn't recognise the phone.
RUU stops every time on 'Rebooting Bootloader' and doesn't move further.
Fastboot does recognise the phone but I can't seem to do anything through it.
The best result I've had was that I was able to extract the most up to date ROM.ZIP from the RUU, which I put on an SD card, as PC10IMG.zip. This did load up, and started updating, but got stuck on 'Updating' the Bootloader, until the battery was completely flat. (4-5 hours). This has happened three times.
The text on the bootloader screen is:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
HBOOT
Parsing ... [SD ZIP]
[1] BOOTLOADER - Updating
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SPLASH1
[6] SPLASH2
[7] USERDATA
[8] TP
[9] TP
[10] RADIO_V2
[11] RADIO_CUST
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Update is in progress
Do not power off the device!
Can anybody offer any advice on what I might still be able to do from this position?
Thanks in advance for any help, and apologies if I've missed any important information!
Ian.

ok, fasboot doesn´t help if you do not have eng hboot.
you could type fastboot oem boot and the phone will try ro boot into the rom and will probably also get stucked on htc screen.
did you try to push power & volume up if the icons comes up after enter recovery?
other thing you could try is to find a ruu that is similar to the version you had on your phone before and try the pc10img thing...
EDIT: or first enter bootloader and then start the ruu on your pc

Hi,
Thanks for your reply.
I tried the 'Power and Volume Up' when the icons came up doing recovery. The screen seemed to go slightly duller than normal, but it then just buzzed 7 times, turned off, and won't turn off again at the moment. Does it need to be left for a period of time after starting this procedure?
FYI - I tried two other ROM.ZIP files from two other RUU's before I got this one to even attempt to load, and both came up with 'Main version is newer than rom' (Or similar). The only one that seems to do anything is the very latest one from the Shipped ROMS website.
RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
All the other ROM's have Radio versions lower than that mentioned on the Bootloader screen, so I guess I won't be able to use any earlier ROM.
I'll try the fastboot oem when it starts responding again from the recovery procedure.
Fingers crossed !

I'm afraid that the 'recovery' method doesn't seem to have made any difference to previous attempts.
The 'fastboot oem boot' comes up with:
fastboot oem boot
.. FAILED (status malformed (1 bytes))
finished. total time: 0.000s
Any other ideas?

Hmm. I think I'm out of ideas.
Does anyone have any other thoughts before I list it on eBay for parts?
Thanks,
Ian

The same thing happened to my phone during an OTA 2.3 update, thankfully for me I still had warranty so sent it off to the shop, when it came back I noticed the void tag has been broken, so I'm guessing the fix may of required replacing the internal memory or something along those lines.

Thanks Greg.
At least it's starting to confirm my fears.
The only other thing I just remembered, was that the SD card failed a couple of weeks before the problem happened, and I replaced it with a new one. Maybe this is tied in with the problem. Do any of the experts have a view on whether the OTA update could have failed because the SD card wasn't the original?
The RUU is able to see what the image version is on the device, so there is some connectivity, but it can't seem to reboot the bootloader.
As a result, I can confirm that the image on there currently is 2.42.405.2.
Similarly, the PC10IMG approach seems to get to the point of updating the bootloader, but then hangs.
Could any of the experts confirm whether this would happen if I didn't have a goldcard in, but need one? I can't seem to create one with any of the methods I've found online so far, and want to know whether this is the best line of attack to move things forward, or whether this will be likely to be a similar waste of time.
As far as I can tell, I can't install an ENG bootloader without being able to boot the phone to turn on ADB, I can't do anything with fastboot without the ENG bootloader, and I can't do anything with ADB whilst the phone won't boot up.
In short, I think I'm stuffed. Any other ideas?
Thanks,
Ian.

Update:
I contacted HTC, and apparently, it's still in warranty, even though I wasn't the original purchaser, so there may be a positive conclusion to this story. Will be back in 7-10 days to let you know what happened
Fingers crossed.

there is really not too much to worry about, if you private message me, I can give you Josh's information here on XDA - he can unbrick pretty much any G2/Desire-Z for $40 and has done 100's of them - he has like almost 500 Thanks on here -
the only thing he can't fix is a fried emmc chip, but thankfully those are relatively rare!
(and if the emmc chip is fried, then HTC will fix it, because that truly is their fault, so no worries!)
(HTC knows of the emmc chip failures, and that is why in this case they are not giving you a hassle about the warranty, sort of like when an auto company has done a silent recall, so to speak)

Cant help
Sorry cant really help you much... i wouldnt want that to happen with me...

Thanks anyway for all responders
I just have to wait a few more days for HTC to pick it up and take it to the phone hospital. So long as the previous owner hadn't done anything to invalidate the warranty, I think I may be OK. I definitely haven't.
I'm starting to wonder if it's a bad pin in the USB socket that's preventing it from communicating with the PC properly. I found an error in the RUU log when trying to do a 'fastboot oem rebootRUU':
... FAILED (status read failed (Too many links))
Apparently, this is linked with bad USB cables or drivers, but I know the USB cable and drivers are OK, because I can communicate properly with my Wildfire S using the same set-up.
Anyway - Thanks again for the advice, and fingers crossed