NBD 8.x doesnt do anything! - 8125, K-JAM, P4300, MDA Vario ROM Development

Hy everyone. I tried installing NBD 8.1, 8.2, and 8.3 on my phone today and it goes well. It says it has finished updating my phone and then when I start my phone, it says its being customized and I see everything being installed. After it is done installing, it resets. When it resets it is just the same old thing. It looks the same way it did when I first bought the phone. Im using a Cingular 8125 if it makes any difference. Thanks.

Your phone is still CID locked.
Follow this tutorial to unlock it, and follow the steps closely.

i wouldnt follow that tutorial just yet. You still need to give us a little more information like if your wizard is a G3/G4. You can only cidunlock your wizard if it is a G3.

I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek

mirekluza said:
I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek
Click to expand...
Click to collapse
I agree! I'd been flashing my G4 phone from about 5 months ago with different ROMs (almost continuously)... ShellTool is the best tool that I tried to flash ROMs without risk.
Cheers!

mirekluza said:
I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek
Click to expand...
Click to collapse
nobody bothers to read anymore and dont know what the search link looks like. The just jump on the bandwagon. But its true i had a hard time following some instructions but i got through it.

Really??
I used shelltool 2 times without problem, but then i get the 1 time a message - flashing done after 8 minutes and the flash wasnt really on the phone. Since then i use RUU (which is in the love wizard rom package) and it works for me.
Today i tried flashing nbd 8.3 to faria aku 3.3 and other faria rom with aku 4. In both casec the flashing stoped at 99% and i had to reflash it with nbd rom.
The flash didnt end , cause i have cid-locked phone?? I would like to have a newer aku(i have 2.3). HELP

I used Shelltool to install the rom I had. It finished after about ten minutes, and then I hard reset my device.
Whenever I start my phone up now it just hangs on the Cingular start up screen and this is what it says.
IPL 2.25
SPL 2.25
GSM 02.25.11
OS 6.6.6.666
Any idea what went wrong or if there is any way to fix this?
Thanks

Are you using Vista?

Nope. I used Windows XP Pro.

I had the same problem with shelltool on xp pro sp2. Get the phone in bootloader mode and flash again. Maybe with RUU , which is in the wizard love rom package. Just replace the .nkb file (rom file) to one u want.

I don't like this topic name. It should be: "I don't know how to install new rom"

A few advices from long time shelltool user
(I used it to flash "faria real thing", several version of "crossbow reloaded", "xda mobile", "pandora", "wrcx3"). I am on a locked G4 phone.
a) I always start by flashing the original ROM of my provider (in my case T-Mobile CZ) in normal way. This may not be a needed, but I read that it is *recommended*to flash your provider's ROM to have some stable base. It takes about 10 minutes or so.
b) Afterwards I flash using shelltool (see shelltool documentation how it is done)
Possible problems with shelltool
a) It does not end and the flashed phone seems to be frozen (clock is not updated etc.):
No problem, flash is done. After 30 minutes from the flash start just take your phone, do the hard reset and everything will work ok.
This (shelltool not ending) happens often, but as I said - it is no problem.
b) The wrong flash
Either the shelltool is interrupted prematurely or it the phone freezes during restart afterwards.
No problem, just reflash your provider's ROM in normal way and try again shelltool.
This happens only very rarely and I never went through this more than once.
Conclusion
Since the shelltool is limited to flashing only OS, you should not ever brick your phone in this way... The most you can do is to screw up your OS - which can be quickly recovered by flashing the official ROM from your provider.
Flashing by normal way is more dangerous: if you flash a locked phone with the ROM containing more than just OS, you can easily brick your phone (if you flash ROM just with the OS you will wonder that nothing has changed - at least this is like I understand it).
Mirek

zoki said:
I don't like this topic name. It should be: "I don't know how to install new rom"
Click to expand...
Click to collapse
I have to agree with you Zoki. Has nothing to do with your ROM.

zoki said:
I don't like this topic name. It should be: "I don't know how to install new rom"
Click to expand...
Click to collapse
I'm sorry. I didn't mean to offend you or anything. I just thought I did it the right way the first time and that something went wrong but not on my part because I followed directions doing it. I'm not saying anything bad about the rom. Sorry!!
I'll try to do it with the RUU then. Thanks a lot.

