Database Users

restore from ROM manager bricked my phone

I did a search and couldn't find much help.
I recently dropped my phone and the screen got a slight crack, so the insurance company sent me a new one.
I figured I'd use ROM manager to backup my old phone, and restore it on my new phone.
New phone restores, reboots, and gets stuck at the black Vibrant screen.
I can get back into recovery mode fine, but nothing seems to work.
I let it sit at the Vibrant screen for about an hour before I try again.
Its attempt 3 when I decided to come on this site for some help.
Specs:
Stock
Rooted
Launcher pro
Nothing too much to be confusing and brick, so wtf?
Oh and I understand I could use odin to reflash my phone, please please please don't suggest odin, because I don't own a PC, I own a mac. Please don't tell me to go out and buy a PC or to download a program that costs $50 to use PC programs on a mac. I could have told myself that kind of information.
HELP, my brand new phone is destroyed wahhhh

From the sound of it you still have your old phone. If so, rather than restore using nandroid, try downloading a copy of titanium backup to backup/restore your apps. I have found that sms restore does a good job restoring texts. For me those two apps get the job done restoring my info. Also, if you haven't, sync your contacts to google and they will auto sync upon load. Of course this all assumes you still have your old phone in working order. ..
Also, there are stock roms flashable via clockwork that basically do the same as odin. Check the ' bible' sticky for links.
Hope this helps
Sent from my SGH-T959 using XDA App

a400meter said:
From the sound of it you still have your old phone. If so, rather than restore using nandroid, try downloading a copy of titanium backup to backup/restore your apps. I have found that sms restore does a good job restoring texts. For me those two apps get the job done restoring my info. Also, if you haven't, sync your contacts to google and they will auto sync upon load. Of course this all assumes you still have your old phone in working order. ..
Also, there are stock roms flashable via clockwork that basically do the same as odin. Check the ' bible' sticky for links.
Hope this helps
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I still have my old phone in working order, but that doesn't help the fact that my new phone is stuck on bootup, and can only enter recovery mode...

