ok guys and girls. I just put in a request to have my phone replaced because of screen issues. I have SuperCID unlocked my phone, and have the XDA live running on it right now with radio version 1.27. What do i need to do to make it looked like the phone has never been messed with?
I just don't want them to call me back and give me @#$% about it.
Thanx for the help.
how about flash the rom it came with
You can flash the original ROM version and language. But the SuperCID stays. Unlikely that they'd spot this unless they examine the phone deeply.
I sent a SuperCID'ed and SIM unlocked Cingular 8125 in for replacement about 7 months ago and it was replaced without question. I know they're different devices, but that's my experience.
k thanx for the help guys
hey im sending my device in with screen issues as well, and i have the 1.34 radio is there any way to get it back to the 1.16 radio it came with. i tried to flash it back but it never starts upgrading
I handed in my bricked JASJAM a couple of days ago for "warranty repair". No word yet whether the warranty will cover this or I will have to pay the MB swap.
SSPL Tool will work for this.
koolhand79 said:
hey im sending my device in with screen issues as well, and i have the 1.34 radio is there any way to get it back to the 1.16 radio it came with. i tried to flash it back but it never starts upgrading
Click to expand...
Click to collapse
You should not have to worry about the CID, but it might be better if you flash the old ROM and radio. SSPL is the way to go if you can't flash it back to what is was.
Yeah, hopefully SuperCID isn't a problem, but it would be nice to have a way to reverse it some time in the future, especially now that Des's SSPL makes it redundant for most people.
abubasim said:
I handed in my bricked JASJAM a couple of days ago for "warranty repair". No word yet whether the warranty will cover this or I will have to pay the MB swap.
Click to expand...
Click to collapse
How much do you think that it will cost to replace the mother board?
kyphur said:
SSPL Tool will work for this.
Click to expand...
Click to collapse
i tried the SSPL tool with this and still nothing. i get the BL screen with the SSPL and 1.09.ds but it never starts to upgrade the radio. it just sits at 0%
koolhand79 said:
i tried the SSPL tool with this and still nothing. i get the BL screen with the SSPL and 1.09.ds but it never starts to upgrade the radio. it just sits at 0%
Click to expand...
Click to collapse
Des SSPL uses spl 1.09 which does not have 'rtask' command, so you must use a radio upgrade in NBH format, not in NBF as you're probably using now.
koolhand79 said:
i tried the SSPL tool with this and still nothing. i get the BL screen with the SSPL and 1.09.ds but it never starts to upgrade the radio. it just sits at 0%
Click to expand...
Click to collapse
When I updated my radio today (for the first time), mine sat at 0% for about 2.5 minutes before moving directly to 4%, and eventual success. Are you sure you're waiting long enough?
pof said:
Des SSPL uses spl 1.09 which does not have 'rtask' command, so you must use a radio upgrade in NBH format, not in NBF as you're probably using now.
Click to expand...
Click to collapse
ok i am using the nbf and not the nbh. any advice on how to get this radio in nbh. i have searched the WIKI and maybe im missing something. if so just point me in the right direction. thanx
RabanJr said:
How much do you think that it will cost to replace the mother board?
Click to expand...
Click to collapse
The price seems to vary a bit depending on the country. A couple of guys on the dead hermes thread have done it. This post shows that the prices charged by HTC America and HTC Europe vary significantly.
just to ask, if i use the aku 2.3, radio 1.16 rom full update from the wiki site, will it change everything back for me or will i have to use the sspl program? I just want to make it look like verything is fine.
Related
Hi,
I am a SoftBank X01HT user. Recently a rom update was released and I applied it.
ftp://210.136.175.150/F1_RUU/RUU_X01HT_1.33.761.4_1.14.00.10.exe
After update the bootloader version changed to 1.09, so I downgraded the bootloader to 1.04 and it seems to be successful (I confirmed it in bootloader mode screen). Then I installed the DoCoMo version shipped rom of following versions.
ROM Version: 1.23.731.2
Radio Version: 1.06.00.10
Bootloader: 1.04
Language: JPN (Japanese)
CID: DOCOM801
The installation finished successfully, but the radio version is 1.14!!
ROM Version:1.23.731.2
Radio Version:1.14.00.10
I tried to upgrade radio to 1.20 but in vain. I ran MaUpgradeUt_noID.exe and it seemed to work correctly till 99% (however it shows ERROR 114 finally).
After soft reset, I found that the radio version was still 1.14.00.10.
What's the matter? Anyone can help please?
Best regards,
uedam said:
Hi,
I am a SoftBank X01HT user. Recently a rom update was released and I applied it.
ftp://210.136.175.150/F1_RUU/RUU_X01HT_1.33.761.4_1.14.00.10.exe
After update the bootloader version changed to 1.09, so I downgraded the bootloader to 1.04 and it seems to be successful (I confirmed it in bootloader mode screen). Then I installed the DoCoMo version shipped rom of following versions.
ROM Version: 1.23.731.2
Radio Version: 1.06.00.10
Bootloader: 1.04
Language: JPN (Japanese)
CID: DOCOM801
The installation finished successfully, but the radio version is 1.14!!
ROM Version:1.23.731.2
Radio Version:1.14.00.10
I tried to upgrade radio to 1.20 but in vain. I ran MaUpgradeUt_noID.exe and it seemed to work correctly till 99% (however it shows ERROR 114 finally).
After soft reset, I found that the radio version was still 1.14.00.10.
What's the matter? Anyone can help please?
Best regards,
Click to expand...
Click to collapse
I also have this problem. I try to upgrade my X01HT's Radio to 1.16 and 1.20. But after softreset it show 1.14 in radio....
01015 said:
I also have this problem. I try to upgrade my X01HT's Radio to 1.16 and 1.20. But after softreset it show 1.14 in radio....
Click to expand...
Click to collapse
In addition I tried this rom with bootloader 1.09 and radio 1.18.00.10.
ftp://xda:[email protected][1].35.255.2_1.35.255.102_1.08.00.10_SHIP.EXE
The radio rom was not upgraded to 1.18, it remains 1.14.
very weird... can you attach a usb-monitor capture when trying to flash another rom? see the wiki (upgrading problems) for instructions on how to use usb-monitor.
pof, see http://forum.xda-developers.com/showpost.php?p=1068511&postcount=35
might be due to the new SoftBank ROM sold since December?
Even they http://www.imei-check.co.uk/m3100unlock.php couldn't do it:
The Unlocker it will NOT WORK with Japanase Softbank devices with SPL1.09 and radio 1.14.00.10 sold after 1st December 2006. To check your spl just put the phone in bootloader :hold the [OK] button (from the left side of the phone where the volume button is) and the [power on] button and in same time press the [reset] hole (near to the charger connector -- use stylus to press it!) and you can see IPL and SPL
Radio version can be checked from Start->Settings->System->Device Information:Radio Version.
If you buy the unlocker and claim that your phone is a 1.09 we will NOT refund you. We don't know when we will release a new update or IF we will release one!!!
Click to expand...
Click to collapse
Yes, I think the new softbank device has the radio area "read only" somehow, that makes impossible to patch the radio in order to SIM/CID unlock. However I would like to see a USB Monitor capture of the process when trying to flash a radio rom on it, to see exactly what the bootloader returns. If anyone can attach it, it would be great
pof said:
Yes, I think the new softbank device has the radio area "read only" somehow, that makes impossible to patch the radio in order to SIM/CID unlock. However I would like to see a USB Monitor capture of the process when trying to flash a radio rom on it, to see exactly what the bootloader returns. If anyone can attach it, it would be great
Click to expand...
Click to collapse
Would be an explaination but uedam said he is stuck on 1.14.0.1 since he installed the new X01HT ROM. This implies he had another version before - so it seems that the read only effect isn't caused by the hardware but by the ROM and can't be removed by flashing another ROM (at the moment).
Perhaps there is a hidden command executed when the ROM is flashed. Something that write-protects a range in memory. But I have no explaination why the process runs until 99%.
Someone has to log the USB traffic when flashing the new ROM.
By the way: I'm not willing to test this on my own device
pof said:
very weird... can you attach a usb-monitor capture when trying to flash another rom? see the wiki (upgrading problems) for instructions on how to use usb-monitor.
Click to expand...
Click to collapse
pof,
I installed usbmon and tried radio rom 1.20 upgrade again (it also failed...)
Here is the log files exported from usbmon. I hope it will help to solve the problem.
ftp://xda:[email protected]/Uploads/Hermes/Tools_and_Programs/usbmonlog.zip
Sorry, the file was too large to attach to this post.
p.s. If you need further information, please let me know.
Thanks uedam, the process seems to be the same like in every other device. The only "minor" strange thing is that when flashing a 0x10000 byte block at address 0x6d0000 you get a failure the first time, then the RUU does an 'rerase' of this memory portion, tries again and gets a success, and follows with the radio flashing process. But I think this has nothing to do with the problem we're facing here.
sn00x said:
Would be an explaination but uedam said he is stuck on 1.14.0.1 since he installed the new X01HT ROM. This implies he had another version before - so it seems that the read only effect isn't caused by the hardware but by the ROM and can't be removed by flashing another ROM (at the moment).
Perhaps there is a hidden command executed when the ROM is flashed. Something that write-protects a range in memory. But I have no explaination why the process runs until 99%.
Someone has to log the USB traffic when flashing the new ROM.
By the way: I'm not willing to test this on my own device
Click to expand...
Click to collapse
Yes, before upgrade I unlocked my X01HT and used with DoCoMo rom. The radio version was 1.06.00.10.
I uploaded the USB traffic log and please view the file. Does the same thing occur when writing another rom? or this is the first case?
pof said:
Thanks uedam, the process seems to be the same like in every other device. The only "minor" strange thing is that when flashing a 0x10000 byte block at address 0x6d0000 you get a failure the first time, then the RUU does an 'rerase' of this memory portion, tries again and gets a success, and follows with the radio flashing process. But I think this has nothing to do with the problem we're facing here.
Click to expand...
Click to collapse
Hmmm, would it make sense to have him log the full-upgrade process - presumably the "locking" happened when he did the RUU_X01HT_1.33.761.4_1.14.00.10.exe
and hopefully it would happen even if Radio 1.14 were already on the system when he re-did the full upgrade.....
Richard
Yes, this will be at least worth looking at
pof said:
Yes, this will be at least worth looking at
Click to expand...
Click to collapse
I did full rom upgrade again and got log to the file.
ftp://xda:[email protected]/Uploads/Hermes/Tools_and_Programs/fullupgradelog.zip
It's beyond my comprehension.
p.s. It's very large (about 400MB text file, the zip is about 120MB)
Hey uedam, nice work dude!
I've had a quick look and seems a normal upgrade to me, I see nothing related to the write-locking of the radio, but will look at it more deeply later, in case I skipped something important.
However I extracted GSM.nb from softbank 1.33.761.4 ROM and GSM.nb from HTC 1.18.416.1ROM which both should be radio 1.14.00.10 but the files are different, so I guess the locking is done in the radio itself (??).
pof said:
Hey uedam, nice work dude!
I've had a quick look and seems a normal upgrade to me, I see nothing related to the write-locking of the radio, but will look at it more deeply later, in case I skipped something important.
However I extracted GSM.nb from softbank 1.33.761.4 ROM and GSM.nb from HTC 1.18.416.1ROM which both should be radio 1.14.00.10 but the files are different, so I guess the locking is done in the radio itself (??).
Click to expand...
Click to collapse
pof, it sounds quite interesting. Softbank built the special version of 1.14.00.10 radio?
So, if possible, we cook new rom which includes radio rom same as HTC 1.18.416.1 rom then the person who has 1st version of X01HT can upgrade it safely?
uedam said:
So, if possible, we cook new rom
Click to expand...
Click to collapse
Unless I missed it, no one has been able to cook Hermes (or any of the new format) ROMs.
Richard
pof said:
However I extracted GSM.nb from softbank 1.33.761.4 ROM and GSM.nb from HTC 1.18.416.1ROM which both should be radio 1.14.00.10 but the files are different, so I guess the locking is done in the radio itself (??).
Click to expand...
Click to collapse
Oooh, that *IS* an interesting (and unpleasant) development. Sounds like imei-check has annoyed some people with good connections to HTC
Richard
rsolomon said:
Unless I missed it, no one has been able to cook Hermes (or any of the new format) ROMs.
Richard
Click to expand...
Click to collapse
If it is impossible, the person who has contract with softbank will have much trouble. Because they have to upgrade their devices till 1st of April in order to use internet connection. Softbank announced that we would not be able to connect to the net without upgrading to new rom.
uedam said:
If it is impossible, the person who has contract with softbank will have much trouble. Because they have to upgrade their devices till 1st of April in order to use internet connection. Softbank announced that we would not be able to connect to the net without upgrading to new rom.
Click to expand...
Click to collapse
Where is this announced? My understanding is that it is not possible to use "Direct Internet" if you don't have the latest ROM but you can still access the internet via normal packet communication - it's more expensive though.
chainbolt said:
Where is this announced? My understanding is that it is not possible to use "Direct Internet" if you don't have the latest ROM but you can still access the internet via normal packet communication - it's more expensive though.
Click to expand...
Click to collapse
Sorry, my explanation was not correct. You are right. Thanks.
just to dispel the myth;
SPL 1.01MFG Flashing via mtty is NOT faster than using the RUU; HTC do not deliberately slow down the process, that's just bloody stupid; the reason it can take longer is if you include a Radio ROM, because flashing a radio takes sodding ages, but can people please learn that using a proper NBH is a smarter and safer way to flash their Hermes.
I second that. this myth appeared because 1.01MFG was the first bootloader that allowed us to flash unsigned, but it didn't allow to flash a radio. So there was the general "feeling" that signature checking was slowing down the process, but it was not: the slowness is caused by flashing the radio.
True, but from strictly a ROM cooker perspective, its not faster. It takes time to build/run the RUU & when you're testing cooked roms, its just far easier to fire up the sspl 1.01MFG and lnb the new os.nb directly.
I understand safety to be the presence of BL v1.10.Oli at location 50020000.
Consequently, I keep this version flashed and test out cooked ideas (currently I'm working on the ATI video issue so I've been flashing a lot of test roms) using your 1.01MFG sspl bootloader.
Expanding on this, I believe that production cooked ROMs should include your 1.10.Oli SPL bootloader from a safety perspective based on my understanding that the BL is flashed first in the RUU under the control of the 1.09Des SSPL loader. This will guarantee a safety net should something go wrong during the OS and/or Radio flashing portion of the process. I would also imagine that this is why you state that RUU flashing is safer too.
Maybe this should be SOP whenever a new production ROM is released by Operators too: Repackage everything into a sspl that also loads 1.10.Oli. Of course, when HTC takes their inevitable next steps in this "spy vs. spy" battle, all this may be invalidated...
Here's an interesting thought: Your bootloader advancements have actually helped Operators since using this technique should result in far fewer bricks being returned for new devices. Now the question is this: does this cost HTC I wonder? Or to put it differently: who sucks up the cost of a bricked Hermes that is replaced in warranty. Whomever this is is very happy with you Olipro and likely to offer you a job as a top developer . Conversely, whomever sucks up the cost is gonna put a contract out on you....
JK: The fact is this: both have a contract on you b/c you've invalidated CID
When I run the RUU, I'll open the Windows Media Player to play the MP3 files, and the update process will be finished in 2-3 minutes.
I guess my major question is this:
At what time during the RUU flashing process is the bootloader flashed? If its the first thing to be flashed then my points above are valid. If not, then everybody who flashes needs to insure that they have 1.10.Oli in flash before stripping the bl out of any ROM they wish to flash. Perhaps we could begin to go through production ROMs and designate those that have had this done with another column on the Wiki.
Sleuth255 said:
At what time during the RUU flashing process is the bootloader flashed?
Click to expand...
Click to collapse
In the order it is placed on the NBH file, generally IPL & SPL are the first.
Sleuth255 said:
If its the first thing to be flashed then my points above are valid.
Click to expand...
Click to collapse
Yes they are: the HardSPL is flashed but the process continues with the current bootloader on device... but after the flashing process ends (or fails) HardSPL is there, which lets you recover the bad flash because even if radio is b0rken the device is seen as SuperCID. Only those with radio bootloader 0108 will need to flash a hardSPL based on 1.09 to be able to recover, the rest will be fine with the one based in 1.04.
pof said:
HardSPL is there, which lets you recover the bad flash because even if radio is b0rken the device is seen as SuperCID. Only those with radio bootloader 0108 will need to flash a hardSPL based on 1.09 to be able to recover, the rest will be fine with the one based in 1.04.
Click to expand...
Click to collapse
But there isn't a 1.09 hardSPl yet, no?
VivaErBetis said:
But there isn't a 1.09 hardSPl yet, no?
Click to expand...
Click to collapse
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Olipro said:
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Click to expand...
Click to collapse
I happen to be in this exact situation. Have bootloader 1.09 and a corrupt radio (which is why I tried to reflash and ended up with a brick). Any ideas?
/politby
politby said:
I happen to be in this exact situation. Have bootloader 1.09 and a corrupt radio (which is why I tried to reflash and ended up with a brick). Any ideas?
/politby
Click to expand...
Click to collapse
no... not quite; you need a Hard-SPL bootloader first; or, you need to be able to boot Windows.
Olipro said:
no... not quite; you need a Hard-SPL bootloader first; or, you need to be able to boot Windows.
Click to expand...
Click to collapse
that's what I thought. Any forecast on when (if) you'll have one available?
politby said:
that's what I thought. Any forecast on when (if) you'll have one available?
Click to expand...
Click to collapse
no... I mean you either need to have flashed on a Hard-SPL before you buggered it up, or you need to be able to still get into Windows after buggering it
Olipro said:
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Click to expand...
Click to collapse
But, will you publish a 1.09 Hard SPL? I will be a good protection measure for those who got the radio bootloader 0108 (like me ).
VivaErBetis said:
But, will you publish a 1.09 Hard SPL? I will be a good protection measure for those who got the radio bootloader 0108 (like me ).
Click to expand...
Click to collapse
well, if you flash 1.04 and bugger up your radio, then of course I'll send you it to flash on, but since it's essentially Des's work, I'm leaving it to him to make his own formal release .
Olipro said:
well, if you flash 1.04 and bugger up your radio, then of course I'll send you it to flash on, but since it's essentially Des's work, I'm leaving it to him to make his own formal release .
Click to expand...
Click to collapse
Ok. Fortunately I don't need it ***yet***. Thanks Olipro.
BTW: I got your 1.10 version installed and it works very well. Thanks.
Hi ,
while I had upgrading only radio to 1.38 the process has interrupted
I had removed the battery and the tytn start but at boot no gms appears instead the radio version then it freezes on windows startup.
I need to reflash the radio firmware but I can do that from active sync.
i have bl 1.04 can anyone help me?
thank you very much
have you install Hard-SPL ?
Ah the curse strikes again... get reading here.... http://forum.xda-developers.com/showthread.php?t=286755
Though post #467 may be of particular interest to you.
sorry for the delay in my response.
i have tried to read all the post about bricked tytn.
Then I have tried to use the kilt methid but my device show a blank screen after the attach. I wait more than 30 minutes after that but without result, so I think this way is not good for me.
Anyway I have use the hard spl 1,10 for the radio upgrade.
I can boot in bootloader spl 1.04 so I hope this a good thing
any ideas?
Thanks
juggero said:
sorry for the delay in my response.
i have tried to read all the post about bricked tytn.
Then I have tried to use the kilt methid but my device show a blank screen after the attach. I wait more than 30 minutes after that but without result, so I think this way is not good for me.
Anyway I have use the hard spl 1,10 for the radio upgrade.
I can boot in bootloader spl 1.04 so I hope this a good thing
any ideas?
Thanks
Click to expand...
Click to collapse
yeah, get a regular RUU for your device, an *official* one and update with it.
if you have SPL 1.10.Oli already flashed on the phone, there is something better we can do... but clearly it sounds like you haven't
Olipro said:
yeah, get a regular RUU for your device, an *official* one and update with it.
Click to expand...
Click to collapse
will not work, 'cos he has SPL 1.04 and htc_boot 0108 (as he was flashing 1.38 radio), so he needs 1.09 to reflash the radio.
I'm closing this thread, as I see juggero has already posted in the right place.
The Wiki states that AT&T OEM Rom 1.95.502.5 came with SPL version 95. All the other AT&T Roms say they came with SPL version 90. If I revert back to version 90 do I brick it or is 95 just a typo in the Wiki. I have not seen ay reference to SPL 95 other than in the Wiki. As you can't see the original SPL version on the phone before you flash hard SPL I'm nervous I'm going to brick my phone.
Thanks!
jakedog said:
The Wiki states that AT&T OEM Rom 1.95.502.5 came with SPL version 95. All the other AT&T Roms say they came with SPL version 90. If I revert back to version 90 do I brick it or is 95 just a typo in the Wiki. I have not seen ay reference to SPL 95 other than in the Wiki. As you can't see the original SPL version on the phone before you flash hard SPL I'm nervous I'm going to brick my phone.
Thanks!
Click to expand...
Click to collapse
Im quite certain thats an incorrect entry, afaik the only other version of SPL around is the CDMA versions (which wont be on your device).
Whoever entered that info is getting confused with the ROM version numbers notice that that ROM has an OEM version of 1.95...the SPL is most likely 1.90. either way ALOT of members have flashed HArdSPL to thier fuze device without issue.
mrvanx said:
Im quite certain thats an incorrect entry, afaik the only other version of SPL around is the CDMA versions (which wont be on your device).
Whoever entered that info is getting confused with the ROM version numbers notice that that ROM has an OEM version of 1.95...the SPL is most likely 1.90. either way ALOT of members have flashed HArdSPL to thier fuze device without issue.
Click to expand...
Click to collapse
I do remember seeing a thread asking if someone would make a version of HARDspl with 1.95. But like you said, 1.90 works just fine. I have flashed my fuze over 30 times in 2 weeks with 1.90.
I have the extracted spl but I am not sure if there is a way to open it to read spl version number. Now I am curious lol and will have to do some research.
Note this post
and
This
I am in UK not in US but if uu download the att original rom is do come with the 1.95 spl but is not for gsm devices i think
donottouch said:
I am in UK not in US but if uu download the att original rom is do come with the 1.95 spl but is not for gsm devices i think
Click to expand...
Click to collapse
No the 1.95 refers to the OEM version.....such as the display drivers and USB drivers etc.... you wont find the SPL version number in the ROM file name or in the startup screen.
If needs be I can see if cmonex can check the version....and that ROM is definatly for GSM devices, it is the Fuze release ROM.
The CDMA stuff you will find on the same page with SPL versions 0.36 and (i think) 0.34....?
I need to return for warranty
I'm not a NOOB, I flashed my Tilt over 100 times. WAYYYYYY over 100 times. I flashed my Fuze to Hard SPL 1.90 and have tried 5 roms so far. I have a bad home key and need to return my Fuze. If my Fuze did indeed come with OEM SPL version 1.95 and I downgrade it to OEM 1.90 to return it I want to ensure that 1. I don't brick it and 2. I dont void my warranty on a 5 day old Fuze with a bad home key. I just don't want to get hosed over a Home Key. Thanks everyone!
Fuze spl
jakedog said:
I'm not a NOOB, I flashed my Tilt over 100 times. WAYYYYYY over 100 times. I flashed my Fuze to Hard SPL 1.90 and have tried 5 roms so far. I have a bad home key and need to return my Fuze. If my Fuze did indeed come with OEM SPL version 1.95 and I downgrade it to OEM 1.90 to return it I want to ensure that 1. I don't brick it and 2. I dont void my warranty on a 5 day old Fuze with a bad home key. I just don't want to get hosed over a Home Key. Thanks everyone!
Click to expand...
Click to collapse
The Fuze does indeed come with spl 1.95. I checked the bootloader before applying Hard Spl!
Dumping SPL 1.95
Does anyone feel like Dumping SPL 1.95 and putting it up? I'm not dead in the water by any stretch with the home key but I'd like to take advantage of the 30 days free swap out for a NEW not Refub Fuze. I wonder if anyone else had done a return and not put 1.95 back on.
jakedog said:
Does anyone feel like Dumping SPL 1.95 and putting it up? I'm not dead in the water by any stretch with the home key but I'd like to take advantage of the 30 days free swap out for a NEW not Refub Fuze. I wonder if anyone else had done a return and not put 1.95 back on.
Click to expand...
Click to collapse
It is very likely that ATT would never notice. Hell 80% of the company dosent even know the fuze exists lol.
That said, I have the SPL dumped. I wont be able to upload it until tomorrow though. I am at work all day.
You should be able to load it as per the directions in the Hard spl thread. Anyone that has opened the nbh can possibly post it before then though.
You could also post in the Hardspl thread or pm olipro or cmonex.
Thanks!
Thank you, I'm available as a US Beta Tester if anyone needs one.
I had to return a Fuze already, and I did so with SPL 1.90 from the HardSPL thread. All the guy at the store did was make sure the phone was in the box, didn't even turn it on.
Fortunately for us the service "experts" at ATT are not to smart. When I returned my TILT a few months ago they were shown how the keyboard was messed up but didn't even look through any of the settings either......
Imagine if some of us worked there...they would probably save a fortune on returns
ryncppr said:
Fortunately for us the service "experts" at ATT are not to smart. When I returned my TILT a few months ago they were shown how the keyboard was messed up but didn't even look through any of the settings either......
Imagine if some of us worked there...they would probably save a fortune on returns
Click to expand...
Click to collapse
My brother works for Verizon Wireless. I already told him how to check for HardSPL and the likes when someone comes in for service/repair. (Because I don't like Verizon...)
i do work for at&t. anytime a htc product comes back my boss makes me go through the device to make sure it is still stock
herg62123 said:
i do work for at&t. anytime a htc product comes back my boss makes me go through the device to make sure it is still stock
Click to expand...
Click to collapse
Can you tell us what store you work in?
Nothing personal but just in case someone here ever needs to return a Fuze, we want to make certain you are not there to make certain it is still stock.
i live i alabama
but if someone mentions this xda website when the device is returned i kinda look away and give it an all clear. if xda is not mentioned i go through it with a fine tooth comb.
that is with me only.
others maybe different.
aruppenthal said:
It is very likely that ATT would never notice. Hell 80% of the company dosent even know the fuze exists lol.
That said, I have the SPL dumped. I wont be able to upload it until tomorrow though. I am at work all day.
You should be able to load it as per the directions in the Hard spl thread. Anyone that has opened the nbh can possibly post it before then though.
You could also post in the Hardspl thread or pm olipro or cmonex.
Click to expand...
Click to collapse
Have you had a chance to upload the v1.95 SPL yet? I'm eager to get my hands on it.
Thanks.
~TWM
jakedog said:
Does anyone feel like Dumping SPL 1.95 and putting it up? I'm not dead in the water by any stretch with the home key but I'd like to take advantage of the 30 days free swap out for a NEW not Refub Fuze. I wonder if anyone else had done a return and not put 1.95 back on.
Click to expand...
Click to collapse
HI,
Same problem. I have two US Raphael (Fuze AT&T), one with original SPL 1.95 and other with 1.90.OLINEX. I need instructions for Dumping SPL 1.95 and restore it. Someone can help
Thanks a lot !!!!
warranty att
i had to warranty exchange mine already and what i did was
1.flash att stock rom
2.flash spl 1.90
3.reflash att stock rom(checked in bootloader...spl 1.95 after reflashing rom)
ive had to do it twice already and worked like charm
xdeslitx said:
i had to warranty exchange mine already and what i did was
1.flash att stock rom
2.flash spl 1.90
3.reflash att stock rom(checked in bootloader...spl 1.95 after reflashing rom)
ive had to do it twice already and worked like charm
Click to expand...
Click to collapse
So are you saying that if I flash my Fuze back to the stock rom, then flash the 1.90 stock spl, then flash the stock ROM again my spl will be back to 1.95?
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.