Develop Bugs

So I think my HTC One V is bricked, can someone help?

So, I previously had an optimus v, which is like the easiest phone to root and get roms for and what not. Well i was hoping that the One V would be the same, it was not.
So I tried to install some rom that i liked after going through the unlocking and rooting process,and it had a restarting problem where every 5-15 seconds after it would boot it would restart. I found a solution (kind of) to that but most of the links where dead so i had to find them on my own. It led me to putting a custom kernel on it and that did not fix it, so i saw something that getting the OTA update that came out a while ago could cause this, and the only way to return it was to use RUU (i still had a custom kernel at this point, i think) so i got the (hopefully) correct recovery.img from RUU and i flashed that and the next step is to relock the device, so i did via command prompt, and i started RUU up again and it was doing its thing and ended in an error 155. I have tried several times and it has still not worked. I found some stuff saying that the HBOOT i have which is 1.57 doesnt have a supported RUU or something to that effect ( i found lots of conflicting information).
So now i am stuck with a phone that only goes to the bootloader menu and because its relocked i cant flash anything to it.
I have tried fastboot oem unlock and that came up with a command error, and everything else i try to flash just fails.
Any help is welcome and a thank you in advance to anyone that helps.

matterlord1 said:
So, I previously had an optimus v, which is like the easiest phone to root and get roms for and what not. Well i was hoping that the One V would be the same, it was not.
So I tried to install some rom that i liked after going through the unlocking and rooting process,and it had a restarting problem where every 5-15 seconds after it would boot it would restart. I found a solution (kind of) to that but most of the links where dead so i had to find them on my own. It led me to putting a custom kernel on it and that did not fix it, so i saw something that getting the OTA update that came out a while ago could cause this, and the only way to return it was to use RUU (i still had a custom kernel at this point, i think) so i got the (hopefully) correct recovery.img from RUU and i flashed that and the next step is to relock the device, so i did via command prompt, and i started RUU up again and it was doing its thing and ended in an error 155. I have tried several times and it has still not worked. I found some stuff saying that the HBOOT i have which is 1.57 doesnt have a supported RUU or something to that effect ( i found lots of conflicting information).
So now i am stuck with a phone that only goes to the bootloader menu and because its relocked i cant flash anything to it.
I have tried fastboot oem unlock and that came up with a command error, and everything else i try to flash just fails.
Any help is welcome and a thank you in advance to anyone that helps.
Click to expand...
Click to collapse
You should be able to flash a stock RUU for your device while it's in the bootloader menu from here:
http://androidfiles.org/ruu/?developer=Primo
make sure to download the correct RUU for your carrier/radio band and if its GSM (PRIMOU) or CDMA (PRIMOC), or you can screw it up more.
What network carrier are you with?
EDIT:, Just re-read your post, sorry. I don't know if anyone has posted a RUU for the updated radio, that Virgin Mobile released, you may need to get ahold of Football on this forum and see if he's still helping find/sell RUU's that you need.
Back in the day I had to get ahold of him to get the RUU for my phone that wasn't listed on any RUU site.

FreakyFreakGA said:
You should be able to flash a stock RUU for your device while it's in the bootloader menu from here:
make sure to download the correct RUU for your carrier/radio band and if its GSM (PRIMOU) or CDMA (PRIMOC), or you can screw it up more.
What network carrier are you with?
EDIT:, Just re-read your post, sorry. I don't know if anyone has posted a RUU for the updated radio, that Virgin Mobile released, you may need to get ahold of Football on this forum and see if he's still helping find/sell RUU's that you need.
Back in the day I had to get ahold of him to get the RUU for my phone that wasn't listed on any RUU site.
Click to expand...
Click to collapse
I don't really know about buying RUU's, that's like blackberry with their pay to unlock the imei thing. although if it saves me from having to buy a new phone ill consider it.

matterlord1 said:
I don't really know about buying RUU's, that's like blackberry with their pay to unlock the imei thing. although if it saves me from having to buy a new phone ill consider it.
Click to expand...
Click to collapse
I paid like $13 for mine, but it gave me piece of mind should the phone ever soft brick or hard brick with boot, that I can recover it and not lose a phone. I don't know if he's even around anymore, but I posted a thread in general asking if he was. I am on Alltel, but one of my family members bought an HTC One V with the updated radio, so for her I couldn't do anything but root. I know there are a few new radio friendly ROM's in the CDMA section of this forum that would of boot with a custom rom and the kernel.