yelowbottlecaps said:
I still have my old phone in working order, but that doesn't help the fact that my new phone is stuck on bootup, and can only enter recovery mode...
Click to expand...
Click to collapse
The only way I can think of that a nandroid restore would soft brick you, is because you have restored a version of android with a different kernel.
If the original phone had the original firmware (JFD), and the replacement had the most recent (JI6), this is what would be expected to happen.
Since you seem unable and unwilling to use Odin, your going to have to tell us more details (i.e. which versions of the firmware as related above were actually in play) before we can begin to help. If you don't know, well....
You can also simply take it back to a local T-Mobile store and do another swap, or you can find a friend with a Windows PC and Odin (or Samsung's Mini KIES with JI6). These are your only real options...

both phones had JI6
Thank you for the quick responses.
I'm not unwilling to use odin, but unless anyone knows of a free software to use PC programs on a mac, I'm SOL.

so, you got the new phone, rooted, got rom manager and then got clockwork recovery right?
You did a nandroid backup right (on the new phone), before flashing anything right?
Why not just download Fusion and flash that to get the phone up and running?

yelowbottlecaps said:
both phones had JI6
Thank you for the quick responses.
I'm not unwilling to use odin, but unless anyone knows of a free software to use PC programs on a mac, I'm SOL.
Click to expand...
Click to collapse
Well hmm....so much for guessing on my part. Crossing different build kernels is one sure fire way to brick...
Well, there is a solution for Mac and Linux for reloading firmware on a Samsung phone from Download Mode, an open project called Heimdall. It does everything Odin does, but without a GUI, so it depends on how comfortable you are with commandline/shell.
I'll pass you the relevant links so you can see for yourself what's going on.
[PROGRAM] Heimdall - Cross-Platform Open-Source Flashing Software (1.0.0 Available)
Heimdall's Website, with downloads...
XDA Dev Thread with JI6 Odin .tar file....
Best of luck!

s15274n said:
so, you got the new phone, rooted, got rom manager and then got clockwork recovery right?
You did a nandroid backup right (on the new phone), before flashing anything right?
Why not just download Fusion and flash that to get the phone up and running?
Click to expand...
Click to collapse
True that...Why didn't I think of that obvious ploy. If he can get into Recovery, and bounce over to clockwork...Well now's a good a time as any to try Bionix or Bionix Fusion...or a few other of the CW Recovery installable builds...Definitely easier than Heimdall or working out Odin on a mac....and definitely preferable to staring at a Vibrant logo...
{{facepalm}}

masterotaku said:
Well hmm....so much for guessing on my part. Crossing different build kernels is one sure fire way to brick...
Well, there is a solution for Mac and Linux for reloading firmware on a Samsung phone from Download Mode, an open project called Heimdall. It does everything Odin does, but without a GUI, so it depends on how comfortable you are with commandline/shell.
I'll pass you the relevant links so you can see for yourself what's going on.
Best of luck!
Click to expand...
Click to collapse
If there was a step by step walkthrough, I have no problem trying this out.
But I downloaded it and have no idea what I'm doing. Therefore, still SOL

^ are you? You didn't answer my questions.

I'm gonna guess and say you also dl'd the oclf from the market to root too... so now you can't get back into CwR... right?
If you can get adb to recognize your phone then your not SOL. Im not sure what the exact command lines would be but you could delete the update.zip and replace it with another ROM. GL

I just tried using Odin on my roommates PC. An error happened and now the phone is showing a picture of a phone, a couple dots, an exclamation mark, a couple dots, and a computer.
Nothing I can do is taking it out of this screen. Unplugged from computer, took out battery, took out sd card, put it back in... nothing
Am I bricked for good now?
This is a terrible day.

edit: i managed to be able to get the phone into download mode.

No you are not completely bricked! Honestly that is almost impossible on this phone. The only way you'll lose this phone is if YOU give up.
Just keep trying and take a few deep breathes. Take a break actually. Just redo the process from step one.
Edit: you're half way there. Just flash Eugene's froyo that doesn't brixk, reboot, flash JFD or JI6, reboot... then you'll be right back to out of the box status.

All~G1 said:
I'm gonna guess and say you also dl'd the oclf from the market to root too... so now you can't get back into CwR... right?
If you can get adb to recognize your phone then your not SOL. Im not sure what the exact command lines would be but you could delete the update.zip and replace it with another ROM. GL
Click to expand...
Click to collapse
If someone can back this up with some instructions that would be amazing.

All~G1 said:
No you are not completely bricked! Honestly that is almost impossible on this phone. The only way you'll lose this phone is if YOU give up.
Just keep trying and take a few deep breathes. Take a break actually. Just redo the process from step one.
Edit: you're half way there. Just flash Eugene's froyo that doesn't brixk, reboot, flash JFD or JI6, reboot... then you'll be right back to out of the box status.
Click to expand...
Click to collapse
Thank you for the motivation!

yelowbottlecaps said:
Thank you for the motivation!
Click to expand...
Click to collapse
No worries, we've all been there. It took me 6 hours lol. Best part is after you go through this once it will only take you 5-10 mins the next time. The hard part is just getting everything setup in the mist of anger, frustration, fear & panic.

All~G1 said:
No worries, we've all been there. It took me 6 hours lol. Best part is after you go through this once it will only take you 5-10 mins the next time. The hard part is just getting everything setup in the mist of anger, frustration, fear & panic.
Click to expand...
Click to collapse
and in the midst of a roommate that needs his pc back.
I still need a fix that would work for macs... if not, I'd have to wait for my roommate to let me bum his pc again

Do my posts not show up or something? wtf.

s15274n said:
Do my posts not show up or something? wtf.
Click to expand...
Click to collapse
/me pats s15274n on the back....don't get mad...get even! =P
Honestly, sounds like yelow's focusing on getting all the help s/he needs from All~G1. I wouldn't worry about it.
~SB

Bricked epic4g using odin

I know there are various threads like this one but my situation is a bit different. I tried using odin to clean install 2.2 to then use the custom rom epic experience. I attempted to install 2.2 using odin but it would get stuck in "setup connection" and I would have to quit and try again. Last time I tried my phone got the "phone connection caution computer" icon and to get into recovery I would have to hold the power and camera button, not the volume down button. When I go to try and install things straight from my SD card I would get an error like "status 7" cus I didn't have the sprint apps to install 2.2. I believe I get these errors installing straight from the card cus I rooted my phone, modifying the kernal cus I read somewhere because when trying to update, it tries to verify but can't cus things are missing or edited cus of the root. I can't try to use odin again because my computer can't recognize the phone anymore regardless reinstalling the samsung drivers. SOOOO, I'm basically ****ing stuck for sure I think. The way I access the SD card is by using an adapter. The only way I see this working is if I find a fix using the SD card, but it's looking slim cus of the stupid root.

I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!

mxcoldhit said:
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
Click to expand...
Click to collapse
You see, I'm out of options. Last thing I thought of was installing a custom rom 2.1 rom cus 2.2 roms need odin, but I try to install and I get a signature error or whatever. I'm about to throw the phone against the wall, crack the screen, and use my warranty and get a new phone cus I literally tried EVERYTHING. I spent my ****ing 8 hours of my saturday trying to fix this.

Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App

cbpagent72 said:
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
omfg, I used my mom's lappy and the drivers worked. Meaning I can try and use an odin fix.

Odin can be tricky to use because of a few factors other than itself. 1) if you can, use a deskto pc and attach to a usb port literally on the motherboard, no front or pci, this may work, but this I what I found (reading countless threads) to be the most failsafe for everyone. 2) your sammy usb cable is for charging or non critical data transfer ONLY, as it is garbage... repeatedly proven in the threads. 3) reboot pc and phone, boot phone into download mode, (hold down 1. On physical keyboard and press power... DO NOT CONNECT YET! Start up odin, place files where needed (.pit, etc...) uncheck all but what you're told in the flashing instructions with the file you're flashing, most have awesome detals, but sometimes your little issue is resolved on page 50 of the thread... not in the OP. Ok so now plug in the usb connection, odin should find it. If it doesn't, search for drivers, uninstall, reinstall start over, OR you have a bad connection, refer back to usb port and cable. I have 1 out of 4 mobo usb ports that the drivers will maintain a connection to, so try another. Then, once odin has a connection, make sure you're following the guides to the T (and read all the posts)... after that, odin is your best friend. The problem lies elsewhere... odin is the goods. If you have run into problems maintaining connection, and plan to re-root, read all the one click posts and if it drops connection a lot, enter the commands in one by one, repeat if one fails till it sticks. There are way better guides, but you seem to have run into the same issues I did, and after hours and hours, I got that scary ass reconnect me now screen. Just read the whole threads, and if your problem hasn't already been resolved, post in the appropriate thread, so others may learn from your discoveries!
Don't give up, once you figure out the quirks of the relationship between your pc and phone, and of course meticulously follow instructions, your elation when successful will make you forget that pesky 'bricked' screen... trust me I got it too, and no matter how much everyone says you can't brick these following instructions on here... its still scary till it all works. If things are wonky, wipe, go back to DI18 and start over... or just sit tight for froyo roms... good luck!
Oh, and sorry for no links, but it would seem you've probly already read em all... not sure I can do links...

Maybe its just my eeepc that doesn't like the drivers, good luck! Sounds like you're on the way... oh don't forget with the drivers to let em install on connect, leave it plugged in for like 10 mins, unplug, it will then complain it wasn't done, reconnect, then after that finishes, reboot. Crazy drivers...

At least I got a computer recognizing my phone, so I can try and use odin. I've been trying to use this fix
http://forum.xda-developers.com/showthread.php?p=9755894#post9755894
and so far odin has been stuck at this one step "file analysis..."

Yeah I used that method to no avail, but it was about 3 pasts old at the time, so I figured id try
something more stable. Tried a couple dk17 roms, then went back to 2.1 and am now using syndicate xtreme. Id suggest going back to DI18, then go from there. Let me check for another post of mine, theres a dialer code I had to do too at one point...
Ok when doing one click root, someone suggested ##8778# in the dialer, then keyboard enter, then set UART to pda not modem. This and removing comodo firewall, all the sudden my intermittent connection was solid. Not responsible for what this does, but it worked for me. Never found out what it does..... still curious. So this may help you even in odin, try to flash di18 after doing this, then the all in one rom you're looking at...

Oddly enough, I managed to semi-brick my phone several hours ago - my wireless adapter was on the same USB header, and both the wireless adapter and the phone crapped out while trying to flash with Odin.
Thankfully I was still able to get into download mode, and plugging the phone into a different USB port worked fine.

After some more research, about 10 hours of it, odin finally cooperated with me after I downloaded about every kind of file that could make my phone work and finally got it into 2.1
I first flashed the stock kernal to get it working, then flashed stock 2.1
Now I'm that my phone isn't rooted anymore I tried installing 2.2 through the recovery menu and I still get error status 7. Any ideas?

Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...

ungovernable1977 said:
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
Click to expand...
Click to collapse
Alright I completely fixed my phone. After I rooted my phone on 2.1, I then used odin v1.6 to install the froyo .tar file into pda and it worked. I then rooted it again so now I'm back to normal. Honestly, I did so many things I forgot what I did but I now have my phone functional. Thanks for help everyone, I greatly appreciate it!

[Q] about to reset my phone

been having some problems with my phone lately and just wondered if anyone else has encountered these. first off it seems to stop playing any media files whatsoever. i have a bunch of music on it and the player just cycles through and says its not supported. youtube always brings up the error message that the video can not be played. i turn the phone off and on and it works after that but around 24 hours later i'm back to the same thing. also tried using kies to download the 2.2 update but that sucks and doesn't work. would like to root but have no idea where to begin and am afraid i'll screw the phone up. does anyone have an explanation as to what my problem can be and the best way to get 2.2 on this phone?

1st things 1st, Go to the noob guide by S15274N in the Gen section. It has all the info you need. Read it..........
Here is basically what you will do:
Make sure you have the Samsung USB drivers loaded on your computer (found in the noob guide)
Download superonclick to Root the phone (on to the computer)
On the phone download rom manager (from the apps store)
Follow the directions from superoneclick (look at unlockcr.com good how to video)
After you root the phone then decide what to load as far as a custom ROM. I would Try the Trigger or Axura, they both very stable Download on to the computer
Then hook up the phone on to the computer Make sure you connect the usb
(the pulldown at the top) make usb debugging is clicked.
Load the rom on to the Internal sd card and then go to the Rom manager and click reboot into into recovery.. install it wait 15 mins to install and you are good to go
READ the NOOB guide it is complete this is just an outline.
good luck

well i'll give it a read and see if i have enough balls to do it. thanks

ndavis_28 said:
been having some problems with my phone lately and just wondered if anyone else has encountered these. first off it seems to stop playing any media files whatsoever. i have a bunch of music on it and the player just cycles through and says its not supported. youtube always brings up the error message that the video can not be played. i turn the phone off and on and it works after that but around 24 hours later i'm back to the same thing. also tried using kies to download the 2.2 update but that sucks and doesn't work. would like to root but have no idea where to begin and am afraid i'll screw the phone up. does anyone have an explanation as to what my problem can be and the best way to get 2.2 on this phone?
Click to expand...
Click to collapse
I'm having these same exact problams and it is very frustrating. Also the video recorder will stop working I found.
So you are using 2.1? I've gone up to 2.2 using kies. I can't remember when I went to 2.2, but my guess is this has been happening since then.
In the past week I've been on the phone way too long with Tmobile support. They say that they have never heard of this (apparently I'm not the only one though) and had me try a master reset. That didn't work and the only solution seems to be to reboot the phone. Am I the only one who thinks having to reboot within 24 hours is ridiculous?
So now that they have sent me 3 phones, they directed me to Samsung which wanted to try the same Master Reset. I know that will only temporarily fix the problem so the next step is to send the phone in. How is that suppose to work? Have no phone for a week.
I guess I could ask Tmobile to do it for me and give me a loaner, but I think it is time to go with a custom ROM.
So is anyone else having the problems we are having? We can't be the only two. Is the stock 2.2 just bad and I will be better served with a custom ROM?
I was hoping to avoid this, but the phone is pretty much crap to me now anyway, so I guess what can I lose?

