Develop Bugs

My ONE X doesn't work now!Please Help! :'(

this is my first time to post on the xda,
if i have post in the wrong forum , please help me to move the right forum,thanks!
i have edit the system file to fix camera issue,but i forget to backup file!
Now my phone can't run in to the system.
How can i repair my phone now ?
My phone software version is 1.29.708.9 (HongKong Version) , i think i need the same version RUU....?
Sorry my english is very poor , hope you can know what am i saying

kill0147 said:
i have edit the system file to fix camera issue,but i forget to backup file!
Now my phone can't run in to the system.
How can i repair my phone now ?
My phone software version is 1.29.708.9 (HongKong Version) , i think i need the same version RUU....?
Sorry my english is very poor , hope you can know what am i saying
Click to expand...
Click to collapse
You need to reflash with the original RUU, you can find some RUUs from here: http://www.filefactory.com/f/7cc7b2fbdd03c031/
THIS PROCESS NEEDS A RELOCKED PHONE. (fastboot oem lock).
edit: the RUU for your version isnt published already. You need to wait for the RUU, Why can you use an older version? You can't because the DOWNGRADE isn't posible with S-ON.

If you know what file you modified, maybe extract it from a similar ROM and adb push it?

if youve edited the build.prop without backing it up first then quite simply youre asking for trouble....
ALWAYS Nandroid and back up anything before altering it.
If you can access download mode then your safe, just connect up usb for fastboot and run a downloaded RUU, if youre not sure what rom to get then id try HTC EUROPE ones they first, these are probably the most common ones.

wolfraim said:
You need to reflash with the original RUU, you can find some RUUs from here: *******
THIS PROCESS NEEDS A RELOCKED PHONE. (fastboot oem lock).
edit: the RUU for your version isnt published already. You need to wait for the RUU, Why can you use an older version? You can't because the DOWNGRADE isn't posible with S-ON.
Click to expand...
Click to collapse
Oh....i have try to downgrade when i post this post, but it isn't possbie....(S-ON Now)
Now,the recovery is broken , my phone is hold on the screen on hboot now! I'm not sure can i input power because the phone is always auto reboot in hboot when i connect the power input

graemeg said:
if youve edited the build.prop without backing it up first then quite simply youre asking for trouble....
ALWAYS Nandroid and back up anything before altering it.
If you can access download mode then your safe, just connect up usb for fastboot and run a downloaded RUU, if youre not sure what rom to get then id try HTC EUROPE ones they first, these are probably the most common ones.
Click to expand...
Click to collapse
i will backup the file to PC in next time when i edit any system file...... i have learn a lesson

Yer try not to mess with the build.prop, i know its fun to tinker and see what can be achieved, but there is also a serious risk that comes with it, unfortunatley the file will stop your phone dead if you mess it up, if you save a backup to your pc then worst case you can push it to your phone via adb and overwrite the damaged one.
What CID are u on, eg, htc--001 ??, cidgetter works from market but not much use if you cant boot up, also what firmware are you running now, release, radio and release keys, that way you could extract the boot, recovery and system from the file and just flash them in bootloader.
YOU must relock your bootlock first, the above command in other post was the one to do that, if not, have u tried to flash CWM 5.8.3.1, and install from the recovery youll get both the super su and a custom rom, like android revolution, this way youll be back up and running on a custom rom based on the latest 1.29, you could then download the 1.29 ruu and run it, again after relocking the bootloader and for good measure download and install htcsync, the program delivers a much better driver for the one x, that should get you back to factory, unrooted, stock boot and firmware.
if the ruu isnt avail, find out what your latest ruu is and look for a custom rom based on that.
Keep us informed how you get on, im sorry you learnt the lesson the hard way, i would not wish this to happen to anyone, except for maybe Bill Gates lmao, but then he would just throw it in the bin and go buy another one ha ha.
I hope you get it sorted and remember, before you tinker, READ the guides on XDA, they are good and will really help you and always make a backup of anything you wish to experiment with.
Good luck.

If you still remember the file, try to get it from someone with the same version as you and push it through adb or recovery (if you can go to hboot, surely you can flash cwm again).
Sent from my HTC One X using xda premium

I hope u can read chinese
I had the same problem... and before.. i just flash the RUU again, but after i upgraded to 1.29.. that didn't work...(The RUU I had was 1.26) so with ALOT of searching on the internet.. i found the below Chinese site.. and luckily i can read chinese too...
anyway hope it helps.
Basically what i did was force the recovery to be install on my phone.. but there is a down side.. me alarm doesn't work.. everytime i try to change the alarm sound it just reboot... i am still trying to find a way to fix it... and maybe flash the 1.28 RUU to see if that will work.... but that will have to wait until tonite.
http://bbs.xda.cn/thread-11018720-1-1.html

last night , i had make a fake RUU(basic on 1.28.708.10 HongKong Version RUU,included recovery.img,boot.img,system.img) and flash it ,the result is my phone is recovered , all function is normal and i can get OTA now !!

[Q] Unable to load ROM

Hi guys,
Hoping someone can help, have bricked my Australian Optus stock One X. I have tried to follow all threads related to loading stock or custom roms from fastboot and am unable to. I still have CWM recovery 5.8.2.7 touch installed.
I had previously rooted it and installed Android Revolution HD 5.1.0 and seemed to be fine but was unstable and would crash and reboot in certain apps. In trying to revert back to stock I stupidly formatted the SD card, DUMB ASS!
I have downloaded stock rom 1.29.401.7-DUO, all-in-one rootkit, and the ARHD ROM and have tried to either:
1) flash ARHD with bootloader still unlocked, doesn't work
2) follow reflashing stock process ie flash stock recovery, relock bootloader, then flash stock ROM, and am getting stuck on just reflashing the stock recovery. When I try to open stock recovery it takes me to a black screen with a red ! in a triangle, this is with the bootloader relocked.
If anyone is able to help an enthusiast noob like me I'd be very appreciative and would also be more than willing to donate for the trouble.

