Database Develop

[Request] HTC Raider Rogers ICS RUU

I think I may have soft bricked my HTC Raider.
I was attempting to flash CM9 on my HTC. I followed the pre-flash procedures (Wiping Data, etc). Then, once it was complete, I rebooted the phone. The phone could not get past the CM9 Blue Tunnel animation. I left it there for about an hour, but nothing happened. I can still access my recovery and bootloader. I have tried flashing another ROM, as well as restoring a Nandroid backup I made, but they all lead to the white HTC screen. My Raider has S-ON.
User MzzSarahx3 had an extremely similar case, except that person had an AT&T Vivid, as seen here:
http://forum.xda-developers.com/showthread.php?t=1416836&page=51
MzzSarahx3 managed to fix the problem by running an RUU, so that is why I believe I can fix my situation by doing the same. I am aware of the RUU Collection that Football uploaded, but clicking on a link on FileFactory will give me an error saying that all download slots are in use.
So could somebody please link me, or upload, an ICS RUU for the HTC Raider on Rogers? Help would be much appreciated.

Just means site is busy keep checking
Sent from my HTC PH39100 using xda premium

ronnie498 said:
Just means site is busy keep checking
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
I have been clicking on that link since this morning. And it still gives me the same message. I will continue to check, though.
Does anyone have an alternate solution?