FreakyFreakGA said:
I paid like $13 for mine, but it gave me piece of mind should the phone ever soft brick or hard brick with boot, that I can recover it and not lose a phone. I don't know if he's even around anymore, but I posted a thread in general asking if he was. I am on Alltel, but one of my family members bought an HTC One V with the updated radio, so for her I couldn't do anything but root. I know there are a few new radio friendly ROM's in the CDMA section of this forum that would of boot with a custom rom and the kernel.
Click to expand...
Click to collapse
yeah i found some ROM's that will work only after this happened. In my research i found something about downgrading HBOOT i only saw it on other phones and it did not look like something i wanted to mess with. And my HTC One V is CDMA on Virgin Mobile.

matterlord1 said:
yeah i found some ROM's that will work only after this happened. In my research i found something about downgrading HBOOT i only saw it on other phones and it did not look like something i wanted to mess with. And my HTC One V is CDMA on Virgin Mobile.
Click to expand...
Click to collapse
UPDATE: So i figured it out, I went and i reflashed the Unlock_code.bin file and now its back to unlocked again. Thanks to FreakyFreakGA to doing his best to help me out.

Be sure to flash an OTA-compatible ROM. Try RhythmicROM or CyanPrimo, both of which I've used for a long time and can attest that they are better HTC One V ROMs.

matterlord1 said:
UPDATE: So i figured it out, I went and i reflashed the Unlock_code.bin file and now its back to unlocked again. Thanks to FreakyFreakGA to doing his best to help me out.
Click to expand...
Click to collapse
so matterlord what rom are you running right now? were you ever able to revert back to stock? I am having the same problem you did.

gotts101 said:
so matterlord what rom are you running right now? were you ever able to revert back to stock? I am having the same problem you did.
Click to expand...
Click to collapse
I never tried to go back to stock, I'm running rhythmic ROM, can't link right now but it seems to work pretty well, its slightly faster than stock when all my stuff is on there and the only problem so far is sometimes when you lock the device and then quickly unlock it then it will freeze and restart.

matterlord1 said:
I never tried to go back to stock, I'm running rhythmic ROM, can't link right now but it seems to work pretty well, its slightly faster than stock when all my stuff is on there and the only problem so far is sometimes when you lock the device and then quickly unlock it then it will freeze and restart.
Click to expand...
Click to collapse
Yeah I just flashed Rhythmic. Seems pretty nice by my wifi is having some weird authentication problem. It doesn't seem like there are very many ROMs out there that would work though.

gotts101 said:
Yeah I just flashed Rhythmic. Seems pretty nice by my wifi is having some weird authentication problem. It doesn't seem like there are very many ROMs out there that would work though.
Click to expand...
Click to collapse
Yeah, make sure you find the right version for your radio, virgin mobile made a terrible move by updating it so you cant do much with it.
Or kernel or something, anyways mine was v5.2 and it was a pain, i think there was a lot more kernels available for older versions.
Best of luck, and if you are having problems with authentication then try using WPS, in some cases it fixes those types of problems.

Pissed Off Desire HD

Hi everybody, I was thinking whether to open new "story" or not and I thought I can do it by myself..but..I did everything I could, I have read hundreds of forums..some things totally confused me and some simply I don't understand..so however I decided to open new thread because I really need professional help here.
Here is the story,
I've bought used HTC DHD before two days with an custom rom android 4.2.2 but WI-FI not worked and also camera not worked very well (when I take a shot phone turns off). i have tried few roms in hope that will fix the problem (PACman v23, CM10.1 and JT 4.2.2 - and still on JT) but nothing. In bootloader says Unlocked but security is damn ON. So, I worked two whole fckin day without success. I have tried many tools, guides etc but it simply won't make S-OFF. Also I've tried to flash to few stock RUU roms to do a downgrade but every time when try I'm getting some errors (140, 150, 170 or even unknown error xD). I really don't know what to do anymore and because I'm pissed off I came here. I love this phone and I won't sell it third day already. I gave last money for this smartphone..I won't money back..I won't new phone..I just want this to be working device. On pic you can see what I already tried..
So please, be patient and take your time to solve this **** together.