pmiller said:
So is anyone else having the problems we are having? We can't be the only two. Is the stock 2.2 just bad and I will be better served with a custom ROM?
I was hoping to avoid this, but the phone is pretty much crap to me now anyway, so I guess what can I lose?
Click to expand...
Click to collapse
IMO stock from samsung have never been very impressive especially when compared to all the custom roms out here. The simplest roms to flash will be the kb1 based roms such as Trigger, Axura or Bionix (in no particular order).
Your phone will feel completely different and you will likely gain a new found appreciation for it, so go flash a custom rom

shreddintyres said:
IMO stock from samsung have never been very impressive especially when compared to all the custom roms out here. The simplest roms to flash will be the kb1 based roms such as Trigger, Axura or Bionix (in no particular order).
Your phone will feel completely different and you will likely gain a new found appreciation for it, so go flash a custom rom
Click to expand...
Click to collapse
Thanks for the advice. After reading through the steps and getting lost at only the 2nd step of rooting, I think I'll just stick to stock and deal with the problems.
Not ideal, but I'm just not in the mood to put that much into a phone anymore. Maybe I'm just lazy, but I'd like to have a program that will do all the steps of getting a new ROM on my device. I feel overwhelmed by having to maintain a ROM.

Its not as hard as you think. Just use superoneclick to get root access, download rom manager , download the rom you want on your sd then reboot into recovery from root manager and chose your rom from the sd.
Sent from my Bi-Winning powered SGH-T959 using XDA App

