Fatal Error - HardSPL - Touch Pro2, Tilt 2 Windows Mobile ROM Development

I'm a Noob, relative to the Tilt 2, but have done this to another phone in the past with no issues.
I have a ATT RHOD300 that I want to put the EnergyROM onto. However, I am having a hard time with hardSPL in that it gives a Fatal Error indicating that ActiveSync is not connected (even though it is).
I'm using version V2_00R3 of hardSPL and have also tried going back a version with the same results.
Any suggestions or help would be greatly appreciated. (and I did try searching on this and been searching for 2 plus hours for an answer)
Thanks
SR

Update:
I did some more digging on this and found that I needed to install enablerpinew.cab on the phone to resolve this problem.
Once done, everything worked as pointed out in the instructions on this forum. Those experiencing similar issues do a search of enablerpinew.cab and install it to the phone for a quick fix.

Related

help appreciated!

Hi wondered if anyone could help me. Am new to pocket pcs, just got my hands on an xda2s, have started to get through the different threads and get my head around it. Decided that the first thing to do was to update the rom to the latest 02 rom. Went online, downloaded the update, plugged in the cradle to the computer etc. followed instructions like backing up info, soft reset etc. Clicked update and then an error occured where it could not update the radio rom. The computer message told me to unplug the cradle, perform a soft reset which i did and run the programme. Trying not to panic too much i followed each step and again the same thing has happened. In fact it looks like it has wiped my xda as it does nothing at all now except read serial v2.07. Anyone got any advice about what I can do? I've paid alot of money for a brick at the moment and after day 3 of owning it, I'm not doing too well! Please help if you can!!!!
have you tried the FAQ?
Have you checked the FAQ?
http://wiki.xda-developers.com/index.php?pagename=BA_GettingStarted
Have fun :wink:
I did read through the FAQ. The problem that I have seems to not be the rom that I used, I even tried to use a different rom just so that it would make my xda useale. Nothing seems to be working! anyone else got an idea?