Come on guys, I know this can be fixed. I need just little of your time. and thank you very much in advance.

NO idea why you so desperately want S-OFF in the first place as you can flash custom ROMS without it and there is no other way you can fix wifi on software level (so most probably it's a hardware problem), but anyone have access to search in the upper right corner if you wish.
As for the phone shutting down when taking photos, it's a common problem and is thought to be related to aging battery, but you have a great chance of fixing(compensating) it by increasing CPU voltage a couple of notches. Install CPU Master and increase the mV of corresponding maximum frequency used, it should be 1Ghz to look at if not overclocked, try to increse it by 50mV

You are unlocked and still s-on so, as with every one who has issues like yours, you need to flash the boot.IMG via fastboot from the ROM you want to install, after you've installed the rom.
I suggest switching to SVHD by mygamers, every thing works, its super smooth and is great on battery too.
P.s. unless you REALLY really need the advanced functions of s-off, I wouldn't worry to much about it.
"Some" advantages to unlocked bootloader and s-off are:
Flash new Roms direct with out having to flash boot.img
Restore nandroids that are different from current installed rom easier
Flash radios
Change splash screen (you may only see it when you turn on phone, but it can be awesome thing to show off a bit)
Sent from my GT-I9505 using xda app-developers app

First, why do you need S-Off? You can flash ROMs without S-Off, and S-Off won't fix your WiFi problems. It's not clear whether you're successfully flashing ROMs right now, but you can. You do need to flash the ROM zip's boot.img from fastboot each time after you flash s ROM from recovery.
Second, please bump a thread only once every 24 hours per the forum rules.

It's pretty damn clear that he have tried other ROMS.
dante.24 said:
i have tried few roms in hope that will fix the problem (PACman v23, CM10.1 and JT 4.2.2 - and still on JT)
Click to expand...
Click to collapse

-SmOgER said:
It's pretty damn clear that he have tried other ROMS.
Click to expand...
Click to collapse
But he finishes that line with "but nothing." Given the number of "flash the boot.img" posts I've had to write lately, I was wondering if that meant he managed to get them to boot or not.

Sorry guys that I did't mentioned before but mainly what I want to do is to bring back stock rom but I can't..someone said that I need S-OFF for that, I heard that when you flash stock rom can fix wi-fi and camera and then if you want can install new custom rom after. About damaged hardware, everything is possible. I was in service shop and guy there said that hardware is modem in essence that controling wi-fi, GSM, bluetooth and GPS. Maybe I understood him wrong. But my BL and GSM working just fine. I have to try new step-by-step tutorial, I'll be back soon.

dante.24 said:
Sorry guys that I did't mentioned before but mainly what I want to do is to bring back stock rom but I can't..someone said that I need S-OFF for that, I heard that when you flash stock rom can fix wi-fi and camera and then if you want can install new custom rom after. About damaged hardware, everything is possible. I was in service shop and guy there said that hardware is modem in essence that controling wi-fi, GSM, bluetooth and GPS. Maybe I understood him wrong. But my BL and GSM working just fine. I have to try new step-by-step tutorial, I'll be back soon.
Click to expand...
Click to collapse
You don't need to get S-Off. Just relock your bootloader with fastboot and run the RUU executable from your computer while the phone's connected to it.

bananagranola said:
But he finishes that line with "but nothing." Given the number of "flash the boot.img" posts I've had to write lately, I was wondering if that meant he managed to get them to boot or not.
Click to expand...
Click to collapse
OK, let's clear this. Every rom I've tried worked but wi-fi not again, camera is little stable in JT 4.2.2. Only rom that not worked was JT 4.3 beta 3. Installed very well but when it boots it stays on splash screen forever.

bananagranola said:
You don't need to get S-Off. Just relock your bootloader with fastboot and run the RUU executable from your computer while the phone's connected to it.
Click to expand...
Click to collapse
OK, I'll try it..

Locked bootloader as you said, started exe from PC and I got error 131 "CUSTOMER ID ERROR"..what's that??

You need to find a RUU compatible with your phone's region.

bananagranola said:
You need to find a RUU compatible with your phone's region.
Click to expand...
Click to collapse
How can I know that man, when I try to flash RUU it says "would you like to update from 3.13.000 to 3.13.405.12"..something like that..Ive already tried two stock roms.
Edit: I've tried WWE and ARA RUUs, do I need to try US and UK versions too??

dante.24 said:
How can I know that man, when I try to flash RUU it says "would you like to update from 3.13.000 to 3.13.405.12"..something like that..Ive already tried two stock roms.
Edit: I've tried WWE and ARA RUUs, do I need to try US and UK versions too??
Click to expand...
Click to collapse
You could make a goldcard to run any RUU, or you could try the US or UK RUUs.

-SmOgER said:
It's pretty damn clear that he have tried other ROMS.
Click to expand...
Click to collapse
Excuse me, but its "pretty damn clear" that only jellybean roms have been tried!
Why are you getting so agro (agrovated for non Aussie readers)) at the mention of trying to use something other than jellybean?
Only trying to help someone out, mate, have you got issues or you got some reason for hating!
Sent from my GT-I9505 using xda app-developers app