pmiller said:
Thanks for the advice. After reading through the steps and getting lost at only the 2nd step of rooting, I think I'll just stick to stock and deal with the problems.
Not ideal, but I'm just not in the mood to put that much into a phone anymore. Maybe I'm just lazy, but I'd like to have a program that will do all the steps of getting a new ROM on my device. I feel overwhelmed by having to maintain a ROM.
Click to expand...
Click to collapse
Give this a look
http://forum.xda-developers.com/showthread.php?t=954509

touch screen not working

Hey guys, a few days ago I finally decided to root my phone and flash cynagen mod 7...
However yesterday evening my touch screen suddenly stopped working, so I can't unlock my phone...
its still showing screen but its not responding when I press anything...
Things ive tried: removing battery for 20 sec, removing battery to turn off the phone and start it up again.
Is it possible to fix this?
or does anyone have the stock Vodafone firmware so I can try flashing it and return it for warranty?

Try reflashing the Rom from recovery again maybe that will help, I think I saw a thread on here about a fix for that problem a few months ago but not sure as I never needed it so didn't read it.
Sent from my HTC Wildfire using XDA Premium App

Scratch0805 said:
Try reflashing the Rom from recovery again maybe that will help, I think I saw a thread on here about a fix for that problem a few months ago but not sure as I never needed it so didn't read it.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
You mean re flashing the stock Vodafone rom?
Any place where I can find it?
Btw even clockworldmod doesn't seem to respond to my buttons(the ones below the screen)
Only the physical buttons work...