Related

(newbie) frustrations...

I understand all the stickies that are posted before this post and all the other people who has had the same issues but I really need an anwser to this question that I have not found yet...
I have followed all the steps in every tutorial I have found in this forum for my phone to be upgraded to WM6 (shelltool, "follow these easy steps", etc..) but everytime I follow these steps word for word I always end up in the same start up screen (where IPL/SPL & OS is shown)...
What am i doing wrong? Should I update my radio (2.25) to "2.19" before or after installing the new rom? I mean thats the only conclusion that I come up with...by the way I tried that and I got one screen farther, its just that I got the startup intro bleep and the white screen of eternity....help anyone?
Cingular 8125 G4 (CID/SIM Locked)
IPL 2.25.0001
SPL " "
GSM 2.25.11
OS 2.25.1.11 (lastest WM5 cingular update)
-IF everyone decides to tell me to look it up, well fine, I guess I'll have no choice and spend another two weeks of searching the endless database....
You have a G4, shouldn't you be using LokiWiz to CID unlock it first?
Madcap180 said:
You have a G4, shouldn't you be using LokiWiz to CID unlock it first?
Click to expand...
Click to collapse
will surely try that now!
thanks alot!
hope it works!
DO NOT USE LOKIWIZ!!! you have been misinformed. if you have a G4, Lokiwiz will not unlock your phone and might brick it.
I don't think G4's can be CID unlocked with that tool.
When using shell tool, make sure that you have first installed Cert_SPCS and EnableRapi to your phone. Wait approx. 2 minutes, then soft reset. After soft reset, make sure the time and date are correct on the phone ( I can't get successfully flash unless I do this), then turn off the radio. Run shelltool. Some ROMS don't give an end message. If I haven't gotten an end message in 20 minutes, I open the task manager and end shelltool and pdocwrite in that order, then hard reset.
Good luck.
oh yeah, G4s can only be unlocked via IMEI-check.
mdhensley5 said:
I don't think G4's can be CID unlocked with that tool.
When using shell tool, make sure that you have first installed Cert_SPCS and EnableRapi to your phone. Wait approx. 2 minutes, then soft reset. After soft reset, make sure the time and date are correct on the phone ( I can't get successfully flash unless I do this), then turn off the radio. Run shelltool. Some ROMS don't give an end message. If I haven't gotten an end message in 20 minutes, I open the task manager and end shelltool and pdocwrite in that order, then hard reset.
Good luck.
Click to expand...
Click to collapse
thanks for the warning, i guess i can try waiting 2 mins after installing both cabs and checking the date and time...
I don't update my radio until after flashing a new ROM.
One way that I know I've had a successful flash is that approx. 10 -15 seconds after the IPL/SPL screen loads, the screen will dim just a little bit. If you aren't looking for that, you might not even notice that the screen is just a little bit dimmer. If I don't see that, I will flash Wizard Love and start the whole Shelltool process again.
Also, the first boot takes a little bit longer than normal.
Make sure b4 you go ahead and flash G4, read all about it. Its easier to Brick G4 than G3.
I looked at your initial post again and the IPL/SPL indicates that you have a G3 not a G4. A G4 will have 2.25.0001 instead of 2.25.001. Check that again. If you have a G3, you don't have to use Shelltool, but will have to use Lokiwiz after all.
make sure that you hard reset after fnish to flash with shelltolls
if this dont work, first apply shelltools and then a wm6 rom
always works here!
mdhensley5 said:
I looked at your initial post again and the IPL/SPL indicates that you have a G3 not a G4. A G4 will have 2.25.0001 instead of 2.25.001. Check that again. If you have a G3, you don't have to use Shelltool, but will have to use Lokiwiz after all.
Click to expand...
Click to collapse
yeah that was my mistake its: 2.25.0001
well it seams you havent read all threads and all tutorials, otherwise you should now that you have to CID unlock your device via imeicheck, there is no other way to do it.
I love newbie bricks!!
charly_mx said:
well it seams you havent read all threads and all tutorials, otherwise you should now that you have to CID unlock your device via imeicheck, there is no other way to do it.
I love newbie bricks!!
Click to expand...
Click to collapse
i love how your post was useless and false
nycelitemaster said:
Make sure b4 you go ahead and flash G4, read all about it. Its easier to Brick G4 than G3.
Click to expand...
Click to collapse
Hi I need yr urgent help - as when i download wm 6.0 i am stuck at 99% and then it does not proceed further - spent an antire day at this situation - pls advise & apprciate yr kind help.

Problem flashing faria's new rom. Please help

Hello I have a CID locked G4 HTC Wizard(T-Mobile MDA) and am trying to flash faria's new rom to my wizard. When I use the RUU I get an error at 99% and have to reflash the original rom provided by T-Mobile and then when I use shelltool(I installed enablerapi.cab and also cert_spcs.cab and restarted the device like instructed to do), I get stuck on the boot screen and this is what I get.
IPL: 2.26.0001
SPL: 2.26.0001
GSM: 02.25.11
OS: 2.18.0.0
If anyone has an idea of a way to circumvent this issue, please help me because I really want to install this rom.
Thanks, Dan.
don't flash the rom using RUU method. Sounds like you aren't letting shelltools finish all the way. In shell tools install the two cabs wait a few minutes,restart, flash using shelltools, let it sit for about a half hour if it doesn't give you a end confirmation.
Actually i am installing both cabs provided in the shelltools download and then waiting a few mins and then rebooting the phone and then ran shelltools and waited untill it instructed me to hard reset and and did exactly as it told me to do and even tapped the screen as soon as the phone came back on as faria reccomended. It just seems to get stuck on the initial boot screen where it tells you your ips and spl.
Edit: Just tried again to flash the rom using the shelltools program with no success... I used the readme pdf and did exactly what it said to do and it just wont install. I think I'm just going to wait untill I can shell out the money to have the phone CID unlocked.
Thanks for trying to help me though. I appreciate it.
Are you flashing an official rom everytime before you flash a cooked rom? That's what is recommended. Have you taken out your sdcard when you flash, and turning of any virus scanner and also your radio? These are some suggestions to try. Reason why I said try again people have gotten it to go through on the 3rd or 4th try. Good luck on what you do hate to see you spend 40 dollars on something you can't for free
I tried all of that and nothing works. I have tried flashing farias rom i think over 10 times but i just cant flash it.
do you think there is any way to remove the ipl/spl and extended rom from farias rom so that it is just an OS like NBD 8.0? if thats possible then shelltool should be able to flash it with no problem even on a cid locked device.
my apologies for the bad spelling and punctuation, its 1am. lol

Flash - What Went Wrong?

I've always fancied flashing my Kaiser (V1615) with a new ROM, but was always nervous because I wasn't sure of the process and didn't want to risk bricking the phone as well as all the effort needed to get everything back on it I needed. Well, a few days ago my old Kaiser met the floor and an untimely end. So I decided to take the risk and put a new ROM on it and decided on the latest Dutty WM6.1 ROM.
I read all about flashing on here and made as much sense of it as I could. Thing is, I'm very technical in general, but not very familiar with Windows Mobile or flashing. I found there was lots to read, but it was all written with an assumed level of knowledge and understanding of terminology. As a result I found it quite hard to understand. I took the plunge anyway and started, but things didn't work out as expected and I didn't understand why.
I'm not trying to be critical of all the work a lot of people have put into the documentation that is available online, it's just that when I originally approached this with zero flashing experience I found it difficult and confusing to understand. What I really needed was a concise and basic introduction to flashing. I've now been through the process and after re-reading the documentation it makes a lot more sense.
I worked out you need to run something called HardSPL before you could flash a new ROM. I'm still not sure what HardSPL does apart from CID unlock the device, but what does CID unlock mean?
I ran HardSPL v1 and it started ok, but then I ended up with a white screen. At this point I already wished I hadn't started, but no going back now. Is it known why some phones white screen? Turns out it's a common problem, so followed the instructions to recover. All was well again, but still with the original ROM.
I thought I'd be brave and stuck with it and this time tried JumpSPL1.56-KAIS instead of HardSPL as recommended on one of the tutorials. This went better and I ended up with the Tri-Color screen. I plugged my USB cable in and USB showed on screen.
Next step I thought was to flash a ROM onto the device. I ran the Dutty updater on my PC and all started ok, but when the update got to 18% I received a communication error. I tried to recover using the updater, but the same thing happened. At this point the phone wouldn't boot, so I was more than a little worried and wishing I hadn't started!
Found something that described several options for recovering from this problem. I decided to try and flash the device back to the original ROM from Vodafone. When I eventually found that ROM I ran JumpSPL again, got to the Tri-Color screen and ran the updater. This time the update completed successfully and the phone rebooted and was all working again.
I decided to leave the device as it was and started customising it myself. I'd still love to put a cooked ROM on there, especially if it helps with performance, but after the experience above I'm not very confident.
Can anyone tell me where or what went wrong? I'm going to get my old Kaiser repaired and want to try again on that phone.
My flashing routene (not ideal but it works for me)
1) run the first part of the Kaiser SIM/CID Unlocker & Changer
2) after device reboots, hold camera button and restart to check SPL
3) Flash rom/radio of choice
4) Follow HardSPL v3.07, v3.28, v3.29 and v3.56 by JockyW 's second guide "If you have problems with the above process, try this:" and flash my 3.XX SPL of choice.
Sam
Wow, I need a cuppa now
I'll go through 1 at a time... (and Sam has answered some questions already)
-CID unlock means that when the phone is loading a new device into the ROM the Carrier ID check is removed, each Mobile phone carrier has a different CID in thier OS ROMs. Unlocked means you can flash a OS ROM from any carrier or a cooked OS ROM from this site.
-The Jump SPL should only be used for replacing the SPL. Do not flash anything other than SPL's when at the Jump SPL (or SSPL). OS and Radio ROMs should be flashed from either in Windows Or By Manually Entering the Bootloaders. More info on SPL's is here: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
-Have a look at flashing from SD Card to avoid communication problems, http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
-The most clear instructions can be found here: http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser#ROMx20.Upgrading
Hope this helps.
Dave
Thanks for the advice, but this is what I normally encounter when I read something on here, which is advice which no doubt makes perfect sense to the author or others experienced in flashing, but usually raises more questions than it answers in my head.
For example;
1) run the first part of the Kaiser SIM/CID Unlocker & Changer
Click to expand...
Click to collapse
What do you mean by the "first part"? The thread you've linked to doesnt really explain what I'm downloading and doing.
2) after device reboots, hold camera button and restart to check SPL
Click to expand...
Click to collapse
Ok. I get this assuming you mean the device will reboot automatically and I restart it to check the SPL version that gets shown on the boot screen, but why do I need to do this?
3) Flash rom/radio of choice
Click to expand...
Click to collapse
So at this point I can simply plug my device into my PC and run the ROM updater I've downloaded. Working out what rom/radio version to download is a minefield in its own right.
4) Follow HardSPL v3.07, v3.28, v3.29 and v3.56 by JockyW 's second guide "If you have problems with the above process, try this:" and flash my 3.XX SPL of choice.
Click to expand...
Click to collapse
I thought HardSPL needed to be run before I flashed? Also, why the different versions? Which one do I choose?
BTW, not trying to moan about everything, just posting my experiences to find out where I went wrong, but also highlight some issues hopefully other flashing newbies can relate to and authors of tutorials can draw some useful feedback from.
Only one question, do I need to CID Unlock before using Jump and HardSpl or, the Hardspl does the Supercid ?
I'm not referring about SIM since I don't care, for now
With WM6.1 - Oficiall HTC ROM
Thanks
Thanks for that one dave, on reflection i kinda missed the whole point of the thread, and as for the majority of the stuff you posted i didnt undertand that to begin with.
Also, DaveTME, if you are wanting to flash a custom rom to youre kaiser. from my experiance and from the number of times ive seen this happen. i advise against asking for reccomendations(sp?) (not saying you will but its worth saying) try a few roms out and decide from there.
Also another thing to note. if you flash to WM6.1 remember to use a 3.xx spl otherwise you'll encounter a few problems with youre device.
Sam
What do you mean by the "first part"? The thread you've linked to doesnt really explain what I'm downloading and doing.
Click to expand...
Click to collapse
download the Kaiser unlocker and run the first stage of it, the program is in the linked thread.
Ok. I get this assuming you mean the device will reboot automatically and I restart it to check the SPL version that gets shown on the boot screen, but why do I need to do this?
Click to expand...
Click to collapse
No, after the device reboots, youre given youre Rom, Protocol and Radio. if you hold the camera button and reset you'll get youre SPL displayed, youre looking for 1.01 olinex to be shown
So at this point I can simply plug my device into my PC and run the ROM updater I've downloaded. Working out what rom/radio version to download is a minefield in its own right.
Click to expand...
Click to collapse
1) Yes, just run the RUU with youre chosen rom and thats it
2) its not a minefield, just make a decision on what rom you like and flash it. theres nothing to stop you flashing another one.
I thought HardSPL needed to be run before I flashed? Also, why the different versions? Which one do I choose?
Reply With Quote
Click to expand...
Click to collapse
The 1.01 SPL will allow you to flash a cutom rom. following that you need a 3.xx SPL as they are designed for windows mobile 6.1. as for yure decision. i use 3.29, yet other users have had better sucess with 3.56. Most rom chefs will say which SPL they reccomend anyway with their rom.
-CID unlock means that when the phone is loading a new device into the ROM the Carrier ID check is removed, each Mobile phone carrier has a different CID in thier OS ROMs. Unlocked means you can flash a OS ROM from any carrier or a cooked OS ROM from this site.
Click to expand...
Click to collapse
Great. Thanks for that. Makes perfect sense now
-The Jump SPL should only be used for replacing the SPL. Do not flash anything other than SPL's when at the Jump SPL (or SSPL). OS and Radio ROMs should be flashed from either in Windows Or By Manually Entering the Bootloaders. More info on SPL's is here: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
Click to expand...
Click to collapse
Ok. I think you mean that the SPL is a component on the device? What is the difference between HardSPL and JumpSPL?
-Have a look at flashing from SD Card to avoid communication problems, http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
-The most clear instructions can be found here: http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser#ROMx20.Upgrading
Hope this helps.
Dave
Click to expand...
Click to collapse
Thanks, will have a read
DaveTME said:
Ok. I think you mean that the SPL is a component on the device? What is the difference between HardSPL and JumpSPL?
Click to expand...
Click to collapse
Read the "SPL Questions" Wiki Page, it is all there and fairly clear.
Ta
Dave