umm if your stuck on splash screen you haven't flashed the kernel. Extract the zip, then place the boot.img into your adb folder. Reboot your phone into hboot then fastboot. Now go to your adb folder type in fastboot flash boot boot.img from cmd.
If that doesn't work to achieve s-off on newer versions of android is 1) Make a goldcard 2) Downgrade with a ruu 3) Get root exploit 4) Get s-off exploit (This was back in 2010 so I don't know if the procedure changed but I s-offed with this. It's probably easier since its 2013:silly
For future reference, Unlocked bootloader means the boot.img is restricted from recovery YOU need to flash kernels via fastboot with Unlocked Bootloader, S-OFF means nothing is restricted apart from splash image, ENG-Soff is engineering mode is same as s-off but with a Eng tag and splash screen is changeable.
Click to expand...
Click to collapse

ranger4740 said:
Excuse me, but its "pretty damn clear" that only jellybean roms have been tried!
Why are you getting so agro (agrovated for non Aussie readers)) at the mention of trying to use something other than jellybean?
Only trying to help someone out, mate, have you got issues or you got some reason for hating!
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
First of all there was no any hate nor any of this "agro" of yours lol.
Secondly, none of the mentioned JB ROMS have wifi issues, so there is really no point in wasting time and trying every available ROM.
Cheers and I hope you now got it, we all learn from our mistakes, don't beat yourself up too much. :laugh:

Thanks dude, I'll try it. I have GC tool but problem is this site revskills are down and can't get .img file. Any alternative for this?

-SmOgER said:
First of all there was no any hate nor any of this "agro" of yours lol.
Secondly, none of the mentioned JB ROMS have wifi issues, so there is really no point in wasting time and trying every available ROM.
Cheers and I hope you now got it, we all learn from our mistakes, don't beat yourself up too much. :laugh:
Click to expand...
Click to collapse
I must say, your a total gentleman to clear that up, it is my mistake to believe we are not playing nice and trying to help each other out here, without deliberately flaming or being just simply malice towards fellow xda members...
Don't worry I won't beat myself up to the point I need hospital admission even though that is where I am right now.
Cheers my xda friend I got it now! :thumbup:
Sent from my GT-I9505 using xda app-developers app

?Hard Brick "QHSUSB_Bulk" TMO M8

Hi everyone.
I hope it's OK for me to post a thread here. I had posted in the TMobile specific help forums yesterday but I noticed that these forums are much more active and I have a somewhat new problem.
My phone is intermittently connected to windows and listed as "QHSUSB_Bulk". I've come across some help threads on this issue for other phones that I'm working through, but I was really hoping to perhaps get some M8-specific guidance. I'm supposed to be studying for my medical boards right now, so I'd really appreciate some help that could save me some time.
Here's the thread that I posted yesterday: http://forum.xda-developers.com/tmo...ruu-error-152-unable-to-restore-tmob-t2869758
(mods please move/merge/close if appropriate).
Thanks!
PDD

