HI, quick noob question,
I have a rooted, stock rom, bell htc raider with CWM 5.5.0.4 recovery.
What steps should I take to prepare for the upcomming OTA update to ICS.
I read that the safest way to do this is to get it as close to stock as possible, how do I do that?
I found a method for the AT&T phones but obviously since bell hasn't released the update yet I wont find one for mine.
thanks for any help you can give me.
PatG20
*edit, I used the same method as the At&t phones, found an original RUU for Bell, relocked the bootloader and ran the RUU. back to bone stock.
AT&T RUU
Run the ICS AT&T RUU and use a Custom ROM like Dark Raider until we get the official update from BELL or ROGERS.
Related
Hi xdaers!
My problem is I've updated my Bell Raider to ICS after S-OFF, and after that, when I am in call, peoples say that they hear themselves in echo thru my device. This is really annoying for them, but also for me when I try to call a voice controlled customer service.
I have tryed the Telsra RUU as well as the ATT, each one with following the said below process :
1) Relock Bootloader
2) Flash my original Bell RUU
3) Flash either of the ICS RUUs
4) Flash unlocktoken via fastboot
5) Flash custom ICS ROM (I've tried Holics, RumFloat, Dark Raider, Virtuous Inquisition...)
Anyone has the solution for that or has experienced the same issue?
Thanks, idealduk
Sent from my HTC Raider 4G LTE running ICS.
ideaLduK said:
Hi xdaers!
My problem is I've updated my Bell Raider to ICS after S-OFF, and after that, when I am in call, peoples say that they hear themselves in echo thru my device. This is really annoying for them, but also for me when I try to call a voice controlled customer service.
I have tryed the Telsra RUU as well as the ATT, each one with following the said below process :
1) Relock Bootloader
2) Flash my original Bell RUU
3) Flash either of the ICS RUUs
4) Flash unlocktoken via fastboot
5) Flash custom ICS ROM (I've tried Holics, RumFloat, Dark Raider, Virtuous Inquisition...)
Anyone has the solution for that or has experienced the same issue?
Thanks, idealduk
Sent from my HTC Raider 4G LTE running ICS.
Click to expand...
Click to collapse
yes i have the same problrm on my aus htc velocity i have s-off and dark raider rom htc boot loader unlocked and echos flashed to just the standard telstra RUU that i had nandroid backed up and no complains about echos but when i flashed darks rom again same echo let me know if u find a fix thanks.
IkIlLaR said:
yes i have the same problrm on my aus htc velocity i have s-off and dark raider rom htc boot loader unlocked and echos flashed to just the standard telstra RUU that i had nandroid backed up and no complains about echos but when i flashed darks rom again same echo let me know if u find a fix thanks.
Click to expand...
Click to collapse
Having the exact same issue someone please help
IkIlLaR said:
yes i have the same problrm on my aus htc velocity i have s-off and dark raider rom htc boot loader unlocked and echos flashed to just the standard telstra RUU that i had nandroid backed up and no complains about echos but when i flashed darks rom again same echo let me know if u find a fix thanks.
Click to expand...
Click to collapse
Did
you flashed the ICS RUU from Telsra or the GB one?
joeish said:
Having the exact same issue someone please help
Click to expand...
Click to collapse
If I find anything I'll let you know!
Sent from my HTC Raider 4G LTE running ICS.
I did the write cid 11111111 before and did soff and also ran the att gb ruu first then ran the att ruu after. Same thing on my bell raider. Im looking to integrate my old ril or radio into this ics.. im on virtouious rom now. Never tried anything else. On samsung phones and such they just flash their old gb ril or delete and copy the system file over to their new rom
ideaLduK said:
Hi xdaers!
My problem is I've updated my Bell Raider to ICS after S-OFF, and after that, when I am in call, peoples say that they hear themselves in echo thru my device. This is really annoying for them, but also for me when I try to call a voice controlled customer service.
I have tryed the Telsra RUU as well as the ATT, each one with following the said below process :
1) Relock Bootloader
2) Flash my original Bell RUU
3) Flash either of the ICS RUUs
4) Flash unlocktoken via fastboot
5) Flash custom ICS ROM (I've tried Holics, RumFloat, Dark Raider, Virtuous Inquisition...)
Anyone has the solution for that or has experienced the same issue?
Thanks, idealduk
Sent from my HTC Raider 4G LTE running ICS.
Click to expand...
Click to collapse
Same issue here as well. I think it may something to do with the mic sensitivity. Turn the volume down on your speaker, a couple notches, ask your friends if they still hear the echo (feedback). My friends don't complain anymore.
Maybe with the ICS OTA just released we can get the update.zip from it?
Where did you get the stock ruu?
THe ICS OTA upgrade craps out on mine because of the CWM I installed.
I'm guessing if I go back to stock the OTA upgrade will work - or am I way off here?
I'm having trouble finding either the stock ruu, or even a modded ICS version to load on the Raider.
Alright so its been a while since I flashed things on my Bell Raider. I have a stock Bell Raider that is just rooted with an unlocked bootloader (will refer to as BL from now on).
I want to flash ICS but do not want to wipe using the Bell RUU. I have been googling around and it says it will work as long as you are as close to stock as possible which I am minus root and recovery.
I used the Bell RUU and extracted the FW.zip file, which contains the recovery_signed.img, so i need to know if its 1.) safe to flash back to stock recovery and 2.) How do i do it using fastboot command?
I want to try this first and as a last resort I will use the RUU and then upgrade.
jebise101 said:
Alright so its been a while since I flashed things on my Bell Raider. I have a stock Bell Raider that is just rooted with an unlocked bootloader (will refer to as BL from now on).
I want to flash ICS but do not want to wipe using the Bell RUU. I have been googling around and it says it will work as long as you are as close to stock as possible which I am minus root and recovery.
I used the Bell RUU and extracted the FW.zip file, which contains the recovery_signed.img, so i need to know if its 1.) safe to flash back to stock recovery and 2.) How do i do it using fastboot command?
I want to try this first and as a last resort I will use the RUU and then upgrade.
Click to expand...
Click to collapse
I am at my girlfriends place ATM. I will upload it for you as soon as I get back home later tonight. Otherwise if you want to extract it by yourself from the RUU, email me @ [email protected] and I will send you the procedure.
Sent from my HTC Raider 4G LTE running ICS.
Help I have a htc vivid it was 4.0 I did root and change the rom to 4.1.2
I did not know why but I put the PH39IMG and returned to be 2.3.4
4.0 and wanted to put it down on the page ruu htc
but every time I try to install it says error 155 something like that you can not upgrade the rom image
I gave up searching google and decides to do a root and no root reading for this version of android
Anyone know how I can do to make it 4.0 or a root to that version 2.3.4
thanks
The Smartphone is out of USA and here I am in Panama there is no coverage for updating ATT
The best thing to do would be to determine if your device is locked or unlocked, if you are unlocked you should lock the device and download the RUU for ICS, since the phone came from the US look for the ATT or Cingular ICS RUU. If you are locked just download that RUU and run the RUU from your computer. This will install ICS. This will also ensure you have the correct HBoot for running any newer android (4.0 or 4.1).
I think 1.85.0025 is the ICS hboot
Sent from my Vivid 4G using Tapatalk 2
I got an unlocked HTC One that was originally on AT&T's network, but now I use it on T-Mobile. The OTA updates won't work since I'm not on AT&T's network and the RUU file has not been released yet. I'm debating whether I should root the device, wait for the RUU file, or bug a friend to use their AT&T sim card to get the update. I'm currently running android 4.1.2 and sense 5 (software number 1.26.502.10). Also if the RUU file does come out can I use it from 4.1 to get to 4.4 or will there be issues?
Thanks
wbrianw said:
I got an unlocked HTC One that was originally on AT&T's network, but now I use it on T-Mobile. The OTA updates won't work since I'm not on AT&T's network and the RUU file has not been released yet. I'm debating whether I should root the device, wait for the RUU file, or bug a friend to use their AT&T sim card to get the update. I'm currently running android 4.1.2 and sense 5 (software number 1.26.502.10). Also if the RUU file does come out can I use it from 4.1 to get to 4.4 or will there be issues?
Thanks
Click to expand...
Click to collapse
The easiest way is to borrow your friend's sim card but that just keeps you locked into AT&T's network. Since, you are running on T-Mobile it may be better to change your phone to look like T-Mobile so you can get all of the benefits of T-Mobile including their OTA updates. You can use this guide Complete Flashing Guide | Rooting to Unlock your bootloader, install custom recovery and root. Then I would use this guide get S-OFF. Once you are S-OFF, then change your MID using this tool MID change without ENG HBOOT then change the CID. You can use this guide nkk71's SuperGUIDE to returning 100% back to stock to show the steps to install the latest T-Mobile RUU. Once the RUU is installed you are set with a stock T-Mobile rom, recovery and S-OFF. Keep S-OFF as long as you can, don't return to S-ON!
majmoz said:
The easiest way is to borrow your friend's sim card but that just keeps you locked into AT&T's network. Since, you are running on T-Mobile it may be better to change your phone to look like T-Mobile so you can get all of the benefits of T-Mobile including their OTA updates. You can use this guide Complete Flashing Guide | Rooting to Unlock your bootloader, install custom recovery and root. Then I would use this guide get S-OFF. Once you are S-OFF, then change your MID using this tool MID change without ENG HBOOT then change the CID. You can use this guide nkk71's SuperGUIDE to returning 100% back to stock to show the steps to install the latest T-Mobile RUU. Once the RUU is installed you are set with a stock T-Mobile rom, recovery and S-OFF. Keep S-OFF as long as you can, don't return to S-ON!
Click to expand...
Click to collapse
Thanks so much for the help, I'll try that when I get the chance.
I currently have a AT&T HTC One (m7). I have my phone rooted and my recovery flashed with TeamWin. I'm still on Jellybean and haven't upgraded. I'm confused what direction I should take. I want to update to the official Kitkat image for AT&T and have my recovery flashed still with teamwin and rooted. I currently have S-ON.
Here's a few questions that I tried finding answers for in old thread post, though I'm just confusing myself more.
Should I take S-Off? Since I'm still on Jellybean and I hear it's easier... can I revert back to my phone looking stock if I do this?
If so how do I do it on Jellybean?
How would I revert back to stock, S-On, stock recovery, no root from Kitkat, S-off, rooted, flashed recovery?
Can I upgrade from Jellybean, with flashed recovery and root to Kitkat without losing all my data? How would I do this?
Thanks for any support you can provide with any of these questions. I've been trying to answering them though the more I read the more confused with a direction I should take. Thanks for your time read thru this, if you need me to explain anything further please let me know.
Yes Do SOFF now, if you can.
Then all you need is stock recovery and stock ATT JB system. IF you have modified the system/removed pre-installed apps, you may run into issues with OTA.
Best case scenario will be to SOFF and then move to US DEV, this will remove ATT bloat, while Keeping the sense. Ofcourse more work.