Is my phone half bricked? - 8125, K-JAM, P4300, MDA Vario ROM Development

I have a Cingular 8125, I have flashed many ROMs and the last one is TNT 20273, IPL/SPL 3.08 and radio 2.19
Recently each time I have to soft reset it takes a very long time to reboot. It can be several hours.
I tried to downgrade to official Cingular rom but RUU doesn't work anymore, there is always a connection problem and it only makes a soft reset that takes hours to come back.
I tried also to force bootloader mode with camera button+reset, running enterbl.exe and disabling usb connection in Activesync but nothing worked.
Once it restarts it works fine until I have to reset but when it happens I have to wait hours to use it again.
I am desperate, I will appreciate any help or comment.
Thanks in advance
talvae

the bootloader couls be the problem. have you tried to downgrade to 225/226 what ever it is?
all you need to do is take the original rom and dump it using core kitchen or hypercore. you will see (should see several partitions once you break down the nbf back into it's parts (nb's)
using nb to nbf you can see which partitions are which and just recompile the new nbf with just the ipl/spl. then flash that new nbf using the upgrade utility.
one important question: G4 or G3?
do you have the Wizard Service tool made by mestrini?
you can figure out what type of device it is, as well as use it to flash nb's onto your phone perhaps... (dont quote me on that ask mestrini.

S.V.I said:
the bootloader couls be the problem. have you tried to downgrade to 225/226 what ever it is?
all you need to do is take the original rom and dump it using core kitchen or hypercore. you will see (should see several partitions once you break down the nbf back into it's parts (nb's)
using nb to nbf you can see which partitions are which and just recompile the new nbf with just the ipl/spl. then flash that new nbf using the upgrade utility.
one important question: G4 or G3?
do you have the Wizard Service tool made by mestrini?
you can figure out what type of device it is, as well as use it to flash nb's onto your phone perhaps... (dont quote me on that ask mestrini.
Click to expand...
Click to collapse
Thank you S.V.I., it s a G3.
Let me check if I understood, what you suggest is to use WST to flash a nb containing only ipl/spl 2.25?
If it is correct, do you think reflashing ipl/spl 3.08 could fix the problem?

I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.

Nicely thing
S.V.I said:
I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.
Click to expand...
Click to collapse
I think it is so much process to reflash but its interesant to try dump original roms... i never heard it... it sound very cool. just try to reflash from begining like it never was unlocked... wizard love etc etc etc.

S.V.I said:
I just reaaly dont understand why one would want to update the bootloader if it does not fix anything. if it isn't broken, why fix it? I can understand the radio might want to be changed, but why bootloder/bios? it does not change anything.
I recomend decompiling the original rom (the one that came from tmobile) and making a bootloader rom out of it. this means not using the cid block or the os block, just the ipl and spl blocks. flash that to your device, then you should not have any problems updating your roms using the manual bootloader mode.
also remember that if the update utility does not see your device when it is in bootloader, you need to exit the utility, and reset the phone back to bootloader, then plug in. wait for the computer to recognise the phone, then start the update utility. that should do the trick.
wst will only copy the blocks off of your phone. this means you need core, or hypercore to dump the factory rom to get the ipl spl blocks.
also, a good practice when flashing roms is to unplug it way after it starts up and you have gone through the setup welcome screens and already set up your activesync partnership.
when puting it into manual bootloader mode, you do not nessesarily need to deactivate activesync on the computer. I never have.
good luck.
Click to expand...
Click to collapse
Thank you S.V.I,
I have extracted the IPL and SPL from the original 2.26 cingular rom using the last version of WST, I have four .nb files.
Now I have to write them to my wizard but I would appreciate some advise.
Should I write each file using WST? or nessesarily I should make one rom with only this blocks and write that file?
talvae

Related

Fatal downgrade...