The stock Bell ICS RUU should work fine on your Rogers Raider. ( I have a Bell Raider but installed it on my buddy's Rogers Raider).
I'm uploading the stock Bell ICS RUU to Depositfiles right now but its gonna take an hour. I'll update my post with the link when it's done.
You can probably find the stock Bell ICS RUU on various threads in the forum. I believe that's where I got it from originally.
Note that if you have unlocked your bootloader (via htcdev), the stock RUU will refuse to install !

LaZiODROID said:
The stock Bell ICS RUU should work fine on your Rogers Raider. ( I have a Bell Raider but installed it on my buddy's Rogers Raider).
I'm uploading the stock Bell ICS RUU to Depositfiles right now but its gonna take an hour. I'll update my post with the link when it's done.
You can probably find the stock Bell ICS RUU on various threads in the forum. I believe that's where I got it from originally.
Note that if you have unlocked your bootloader (via htcdev), the stock RUU will refuse to install !
Click to expand...
Click to collapse
Thank you very much for uploading it!
I am definitely looking forward to using my phone again!
BTW I have looked around for the Bell ICS RUU on these forums, but did not find anything. The closest thing I found was this:
http://forum.xda-developers.com/showthread.php?t=1672800&highlight=bell+ics+ruu
But they said it was not a RUU so.....

I have uploaded the Bell ICS RUU to DepositFiles. You're welcome!
Filename: RUU_HOLIDAY_ICS_35_S_BM_3.38.666.2_Radio_3.04.4740.11_34.29.701040.22_release_255916_signed.exe
http://depositfiles.com/files/ofalwm57q

LaZiODROID said:
I have uploaded the Bell ICS RUU to DepositFiles. You're welcome!
Filename: RUU_HOLIDAY_ICS_35_S_BM_3.38.666.2_Radio_3.04.4740.11_34.29.701040.22_release_255916_signed.exe
Click to expand...
Click to collapse
Umm, well I downloaded the RUU file you kindly uploaded, but I have encountered a problem.
ERROR [131]: CUSTOMER ID ERROR
I have tried many times. Got this error every time. I guess it is because I have a Rogers phone and attempting to update using a Bell RUU.
Any suggestions?

LeoCFZ said:
Umm, well I downloaded the RUU file you kindly uploaded, but I have encountered a problem.
ERROR [131]: CUSTOMER ID ERROR
I have tried many times. Got this error every time. I guess it is because I have a Rogers phone and attempting to update using a Bell RUU.
Any suggestions?
Click to expand...
Click to collapse
Damn... I don't remember having to do that for my buddy's Rogers Raider. Sorry.. it was some time ago.
He's here so I just checked his phone... we must have put in the SuperCID back then (which may accept any RUU?)
C:\Users\Master>fastboot getvar cid
cid: 11111111
finished. total time: 0.000s
and I ran mine (actual Bell Raider).:
C:\Users\Master>fastboot getvar cid
cid: BM___001
finished. total time: 0.000s
Feeling adventurous? I'm not sure if you need to be S-OFF to do this (or have unlocked bootloader, or even both) but...
You can change the CID via fastboot.
Fastboot commands that you can do: (thank you jmone from showpost.php?p=25187040&postcount=199)
(to check your current CID - write it down?)
fastboot getvar cid
(to write a new CID to the phone)
fastboot oem writecid 11111111 (where the 11111111 contains the CID you want - you can try the 11111111 (is that known as SuperCID?) or you can try mine, which is BM___001 as specified above)
(then reboot into bootloader mode)
fastboot reboot-bootloader
(then if it reboots back into fastboot mode, you can run this to verify your desired CID made it)
fastboot getvar cid
Then maybe the RUU will allow itself to install?

LaZiODROID said:
Damn... I don't remember having to do that for my buddy's Rogers Raider. Sorry.. it was some time ago.
He's here so I just checked his phone... we must have put in the SuperCID back then (which may accept any RUU?)
C:\Users\Master>fastboot getvar cid
cid: 11111111
finished. total time: 0.000s
and I ran mine (actual Bell Raider).:
C:\Users\Master>fastboot getvar cid
cid: BM___001
finished. total time: 0.000s
Feeling adventurous? I'm not sure if you need to be S-OFF to do this (or have unlocked bootloader, or even both) but...
You can change the CID via fastboot.
Fastboot commands that you can do: (thank you jmone from showpost.php?p=25187040&postcount=199)
(to check your current CID - write it down?)
fastboot getvar cid
(to write a new CID to the phone)
fastboot oem writecid 11111111 (where the 11111111 contains the CID you want - you can try the 11111111 (is that known as SuperCID?) or you can try mine, which is BM___001 as specified above)
(then reboot into bootloader mode)
fastboot reboot-bootloader
(then if it reboots back into fastboot mode, you can run this to verify your desired CID made it)
fastboot getvar cid
Then maybe the RUU will allow itself to install?
Click to expand...
Click to collapse
I typed in the commands and I got this:
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO holiday_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.076s]
finished. total time: 1.076s
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot getvar cid
cid: ROGER001
finished. total time: 0.002s
So, that means the SuperCID did not manage to write. I searched around and found hints about something called Radio S-OFF or Gold Card, but it was for a different HTC phone...
Is there a guide to follow so i could get this?
BTW SuperCID would allow the user to use any RUU.

LeoCFZ said:
I typed in the commands and I got this:
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot oem writecid 11111111
... INFOvreg_set: request is duplicated id 14
INFO holiday_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.076s]
finished. total time: 1.076s
c:\Users\Leo Zheng\Desktop\Vivid Toolkit\Data>fastboot getvar cid
cid: ROGER001
finished. total time: 0.002s
So, that means the SuperCID did not manage to write. I searched around and found hints about something called Radio S-OFF or Gold Card, but it was for a different HTC phone...
Is there a guide to follow so i could get this?
BTW SuperCID would allow the user to use any RUU.
Click to expand...
Click to collapse
Ahhh.. so you need to be S-OFF it seems. The S-OFF procedure isn't super easy, but it's nice to have (because with S-OFF, the custom roms you install will be able to automatically flash their kernel. With S-ON, to run a custom rom, you need to flash the kernel separately... not a huge deal, but having S-OFF is convenient if you like to try different custom roms). To S-OFF, you have to be willing to void your phone's warranty.
Theres gotta be the Roger RUU out there somewhere (that is ICS). I have the Rogers Gingerbread RUU... but I think it will only work if you havent upgraded your phone to ICS yet...

LaZiODROID said:
Ahhh.. so you need to be S-OFF it seems. The S-OFF procedure isn't super easy, but it's nice to have (because with S-OFF, the custom roms you install will be able to automatically flash their kernel. With S-ON, to run a custom rom, you need to flash the kernel separately... not a huge deal, but having S-OFF is convenient if you like to try different custom roms). To S-OFF, you have to be willing to void your phone's warranty.
Theres gotta be the Roger RUU out there somewhere (that is ICS). I have the Rogers Gingerbread RUU... but I think it will only work if you havent upgraded your phone to ICS yet...
Click to expand...
Click to collapse
I also have the Gingerbread RUU and yes, it does not work. You were right about the ICS RUU out there somewhere.
I dug deeper into the comments of Football's thread on the Shipped RUU Collection to see if anyone had trouble downloading from FileFactory and somebody requested the Rogers ICS RUU mirror there. I downloaded it any now my cell is back to being operational!
http://forum.xda-developers.com/showthread.php?t=1338919&highlight=football&page=14
Thanks to LaZiODROID, ronnie498,and Gene Poole for all their help!
Well, I also like to make sure I don't make the same mistake again. Anyone know why my phone ended up the way it is?

