Related
The seller said it is unlocked. How can I verify it?
I read CID Unlocking and Sim Unlocking. How can I confirm both.
Also, how can I tell which version of the radio?
and which version of SPL (3.5 or 1.2)?
Or is there any great tutorial I can setup for the AP4?
I am starting to get confused.
the seller probably was not lying as it is easy to do (thanks to olipro - cmonex/olinex) but if you want to check, press and hold your camera button, whilst doing that press the reset button, and tell us the details on the rainbow screen.
this will also tell you if it is SPL 1.1-1.2 or 3.5
when your done just press reset again
LOCKing is related to SPL. SPL is a part of the "bios" (just to use the PC paradign IPL and SPL are "extended bios" ), then you have the RADIO section of the rom and the OS (WMxx)
Other part of the rom are the EXTENDED ROM (where the file needed for operator customizzation during first install are stored) and splash screens (a FULL ROM means IPL,SPL, SPLASH 1, SPLASH 2, RADIO, OS, EXTENDED ROM).
This "bios" , called SPL can receive commands from RUU (Rom Update Utility, the sw used to flash the rom file). ROM info are "wrapped" in a .nbf file and the RUU, interacting with SPL with some batch commands, flash into the device memory the ROM parts (Splash are flashed in their locations, os, radio, ....) RUU opens the .nbf file, read abatch command file, and send the commands to the SPL to flash the rom sections
Now you can understand how a custom ROM is done: using a "kicken" you can prepare a .nbf file containing the data and the batch command file used by RUU to flash it in the right location of your ROM (SPL, RADIO, OS, SPLASH, or all together) SPL is a KEY part for this process.
With the stock RUU IPL and SPL some controls are done before flashing, first of all device's language and vendor ID, so called CID. If they doesn't mach with the ROM file you will have an error and RUU exits: wrong language, wrong vendor, ....
Flashing a custom SPL you avoid this check (or it sets the CID to "supercid", it means I accept every language and vendor ID)
The SIM unlock (phone working with all SIM card) needs something more complex. In the ATHENA FORUM whe have ATHENA UNLOCKER, from OLIPRO, for SIM Unlock and CID Unlock and ATHENA WRAPPER, just for CID unlock. They will update the HTC SPL to OLIPRO 1.2
Hi sergiopi,
Your post is so concise. You told us the whole theory it may take me more than a day to find. You have the potential to be a book author. Thanks anyway.
Questions:
1. How can I tell whether the sim is unlocked?
2. How can I tell whether the cid is unlocked? Or it is no harm to run the ATHENA UNLOCKER again?
3. What is the different btw SPL 3.5 and 1.2? Should I update it? I am planning to run the AP4.
Thanks again!
Did you completely miss my previous post, if you follow the simple instructions. I gave you earlier, we will be able to answer all your questions.
ice_coffee said:
Did you completely miss my previous post, if you follow the simple instructions. I gave you earlier, we will be able to answer all your questions.
Click to expand...
Click to collapse
To check if your Athena is SIM Unlocked take a SIM from your friend's phone who is in another network and put it in your Athena. If it refuses to accept the SIM then it is locked and you have to unlock it. If it accepts the SIM and lets you place a call, it is SIM unlocked and most probably CID Unlocked. To check if it is CID unlocked just do what ice_coffe says.
I didn't miss the post from ice_coffee. My Athena is still in shipping. I just want to get more info first. Besides testing with a real sim card, is there any method we can run from the machine?
alui said:
Hi sergiopi,
Your post is so concise. You told us the whole theory it may take me more than a day to find. You have the potential to be a book author. Thanks anyway.
Questions:
1. How can I tell whether the sim is unlocked?
2. How can I tell whether the cid is unlocked? Or it is no harm to run the ATHENA UNLOCKER again?
3. What is the different btw SPL 3.5 and 1.2? Should I update it? I am planning to run the AP4.
Thanks again!
Click to expand...
Click to collapse
Thanks, the post is for you and for other newbies, to help everyone to understand. This is a DEVELOPER'S forum, we like smart users!
alui said:
Hi sergiopi,
Your post is so concise. You told us the whole theory it may take me more than a day to find. You have the potential to be a book author. Thanks anyway.
Questions:
1. How can I tell whether the sim is unlocked?
2. How can I tell whether the cid is unlocked? Or it is no harm to run the ATHENA UNLOCKER again?
3. What is the different btw SPL 3.5 and 1.2? Should I update it? I am planning to run the AP4.
Thanks again!
Click to expand...
Click to collapse
Listen Alui. The question numbr 3 shows of your post shows that you are realy a noobie. So if you are still waiting for your new device, do not waste your time but start reading. If you already decided that you want to go for AP4, then did you realy read the AP4 thread from first post? I am almost sure, you didn't.
So please remember, if you do not know what you are doing then you have a big chance to convert your super device into a brick.
And once more, if you browse this forum, you can see how many threads is there, and how many post is in each thread. If you see this you should be sure that you are not the first person here who just got his new device. All your questions were answered many times here so just read and read and after a week of reading start to plan what to do next.
Sorry if this is a stupid question but I am in a hurry so have no time to search and investigate in this mater by myself for now!
I have flashed several roms in the past, right now I am running RomeOS 1.40
However I have now sold my device and need to revert to the original rom and SPL!
I have the Swedish rom, but the problem is that the file I have is RUU_Signed.nbh I dont have the wrapper or what it is called so that I can flash my raphael!
Also, do I need to SPL lock the device again? and if so how do I do that?
Last but not least, after flashing RomeOS, I got alot of information on the first screen (You know when you first start the device where it shows the radio version and everything!) But the problem is that I have tried to flash other roms but the information on the first screen is still there!
How do I get rid of it so it looks like the original?
Hope you know what I mean and how to help me!
Thanks in advance!
branko.savic said:
Sorry if this is a stupid question but I am in a hurry so have no time to search and investigate in this mater by myself for now!
I have flashed several roms in the past, right now I am running RomeOS 1.40
However I have now sold my device and need to revert to the original rom and SPL!
I have the Swedish rom, but the problem is that the file I have is RUU_Signed.nbh I dont have the wrapper or what it is called so that I can flash my raphael!
Also, do I need to SPL lock the device again? and if so how do I do that?
Last but not least, after flashing RomeOS, I got alot of information on the first screen (You know when you first start the device where it shows the radio version and everything!) But the problem is that I have tried to flash other roms but the information on the first screen is still there!
How do I get rid of it so it looks like the original?
Hope you know what I mean and how to help me!
Thanks in advance!
Click to expand...
Click to collapse
The wrapper is included in the attached file along with the htc splash screen. the original spl also in there so do the following:
1- extract the zip file and put the customruu + your RUU_Signed.nbh in one folder and run that to get your original rom
2- put now the customruu + htcsplash together and flash to change the splash screen
3- Now use the spl tool to revert to the original spl
karimartine said:
The wrapper is included in the attached file along with the htc splash screen. the original spl also in there so do the following:
1- extract the zip file and put the customruu + your RUU_Signed.nbh in one folder and run that to get your original rom
2- put now the customruu + htcsplash together and flash to change the splash screen
3- Now use the spl tool to revert to the original spl
Click to expand...
Click to collapse
Thank you, I did everything you told me and it worked like a charm!
I cant thanks you enough!
Dear all,
I am facing a problem here.
Had a hardware problem with the built in microphone and had to revert back to stock rom/splash screen/Original SPL in that order.
Had no problems reverting the ROM and the original screen back (just a couple of flashes), BUT when I tried to revert back the stock SPL here http://forum.xda-developers.com/attachment.php?attachmentid=110582&d=1220406410
I renamed the file to RAPHIMG.nbh, copied it to the root of the SD Card and entered bootloader mode and this is what it displays:
RAPH100
SPL-1.90.0000 (Which means a successful flash)
!!! AND THEN THIS !!!
"Upgrade ROM code error"
"Please try again"
This message is located in the last part of the green stripe in the tri color screen (bootloader)
It is then followed by the grey screen automatically which you are supposed to press volume key to start a flash process BUT it just HANGS at Loading...
unabling you to flash anything.
It's actually a friend's phone too so I guess you understand how hard it is....
Any help is appreciated
Thanks in advance
Possible image might be corrupt on sd card, grey screen is shown when it's trying to read sd, have you tried with sd removed? if you get to 2nd tricolor screen with sd removed i would use usb flash to restore it to working order..
Da_G said:
Possible image might be corrupt on sd card, grey screen is shown when it's trying to read sd, have you tried with sd removed? if you get to 2nd tricolor screen with sd removed i would use usb flash to restore it to working order..
Click to expand...
Click to collapse
Removed the SD and it stays at the tricolor screen with the spl version as mentioned in 1st post.
Also, displaying the Upgrade ROM code error, please try again message
The mode is currently serial
What can I do from here?
fireblade63 said:
Dear all,
I am facing a problem here.
Had a hardware problem with the built in microphone and had to revert back to stock rom/splash screen/Original SPL in that order.
Had no problems reverting the ROM and the original screen back (just a couple of flashes), BUT when I tried to revert back the stock SPL here http://forum.xda-developers.com/attachment.php?attachmentid=110582&d=1220406410
I renamed the file to RAPHIMG.nbh, copied it to the root of the SD Card and entered bootloader mode and this is what it displays:
RAPH100
SPL-1.90.0000 (Which means a successful flash)
!!! AND THEN THIS !!!
"Upgrade ROM code error"
"Please try again"
This message is located in the last part of the green stripe in the tri color screen (bootloader)
It is then followed by the grey screen automatically which you are supposed to press volume key to start a flash process BUT it just HANGS at Loading...
unabling you to flash anything.
It's actually a friend's phone too so I guess you understand how hard it is....
Any help is appreciated
Thanks in advance
Click to expand...
Click to collapse
You cannot flash an SPL from the bootloader. You need to use SSPL. The directions can be found in the HardSPL thread.
NotATreoFan said:
You cannot flash an SPL from the bootloader. You need to use SSPL. The directions can be found in the HardSPL thread.
Click to expand...
Click to collapse
Hey man, thx for stopping by..
If I understand correctly, SSPL runs through the device which is stuck at bootloader currently... or am I hopefully wrong??
If you're at the tricolor screen and it reads serial, that should be fine.. plug in usb and it should switch to usb.. then flash a stock carrier rom through usb.. that should get you up and running and you can then run sspl and flash your spl
Da_G said:
If you're at the tricolor screen and it reads serial, that should be fine.. plug in usb and it should switch to usb.. then flash a stock carrier rom through usb.. that should get you up and running and you can then run sspl and flash your spl
Click to expand...
Click to collapse
Keep in mind im currently on stock SPL, do u think flashing the stock ROM is ok?
That's exactly why i suggested stock ROM, stock SPL will only accept stock ROM's (it will overwrite the spl too so make sure the stock rom you are using is the right one)
dude....i hate to say this...butyou might be s.o.l. at this point. i did the same to my fuze not too long ago... tryingto flash anything to the phone just locks it up.i was lucky enough to bs my way through an att guy to get me a new one (was still under the 30 day warranty).
Da_G said:
That's exactly why i suggested stock ROM, stock SPL will only accept stock ROM's (it will overwrite the spl too so make sure the stock rom you are using is the right one)
Click to expand...
Click to collapse
That's wt Im trying now, tried to flash 2 ROMs already and stops at 2% saying Invalid Vendor ID
I gess I'm using wrong shipped roms till now
fireblade63 said:
That's wt Im trying now, tried to flash 2 ROMs already and stops at 2% saying Invalid Vendor ID
I gess I'm using wrong shipped roms till now
Click to expand...
Click to collapse
I had the same problem as you and could not flash any rom, Always get Invalid vendor ID.
You need the right Stock Rom to flash and in my case in the middleeast, the Stock Rom is so far only available in at HTC.
I had to take the phone to HTC Service Center and they flashed the correct Stock Rom and charged me as they did it out of warranty.
Regards
fireblade63 said:
That's wt Im trying now, tried to flash 2 ROMs already and stops at 2% saying Invalid Vendor ID
I gess I'm using wrong shipped roms till now
Click to expand...
Click to collapse
Sorry about my last post... I misread your issue.
If you flashed the stock 1.90 SPL from the HardSPL thread, then you will need to ask Olipro (or cmonex) which WWE ROM it originated from. That ROM is the ONLY one your phone will accept.
The steps in reverting SPL for warranty / return state to always do the ROM first so that you do not run into this problem. I had the same issue when I was testing a US 3G Diamond I bought from Best Buy (to become acclimated to TF3D prior to the Fuze's release). I restored the SPL first, and then couldn't get Dutty's ROM off the phone, because I could not locate a downloadable version of the WWE ROM that phone came with. [Luckily, Best Buy Mobile's employees in KOP, PA aren't too clever, and I was able to convince them that the phone came that way. ]
NotATreoFan said:
Sorry about my last post... I misread your issue.
If you flashed the stock 1.90 SPL from the HardSPL thread, then you will need to ask Olipro (or cmonex) which WWE ROM it originated from. That ROM is the ONLY one your phone will accept.
The steps in reverting SPL for warranty / return state to always do the ROM first so that you do not run into this problem. I had the same issue when I was testing a US 3G Diamond I bought from Best Buy (to become acclimated to TF3D prior to the Fuze's release). I restored the SPL first, and then couldn't get Dutty's ROM off the phone, because I could not locate a downloadable version of the WWE ROM that phone came with. [Luckily, Best Buy Mobile's employees in KOP, PA aren't too clever, and I was able to convince them that the phone came that way. ]
Click to expand...
Click to collapse
Hmm, then I need to know from which ROM the SPL originated and then flash it.
Thing is, some of the shipped roms available at wiki are just nbh files..
I tried flashing with the wrapper exe and the RaphaelCustomRUU.exe and still all roms I've downloaded don't seem to work.
It's a RAPH100 untied to a network.
fireblade63 said:
Hmm, then I need to know from which ROM the SPL originated and then flash it.
Thing is, some of the shipped roms available at wiki are just nbh files..
I tried flashing with the wrapper exe and the RaphaelCustomRUU.exe and still all roms I've downloaded don't seem to work.
It's a RAPH100 untied to a network.
Click to expand...
Click to collapse
Post in the HardSPL thread asking which ROM the SPL originated from. Once you know that, you can download the appropriate ROM from the Wiki.
NotATreoFan said:
Sorry about my last post... I misread your issue.
If you flashed the stock 1.90 SPL from the HardSPL thread, then you will need to ask Olipro (or cmonex) which WWE ROM it originated from. That ROM is the ONLY one your phone will accept.
The steps in reverting SPL for warranty / return state to always do the ROM first so that you do not run into this problem. I had the same issue when I was testing a US 3G Diamond I bought from Best Buy (to become acclimated to TF3D prior to the Fuze's release). I restored the SPL first, and then couldn't get Dutty's ROM off the phone, because I could not locate a downloadable version of the WWE ROM that phone came with. [Luckily, Best Buy Mobile's employees in KOP, PA aren't too clever, and I was able to convince them that the phone came that way. ]
Click to expand...
Click to collapse
SPL has nothing to do with the Invalid Vendor ID Error, It is the CID. In another word you can flash SPL 1.95 and still can not flash the AT Rom 1.95.502.5 because the CID is different.
Regards
ViperBJK's QMAT features GoldCard generator for current HTC devices that can force RUU to bypass CID check.
Do you know what is the CID of your device?
shafez said:
SPL has nothing to do with the Invalid Vendor ID Error, It is the CID. In another word you can flash SPL 1.95 and still can not flash the AT Rom 1.95.502.5 because the CID is different.
Regards
Click to expand...
Click to collapse
The CID is determind by the SPL.
Look up the error code posted... everything points to HardSPL. Back in my Wizard days, HardSPL did not exist, and we just did a CID unlocking. This is not the case with newer devices.
All ROMs are not created equal. Each WWE ROM checks for specific information within the SPL, and if it doesn't find what it's expecting, fail...
stepw said:
ViperBJK's QMAT features GoldCard generator for current HTC devices that can force RUU to bypass CID check.
Do you know what is the CID of your device?
Click to expand...
Click to collapse
I'm not sure
Where can I know that?
@NotATreoFan && Shafez,
I remember from TyTNII day when Shafez suggested extracting 3.29 and 28 SPLs from the newer shipped 6.1's for a better responsive device.
We could extract and build with htc rom tool if I remember the name of the tool correctly.
Do we have a tool as such compatible with TP? (agreeing with NotATreoFan here)
@Shafez,
Since you think it is not SPL and it is a CID issue, what can I do about it?
Sending it to SVC for repair out of warranty is an option but I'd like to leave it as my last.
Did they provide the ROM or they flashed it for you?
Were u able to make raw files out of it for future use or any1 else has it?
Thx guys and keep the help coming
fireblade63 said:
@NotATreoFan && Shafez,
I remember from TyTNII day when Shafez suggested extracting 3.29 and 28 SPLs from the newer shipped 6.1's for a better responsive device.
We could extract and build with htc rom tool if I remember the name of the tool correctly.
Do we have a tool as such compatible with TP? (agreeing with NotATreoFan here)
@Shafez,
Since you think it is not SPL and it is a CID issue, what can I do about it?
Sending it to SVC for repair out of warranty is an option but I'd like to leave it as my last.
Did they provide the ROM or they flashed it for you?
Were u able to make raw files out of it for future use or any1 else has it?
Thx guys and keep the help coming
Click to expand...
Click to collapse
Since you cannot get past the bootloader, your only option is to find the WWE ROM that matches the SPL you flashed. Even though the HTC ROM Tool "signs" the NBH file, it still won't fool the stock bootloader... if it did, we wouldn't need HardSPL.
This thread is to answer the popular question of:
"How can I get my Fuze back to stock and be able to return it for warranty service?"
I've been able to find very convoluted instructions and containing unnecessary manual effort for no reason. I returned phones to AT&T and HTC w/o any problems and I learned the shortest method of complying with the expectations involved. The thread will contain pictures of boot-screens pertaining to the process so that people can use them for reference. There will also be pictures of the progress and the different variations of devices out there.
This is for AT&T Fuze ONLY. The concept, however, can be used on any HTC Touch Pro (GSM and probably CDMA) as long as you get the correct Stock ROM from the Stock ROM Wiki.
You only need to do this if you have HardSPL already on your device.
To get to the canary screen / flashing screen (instruction for Fuze press and hold power and volume-down then press the small reset button on the right of the charging hole).
OliNex 1.90 HardSPL will refer to OliNex HardSPL for GSM Raphael devices.
OliNex 1.90 Stock Warranty SPL will refer to software also obtained from the same thread as above.
Screenshots below show RAPH110 and RAPH*** - there is no difference, so don't concentrate on that.
If your phone is Security Unlocked and you feel that you need to lock it back up (optional), please look at the procedures in post #2. However, I feel that AT&T and HTC will not care if it's security locked or unlocked, the screenshots below with the unlocked verbiage is actually a replacement that AT&T sent to me already Security and SIM unlocked.
Tri-color RUU bootloader refers to the colorful screen seen when the device is booted into flashing mode. This is accessed by holding down the Power Button with the Volume-Down Button and pressing the reset button. Reset button is located next to the charger hole. A screen showing the RUU boot screen like below will come up.
For the AT&T "World Phone" boot splash screen, see this post, but splash screen should come with an AT&T ROM applied in the step #5 below.
YOU WANT YOUR DEVICE TO END UP JUST LIKE ONE OF THESE SCREENSHOTS BELOW.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
YOU ONLY NEED THESE INSTRUCTIONS IF YOU HAVE THE HARDSPL
LIKE PICTURED BELOW, OTHERWISE YOU'RE WASTING YOUR TIME.
Some Explanation:
The concern is the fact that my Fuze came stock with 1.95 SPL, not 1.90 that OliNex provides, so to return my device with 1.90 SPL was a problem for me. I am including OliNex's 1.90 Warranty SPL which I hex-edited to show 1.95 instead. The reason why I did that is in case the person forgets or screws up on flashing the stock 1.95 ROM as noted in the last step of the instructions below.
OliNex's HardSPL does not allow any SPL to overwrite it. This is the reason why you need to flash the Warranty SPL, to overwrite that write-protected HardSPL. There is something special about that OliNex Warranty SPL because it's the only UNSIGNED SPL that seems to be able to overwrite the HardSPL. When I tried to apply any of my extracted SPL's (repository here) it would not work, like the author mentions in large and bold edit and had a Moderator close his thread. However, once you're at step #4, you can then flash only a full Stock Signed ROM (original HTC basically) from step #5 or any other Stock ROM (full list). Whatever SPL is included in that Stock ROM from step #5, will actually overwrite the Warranty SPL applied in step #4. Just an SPL extract/dump cannot be applied to the device because they are not signed. It also cannot be done when the HardSPL is present because the HardSPL does not allow overwriting of itself.
Steps to return the Fuze back to STOCK:
Unzip the attachment called JZ_Fuze_WarrantySPL_1.95.zip to a new folder.
Run the EXE file to flash OliNex's 1.90 Warranty SPL. I hacked his file to say 1.95 (if HardSPL is NOT present on your device expect the flashing process to stop at zero percent w/o any progress, and ask yourself did I read bullet 2 at the very top!)
Get to the tri-colored boot screen by holding power+volumeDown+reset to verify that you see 1.95... you're not done. It should look like this... (NOTICE: THE LAST TWO LINES ARE MISSING WHEN COMPARED TO THE VERY FIRST SCREENSHOTS AT THE TOP)
Not done yet if your tri-color boot screen looks like this:
At this point, you're ready to flash the AT&T Stock 1.95 ROM which can be downloaded from here or here. If this is done correctly you should see the same tri-color boot screen as in the very first screenshot on top.
Props go out to: Olipro, Cmonex and mskip - thanks for the software and the insightful info!
Thanks!
JZ
Security and SIM Locked Info...
If your phone is Security or SIM Unlocked and you feel that you need to lock it back up, below is some info. However, I feel that AT&T and HTC will not care if it's security locked or unlocked, the screenshots below with the unlocked verbiage is actually a replacement that AT&T sent to me already Security and SIM unlocked.
SIM Unlocked: Allows you to use SIM's from another carrier. Can be done using codes or unlocker programs on xda-devs.
Security Unlocked: Allows you to flash radios from another device (i.e. Blackstone or Diamond) - It does other stuff, but this is all the casual user will use it for.
To check if your phone is SIM or Security Locked you need ATCommander. Below are the commands for ATCommander to check the status of those two things.
[email protected]?40 --- tells you if you are SIM Locked (all zero's is unlocked)
[email protected]?AA --- tells you if you are Security Locked (all zero's is unlocked or here)
1) Reset Call Timers to zeros (optional and needed!) AT command: [email protected]=270f,270f
2) SIM relock is not needed for Warranty Service, per Olipro.
3) Relock Security last with Secrelock.zip by running the EXE on the device. Or AT command to Security Lock: [email protected]=7,1
To SIM unlock your phone for FREE, call AT&T and say that you're traveling abroad and need your phone to work with another SIM chip, they will give you an unlock code!!! It will not look like the one pictured at the top of this thread, on the right, which says "Security Unlocked", but it will be SIM Unlocked. Keep in mind that a ROM can change your IMEI by the last two digits causing the need for a new unlock code from AT&T.
reserved post 2
reserved post 3
would you be able to do this hack for SPL 1.69 Raph 300 as well? That's T-Mobile
Dust2Dust said:
would you be able to do this hack for SPL 1.69 Raph 300 as well? That's T-Mobile
Click to expand...
Click to collapse
Once I explain a bit more, I think your need for a hacked SPL will disappear.
Basically, apply either my attached zip on post #1 or use the Warranty SPL from OliNex... this brings you to a level where you can just apply a STOCK ROM (which includes the SPL) and whatever SPL is on that ROM will overwrite the warranty SPL... simply use a ROM that has that 1.69 SPL version and apply it to your device.
JZ SmartMort said:
Once I explain a bit more, I think your need for a hacked SPL will disappear.
Basically, apply either my attached zip on post #1 or use the Warranty SPL from OliNex... this brings you to a level where you can just apply a STOCK ROM (which includes the SPL) and whatever SPL is on that ROM will overwrite the warranty SPL... simply use a ROM that has that 1.69 SPL version and apply it to your device.
Click to expand...
Click to collapse
would that be like the one I created but has not yet been tested?? As there is no dutch factory T-Mobile rom available other than reconstructed ones that only have OS.nb.
http://forum.xda-developers.com/showthread.php?t=504570
If so I am going to flash the thing and see what happens with radio and splash.
Great, keep it up!
Dust2Dust said:
would that be like the one I created but has not yet been tested?? As there is no dutch factory T-Mobile rom available other than reconstructed ones that only have OS.nb.
http://forum.xda-developers.com/showthread.php?t=504570
If so I am going to flash the thing and see what happens with radio and splash.
Great, keep it up!
Click to expand...
Click to collapse
Interesting method of mixing different ROM pieces, a little on the desperate side but I've done lots of desperate things with NBHtool.
The problem is the key-word that you see at the top of this thread, your ROM is not "SIGNED" which means that your ROM might not be able to be applied to the device at all.
JZ SmartMort said:
Interesting method of mixing different ROM pieces, a little on the desperate side but I've done lots of desperate things with NBHtool.
The problem is the key-word that you see at the top of this thread, your ROM is not "SIGNED" which means that your ROM might not be able to be applied to the device at all.
Click to expand...
Click to collapse
Thanx m8 , that is the feedback I needed and was asking for. I will take the spl out and try to flash and see what happens.
It is not that I am on the desperate side, I just want to get this over with and be prepared once I am desperate, which hopefully doesn't happen for a while anymore
EDIT: I took out SPL, splash and radio and it allows me to flash ! using the czech stuff, Flashing as we speak...
Finished in czech:
Hey Dust2Dust did you manage to make a warranty RMA ROM for the MDA Vario IV?
Part of the first post said:
if you want to security unlock your phone for FREE, call AT&T and say that you're traveling abroad and need your phone to work with another SIM chip, they will give you an unlock code!!! It will not look like the one pictured below on the right, but it will still be security unlocked.
Click to expand...
Click to collapse
I have to point out that what you just discribed is not security unlocked... but SIM unlocked. There is a difference. SIM unlocked (which is what you are describing) is where you can put in another carriers SIM card and still use your phone with 100% functionality. Security unlocked is when you can put another carriers radio on.
Just dont want people to get confused.
great thread
AdamNimrod said:
I have to point out that what you just discribed is not security unlocked... but SIM unlocked. There is a difference. SIM unlocked (which is what you are describing) is where you can put in another carriers SIM card and still use your phone with 100% functionality. Security unlocked is when you can put another carriers radio on.
Just dont want people to get confused.
Click to expand...
Click to collapse
Got it, thanks for clearing it up, I will correct it. Learn something new every day
Questions though:
SIM Unlock is something that you need a "code" for from the phone vendor another carrier's SIM can now be used, correct?
Security Unlock will allow you to flash another device's radio?
HardSPL allows you to flash a non-signed OS, Radio & Splash? Or just a non-standard Radio (from another device)?
Security unlocking is achieved how? HardSPL? So, security unlock=hardspl/softspl?
OliPro used Security/SIM/CID unlock in this thread title, do all three mean the same thing? Or will OliPro send a different activation code for each feature?
secrelock.zip that I reference in the first post is to re-lock the Security Unlock? Or SIM unlock?
On my first screenshot, top-most phone pictures (on the right) says "Security Unlocked" and I received it this way from AT&T warranty, which feature is unlocked on the device, Security or SIM? Seems odd that AT&T would send me a phone that I can flash any ROM to... (it does say security unlocked after all)
Anybody that knows please speak up, this is interesting stuff.
Thanks!
JZ
EDIT: per these posts (post1, post2, post3, post4) I definitely learned that SIM unlock is different from Security Unlocked. Two different commands in ATCommander:
[email protected]?40 --- tells you if you are SIM Locked (all zero's is unlocked)
[email protected]?AA --- tells you if you are Security Locked (all zero's is unlocked)
The phone that I have in the screenshot (with the white "Security Unlocked" verbiage) shows that I'm both SIM & Security UNLOCKED... the phone w/o that white band shows 1's for both settings so it's actually locked yet I do have a OliPro's HardSPL on it. I wonder if the white band is available on older devices.
JZ SmartMort said:
Got it, thanks for clearing it up, I will correct it. Learn something new every day
Questions though:
SIM Unlock is something that you need a "code" for from the phone vendor another carrier's SIM can now be used, correct?
Security Unlock will allow you to flash another device's radio?
HardSPL allows you to flash a non-signed OS, Radio & Splash? Or just a non-standard Radio (from another device)?
Security unlocking is achieved how? HardSPL? So, security unlock=hardspl/softspl?
OliPro used Security/SIM/CID unlock in this thread title, do all three mean the same thing? Or will OliPro send a different activation code for each feature?
secrelock.zip that I reference in the first post is to re-lock the Security Unlock? Or SIM unlock?
On my first screenshot, top-most phone pictures (on the right) says "Security Unlocked" and I received it this way from AT&T warranty, which feature is unlocked on the device, Security or SIM? Seems odd that AT&T would send me a phone that I can flash any ROM to... (it does say security unlocked after all)
Anybody that knows please speak up, this is interesting stuff.
Thanks!
JZ
EDIT: per these posts (post1, post2, post3, post4) I definitely learned that SIM unlock is different from Security Unlocked. Two different commands in ATCommander:
[email protected]?40 --- tells you if you are SIM Locked (all zero's is unlocked)
[email protected]?AA --- tells you if you are Security Locked (all zero's is unlocked)
The phone that I have in the screenshot (with the white "Security Unlocked" verbiage) shows that I'm both SIM & Security UNLOCKED... the phone w/o that white band shows 1's for both settings so it's actually locked yet I do have a OliPro's HardSPL on it. I wonder if the white band is available on older devices.
Click to expand...
Click to collapse
Here are some answers that I got from DaveShaw. He answers most of my questions. The only left-over question is secrelock.zip will lock both SIM and Security or just Security?
http://forum.xda-developers.com/showthread.php?p=3225507#post3225507
SIM: Allows you to use SIM's from another carrier. Can be done using codes or unlocker programs on xda-devs.
Security: Allows you to flash radios from another device (i.e. Raphael) - It does other stuff, but this is all the casual user will use it for
CID: CID unlocking is an old concept, nowadays you flash Hard SPL instead. This lets you flash any ROM, Splash or Radio (depending on sec unlock) to your device. N.B. the CID is the carrier ID (e.g. HTC__001). The stock SPL's only let you flash ROM's that match the CID in the ROM image with the CID on your device.
Also, SuperCID is an even older concept no longer valid on newer devices.
Help
I'm really new to all this and I need to bring my phone back in for warranty repair and I just need to replace the SPL. I downloaded your zip file, unzipped it and tried running the .exe in the folder. It started the program but gave me an error after the second screen saying that the updater couldn't open the requested file. I'm not sure what I'm doing wrong. Can you help me?
Kyireana said:
I'm really new to all this and I need to bring my phone back in for warranty repair and I just need to replace the SPL. I downloaded your zip file, unzipped it and tried running the .exe in the folder. It started the program but gave me an error after the second screen saying that the updater couldn't open the requested file. I'm not sure what I'm doing wrong. Can you help me?
Click to expand...
Click to collapse
This kinda stuff is not easy to troubleshoot remotely so I'll give you some pointers... take a picture of your bootloader so I can have a look. Also take a screenshot of the error you get (if on the computer) use print-screen key and paste into mspaint or MSWord...
From the sound of it, you do not have a HardSPL so you're trying to reverse something that you probably don't have activated.
Thank you for the guide.
I just flashed back to stock spl / os.
I have one concern, the screenshot from the Att fuze show Raph*** in the tri-color boot screen, mine however shows Raph110. Is that acceptable for a warranty exchange?
Thanks in advance!
trancer_84 said:
Thank you for the guide.
I just flashed back to stock spl / os.
I have one concern, the screenshot from the Att fuze show Raph*** in the tri-color boot screen, mine however shows Raph110. Is that acceptable for a warranty exchange?
Thanks in advance!
Click to expand...
Click to collapse
Yeah, you're perfectly fine... this is a quote from the first post:
Screenshots below show RAPH110 and RAPH*** - there is no difference, so don't concentrate on that.
And make sure to actually look at those screenshots (top-most) on the first post as you want to use them for comparison.
Also make sure to have the last two lines:
PCBID 0x80
RID 0x0
Huh I get both a one and a zero
JZ SmartMort said:
To check if your phone is SIM or Security Locked you need ATCommander. Below are the commands for ATCommander to check the status....
[*][email protected]?AA --- tells you if you are Security Locked (all zero's is unlocked
Click to expand...
Click to collapse
OK ran the software and not sure of the result.
Got for the AA run "@secu_flag 1 0"
So since I got both a one and a zero I'm not sure of the status.
webfrm said:
OK ran the software and not sure of the result.
Got for the AA run "@secu_flag 1 0"
So since I got both a one and a zero I'm not sure of the status.
Click to expand...
Click to collapse
You actually quoted my first post with the answer --- all zero's is unlocked... you have a 1 that means locked. Click the link too all zero's is unlocked from above... you would have seen your answer.
Hey guys, let's see if you can help me.
My phone is dead, probably hardware failure. I last ran MAGLDR on it, and it was starting to tweak out. Random reboots, not booting up, etc. I flashed it back to stock about six months ago and it was still rebooting and dying but the rom did boot. Since then, for whatever reason and without actual use of the phone, the hardware problem has become MUCH worse. I can no longer boot into WinMo but can 1 in 20 tries boot into the HSPL screen/bootloader.
I need to send it back into HTC before the 28th of October and I don't want them to see Cotulla HSPL on screen. I've never overclocked or so much as used the phone for a long period of time, and I'm extremely gentle to electronics, so I don't know what the problem is.
I've been trying to flash back via this method.
http://www.youtube.com/watch?v=Wc89Gh0QpIY
I don't think the rom is right for my device, so I haven't used it. I own a TMOUS HD2 and the rom this guy has is a WWE rom. I don't know if this is safe to flash. Anyway, I went ahead and downloaded the latest TMOUS stock rom which unzips as an executable. I then ran the EXE, and it unzips the RUUXXXX.nbh file into C root--at least that's where I found it. I copied the file to root of the SD (FAT32) and renamed it LEOIMG.nbh. When I boot into the bootloader tri-color screen, it finds the image but only gives me an option for flashing the OS. In the youtube vid the guy flashes all sorts of things. When I flash the OS, it doesn't replace the HSPL. Does anyone have a LEOIMG that includes the SPL for a regular TMOUS? His RUU is 266 mb and mine is 5.
Any thoughts? I've scavenged the internet and I can't find a good nbh file that works.
metroidnemesis13 said:
His RUU is 266 mb and mine is 5.
Click to expand...
Click to collapse
thats wrong, you have a corrupt download or something, whats the filename before you extracted it? Go to t-mobile.com and download again. Instead of running the .exe and finding the file in c drive, you can just change the filename extension from .exe to .zip and it will open as a zip file.
I found an RUU that is 200 something MB. It has all that he had on his. It is also a TMOUS version. The problem I am having is the thing freezes after about a fifth of the installation completes, time and time again. I believe the image is good. I think the NAND on my HD2 is permanently messed up. When I access the tricolor screen now it tells me that the update failed and to please try again, and cotulla is still printed at the top. Any thoughts? Do you think HTC checks these? I sent in a Nexus One in and they sent me a new one back, no questions asked, even though the bootloader was unlocked.
I have to send this in very soon, since it expires the 28th of Oct.
all you can do is try all the tmous roms from the 't mobile test and stock roms'' thread, but not teh first three in eth list.
if all else fails you can try flashing a non tmous stock rom, which will brick teh phone, BUT will also brick bootloader, so they wont be able to see cotulla, which is the ionly thing they are interested in.
DISCLAIMER - flashign a non tmous stock rom WILL brick your tmous. The point being it will not boot at all, completely dead, so tey cant see the spl has been hacked.
Sounds like a plan.
That didn't work. The UK rom exe freezes at 1%. Returning to the bootloader I still see Cotulla's name. Ideas?
EDIT: After the third or fourth attempted flash it now says software update failed with an exclamation point and a triangle, and the only way to access the tricolor screen is to have a LEOIMG on an sd card and hit cancel. There it says cotulla. I'm going to try to brick it more with a .51 radio just to be safe.
Thanks for your help guys. The phone pretty much bricked itself. I couldn't flash the .51 radio because it stopped turning on after a while. I sent it into HTC and they repaired it, no questions asked. Now as long as it doesn't fail again... I may get an EU version because those seem to be a little bit more reliable...
Thanks again! Thread can be closed.