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 !!

Cant get into recovery , dont have root and constant rebooting PLEASE HELP ME!

i cant access my recovery anymore , it was twrp and i have kitkat 4.4.4 rom ... i know that sometimes i would have to manual install superuser on twrp recovery but now i cant...... because i cant access my recovery....also my phone is rebooting due to this.... every 15 seconds..... i recently relocked the bootloader cause i was gonna flash a firmware that i needed.....never found the firmware that matches my cid and mid..... i have no idea what to do now..... i cant access my recovery and the phone is rebooting on me....
Edit : also i can go to my bootloader no problem , and when ever i try to go to recovery it will just take me to fast boot again...

Did you try to flash TWRP again?
On a side note, I don't know why people insist on going back to S-ON and relocking bootloader with the mantle of "stock". No need to go back S-ON and while you're S-OFF you never need to lock the bootloader
Lost count on how many posts I read with people that ended up asking for help with exactly the same steps taken. :silly:

BerndM14 said:
Did you try to flash TWRP again?
On a side note, I don't know why people insist on going back to S-ON and relocking bootloader with the mantle of "stock". No need to go back S-ON and while you're S-OFF you never need to lock the bootloader
Lost count on how many posts I read with people that ended up asking for help with exactly the same steps taken. :silly:
Click to expand...
Click to collapse
actually i am wrong , i never went back to s on , i was s on to begin with , i had to relock bootloader to flash a firmware that i needed.... never flashed it because it didnt match my cid and model id.... and yes i did try to flash twrp with fastboot but it is saying signature verify failed....
at this point i seriosly think i am screwed..... i can boot into the phone but it will reboot within 15 to 20 seconds

GabrielOspina said:
actually i am wrong , i never went back to s on , i was s on to begin with , i had to relock bootloader to flash a firmware that i needed.... never flashed it because it didnt match my cid and model id.... and yes i did try to flash twrp with fastboot but it is saying signature verify failed....
at this point i seriosly think i am screwed..... i can boot into the phone but it will reboot within 15 to 20 seconds
Click to expand...
Click to collapse
You need an unlocked bootloader to flash, whether it's ROMs or recoveries, it needs to be unlocked.

BerndM14 said:
You need an unlocked bootloader to flash, whether it's ROMs or recoveries, it needs to be unlocked.
Click to expand...
Click to collapse
figured that much , i do have usb debugging on so is that more then enough to do it, ill try it right now

BerndM14 said:
You need an unlocked bootloader to flash, whether it's ROMs or recoveries, it needs to be unlocked.
Click to expand...
Click to collapse
wow...... just unlocked my bootloader and i can go into recovery.... thanks alot man i know it is a newb mistake but regardless thank you........

GabrielOspina said:
wow...... just unlocked my bootloader and i can go into recovery.... thanks alot man i know it is a newb mistake but regardless thank you........
Click to expand...
Click to collapse
Ok cool, glad it's working now. :good: Enjoy.