Sorry I meant try reflashing your cm7 Rom again from recovery, use the volume buttons and the trackball to navigate in clockwork.
Sent from my HTC Wildfire using XDA Premium App

Scratch0805 said:
Sorry I meant try reflashing your cm7 Rom again from recovery, use the volume buttons and the trackball to navigate in clockwork.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
ill give it a shot, by the way when I tried to flash with RUU it didn't detect my phone.
Also when I boot up my phone with charge cable it stops responding and only the red charging light will burn(even when the battery is full, because it did this for hours a few days ago)
Also in clockwork when I go to advanced and key test it doesn't do anything when I press a key, It doesn't show anything in the log.
So I think its really broken.
Update: reflashed with cyanogen didn't fix it
And when I try to flash with WUU it says my phone is not connected
ofc I can't access my usb settings on the phone...

The charging bug comes with clockwork, when the phone is off if you plug in the charger it happens so I always make sure to hit the power button first wait till the splash screen has gone and then plug it in, its annoying but just pop the battery out and then reboot the phone. There's a fix for that too but it didn't work for me.
As for the other problems I'm not sure as I've never come across them on my phone before, I would definitely try reflashing first before using an ruu. If that doesn't help hang fire till someone a bit smarter than me sees this.
Sent from my HTC Wildfire using XDA Premium App

Scratch0805 said:
The charging bug comes with clockwork, when the phone is off if you plug in the charger it happens so I always make sure to hit the power button first wait till the splash screen has gone and then plug it in, its annoying but just pop the battery out and then reboot the phone. There's a fix for that too but it didn't work for me.
As for the other problems I'm not sure as I've never come across them on my phone before, I would definitely try reflashing first before using an ruu. If that doesn't help hang fire till someone a bit smarter than me sees this.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
I just tried re flashing and that didn't help, I think my screen is really broken.
Including those home, menu back and search button.
only the power and the volume buttons and track ball work...
Update: sometimes my screen seems to work for a few seconds and then it doesn't again...
Depends on how I hold my phone...

gijs007 said:
I just tried re flashing and that didn't help, I think my screen is really broken.
Including those home, menu back and search button.
only the power and the volume buttons and track ball work...
Update: sometimes my screen seems to work for a few seconds and then it doesn't again...
Depends on how I hold my phone...
Click to expand...
Click to collapse
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin

ErwinP said:
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin
Click to expand...
Click to collapse
I would give it a try, but im not out of warranty, its just voided until I re flash a stock Vodafone firmware.
So if anyone could give me one id be really happy.
Preferably a Dutch/nl one with hboot 1.02

There's links to some ruu's in here, hope you find what your looking for.
http://forum.xda-developers.com/showthread.php?t=1029318
ErwinP said:
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin
Click to expand...
Click to collapse
I've changed the touchscreen on mine and can confirm the softkeys are attached to it, there's 2 separate cables though I think the one from the softkeys is only for the led's as mine broke, the buttons work fine but I have no lights behind them.
Sent from my HTC Wildfire using XDA Premium App

gijs007 said:
I would give it a try, but im not out of warranty, its just voided until I re flash a stock Vodafone firmware.
So if anyone could give me one id be really happy.
Preferably a Dutch/nl one with hboot 1.02
Click to expand...
Click to collapse
As you are looking for a ROM with hboot 1.02, I assume that before rooting you had the same hboot? Because then you must have gained root using AlphaRevX/Revolutionary, which installs a custom bootloader. This hboot can, to my knowleadge, not be downgraded to the original one. In other words: you have voided your waranty and there is no way to cover it up...
Erwin

ErwinP said:
As you are looking for a ROM with hboot 1.02, I assume that before rooting you had the same hboot? Because then you must have gained root using AlphaRevX/Revolutionary, which installs a custom bootloader. This hboot can, to my knowleadge, not be downgraded to the original one. In other words: you have voided your waranty and there is no way to cover it up...
Erwin
Click to expand...
Click to collapse
Damn, will they figure this out or is their a change they are just like oh yeah the screen is broken lets fix it?
As its clearly a hardware issue and not a software issue...
Other whys ill just fix it my self or go to a phone store...
update: I tried flashing SUU but it keeps giving me a message that my phone is not connected...
But the phone store told me rooting does not void my warranty as its a hardware issue and not a software issue.. they told me they could send it for me to a special company that repairs phones and is qualified by mayor factories like HTC,Samsung,etc.
But they also told me it would be easier to just contact Vodafone for repairs as that is free and if not I could always come back.

I'd send it back to Vodafone, best case they'll switch the touchscreen power it up for a quick test then send it back, worst case is they may check your software versions... then send it back unrepaired.
I used to fix iphones and ipads for an insurance company and hardly ever had enough time for checking software, just fix it, send it out and crack on with the next one!
Sent from my HTC Wildfire using XDA Premium App

dont panic your phone is all right
It also happened in my case.Go to the following link
http://shipped-roms.com/index.php?category=android&model=Buzz
and flash a suitable ruu rom .it will definitely fix ur phone.or u can just boot into recovery by pressing volume and power button simultaneously during the boot and flash cm 7 rom.

rashmifantasy said:
dont panic your phone is all right
It also happened in my case.Go to the following link
http://shipped-roms.com/index.php?category=android&model=Buzz
and flash a suitable ruu rom .it will definitely fix ur phone.or u can just boot into recovery by pressing volume and power button simultaneously during the boot and flash cm 7 rom.
Click to expand...
Click to collapse
I already re flashed cm7, and at first it didn't help then suddenly it did help and now its doing nothing all over again...
Update: re flashed again and still nothing.

AFAIK reflashing a custom rom from a custom recovery should not solve the issue.
But reflashing a stock ROM (= RUU) should solve that. Also reflashing a stock ota update will solve that. Ota update needs to be flashed from stock recovery. Do either of these things depending on what your hboot version is (if hboot is latest then ota will be option for most times) Also remember PC49IMG method if you presently have custom recovery.
P.S : what all I said is thinking that it is software issue. this shouldn't help if it is related to hardware.
Sent from my Blade using XDA App