Cant change my rom on my 8125

Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
ecomajor said:
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
Click to expand...
Click to collapse
do you have a G3 or G4?
What are your IPL/SPL?
Which other ROMs have you had installed on this wizard?
ecomajor said:
Hi,
I used to upgrade roms all the time on my 8125 and never had a problem - until a couple of days ago. I tried installed the wm6 "most beautfiul" rom on my ppc and it bricked my phone. After many attempts I finally realized that I needed to install the official cingular 225 rom (available on the site) in order to get my phone to work. Since then I have tried downgrading to button and to wizard love with no success. My ultimate goal is to get to WM6. I have tried unlocking and have read all the threads and followed the directions but I cant switch roms. Can someone please help me with this. I am getting desperate.
thanks
Click to expand...
Click to collapse
So, you start a new thread with the same problem you posted in another thread hoping to get an answer??
My answer to you is the same one I posted to you before --
READ THE STICKY ABOUT UNLOCKING AND FOLLOW IT STEP BY STEP!!
Then -- and ONLY then -- will you be able to flash to a custom ROM.
newbie2 said:
So, you start a new thread with the same problem you posted in another thread hoping to get an answer??
Click to expand...
Click to collapse
Yep, I've replied to ecomajor's various posts in various threads and have basically given up. Very little info each time and having a problem that nobody else that has followed the steps has had.
Sorry ecomajor, don't know what else to tell you that hasn't already been said numerous times.
One Last Try -- Then, I Give UP!!
Read the following post on how to flash ANY Wizard (yes, that includes the 8125) --
http://forum.xda-developers.com/showpost.php?p=1177659&postcount=1
Now, follow the directions in that post WORD FOR WORD and STEP BY STEP. The only reason it wouldn't work is that you're NOT READING and/or NOT FOLLOWING THE INSTRUCTIONS STEP BY STEP.
If you CAN'T read and follow directions, then don't be trying to flash different ROMs to your phone. If you're not willing to do what's necessary to help yourself, then noone else is willing to help you, either. . . especially when your problem has already been replied to with the same information over and over in 2 DIFFERENT THREADS now.
Let me detail you the exact steps I have taken. I have read through those posts, many times so I am certain I took those steps
1)device starts normally goto step 3.6 since unsure if unlocked.
2) read farias thread
3) download buttons rom
4)attempt to downgrade rom - failed
4a)tried 1.08 rom instead of button - failed
4b)tried wizard love- failed
5)download lokiwiz
6)followed all directions -failed - since was not able to downgrade rom.
Obviously these directions are not 100% foolproof - I know that the first time I tried installing WM6, I did not read through all the threads and after much effort I discovered that if I installed the official cingular 225 rom then I could get my ppc back working but since then I have had no luck getting flashing to work. Please tell me what I am doing wrong because noone has had my exact situation. there is no need to act all holier than thou and accuse me of not reading because since I screwed up the first time I have read through all these threads numerous times.
Ok, one more thing to try (shot in the dark, but I have no clue what is happening here)...
On your PC (its running XP, right???), do you have Firewall and/or Antivirus? If so, reboot your pc and don't start anything and then turn off your Antivirus and Firewall programs (I found a couple of threads where people were getting the error 260 when ZoneAlarm is active). Now try flashing the button rom. Don't try doing any other roms, don't try doing lokiwiz, just try to get the button rom on. If that works, then continue on with the steps here:
http://forum.xda-developers.com/showthread.php?t=285435
You might even try booting your computer into safemode and try flashing that way (I doubt activesync would be there, so put the phone in bootloader mode, and if you see USB above the left softkey then you should be able to flash it this way from safemode. Never tried it, but it pretty much eliminates anything that may be on your PC thats causing problems).
If none of that works, then get back to an official stock rom again and report back here with exactly what you did, what you saw, and all. Don't worry about the post being long, because to me, too much info is better than just short posts that don't tell us anything. Also, only update this thread. Forget all the other threads you have stuff going on about this problem.
Final question, I asked this before (and I don't remember if you answered or not)... Have you tried to flash your device from another PC?
And I've attached the ROM Update Utility Readme.doc that describes the error messages and how to fix them.
The weird thing is I never get code 260 with the cingular rom update just with the other roms. I will have to try the disabling all firewalls, antivirus etc at home bc at work there is all sorts of stuff i dont want to mess with. Problem if I do it in safemode is then the activesync driver wont be loaded and it will give me an error for that.
mfrazzz said:
Ok, one more thing to try (shot in the dark, but I have no clue what is happening here)...
On your PC (its running XP, right???), do you have Firewall and/or Antivirus? If so, reboot your pc and don't start anything and then turn off your Antivirus and Firewall programs (I found a couple of threads where people were getting the error 260 when ZoneAlarm is active). Now try flashing the button rom. Don't try doing any other roms, don't try doing lokiwiz, just try to get the button rom on. If that works, then continue on with the steps here:
http://forum.xda-developers.com/showthread.php?t=285435
You might even try booting your computer into safemode and try flashing that way (I doubt activesync would be there, so put the phone in bootloader mode, and if you see USB above the left softkey then you should be able to flash it this way from safemode. Never tried it, but it pretty much eliminates anything that may be on your PC thats causing problems).
If none of that works, then get back to an official stock rom again and report back here with exactly what you did, what you saw, and all. Don't worry about the post being long, because to me, too much info is better than just short posts that don't tell us anything. Also, only update this thread. Forget all the other threads you have stuff going on about this problem.
Final question, I asked this before (and I don't remember if you answered or not)... Have you tried to flash your device from another PC?
Click to expand...
Click to collapse
ecomajor said:
The weird thing is I never get code 260 with the cingular rom update just with the other roms. I will have to try the disabling all firewalls, antivirus etc at home bc at work there is all sorts of stuff i dont want to mess with. Problem if I do it in safemode is then the activesync driver wont be loaded and it will give me an error for that.
Click to expand...
Click to collapse
I've never tried it in safemode so I don't know if that will work or not, it was just an idea as we are grasping at straws here. But if you boot to safemode, and with the phone at the bootloader screen (hold down the camera button while you turn it on to get to the "rainbow" bootloader screen), if it shows USB above the left softkey then the computer and phone are communicating and Activesync does not matter. BTW:You can try the safemode way there at work as you will have no network connectivity in safemode so you don't have to worry about violating security policies.
You still have not answered my one question directly... Have you tried flashing the button rom to your phone on multiple computers? Or have you always done it from the same PC? And are the PC(s) that you are using running Windows XP?
What DOC chip does your device have? G3 or G4?
If you have a G4 then i guess you ruined your bootloader since G4 devices don't have and don't accept 1.xx IPL versions!!
I have tried button from multiple pcs. This time it gets up to 98% on button and then dies and it gives error 302 - update error for the button. This is a problem that I was having before.
Did you read the document I posted?? If you're getting Update Error 302, you're not going to be able to recover with anything other than the stock Cingular ROM.
Chances are that you did indeed ruin the bootloader when you tried using the ShellTool to flash a G3 phone. And I doubt seriously that you'll be able to do a warranty exchange if you can run the stock ROM successfully, so I'm afraid you're stuck now with the stock-shipped ROM.
So you are saying there is no way to fix the bootloader (like flashing it or soething) I was figuring I had screwed something up. I actually had read the document before but thanks for your help. Why is it that you can fix many other issues with the 8125 but not the bootloader?
I'm not saying it CAN'T be done. What I AM saying is that in the year I've been registered and active here, I've not seen any posts/threads about recovering from a bad bootloader. But that doesn't mean that there ISN'T a way to do it.
You might want to do a search of the Wizard section for bootloader error or recovering bootloader to see what might come up.
Good Luck!!

i-mate KJAM stuck on bootloader

Hello everyone,
First - I'm really happy to have found this resource. I had no idea about all the cool things I could do to my phone. Thanks to everybody for all your hard work.
I spent a lot of time reading up with the goal of upgrading to a Windows Mobile 6 ROM. But now I need some help please, because I can't get my phone back!
I determined that my phone is a G4 (IPL/SPL of 2.16.0001). I attempted to load various WM6 Roms (TNT 4.0 Official and XDA Mobile 6), without success (error 300). Eventually, I succeeded in loading Wizard Love 2.26.10.2, and booted into Windows successfully. I then tried to load TNT 4.0 on. It got up to 100%, rebooted - and now I am stuck on the RGB / bootloader screen. Plugging in USB cable gives me the USB txt in the bottom left, but no response from the computer. The various RUU utilities I have tried to restore the phone back to Wizard Love or official iMate ROMs all fail - they can't seem to find the phone.
I would greatly appreciate any help. Thanks you in advance.
Regards,
Nick
Progress!
More research led me to find that WinXP should be able to install a new ROM without ActiveSync - in fact, you need to disable ActiveSync USB connections and end wscecomm.exe via task manager.
These steps allowed me to attempt flashing of a new ROM:
1. Uninstall device from device manager
2. Turn off device completely
3. Disable USB in ActiveSync
4. End process "wscecomm.exe" via Task Manager
5. Plug in phone, windows will detect and install as a Windows CE. This will make wscecomm.exe load again. End this before running the RUU tool
6. Run RUU. When detecting your phone, it will run wscecomm.exe. I kept ending it and crashing the RUU . RUU stops it itself.
7. Finally my phone was detected and I was able to proceed to flashing without an RUU error. Previously, i was getting error 260, 264, 300...
I was greedy and attempted to load XDA Mobile 6. It got to 99% and crashed. I will try and get back to Wizard Love.
If somebody could tell me what I am missing / doing wrong that would be great. To summarise:
- I have been able to install Wizard Love
- I have a G4 i-mate KJAM
- TNT 4.0 has reached 100%. On reboot, I only got boatloader.
- After many hours trying to fix, I finally was able to attempt to flash XDA 6 r2. It reached 99% before crashing
I will now try to put Wizard Love back on, but I really want to run WM 6.0 and am not very concerned about which flavour. Thanks for your help
No...You shouldn't use RUU for upgrading to WM6 because your G4 is not unlocked (You need to pay to unlock a G4, however it is not required if you don't use RUU).
Flash to Wizard Love, then get a copy of ShellTool and use it to flash the nk.nbf inside WM6 RUU.
no worries. I have the same phone and running XDA r2a, so it can be done!
Simply get hold of G4_step_by_step_install_wm6 I think theres a link to rapidshare on this forum, try search. (I will try get the link later on.) Follow the steps and it has shelltool which will extract th OS for and you can then install. Make sure you get the splash screens from XDA thread so you get the full package.
Good luck
G4_step_by_step_install: http://rapidshare.com/files/22275022/G4_step_by_step_install_wm6.rar.html
link: http://www.megaupload.com/?d=VRYOZ4GO
Read this: http://forum.xda-developers.com/showthread.php?t=293480
You need this: ftp://xda:[email protected]/Uploads/WIZARD/Unlocking/ShellTool_bugfixed.zip
G4_step_by_step_install_wm6 will give u step by step guide on what to do.
Thank you
Hey guys - thanks so much, I can't wait to get stuck into it.
You know I spent my whole weekend getting into this stuff and I'm sure I have only just scratched the surface!
I think it's fantastic that so many of you put so much work into this, and then also have time to guide people through the process.
Regarding the FTP links throughout these forums - They never seem to work for me. I get an error 550 - failed to change directory. These are links with usernameassword of xda:xda. The only link that worked had something different, along the lines of xdaupload:xda, can't remember for sure.
What am I doing wrong?
Just get the G4_step_by_step, forget everything else. Its on rapidshare. It has even a WM6 Rom in it so you can even that on your Wizard. But you can install XDA R2a also by following the step by step guide and knowing what to replace. Have you downloaded it? Its about 75MB but well worth every bit of it! You wont need anything else after that.
We learn from each other! Thats why we help others so they help us too
cochumbo said:
Regarding the FTP links throughout these forums - They never seem to work for me. I get an error 550 - failed to change directory. These are links with usernameassword of xda:xda. The only link that worked had something different, along the lines of xdaupload:xda, can't remember for sure.
What am I doing wrong?
Click to expand...
Click to collapse
The forum carried many ROMs before. Micro$oft had some opinion on this and hence the ROMs were all removed. Most of the 550 errors would be due to this.
kernelguy

Error 262 Updating any Custom ROM

I am new to completely flashing a custom ROM. I've been trying to flash a new ROM on my tilt, with the latest AT&T updates(ROM 1.62.502.0 Radio 1.27.14.09). Each time I try to flash a custom ROM I get Error 262 Update Error. The progress bar never gets past 0%. I've tried multiple PCs and tried reinstalling ActiveSync. Am I missing something, or do I have to do something first before being able to flash the new ROM?
Any help is greatly appreciated!
Steve
i suggest u read all the wiki's and stickies regarding flashing a custom rom before taking any action...u obviously havent read it or havent got a good understanding of it which is why ur getting this error...and btw..i also suggest u search for solutions rather than just posting a thread like this which can be answered through a brief search of the forums.
I am about 100% sure you searched, didn't you?
Here, baby boy, let me spoon feed you and you can ask your mommy if she can whipe your drool:
http://www.digwin.com/view/schaps-wm6-pro-roms-update-error-262
bapssystupr3m3 said:
i suggest u read all the wiki's and stickies regarding flashing a custom rom before taking any action...u obviously havent read it or havent got a good understanding of it which is why ur getting this error...and btw..i also suggest u search for solutions rather than just posting a thread like this which can be answered through a brief search of the forums.
Click to expand...
Click to collapse
I have searched the forums over the past week or so. The solutions suggested such as soft reset, hard reset, reinstall activesync, switch USB ports, etc have not done anything. I also came across this thread:
http://forum.xda-developers.com/showthread.php?t=370205
which would suggest that I there is an incompatibility. I was hoping someone could point me in the direction of which radio version etc I would need to update to in order to update to a WM 6.1 ROM.
edit:yes I have run CID unlock.
Steve
AT&T 1.62.502.0 w/ 1.27.14.09 radio should flash fine on any Tilt even without CID unlock, since it's signed by AT&T. While I'm glad to hear your phone is CID unlocked, it's still strongly suggested that you flash HardSPL & Security Unlock your device.
Regarding your current issue, have you:
* Tried another computer to flash from?
* Entered tri-color bootloader mode on your phone prior to flashing? You can find out how to on the wiki.
Hope this helps!
_Alex_ said:
AT&T 1.62.502.0 w/ 1.27.14.09 radio should flash fine on any Tilt even without CID unlock, since it's signed by AT&T. While I'm glad to hear your phone is CID unlocked, it's still strongly suggested that you flash HardSPL & Security Unlock your device.
Regarding your current issue, have you:
* Tried another computer to flash from?
* Entered tri-color bootloader mode on your phone prior to flashing? You can find out how to on the wiki.
Hope this helps!
Click to expand...
Click to collapse
Thanks Alex! Tri-Color mode worked!
Steve
My error 262 fixed
I don't know if this is the best place to put this, but I didn't want to open a new thread.
I too had been getting repeated error 262. And I spent a couple of hours searching for answers, and while there have been many questions raised on this subject, there have been few clear solutions (and certainly none that worked for me).
I have the HTC branded Kaiser installing from Vista. (By the way I am new to this, but as I had such a hard time working this out, I thought I should at least post what worked for me.) I unlocked the CID with pof's Hard-spl v1 tool. Then (as I want to stay with Mobile 6.1) I upgraded the hard spl to v3.28 by JockyW. I then downloaded a number of Roms I wanted to try. That is where the trouble started.
Each ROM I tried would get past the tri-color screen with no problem. Then it would hang at the 0% until finally showing the error 262. A soft reset would reload my previous rom unchanged. I tried many things: removing all USB's, firewall, virus protection, hard reset, reboot windows, every suggestion I could find (and understand).
While the hard spl I had should have worked, I thought I should try version 3.29. When trying to upgrade to that I had a similar problem with error 260 this time. Looking over spl update instructions I realized I had forgotten to uncheck "disable usb connections" in "Activesync" at the proper stage. Once that was unchecked, the new spl loaded. After that I was able to load the cooked roms with no problem.
It appears there was something wrong with the HardSPL v3.28 I was using or in how I installed it. The tricolor screen was showing 3.28. In any case, after I reinstalled a new hard spl (this time 3.29), I had no more error 262.
A bit long-winded, but hopefully this might help someone else.

ATT Tilt 6.1 to 6.5 issues

I have been trying to upgrade to 6.5 for last five hours now but every single flash I tried it always go up to the 0% screen and fails. Does anyone know how can I fix this?
I just did mine this morning
I quickly found you have to unlock the phone 1st. I found software on here called "kaiser-HardSPLv1". I flashed my Tilt with that first, which I guess unlocked it and then flashed the 6.5 update.
It worked perfectly. I sure hope you have the same results.
desiguru said:
I have been trying to upgrade to 6.5 for last five hours now but every single flash I tried it always go up to the 0% screen and fails. Does anyone know how can I fix this?
Click to expand...
Click to collapse
Try reading the "flashing your first ROM" thread first. Then read it again. Then read it again.
You have to unlock the phone first, change SPLs, then you can flash a new ROM. If going to 6.5, make sure you flash a stock HTC ROM first (go to their website to download).
There's several threads and Wikis that explain everything. Half the threads on the board wouldn't be here if people would read!
kaiser SPL does it
I had some similar issues related to connectivity. kaiser-HardSPLv1 is def the way to go and reading all the instructions thoroughly is very much required; especially the one where it asks if you're phone is connected.
I did my recent flashing via Windows 7 RC 1, which I thought would be an issue. I had to reboot my computer after each flash step to regain connectivity. Using Windows Mobile Center, I simply waited for the check mark, or you can open "My Computer" and find your device there. Worked great! Love it!!
Another alternative step is to sync it up with a fresh copy of Win XP, on a spare laptop, if you have one.

Categories

Resources