MAKE SURE you have exactly the right RUU for your phone, whatever the rom was on you were using, ie, 1.26, 1.28, 1.29, you need the same version of RUU, i discovered the problem trying to flash RUUs and after 2 days finally got the correct one, thats when i realised, unlike on other phones, you cant downgrade the One X and when recovering it seems to prefer the one that matches what you were using.
Also make sure youre cid is supported in that RUU, ie, HTC 001, TMOB 054, etc etc, mine can only accept 401 roms, so they must match exactly, until we can get S-Off this problem will remain, dont worry about recovery, so the guide on in case of disaster, you cant go wrong with it, relock your bootloader and get your RUU installed, from their update it to your latest ics version and then if you must reflash your cwm and root it.

Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.

agentorange82 said:
Thanks for the info, graemeg. After downloading an RUU that was .exe file, I felt I was getting closer, as it was an AU Optus RUU. But it turns out that my current version is 1.28.980.10 and the RUU version was 1.26.980.3 and so yes I met with the non-downgrading issue.
It seems that there is not currently a stock 1.28.980.10 RUU at the moment, so might be using this as an ornament for much longer than I would have hoped/thought. Bummer.
Click to expand...
Click to collapse
You can get 1.28.980.10 from htcdev downloads. I would link but I'm a new user, just filter by One X, Optus, and it's there.

Thanks again for the help. I have seen those files on htcdev website, but don't know how to use them
I don't know how to load a RUU that is not a .exe file...if anyone is able to assist, again, I would really appreciate it and will donate once up and running again.
Edit: I just wanted to add that I have tried to follow the thread that explains how to load/flash recovery and boot images via fastboot in command prompt, and have not been able to. So I don't think I'm a complete dumb ass, but do need someone with the knowledge and patience to guide me through it. Please!

First thing first, do you have the right RUU with you ?
If not, maybe this is the one for you : http://hoxroms.serveftp.com/RUU_END...Radio_1.1204.103.14_release_258004_signed.exe
second: do you have fastboot directory set up on your pc ? and htc usb driver too ?

Just starting the download now, I think that could be the RUU I've been looking for. Yes I have the drivers and fastboot directory. Will give this RUU a go and let you know, thanks for the quick reply, ckpv5!

Most important before you run the RUU, you need to:
1) have a stock recovery flashed to you your device first (I believe you already have one)
2) relock the bootloader - fastboot oem lock
3) run RUU, it should work.

THANK YOU!
ckpv5, thank you for the link to the updated RUU. Phone is functioning again, stock. Donation coming your way. Thanks for all your help. agentorange82.

Stuck on starting screen... (bricked?)

Hey guys,
fairly new to this all and it seems I have messed up at some point...
I managed to root my phone and i do have TWRP on it and wanted to install a rom (blade elite 1.1). went into bootloader and flashed the boot.img with the tool, then went into recovery, cleared all the caches/factory reset/system and flashed the rom which i had previously copied onto my sd card. then i pressed reboot. It didnt start up for a few minutes so i kind of panicked and went into recovery again. I had made a backup previously, which I then restored. But it's still stuck on the screen where it sais htc one on the white screen with the beats audio thing on the bottom... Waited for around 20 mins. I can still get into recovery, so I'm hoping not all hope is lost.
What do I do now? :/ Do I have to flash the stock kernel or something first before I can restore with twrp?
Please help :/ I kinda really need my phone...
Oh yeah I forgot one thing. The tool said "error: device not found" in the first cmd window when I flashed the kerel, but when I clicked it away a second one popped up and it said it flashed correctly. It did the same thing when I flashed twrp and thats definitely on my phone, so Im guessing it has flashed the kernel correctly. Just thought I'd mention that.
fastboot getvar version-main
gave me:
2.17.401.2