I was wondering if there was a way to flash using that method, as I said I never needed to flash an ruu yet so don't know much about em. Just saw your other post explaining how to use PC49IMG to flash an ruu. Thought i'd copy it here as it may help.
bharatgaddameedi said:
If it still had the issue, then install the RUU by pc49img method. Download the correct ruu for your phone. Donot connect phone to PC. On windows PC click on start and type %temp% and enter. This opens the user temporary folder of your PC. Now run the ruu. Now if you observe the temp folder, there will be extra folders created which have folder name enclosed in {} brackets. Search in these folders for the file ROM.zip. Copy the ROM.zip to a safe location. Now format your memory card to fat32 (must) and put the ROM.zip to the root of memory card. You should use memory card reader. Then rename the ROM.zip to PC49IMG.ZIP . Then insert memory card in phone and reboot to hboot menu from where you can update/reflash the partitions. If still not working, clear storage again from hboot menu.
Sent from my Blade using XDA App
Click to expand...
Click to collapse

if ur stock screen is showing a date of 1980(after flashing a custom rom)
Just flash the RUU_Buzz_Froyo_hTC_Asia_WWE_2.24.707.1_Radio_13.55.55.24H_3.35.20.10_release_161113_signed.exe
it will help

Scratch0805 said:
I was wondering if there was a way to flash using that method, as I said I never needed to flash an ruu yet so don't know much about em. Just saw your other post explaining how to use PC49IMG to flash an ruu. Thought i'd copy it here as it may help.
Click to expand...
Click to collapse
Did that and now its on stock Vodafone firmware
But the touch screen still isn't working.
Oh well now I can send it back to Vodafone for repairs.
Thanks for the help
Btw: is their anyway to get the original hboot back?

For maybe some more like me that want to go back to what it use to be with the hboot S-OFF, S-ON issue.
I had my phone S-OFF with alpharevx beta. Used CM7 -stable for couple days but decided i wanted to go back to all original. I first RUU my phone with the RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed.exe file. Boot it up, made sured it runs, then did what is instructed below here;
To be able to do this you need HTC USB drivers installed. Install the HTC pakage, reboot, uninstall the HTC-
Sync software, keep the drivers! reboot PC again.
Power off your phone. Plug in your USB cable to phone. Press volume down and powerup your phone. After it
settle navigate down and choose fastboot option.
1. Unpack these files to your c:\fastboot
2. Open up your windows command promt (WinVista/7 users rightclick choose run as Administrator)
3. in command promt type CD\ then press enter
4. then your should be in C:\
5. type cd fastboot
6. then you should now be in dir C:\fastboot
7. Im bored to death typing, look below. Beware of each command ends with enter. After success, reboot.
C:\fastboot>fastboot oem mb 9C068490 1 30
... OKAY
C:\fastboot>fastboot flash hboot hboot_buzz_7225_1.01.0001.nb0
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... OKAY
Files needed (Windows version): megaupload.com/?d=UO9L74I9
Works perfectly for me.
* NOTE: Im not responsible for your phone if you brick/kill it. These steps worked for me!

[SOLVED] Boot loader Won't unlock

hi. so I just bought my a500 used in the forums never rooted or unlocked already on the ice ota. I tried to unlock the bootloader' but everything just freezes while flashing. I am just stock rooted for now' but I really want to do some good dev work since my a2 has a locked boot loader. thanks/for any help and sorry if this had been covered. I may seem like it but I am not a complete noob.
Sent from my A500 using xda premium

lkrasner said:
hi. so I just bought my a500 used in the forums never rooted or unlocked already on the ice ota. I tried to unlock the bootloader' but everything just freezes while flashing. I am just stock rooted for now' but I really want to do some good dev work since my a2 has a locked boot loader. thanks/for any help and sorry if this had been covered. I may seem like it but I am not a complete noob.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Which OS are you on? ICS? HC?
Which "one step" app are you using to change out bootloaders?
MD

Moscow Desire said:
Which OS are you on? ICS? HC?
Which "one step" app are you using to change out bootloaders?
MD
Click to expand...
Click to collapse
I am on stock rooted is. it came stock ics and I just rooted it. I have tried pretty much all the tools available in windows, and done it manually with no flash in ubuntu. I can give u the. exact nvflash error later, but it falls I think on the step of actually flashing the new bootloader
Sent from my A500 using xda premium

