Develop Bugs

[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.

[Q] Problem with updating from hboot 0.43

Evening folks.
I was running a rooted and ROM'd One X with ARHD 9.x and quietly waiting for T-Mobile UK to release their version of JB. Now it's out, I've reverted to stock from Nandroid, gone back to stock recovery and stock boot image and waited for a system update OTA from T-Mob.
My phone picked up an update which was about 28mb. I figured this might be to update my hboot as I'm on 0.43 and I understand that needs to be updated before I can update to JB. I ran the install, the phone rebooted and then I got the following message flash up:
"This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action."
Since then I can't do anything like a factory reset (I get the same message flash up). The phone boots fine but tells me I have an update waiting to be applied.
Given that the phone was reverted completely to stock, I'm not quite sure what the update is that it picked up.
I'm thinking about doing it all manually but I'm frankly confused by all the information that's around - it's hard to work out what relates to my phone, and what I need to do. Here are the things I need to understand:
How do I get the hboot to a later version?
What version do I need to get it to to be able to then install JB?
Can I go directly from 0.43 to the one that will allow the JB install or does it need to be done in stages?
version-main: 1.26.110.5
CID = T-MOB005
hboot = 0.43
I'd really like to wrap my head around this and any help would be very much appreciated.
Edit: I've just noticed that I can no longer get into the stock Recovery...

You can flash this ruu
http://www.htcruu.com/securekey.php...Radio_1.1204.105.14_release_260731_signed.exe
It will bring your hboot to at least 0.95 or 0.96, from there you have to try and update to android 4.0.4 hboot 2.17 and from there to JB
Put the phone in fastboot usb mode and lock the bootloader
Fastboot oem lock
Stay in the fastboot usb mode and execute the RUU.exe from pc ... right click it and select
Run as administrator
It will flash the phone to full stock, you lose all data on the phone !

Thanks Mr Hofs, that worked. I've now got 1.29.110.11 on the phone, however it doesn't seem to be installing the 4.0.4 update (which it picks up OTA).
It downloaded it, rebooted, looked like it was installing but when the phone restarted it was still on 4.0.3 and picked up the system update again...
Edit: Ran it again and it's worked! I'm on 4.0.4 and 2.17.110.5. Next I'm hoping it picks up the T-Mobile OTA for JB. Then I can let it sort the hboot, unlock it, flash it and *done* hopefully!
Edit 2: Superb, it's picked up the Jelly Bean update. Downloading now!
Thanks for your help Mr Hofs!

No problem mate ! Enjoy the JB experience

[Q] Why is my HTC One x (PROTOTYPE) stuck on ICS?

Why is my HTC One x (PROTOTYPE) stuck on ICS?
Hey guys, This is my first post ever on XDA so please forgive me if I sound like an idiot
I got hold of a HTC One x which was already had an unlocked bootloader, rooted and had CWM recovery installed. I was told that I have a prototype version of the one x. Anyway that is not issue. when I got the phone it was running android version 4.0.4 HTC Sense version 4.1 and I checked software update. The 3.14.401.27 OTA update was available so I proceeded with the update and after the reboot I found my phone stuck in a bootloop and the only way for me to sort it out was by restoring my nand back up from CWM. I really wanted the new Sense 5 UI and android jelly bean so I downloaded:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Rad io_5.1204.162.29_release_292865_signed.exe
My CID was HTC__621 thats why I downloaded that ruu but after flashing it not was I only stuck in a bootloop but also when I entered recovery mode it was just a blank black screen with the back lights on. I even flashed different versions of CWM recovery and TWRP which gave me the same black screen so I flashed the stock recovery.img which also gave me the same black screen. I thought me maybe a different Ruu would resolve this issue so I used 'JBFWTOOL21' to change my CID to '11111111' this allowed me to flash:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radi o_5.1204.162.29_release_298897_signed.exe
&
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed.exe
After trying both these ruu's I still found my device stuck in a bootloop. Next I downloaded 'Endeavoru_CustomRUU' this contained a 'rom.zip' which I belive was a jelly bean rom and said it would update my image version to '3.14.401.31' after flashing this ruu, my phone booted up past the 'HTC Quietly Brilliant' screen but into a black screen but I could hear the boot sound and knew it booted up but it still gave me a black screen. barre in mind this was the only rom that booted up and didn't get stuck in a bootloop but the downside was I had no picture on the screen it was literally pitch black with the backlight on when it went past the 'HTC Quietly Brilliant' boot screen. I didn't even see the one x boot animation. I could only hear the boot up sound and once it was booted up the notification LED would flash I was receiving network settings from my operator. That was about it. I booted into recovery to see wether that worked but unfortunatelly it was also still giving me a black screen. The only thing I could boot into without a problem was 'power button + volume down' which booted into bootloader in which I chose 'fastboot' to flash all these roms.
At this point I thought my device was soft bricked so I gave it to my friends father who happened to really good with his IT skills. He managed to change my device's CID from 'HTC__621' to 'HTC__001' after doing so he downloaded this ruu and flashed it:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radi o_2.1204.135.20_release_274900_signed.exe
This ruu turned out to work perfectly fine with my device. Everything functioned once again, the device was able to boot into recovery and boot normally without a hassle. I also discovered that this was the rom that I received my phone with which put me back to the start on android 4.0.4
I was really annoyed with the fact that I was stuck on ICS so I flashed the MaximusHD 21.1.0 rom and its boot.img which put me into a bootloop again. I also tried other custom roms such as Revolution and SD secxces which all put my phone in a bootloop even though I flashed their boot.img kernels. I knew that I required a hboot 1.33.0000 or above in order to flash jb roms so I used 'JBFWTOOL21' once again before flashing these custom roms to update my hboot from 1.12.0000 to 1.33.0000. so all these bootloops still occourd after doing all this and I just had to return back to ICS. barre in mind I only tried flashing JB roms as I want sense 5 so I don't know if a custom ics rom would work on my device as I havent tried it yet but I know for a full fact that none of the jb roms work on my device.
For those who are wondering here, I uploaded some pictures of my device just check the attachments. It has all the information you may want to know about my device (HTC One X PROTOTYPE).
I really hope someone can help me update to jelly bean and get sense 5 as I am frustrated from failing and being stuck in bootloops
If you read all of this I honestly appreciate it and I Thank you for it, I hope you can help me!

all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140

I did that
nogotaclue said:
all you need to do is flash the stock recovery from this post>>>>>http://forum.xda-developers.com/showthread.php?t=1975140
Click to expand...
Click to collapse
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop

so you have a stock recovery now? and receive ota notifications?

Yes
nogotaclue said:
so you have a stock recovery now? and receive ota notifications?
Click to expand...
Click to collapse
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:

sN_iPower said:
Yes I do and if I proceed with the update it will install without any problems but once it reboots it will be stuck in a bootloop. I ended up returning back to ICS and ignoring the update prompts when get told to update my software.
here you can see the update notification I recieve:
Click to expand...
Click to collapse
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there

alright
nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
alright im going to try that now, I will get back to you once I done it

nogotaclue said:
you could try installing the update and if it bootloops go into the bootloader, vol down and power, and do a factory reset from there
Click to expand...
Click to collapse
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS

sN_iPower said:
I just tried everything you told me, and I still ended up in a boot loop now I have to flash
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
to return back to ICS
Click to expand...
Click to collapse
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor

sN_iPower said:
Thank you for your input, but I already done that which resulted no success for me. The only way for me to overcome these black screens was by flashing:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This makes my device fully functional again but it just leaves me locked on ICS because when do the OTA updates, Flash JB ruu's or even flash custom JB roms I just get stuck on bootloops. I don't seem to get one JB version of android working on my device. Thats why I'm here seeking for help from geniuses like yourself. At the moment my device is back on android 4.0.4 but thats about it. It works perfectly fine on this version but I just can't update no matter what way I try I end up in a bootloop
Click to expand...
Click to collapse
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend

nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 http://www.androidruu.com/?developer=Endeavor
Click to expand...
Click to collapse
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan

Thant said:
Lock you are S-OFF try fastboot writecid HTC__032 i think is something like this and see what will happend after applay update. Or try manualy update with this RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe after changeing the CID
The other way is manualy update your hboot to high version! Download from here firmware .zip for region 401 hboot1.31 and see what will happend
Click to expand...
Click to collapse
sN_iPower said:
I flashed the asian ruu first because my CID used to be HTC__621 which requires TW ruu's (I tried the JB one) also on the back of my device it says made in Taiwan. But after flashing the rom it didn't work and put me in a bootloop so I changed my CID to 11111111 and flashed the European ruu ( I tried the JB one) which also didn't work and ended up putting me in a bootloop. It was my friends father who then changed my CID to HTC__001 and flashed the European ICS ruu which worked flawlessly. Do think I should flash the ruu you recommended? because its a ICS ruu and I'm trying to get to JB. Anyway I really thank you for trying to help me, you are the only one who replied to me
Look at this image it shows you that my device was made in Taiwan
Click to expand...
Click to collapse
Actually @Thant replied also, try what he suggests at the bottom of his post to update your hboot, it's a different one to the one you tried, then try a higher ruu

I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.

Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
Maybe you are right he must to prepear and know the chance to broke his OneX is big because is prototype.

Tigerlight said:
I am wondering why everyone, OP and those attempting to assist, are assuming that what is apparently a prototype model of the One X would even be compatible with the updates.
If it is a prototype, regardless of how it identifies itself, it may have differences that simply prevent ANY of these software versions from operating.
I think that is one possibility the OP may have to be prepared for.
Click to expand...
Click to collapse
That had crossed my mind actually, but he is receiving ota notifications and the results he posted from "getvar all" indicate everything is as it should be, same model number even.
I have come across an early prototype before and the only 2 differences were the casing and slightly larger headphone jack socket. AFAIK the hardware was the same. Unfortunately, the one I saw wasn't working so I don't know what version of android it had

nogotaclue said:
I'm curious why you first chose an asian ruu for your first attempt and then got the european ruu. there is another ruu available but I need you to answer the above first.
I have to go to work now so I won't be able to answer you, there is another ruu available for version number, it's the 18th one down the list, release 974956 androidruu/?developer=Endeavor
Click to expand...
Click to collapse
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app

xb2 said:
Just to ask further: i dont see ruu for 4.19.707.3 (cid htc_044) on the site androidruu? I'm looking for it but yet to find, except for odexed/deodexed stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.

Thant said:
No more RUU only stock rom or nandroid. You never find that RUU because HTC never release this RUU.
Click to expand...
Click to collapse
Ah, I see. Manual flashing stock rom is still ok anyway.
Thanks for the info, Thant
Sent from my HTC One X using xda app-developers app

Welcome... this had been discussed...
http://forum.xda-developers.com/showthread.php?t=2232063

I have Htc one x Prototype only ics no custom recovery no jb
hi, i have a htc one x protoype(engineer model) i have tried many times to install custom recovery and jb ruu but result is always same. bootloop and black screen. is someone can help. i know only xda members can help. so plz

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!

Phone automatically starts into bootloader and flashing doesnt work

So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help

Hi,
Did you try to reflash your recovery and try to install another rom like ViperOne M8? Or if you want i can send you the stock ROM Android 6.0

Laurens54321 said:
So as you might have heard, android 6.0 is out on htc one m8 now, and as usual i wanted to update. I got my device into a bootloop after unrooting and downloading some OTA's online, and messing around with stuff that didnt work.
But now im rly stuck, when i boot my phone up it automatically boots into bootloader. I cant flash a boot.img because i get a signature verify fail. Updating with RUU returns error 130 and factory resetting doesnt do anything at all(in fastboot and in recovery). plzzzz help
Click to expand...
Click to collapse
You seem to be going about things rather haphazardly:
1) Not sure exactly what "some OTAs" refers to. But there is typically only one OTA that will properly work. That being the one that is for your CID (carrier version) and for the next software version (can't skip any).
2) Along the same lines, you can't just flash any RUU. It has to be for your CID and MID (Error 130 usually means wrong MID), and equal or greater version number than main version on the phone (no "downgrading" unless you have s-off).
3) "messing around with stuff that didnt work" doesn't tell us anything about how you got to the current condition. You need to be specific and detailed, if you want us to be able to tell what you did, and how to recovery.
4) You can't unroot and OTA, it has to be a stock (never rooted) ROM and stock recovery.
5) boot.img in itself probably won't help your situation. And signature verify fail usually means you tried to flash without the bootloader unlocked (which won't work).

Are you S-OFF? If so, this works;
1) Download 0P6BIMG.zip. You'll have to Google
"dottat @ XDA M8 RUU" to get the file as I haven't
made at least ten posts here and can't post links yet.
2) Place 0P6BIMG.zip on an SD card formatted fat32 ONLY.
3) Boot your phone, allow HBOOT to recognize 0P6BIMG.zip
and follow the prompts.
RESULT: This will land you on STOCK kitkat 1.55.605.2
pre-rooted with stock recovery.
----------------------------------------------------------------
CREDIT: dottat @ XDA