Related
Hope anyone can help me. Has soon tried everything without success. Phone is rooted with bootloader 0.80 Radio. 5.09.00.20 March 29 2010 and defrost system version 4.3
Have bootloader 0.80 which says wrong version when booted, and Touch panel fail sometimes. The phone can boot up sometimes, but after 2 to 3 my phone goes black and can only be started up again by taking out the battery. Is there any possibility to get the phone back to the original as it can be sent for repair. Believe, in fact it could be something hardware does not. If it can not be done, can it be made without it costing more than a new phone
Have u tried another rom?
If u want to send it to repair u need this RUU to unroot
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
I use it to unroot mine, but u need to be sure your screen is amoled, this is for AMOLED screen ONLY
Sent from my HTC Desire using XDA App
Thanks for the quick reply. Have tried with another ROM without success. Have tried with a RUU. Unfortunately, the phone will not be in usb mode when i try to sync HTC. Windows writes that there is connection to usb port. Can you get RUU in zip format so it can be loaded via Update.zip / recovery mode. The RUU you recommend that can be used for Danish phones. Whew, lots of questions.
Yes u can install the RUU threw Sdcard, try and find a SAPPIMG containing froyo2.2 or u can try and downgrade to 2.1 and see if the phone works properly, i only have links to the 2.1 here u are:
http://shipped-roms.com/shipped/Bra...8U_4.06.00.02_2_release_126984_signed_txt.zip
1. download the file to SD card.
2. rename to PB99IMG.zip
3. boot into recovery (turn phone on while holding down volume)
4. just let it load the zip file and press yes when asked to install
This will get u back to 2.1 so then u can try OTA updates or running RUU´s again.
manchesterob said:
Thanks for the quick reply. Have tried with another ROM without success. Have tried with a RUU. Unfortunately, the phone will not be in usb mode when i try to sync HTC. Windows writes that there is connection to usb port. Can you get RUU in zip format so it can be loaded via Update.zip / recovery mode. The RUU you recommend that can be used for Danish phones. Whew, lots of questions.
Click to expand...
Click to collapse
Probably u have USB Bricked, look for threads explaning how to fix USB Brick..
Many thanks for your help. Try it during the night. The problems with the phone locks and the screen goes black and can only be restarted by taking the battery out, because it surely wrong bootloader or brincked usb
Have tried to install PB99IMG.zip. Unfortunately, when it only to load up a bit of the column before the phone goes black again, and battery removal to restart. Anyone have an explanation for this. I completely drained of ideas
U seem to have a true brick.I broker my friends magic.
The new jtag riff box can now fix bricked desires
Sent from my HTC Desire using XDA App
Sounds like there weren't any ideas in Q&A for this one, and I haven't seen much in terms of not being able to access recovery, so here goes...
I was happily using CM7, and while reading through a Diablo III news page (hopefully it comes out soon ), my phone rebooted into a boot loop. Weird, but I figured at worst I would wipe data and reinstall a ROM. Unfortunately, I can't get into recovery any longer.
If I boot the phone normally, I see the white HTC splash screen for a few seconds, then it reboots. I can use HBOOT fine, but as soon as I try to reboot normally / boot into recovery / boot into Restore Factory Defaults, my phone will reset. Let me clarify...
Pull and replace battery
Boot into HBOOT (volume down + power)
Select Recovery
Phone reboots and reaches CWM Recovery 3 for about 1/2 second, not long enough for me to click anything
Phone reboots into boot loop
I've used HBOOT to flash to CWM Recovery 3.0.0.8, downgraded to the stock radio, run the 2.2 RUU. I'm still running up against the same boot loop problem.
I wouldn't be surprised if it was a hardware problem, but I'm anxious to hear if anyone has ideas to try first. Additionally, is there any way to restore to S-ON through HBOOT in case I need to bring this into a Verizon store? I have fastboot.exe that can recognize the device over USB while the device is in HBOOT, maybe this will help?
Thanks!
Current state: Ran 2.2 RUU, S-OFF, HBOOT-0.92.0000, AMOLED, 2.15.00.07.28 radio
Thanks again.
Had this exact issue while running cm7. First couple of from when it was crackflashers. I couldn't find anything to help or fix it. I got a new dinc because I can't afford to be without for long.
Good luck dude.
Sent from my ADR6300 using Tapatalk
Thanks for the note. Maybe my fate will be the same. Did you get any sympathy from Verizon?
Doesn't sound like there are even any suggestions using fastboot, lol. [crickets chirping]
Can you flash cwm 2.5.x and try? Not sure if it will help but worth a shot?
sent from a phone
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into bootloader (volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
hope that helps
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
popasmurfn23 said:
@phazeone let's say he just does that. Now his phone reboots and is on stock and looses his root, now he can root it again and then turn the S-on by the single file flash from recovery mode, and then use the update file again to flash the phone back to normal stock without root ( if he was taking it back) so whenever u want to manipulate the S security u must be rooted correct?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
You are correct.
popasmurfn23 said:
Yeah take out battery, then pull out sd card put it into a adapter and insert it to ur pc. Then find the file that was shipped specifically for ur device it looks something like this PC130mg.zip or some crap like that anyways put that on the root of your sd card. load ur card back to your phone now into hboot(volume down plus power) mode. Your phone will auto detect that file and start to ask if u want to install update say yes boom it will flash back to stock.....however my only concern would be if u need to turn s-ON before u do this.
I did this for a evo 4g and it worked but I turned s-ON first as it was in the instructions I was following. I think maybe the update file checks to see if ur S-off or on. But don't quote me on that.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
phaze one said:
Yeah, I agree with popasmurf. Put the PB31IMG.zip on your sdcard. Then let hboot discover and update it. It'll be back to stock and youll have to reroot but better than a paperweight.
You can find the image here -----> http://dougpiston.com/?page_id=108
I'm assuming you have a dinc.
sent by carrier pigeon
Click to expand...
Click to collapse
Thanks for the replies.
I tried this method to flash back to the stock 2.2 image before I started this thread. That's what I meant by "I've used HBOOT to ... run the 2.2 RUU." The stock image seemed to install properly in HBOOT. I have evidence that it successfully went back to stock, since I get the original ! triangle graphic instead of CWM when I try to enter recovery from HBOOT. However, I only see the graphic pop up for a brief second before it reboots again. Trying to boot into recovery or the ROM itself still result in a reboot.
I cannot achieve S-ON without having access to recovery, at least there's no way that I've found to do it through HBOOT.
Any other thoughts? I think it's a hardware problem. It appears the phone is back to stock (except it's still S-OFF), but everything outside of HBOOT causes a boot loop. I stopped in at Verizon this afternoon and they'll be sending a new phone to arrive by Tuesday. At this point, it'd be nice to try all avenues of repair for the future benefit of others that run into this problem.
Probably bad memory chips on the phone. Since it happened all of a sudden during normal use it usually indicates hardware failure.
That is pretty much what I determined. Bad hardware. Sorry for your trouble but is nice to know I'm not the only person to ever have this. Also nice to know I didn't miss something that could've brought it back to life.
I filed an insurance claim. Figured since I have had it for years and never used it I'd take advantage.
Sent from my ADR6300 using Tapatalk
You can boot your phone like regular right? Just let it launch up or do you get loops?
Nevermind i see what ur saying. when i was flashing incorrect kernals i would get the same behavior from my phone. So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
If that doesn't work, (I'm assuming that you can boot the phone normally at this point) try re-rooting with the Unrevoked tool.
Then use Rom Manager to flash a newer Recovery (be sure to check Erase Previous Recovery under Settings). If that still doesn't work, I'll see about packaging an RUU in a PB31IMG.zip with a valid version of CWM as the recovery.img within that zip. I'm not sure about the practicality of this final option, but if it comes down to it, I'll attempt to package that up for you.
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Sent via my Incredible CM7 Gingerbread sorcery.
Crans said:
I wonder if he could just wipe that SD card, place a new Rom etc on it and reinstall. Bricking displays no response you've got a better shot at recovering course your SD card/battery could be bad
Click to expand...
Click to collapse
This would work if he could access CWM Recovery, but he can't, thus the issue.
I wonder if he could mount something from within hboot and replace the binary code for the recovery image with a bunch of zeroes and then try flashing another through hboot again.
Sent via my Incredible CM7 Gingerbread sorcery.
I was JUST about to post the same topic when I came across this. I have done the stock image restore, restored BACK to hboot 0.92, back to the most current INC radio, and have tried flashing CW3.0 and Amon_RA. Everything flashes fine but the boot loop continues and if I try to enter recovery, it lasts maybe one full second before rebooting again. The only thing that I can think of that would create this situation for me was that earlier I was trying to update the PRL via *228 on MIUI but the dialpad never popped up so I hung up.
popasmurfn23 said:
So i suggest you take phazeones link and try that file.Because u might have the incorrect file. There might be more than meets the eye make sure u got the right file.
When i searched for my zip file for my evo there was like 4 of them. They had to match what was said in the upper left corner of my hboot screen. So let me knoe if it worked
Click to expand...
Click to collapse
I'll take another crack at it, but I don't think I had gotten the wrong image. No worries though, it's easy enough to try again using the link on page 1 directly. Can't hurt, right ;-)
RegnierD said:
Since you're trying to flash the 3.x.x.x version of CWM, that may be your issue. Here's a zip for 2.5.0.5, one of the most stable earlier Recoveries. Flash through hboot as per usual.
Click to expand...
Click to collapse
Sure. Once again, worth a shot.
RegnierD said:
This sounds incredibly frustrating. Thus my interest in the matter.
There's gotta be a way to fix this... even if it's just long enough to get S-On and keep your warranty valid.
Click to expand...
Click to collapse
Thanks for the sympathy . Like I mentioned, I visited the Verizon store and a new one is on its way... doesn't that mean that it doesn't matter (other than for science sake) whether this gets S-On or even fixed?
[waiting for flash of build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
It just seems unlikely that this is a problem with flashing the wrong recovery, or the wrong stock image, since booting into recovery and booting normally both exhibit the same behavior. If I could boot normally into recovery but not boot into a stock image, I would suspect that I had flashed the wrong image. Since both have the same problem, I think it might be something else.
[finished flashing build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip]
Same behavior. White htc Incredible splash screen -> darkness for a second (presumably while the ROM tries to boot) -> reboot.
Alternatively, HBOOT -> Recovery -> White htc Incredible screen -> Triangle / ! error screen for a half second -> reboot.
[finished flashing CWM 2.5.0.5]
Same behavior:
HBOOT -> Recovery -> White htc Incredible screen -> CWM recovery 2.5.0.5 for a half second (this confirms that it flashed properly) -> reboot.
Hello,
I have for quite some time used leedroids rom lately the the hd port.
That rom has been a little bit unstable but no real big issue. Now however my
phone has gone totally bonkers.
I have leedroids http://forum.xda-developers.com/showthread.php?t=1038195 due to that i tried to solve the issue. Using the a2sd+ version. Tried the alignment patch etc and spend more or less the entire day studying the forum.
The issue is that the phone is highly unstable.
Most often the alpha rev joker image just keeps rebooting after the joker show up, or it just sit's there. If i pull the battery for a while like a few minutes the phone often boots up but after a while it reboots again. Faster if i open an app. Especially the market app then i get almost an instant reboot.
Did a full wipe ofcourse when installing the rom, did a checkdisk on the sdcard and got new partitions for it both primary of course etc.
I just cant seem to figure out what the error might be. Only thing i havent tried is to install the stock rom. Mainly because i'm not quite sure which one i should use. So if someone could please provide a link the the proper one i would be gratefull. Rooted and s-off one would be good. I'm on the 3 network in sweden but i think they use the standard rom.
no errors while installing
hboot 0.93
Anyone got any ideas?
Well you should start by flashing any other rom using a full wipe.
If that doesn't cut it, you should try to install a htc one. This can be easily done if you are s-off. You should install the latest alpharev hboot with stock partition-layout. Then you can flash a ruu thile staying s-off. Please write back for further help, if the first option didn't help you.
mortenmhp said:
Well you should start by flashing any other rom using a full wipe.
If that doesn't cut it, you should try to install a htc one. This can be easily done if you are s-off. You should install the latest alpharev hboot with stock partition-layout. Then you can flash a ruu thile staying s-off. Please write back for further help, if the first option didn't help you.
Click to expand...
Click to collapse
Is there a way to flash the latest alpharev without having the phone booted? In recovery for example? It's a bit dangerous i noticed cause if my phone crash in the middle of flashing that i would probably be bricked i think. But i'm already s-off though should i do it again to get the latest?
To put it simple yes there is a way to do it without being booted.(actually that is the only way you can't do while booted to the system)
And no you should not run the tool itself again. When you are already s-off you can just download a new hboot image from their website and flash it directly. Download:
http://alpharev.nl/bravo_alphaspl.img
And flash it by following my directions given here:
http://forum.xda-developers.com/showthread.php?t=1248910
You will need to have the sdk installed beforehand.
mortenmhp said:
To put it simple yes there is a way to do it without being booted.(actually that is the only way you can't do while booted to the system)
And no you should not run the tool itself again. When you are already s-off you can just download a new hboot image from their website and flash it directly. Download:
http://alpharev.nl/bravo_alphaspl.img
And flash it by following my directions given here:
http://forum.xda-developers.com/showthread.php?t=1248910
You will need to have the sdk installed beforehand.
Click to expand...
Click to collapse
doesn't seem to be able to connect it via adb. tried the zipfile thing too but it wouldn't allow to install the file using the recovery tool.
Also it seems to be able to boot if i pull the battery for a long time. But as soon as it seems to heat up a bit poof it goes into a reboot. Could there be something wrong with the battery so it get's to hot and reboots?
Might be but you need to be back to stock in order to know for sure. Lets just drop flashing another hboot and return it completely to stock(i don't have time to guide you through that process right now) then you can always reroot afterwards.
Just download the gb ruu here: http://www.htcdev.com/process/legal_download/152
In order to flash it, boot up in the bootloader by holding vol down and pressing power. Then connect it by usb and run the ruu.
mortenmhp said:
Might be but you need to be back to stock in order to know for sure. Lets just drop flashing another hboot and return it completely to stock(i don't have time to guide you through that process right now) then you can always reroot afterwards.
Just download the gb ruu here: http://www.htcdev.com/process/legal_download/152
In order to flash it, boot up in the bootloader by holding vol down and pressing power. Then connect it by usb and run the ruu.
Click to expand...
Click to collapse
Ok great thanks, trying cyanomod now to see if i get the same issues. But i put the phone in the fridge for a few minutes, then it booted just fine and i put set cpu to powersave and phone didnt get hot and no reboot. So gonna try cyano and see if the same happends. Will try full stock when i wake up tommorow. Thanks for the help
ok got reboot on cyano too
It seems to be the famous boot loop problem in HTC desire .
To confirm flash the original RUU, if the problem persist then your mainboard has developed fault.
Sent from Hell
Got it to work for a few hours this morning. Had it turned off and charged it to full during the night. Worked for some 2-3 hours and then reboot.
mortenmhp said:
Might be but you need to be back to stock in order to know for sure. Lets just drop flashing another hboot and return it completely to stock(i don't have time to guide you through that process right now) then you can always reroot afterwards.
Just download the gb ruu here: http://www.htcdev.com/process/legal_download/152
In order to flash it, boot up in the bootloader by holding vol down and pressing power. Then connect it by usb and run the ruu.
Click to expand...
Click to collapse
Ok tried this now, had the battery charged over night also, when i tried to install it it says battery below 30% but he battery has full charge :S
I think I bricked my HOX.
I have custom recovery installed and lots of battery left. I tried to install a new rom (android revolution) and it worked fine, then I noticed that I had lots of left overs on my sd card from earlier installations. So I decided to format it and cleaned /data /system and /cache. The result is that the phone is stuck at "HTC - Quietly brilliant".
Is there anyway possible for me to connect the phone to the usb and transfer the rom files again to flash them?
Or what should I do to have my phone working again.
I have read the guide and I am currently downloading a RUU file, but I prefer not to lock the bootloader > revert to stock > flash rom again.
Please advice,
Samiii2 said:
I think I bricked my HOX.
I have custom recovery installed and lots of battery left. I tried to install a new rom (android revolution) and it worked fine, then I noticed that I had lots of left overs on my sd card from earlier installations. So I decided to format it and cleaned /data /system and /cache. The result is that the phone is stuck at "HTC - Quietly brilliant".
Is there anyway possible for me to connect the phone to the usb and transfer the rom files again to flash them?
Or what should I do to have my phone working again.
I have read the guide and I am currently downloading a RUU file, but I prefer not to lock the bootloader > revert to stock > flash rom again.
Please advice,
Click to expand...
Click to collapse
What is stoping you from booting into recovery, plugging it in via USB and sticking a new ROM on there... Sorry if I'm wrong, don't have the phone yet but seems like what I'd try to do...
bortak said:
What is stoping you from booting into recovery, plugging it in via USB and sticking a new ROM on there... Sorry if I'm wrong, don't have the phone yet but seems like what I'd try to do...
Click to expand...
Click to collapse
I am trying, but the phone is not showing up in my explorer so I can not transfer any files?? Tried both in recovery and in the stucked mode. However I might be doing it wrong?
Samiii2 said:
I am trying, but the phone is not showing up in my explorer so I can not transfer any files?? Tried both in recovery and in the stucked mode. However I might be doing it wrong?
Click to expand...
Click to collapse
When you boot into recovery do you not have an option to toggle USB storage when you plug the phone in via usb?
bortak said:
When you boot into recovery do you not have an option to toggle USB storage when you plug the phone in via usb?
Click to expand...
Click to collapse
There is an option under Mounts and storage menu in CWM that allows me to "mount UBS storage" However it is not working and returning an error, "Unable to open ums lunfile (No such file or directory)"
I guess boot into bootloader and then push your desired .zip over...
Sent from my HTC One X using xda premium
USB is not yet working in recovery for the HOX, I don't see any other option then going back to stock....
Send from CM9 powered Galaxy Note
Klyupp said:
USB is not yet working in recovery for the HOX, I don't see any other option then going back to stock....
Send from CM9 powered Galaxy Note
Click to expand...
Click to collapse
Oh, well in that case the only reasonable thing would be to also disable the "erase sd-card" feature also, to prevent issues like this
Woaahh just saw your signature, you got a 4s over the SGS II? (I'm guessing) ohh dearrr
why did you format /system? ROFL thats ur problem right there.
Your only options are
a.) wait till recovery is released w/ USB mounting currently there is none.
b.) obtain the correct official HTC RUU (HTC vendor tool) and flash in fastboot. This WILL WORK but you need the exact correct RUU for your specific build
c) use adb push commands
And btw bricked means the phone is completely dead, you can boot but not in rom
Sent from my HTC One X using xda premium
Ok, i got this baby running again. Have to say it was real dead at one time too. No battery left and no possibility to charge. Promised myself not to play anymore with it if I bring it back to life again.
However, I read somewere that I could use the iphone charger to get some batterylife to boot it and it sure worked. Left it on and the next day the light was green on the phone. My face went from to
With full battery I downloaded the 1.29 RUU but it still didnt work. Read somewere else agian that I had to relock the phone again to be able to use the RUU. So I did and it sure worked. Brought it back to stock and here I am again with a working phone in my hand.
I couldnt stay away from ARHD so I unlocked the bootload again, flashed it and customized
Must be real real hard to brick this phone completely!
Hi guys, well I'm a new HTC One X owner and I just jumped ship from the iPhone. I had jailbroken my iPhone several times with only minor problems in the past so I thought I'd give it a try on the One X. Unfortunately, I think I've really screwed something up and now when i boot it up, it vibrates and then hangs at the HTC Quietly Brilliant screen. So here's what I did:
I downloaded Hasoon2000's HTC One X All-In-One v.1.1 kit. I followed the instructions and as far as I could tell, everything worked fine. The bootloader was unlocked and I was able to root the phone. However, after installing a couple of apps which all crashed when I tried to run them (it made the phone restart), I decided to do a factory reset and do it again. So i held onto the power button + volume down and went into the Bootloader and tried to reset it which then took me to the CWM 5.8.4.0 screen. I then did the factory reset there which led me to where I am now.
Could someone please tell me where to proceed from here to bring it back up and running normally again? As you can probably tell, I know next to nothing about Android so I would really appreciate some patience and step by steps. I've already scoured Google looking for a solution but I could never understand what people were talking about. If you need any more information to give you a better diagnosis, please let me know and maybe tell me how to find the information
Thanks a lot people, any help would be much appreciated!
MarcusJKX said:
Hi guys, well I'm a new HTC One X owner and I just jumped ship from the iPhone. I had jailbroken my iPhone several times with only minor problems in the past so I thought I'd give it a try on the One X. Unfortunately, I think I've really screwed something up and now when i boot it up, it vibrates and then hangs at the HTC Quietly Brilliant screen. So here's what I did:
I downloaded Hasoon2000's HTC One X All-In-One v.1.1 kit. I followed the instructions and as far as I could tell, everything worked fine. The bootloader was unlocked and I was able to root the phone. However, after installing a couple of apps which all crashed when I tried to run them (it made the phone restart), I decided to do a factory reset and do it again. So i held onto the power button + volume down and went into the Bootloader and tried to reset it which then took me to the CWM 5.8.4.0 screen. I then did the factory reset there which led me to where I am now.
Could someone please tell me where to proceed from here to bring it back up and running normally again? As you can probably tell, I know next to nothing about Android so I would really appreciate some patience and step by steps. I've already scoured Google looking for a solution but I could never understand what people were talking about. If you need any more information to give you a better diagnosis, please let me know and maybe tell me how to find the information
Thanks a lot people, any help would be much appreciated!
Click to expand...
Click to collapse
Did you flash a custom ROM?
as long as u can see the HTC logo ur phone is not bricked. Its a soft-brick.
just find an official firmware and flash it from recovery...ur One X will b up and running!
dr9722 said:
Did you flash a custom ROM?
Click to expand...
Click to collapse
Sorry, I'm embarrassed to say that I'm not sure exactly what you mean. By that, do you mean did I install a non-stock OS? If so, then the answer would be no. I did flash the recovery with CWM 5.8.4.0 but I have a feeling that, that's not what you meant.
realzahed said:
as long as u can see the HTC logo ur phone is not bricked. Its a soft-brick.
just find an official firmware and flash it from recovery...ur One X will b up and running!
Click to expand...
Click to collapse
Thanks a lot man! Could you...please tell me how to do that? I saw a few threads discussing soft-bricks and they suggested downloading some stuff and then plugging the phone into the PC and typing some commands into cmd. But when I connect my phone into my PC i get no response, even when I'm in the Bootloader screen.
And also, does it matter which version of the official firmware i get? I saw people mentioned RUU files but it had to match my phone's version. Does this have anything to do with that?
I believe you should just plug the phone and run your factory ruu and that would do it and bring the phone back to stock.
Heres where u can get the ruu, am not sure whats the codename for the international hox but i think this is it. Please make sure you are using the correct ruu for your phone.
http://forum.xda-developers.com/showthread.php?t=1543604
Sent from my HTC One XL using xda premium
You should probably read up before trying this again. If you can hold the power button and volume down. It should bring you into a menu. You should press the volume down button until fast boot is highlighted and then press the power button to select it. Download htc sync and install the drivers. Go to the one x development section and download the ruu for your device. Then run the ruu.
Sent from my iPhone using Tapatalk
Thanks a lot for the responses guys. That link you gave me says that they are ROMs for Endeavor, is that the same as a ruu? And also, how do i figure out which ruu is right for me? I'm in Switzerland and my carrier is Orange but I see several ruus there under orange but none of them are for Switzerland and there are even different version numbers. In my current state, is there a way for me to find out which version I need?
By the way, when I try to connect my phone to my PC in fastboot mode and open cmd prompt and type in "fastboot getvar cid", i get "'fastboot' is not recognized as an internal or external command, operable program or batch file." If i click Fastboot on my phone and then HBOOT whilst plugged into the PC, i get a few lines on my phone saying that it "Failed to open USB master mode" and then "please plug off USB".
MarcusJKX said:
Thanks a lot for the responses guys. That link you gave me says that they are ROMs for Endeavor, is that the same as a ruu? And also, how do i figure out which ruu is right for me? I'm in Switzerland and my carrier is Orange but I see several ruus there under orange but none of them are for Switzerland and there are even different version numbers. In my current state, is there a way for me to find out which version I need?
By the way, when I try to connect my phone to my PC in fastboot mode and open cmd prompt and type in "fastboot getvar cid", i get "'fastboot' is not recognized as an internal or external command, operable program or batch file." If i click Fastboot on my phone and then HBOOT whilst plugged into the PC, i get a few lines on my phone saying that it "Failed to open USB master mode" and then "please plug off USB".
Click to expand...
Click to collapse
That probably means fastboot is not properly installed in your pc.
Sent from my HTC One XL using xda premium
joker96 said:
That probably means fastboot is not properly installed in your pc.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
okay, I didn't realise I had to install fastboot on my PC. So i just configured it following the directions here: http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
and now when my phone is hooked up to my PC and i type "fastboot getvar cid" into cmd prompt, i get this:
cid: None
finished. total time: 0.004s
So what does this mean?
Download an app from the marketplace and see what that comes up with. Also go into settings about phone software information then software number. What is the software number?
ste1164 said:
Download an app from the marketplace and see what that comes up with. Also go into settings about phone software information then software number. What is the software number?
Click to expand...
Click to collapse
My phone can't get past the opening splash screen, you know where it says HTC Quietly Brilliant? It just stays there, so I can't go into marketplace or check my settings,
You are going to need to find out wich ruu version u need. I dont know how carriers identify themselves on europe. After you identify it get into the bootloader menu get on fastboot and the open the ruu you downloaded the software should do everything by itself. Btw if you do this your going back to stock that means no root no cwm or wtever you had your going to have to do everything again but at least you got the phone working. Once you identify the ruu you need i would not download the latest version just in case the carrier fixed the root method or something. Again i dont know much about how europe works and how bossy carriers are about rooting/unlocking bootloader. You can try asking on that same thread for the one you need. Someone elsr might have an answer. Good luck.
Ps. Am not sure if you are going to need to relock the bootloader in order for the ruu to run. Can someone shed some light on this?
Sent from my HTC One XL using xda premium
Btw before you do that have you tried getting on the recovery??? Can you get on cwm?? If u can do that i believe there no need to flash the ruu instead just flash a different rom maybe??? Did you get to make a backup before this happened??
Sent from my HTC One XL using xda premium
Thanks a lot joker96. I can get into CWM, so how would i flash a different rom? Unfortunately, the only backups I made are of my personal files and apps, I didn't think to backup anything else.
What were you trying to do that made all this happen?
Sent from my HTC One XL using xda premium
Oh derp sorry I completely forgot. You would download a different rom and follow the guides on the thread to install it. Wipe davlik cache, cache and data. Try ARHD.
Sorry, i didnt read the first post completly. So you did a factory restore wipe on cwm, am i correct? You didnt clear cache and dalvik?
Sent from my HTC One XL using xda premium
ste1164 said:
Oh derp sorry I completely forgot. You would download a different rom and follow the guides on the thread to install it. Wipe davlik cache, cache and data. Try ARHD.
Click to expand...
Click to collapse
What do you mean "different rom"? As in a different rom to the one I had? And what's ARHD?
joker96 said:
Sorry, i didnt read the first post completly. So you did a factory restore wipe on cwm, am i correct? You didnt clear cache and dalvik?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Well the thing is, I'm not 100% sure what I did. First I did a factory reset on CWM and everything worked fine, but when my phone rebooted, I realised CWM was still there. What i wanted was to go back to square one, as in no recovery and no root. So i went back into recovery and wiped some other stuff, and that's when this happened. I know, I'm a total idiot, I don't know what i was thinking
Yea a different rom to what you had maybe that one had problems. ARHD is Android Revolution HD any other rom would work though. Just pick one from the development section.
ste1164 said:
Yea a different rom to what you had maybe that one had problems. ARHD is Android Revolution HD any other rom would work though. Just pick one from the development section.
Click to expand...
Click to collapse
Well i just took a look at the ARHD thread and I'm stuck on the second line of instructions: "Download "Super Wipe" script & place it on your SD card (optionally if coming from earlier version of my ROM, obligatory if coming from stock or other custom ROM)"
I have no access to my SD card, when i plug it into my PC, nothing happens because all i can do is go into recovery and bootloader.
Just a question, if I try to use the wrong ruu, what would happen?