Hi, first off I want to say I am a total noob, so please bare with me. I have an HTC One X, Telus Variant, and I was trying to flash a ROM, and, well, something wrong happened when trying to do the recovery part. So, I went through all the correct steps, rooted the phone, everything seemed to be working properly, and then I got to the part where I had to install ClockworkModRecovery. So, as expected, I put in the command "fastboot flash recovery recovery.img". Okay, so, I thought it was all said and done, so I went to boot into recovery. Nope. Wasn't happening. It shows the HTC Logo, and then under that: "This build is for development purposes only....". Aaaaaand I'm stuck there. The only thing I can do is boot into the bootloader, and that is it. Does anyone recognize the issue?
You probably have the 4G dual core variant. You must use TWRP and go to your forum. This is for the international one X
Sent from my HTC One X using xda app-developers app
BaneOfRadiohead said:
Hi, first off I want to say I am a total noob, so please bare with me. I have an HTC One X, Telus Variant, and I was trying to flash a ROM, and, well, something wrong happened when trying to do the recovery part. So, I went through all the correct steps, rooted the phone, everything seemed to be working properly, and then I got to the part where I had to install ClockworkModRecovery. So, as expected, I put in the command "fastboot flash recovery recovery.img". Okay, so, I thought it was all said and done, so I went to boot into recovery. Nope. Wasn't happening. It shows the HTC Logo, and then under that: "This build is for development purposes only....". Aaaaaand I'm stuck there. The only thing I can do is boot into the bootloader, and that is it. Does anyone recognize the issue?
Click to expand...
Click to collapse
I had something similar when I booted up a jelly bean ROM a while back with my bootloader RE-locked. If this is the case with your phone just reflash the unlock token and reflash your recovery. If it is as BaneOfRadiohead says you should be more careful with what you flash, Flasing stuff that is not meant for your device can be quite harmful.
Related
So you probably see these types of threads all the time, but this one is different--
So the phone is a T-Mobile G2, Yes, It is Rooted, and S-OFF.
Long story short, I rooted the phone fine, but I cannot reboot into recovery.
I have the newest CWM flashed. It is version 3.0.0.5. When I try to boot the phone into recovery, it simply gets stuck on the HTC Logo screen. But, it is not bricked, but if I remove the battery, and put it back in, the phone boots and its fine. One more time. The phone is S-OFF and rooted.
The only thing I can do is flash CM 2.5.1.3...... 2.5.1.4+ do not work.
I just want to know WHY its doing this. Its my friends G2 and I have rooted mine the SAME exact way, and its fine. I have tried factory resetting it, but it doesn't work.
PLEASE TELL MY WHY.
EDIT*
I'm trying to do this process in ROM Manager- I also have tried flashing it more than once.
Brazildiogo732 said:
So you probably see these types of threads all the time, but this one is different--
So the phone is a T-Mobile G2, Yes, It is Rooted, and S-OFF.
Long story short, I rooted the phone fine, but I cannot reboot into recovery.
I have the newest CWM flashed. It is version 3.0.0.5. When I try to boot the phone into recovery, it simply gets stuck on the HTC Logo screen. But, it is not bricked, but if I remove the battery, and put it back in, the phone boots and its fine. One more time. The phone is S-OFF and rooted.
The only thing I can do is flash CM 2.5.1.3...... 2.5.1.4+ do not work.
I just want to know WHY its doing this. Its my friends G2 and I have rooted mine the SAME exact way, and its fine. I have tried factory resetting it, but it doesn't work.
PLEASE TELL MY WHY.
Click to expand...
Click to collapse
If you can boot up normally, load rom manager (download from market), and go to install alternate recovery, and install any alternate recovery. Then when that is complete, go back and install the Clockwork recovery version you want on top of the alternate.
What happens is SOMETIMES recovery will get messed up while installing, and you'll get exactly that, loop at the HTC screen.
If you cannot reflash an old, then the proper recovery through Rom Manager, you can do it via fastboot with your computer and USB, there are a few guides on the developer forum on how to do that. If you need i can try to dig up the fastboot recovery method guide later... but really, if you can boot up, Rom Manager is your best/easiest bet.
Yeah, I'm trying to do it using ROM Manager. and It still doesnt work. Ive rooted- unrooted and did everything, idk what I'm doing wrong. I tried flashing the new recovery like 4 times, it doesn't work for me. Thanks for the reply!
Hi, I have foolishly (possibly?) wiped Android off of my OneX
I was attempting to apply the Tegra tweak and well things went downhill.
I successfully unlocked the bootloader from HTCdev.
I proceeded to apply Interim ClockworkMod to gain root access
This is where things started to go wrong. Any new reboot would only take me to Clockworkmod screen.
I tried http://forum.xda-developers.com/showthread.php?t=1599748
clear cache, davik cache... relocking the bootloader - This results in the device constantly rebooting.
I attempted to apply the RUU ROM's ( from: http://forum.xda-developers.com/showthread.php?t=1543604)
From within ClockworkMod I was then able to:
adb push One_X_1.26.401.2_odexed.zip /sdcard/
Once there I used ClockworkMod to apply an update zip (which I was hoping was the Stock ROM).
A reboot just brought me back to Clockwork.
I then locked the bootloader ( fastboot oem lock. ) hoping it would then proceed to boot as expected.
It didn't just going to HBOOT or an attempted recovery (isometric view of a phone with a green arrowed circle -> RED triangle).
Please someone help, starting to panic a bit. The fact I can upload, the fact that there is some basic interactions should imply this is fixable, but how?
The boot to recovery sounds like you have the same problem that I had.
Perhaps you followed the same incorrect instructions as I did. See here for a solution.
mwhincup said:
The boot to recovery sounds like you have the same problem that I had.
Perhaps you followed the same incorrect instructions as I did. See here for a solution.
Click to expand...
Click to collapse
This may help.
with the locked bootloader you will only be able to run a proper ruu so before even attempting the instruction above unlock your bootloader again and proceed from there.
I might start working on some core .IMG files that can be flashed through fastboot to get you going again tomorrow
Sent from my HTC One X using XDA
THANKS!!!
booted back to the lovely ICS desktop
It looks like I did end up flashing RUU since none of the Vodafone branding is present (and it is actually better!)
No idea what went wrong but probably flashed over the boot as hinted at in the other thread.
The provided img files assisted. just need to get this Tegra thing working (not showing up as a running/registered process but thats another story)
Thanks all
Hi there,
The other day I decided to S-OFF, root, and flash a custom ROM on to my HTC Desire handset. It all seemed to go perfectly well. I could access HBOOT, Fastboot, Recovery (4EXT), and I could boot into the custom ROM. It worked absolutely fine for approximately 24 hours. Then, the phone restarted and I can't get past the splash screen.
I am able to access the Bootloader (HBOOT, Fastboot etc.) but I cannot boot into the ROM or into Recovery.
I followed the instructions (step 2) found here: http://forum.xda-developers.com/showthread.php?t=1275632&highlight=can+t+get+past+hboot
I've tried using Method 1 and Method 2. And, although the process appears to be successful (according to Android Flasher's and cmd's response) but I'm still unable to get past the splash screen or access the recovery.
I thought that perhaps it did work fine and that it was just the recovery image I was using so I downloaded the latest Clockwork Mod Recovery image from their website. Unfortunately, this hasn't made any difference.
I used Fastboot to wipe the userdata, system, recovery, and cache but this has still not made a difference.
Does anyone have any ideas or is it busted?
Would flashing a RUU potentially resolve the issue (although, ideally, I don't want to do that and it would be a last resort).
Many thanks in advance.
This problem didn't appeared on its own, did it?
Probably you did something wrong. I suggest you to use RUU and start all over again.
Remember to downgrade your hboot first
Sent from my HTC Desire using xda app-developers app
paolo-red1 said:
This problem didn't appeared on its own, did it?
Probably you did something wrong. I suggest you to use RUU and start all over again.
Remember to downgrade your hboot first
Click to expand...
Click to collapse
Hi paolo,
Well, as I explained, it did all appear to be fine. I didn't do anything else to the phone when it started rebooting. But, clearly, something has gone wrong somewhere.
I've downgraded the HBOOT, and used the RUU. It looks to be sorted now.
Thanks for your help.
Glad that you solved your problem. Cheers
Ok so guys i had just rooted my htc wildfire s (or atleast thought i rooted it ) and was trying to install a cyanogen mod ROM , it would not install ,if it would install it would be stuck at the htc logo screen , now i thought this would be the fault of recovery so i decided to install another recovery and flash that with cmd (fastboot flash recovery recovery.img) but then when i booted in recovery it would show me the pink recovery, i got a little scared and flashed another recovery and now the recovery will not even boot . it will just go on htc logo and black screen , i tried many different recoveries but no avail , it is in s-on right now , please forgive me if this sounds noobish i really am a noob at this .please provide me with a solution and tell me if it is bricked and if i can repair it by taking it to a software shop and asking them to do it for me (Just advise me if i can come back from this)
Flash the first recovery, which actually worked, and if it installs, wipe everything and flash a basic CM7 rom. It'll work. It's just soft bricked don't worry.
parasthakur37 said:
Flash the first recovery, which actually worked, and if it installs, wipe everything and flash a basic CM7 rom. It'll work. It's just soft bricked don't worry.
Click to expand...
Click to collapse
actually i gave it to a software store , he said he couldn't do it as the files were not to be found ... i think it might have been bricked but seeing as i can access h-boot only and when i turn on the phone it only stays on the htc logo screen and does not proceed can you call this bricked . ? i tried the first recovery as you mentioned but it was no use ... i tried relocking and unlocking bootloader again but it seems as if that was unnecessary as nothing different happened .. im still waiting for an answer
This is really very weird.
Check this out
http://forum.xda-developers.com/showpost.php?p=28646721&postcount=5
Start from square one, unlock the bootloader, flash the recovery, if one doesn't install, try another, at least one will surely work, and then flash a new rom.
All the best.
Remember, android can never be bricked, there is always a way out.
parasthakur37 said:
This is really very weird.
Check this out
http://forum.xda-developers.com/showpost.php?p=28646721&postcount=5
Start from square one, unlock the bootloader, flash the recovery, if one doesn't install, try another, at least one will surely work, and then flash a new rom.
All the best.
Remember, android can never be bricked, there is always a way out.
Click to expand...
Click to collapse
thank u for the quick reply but i donot know how but i just flashed an old recovery and voila it worked .. now i am a little scared to proceed please guide me what to do to bring back the stock rom ...
ITS DONE
i finally got it to work thank u so much i used jelly king rom on it and it worked DDDDD
Press thanks.
...I think
I would gladly give a better Topic Title but i can't. Maybe you guys can give further troubleshooting assistance.
Actual State:
Can boot to bootloader and Fastboot. Bootloader unlocked and TWRP Recovery installed. There _should_ be a Revolution HD on the device. When device powers up it goes smoothly to the White HTC quietly brilliiance screen (screen brightness begins to flicker) and goes off after (really off, not hanging, plain off). After i cleared boot cache via adb i'm able too see a split second of the htc bootlogo and then goes off right after.
State of device when i began to "fix" it:
BL Locked, No Custom Recovery, Stock recovery dead (Just red triangle), rom maybe was dead too but i don't know.
Last attempts i did were:
1. Flash boot.img through fastboot (Fastboot flash boot boot.img)
2. Flashed the Superwipe script (was desperate)
3. Flash Android Revolution through TWRP-Recovery
First:
I Don't know wich carrier. Boy that bugs me a lot. I'Ve tried Generic, Vodaphone and T-Mobile (since i'm in germany) but no Luck. Is there a possibility to check what RUU i need without a Running ROM? I haven't bought the device i got it from a friend of mine and it went straight to my wife. I've asked, he doesn't know. I'm not so into HTC, so i'm not quite firm concerning Stock restore.
Next:
I think i tried everything except for restoring stock (because.... meh....): I've unlocked the phone. I've flashed CWM aswell as TWRP. I've flashed different boot.img from different roms i've flashed.
I'Ve litteraly did EVERYTHING what seemed like a good idea to me. But now i'm at the end of my knowledge.
My last piece of Information:
After 2 1/2 hours i had a Custom Recovery Running (did the trial and error RUU Method before). I've mounted the SD-Card and it was Blank. There was NOTHING on it except for some Recovery Folders. SD Card is about 24GB. This looks like a lot to me. Is that really normal? Mounting system, data and sd via adb works like a charm.
So if one of you could help me that'd really be cool. If there is some crazy stuff i need to do via adb, please go into detail. I know the basics (how to mount partitions and to push files) nothing more.
But maybe it's just faulty...
Thanks in advance