Does anyone have an HTC Raider 4G LTE on Bell and can provide me with a Stock Firmware? I tried a custom rom and stupid me, didn't back up my stock one .
I really need to get back to a Stock rom as it seems the custom one on this site is Korean
Any help would be appreciated!
Thanks
you mean like the ones posted here on XDA?
http://forum.xda-developers.com/showthread.php?t=1338919
Thanks Pirateghost - I've tried the on with BM in the name as I'm guessing that's for Bell Mobility. I am getting an error 155 when trying to run the flash.
My Raider has CWM installed on it and a rooted mod. I've booted using the Power-VolDown button and put it into FastLoad. It seems to reboot when the update starts but then just sits at the HTC logo and the flash tool errors out with 155.
Any ideas?
I'm trying to extract the rom.zip from the EXE using Process Monitor. When I find the rom.zip, it seems to be corrupt. Can you confirm that the there is correct?
I was able to finally extra the rom.zip from the BM RUU and everything flashes except for the system image . It says data length is too large.
So I'm kinda stuck right now with this other ROM.
If anyone knows of another source for an HTC Holiday/Raider 4G on Bell (BM), please let me know!
Thanks
OEM LOCK the device BEFORE running the RUU upgrade!!!
Figured it out!!!
You need to re-lock the bootloader before the RUU will actually succeed!
fastboot oem lock
As I'm not cool enough to post in the Development section, can someone post an update to http://forum.xda-developers.com/showthread.php?t=1351717 and let the person know there who is having the same problem I am that he/she needs to re-lock the bootloader before they can apply the RUU? [email protected]!!!
Related
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Hi I was trying to make a rom and ended up in a bootloop, so i made a mistake and flashed the boot.img from the android sdk folder to my raider and now I can't get into hboot, but with adb can get into cwm. i did have a backup and can restore the backup.
now when the restore is complete i try to restart and the phone hangs at the htc logo, then the screen turns black. phone never boots.
any ideas on what might fix this?
Thanks
abray1978 said:
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Click to expand...
Click to collapse
Can you get back into HBOOT now that you did the restore?
I'm by far no expert but I'm curious if you can get back to HBOOT if you can put it into fastboot, re-lock the bootloader (fastboot oem lock) and then use the RUU to restore back to stock. That should fix the boot image and I you then can start the process over again by unlocking and playing.
That's what I did and I'm back to a non-bricked phone. You can get the Holiday (aka Raider) RUUs by searching these forums. Just download the one for your carrier.
Good luck
abray1978 said:
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Click to expand...
Click to collapse
Where did you find an RUU for the HTC Raider?
I need RUU. I am in japan,but there is some thing wrong with my vivid, factory reset did not work....I can just see htc logo and then att logo, and then...though there is a setup but when i click that it shut down directly.....can any one help me ?
http://forum.xda-developers.com/showthread.php?t=1416836
2nd post has the links for stock ruu for all carriers
Sent from my HTC PH39100 using XDA App
thank you sooooo much.
Sent from my HTC PH39100 using XDA App
abray1978 said:
As a quick FYI, I spent a lot of time yesterday trying to get the stock RUU update to flash my HTC Raider. I played around with a custom ROM and wasn't too happy with it, but stupidly I didn't backup my stock rom with CWM... Lesson learned!
Anyways, if you are trying to go back to stock and are hitting Error 155 during the RUU Update, try re-locking the bootload with "fastboot eom lock". I tried this today and the stock firmware flashed on first try and I'm back to the good old Bell bloat!
Hope this helps anyone!
Click to expand...
Click to collapse
Many thanks! I thought that mine Raider was completly dead. Didn't want get into CWM only 2 lines for less than 0.25sec with messsage that is unable to get acces to cache then reboot and stuck with htc logo forever. Then i read this post and my Raider is get back to live.
Many thanks once again.
Thank you so much!
I cannot find an answer to my problem as hard as i look. today, i decided to root my phone (HTC vivid). I rooted it successfully, i went to the Superuser and it said it needed to be updated and to flash a kernel or something like that. (i was using this program http://forum.xda-developers.com/showthread.php?t=1498003) I went to the program that i meantioned above and i clicked flash stock vivid kernel, thinking that this was the kernel i had to update or flash or whatever then my phone reboots and its all like Hurr duur im stuck on the HTC screen watcha gonna do about it. I tried many things:
One thing i tried was to do the .zip thingy, with the boot loader relocked, and it wont boot to anything else but the boot loader
i tried also to do the ruu thing, but it kept giving me errors about my phone model or something like that
Can someone please tell me what i did wrong and how to fix it?
i would really appreciate it big time!
Edit: i have an micro sd, if that info helps
I would try to restore it back to stock.
Relock to bootloader if it isn't still locked.
Then run the stock ruu for your phone from http://forum.xda-developers.com/showthread.php?t=1338919
I had my vivid stuck on the HTC screen and this worked for mine.
Also, If you rooted to ICS you are most likely stuck until the official RUU from HTC is out...
FernandoR211 said:
I would try to restore it back to stock.
Relock to bootloader if it isn't still locked.
Then run the stock ruu for your phone from http://forum.xda-developers.com/showthread.php?t=1338919
I had my vivid stuck on the HTC screen and this worked for mine.
Also, If you rooted to ICS you are most likely stuck until the official RUU from HTC is out...
Click to expand...
Click to collapse
You need to install HTC sync or the htcdrivers before running the ruu otherwise it won't see your phone and will just error out.
Sent from my HTC PH39100 using xda premium
pichi123 said:
I cannot find an answer to my problem as hard as i look. today, i decided to root my phone (HTC vivid). I rooted it successfully, i went to the Superuser and it said it needed to be updated and to flash a kernel or something like that. (i was using this program http://forum.xda-developers.com/showthread.php?t=1498003) I went to the program that i meantioned above and i clicked flash stock vivid kernel, thinking that this was the kernel i had to update or flash or whatever then my phone reboots and its all like Hurr duur im stuck on the HTC screen watcha gonna do about it. I tried many things:
One thing i tried was to do the .zip thingy, with the boot loader relocked, and it wont boot to anything else but the boot loader
i tried also to do the ruu thing, but it kept giving me errors about my phone model or something like that
Can someone please tell me what i did wrong and how to fix it?
i would really appreciate it big time!
Edit: i have an micro sd, if that info helps
Click to expand...
Click to collapse
1. You obviously didn't know what you were doing. Lessons for next time.
2. If the .zip thingy made the bootloader update and it seems like it managed to flash everything alright, then you need to make sure the zip isn't on any storage connected to the phone, then go from bootloader to fastboot, unlock the bootloader using the HTCDev bootloader unlock procedure (I hope you kept your unlock_code.bin!), then fastboot flash a recovery.img, then boot to recovery from the bootloader, and flash an ICS ROM, then go back to fastboot and flash the boot.img to get the kernel flashed.
I'm guessing that you may have flashed the ICS bootloaders, but you aren't specific enough. What ruu did you try to run, exactly what zip did you try to install?
You didn't do anything wrong, you just didn't complete the procedure.
kozmikkick said:
You need to install HTC sync or the htcdrivers before running the ruu otherwise it won't see your phone and will just error out.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Well I hope that was a given. BUt I guess I should have listed it. Good point!
If you have an AT&T Vivid, then you should be okay, run the latest ICS RUU and hope for the best. If not, you'll have to do it the old fashioned way through lots of fastboot commands.
thank you everyone!
/thread
I managed to pull out the Bell ICS OTA from my SDCard and I am sharing it for you guys!
I hope this can fix the annoying fact that we can't use stock WiFi Tether with the ATT base!
Link here: --> OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip <--
I also have a plain Bell ICS nandroid (RUU'ed, directly OTA'ed then Backed up) if you want me to upload it, so just say me if you'd like it and I'll push it sometime during the W/End!
HAND, ideaL
awesome thank you. Dl'ing now
Have you tried to tether on it just wanted to see if it worked on stock bell ics rom
Sent from my HTC Raider X710e
Please upload the RUU aswell if you could please. sine you offered
I tried to see if I can teather and its not working. I think its becouse I'm on holics Rom
zombie.raised said:
Have you tried to tether on it just wanted to see if it worked on stock bell ics rom
Sent from my HTC Raider X710e
Click to expand...
Click to collapse
it does work
raymar23 said:
Please upload the RUU aswell if you could please. sine you offered
Click to expand...
Click to collapse
its not an RUU, its just a nandroid that I saved from a clean installation of ics. If someone know how to make one from the ota file, let me know
azz72 said:
I tried to see if I can teather and its not working. I think its becouse I'm on holics Rom
Click to expand...
Click to collapse
holics is based off of ATT if I remember, so thats why it does not
Sent from my HTC Raider 4G LTE running ICS.
Is there a beats audio belt in, as in at&t build?
Question
Sorry for the dumb question, but I'm guessing this is the flashable zip by recovery same as any other ROM right?, has any one tested this already??
Thanks!
This file is the OTA update file you will get only when you have Bell's stock GB ROM already installed on the Raider. It is not a complete ROM, and if your CID is not BM___001 it will not let you update.
There is no Beat Audio in this ROM.
any luck getting this installed on a stocked rooted bell raider?
I don't really want to wipe again, buddy of mine tried by locking bootloader removing superuser but it failed.
If you are rooted, with unlocked bootloader, and SuperCID your phone, the update will not apply properly, it will even display a message saying your phone's software has been modified and stops right there.
You will probably have to start fresh again.
I managed to flash it on Roger's Raider (to use on Bell).
I was gonna write a tutorial but wasn't sure how many will actually need it the exact same way I do, here is the short version of what I did:
I was already using AT&T ICS (already have s-off, supercid, etc)
1) in fastboot, change CID to BM___001
2) in fastboot, relock bootloader
3) in fastboot, flash Bell GB RUU
4) boot into OS, update to ICS (right from "System Updates" in settings)
5) in fastboot, unlock bootloader (you will need a new unlock bin, the old one from GB didn't work for me, follow the steps at HTCDEV again)
6) in fastboot, flash custom recovery and change CID back to 11111111 if you want
7) boot into the custom recovery you just flashed, and flash supersu package
8) profit.
That's what I did anyway... let me know if anyone wants a longer version of this.
thanks but i have a stock Bell with S-ON and its just rooted. My buddie already got ICS by lock the bootloader and flashing the Bell GB RUU, but i'm looking for a way around itso i don't have to start over.
Nandroid ??
ideaLduK said:
I managed to pull out the Bell ICS OTA from my SDCard and I am sharing it for you guys!
I hope this can fix the annoying fact that we can't use stock WiFi Tether with the ATT base!
Link here: --> OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip <--
I also have a plain Bell ICS nandroid (RUU'ed, directly OTA'ed then Backed up) if you want me to upload it, so just say me if you'd like it and I'll push it sometime during the W/End!
HAND, ideaL
Click to expand...
Click to collapse
Thanks for the work. Would you be willing to upload that nandroid of the fresh ICS install so I can play with it?
Thanks in advance!
raymar23 said:
Thanks for the work. Would you be willing to upload that nandroid of the fresh ICS install so I can play with it?
Thanks in advance!
Click to expand...
Click to collapse
Yeah sure give me an hour or two and ill upload it (putting all the img into a zip than uploading with crappy upstream xD
Sent from my HTC Raider 4G LTE running ICS.
EDIT : Currently being uploaded, ETA 1200 hours GMT-5
EDIT 2 : System partition download link : http://www.filefactory.com/file/26estudnmg3f/n/Stock_BM_ICS_OTA_system.ext4.tar
I only uploaded the system partition because the data is empty, recovery is not needed if you want to mod it, boot is the default kernel and cache was empty as well. Happy tweaking!
technote said:
If you are rooted, with unlocked bootloader, and SuperCID your phone, the update will not apply properly, it will even display a message saying your phone's software has been modified and stops right there.
You will probably have to start fresh again.
I managed to flash it on Roger's Raider (to use on Bell).
I was gonna write a tutorial but wasn't sure how many will actually need it the exact same way I do, here is the short version of what I did:
I was already using AT&T ICS (already have s-off, supercid, etc)
1) in fastboot, change CID to BM___001
2) in fastboot, relock bootloader
3) in fastboot, flash Bell GB RUU
4) boot into OS, update to ICS (right from "System Updates" in settings)
5) in fastboot, unlock bootloader (you will need a new unlock bin, the old one from GB didn't work for me, follow the steps at HTCDEV again)
6) in fastboot, flash custom recovery and change CID back to 11111111 if you want
7) boot into the custom recovery you just flashed, and flash supersu package
8) profit.
That's what I did anyway... let me know if anyone wants a longer version of this.
Click to expand...
Click to collapse
If you are SuperCID (11111111) you dont have to put it back to BM___001. Just flash the RUU than flash the zip. That's what I did and it worked. i was also under ATT firmware.
Sent from my HTC Raider 4G LTE running ICS.
Thanks Again
ideaLduK said:
Yeah sure give me an hour or two and ill upload it (putting all the img into a zip than uploading with crappy upstream xD
Sent from my HTC Raider 4G LTE running ICS.
EDIT : Currently being uploaded, ETA 1200 hours GMT-5
EDIT 2 : System partition download link : http://www.filefactory.com/file/26estudnmg3f/n/Stock_BM_ICS_OTA_system.ext4.tar
I only uploaded the system partition because the data is empty, recovery is not needed if you want to mod it, boot is the default kernel and cache was empty as well. Happy tweaking!
Click to expand...
Click to collapse
Thank you soo much. I didnt want to install it just to get a "base". The last time I tried to cook a ROM was for a SGS, and by the time I could cook anything, the seasonsed devs beat me to it 4 times overs. Developement is slow/scarese for this device so I might have a chance this time. It's gonna time me 9 hours to download the damn thing though
raymar23 said:
Thank you soo much. I didnt want to install it just to get a "base". The last time I tried to cook a ROM was for a SGS, and by the time I could cook anything, the seasonsed devs beat me to it 4 times overs. Developement is slow/scarese for this device so I might have a chance this time. It's gonna time me 9 hours to download the damn thing though
Click to expand...
Click to collapse
If you release anything, please put my name in the thanks for the base !
Sent from my HTC Raider 4G LTE running ICS.
ideaLduK said:
If you release anything, please put my name in the thanks for the base !
Sent from my HTC Raider 4G LTE running ICS.
Click to expand...
Click to collapse
I definitely will. I'm actually ripping through it now. I think I will make a base Bell Rom with root busybox and de-odex first. then add tweaks and such. I don't get much time to "play" with it much as I work full time and have 3 young kids. but keep checking the dev forum for a new Rom ;-)
Double post
It is solved! For the answer look at my post below
Hello guys,
phone HTC one M8 Harman Kardon Edition
Happens that in my urge to unlock my phone sim lock I firstly changed the MID to unlocked SIM Dev edition MID and CID to SuperCID, well that went great until I was dumb enough to try to flash a Dev edition RUU to the phone and then i lost my TWRP recovery and everything went haywire. cause now i try to flash Recovery through fastboot and it suceeds but the phone gets stuck in entering recovery, Im not able to flash a Sprint RUU for HK because 1. i havent found one and 2. it probably wont load because of the MID which is 0P6B1200 if im correct.
please help me either load the Custom recovery so i can have access to adb, or any other way to fix it.
thank you!!
if someone could please give me any ideas, or contact anyone who could help me, it would be greatly apreciated, i can pay up to 20 usd through paypal if anyone can help me!!!
Change your MID back to Sprint and run the Sprint HK RUU...should be good to go.
Nevermind.. As long as you see hboot menu and capable to select different options you are safe and in healthy state.. Even if you want to brk things.. You won't be able to brk.. Just flash twrp 2.8 again using fastboot commands.. You should back on track...
thank you but no
Sarvesh.huddedar said:
Nevermind.. As long as you see hboot menu and capable to select different options you are safe and in healthy state.. Even if you want to brk things.. You won't be able to brk.. Just flash twrp 2.8 again using fastboot commands.. You should back on track...
Click to expand...
Click to collapse
I dont know what is going on but i did that already, even trying the new recovery image, and it gets stuck in the Entering Recovery... step
"Fastboot erase cache" and make sure you are flashing the correct version of twrp(change the MID back to the original one, this is dangerous if there is hardware difference across the 2 MIDs)
Guys all off your help was greatly apreciated but there was something wrong
Ok guys so I was able to fix it.
Although it looked like it was easy to flash the twrp recovery, remember I ran the ATT RUU so the hboot was wrong according to the phone. This means it wouldnt flash the recovery correctly, however something strange happened when i tryed to entered recovery after flashing, it would connect to the computer. When that happened the only thing i thought was that twrp has adb interface, so i instantly checked devices and proceeded to change back the MID. Once that was through i flashed Android 4.4.2 Sprint RUU non HK since the HK was giving unlock issues, then, pasted the Modded HtcOMADM_SPCS.apk and did the
Su am start com.redbend.vdmc/com.htc.omadm.test.TestMainActivity
Then clicked on sim lock
(You must be rooted and check for the moded file in the sim unlock thread on the general section)
And now i was fully funcional and GSM unlocked outside US.
I proceeded then by flashing HK lollipop RUU and then i was back on track.
Hey
jseb14 said:
Ok guys so I was able to fix it.
Although it looked like it was easy to flash the twrp recovery, remember I ran the ATT RUU so the hboot was wrong according to the phone. This means it wouldnt flash the recovery correctly, however something strange happened when i tryed to entered recovery after flashing, it would connect to the computer. When that happened the only thing i thought was that twrp has adb interface, so i instantly checked devices and proceeded to change back the MID. Once that was through i flashed Android 4.4.2 Sprint RUU non HK since the HK was giving unlock issues, then, pasted the Modded HtcOMADM_SPCS.apk and did the
Su am start com.redbend.vdmc/com.htc.omadm.test.TestMainActivity
Then clicked on sim lock
(You must be rooted and check for the moded file in the sim unlock thread on the general section)
And now i was fully funcional and GSM unlocked outside US.
I proceeded then by flashing HK lollipop RUU and then i was back on track.
Click to expand...
Click to collapse
Where do you type the "su ...." command into?
Hello,
I am new to xda forum and expecting a helping hand from fellow members, here's the scenario, I have a sprint htc one which was working fine a few days ago before i decided to act smart .
It was rooted when i purchased it so i thought of flashing a new custom rom into it.I tried flashing (HTC_One_-_MaximusHD_53.0.0) and this one (NuSenSeveN-LP-m7-Sprint_v4.02_050715) and ended up being stuck at green HTC logo, even though the physical buttons are performing their respective functions when pressed but the screen shows just the htc one logo and nothing else.
It is unlocked, tampered and s-on and i have twrp recovery on board, hboot 1.57.0000
WHAT I HAVE ALREADY TRIED AND FAILED:
1) tried rum runner to turn s-off because i though may b because of s-on the roms are not being flashed properly but it says adb device not found
2) tried flashing Bad_Boyz_Sprint_ONE_M7_Lollipop_v2.0 but stuck at handsfree activation, even though i deleted htcwizard.apk.
Now the bottom line is, I am unable to use my device and in desperate need of your help.
Please respond, awaiting to put my hand back on the device.
Thank You
Flashing MaximusHD_53.0.0 messed up your partitions (it's not Sprint compatible as far as I know) and NuSenSeveN you have to fastboot flash the kernel separately ( I had the same problem lol)
The easiest fix would be to run the latest RUU and start fresh, then only flash roms that are Sprint compatible.
Sloth said:
Flashing MaximusHD_53.0.0 messed up your partitions (it's not Sprint compatible as far as I know) and NuSenSeveN you have to fastboot flash the kernel separately ( I had the same problem lol)
The easiest fix would be to run the latest RUU and start fresh, then only flash roms that are Sprint compatible.
Click to expand...
Click to collapse
Hey thanks for the response, I am not tech geek so I have no idea how to flash the latest RUU can you please be more specific about how to perform the above mentioned process or can you have a chat on hangouts as I have altready added you on it.
Thanks alot
Try to flash ruu which could be found on other posts do u know how to boot into the bootloader?
problem solved
Update: thanks to @Sloth I have fixed the problem, if anyone out there who owns a sprint htc one and have messed up his phone by flashing an incompatible rom the way i did, first relock your bootloader if you are s-on and then simply download RUU file from htc official website, make sure its for sprint variant.
Once the bootloader is relocked simply run ruu.exe file that you have downloaded and you are done.
Note: if the ruu setup says that you phone is not connected or gets stuck, boot into recovery and perform factory, after that re-try running ruu.
Thanks Sloth, and thanks xda members