HTC M9 won't boot after update - can't flash anything, factory reset or unlock bl..?!

Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(

At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.

fernandezhjr said:
At the screen with the red triangle and exclamation mark, press and hold the power button. While holding the power button, quickly press and release the volume + button. If this gets you to recovery, try a factory reset.
Click to expand...
Click to collapse
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?

zroice said:
Hey guys
got a HTC M9 with cid "O2___102" which won't boot up after stock update.
Phone was not modified yet.
1. Can't unlock bootloader (says: "(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock") - so no way to install custom recovery + custom rom to revive
2. Can't boot into recovery (shows phone with a red exclamation mark but no menu) so no way to factory rest
3. can't find a matching RUU for the "O2___102" CID ...
PLEASE HELP =(
Click to expand...
Click to collapse
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.

Aldo101t said:
as for the bootloader unlock go into settings>developer options>check oem unlocking. then you can unlock bootloader.
Click to expand...
Click to collapse
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course

zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
lol, sorry missed that part
---------- Post added at 07:50 PM ---------- Previous post was at 07:26 PM ----------
zroice said:
the damn thing is not booting.... =( Stuck at HTC logo - or else I would do that off course
Click to expand...
Click to collapse
I do believe if you can get to download mode you can do a factory nreset from there, if that will help you.

zroice said:
got into the recovery menu, thanks.
But damn phone is still not booting.
Guess I need to get factory image or custom rom on there but bootloader cant be unlocked and there is no damn RUU for this CID out is there?
Click to expand...
Click to collapse
What about flashing an older RUU and trying to take the update again?

fernandezhjr said:
What about flashing an older RUU and trying to take the update again?
Click to expand...
Click to collapse
cant find any ruu for that branding - if you see/saw one please let me know.

zroice said:
cant find any ruu for that branding - if you see/saw one please let me know.
Click to expand...
Click to collapse
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.

Flippy498 said:
The UK ones for O2 can be used with the German O2 CID, too. You can find them for example in my Collection of Back-to-Stock Files or on androidRUU. But I'm not sure whether a downgrade from android 5.1 is possible with S-ON. The only confirmed downgrades with S-ON were from 1.32.XXX.15 to 1.32.XXX.8. And from my experiences with Denis Meissner and Amr Nasser I would say that a downgrade isn't possible with S-ON if the first and/or the second number of the actual firmware version differ from the ones of the firmware you want to downgrade to.
Click to expand...
Click to collapse
*downloading with fingers crossed*

Failed: -2, 19 to flash via downloadzip or smth like that

Can you flash twrp recovery? If you can, maybe you can flash a stock backup from someone else.

zroice said:
Failed: -2, 19 to flash via downloadzip or smth like that
Click to expand...
Click to collapse
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.

Flippy498 said:
Yeah, would have suprised me if it worked. As said before even downgrading from 1.40.XXX.X to 1.32.XXX.X seems to be impossible with S-ON. How long did you actually wait until you thought that you phone doesn't boot? The update to android 5.1 and the first boot took around an hour for me. Maybe you just need to wait a little longer. If your phone was unlocked I would suggest you to flash TWRP and use one of my stock backups but...
The only other option I can see right now is trying to find someone who has a java card. With S-OFF you should be able to downgrade with the RUU. (If I remember correctly there were one or two shops advertising their java card services on Android-Hilfe.) This option may not be for free but it should still be cheaper than sending your phone to HTC's repair service or buying a new phone.
Click to expand...
Click to collapse
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?

zroice said:
whats that java card you're talkin about? Never heard of that.
An appropiate RUU with the latest version should theoretically also work, right?
Problem ist that I cant flash anything custom because bootloader locked and I cant get inside the system to enable the bootloader unlock... =( and the thing has a visually broken volume up key for dropping down, so the htc support won't fix it (for free) I fear.. otherwise I would just give it to them since it has not been modified yet. (not my phone ..)
P.S:
OS Version is 2.10.206.2 - thats the latest one right?
Click to expand...
Click to collapse
Yes, 2.10.206.2 is the latest version for now. If there were a RUU with your firmware version then using it would be the easiest way to solve your problems. But as far as I know the only existing ones for O2 are for 1.32.206.6 and 1.32.206.15. But with S-OFF you would be able to use the older RUUs, too.
I never used a java card so my knowledge about this topic isn't that outstanding. I know that it is a small, SIM-Card-like looking thing that allows you to S-OFF your phone. Usually they cost several hundred euros/dollars and the number of times you can use them is limited. Since verizon blocks bootloader unlocking these cards are the only option if a verizon users wants to flash anything on his/her phone. Some German phone shops offered S-OFF by java card, too, before sunshine got updated for the M9. That's why I gave you the link to Android-Hilfe. (And that's actually all I know about that topic.)

i need this rru please any one have to uplode link
thanks

Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.

theadra said:
Just as an update, I recently bricked this phone trying to flash lineage to it. To fix it, I went to HTC.com and downloaded the current RUU and put the phone into download mode. I know some people say you don't need to "relock" the device, but I don't get errors during the installation with RUU when relocked. Plus, I am running with S-on.
Click to expand...
Click to collapse
Bootloader and s status are irrelevant. The phone will flash regardless.

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!

M9 Stuck in a permanent boot loop even after hard reset :(

Hi everyone,
It would appear that my phone is stuck in a permanent boot loop. I'm still on the latest official rom from my carrier, it's not rooted nor have I made any changes to the bootloader.
The only thing that I did was restart my phone from within the OS after I couldn't launch the official SMS app (some MMS process error).
Now I'm stuck in a boot loop where the phone doesn't get past the first "HTC" logo page. I also notice that there are two thin dark horizontal lines on the top and middle of the screen that weren't there before. They look like clusters of dead pixels and are across the whole screen.
I've tried using the official bootloader to do a factory reset and wipe cache but I'm still having the same issue.
What else can I try? Is it safe for me to unlock the bootloader and try flashing a custom ROM while the phone is in this state?

I'd try to look for an RUU that matches your firmware before trying anything else.
Sent from my HTC 10 using XDA Labs

squ89r97 said:
I'd try to look for an RUU that matches your firmware before trying anything else.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?

P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
If everything is official, I'd send it back and get a replacement.

P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
If your phone has a warranty send it back. For it to bork the way it has it was probably faulty, unless you know something we don't..
You could revive the phone but it may still have a fault.
Beamed in by telepathy.

squ89r97 said:
If everything is official, I'd send it back and get a replacement.
Click to expand...
Click to collapse
shivadow said:
If your phone has a warranty send it back. For it to bork the way it has it was probably faulty, unless you know something we don't..
You could revive the phone but it may still have a fault.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi guys,
Thank you very much for the friendly help. I've found the RUU file and it revived it. Wasn't free though (ir-file.com).
When I get the time I'll re-upload it and make available in one of the RUU threads.
Anyway, the first thing I did was to unlock the bootloader, install TWRP, root and finally S-OFF. If I had TWRP to start with I could have avoided all this hassle and just restore the boot partition for example.
However it does worry me a bit that such a thing occurred out of the blue. Are there any ways of checking if there is storage corruption, bad sectors in memory ect?

P$YCH0 said:
I've tried to find it but I'm not having luck.
Since I'm S-ON I can only flash the ROM with the same firmware and I've figured that I need:
version: 3.35.166.12 for CID: VODAP120 (A1 Telekom Austria).
Now in case I can't find it, I would need to unlock the bootloader and flash a custom recovery.
However, since there is no way to go S-OFF without actually booting into the phone is there a risk of bricking the phone when trying to flash a custom ROM?
Click to expand...
Click to collapse
P$YCHO, How did you find the version number and CID code, I can't see those anywhere on the bootloader of recovery?
Thanks

templer59 said:
P$YCHO, How did you find the version number and CID code, I can't see those anywhere on the bootloader of recovery?
Thanks
Click to expand...
Click to collapse
Hold the power button and volume down while booting. The OS line will show you the ROM version that you have to look for when trying to find the RUU. You need to install ADB and Fastboot and run a special command to read the CID and other device data. Something like allvars, can't remember exactly, did it a year ago when I got the phone
Sent from my HTC One M9 using Tapatalk

P$YCH0 said:
Hold the power button and volume down while booting. The OS line will show you the ROM version that you have to look for when trying to find the RUU. You need to install ADB and Fastboot and run a special command to read the CID and other device data. Something like allvars, can't remember exactly, did it a year ago when I got the phone
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
You mean "connect it to a pc while in download mode, install a copy of fastboot.exe and type: fastboot getvar.
P$YCH0 said:
Hi guys,
Thank you very much for the friendly help. I've found the RUU file and it revived it. Wasn't free though (ir-file.com).
When I get the time I'll re-upload it and make available in one of the RUU threads.
Anyway, the first thing I did was to unlock the bootloader, install TWRP, root and finally S-OFF. If I had TWRP to start with I could have avoided all this hassle and just restore the boot partition for example.
However it does worry me a bit that such a thing occurred out of the blue. Are there any ways of checking if there is storage corruption, bad sectors in memory ect?
Click to expand...
Click to collapse
If you need permanent storage for the ruu you got let me know as i have plenty of gdrive space.
Beamed in by telepathy.

Hi guys, I am in the exact same situation and don't seem to be able to find the appropriate RUU file for my phone. Can you please give me some indication regarding how to find it.
So far I managed to unlock the bootloader, install TWRP and attempted flashing several RUU files without any success whatsoever.
Thanks a lot in advance!
Cheers!