LeoCFZ said:
I also have the Gingerbread RUU and yes, it does not work. You were right about the ICS RUU out there somewhere.
I dug deeper into the comments of Football's thread on the Shipped RUU Collection to see if anyone had trouble downloading from FileFactory and somebody requested the Rogers ICS RUU mirror there. I downloaded it any now my cell is back to being operational!
http://forum.xda-developers.com/showthread.php?t=1338919&highlight=football&page=14
Thanks to LaZiODROID, ronnie498,and Gene Poole for all their help!
Well, I also like to make sure I don't make the same mistake again. Anyone know why my phone ended up the way it is?
Click to expand...
Click to collapse
Amazing! Glad it worked out. Thanks for that link. I'll be archiving a copy of that Rogers RUU.
As for why your phone wouldnt boot with CM9... Is CM9 still in development? Maybe you should try a different ROM.
I'm using Pegasus right now and enjoying it. (As per kozmik I did have to do an extra step to get my LTE going, but it was pretty easy).
Remember to do a backup and your 4 wipes (data, cache, dalvik,and /system) before you install the rom, of course!

OK, thanks for the tips and the ROM suggestion.
I'll try Pegasus next.

LeoCFZ said:
OK, thanks for the tips and the ROM suggestion.
I'll try Pegasus next.
Click to expand...
Click to collapse
Thanks for this post. I had the same problem and was looking on the site to find an answer....

I uploaded all the RUU's here including the rogers one
http://forum.xda-developers.com/showthread.php?t=2013122
from my HTC PH39100 using xda premium

Here's today's brain teaser of a question: if you have Super CID on, do you need to have the bootloader re-locked in order to run any RUU?

Spazmogen said:
Here's today's brain teaser of a question: if you have Super CID on, do you need to have the bootloader re-locked in order to run any RUU?
Click to expand...
Click to collapse
Yes, I am pretty sure you do. I re-locked mine whenever I had to use a RUU.

[Q] My HTC One recently unrooted, how do i return to stock RUU?

I'm S-OFF. My device is recently unrooted, and my version is 1.28.771.10 on the THREE 3 UK network. It seems there isn't an RUU for my phone released by three. Is there any way that I can return to stock so that my phone is as new? Step by step instructions would be appreciated as i'm very new to this. My bootloader is also locked.

