Related
Specifically the HTC Titan (Eternity) and the HTC Radar 4G (Omega).
What are the options for developing custom ROMs for these devices?
Bootloader mode and USB Host mode can be accessed in much the usual way.
1) RUU Rom Update Utility. This certainly works fine for standard updates from the same vendor as the original device but not for unbranding a device to eg a standard Europe ROM.
2) Hard SPL/ RSPL - has anyone tried this? I would expect that the SPL is locked in much the same was as HTC have locked the first gen WP7 phones with 4.x & 5.x SPLs.
3) Goldcard. I have tried this on the Radar 4G with a HD7 y-cable, but it does not work. It does start to read the file in the format OMEGIMG.NBH but then reverts to a non-functioning USB Bootloader mode. Someone said on the Titan forum that this is because of the use of NAND memory but can anyone clarify this?
4) Ansar's method. From what I can work out he has been able to substitute parts of an NBH file from one official RUU to another, using some sort of D000f builder. Can anyone say if this technique would work on the 2nd gen devices? If so do I need an official RUU from my phone's original vendor?
5) Any other methods?
I am wanting to interop unlock my hd7 running latest mango. i tried the htc unlock xap and the connection setup app (which tells to use interop unlock as country) but to no avail. has anyone been able to get interop unlocked on htc hd7 ?
fearlessdolphin said:
I am wanting to interop unlock my hd7 running latest mango. i tried the htc unlock xap and the connection setup app (which tells to use interop unlock as country) but to no avail. has anyone been able to get interop unlocked on htc hd7 ?
Click to expand...
Click to collapse
Do you have it developer unlocked first?
HTC Have 2 OEM Update after Mango
if you updated your Phone with Second OEM Update, you can not Interop Unlock your phone
yes i have a dev account from app hub.
how do i find out if im running second oem? do you have the build number handy? the os version i have is 7.10.7720.68
It's not the OS build number, people. HTC controls the firmware number, not the OS number (that's Microsoft code). 7720.68 just means the RTM release of Mango. I swear, I write this so often...
If the third digit grouping of your firmware starts with 4 - that is, if your firmware version matches *.*.4XXXX.* - or lower, you can use the HTC Interop Unlock XAP. It *might* even be possible with *.*.50XXX.*, but I don't think so, and it certainly isn't possible with *.*.51XXX.* or newer.
well that helps a lot, ya my firmware shows 51004. so are there any workarounds as of yet?
The only work-around I know of is to downgrade. You can roll back a Zune restore point from before the firmware update(s) was installed, interop-unlock, and then reinstall the updates if you want (I've elected to semi-permanently keep my phone a few versions outdated on firmware). You could also flash a stock ROM that includes an older firmware. Be aware, however, that either option will lose some data - everything newer than the backup if you restore, everything on the phone if you flash a stock ROM.
GoodDayToDie said:
The only work-around I know of is to downgrade. You can roll back a Zune restore point from before the firmware update(s) was installed, interop-unlock, and then reinstall the updates if you want (I've elected to semi-permanently keep my phone a few versions outdated on firmware). You could also flash a stock ROM that includes an older firmware. Be aware, however, that either option will lose some data - everything newer than the backup if you restore, everything on the phone if you flash a stock ROM.
Click to expand...
Click to collapse
Hey thanks for the information, I was wondering if there were any guides you can point me to on how to flash from a stock ROM. I have an HTC HD7.
Thanks again for your help. i know sometimes its tiring explaining the same thing over and over, but it is much appreciated.
Go to the HD7 ("Schubert") portion of the XDA-Devs wiki (http://forum.xda-developers.com/wiki). I'm pretty sure you can find the download links for stock ROMs there. You could also try the HD7-specific forum section. You'll download a tool called a RUU (ROM Update Utility) that will have some image files (extensions like .NBH and .NB) along with it. You put the phone in bootloader mode (four bars of different color - you have to boot the phone while holding the Volume Down button). It should have yellow text, and at the bottom should say "Serial". Connect the phone to USB. Your PC will need to install a driver (normally this will happen automatically, if not, use Device Manager to tell the computer to search Windows Update for the driver). Once the driver is installed, the "Serial" will be replaced by "USB". You can now run the RUU program.
I *strongly* recommend creating a backup first! The RUU will wipe all data on the phone, and if the flash fails for whatever reason, you'll be unable to boot the phone again.
Ok Thanks, That was helpful. i read a few guides and I think Im ready to try. i just wanted to ask a quick question before diving in. Hope you dont mind. Some threads make refrences to certain Bootloaders being unable to go through the downgrade process (by flashing a Stock Rom). Is this correct? My bootloader version is:
5.10.2250.0(132968)
If it doesnt matter than are there any other things that would prevent me from doing this process?
And one more question and I promise to leave you alone lol. I plan on backing up my phone before beginning, but if the flash fails for whatever reason and the phone is unable to boot again as you warned, will I still be able to connect it to Zune and restore my backup? Thanks again. Hopefullyone day I can give more to the community once I get used to it.
Booting the phone while holding the Camera button will put it in backup/restore mode. If you connect the phone to the PC while it is in this mode, and the Zune software is running, it should automaticlaly try to restore.
Your bootloader (SPL) version is too high to install HSPL (needed for custom ROMs), and it's high enough that it won't automatically downgrade just by installing a stock ROM. However, you should be able to install the other parts of a stock ROM (in particular, the firmware) just fine.
If needed, there are a couple ways to downgrade the SPL; search the dev&hacking sub-forum for info. I would generally recommend GoldCard, but that will require a little bit of equipment. Apparently, "SLSPL" flashing will allow you to downgrade the SPL safely as well, though I haven't tried it. These are mostly for preparing to install a custom ROM, though - stock ROMs should be installable on any SPL version.
it not work with my trophy verizon
GoodDayToDie said:
Booting the phone while holding the Camera button will put it in backup/restore mode. If you connect the phone to the PC while it is in this mode, and the Zune software is running, it should automaticlaly try to restore.
Your bootloader (SPL) version is too high to install HSPL (needed for custom ROMs), and it's high enough that it won't automatically downgrade just by installing a stock ROM. However, you should be able to install the other parts of a stock ROM (in particular, the firmware) just fine.
If needed, there are a couple ways to downgrade the SPL; search the dev&hacking sub-forum for info. I would generally recommend GoldCard, but that will require a little bit of equipment. Apparently, "SLSPL" flashing will allow you to downgrade the SPL safely as well, though I haven't tried it. These are mostly for preparing to install a custom ROM, though - stock ROMs should be installable on any SPL version.
Click to expand...
Click to collapse
Hey thanks again! Im going to try it out today, cross fingers, Ill let you know how it all went. I appreciate the help.
Well?? Did it work? Would really like to know before I attempt the same
Thanks
did it work ????
Hi,
I'm attempting to Interop Unlock my HTC HD7.
I've just run a restore in Zune, but it appears that the earliest restore gives me:
OS version: 7.10.7720.68
Firmware revision number: 2250.21.51002.728
Hardware revision number: 0002
Radio software version: 5.71.09.02a_22.51.50.21U
Radio hardware version: A.102.0.D4
Bootloader version: 5.10.2250.0(132968)
Chip SOC version: 2.2.5.0
I understand that if I have a Firmware revision number of 5xxxx, I cannot run the Interop Unlock as seen in this thread.
From what I see, it is possible for me to download a Stock ROM, in my case, this, and run that to downgrade my Firmware revision number.
I would just like to clarify before I start this process. Is the above information correct, and to run the Stock ROM, do I simply enter Bootloader Mode, start the .exe as downloaded from the thread, and let it run (seems too simple to me)?
Also, should I manage to get Interop Unlock working on a Firmware revision number of 4xxxx, would the Interop Unlock stick once I update the phone (is normal Zune update even possible after that)?
Thanks.
Be very careful. Since you have bootloader 5.xx
Pretty sure downgrading like that will brick your device. You have to use a y-cable. Last I heard, ive had my hd7 unlocked for a while not sure of newer ways.
Look for the downgrading spl thread in hd7 development. I think that's where it is.
After downgrade spl. I would just install hard-spl and flash a custom rom. Easier.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
Thanks for the reply. Didn't know about the Bootloader thing, fortunately I didn't go ahead with it yet.
I was under the impression that if the ROM is the official ROM for my region (SEA, Singapore, 728), I wouldn't require any modifications to the SPL.
I don't want to mess with the SPL or the bootloader though, I've bricked enough devices (not WP7) to have a phobia of such things. Guess I'll have to wait for a breakthrough in unlocking, unless someone has any other methods.
If you want to be absolutely safe, GoldCard (which what @reeg420 meant when mentioning Y-cable) is the most reliable method.
However, I *think* you can actually downgrade to an older stock ROM just fine even with SPL 5.x. It just won't downgrade the SPL itself the way it normally would. You can't use RSPL on SPL 4.x or higher, which is why being able to downgrade the SPL is sometimes important (people who want to use custom ROMs need RSPL).
I suggest you do a bit more searching before deciding. I have not tried messing with SPL 5.x at all; I briefly had 4.x on my phone and promptly downgraded it to 3.1 again.
Thanks. I decided to go ahead with it, but got an error: "ERROR 226 (Flash Write - FLASH write error happened. Please check your PDA Phone)", which rebooted my phone. Phone appears to be okay though, not bricked.
Looks like I'll probably need to use a GoldCard?
Edit: So it appears that the earliest ROM that allows me to HSPL is this, which has the Bootloader 1.54.2250.0(112696). Could someone check my following steps and verify that I'm correct?
1. Get Y-Cable, USB Gender Changer, MicroSD+Card Reader
2. Get GoldCard Tool
3. Get GoldCard IMG, from this thread? "My custom goldcard.img"
4. Format MicroSD to FAT32
5. Place RUU_signed.nbh extracted from the aforementioned ROM with Bootloader 1.54.2250.0(112696), renamed to SCHUIMG.nbh
6. Run GoldCard Tool, ignore CID box, use GoldCard IMG, Patch MMC
7. Connect GoldCard, Y-Cable, phone, etc, etc, etc, patch phone
8. Get DFT's WP7FG3 from this thread
9. Install HSPL (or should I get RSPL? What is the difference?)
10. Find ROM of my choice (what do you recommend?)
11. Run selected ROM's ROMUpdateUtility.exe, flash device to new Custom ROM
Q1: What happens if the GoldCard process fails?
Q2: Is there any cons as to having an outdated Bootloader?
Q3: Am I able to upgrade my device with Official ROMs in the future after performing this, or must I simply use Custom ROMs from here?
Q4: Will having a Custom ROM affect my connectivity with my network?
ReignOfComputer said:
Thanks. I decided to go ahead with it, but got an error: "ERROR 226 (Flash Write - FLASH write error happened. Please check your PDA Phone)", which rebooted my phone. Phone appears to be okay though, not bricked.
Looks like I'll probably need to use a GoldCard?
Edit: So it appears that the earliest ROM that allows me to HSPL is this, which has the Bootloader 1.54.2250.0(112696). Could someone check my following steps and verify that I'm correct?
1. Get Y-Cable, USB Gender Changer, MicroSD+Card Reader
2. Get GoldCard Tool
3. Get GoldCard IMG, from this thread? "My custom goldcard.img"
4. Format MicroSD to FAT32
5. Place RUU_signed.nbh extracted from the aforementioned ROM with Bootloader 1.54.2250.0(112696), renamed to SCHUIMG.nbh
6. Run GoldCard Tool, ignore CID box, use GoldCard IMG, Patch MMC
7. Connect GoldCard, Y-Cable, phone, etc, etc, etc, patch phone
8. Get DFT's WP7FG3 from this thread
9. Install HSPL (or should I get RSPL? What is the difference?)
10. Find ROM of my choice (what do you recommend?)
11. Run selected ROM's ROMUpdateUtility.exe, flash device to new Custom ROM
Q1: What happens if the GoldCard process fails?
Q2: Is there any cons as to having an outdated Bootloader?
Q3: Am I able to upgrade my device with Official ROMs in the future after performing this, or must I simply use Custom ROMs from here?
Q4: Will having a Custom ROM affect my connectivity with my network?
Click to expand...
Click to collapse
Answer for Q1: it will definitely brick your device
Answer for Q2: no cons that may disturb you
Answer for Q3: yes, you're able to upgrade your device with official roms
Answer for Q4: no, as i use custom rom on my device, no connectivity problems
Wow, the GoldCard step looks incredibly daunting then. Guess I'll give this a shot. Will have to wait for the stuff to arrive from Amazon though, which will probably be a while given my location.
Thanks everyone for your input
Anyone tried this yet? I know the boot loader is locked. But since rogers from is official as well. That should work right? Any one has directions on how to do it?
Just run the exe? Any Mac versions?
Please don't post in the development section with this kind of stuff. Thread moved.
In answer to your question, no it won't work. Model numbers between at&t and rogers differ slightly and the ruu looks for model id to verify that it is right to flash. This is by design and is good so that some moron can't flash a vivid RUU on a HOX or flash int'l ruu on an at&t
Sent from my HTC One X using Tapatalk 2
Thanks. I am a noob when it comes to htc. For xperia s. We can load other similar roms with no root or bootloadet unlock. So the only way to load rogers onto att is to wait for bootloader unlock then? Can anyone verify this?
hexproject said:
Thanks. I am a noob when it comes to htc. For xperia s. We can load other similar roms with no root or bootloadet unlock. So the only way to load rogers onto att is to wait for bootloader unlock then? Can anyone verify this?
Click to expand...
Click to collapse
Nothing to verify. This has been HTC's model for quite some time.
Sent from my HTC One X using Tapatalk 2
So only way is bootloader unlocked and then flash with official rogers rom if you are on att? So thats why everyone is all pissed about att version not having bootloader unlocked. Thanks for your info.
hexproject said:
So only way is bootloader unlocked and then flash with official rogers rom if you are on att? So thats why everyone is all pissed about att version not having bootloader unlocked. Thanks for your info.
Click to expand...
Click to collapse
Unlock bootloader
Flash cwm recovery (don't have one yet)
Flash rom
Profit
Sent from my HTC One X using Tapatalk 2
Are the bootloaders between Rogers and AT&T different? I know that when you try to unlock the bootloader, it gives you a string of numbers that you enter prior to unlocking the bootloader. If the bootloaders are the same, then theoretically us AT&T users ought to be able to use a string of numbers from a Rogers phone just to make the tool happy. Right?
mikelebz said:
Are the bootloaders between Rogers and AT&T different? I know that when you try to unlock the bootloader, it gives you a string of numbers that you enter prior to unlocking the bootloader. If the bootloaders are the same, then theoretically us AT&T users ought to be able to use a string of numbers from a Rogers phone just to make the tool happy. Right?
Click to expand...
Click to collapse
Nope. Its a hash of some sort. Its different everytime you run the command.
Sent from my HTC One X using Tapatalk 2
Pirateghost said:
Unlock bootloader
Flash cwm recovery (don't have one yet)
Flash rom
Profit
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I dont want custon rom just yet, Just rogers official rom to work on att . Do i still need cwm? No one has tried putting the rogers zip file in the root and update that way?.. You can download all the official rom from the development section. Iatt is in exe and rogers is in zip file...
hexproject said:
I dont want custon rom just yet, Just rogers official rom to work on att . Do i still need cwm? No one has tried putting the rogers zip file in the root and update that way?.. You can download all the official rom from the development section. Iatt is in exe and rogers is in zip file...
Click to expand...
Click to collapse
you're spinnin your wheels here mate.
i KNOW how it works with RUUs and the zip files they produce....i have been around for at least a few months with a few HTC devices.....
JUST having root DOES NOT mean that you can miraculously flash any file you want
unlocking the bootloader would allow you to modify the rom zip that is produced by the RUU and fastboot flash it, but you will not be able to flash the radio that comes with it, essentially all you could flash is /system and /boot
you dont think that every possibility was attempted while working on the Vivid? this aint my first rodeo.....
Pirateghost said:
you're spinnin your wheels here mate.
i KNOW how it works with RUUs and the zip files they produce....i have been around for at least a few months with a few HTC devices.....
JUST having root DOES NOT mean that you can miraculously flash any file you want
unlocking the bootloader would allow you to modify the rom zip that is produced by the RUU and fastboot flash it, but you will not be able to flash the radio that comes with it, essentially all you could flash is /system and /boot
you dont think that every possibility was attempted while working on the Vivid? this aint my first rodeo.....
Click to expand...
Click to collapse
These RUU files are funny. Way back in WM days, with the HP 6315 (htc built) I was the guy that hex edited the RUU executable to bypass the model check. I had/have VERY little programming experience but it only took me a few hours to figure it out. I wonder if this method is still feasible..........
beaups said:
These RUU files are funny. Way back in WM days, with the HP 6315 (htc built) I was the guy that hex edited the RUU executable to bypass the model check. I had/have VERY little programming experience but it only took me a few hours to figure it out. I wonder if this method is still feasible..........
Click to expand...
Click to collapse
have a crack at it, but the zip file actually contains the signature and the model check, not the exe.
if you can modify the zip file without changing the signature, then by all means, please do....
or someone could just unlock the bootloader and it wouldnt matter if the zip is signed or not, just need to edit the checks and remove the hboot, recovery, radio, adsp, etc from the zip
That would be cool. I came from sony and samsung and this is my first time with HTC. So thanks for all these info. A great help with people who just want to use stock roms from other carrier.
hexproject said:
That would be cool. I came from sony and samsung and this is my first time with HTC. So thanks for all these info. A great help with people who just want to use stock roms from other carrier.
Click to expand...
Click to collapse
after unlocking bootloader, and getting a recovery installed, you can run stock rom from any other carrier, just from a CWM version
I like having several stock rooted roms in CWM format, so I tend to knock em out as soon as I can....and get them into your hands
Pirateghost said:
have a crack at it, but the zip file actually contains the signature and the model check, not the exe.
if you can modify the zip file without changing the signature, then by all means, please do....
or someone could just unlock the bootloader and it wouldnt matter if the zip is signed or not, just need to edit the checks and remove the hboot, recovery, radio, adsp, etc from the zip
Click to expand...
Click to collapse
My skills are rusty. But back when I was dealing with the WM RUU I bypassed both the model check and also the CRC check right in the executable. Granted these security measures have come a LONG way since then, but sometimes people overlook the obvious, you know?
If the phone gets S-OFF you can set SuperCID and flash away.
I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.
tykidd66 said:
I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.
Click to expand...
Click to collapse
Post is a bit confusing. You talk about Bell, Rogers, and Telus all at once. Also, if you got an OTA update from Bell, you will only be able to execute an RUU that has an hboot version equal to or higher than your current one.
If you are looking for a more recent RUU than the ones posted on http://forum.xda-developers.com/showthread.php?t=1543588
then I suggest you send a private message to Football, the user who started that post. He helped me find newer Bell Mobility RUUs (which have since been posted to the thread).
Your other option is to do a bootloader downgrade (see the dev post on this, its a bit complicated), and then you can flash other radios from http://forum.xda-developers.com/showthread.php?t=1998270
If you dont want to downgrade your bootloader, you can always flash to a CM10 base (AOSP type) ROM, such as PAC Man, or Jelly Bam, etc. Then you can flash radios without having to downgrade.
Again, though this is all assuming that your true problem is with you baseband radio and now switching carriers has made your reception poor...
Also remember you will have to relock your bootloader before you execute an RUU, otherwise it wont take (that and a correct bootloader version)
AKToronto
Thanks for the info. The phone is a sim-unlocked Fido unit. It was running on Bell before the OTA update.
Here are the specs:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Is the "build number" the RUU? I'll try Football, but do I need the Rogers (Fido) RUU?
Thanks.
you can not execute an rogers ruu on a bell phone, the cid wont match
there is an app on play who will display you the cid and the original network; like that you'll know exactly what phone do you have in hand
you just have to unlockit after and you will be able to useit in whatever network you want
Thanks. Ran CID getter and says it's ROGER001. So I've confirmed that I need a Rogers file. And I would like to unlock it, but from what I've read I cannot restore back to Rogers 1.70 because the unit has been updated to 1.84. I have read that if I can find a 1.84 Rogers file, I can use that to restore the unit. This is the next thing I need to confirm. I appreciate your help.
I think that is almost correct. You can change the CID to the Rogers one using the same technique as posted in the super Cid thread in the development section. Normally though you can't flash an older ruu as the hboot version can't be older. But You may also want to try posting a message in the bootloader downgrade thread that is stickied to n the development section. I think if you downgrade your bootloader and also do a minor hex edit to a partition you can flash an older RUU. I have downgraded my bootloader but haven't tried flashing an older ruu so I can't say for sure.
Sent from my HTC One S using xda premium
Thanks again. So I can assume the CID is already Rogers, yes? I don't want to change it. My hope is that I can use the All in One Toolkit (one of the sticky posts) to bring the phone back to stock and then SIM unlock it for use with Telus. If I run the Toolkit, and use cbetso's instructions from the "How to Return to Stock" post (after adding the stock recovery to the folder). If I locate the Rogers 1.84 RUU, can I run it without downgrading?
don't assume, your cid is rogers ROGER001, so there is absolutely no way your phone could download and execute an update from bell.
so I can not understand what has bell to do in this.
if you just want to use it on telus network, you just have to unlock it, you don't even need root for this. and the phone will work just fine.
the root is needed when you want to change ROM, radio, debloat and others.
one of the others will be tweaking the build.prop file to achieve maximum capacities of your 3g/4g desired network
Thanks - it's a difficult story to tell, really. It was a Rogers unit, SIM unlocked to work with Bell. It was on Bell's network for two months, and an OTA update caused major radio and reception problems. It will not keep a network signal anymore. I have tried other SIMs in the unit and it will not recognize them, nor start up with the "Enter Unlock Code" screen to SIM unlock it. It's my understanding that I need to return it to stock by finding the Rogers RUU file that matches the software version on the unit, which is 1.84. This is my very limited understanding of the issue, but it's what I've been able to figure out.
if it was a rogers device, and you did not change the CID, you get the ROGER001 cid with the app, your phone is still a rogers device
doesn't matter in which networks was used, for the two months before you get it, and by you after
as long the cid stays ROGER001, your phone will remain a rogers device, unlocked to be used in different networks.
so there is absolutely no way an OTA update, from bell or telus could be the source of your problems, because your phone will not download or execute an ota update from other networks
same for rogers ota update, as long the phone was unlocked, will not execute OTA updates, even the updates will be downloaded on the phone
your connection problem came from other reasons;
however it you want to return the phone to rogers stock, the key number is HBOOT version;
you can execute any RUU with HBOOT version higher or equal with your present version on the phone
if somehow you're on a very high version and you can not find the appropriate RUU, we can always downgrade RUU, check development section for tutorial
it's not very simple, but as long you're ok and you understand the steps, go for it, it is doable.
if you have root, you might try different radios before all above, or maybe a custom rom; just an ideea; as long the phone is not soft bricked or physically damaged, there is no reason a custom rom will not work
Thanks for the information. There seems to be other problems with the unit, including it won't delete all data after hard reset, it won't recognize other networks when other SIMs are put in, it has been upgraded past the 1.70 stock Rogers RUU. I wish I could get it figured out or I may have to sell it as is. Appreciate your help.
factory reset in fastboot didn't work?
means you're on some custom rom with non stock recovery?
have you tried to flash a stock recovery? any of them, whatever you'll find around here; there are no much difference in term of facilities between them;
then you should be able to restore phone to factory defaults
try find somewhere All in one kitt one S v1.0; there is stock recovery in it, and flashing is easy
in v1.1 there is no more stock recovery
donwload ruu or open up ruu..when it first starts go into your windows manager and in the link section delete what you have in that section like c:/program files and replace it with %temp% and it will find two encrypted folders with a big letter/digit name and they will show you what time they were opened . open them up and find rom.zip copy it to your desktop and then extract it somewhere safe .. in the folders in rom.zip you will see recovery_signed.img rename it recovery.img and flash it via hasoons tool kit provided in the development section..just in case you ever run into this again
Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.
tykidd66 said:
Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.
Click to expand...
Click to collapse
Not sure about your radio issue, that would require testing out different radios. You can do that on a higher hboot by trying AOSP ROMS and using the Radio flasher in the dev forums.
As for flashing stock recovery you can also just use the following link: http://loadbalancing.modaco.com/down...ery_signed.img
The stock recovery doesnt really change from RUU to RUU. You dont need a particular recovery to use a particular RUU, as far as I know.
Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?
tykidd66 said:
Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?
Click to expand...
Click to collapse
http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Try that. Sorry about the other link
I maybe miss it, but you never said what is the exact status of the phone right now;
it is booting? it is working on some network? at least partially like voice only? what ROM are you on? what HBOOT?
Hi there - thanks for getting back to me and asking. The phone seems to be booting normally and always has been. It is not able to recognize any new SIM card. It's a Rogers unit, and when I add my Telus SIM it does not go to the "Unrecognized SIM" screen, it actually registers the TELUS network for a moment, then the radio gives no signal.
How can I check the ROM, 'cause I have no idea. Is the HBOOT in these specs?
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Thanks again.
for the Hboot version you have to reboot in fastboot
for recovery reboot into recovery
for the ROM version, once booted normaly you have to go into about phone > software
are you sure you have the right settings for Telus APN? for some reasons, the phone will not registered to network, if apn setting are wrong;
at least for me, which I'm opposite to you as I have a telus phone and using it in fido network, if I dont have Fido APN setted up, the phone does not register to network