Edited in blue font on 3/24/2012 @ 9:11PM
FYI:
WARNING!
Several people have had serious issues in updating to ICS while using a custom rom/recovery. I hate seeing bricked devices & if you were an early user of the custom recovery, there was an overwrite flaw that can cause serious issues when updating using ruu's & other factory firmware such as OTA's.
While this has been used by many & is the safest way to update, I do not know what changes you have made to your device/firmware. As always, anything custom is used at your own risk, that said I believe this is the safest way to update to ICS particularly for those that have not changed their recovery since the first release or two. Theire are detailed instructions to help you minimize the risk involved with updating an unlocked device.
Before updating to ICS, make sure you have a newer version of Recovery. One of the first recoveries released could not be overwritten without first flashing another moddified factory recovery first. Updating your device firmware with the older non-writable recovery will stop the device from reflashing the needed files after the first reboot & may cause other issues for some users.
If you try to update to ICS using this recovery you will get BSOD, boot loop or worse, qshsub_dload. All of these are fixable, but the last is still being worked on & as of this time requires jtag/riff to recover from.
If you're using a custom recovery that is older, take note of version & try to flash newer recovery. If recovery fails to be updated, then you are using a flawed recovery & need to flash two files before updating to ICS.
I highly recommend fastboot flashing to the attached recovery before updating your device. This recovery has many features & is more current than the release in the thread. You will have to re-install the recovery again after using the PH39img ICS update, which changes your SBL, Radio & other component firmware required to run ICS.
If you want to use the stock OTA, it is recommended that you return to stock recovery & relock your device using ADB/Fastboot. To flash stock ruu or OTA, you must relock your device. It can be unlcoked using the unlock bin file again from HTCDev.
The command to relock you device is "fastboot oem lock"
This info is in particular for AT&T customers.
The absolute safest way to update to ICS is to relock your device & return it to as close to stock as you can get it. Relocked you can flash the leaked GB AT&T rom in football's thread. Once complete, you can now download a final RUU from the HTC website at: http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe
Using the stock GB recovery & firmware in conjunction with the new RUU is probably the best way to ensure a safe flash since you are then using firmware tested by HTC on devices & made to work together. We have know for some time that locking the device is temporary & unlocking it again can be acheived in many cases with your original unlock_code.bin, or by simply obtaining a new unlock_code.bin after registering/logging in to the htcdev.com website.
The next safest way to update is to return to GB & the stock recovery, relock your device & receive the OTA update. But for those that want to live in the fast lane, lol, this is the method that I & several hundred others have used without incident.
I am posting a link that includes many tools & a custom recovery that I highly recommend. Take note of the information in the Instructions.txt to have a safe ICS upgrade experience.
The recovery included is CWM based recovery. The only difference is it adds some touch support & correct Nand backup abilitiy as well as some nice tools available in newer versions. If you are NOT familiar with flashing via fastboot, all you have to do is extract the zip to the any folder & double click the batch (.bat) files & they will automatically write the recovery or whatever boot.img you select. The recovery script is only for the WCX version of CWM though. Just make sure you extract the files to a folder on your PC that does not have any spaces in the naming. That means if your pc is named Joe Smith-PC, you cannot use the Documents folder or any library folders, so I suggest using C: or create a new folder in c: without space, i.e. C:/Android
The wcxrecovery is CWM based, just more recent, updated with full nand backup support & capacitive button support. All of the files have been safely used & tested extensively by WCX, his rom team & his beta testers. The recovery is also compatible with all of the custom roms (GB & ICS) that I have played with. These items are for users & not to be cooked into public roms without permission of Wild Child. I posted it here due to all of the requests for help I have gotten over the last several days & the amount of time it was costing with one on one support.
If you choose to use the All-In-One tool located Here: http://forum.xda-developers.com/showthread.php?t=1498003 to unlock your device again & still want to use the newer wcx recovery in my zip, you can simply navigate to the /data/recovery folder for the all-in-one kit & replace the recovery included there with the wcxrecovery.img & then copy the existing recovery name (should be recovery-cwm-vivid-5.5.0.4B2.img) delete the file recovery-cwm-vivid-5.5.0.4B2.img, & rename the wcxrecovery.img to recovery-cwm-vivid-5.5.0.4B2.img. You can then use the all in one tool to unlock & flash the new recovery, albeit a few more steps than just using the batch file I included.
Thank you to the developers & owners of the included firmware/tools for allowing users to safely update custom roms to ICS. Please do not Donate to me for any of these items, I merely packaged together the work of others & wrote a pair of scripts to make things easier.
http://www.mediafire.com/?n4x2pcn1jw0g206
Hey can you include a cwm recovery image as well
Sent from my HTC PH39100 using XDA
The wcxrecovery in the zip is CWM based. It is just updated & it includes capacitive button support.
We have two videos...one is for those who have already unlocked their bootloader and one for those with a brand new phone wanting to unlock the bootloader from being locked from the factory. They will probably be updated again but here are the beginning videos
Already Unlocked Phone Video ccb101
Locked Phone From the Factory New Video Randong
WC
Just got a error when trying to download.
Third try it worked.... Sorry false alarm.
Sent from my HTC PH39100 using XDA
GSLEON3 is great! Good advice. I was on gingerbread but had an unlocked boot loader and rooted. Did exactly as he said, relocked boot loader, reinstalled gb to factory standards, accepted ics ota, installed and unlocked my phone. No need to rush into getting ics. It is not worth messing up your phone to save a couple of minutes. It took very little time, maybe an hour in all. Just make sure to have your phone charged up as well.
The videos run through everything from flashing hboot to finally flashing the roms
Dropbox suspended my account for 3 days due to high traffic I am uploading it now for wildchild and he will upload it to his YouTube page. Sorry for any inconvenience. Eta is about 2 hours from now.
Sent from my HTC PH39100 using xda premium
ccb101 said:
Dropbox suspended my account for 3 days due to high traffic I am uploading it now for wildchild and he will upload it to his YouTube page. Sorry for any inconvenience. Eta is about 2 hours from now.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Thanks for you work on the video! I really learn so much by watching someone else do the steps. That is not cool how they suspended your account.
megatronisabeast said:
Thanks for you work on the video! I really learn so much by watching someone else do the steps. That is not cool how they suspended your account.
Click to expand...
Click to collapse
Your welcome glad I could help
Sent from my HTC PH39100 using xda premium
Video finally edited and uploaded to youtube channel
WC
My toolkit has been updated with this new recovery.
http://forum.xda-developers.com/showthread.php?t=1498003
Wild Child said:
Video finally edited and uploaded to youtube channel
WC
Click to expand...
Click to collapse
Just curious... as I don't own the AT&T version.
where about is that recovery flash-able AT&T ICS file shown on the video ??
all I see available are the RUU and the Velocity version..etc
BTW... I have the Rogers version but SIM unlocked it to use with Bell ( and other carriers ).... for future reference... I can only flash Rogers released version...correct ??
Or when DEV released a universal version... then all bets are off ?? LOL
Thanks
UnicornKaz said:
Just curious... as I don't own the AT&T version.
where about is that recovery flash-able AT&T ICS file shown on the video ??
all I see available are the RUU and the Velocity version..etc
BTW... I have the Rogers version but SIM unlocked it to use with Bell ( and other carriers ).... for future reference... I can only flash Rogers released version...correct ??
Or when DEV released a universal version... then all bets are off ?? LOL
Thanks
Click to expand...
Click to collapse
http://www.wcxxperia-nce.com/index.php
Here you go. Several versions available. You have to sign up to see the vivid forum. This is wild child's site. Just follow all directions and you won't be disappointed.
You don't want to use the ruu to flash the att ics if you are on rogers. It would change the radio and you wouldn't be able to use your phone.
megatronisabeast said:
http://www.wcxxperia-nce.com/index.php
Here you go. Several versions available. You have to sign up to see the vivid forum. This is wild child's site. Just follow all directions and you won't be disappointed.
You don't want to use the ruu to flash the att ics if you are on rogers. It would change the radio and you wouldn't be able to use your phone.
Click to expand...
Click to collapse
There's no love there for us Bell & Rogers owners ?
I thought ... by SIM unlocked + Bootloader unlocked & rooted roms & everything... I now have a world phone that can adapt to the spec Freq. , that I can take anywhere ?...etc. ( provided that the country uses one of the compatible freq. )
how does this radio part of thing come into play ?
I've been able to use my past devices flashing different radios on them and have used them oversea successfully 3G+ ...etc
actually... AT&T freq. bands are compatible with BELL & ROGERS up here in north.... it's T-Mobile that uses the incompatible freq.
There is no changing radios on these phones,only boot.img,recovery.img and a rom....no s-off no radios flashing
Wild Child said:
There is no changing radios on these phones,only boot.img,recovery.img and a rom....no s-off no radios flashing
Click to expand...
Click to collapse
my original Nexus One can flash custom radios with S-ON intact. why is that so ?
UnicornKaz said:
my original Nexus One can flash custom radios with S-ON intact. why is that so ?
Click to expand...
Click to collapse
Well I can tell you the raider/vivid is not able to flash radios with S-0n. if we could i would have ICS already.
You may find the answer as to why you can flash the radio with S-on in the nexus One thread.
Just a thought.
Ahh...Technically not true. The RUU & PH39IMG files have.....New Hboot & radios in them as well as SBL files. So, as long as the signaturre is correct, you can flash radios. You just can't use CWM to flash radios, but why would you want to anyway? There are not many compatible LTE radios out there yet, so it is pointless.
As for the NEXUS One...It is a Nexus line & is you are flashing radios from anything other than OEM PHxxIM.zip or RUU, then the radio secu_flags most certainly are off, regardless of S-Off Hboot status.
But whomever started the "you can't flash radios on S-On devices" was misinterpreted or misunderstood. With correct signature & byte typing you can flash modem, misc, hboot, sbl, & radio files. Just nobody has packaged all the tools & written the scripts that are needed to make it feasible & simple enough for average users.
Getting the phone to say S-Off is just a matter of two bytes in the image, however, to truly be S-Off (Even many S-Off devices are not truly S-Off in the strict sense) you need the radio, hboot/spl & kernel to all agree.
do we have to be locked to do the ics ruu update?
Related
If I am correct I can install a Custom Rom with out turning S-Off if I install a extra image. Am I correct on this or do I need to turn S-Off to use custom rom. I been trying to try and read everything I can but getting a little lost on the custom rom. I have turned off the Bootloader from HTC Dev and Rooted. Also I have CWM installed can I install a Rom like I would with a Samsung. Ex. Log into the recovery and point it to the zip I want and install and reboot or is there a step I need to add as I do not have S-Off. Thanks for the help.
Have a look in the superguide, it has all you need to flash roms You can flash custom roms with your setup with cwm, depends on your HBOOT (when you fastboot flash things). There are steps in the superguide, you may have to update it
Sent from my HTC Velocity 4G using xda premium
Think I got it.
You need S-Off if you going from a stock GB rom to a ICS rom. Now if Rogers ( My Provider ) updates to a ICS rom then I will not need to have S-Off to put a custom rom on my phone. My Next Question is - Is it possible to update my phone to a AT&T stock ICS rom. Then from there update to a custom firmware ICS rom. With out doing S-Off. I know for samsung you could put AT&T roms on a Rogers Phone and all you had to do was fix the APN. Is this the same as HTC.
Ah, sorry, misread the 'Rogers' part... I'm pretty sure (someone with more knowlege should verify this...) you can't, something to do with the region/carrier which I think is the HBOOT is not compatible with any other roms from other regions; I remember reading a post from bannanacakes and he said something along the lines of not being able to get ICS until either his carrier provided it, or until s-off came along... I'm 99% sure you do need s-off to get ICS... sorry, wish I knew more, I'm in a bit of a hurry, so no time to read more, will add to this after a bit of a read
EDIT:
ah, here you are, this is if you want ICS on Rogers: http://forum.xda-developers.com/showthread.php?t=1612685
[Guide] ICS for All htc holiday
And it does confirm that you do need s-off :/
Thanks that gives me some stuff to think about. I may wait for the Rogers ICS.
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
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Yes there a some ROMs in the Development section that are completely stock that you can flash through recovery.
The original GB 2.3.3/Sense 2.1, the GB 2.3.5/Sense 3.0 and the latest ICS 4.0.4/Sense 3.6
markj338 said:
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
Click to expand...
Click to collapse
I'm going to sell my device so I need it back the way it was. I want to keep it rooted though, so that the next owner can decide for himself what he wants to do with it. If he he's no techie, he can enjoy the device in stock (including OTAs, or can this be done like you mentioned?). If whe wants to toy with it, he can do that too. If it's easier to just go back to stock entirely, that's fine too.
It seems that I can no longer get into hboot now? After installing that hacked gingerbread, my device just boots into Android when pressing volume down and power??
tpbklake, I'll try to flash one of those when I can get back into recovery
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
gladii said:
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
Click to expand...
Click to collapse
Yes
But since you want stock it won't matter
You CANNOT have both root and ota updates
Either one or the other unfortunately
You have to make a choice a rooted stock ROM will be identical to the official ota from htc but you will be able to keep root, but can't get ota updates
but unfortunately I think sense 3.6 4.0.4 is the last update
But, I have been proven wrong before
Sent from my Nexus 7
K then in my case a full stock device would be best. How do I get started with this? First install a stock ROM, then the stock recovery and then put It back in S-OFF? Which ROM should I install (would prefer the stock 2.3.3)? And where can I find the recovery? Sorry for the basic questions but those lists of ROMs can get a bit complicated..
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
gladii said:
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
Click to expand...
Click to collapse
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Nonverbose said:
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Click to expand...
Click to collapse
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
gladii said:
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
Click to expand...
Click to collapse
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Please read the post that nonverbose referenced for you. That tells you all you need to do.
tpbklake said:
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Click to expand...
Click to collapse
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0af340/n/RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe)
gladii said:
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0a...5AU_3805.06.03.03_M_release_199399_signed.exe)
Click to expand...
Click to collapse
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
tpbklake said:
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
Click to expand...
Click to collapse
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
World Wide English with support for most European languages
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
Ah, perfect! Canceled my download, but there's a 20 minute interval before starting a new one, so it'll take me at least an hour to download it.
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
gladii said:
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
Sounds like it may be a port issue, cable issue or driver issue on the PC.
Have you tried different ports or a different cable? Do you have HTC Sync running in the System Tray on the PC?
As for the hboot file, yes that is the one.
gladii said:
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Nonverbose said:
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Click to expand...
Click to collapse
No I wanted it back the way I wanted it. Rom, recovery,... all stock. But surely I'll give ICS a testdrive via OTA
Firstly, thank you for reading this post. I appreciate that there are a number of posts already covering a lot of what I will be asking (I have already checked and Googled) but in much the same way you end up watching a video of a cat rescuing a child from Narnia on YouTube when you originally started with videos about the political stability in the Middle East, the tedious link between start and finish is now well and truly blurred!
With the above in mind, the aim of this post is to try and collate answers to my questions in one place. I will try and be as clear as possible.
It is also worth mentioning I am not completely new to this. I previously owned an HTC Sensation which I rooted myself (even used the paper clip technique) but the world of ROMs and “Framework” etc seems to be totally different to what is was a few years ago.
I suppose I will start with the basics, the custom recovery.
I have used both CWM and 4EXT in the past and am wondering which is favourable for the HTC One? A lot of posts I have read use CWM but an advantage I found with 4EXT was the ability to flash Kernels without having to go through the whole Super CID route I had to with my Sensation. Am I concerned about an issue that no longer exists or are the benefits of using 4EXT still relevant for the HTC One?
Secondly….and sort of thirdly, kernels and ROMs. Obviously I am wanting to OC the HTC One and I have found a number of kernels which allow this. I have also found a number of custom ROMS which include kernels that allow for over clocking….fine, except the “thirdly” part of this question is the difference between custom ROMs and the “Xposed” framework I have been reading about.
If I flash a custom ROM will Xposed still work or is it a case of one or the other?
To me, it seems the Xposed framework is the preferred option by a number of people for the very detailed level of customisable options it provides without (almost) any of the unwanted parts.
I appreciate the above might be a bit tongue tied so here is a simpler way of what I am asking:
• Custom ROM + Kernel + Xposed – Possible? And or necessary?
• Kernel + Xposed – Possible?
• Custom ROM + Kernel – I know this is possible.
Now, if the first bullet point is possible, I would like to know of a few 4.3 ROMs I can use. Please remember I am on the international UK version. A number of posts have US 4.3 ROMs but every time I look for international compatible ROMs it only ever states 4.2.2.
Is there a 4.3 ROM available for the UK HTC SIM Free One?
Note* The ROMs do not have to include kernels, I can find a compatible one easy enough.
Lastly, S-OFF.
If the original question about recovery images is negative, do I have to S-Off the device and S-CID etc?
If you got this far, thanks for reading and hopefully you can make things a little clearer than mud!
First thing I'd do is check the HBOOT on the phone as if you're on 1.44 I'd S-OFF it NOW! Even if you never do anything else it gives you the option in future
I'd then just use the phone as normal as this is the first phone I've not had to root...
If you DO want to go down the rooting route, then I'd look at Android Revolution HD which is currently running the latest leaked build for the EU handsets and works 100% fine on the unbranded EU/UK handset
EddyOS said:
First thing I'd do is check the HBOOT on the phone as if you're on 1.44 I'd S-OFF it NOW! Even if you never do anything else it gives you the option in future
I'd then just use the phone as normal as this is the first phone I've not had to root...
If you DO want to go down the rooting route, then I'd look at Android Revolution HD which is currently running the latest leaked build for the EU handsets and works 100% fine on the unbranded EU/UK handset
Click to expand...
Click to collapse
Thanks Eddy,
I would like to go down the rooting path due to the OC and customisable options.
I will check the HBOOT though when I get it in a few days....
Thanks.
Anyone else with any other comments on OP?
http://forum.xda-developers.com/showthread.php?t=2365506
Sent from my HTC One using Tapatalk
r1tesh said:
http://forum.xda-developers.com/showthread.php?t=2365506
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks for the link.
I did already find this and have it saved as a point of reference for when I figure out what I need to do.
I think my questions above still require guidance though as I am already aware updating firmware will require S-Off and S-CID but when I rooted my second Sensation, 4EXT allowed for the flashing of certain things without the requirement to S-OFF or S-CID (paper clip trick).
Furthermore, this doesnt touch on the ROM vs Xposed query but as mentioned, thanks for the link.
WOW long post
ssjghost said:
Lastly, S-OFF.
If the original question about recovery images is negative, do I have to S-Off the device and S-CID etc?
Click to expand...
Click to collapse
Actually, this should be firstly, S-Off if you can (at the moment that's only for hboot 1.44 pre June 2013, or using a JavaCard); use vomer's guide posted above.
Things have changed since Sensation, S-Off is good to change CID (IF needed), but a must for flashing unsigned firmware. (not to mention running a downgrade RUU)
However, even with S-On, you can still flash custom ROM, kernel, recovery, and even radio, using HTCdev to get an unlock token for your phone.
ssjghost said:
I suppose I will start with the basics, the custom recovery.
I have used both CWM and 4EXT in the past and am wondering which is favourable for the HTC One? A lot of posts I have read use CWM but an advantage I found with 4EXT was the ability to flash Kernels without having to go through the whole Super CID route I had to with my Sensation. Am I concerned about an issue that no longer exists or are the benefits of using 4EXT still relevant for the HTC One?
Click to expand...
Click to collapse
You'll need to use either CWM or TWRP, I believe 4EXT is not (yet) compatible with HTC One M7. As mentioned above both these recoveries are able to flash ROM, kernel and radio. S-Off and SuperCID not needed. Download those from the threads in xda, not the official web site as the ones in the thread are more up to date.
ssjghost said:
• Custom ROM + Kernel + Xposed – Possible? And or necessary?
• Kernel + Xposed – Possible?
• Custom ROM + Kernel – I know this is possible.
Click to expand...
Click to collapse
All three possible. :good::good:
ssjghost said:
Now, if the first bullet point is possible, I would like to know of a few 4.3 ROMs I can use. Please remember I am on the international UK version. A number of posts have US 4.3 ROMs but every time I look for international compatible ROMs it only ever states 4.2.2.
Is there a 4.3 ROM available for the UK HTC SIM Free One?
Click to expand...
Click to collapse
I can't say for all ROMs, but many of them are/were based on the US Developer edition, which was one of the first to receive 4.3, but were recoded to be WWE editions, that would work for UK.
Just remember to stay away from Sprint and Verizon editions, as these are completely different.
ssjghost said:
Note* The ROMs do not have to include kernels, I can find a compatible one easy enough.
Click to expand...
Click to collapse
The ROMs do include a kernel, but you can flash any other kernel after having flashed the ROM; so by extension every time you flash a ROM, you would need to reflash your custom kernel (making sure it's compatible with the ROM base obviously).
Hope that helps out a little, and remember to hit the thanks button for all that helped
nkk71 said:
WOW long post
Actually, this should be firstly, S-Off if you can (at the moment that's only for hboot 1.44 pre June 2013, or using a JavaCard); use vomer's guide posted above.
Things have changed since Sensation, S-Off is good to change CID (IF needed), but a must for flashing unsigned firmware. (not to mention running a downgrade RUU)
However, even with S-On, you can still flash custom ROM, kernel, recovery, and even radio, using HTCdev to get an unlock token for your phone.
You'll need to use either CWM or TWRP, I believe 4EXT is not (yet) compatible with HTC One M7. As mentioned above both these recoveries are able to flash ROM, kernel and radio. S-Off and SuperCID not needed. Download those from the threads in xda, not the official web site as the ones in the thread are more up to date.
All three possible. :good::good:
I can't say for all ROMs, but many of them are/were based on the US Developer edition, which was one of the first to receive 4.3, but were recoded to be WWE editions, that would work for UK.
Just remember to stay away from Sprint and Verizon editions, as these are completely different.
The ROMs do include a kernel, but you can flash any other kernel after having flashed the ROM; so by extension every time you flash a ROM, you would need to reflash your custom kernel (making sure it's compatible with the ROM base obviously).
Hope that helps out a little, and remember to hit the thanks button for all that helped
Click to expand...
Click to collapse
Perfect! Thats the answer I was "rooting" for.......
Although, your detailed answer has prompted another question.
Given that I can flash ROMS, Xposed and kernels without the need to S-Off or Super CID and the only benefit to S-Off and S-CID is the ability to flash new firmware and radios, this begs the question, for the not so hard core rooting user, do I even need to?
Agreed the posts say to S-Off straight away so I will heed this advice but in honesty, am I required to?
Am I likely to encounter any problems by flashing 4.3 ROMs without upgrading to the latest firmware?
S-OFF gives you a 'get out of jail' option should you ever need it as you can flash an RUU to return the phone to stock. What software build are you running on at present?
It's always best to match firmware to the ROM
EddyOS said:
S-OFF gives you a 'get out of jail' option should you ever need it as you can flash an RUU to return the phone to stock. What software build are you running on at present?
It's always best to match firmware to the ROM
Click to expand...
Click to collapse
Sorry, excuse my ignorance.
When you say "software build" do you mean firmware version or android build? Or something else completely!?
ssjghost said:
Perfect! Thats the answer I was "rooting" for.......
Although, your detailed answer has prompted another question.
Given that I can flash ROMS, Xposed and kernels without the need to S-Off or Super CID and the only benefit to S-Off and S-CID is the ability to flash new firmware and radios, this begs the question, for the not so hard core rooting user, do I even need to?
Agreed the posts say to S-Off straight away so I will heed this advice but in honesty, am I required to?
Am I likely to encounter any problems by flashing 4.3 ROMs without upgrading to the latest firmware?
Click to expand...
Click to collapse
SuperCID is not needed anyway (I believe) for flashing unsigned firmware, S-Off should suffice. On the other hand, finding signed firmware, is quite difficult, I haven't seen but a few around (and pretty old). You could still receive them using OTAs, but that would force you to flash stock ROM, stock recovery, and maybe even relock the bootloader, then having to go through the bootloader unlocking procedure again (which also wipes your phone completely, including sdcard/internal storage)
That bring one thing to mind, the first thing you should do once you install a custom recovery, is do a complete nandroid backup of your phone, should you need to get back to it at some later point in time (including for example, receiving OTAs)
As for "needing" to upgrade firmware, there are people still running 1.xx firmware (from Android 4.1.2) with 4.3 ROMs. Everything from 4.1.2 to 4.2.2 was pretty much OK with any firmware.
However, I've recently read a few posts on ARHD, where some issues (on ARHD 30.0) were actually only resolved with an update to the latest firmware. I cannot confirm these were actually issues due to different firmware and base versions, but it may very well be case.
If you are able to achieve s-off (I personally did it with revone, as it doesn't use a custom hboot, just get's rid of the security ON), I highly recommend it. Even if you never need it, having it is better as it will allow you to downgrade/upgrade, etc.etc.
One last thing, when you use HTCdev to unlock your bootloader and flash custom stuff, the bootloader will show "UNLOCKED" and "TAMPERED", even if you lock it again, it will only show as "RELOCKED", whereas with revone, you can remove the "TAMPERED" sign, and even return it to "LOCKED".
PS: Since you're in the UK, at worst, you can use the FunFoneShop (or whatever they're called), because they have JavaCards which can achieve S-Off even for 1.54 hboot (I think they charge something like 20 or 30 pounds, if I'm not mistaken)
Also, some people are saying that s-off for 1.54 "is around the corner" (by beaups), but can't confirm that either.
---------- Post added at 06:24 PM ---------- Previous post was at 06:20 PM ----------
ssjghost said:
Sorry, excuse my ignorance.
When you say "software build" do you mean firmware version or android build? Or something else completely!?
Click to expand...
Click to collapse
Software build is the HTC version, ie ARHD 30.0 is "latest official HTC One 3.57.401.500 - Android 4.3", and firmware would be the firmware in that release. You can use different firmware version with different base version, but it's always best (if you can) to have both the same.
ssjghost said:
Sorry, excuse my ignorance.
When you say "software build" do you mean firmware version or android build? Or something else completely!?
Click to expand...
Click to collapse
As in the build shown in Settings>About phone>Software information, e.g. 2.24.401.8
nkk71 said:
SuperCID is not needed anyway (I believe) for flashing unsigned firmware, S-Off should suffice. On the other hand, finding signed firmware, is quite difficult, I haven't seen but a few around (and pretty old). You could still receive them using OTAs, but that would force you to flash stock ROM, stock recovery, and maybe even relock the bootloader, then having to go through the bootloader unlocking procedure again (which also wipes your phone completely, including sdcard/internal storage)
That bring one thing to mind, the first thing you should do once you install a custom recovery, is do a complete nandroid backup of your phone, should you need to get back to it at some later point in time (including for example, receiving OTAs)
As for "needing" to upgrade firmware, there are people still running 1.xx firmware (from Android 4.1.2) with 4.3 ROMs. Everything from 4.1.2 to 4.2.2 was pretty much OK with any firmware.
However, I've recently read a few posts on ARHD, where some issues (on ARHD 30.0) were actually only resolved with an update to the latest firmware. I cannot confirm these were actually issues due to different firmware and base versions, but it may very well be case.
If you are able to achieve s-off (I personally did it with revone, as it doesn't use a custom hboot, just get's rid of the security ON), I highly recommend it. Even if you never need it, having it is better as it will allow you to downgrade/upgrade, etc.etc.
One last thing, when you use HTCdev to unlock your bootloader and flash custom stuff, the bootloader will show "UNLOCKED" and "TAMPERED", even if you lock it again, it will only show as "RELOCKED", whereas with revone, you can remove the "TAMPERED" sign, and even return it to "LOCKED".
PS: Since you're in the UK, at worst, you can use the FunFoneShop (or whatever they're called), because they have JavaCards which can achieve S-Off even for 1.54 hboot (I think they charge something like 20 or 30 pounds, if I'm not mistaken)
Also, some people are saying that s-off for 1.54 "is around the corner" (by beaups), but can't confirm that either.
---------- Post added at 06:24 PM ---------- Previous post was at 06:20 PM ----------
Software build is the HTC version, ie ARHD 30.0 is "latest official HTC One 3.57.401.500 - Android 4.3", and firmware would be the firmware in that release. You can use different firmware version with different base version, but it's always best (if you can) to have both the same.
Click to expand...
Click to collapse
OK, so asuming I will be flashing a 4.3 ROM or 4.2.2 at the latest, my software version will be 3.57.401.500?
Therefore find the appropriate firmware for this software build?
The build is linked to the ROM you flash. ARHD is currently based on the recent 3.57.401.500 leak which is Android 4.3 and you'd ideally need the FW to match it but you have to be S-OFF to flash the FW
Going back to my previous question, what build are you currently on? It's more to direct you for backups/recovery options more than anything as before you jump head long into the rooting world it's ALWAYS the best to know how to revert to stock if required
EddyOS said:
As in the build shown in Settings>About phone>Software information, e.g. 2.24.401.8
Click to expand...
Click to collapse
Just to confirm, I am yet to obtain the phone.
Once I have it I and I have flashed a 4.3 ROM, I asume I will need to find the compantable firmware and also flash this.
ssjghost said:
Just to confirm, I am yet to obtain the phone.
Once I have it I and I have flashed a 4.3 ROM, I asume I will need to find the compantable firmware and also flash this.
Click to expand...
Click to collapse
Recommended YES, needed not always necessary. (and you need s-off for that)
Firmware can be found in @vomer's guide here: http://forum.xda-developers.com/showthread.php?t=2365506 (in section 2)
EddyOS said:
The build is linked to the ROM you flash. ARHD is currently based on the recent 3.57.401.500 leak which is Android 4.3 and you'd ideally need the FW to match it but you have to be S-OFF to flash the FW
Going back to my previous question, what build are you currently on? It's more to direct you for backups/recovery options more than anything as before you jump head long into the rooting world it's ALWAYS the best to know how to revert to stock if required
Click to expand...
Click to collapse
Gotcha,
So, what's needed is:
Root device
Install Custom Recovery
S-Off and S-CID
Flash Custom Rom
Find and Flash matching FW to ROM
Flash GApps
Flash Xposed Framework
Excluding the obligatory back-ups along the way....Happy days?
ssjghost said:
Gotcha,
So, what's needed is:
Root device
Install Custom Recovery
S-Off and S-CID
Flash Custom Rom
Find and Flash matching FW to ROM
Flash GApps
Flash Xposed Framework
Excluding the obligatory back-ups along the way....Happy days?
Click to expand...
Click to collapse
No. First thing is:
1. Find build version
2. Find RUU for backup purposes and download if available for your build
3. S-OFF (if possible) and unlock bootloader at the same time
4. Flash custom recovery (through fastboot)
5. Backup current ROM
6. Flash new ROM
7. Flash GAPPs (only if using CyanogenMod/AOSP - they're included in Sense-based ROMs)
8. Flash FW (through fastboot, not recovery)
9. Do anything else you want
ssjghost said:
Gotcha,
So, what's needed is:
Root device
Install Custom Recovery
S-Off and S-CID
Flash Custom Rom
Find and Flash matching FW to ROM
Flash GApps
Flash Xposed Framework
Excluding the obligatory back-ups along the way....Happy days?
Click to expand...
Click to collapse
If you get it with hboot 1.44 (pre June 2013), you can first S-Off and unlock bootloader without using HTCdev.
EddyOS said:
No. First thing is:
1. Find build version
2. Find RUU for backup purposes and download if available for your build
3. S-OFF (if possible) and unlock bootloader at the same time
4. Flash custom recovery (through fastboot)
5. Backup current ROM
6. Flash new ROM
7. Flash GAPPs (only if using CyanogenMod/AOSP - they're included in Sense-based ROMs)
8. Flash FW (through fastboot, not recovery)
9. Do anything else you want
Click to expand...
Click to collapse
Thanks, and thanks eveyone else. You can probably see from the number of posts Ive made I try and find out stuff before posting so its appreciated not getting flammed when I do!
Thanks for all your help with this and no doubt youll hear from me again when I follow the step by step guides "to the letter" and end up on boot-loop!
Didn't think it would take long before I posted again.
Spent the evening trawling the forum and the CM page but cant seem to find a CM ROM for the international M7? Even a link to the CM site from another site returned a page on CM website but no files? Am I mistaken? Example: http://www.get.cm/?device=m7&type=
So...after yet more searching Im guessing the Pac-Man ROM here http://forum.xda-developers.com/showthread.php?t=2348415 and kernel here http://forum.xda-developers.com/showthread.php?t=2301543 are compatible although it doesn't look like the kernel allows for middle HTC button to become menu. Does anyone know where I can find the firmware?
IGNORE HERE: PRE EDIT - If not, then can anyone advise a lightweight,non-sense ROM (offering 4.2.2 or 4.3), a compatible overclocking and HTC menu button converting kernel and the applicable firmware?
OK, so about 9 months ago I rooted my Three branded HTC one, installed CWM recovery and put ARHD12 on there and it's been brilliant. Three are now rolling out the 4G radio updates which as far as I understand is entirely separate to any ROM such as ARHD. So how do I get the radio update? Do I have to go back to stock? If so, now's the time to confess I didn't take a backup before I installed ARHD. So I guess I need the most recent Three RUU - do I have to remove CWM before I install it? I'm not a n00b - I managed to do this on my own last time and I'm fairly technically competent. The only problem I have now is one of time - I can't spend an entire day figuring stuff out due to the 9-month old bundle of joy that requires a fair bit of attention! If you can help me with a fairly simple outline of what to do in what order, that would be very much appreciated. Cheers!
ShadowTD said:
OK, so about 9 months ago I rooted my Three branded HTC one, installed CWM recovery and put ARHD12 on there and it's been brilliant. Three are now rolling out the 4G radio updates which as far as I understand is entirely separate to any ROM such as ARHD. So how do I get the radio update? Do I have to go back to stock? If so, now's the time to confess I didn't take a backup before I installed ARHD. So I guess I need the most recent Three RUU - do I have to remove CWM before I install it? I'm not a n00b - I managed to do this on my own last time and I'm fairly technically competent. The only problem I have now is one of time - I can't spend an entire day figuring stuff out due to the 9-month old bundle of joy that requires a fair bit of attention! If you can help me with a fairly simple outline of what to do in what order, that would be very much appreciated. Cheers!
Click to expand...
Click to collapse
You will have to return completely to stock. That means everything must be as it was out of the box. As for the ruu for your carrier, if they released it then it should be in one of the stickies.
Bat cave One
I'm on Three in the UK and before I flashed a custom ROM I made sure I got S-Off then flashed the latest unbranded firmware(FUU_4.19.401.9-TWRP2633_combined_nowipe.exe which I got from XDA) and then changed my CID to SuperCID. After that I flashed custom ROM without flashing a stock ROM. LTE/4G works perfectly ok.
heat57 said:
I'm on Three in the UK and before I flashed a custom ROM I made sure I got S-Off then flashed the latest unbranded firmware(FUU_4.19.401.9-TWRP2633_combined_nowipe.exe which I got from XDA) and then changed my CID to SuperCID. After that I flashed custom ROM without flashing a stock ROM. LTE/4G works perfectly ok.
Click to expand...
Click to collapse
Thanks Heat57. I'm currently S-On, Unlocked, Tampered. I've also found this thread:
http://forum.xda-developers.com/showthread.php?t=2419699
which seems to contain all of the radio files in the world, and also all of the firmware. This radio:
(1.29.401.12 WWE OTA) Radio_4A.14.3250.13_10.33.1150.01L
Looks interested, but you say you never flashed your radio? When did you get your one?
I'm thinking from your post I'm going to get S-OFF (using Revone, yes?) and flash a firmware to see if the 4G radio options show up. I can't see the one you mentioned - could you recommend one from the above thread? Also, it says TWRP - I'm using CWM - is that a problem?
Final question - if I do a backup I'm backing up the radio and firmware as well? So if I make a total plums of this I can get back to CWM and restore?
TIA for any further help you can give me
ShadowTD said:
Thanks Heat57. I'm currently S-On, Unlocked, Tampered. I've also found this thread:
http://forum.xda-developers.com/showthread.php?t=2419699
which seems to contain all of the radio files in the world, and also all of the firmware. This radio:
(1.29.401.12 WWE OTA) Radio_4A.14.3250.13_10.33.1150.01L
Looks interested, but you say you never flashed your radio? When did you get your one?
I'm thinking from your post I'm going to get S-OFF (using Revone, yes?) and flash a firmware to see if the 4G radio options show up. I can't see the one you mentioned - could you recommend one from the above thread? Also, it says TWRP - I'm using CWM - is that a problem?
Final question - if I do a backup I'm backing up the radio and firmware as well? So if I make a total plums of this I can get back to CWM and restore?
TIA for any further help you can give me
Click to expand...
Click to collapse
Well, I flashed the firmware, which amongst other hardware bits includes the radio. My first goal was to unlock the bootloader and then S-Off, as the latter removes any potential issues with firmware flashes and the like. I also went and changed CID to 11111111, which I understand is SuperCID and enables flashing of firmware and ROMs of different CID designations. Please beware, YOU MUST BE S-OFF FOR FIRMWARE FLASHING!!!
Regarding your question of revone, if you're on hboot 1.44 then yes, revone, hboot version 1.54 and 1.55 only work with rumrunner and latest versions require the 'firewater' exploit.
I am relatively new to HTC, although I owned an original Desire many years ago, so I still remember the peculiarities of HTC ROM. I had a Galaxy Note 2 and rooting and flashing ROMs there is a piece of cake by comparison. I digress.
Unlike most other manufacturers, where you get everything included in the custom ROM, it seems with HTC that is not the case, hence if you want to update your radio for example, you need to flash a firmware package. Therefore, I am not certain if a Nandroid would restore the firmware, if you encounter any problems, maybe someone more knowledgeable can confirm. In any event, if you're S-Off then flashing any firmware for the M7ul should work, so worst case, if you mess up you could always flash the one I pointed out via adb. Here is a link to the latest firmware http://forum.xda-developers.com/showthread.php?t=2485651
Regarding the recovery, I just prefer TWRP and use the one but last version 2.6.3.4, which works perfectly. #However, there is no reason why your CWM should not be adequate. Before I took the jump, after just receiving my One, I read through the threads for about a day to make sure I got it right.
Finally, if you end up rooted and S-Off then there is a supper little flashable zip called 'Guru_Bootloade_Reset_1.0.zip' that allows you to remove the tampered flag, relock the bootloader and unlock it again by simply flashing it and selecting what you want in it's aroma installer. You'll find it on XDA as well, justuse the search function.