I am on 3 UK also.
Have done this many times .
As you have S off you can change your cid (customer or carrier id) from H3G__001 (which is 3 UK)
to so called super cid which is
11111111 (eight 1's)
When in bootloader fastboot usb mode
C:\adb> fastboot oem writecid 11111111
This will allow you to use any version RUU for your model.
Best one is WWE version which has 401 in the place where yours had 771.
I have always been unlocked when doing this. As you have got S off I will assume you can unlock bootloader.
Then download to your pc the appropriate ruu, I would suggest file (very long filename, I will just list first part of filename - will edit post to add download link)
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7
Download this to your pc
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
It's a large file 990 MB .
The following will delete all your data, photos, video, music, txt , etc (phone number should remain in SIM ) so BE SURE TO COPY FROM PHONE TO PC ANYTHING YOU WANT TO KEEP.
Then connect your HTC One to your pc with usb cable (usb 2, preferably) and simply run the program you've just downloaded .
Your phone can be either in fastboot mode or with android running, doesn't matter which .
Follow on screen instructions, ticking boxes as appropriate.
Total process takes approximately ten minutes from starting the program to finish.
When finished you will be on stock 1.28.401.6 which is original Android 4.1.1
However if you wish you can easily update Ota (over the air) through successive versions up to 4.2 by entering settings then about then software updates then check now
Hope this helps
Sent from my HTC One using xda app-developers app

paul_59 said:
I am on 3 UK also.
Have done this many times .
As you have S off you can change your cid (customer or carrier id) from H3G__001 (which is 3 UK)
to so called super cid which is
11111111 (eight 1's)
When in bootloader fastboot usb mode
C:\adb> fastboot oem writecid 11111111
This will allow you to use any version RUU for your model.
Best one is WWE version which has 401 in the place where yours had 771.
I have always been unlocked when doing this. As you have got S off I will assume you can unlock bootloader.
Then download to your pc the appropriate ruu, I would suggest file (very long filename, I will just list first part of filename - will edit post to add download link)
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7
Download this to your pc
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
It's a large file 990 MB .
The following will delete all your data, photos, video, music, txt , etc (phone number should remain in SIM ) so BE SURE TO COPY FROM PHONE TO PC ANYTHING YOU WANT TO KEEP.
Then connect your HTC One to your pc with usb cable (usb 2, preferably) and simply run the program you've just downloaded .
Your phone can be either in fastboot mode or with android running, doesn't matter which .
Follow on screen instructions, ticking boxes as appropriate.
Total process takes approximately ten minutes from starting the program to finish.
When finished you will be on stock 1.28.401.6 which is original Android 4.1.1
However if you wish you can easily update Ota (over the air) through successive versions up to 4.2 by entering settings then about then software updates then check now
Hope this helps
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hey buddy, I know this is an old threat but you're on the exact same network as me and such.
I managed to get back to stock, and i'm on android version 4.1.2... but i can't seem to find any OTA android updates? Which is the main reason why I unrooted my phone. Tried the google framework fix too. Got any ideas?

tomquartey said:
Hey buddy, I know this is an old threat but you're on the exact same network as me and such.
I managed to get back to stock, and i'm on android version 4.1.2... but i can't seem to find any OTA android updates? Which is the main reason why I unrooted my phone. Tried the google framework fix too. Got any ideas?
Click to expand...
Click to collapse
If you are supercid (11111111) you will not get ota. You must change cid to one that match you OS base.

alray said:
If you are supercid (11111111) you will not get ota. You must change cid to one that match you OS base.
Click to expand...
Click to collapse
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?

tomquartey said:
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?
Click to expand...
Click to collapse
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota

alray said:
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota
Click to expand...
Click to collapse
Thank you buddy, will try this soon.

tomquartey said:
I had to SUPER CID to flash this particular RUU.
If I change my CID back now, will this mean my RUU is redundant and then brick my phone?
And the original CID was H3G_001. Do I need to go back to this one?
Click to expand...
Click to collapse
alray said:
no its safe to change CID, you will never get OTA with supercid from this carrier
change back your cid to H3G__001 (2 lower case H3G _ _001)
Code:
fastboot oem writecid H3G__001 [COLOR="SeaGreen"]---> cid change[/COLOR]
fastboot reboot-bootloader [COLOR="SeaGreen"]--> reboot and go back to fastboot usb[/COLOR]
fastboot oem readcid [COLOR="SeaGreen"]--->confirm cid is now H3G__001[/COLOR]
fastboot reboot [COLOR="SeaGreen"]--->reboot to system[/COLOR]
then install ota
Click to expand...
Click to collapse
1- easy on the double posting , then make up your mind, where you wanna post, so people can actually help
2- what ruu are you referring to?
3- no just changing CID back to original (H3G__001) does not mean you're going to get any OTA if the ^^ ruu is not H3G

nkk71 said:
1- easy on the double posting , then make up your mind, where you wanna post, so people can actually help
2- what ruu are you referring to?
3- no just changing CID back to original (H3G__001) does not mean you're going to get any OTA if the ^^ ruu is not H3G
Click to expand...
Click to collapse
I was told to change my RUU to a particular RUU from another user who is on the same network as me.

tomquartey said:
I was told to change my RUU to a particular RUU from another user who is on the same network as me.
Click to expand...
Click to collapse
well if you are on CID H3G_001 then this "change my RUU to a particular RUU" (there is no particular RUU) makes no sense at all, if you are S-Off:
1- you can change CID to unbranded and use an unbranded RUU
2- you can use one of the guides around here to go back to H3G stock

[Q] How to find out what carrier this phone is?

i got the phone stuck on TWRP so i downloaded the telus ruu and installed it fine, then i noticed there was a rogers one too. is there anyway to tell what carrier this phone is for? i have no sim cards to test it out besides a fido one. its the 801e UL variant. someone must be able to help me i have searched everywhere for answers.

In fastboot: fastboot getvar all
This will display your CID

Marc199 said:
In fastboot: fastboot getvar all
This will display your CID
Click to expand...
Click to collapse
ya but what if the cid was changed to 1111111111 to get s-off?

I don't think it is possible to find out what your original CID was. Where did you buy the phone?

gnome9er said:
ya but what if the cid was changed to 1111111111 to get s-off?
Click to expand...
Click to collapse
that's SuperCID, keep it as is and download CIDGetter from Play Store, when it sees SuperCID it will pull CID from a secondary location, hopefully that wasn't changed and it will show your original CID.

[Q] Can't change MID again

Hey guys! I was hoping I could get some help here, I would say I have moderate experience in this area but..
I was changing my Model ID. I got the ENG H-BOOT zip and edited the android-info.txt to my own device. I noticed some things different from the last time I did this. Instead of the fuzzy grey screen it actually had the bootloader showing up. It was the ENG bootloader and was a low version H-BOOT. I then issued the command:
Code:
fastboot oem writemid PN07120
after that I changed my CID and then proceeded to use the BrightStar US RUU for the Developer Edition. It told me:
Code:
FAILED (remote: 41 model id check fail)
Realizing my mistake, I made the zip again with the eng hboot and replaced the necessary variables. ie. modelid: PN07120 but when I try to flash it in RUU mode it still gives me the:
Code:
FAILED (remote: 41 model id check fail)
I keep on trying different combinations but to no avail.
I'd be very grateful if anyone could lend a helping hand. :fingers-crossed:

squabbi said:
Hey guys! I was hoping I could get some help here, I would say I have moderate experience in this area but..
I was changing my Model ID. I got the ENG H-BOOT zip and edited the android-info.txt to my own device. I noticed some things different from the last time I did this. Instead of the fuzzy grey screen it actually had the bootloader showing up. It was the ENG bootloader and was a low version H-BOOT. I then issued the command:
Code:
fastboot oem writemid PN07120
after that I changed my CID and then proceeded to use the BrightStar US RUU for the Developer Edition. It told me:
Code:
FAILED (remote: 41 model id check fail)
Realizing my mistake, I made the zip again with the eng hboot and replaced the necessary variables. ie. modelid: PN07120 but when I try to flash it in RUU mode it still gives me the:
Code:
FAILED (remote: 41 model id check fail)
I keep on trying different combinations but to no avail.
I'd be very grateful if anyone could lend a helping hand. :fingers-crossed:
Click to expand...
Click to collapse
I'll leave this here for now: http://forum.xda-developers.com/showthread.php?t=2535365
EDIT: you do KNOW that MID is more than 7 characters right ???

nkk71 said:
I'll leave this here for now: http://forum.xda-developers.com/showthread.php?t=2535365
EDIT: you do KNOW that MID is more than 7 characters right ???
Click to expand...
Click to collapse
Haha thanks! Ugh yea. I got carried away on something I saw that looked right. :\ Thanks for the link! It looks promising!

[Q] i lost my information i lost everything htc one m7 México

hello, i have a big problem, i lost my information of my htc one i don't have a S.O, but i can enter to bootloader
i can't install a rom by ADB why? i don´'t know my laptop don't recognize my htc only i can use a fastboot
I need a rom or something for my htc go back to life
I tried to install a new firmware by fastboot but i have a error : remote: (24 parsing android-info fail)
And i don't know what to do.
Help me please.
Mi cid is HTC_033
hbot.1.44
TWRP:2.7.1.0

juan_freyre said:
hello, i have a big problem, i lost my information of my htc one i don't have a S.O, but i can enter to bootloader
i can't install a rom by ADB why? i don´'t know my laptop don't recognize my htc only i can use a fastboot
I need a rom or something for my htc go back to life
I tried to install a new firmware by fastboot but i have a error : remote: (24 parsing android-info fail)
And i don't know what to do.
Help me please.
Mi cid is HTC_033
hbot.1.44
TWRP:2.7.1.0
Click to expand...
Click to collapse
its a good job your s-on because by the sounds of it, if you had of managed to flash that firmware then you would now have a nice new shiny brick, the error you got basically means, that firmware is not for your phone.

Seanie280672 said:
its a good job your s-on because by the sounds of it, if you had of managed to flash that firmware then you would now have a nice new shiny brick, the error you got basically means, that firmware is not for your phone.
Click to expand...
Click to collapse
i have a s-off
Basically you say is my phone is bricked?

No you are not bricked, you are only bricked when your phone won't switch on at all.
If you are s-off then change your cid and mid and flash any ruu, you will have to match mid to the ruu you choose to flash, change cid to super cid which is 11111111 (8 x 1s)

juan_freyre said:
i have a s-off
Basically you say is my phone is bricked?
Click to expand...
Click to collapse
bricked phone will not screen on any how computer recognizes qhs USB mode only
from HTC One

yatindroid said:
bricked phone will not screen on any how computer recognizes qhs USB mode only
from HTC One
Click to expand...
Click to collapse
so what can i do for fix my phone?

juan_freyre said:
so what can i do for fix my phone?
Click to expand...
Click to collapse
first tell us fastboot getvar all
Hide imei & serial number from that
There will be version main & cid find a ruu according to that @ htc1guru.com
Flash that ruu
If ruu not found then I will answer according to your situation
from HTC One

juan_freyre said:
so what can i do for fix my phone?
Click to expand...
Click to collapse
did you solve your problem ? send me a pm i can help you lol hablo español xD