PasDeDeux said:
Hi everyone.
I hope it's OK for me to post a thread here. I had posted in the TMobile specific help forums yesterday but I noticed that these forums are much more active and I have a somewhat new problem.
My phone is intermittently connected to windows and listed as "QHSUSB_Bulk". I've come across some help threads on this issue for other phones that I'm working through, but I was really hoping to perhaps get some M8-specific guidance. I'm supposed to be studying for my medical boards right now, so I'd really appreciate some help that could save me some time.
Here's the thread that I posted yesterday: http://forum.xda-developers.com/tmo...ruu-error-152-unable-to-restore-tmob-t2869758
(mods please move/merge/close if appropriate).
Thanks!
PDD
Click to expand...
Click to collapse
bricked, sorry

rbouza1 said:
bricked, sorry
Click to expand...
Click to collapse
What do you think about this sort of thing: http://forum.xda-developers.com/showthread.php?t=2582142
I'm trying to find the other thread I was referring to where the guy said his phone was in the same state as mine but was able to recover it. Edit: Ah it was this thread, but was applicable when I had Error 152, not QHSUSB. http://www.xxxx.com/htc-one-x/help/error-152-ruu-update-t2861685
Do you have any tips for avoiding this problem in the future?
I'll probably have to return, just want to learn at this point.
Thanks! PDD

PasDeDeux said:
What do you think about this sort of thing: http://forum.xda-developers.com/showthread.php?t=2582142
I'm trying to find the other thread I was referring to where the guy said his phone was in the same state as mine but was able to recover it. Edit: Ah it was this thread, but was applicable when I had Error 152, not QHSUSB. http://www.zpiiets.com/htc-one-x/help/error-152-ruu-update-t2861685
Do you have any tips for avoiding this problem in the future?
I'll probably have to return, just want to learn at this point.
Thanks! PDD
Click to expand...
Click to collapse
I don't know what you did to get there, be careful with firmware and hboots.

rbouza1 said:
I don't know what you did to get there, be careful with firmware and hboots.
Click to expand...
Click to collapse
Tried to run an RUU. Thought it would be the safe route ha!

PasDeDeux said:
Tried to run an RUU. Thought it would be the safe route ha!
Click to expand...
Click to collapse
did you unplug phone before finishing ?

rbouza1 said:
did you unplug phone before finishing ?
Click to expand...
Click to collapse
Nope. I gave a pretty detailed summary of stuff that happened before the phone became unresponsive in the thread from my OP. I think the main problem was thinking I could update versions since the RUU said it "update." Should have stuck with same version RUU. Don't know why that would completely brick the phone, though. And it only bricked after the time I ran it and it said "congrats everything worked!"

RUU are normally the safest way to flash devices. If it was bricked because of it. It could be any number of things.
Corrupt RUU
Premature disconnect from either end
Or bad emmc table
I went through three m8 first two ended up in QHUSB mode and the third after playing it safe for while attempted again and it worked out just fine. All I was trying to do was flash the international 4.4.3 firmware zip.
First two came from T-Mobile while the third HTC sent it out to me. So maybe that made a difference, I did change the model and CID to that of the international version the third time so if that made a difference I wouldn't know for sure.

wifi broken, help please!

Silly prob, just developed from nowhere. If my wifi is either switched off manually or by itself it cannot be switch on again. Found a painful way around it and that is to reboot into recovery, delete dalvik cache and cache, reboot again and its there. Obviously this is annoying process so am hoping some one has experienced this same issue an found a fix. Or someone knows whats happening.. thx:good:

Can you post the output of fastboot getvar all (removing the IMEI and serial number) and also which ROM you're using?