aaaalright.
I installed fastboot, found the correct ruu for my device, relocked the bootloader and installed the ruu and my phone is now up and running again! and i feel like a genius :S
however! something went wrong and I would like to know where my mistake was. i still want that custom rom!
since i installed the ruu, that means everything is gone again right? no unlocked bootloader, no root, no twrp? so ill just use the tool again to get that back?
quick question for that. will i need a new token id and register again, or can i use the old one?
its 5:30am here and i'll need to get some sleep now... maybe i can get it tomorrow. still appreciating any help !

Your hboot is to low, you need to update. Since you used the ruu, go into settings - about menu and update the phone with the software update utility.
You are still on ICS and need to update to JB.

You can also update your Hboot yourself by check your cid number using this app
https://play.google.com/store/apps/...sMSwxLDEsIm9yZy50cml0b25zb2Z0LmNpZGdldHRlciJd
Finding the Hboot to match your cid number here
http://forum.xda-developers.com/showthread.php?t=1957376
And upgrade your Hboot manually or by using a tool like this one here (you'll need to put the correct Hboot in the relevent folder of the app first!)
http://forum.xda-developers.com/showthread.php?t=1924003
Read through the full guide and comments first before proceeding!
Hope this helps.

Easiest is to update with the official ota now as he already installed the ruu
And yes you can use the old unlock code again

StreamOfLife said:
aaaalright.
I installed fastboot, found the correct ruu for my device, relocked the bootloader and installed the ruu and my phone is now up and running again! and i feel like a genius :S
however! something went wrong and I would like to know where my mistake was. i still want that custom rom!
since i installed the ruu, that means everything is gone again right? no unlocked bootloader, no root, no twrp? so ill just use the tool again to get that back?
quick question for that. will i need a new token id and register again, or can i use the old one?
its 5:30am here and i'll need to get some sleep now... maybe i can get it tomorrow. still appreciating any help !
Click to expand...
Click to collapse
You can use the original Token they sent you. No need to go through the whole HTCDev process again :good:

You guuuuuys, it worked !!
Thanks a bunch! Was totally easy with the ota update too, very smart!

Good ! Enjoy
CASE CLOSED !

[Q] Flash the normal ROM and make it "new"

Hello,
My HTC Desire HD gets stuck on the HTC screen when I try to boot it.
I am kinda new to this, so I should not have done what I did. I got this phone used and I rooted it, and tried to install a custom ROM.
And something went wrong, likely I didn't prepeard the phone the right way.. And of course, I have been serching a lot on the web, some things don't work and other this requires tools that have a bad download link or outdated.
So my question is: How do I make my phone like normal? Like unrooting and removing everything if possible..
Would be so great if someone could help me out or just by linking me to a working tutorial.
Thank you and have a nice day. And please, ask if something is unclear or if you have questions.

I have a very similar issue
trakku said:
Hello,
My HTC Desire HD gets stuck on the HTC screen when I try to boot it.
I am kinda new to this, so I should not have done what I did. I got this phone used and I rooted it, and tried to install a custom ROM.
And something went wrong, likely I didn't prepeard the phone the right way.. And of course, I have been serching a lot on the web, some things don't work and other this requires tools that have a bad download link or outdated.
So my question is: How do I make my phone like normal? Like unrooting and removing everything if possible..
Would be so great if someone could help me out or just by linking me to a working tutorial.
Thank you and have a nice day. And please, ask if something is unclear or if you have questions.
Click to expand...
Click to collapse
Hi, I have done a similar thing, in that in an attempt to flash a custom ROM, I removed everything. Now, all ROMs just produce the HTC splash screen.
Please help as this is my only phone !!!

You both need to provide more detail on what state your phone was in to begin with and what you did to it. I have a hunch that your phones are S-On with unlocked bootloaders, and that neither of you flashed the boot.img from fastboot after flashing the ROM from recovery. But more detail on what you have and what you did is necessary.

bananagranola said:
You both need to provide more detail on what state your phone was in to begin with and what you did to it. I have a hunch that your phones are S-On with unlocked bootloaders, and that neither of you flashed the boot.img from fastboot after flashing the ROM from recovery. But more detail on what you have and what you did is necessary.
Click to expand...
Click to collapse
Yes, you are right. I just flashed the boot.img with fastboot AFTER installing from recovery. Jellytime booted up. I really have to thank you for that.
And again, you are right. The phone is S-Om and bootloader unlocked.
I used a a tool named "EasyUnlockTool". It rooted, unlocked the bootloader and some other things.
But right now, I think I am going to stick to jellytime. But to help caraar12345 and me later if I want to go back to stock room, what kind of information do you need?
Thank you for helping

You can either flash a rooted stock-like ROM from recovery, in which case you'd be mostly stock, or relock your bootloader and run a RUU from your computer in fastboot, in which case you'd be completely stock.

Check here:
http://bit.ly/186aMrl

Returning to stock issues.

I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!

Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.

I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?

Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.

Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?

Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...

Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.

Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?

Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?

Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!