I need some help BAD! My Tilt lost sound and black screen after boot

I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
shawndh said:
I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
Click to expand...
Click to collapse
Ick...this sounds like one of a couple of things...either you really screwed it up (btw, even "really screwed up" has been known to be fixable thanks to the super awesome folks here on XDA Devs) or it's a simple fix. My first suggestion would be to put it back into bootloader (just hold the usualy bootloader buttons and stick the stylus up in the Reset hole OR take the batter out and put it back in, your choice I think) and try rerunning everything EXCEPT the KasierUnlocker (btw, dont quote me but I would almost swear KaiserUnlocker needed a special radio flashed in order to properly work...you may wanna head back to that thread and check it out. I unlocked mine with it and I can about guarantee I had a special radio...) and see if it fixes anything OR find a compatible radio and reflash it (well, first off...get it into bootloader and tell us what the bootloader says on it)
Anyways, first things first would be to see what the bootloader is showing and then work from there. Sounds like a little bug so don't freak out too bad. If you think flashing these babies are hard then you really didnt try flashing G4 versions of the Wizard =P I totally bricked one because it was the pesky G4s and I didn't realize it at the time (complete newbness lol) So yeah, Kaiser's are a LOVELY change for me =] I've flashed mine countless times and loved it since the moment I got it! =D
But yeah, gimme info! =]
Did you use WM6.1 or WM6.0 to unlock the phone? Put in boot loader and flash orginal WM6.0 ROM as the other user suggested. You should be able to flash it if it is not a brick.
If it doesn't work you can use mtty to recover your phone, the needed information you'll find in the Kaiser Wiki.
Hope it helps
I just had this exact problem.
Use the EXE included in the tutorial to flash any windows 6.1 ROM from the bootloader via USB, and you will boot again.
HTCOmega said:
Ick...this sounds like one of a couple of things...either you really screwed it up (btw, even "really screwed up" has been known to be fixable thanks to the super awesome folks here on XDA Devs) or it's a simple fix. My first suggestion would be to put it back into bootloader (just hold the usualy bootloader buttons and stick the stylus up in the Reset hole OR take the batter out and put it back in, your choice I think) and try rerunning everything EXCEPT the KasierUnlocker (btw, dont quote me but I would almost swear KaiserUnlocker needed a special radio flashed in order to properly work...you may wanna head back to that thread and check it out. I unlocked mine with it and I can about guarantee I had a special radio...) and see if it fixes anything OR find a compatible radio and reflash it (well, first off...get it into bootloader and tell us what the bootloader says on it)
Anyways, first things first would be to see what the bootloader is showing and then work from there. Sounds like a little bug so don't freak out too bad. If you think flashing these babies are hard then you really didnt try flashing G4 versions of the Wizard =P I totally bricked one because it was the pesky G4s and I didn't realize it at the time (complete newbness lol) So yeah, Kaiser's are a LOVELY change for me =] I've flashed mine countless times and loved it since the moment I got it! =D
But yeah, gimme info! =]
Click to expand...
Click to collapse
I know. The crazy thing is that I've successfully flashed a G3 and a G4 Wizard and I still find this confusing.
When I go to the boot loader screen I have:
KAIS1*0
SPL-3.56.Hard
CPLD-8
When I reset the device normally I get:
R 1.27.12.11
G 22.45.88.07H
D 1.62.00.00
I didn't try to flash any other ROMS to unlock it. I just went with the hard SPL and then tried the Unlock tool. The phone is stock.
Thanx for the replys. I reflashed the original ROM and now it's working again. This is what I have now:
When I go to the boot loader screen I have:
KAIS1*0
SPL-3.56.Hard
CPLD-8
Now when I reset the device normally I get:
ROM version 1.62.502.0
Radio version 1.27.14.09
Protocal version is 22.45.88.07H
Device info:
Windows Mobil 6
CE OS 5.2.1622 (Build 18128.0.4.4)
Can I go strait to a SIM unlocker and then flash a new ROM?
Well you've got HardSPL 3.56 flashed to it.
Why do you need to sim unlock it? Sim unlocking is not neccesary to flash one of the many Roms avaliable for the Kaiser/Tilt.
Once it's got HardSPL flashed, you're free to flash any type of rom onto it
shawndh said:
I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
Click to expand...
Click to collapse
A couple of things:
1) The Kaiser-Unlocker only works on 1.xx hardspl's, so you'll have to put one of those on first.
2) You do need to install the patched radio before you run it.
3) You'll need to flash a compatible radio afterward too, or else your device might not boot all the way.
4) Next time please post these questions in the thread for the unlocker you are using. It makes it much simpler for everyone.
stuff said:
Well you've got HardSPL 3.56 flashed to it.
Why do you need to sim unlock it? Sim unlocking is not neccesary to flash one of the many Roms avaliable for the Kaiser/Tilt.
Once it's got HardSPL flashed, you're free to flash any type of rom onto it
Click to expand...
Click to collapse
But HardSPL 3.56 doesn't SIM unlock the phone from what I understand. I need to use it with T-Mobile SIM. So I need to chenge to a 1.XX Hard SPL to do this?
So I guess I went wrong with flashing 3.56 first and not 1.1
Then I need to patch the radio
Run the unlocker
rinstall the radio
Then flash the ROM
Problem I have now is that I can't seem to go back down to a lower SPL version.
shawndh said:
But HardSPL 3.56 doesn't SIM unlock the phone from what I understand. I need to use it with T-Mobile SIM. So I need to chenge to a 1.XX Hard SPL to do this?
Click to expand...
Click to collapse
You need to read the instructions carefully, and ask questions in that thread. All the experts in unlocking will be there to help you.

[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.

Categories

Resources