Hi there,
My currently installed Rom was RUU-Prophet-G4-AKU2.2-2.20-2.47.21-Jester-r1.exe. (thank you jester for you good job)
Nevertheless, this ROM is in English and I wanted to downgrade to a French One before the selling of my device.
I have tried to install the downgrade kit detailed in this topic : http://forum.xda-developers.com/showthread.php?t=267344
The first step went OK but while trying to make the secnd step, my qtek is blocked at the boot splash screen showing the Jesterz picture and red information about the SPL and so on on the upper left corner... without starting... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Don't worry, its nowhere close to being dead. If you have superCid, then use the SD card image to restore in bootloader mode. However, if the Cid is locked, then you would need a utility that can unlock Cid without Activesync mode (coz in your case, you would not be able to get an Activesync connection). imei-check.co.uk has a utility ($38 i guess) that unlocks Cid in bootloader.--- else show it to a professional. (in my country, I would have to shell out around $20 to get such a problem fixed at a mobile repair shop)
illanz said:
... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Click to expand...
Click to collapse
Just take out the battery for about 10 minutes and re-insert. If it does not re-start, do a soft resert with the stylus and hopefully you should be fine
Hy,please help!
after downgrade, it doesnt work anymore.... i mean... i cant start the mobile!
after the downgrade i disable the USB data cable and now the mobile is dead... it doesnt starts from the ON/OFF Button and even if i connect the USB cable it makes nothing! No Led on... nothing! absolutly DEAD!!!
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Try this in order to reach the bootloader:
Hold down the camera button and reset the device. (Boot Loader Mode is: Press Camara + Soft Reset, then release soft reset and KEEP PRESSING camara button till appear the Boot Loader.)
it doesnt work
I seem to have a simular problem. this is my post in another topic. It seems to fit better here.
This is what I tired so far:....
I used the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_S hip-NoVendorID and it often hangs and was slow with Push Email over GPRS.
I tried to find a way to downgrade but hadn't had time sofar. When I logged on XDA Developers Site I saw there was a new Image.
So I thought Great I dont need to find how to downgrade.
I don't know what G4 and G3 is so as everybody let's try the higest best one.
I uploaded the RUU-Prophet-G4-AKU3.3-Jester-b1
Wrong...
Now as previously stated I get to the multicolor screen with IPL 2.09 and the SPL 2.20..0001 on the screen and that's it.
I can get to the bootloader and load the same image again and get the same result.
I can load another image on and it loads to 80 Percent and says error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file.
If I try an older Version it tells me upgrad only
And when I try to upload the G3 version it tells me error[300] invalid upgrade tool. This upgrade utility canot be used for your PDA Phone. Please get newer Upgrade utility.
Trying to use the nf.nbf or the G3 with the ROMUpdateUtility_NoID of the G4 doesn't work either.
If I would like to do the downgrade tool I need a Active Sync connection which I don't have.
I have no more thoughts. Please Help.
If you would have just read the forums better you would have known if your device is a G3 or a G4. (read this!).
Now it appears you have tried both for an update. Which may possibly have bricked your phone.
But... first things first. Can you get into the bootloader? (read wiki HERE on how to do that).
If you can still get into the bootloader then there is still a possibility for updating.
Try upgrading with the latest Qtek rom (note: this is an official rom, this one works for both G3 and G4! And since it's the latest you should be able to upgrade to this one).
Instructions quoted from another post of me:
You could try the 2.20 qtek rom which seems to be working well for quite some people (found here).
Although you have to make sure you read that thread good and use the ROMUpdateUtility_NoID.exe (found here ) to upgrade.
Update instructions:
1: With the qtek 2.20 rom you need to extract the zip and the exe file in the zip with WinRAR.
2: Then there is one folder called 'OutputFile' and a folder called 'RUU_TOOLS'.
Inside the RUU_TOOLS there is prophet and in that one WWE, when you go through them and in the WWE folder you see a bunch of files (readme.doc, enterbootloader.exe etc etc).
You need to copy ROMUpdateUtility_NoID.exe to the WWE folder with all the files. And you also need to copy the 'nk.nbf' file to the WWE folder (from the 'OutputFile' folder).
3: And then you need to put your phone in bootloader mode and run ROMUpdateUtility_NoID.exe to upgrade, which should work nicely then.
Click to expand...
Click to collapse
This should give you a good enough idea of what to do. This should work (new rom combined with no NoID updater).
However, if it's impossible to get yourself into the bootloader your options of upgrading your device are getting smaller.
Downgrading of a complete rom is only possible on a CID unlocked G3 (when it's CID unlocked you would know! because you would have done that yourself) and not on a G4 device.
Flasing a G3 device with a G4 rom or G4 device with a G3 rom might possibly turn your phone into a brick. This can easily be avoided by reading the forums properly and know what you are doing.
If anything (even if it's a small thing) is not completely clear to you about upgrading/downgrading your device I'd recommend not doing so.
edit: oh yeah... if you have a G4 device (which you should know by now) you cannot downgrade from this rom (well, only via a payed online service). And when you have a G3 device you could try and CID unlock it (read wiki + forums) before you want to downgrade, or don't downgrade at all.
But whatever you do, don't try to downgrade it without doing any of those things because you'll get into trouble. (to put it down bluntly)
illanz said:
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Click to expand...
Click to collapse
If you have reached the bootloader screen, just run my installer (or any official ROM) to get your phone working again.
My Prophet Died
I need help, to restore my Prophet, i upgrade wrong rom, i need will try the SD Backup, where can i see this process ?
Sorry my Inglish is too bad.
I've merged a couple of threads under this one, as they are all about the same problem (mostly)
Opening a new thread for the same problem isnt very useful
Hi RaptorRVL
Thank you very much for your patience in resuming all this for me.
I do try to read the forum but it isn't like a manual where you find the procedure stepby step. Like the G3 and G4 version I have newer come across until now. Sorry.
I tried the image you metioned and I have the result that at 80% it tells me error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file
Any more thoughts?
As you seem to be an expert Can you let me know more about goldcard solution.
Cheers
Mick
From a readme I once found inside an update:
* ERROR [320~328] : INVALID COMMAND
These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.
Click to expand...
Click to collapse
Doesn't sound too good really. Maybe someone else here on the forums know what to do with this error :/
You did use the ROMUpdateUtility_NoID.exe and not the normal updater right? Can remember someone getting a similar error when using the wrong updater, but I'm not sure about that though...
edit: try doing a search on the prophet forums for "INVALID COMMAND" maybe there is a helpful post in there somewhere...
THANKS!! I was worried b/c i had the same problem today. I've been looking for so many threads abt this problem. Thanks for ur help guys!
same problem
so i have the same problem. I want to downgrade and it break at 95% invalid file. But now XDA is still alive. I can`t go into the bootloader but i tried this file: RUU_Prophet_220734_2207114_024721_NVID.exe
and now my Prophet is still running again. Hope i can help you. Good luck.
peter paul
P.S. sorry for my english, but its good to learn it again

I screwed up the unlocking, Please HELP!!!

I didn't read the unlocking SIM procedure by jocky properly. I understood that I MUST get HardSPL installed, and so I go the JumpSPL1.56-KAIS.exe to the phone and then executed it. It got me the tri-color screen (Is this called bootloader?) and then I executed the KaiserCustomRUU.exe from the flash-HardSPL.zip thinking that this will put in the HardSPL into the ROM. The progress bar went upto 95% and then it exited with error and after that the "Recovery" option of the loader hasn't been able to revive the phone. Every time, I put the battery back in and power it up, I get the tri-color screen with the following message:
RUUNBH (on the top right hand side of the screen)
KAIS1*0
SPL-1.56.0000
CPLD-8
I think I now understand the mistake I made. I had a bunch of .nbh files in the directory from where I ran the KaiserCustomRUU after extracting and that is why it must have failed. Now every time I get the tri-color screen when I boot up.
Can someone please help me recover from this position? I have now got the actual simunlocker zip from the original thread and extracted it with folder names and so now I am ready to try again, only if I can recover from the mess I created. Please help!!!
mtty recovered, but I get back the bootloader every time I power up
I used mtty (set 14 0 and boot) to make the phone work (now data was lost and all my prgrams were still there). However, every time I power up my phone, the tri-color screen is back. How can I resolve this?
When I run mtty, I get the following messages on mtty:
set 14 0
HTCST ÚÈÒHTCE
Cmd>boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
FMD_ReadSector+, bad block no=0xFAC0, status:0x0
flash the original rom your device came with! only shot buddy!
Thanks for the advice. Where do I get the original ROM and how do I flash it? After the mess I created, I want to be doubly sure. I remember the versions of ROM that the phone used to show during bootup was R1.27.12.11 and D1.56.00.00 (I don't remember the G number). Appreciate if you could let me know. I have downloaded the Radio ROM numbered 1.27.12.11... is that the original ROM?
if it's a tilt, flashing the original rom will not work, you will get an invalid model error. Instead, use this one RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe. Trust me, been there done that. (twice)
Once you've done flashing to RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe and you want to unlock, HardSPL, then flash it back to RUU_Kaiser_CINGULAR_WWE_1.57.502.2, then start w/ step 1 from simunlock.
the_passenger said:
if it's a tilt, flashing the original rom will now work, you will get an invalid model error. Instead, use this one RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe. Trust me, been there done that. (twice)
Once you've done flashing to RUU_Kaiser_CINGULAR_WWE_1.61.502.2.exe and you want to unlock, HardSPL, then flash it back to RUU_Kaiser_CINGULAR_WWE_1.57.502.2, then start w/ step 1 from simunlock.
Click to expand...
Click to collapse
Did you mean to attach the ROM because it isn't there? I found this thread http://forum.xda-developers.com/showthread.php?t=335568 and it shows a ATT_SPL ROM. But, I ran out of free download limits from rapidshare for today (tonight). Is that the correct procedure? And when you say "flash" the ROM, please correct me if my understanding is wrong:
1. Get the bootloader running (tri-color screen). In my case, just power cycling does it.
2. Have the .nbh file for the ROM and the KaiserCustomRUU.exe in a folder with no other files in it in your PC.
3. Execute the .exe file which should take me thru the prompts on the PC to flash the ROM. I should see a progress bar on the PC as well as cellphone.
Is this procedure correct?
If I am able to get the device back to original state, I will need to find out how I can get the HardSPL loaded "definitively" as well.
sigh, I thought you know how to flash. Anyway, i'm being nice tonight.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
get the 1.61.502.2 from that link. put your phone into that tri-color screen, run the exe file you just download. That will bring your Tilt back, if you want to unlock the phone, then read my previous post again, and again and again if you still dont get it.
the_passenger said:
sigh, I thought you know how to flash. Anyway, i'm being nice tonight.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
get the 1.61.502.2 from that link. put your phone into that tri-color screen, run the exe file you just download. That will bring your Tilt back, if you want to unlock the phone, then read my previous post again, and again and again if you still dont get it.
Click to expand...
Click to collapse
I know why you feel that way. But, since I screwed up a simple process, my grey cells have really degenerated. My apologies for being dense. I did download that file from the original post of the thread, but now I have run out of free downloads from Rapidshare and I don't have a paypal account. I have to wait another 1hr before it allows me to download. I will try using the Cingular file to flash the device. Fingers crossed!!!
It'll work, dont worry. Just get a new ip and d/l from rapidshare.
Got error 294: Invalid vendor ID, just 1% into flashing. How can I make the phone not go into the boot loader every time I power it ON? Currently, I am using mtty to boot it out of the bootloader.
PS: I had earlier today downloaded the Cingular ROM, but its size as shown in Rapidshare is different from the one you pointed to. I will try that once Rapidshare allows me to.
Looks like the vendor id got screwed up when I had incorrectly flashed the device as I am not able to send emails (POP yahoo mail) or get Direct Push Mail (Outlook) working now. Before this attempt of mine to unlock the SIM, the yahoo and outlook was working fine. Now, during activesync, it says "waiting for network". I am able to browse the internet using PIE though.
I hope the AT&T ROM flashing works.
Downloaded the 1.61 ROM and was able to flash it successfully. It installed all the apps that came with ROM. However, I am not able to access my yahoo POP mail nor my Outlook. I am able to browse the internet though.
Is there a way to get the original AT&T ROM (v1.56) with the 1.27.12.11 radio? I know that that ROM worked fine with my data connections.
Edit: I am able to sync Outlook and Yahoo successfully now with the 1.61 ROM itself.
Thanks to all who helped me with this. I can't thank enough.
Try this first: http://forum.xda-developers.com/showpost.php?p=1894935&postcount=135
i screwed up TytnII
dear all...after flashing my tytnII with DCS V1.3 rom my tytnII is unable to boot up again. the only show on the screen is word "smart mobility" and 3 red lines below it. i have tried everything included hard reset, remove sim card and SD card but still wont help me. i also tried to flashed again but i cannot communicate with activesyn anymore. please if there still way to safe my baby...
Enter to bootloader,and then flash again
thank you for you advice.finally my tyntII is back on line...thanks again my man
jockyw2001 said:
Try this first: http://forum.xda-developers.com/showpost.php?p=1894935&postcount=135
Click to expand...
Click to collapse
Thanks jockyw2001.
Now that my phone is working nicely with the modified AT&T ROM, I want to attempt unlocking the SIM again. I screwed up when I tried to install HardSPL. I will write the procedure here from what I understood from your posts (and thank you very very much for your work). Appreciate if you can confirm that before I show my stupidity again.
Steps:
1. Go to the bootloader by executing JumpSPL1.56-KAIS.exe from the phone
2. Connect thru USB to my Win XP laptop (the loader should show USB)
3. Unzip the contents of flash-HardSPL.zip into an empty folder which will put KaiserCustomRUU.exe and kaiser_hardSPL_1.0.nbh files into the folder.
4. Run the .exe file from that folder which will bring up the ROM loader utility which will automatically load the .nbh file located in the same folder. This will result in the HardSPL being loaded into the phone and the SPL string as seen on the boot loader will change to SPL-1.0 OliPof. Is that a confirmation that HardSPL is loaded?
Can I get out of the boot loader mode after loading HardSPL and continue to use my phone and then attempt the SIM unlocking later?
My phone currently has the AT&T ROm v1.61.502.2 with the Radio ROM v1.27.14.09. Will jocky's unlock method work with this?

My first ROM installation

I have unlocked my CID on my G4 phone, I have downloaded SNN version 2.0 I have a question, do I just hook my phone through active sync or is there a special way to install a rom? Really could use some details here. I've read the newbie instalation post but it leaves this part out. Thanks
dwilha said:
I have unlocked my CID on my G4 phone, I have downloaded SNN version 2.0 I have a question, do I just hook my phone through active sync or is there a special way to install a rom? Really could use some details here. I've read the newbie instalation post but it leaves this part out. Thanks
Click to expand...
Click to collapse
Yep, if you have xp, another option is to flash it with a miniSD card or in the bootloader mode
I dont know your situation
lost
I have XP, I tried it and got the 3 red colors, I unhooked the usb and and rebooted the phone and it came back ok, but it updated nothing, I really want wm6 but just dont understand.
explanation Please
OK I downloaded TNT TouchFlo, This is what I see when I download and open it what do I do from here no read me's, There is a Bootloader , nk.nbf , RUUGetInfo.exe file, RUUResource.dll file, XP_ROMUpdateUtility.exe file,
Do I need to drag and drop a file into something or just click on one of the exe files. This is not explained in the newbie section. Thanks again
dwilha said:
I have unlocked my CID on my G4 phone, I have downloaded SNN version 2.0 I have a question, do I just hook my phone through active sync or is there a special way to install a rom? Really could use some details here. I've read the newbie instalation post but it leaves this part out. Thanks
Click to expand...
Click to collapse
A G4 device cannot be CID unlocked,what you mean by saying You got it CID unlocked,Have you applied 'HardSPL' what IPL/SPL it shows at present ?
I applied the hard one and the IPL is at 2.21.0001 and SPL 2.21.0lip
dwilha said:
I applied the hard one and the IPL is at 2.21.0001 and SPL 2.21.0lip
Click to expand...
Click to collapse
All you have to do is run the RomUpdateUtility.exe. I would recommend making sure you don't have any screen savers running on your pc and that you put your phone into "airplane mode" from your comm manager before clicking the update utility.
Once you click on the rom update utility you will be presented with a series of screens. The first two screens you have to check off that you understand and press next. It will then get your current rom settings then you click update then next.
The point that the your phone is being "flashed" is represented when you have a progress bar. Make sure you don't touch your pc or your phone. The process takes about 10 minutes to complete. It may also seem to "freeze" around the 99% or 100%, just let it be, this point of the process always takes longer. The process will complete with a screen saying that you've successfully updated your device, it will then send an order to reboot your phone. Congrats you've updated your phone.
error 300
everything was going good , then error 300, invalid update tool, The update utility cannot be used for your PDA phone. Please get newer update utility.
Thats what it says and I have the 3 color screen on my phone, what do I do now? LOL Hope its still ok. Everything worked fine till the update bar appeared then that message appeared.
Negative.
That is NOT CID-unlocked, just to trick RUU as if it is unlocked. If you use WST, you can still see your CID is locked.
?
What is WST, and what do I need to do?
newbie1221 said:
You are correct, you are CID unlocked. All you have to do is run the RomUpdateUtility.exe. I would recommend making sure you don't have any screen savers running on your pc and that you put your phone into "airplane mode" from your comm manager before clicking the update utility.
Once you click on the rom update utility you will be presented with a series of screens. The first two screens you have to check off that you understand and press next. It will then get your current rom settings then you click update then next.
The point that the your phone is being "flashed" is represented when you have a progress bar. Make sure you don't touch your pc or your phone. The process takes about 10 minutes to complete. It may also seem to "freeze" around the 99% or 100%, just let it be, this point of the process always takes longer. The process will complete with a screen saying that you've successfully updated your device, it will then send an order to reboot your phone. Congrats you've updated your phone.
Click to expand...
Click to collapse
newbie1221
You are wrong here,its not CID unlocked,its just tricked into CID unlocked with a patched IPL/SPL,whereas,its not actually CID unlocked.
Don't miss guide the people.
dwilha
With IPL2.21.0001 and SPL 2.21.0lip,your phone is HarSPL,its temporarily tricked into CID unlock,yes,you can flash any wm6 or 6.1 rom onto it,by just hook up the phone with pc via usb cable and run the RUU exe application included in the rom,it'll start to upgrade,but if you have problem,download the 'Mun's RUU' and replace it with the RUU application in the Rom and run it.
zabardast_1 said:
newbie1221
You are wrong here,its not CID unlocked,its just tricked into CID unlocked with a patched IPL/SPL,whereas,its not actually CID unlocked.
Don't miss guide the people.
dwilha
With IPL2.21.0001 and SPL 2.21.0lip,your phone is HarSPL,its temporarily tricked into CID unlock,yes,you can flash any wm6 or 6.1 rom onto it,by just hook up the phone with pc via usb cable and run the RUU exe application included in the rom,it'll start to upgrade,but if you have problem,download the 'Mun's RUU' and replace it with the RUU application in the Rom and run it.
Click to expand...
Click to collapse
Okay my fault, i should have phrased my statement correctly. That's what i meant to say but in the end the CID needs to be "unlocked".
Thanks guys, but with the SPL and IPL where they are I should be able to flash correct? When I do I get error 300 as I posted earlier, Yoy also state to download Muns I think, how do I replace the Ruu in it, Please explain.
dwilha said:
Thanks guys, but with the SPL and IPL where they are I should be able to flash correct? When I do I get error 300 as I posted earlier, Yoy also state to download Muns I think, how do I replace the Ruu in it, Please explain.
Click to expand...
Click to collapse
Download the RUU MUN from the attached file,extract the zipfile and copy and paste all the contents of the unzipped file RUU MUN to the folder of the Rom you downloaded and then run the RUU, or extract the 'nk.nbf' file from the Rom folder and paste it in the RUU MUN folder and run the RUU,ok
You Guys Rock
You guys ROCK, I have windows mobile 6, wahoooooooo. Thanks so very much.
I dont suppose you might know of a rom that looks like the iphone?
guess I better not press my luck, Thanks so much
CAB files
I want to add the voice calling thing and I find there are cab files for that, how do I add a cab file is it the same as a flash, or is it just copy and paste to the device? Thanks again you guys have helped me so much.
dwilha said:
I want to add the voice calling thing and I find there are cab files for that, how do I add a cab file is it the same as a flash, or is it just copy and paste to the device? Thanks again you guys have helped me so much.
Click to expand...
Click to collapse
Thanks !,glade you got it
Just copy and paste cabfile anywhere in the phone,preferably 'My documents' and execute it there in the phone,after install,you can delete the cabfile to save space
Cheers!
need help
Helo dears I have a G3 i-mate k-jam wanted to update it. Unfortunately I updated it to 3.08 with IPL_SPL_3.08 tool. Now when I try to update it, all the process goes as usual (from 0 to 100%) but after restart first screen appears win6.1 the next screen win 5 as it was. I think I have to downgrade SPL from 3.08 to 1.06 first, and then I’ll be able to update it. But how??? Pls help me.
Thanks in advance
Best regards
azhar63 said:
Helo dears I have a G3 i-mate k-jam wanted to update it. Unfortunately I updated it to 3.08 with IPL_SPL_3.08 tool. Now when I try to update it, all the process goes as usual (from 0 to 100%) but after restart first screen appears win6.1 the next screen win 5 as it was. I think I have to downgrade SPL from 3.08 to 1.06 first, and then I’ll be able to update it. But how??? Pls help me.
Thanks in advance
Best regards
Click to expand...
Click to collapse
Perhaps ! its still CID unlock,did you CID unlock it before upgrading to IPL/SPL 3.08 ? download WST 4.2.2 tool and run the 'CID Action' button to verify the CID lock/unlock status.
Don't downgrade directly from 3.08 to 1.xx,Sometimes SPL freezes at 3.08 and won't get downgraded if you flash Button's Rom 1.05 to downgrade directly,First try to downgrade to 2.xx by downloading and flashing the official Rom,then after that downgrade to 1.xx through Button's Rom.

[Q] wrong rom update, what now?

Hello everyone.
Yesterday I saw that there was a new update of my favourite rom EnergyRom. So today I downloaded it, installed it, everything went well. Until I restarted my Raphael ( raph300 btw). It kept stucking on the bootscreen.. even after I installed the rom again it still stucked at bootscreen. So I began trying to fix it with installing my hardSPL again, that didn't work either, still no further than my bootscreen.. after a while I decided to downgrade my spl to my stock-spl. that went well but still stuck on bootscreen. So I tried to install my stock-rom from my provider: (t-mobile netherlands). But then the Rom updater stuck at 0% and I received the well-known [262] error. Suddenly I saw that I stupidly accidentally installed the cdma version of EnergyRom instead of the one I needed: GSM. That explained why it wouldn't boot in the first place. Now I tried to install the olinex hardspl, but the updater stopped everytime with the 262 error. I connected my device to another computer with windows XP, but there I saw that the computer recognized it as a CDMA device.
I know it is a stupid mistake, but is there anybody who knows what I could try? I also tried to hard-reset it, but that wouldn't help either. Any help would SO be appreciated
try to search a tool called MTTY maybe it helps
lvxincad said:
try to search a tool called MTTY maybe it helps
Click to expand...
Click to collapse
Thanx, but how can I use this in combination with my problem?
As I remember 2 years ago,HardSPL is somehow depended on RadioROM. Maybe the ROM influenced the Radio with HardSPL,so try to reflash HardSPL again and Radio. Or it works absolutely not?
http://forums.techarena.in/hardware-peripherals/1161954.htm
http://forum.xda-developers.com/showthread.php?t=371154
http://htcwiki.wetpaint.com/page/RUU+Error+List
TomasNM said:
As I remember 2 years ago,HardSPL is somehow depended on RadioROM. Maybe the ROM influenced the Radio with HardSPL,so try to reflash HardSPL again and Radio. Or it works absolutely not?
http://forums.techarena.in/hardware-peripherals/1161954.htm
http://forum.xda-developers.com/showthread.php?t=371154
http://htcwiki.wetpaint.com/page/RUU+Error+List
Click to expand...
Click to collapse
No, I can't update any ROM. So now i'm stuck with my stock SPL, therefore I wanted to Hard SPL my device, but that didn't work and since then I haven't been able to update any ROM.. would flashing on a different PC help maybe? now I am on a Win7 Pc but maybe it will work in WinXP..
It is also not a bad idea to try different PC with XP to flash. I remember apx.1 month ago I tried to update HTC Trinity with WM6.5 ROM and it keeps failed with some errormessage(nowadays I can't remember which,but the syndroms was similar). Then I considered it as "bricked",until I tried another PC and everything wents correctly and the phone is in its productivity again. Yes,tfirst PC was company notebook with lot of safety kind of software(firewall,this,that,etc...) and the second one was my private laptop at home,just equipeed with regular antivirus software,all updates disabled(instead of AV).
Btw,what about trying to flash official ROM,while you are with stockSPL? Maybe it helps you to startup again the device and then HardSPL again afterwards...
TomasNM said:
Btw,what about trying to flash official ROM,while you are with stockSPL? Maybe it helps you to startup again the device and then HardSPL again afterwards...
Click to expand...
Click to collapse
yeah, that's what I thought too. I tried that also, also tried other custom roms btw before going to the stock rom. But with the stock rom it also stuck at 0% on the update
so, today I tried to flash my rom with two different computers: one with win7 and one with winXP. didn't work either.. I read the MTTY thread and after I installed the custom driver I was able to connect trough MTTY. But what commands should I use to clear the ROM and is there any way that I can update my rom via MTTY?
search MTTY on the forums the first link has all you need to clear the rom and flash via MTTY
I think you may be screwed. You should've asked for help before you started messing with the spl. I don't understand why you thought reverting to the stock spl would be a good approach; it may well be the end of your device. What you should have done is just flashed a stock rom-that would probably have restored your device. Re-flashing hard spl is kind of pointless. The only thing that can over-write hard spl is the special 'stock spl' that olinex put together. It's not entirely stock, and I am not sure that it can be over-written by hard spl. The sole purpose of the 'return to stock spl' is so that you can flash a stock rom, then restore the spl so that you can return your device for warranty/service without being dinged for having unofficial firmware on the device. When you do this, you aren't anticipating getting the device back, so I'm not sure that hard spl can over-write it. I know there have been discussions on whether or not it can be over-written, but I'm not sure that there was ever a clear answer. Anyway, with the 'stock spl' on the device, you can't flash any cooked roms to the device. If you are very lucky, you may be able to flash a stock rom. So, my advice is to try a few stock roms.
I'm pretty sure you'll need hard spl to run mtty/task 29, so I wouldn't waste your time on that. I really doubt it works, and I'm not sure what it's going to buy you, anyway. You really need to be able to flash a rom to the device, and you can't flash a cooked rom with that spl. Maybe you can flash a stock rom, but maybe not. I'm not sure which carrier it will let you upgrade to, either.
NeoTokyo22 said:
search MTTY on the forums the first link has all you need to clear the rom and flash via MTTY
Click to expand...
Click to collapse
yes I did, but the problem is that I can't access my Internal Storage, so I can't put any ROM's on that. Tonight I tried to flash a ROM via my SD card, but when I put my device in bootloader-mode it kept saying that it was 'loading...'
If the bootloader just says 'loading', then you probably need to either reformat the card to FAT32 or rename the image to RAPHIMG.nbh. Make sure you get the extension correct (not RAPHIMG.nbh.nbh).
But you're not going to flash anything with the stock spl, anyway. You need hard spl. I'm not sure you can even flash a stock rom off of the sd card-it probably needs to do it over usb.
I updated lot of smartphones already,but it was already few years ago. However I think,that SP's are flashed with MTTY. For that I needed ROM image in nbh file and with some commands you tell the PC,that it should flash it. Don't forget to disable USB connection in Activesync on XP in case MTTY will connect.
TomasNM said:
I updated lot of smartphones already,but it was already few years ago. However I think,that SP's are flashed with MTTY. For that I needed ROM image in nbh file and with some commands you tell the PC,that it should flash it. Don't forget to disable USB connection in Activesync on XP in case MTTY will connect.
Click to expand...
Click to collapse
I already managed to connect my device with MTTY, the only thing I need to know is which commands I can use to flash the ROM through MTTY. It just sucks that I am not able to go to my Internal Storage, otherwise it would be much simpler I think.
Farmer Ted said:
I think you may be screwed. You should've asked for help before you started messing with the spl. I don't understand why you thought reverting to the stock spl would be a good approach; it may well be the end of your device. What you should have done is just flashed a stock rom-that would probably have restored your device. Re-flashing hard spl is kind of pointless. The only thing that can over-write hard spl is the special 'stock spl' that olinex put together. It's not entirely stock, and I am not sure that it can be over-written by hard spl. The sole purpose of the 'return to stock spl' is so that you can flash a stock rom, then restore the spl so that you can return your device for warranty/service without being dinged for having unofficial firmware on the device. When you do this, you aren't anticipating getting the device back, so I'm not sure that hard spl can over-write it. I know there have been discussions on whether or not it can be over-written, but I'm not sure that there was ever a clear answer. Anyway, with the 'stock spl' on the device, you can't flash any cooked roms to the device. If you are very lucky, you may be able to flash a stock rom. So, my advice is to try a few stock roms.
I'm pretty sure you'll need hard spl to run mtty/task 29, so I wouldn't waste your time on that. I really doubt it works, and I'm not sure what it's going to buy you, anyway. You really need to be able to flash a rom to the device, and you can't flash a cooked rom with that spl. Maybe you can flash a stock rom, but maybe not. I'm not sure which carrier it will let you upgrade to, either.
Click to expand...
Click to collapse
Oke, thanx for your input. I tried to reset my ROM memory with mtty/task 29, but that didn't work, just like you predicted. So my next question is: 'Is there any app that can perform the task 29 without MTTY?'. I googled it, but I could only find the task 29 app for the HTC HD2.. And further, does anybody have a recovery ROM for my RAPH300? I tried the stock ROM on the XDA thread of HTC Raphael, but still got the 262 error
There's really no point in doing Task 29. The bad rom isn't what's killing you now, it's the SPL. It's going to block task 29, no matter what you try (that's one of it's jobs). You should just try to get hard spl back on the device, or try flashing every stock rom you can find. I tend to doubt that either will work, though. The only other option would be to look up the jump spl developed by PoF. I don't remember the name (search for threads started by him), but it was a universal soft spl that would temporarily CID unlock devices so you could flash custom roms. I've never used it before, and I don't know how it loads. You may not be able to load it onto your device with its current state, and it may not even be compatible with a Raphael (it's 3 or so years old), but it's probably worth at least checking out.
Edit: here's the jump spl link. I think you may have to activate it off the device.

[Q] Does updating the SPL update the Bootloader?

My Titan cannot get updates to install and it seems to be related to the Bootloader.
http://forum.xda-developers.com/showthread.php?t=1481445
http://forum.xda-developers.com/showthread.php?t=1435745
HTC Hong Kong wants me to take my Titan to their service center for servicing, which will wipe my data in the process. Since there's no way for me to backup my messages and app data, no way I'm doing that, I'll either find a way to fix this problem myself, or brick my device trying.
My Titan's About screen says its Bootloader version is "2.2.160015.3(134181)". If I get an .nbh of a newer ROM, keep only the SPL.nb and throw away everything else, and flash the new .nbh with RUU or the Goldcard method, will the Bootloader be updated to a newer version?
The SPL is the bootloader, yes.
There are ways to update the SPL without flashing the whole OS (which also wipes the phone). For my HD7, there was a "radio update" RUU download that had both the radio and SPL updates in different files. I removed the radio part, and then put the phone in download mode and ran the RUU. It downgraded my SPL from 4.5 to 3.1 (so I can now use HSPL again, if I choose to). Something similar might work for you.
Be sure you use an RUU that doesn't wipe the whole phone. You'll get a message telling you it will wipe the phone anyhow (scary) but not all of them do so; it depends on a configuration setting.
GoodDayToDie said:
The SPL is the bootloader, yes.
There are ways to update the SPL without flashing the whole OS (which also wipes the phone). For my HD7, there was a "radio update" RUU download that had both the radio and SPL updates in different files. I removed the radio part, and then put the phone in download mode and ran the RUU. It downgraded my SPL from 4.5 to 3.1 (so I can now use HSPL again, if I choose to). Something similar might work for you.
Be sure you use an RUU that doesn't wipe the whole phone. You'll get a message telling you it will wipe the phone anyhow (scary) but not all of them do so; it depends on a configuration setting.
Click to expand...
Click to collapse
I've (accidentally) tried using the stock RUU and the HD7 RUU that doesn't wipe the phone, both couldn't flash the SPL .nbh I made, the progress bar just stuck at 0% forever.
I'm thinking of trying the goldcard flashing method, but does it accept SPL-only .nbh files? Will it wipe my data after flashing the .nbh I give it?
If it's going to wipe my data anyway, I'm going to stick to 7740 for a while until Microsoft comes with a better backup solution.

Categories

Resources