lkrasner said:
I am on stock rooted is. it came stock ics and I just rooted it. I have tried pretty much all the tools available in windows, and done it manually with no flash in ubuntu. I can give u the. exact nvflash error later, but it falls I think on the step of actually flashing the new bootloader
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Well, if you can't use the tools, (you don't need to give the NVFlash error, I already know what it is), then first try the following. (no matter how silly they sound.
1. Different PC
2. Different USB port. (mine has 4)
3. A good USB cable. Using one that comes with the printer or camera, or an el-cheapo won't work. Data pins aren't always the same. I use my HTC cable.
4. Make sure anti-virus and such is off.
If that doesn't work, only recourse is to roll back to 3.0, preferably by RUU. Problem is, you need an HC UID number to run the ruu. That should set your partitions in place. It's possible you might be able to run an HC 3.2 full update, grab the UID, then run the RUU.
After that, do the NVFlash to get the bootloader/CWM.
At least if it were me, that's the route I would take. Never did it before, but seems sound.
A Pity you bought it already with ICS.
MD

Moscow Desire said:
Well, if you can't use the tools, (you don't need to give the NVFlash error, I already know what it is), then first try the following. (no matter how silly they sound.
1. Different PC
2. Different USB port. (mine has 4)
3. A good USB cable. Using one that comes with the printer or camera, or an el-cheapo won't work. Data pins aren't always the same. I use my HTC cable.
4. Make sure anti-virus and such is off.
If that doesn't work, only recourse is to roll back to 3.0, preferably by RUU. Problem is, you need an HC UID number to run the ruu. That should set your partitions in place. It's possible you might be able to run an HC 3.2 full update, grab the UID, then run the RUU.
After that, do the NVFlash to get the bootloader/CWM.
At least if it were me, that's the route I would take. Never did it before, but seems sound.
A Pity you bought it already with ICS.
MD
Click to expand...
Click to collapse
Alright, thanks.
I feel like such a N00B right now, LOL. This is like when I first bought my Atrix 2.
I bought it used on the forums and figured I was good, I don't have to even update it and stuff since it is on ics, and the bootloader is unlocked, so I will have aokp on it by the end of the night I get it. I guess I was wrong....
Anyways, I tried other ports, and I was using the good motorola cable, but tried the one that came with i as well, so I guess I have to go back to HC. Why would that help? is the idea that I can then just unlock it some other way? If so, how might I go about getting the UID.
Also, is it worth trying to flash the honeycomb bootloader? any better chance there? cause with that I could just flash the new one with a zip or fastboot. also, Is there any way to just put the new one on by simply putting it on the partition using cat or something. I know I did that on my a2 with recovery, but it would brick with the bl.
Thanks for your help.

Thanks everyone, I got it, here's what I did. As usually I massively screwed things up in the process, but I got it:
So first, I tried to flash again in a few different ways, no success, no harm.
Then I downloaded a HC 3.1.2 or something full rom and put it on my sdcard and rebooted and applied it. BRICK. boot verification failed. So that clearly didn't work, and I realized that is because I had an HC rom with ICS bl.
Long story short I tried to get back with an ics update.zip with no luck, so I tried using a stock rom EUU, but it got to the part where it was looking for the tablet with adb debugging so I cancelled it, since obviously that was not going to do anything. Then I tried a few more zips, with no luck at all and somehow ended up in fastboot, which makes no sense since nothing flashed (or at least I though). From there I tried flashing cwm so I could recover, but it just kept saying "not supported in lock mode" so I gave up on that.
Now comes the accidental fix part. I tried the other exe in the EUU just to see what it did, and it appeared the same, so I just kept hitting continue, and when it got to the usb debugging part, I must have hit minimize instead of close. about 30 minutes and me being really pissed that I somehow hardbricked later I realized there were now 2 windows of the EUU thing open. One said that it could not find my device, and to manually put it in apx mode. WOW, so I was just too impatient before.
Long story shorty again, that worked and it was back on stock honeycomb, and I flashed the HC unlocked BL with no issues, but that did me no good, so I put aokp on my sdcard and flashed the ICS BL with no problem at all this time. I rebooted into recovery and flashed aokp, watched the boot animation that reminded me it was made by a 7 year old girl for a few while the dalvik cache built, and then I was good to go screw with the unusually large number of settings included and flash gapps.
So, yeah, basically I am an impatient moron, but hey! it worked.
Now I just have to find a good OC'd kernel that will work with aokp and I an good to go.
Just a heads up, I plan on building JB aokp and releasing it, so get ready for some serious unicorn swagger in a few months when I finally decide to do it.

I like that process. Flash everything till something works :laugh::laugh::laugh:
At least it works for me sometimes
Glad you got it going.
Listen, edit your post and link to the EUU files you were successful with. Might help some others.
MD