Because Lollipop requires the new firmware so if you're now using a Lollipop ROM it's more than likely your issue (you've not mentioned either so I'm making assumptions but because of how rude you have been I don't really care). Next time I won't bother but trust me, I wouldn't have if I didn't know what I was on about. Have fun fixing it yourself

veroby said:
Harden up, don't be so sensitive, read, understand, then write.
Click to expand...
Click to collapse
Exactly what eddy says. You came here for help.....we didnt ask you to come here.
And you seem to know which advice will be given, if you are that good why don't you write in the OP what you already know about the issue and provide logcats so we can dig through them to spot some error maybe. Ever thought about that ?
If i were you i would say : thanks for the reply eddy but ...... etc etc. This kind of "a developer is qualified to help" attitude won't get you far here. At the end of the day it's not our device that needs a fix.
Happy fixing

Moderator Information,
Thread has been cleaned. For info the older firmware does not work with the newest versions of Android. This is because the wifi drivers were changed in the newer version. The only fix is to update the firmware, this can be done via s-off methods or going back to stock and flashing the latest OTA.
Here is a good link for updating the firmware:
[2015.02.08][GUIDE] FUU and Firmware flashing

Im still abit new to XDA so forgive me for any rookie errors. Just like Veroby, I am also having wifi issues, I am aware that you need to upgrade firmware to upgrade to Lollipop but since I'm S-On only option for me is to revert to stock using a Stock Nandroid Back up of my cid (OPTUS001) from Mr Hofs thread, to go back to stock, which worked fine, but after doing 1 OTA update, my wifi will stop working! Same as what veroby describes. Help us out guys! Will provide information if required.

mgarces024 said:
Im still abit new to XDA so forgive me for any rookie errors. Just like Veroby, I am also having wifi issues, I am aware that you need to upgrade firmware to upgrade to Lollipop but since I'm S-On only option for me is to revert to stock using a Stock Nandroid Back up of my cid (OPTUS001) from Mr Hofs thread, to go back to stock, which worked fine, but after doing 1 OTA update, my wifi will stop working! Same as what veroby describes. Help us out guys! Will provide information if required.
Click to expand...
Click to collapse
Open your own thread. Your case is about restoring a backup on wrong hboot.
Not going to respond further here.

Info regarding what can be flashed to VZW M9's

Hey guys, this is my first HTC device. I've been reading through the threads here and in the intl forum and I just wanted to get a little info in one place as to what we can flash for this device. I sent mine off to someone with a Java Card, so now that I'm good to go, I wanted to see what all I (and other VZW users) can do at this early stage in the game. I know that until there is an easier way to S-Off/root/etc than sending your device to someone it is still kinda rocky as to development on this particular device, but I've heard mixed reviews on what ROMs/kernels are good to flash.
I assume that as long as I've got a custom recovery, flashing ROMs on this device would be the same as the other devices I've used... just pick the file in TWRP and flash, right?
As far as ROMs go, I've read that ViperOne works, along with InsertCoin with nothing extra.. just flash and go apparently. As for other ROMs, a little editing and some files from the stock VZW ROM should make them work, right? What files exactly would be needed?
Basically, if you've flashed anything, post your results here. What works, what doesn't, anything I should do before I start flashing myself. Any good threads I should read before I jump in. Thanks guys!

I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.

jtommyj said:
I have a thread about the roms in this forum named VZW M9 roms.
Basically the ones you've named I've tried with success. Also LeeDrOiD rom added Verizon support today. Build 7.5.
Click to expand...
Click to collapse
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.

lordcheeto03 said:
I never claimed to be a genius I've read through your thread, that's where I got the ROMs that worked... My brain wasn't working at full capacity when I made the thread. Thanks.
That being said though, lets assume that a soft-brick occurs. How would one go about fixing that? In my experience with the S4 and the device I had previous to that, it was simple to fix a soft-brick as long as I still had recovery access. Would the same be true for the M9? What about reverting to stock.. as in stock recovery, firmware, etc. Also, from what I've seen, adb tends to be used a bit more for this device than others that I'm used to. Not that I have a problem with it, I just haven't used it very much and will likely have to brush up a little bit on the nuances of it. I just don't want to create a $650 paperweight so I want to be absolutely sure that what I'm doing can be fixed, and that I avoid doing things that CAN'T be fixed.
Click to expand...
Click to collapse
Well first thing you need to have a custom recovery flashed.
Then you would need to backup your stock system. If you are in a soft brick then volume up and power being held at the same time should get you out of it.
There should not be a need to refresh firmware since the original firmware is all we have. I do believe an Ruu is being worked on currently.
Final word- if you're unsure,don't!!