I just got my brother's MDA (mine got worn out), and he had upgraded to a TNT WM6 build (not sure which one). I would like to either downgrade back to OEM T-mobile, or try another of the WM6 builds.
The problem comes when I try to run RUU, with the T-mobile version, it gives me an error and wants me to start over, with the SNN 3.1 upgrade, it just shuts down RUU and with both errors it give me the tri colored screen. When I remove the battery and restart, it loads normally.
I have a G3 wizard, IPL/SPL: 2.26, I'm running Vista on my pc, and I have the latest Windows Mobile Device Center. Also the phone is cid unlocked from when my brother upgraded. This is driving me nuts. I am relatively new to the whole rom flashing world, so any thoughts would be appreciated.
As a side note, I also can't get Wizard Service Tools to work, it won't detect my phone, so if that's part of whatever suggestion might be made, I can't really use that.
Thanks.
have you tried flashing from bootloader?
Camera/reset combinaion?
the idea is that you put it into bootloader first, then run the ruu.
Simple answer to all of your problems is Vista,its still not compatible and has many problems.Do it on WinXP,there won't be any problems and its highly recommended.
Secondly,WST_4.2.2 will not work in Bootloaders,it must be run on a working OS.
Agian...
And again, And again, and again...
Why is a thread saying that is a proved method to flash by vista?
Which version of VIsta do you have ?
see this tutorial i have written for flashing RUU in Vista : http://forum.xda-developers.com/showthread.php?t=428469
Hey ather!!!
ather90 said:
Which version of VIsta do you have ?
see this tutorial i have written for flashing RUU in Vista : http://forum.xda-developers.com/showthread.php?t=428469
Click to expand...
Click to collapse
Is there a special version for vista that works? maybe changing the thread name especifying the Version could helps? wich is it? home basic? Bussines? Ultimate?
lol, i meant which Bit do you have, is it a 32-Bit version or a 64-Bit version ?, if its 64, the above tutorial will work...but you have to find the 64-bit version drivers
hi, I've updated a rom before but never on vista 64 where can I find this driver?
64-Bit Drivers :
http://mahmood1.com/Documents/64bit.rar
Notes :
1. YOUR DEVICE MUST BE IN BOOTLOADER BEFORE CONNECTING IT TO THE PC
2. If you are running Windows Vista 64-bit, then driver signing verification is on. In order to turn it off, and, thus, load this driver, you have to reboot the machine and turn driver signing verification off.
When the OS starts to load, hit the F8 key. That will bring up the boot options screen. The "Disable Driver Signing Verification" choice is towards the bottom of the list.
3. if you are running SP1 on your system...updating these drivers will cause RUU to crash when you try to do an upgrade.
4. If you get access denied, try closing your AV and disabling your Firewall
Hope this helps
Related
Upgrade OS pocket pc (RUU file problem how to solve ) in Windows Vista
First of all, connect your device when it`s in bootloader.
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
then, kill wmdc.exe with any taskmanager
You are Ready. run ruu or connect MTTY. I guess that vista default driver uses another port, not WCEUSBSH001, that`s why we have to use the old driver.
http://mahmood1.com/Documents/USBAS.rar
http://mahmood1.com/Documents/64bit.rar
Best reguards to mahmood
NetrunnerAT said:
First of all, connect your device when it`s in bootloader.
Click to expand...
Click to collapse
done.
NetrunnerAT said:
next, open Windows Mobile Device Center and in connection settings uncheck Allou USB Connections.
Click to expand...
Click to collapse
done.
NetrunnerAT said:
next, goto contol panel-administrative tools-services and start windows mobile device connectivity and windows mobile device 2003 connectivity
Click to expand...
Click to collapse
they were already running
NetrunnerAT said:
next, goto device manager and find your device and update the driver to the one from AS 4, i attached it, wceusbsh.inf.
Click to expand...
Click to collapse
in the 64bit.rar there are drivers in the ruu-work-64bit folder and in the wce.zip. i tried both for my vista x64 system.
NetrunnerAT said:
then, kill wmdc.exe with any taskmanager
Click to expand...
Click to collapse
i also killed the mobsync.exe
NetrunnerAT said:
You are Ready. run ruu or connect MTTY.
Click to expand...
Click to collapse
the ruu simply crashes while trying to connect to the device. luckily the flash didn't start yet.
Not that you need this in pictures, but someone may:
http://www.modaco.com/index.php?showtopic=252977&st=0&gopid=814012&#entry814012
Anyways, I've got this fix working for the NVID ROM, but it won't work for other RUU-based upgrades, such as the one from PDAMobiz WM6 1.0. Perhaps there are different versions of the RUU utility that require or use different components.
Something else that is odd is that the drivers packaged in the "64 bit" rar are the same ones packaged in the VistaRUU.zip found in the Modaco link above, and which work on my 32-bit OS. So, they may not be 64-bit drivers at all.
Yeah I live in New Zealand and I think the 700wx here are different somehow. For example I don't think mine has a bootloader period.. I tried all 400 ways of getting it into bootloader and all I get is a reset back to normal screen no tricolour.
Weird but unless I can get it into bootloader first I don't think its going to get anywhere. Which my palm 700wx just doesn't have I think.
i managed to do it with vmware on vista. tried all these methods but the programs crashes all the time, luckily not frying my 818pro as well!
I have the same experience. The NVID RUU works, but al others don't. By the way, the NVID also work with only the "old" drivers installed, not dis-allowing USB connection, not starting in bootloader and not killing wmdc.exe.
I don't know for sure, I noticed the RUU Utility version is newer. But when I just switch the nb.nsk file, I get an error, or it crashes just like before. Can it has something to do with the fact that the NVID RUU updates the SPL as well?
floepie said:
Not that you need this in pictures, but someone may:
http://www.modaco.com/index.php?showtopic=252977&st=0&gopid=814012&#entry814012
Anyways, I've got this fix working for the NVID ROM, but it won't work for other RUU-based upgrades, such as the one from PDAMobiz WM6 1.0. Perhaps there are different versions of the RUU utility that require or use different components.
Something else that is odd is that the drivers packaged in the "64 bit" rar are the same ones packaged in the VistaRUU.zip found in the Modaco link above, and which work on my 32-bit OS. So, they may not be 64-bit drivers at all.
Click to expand...
Click to collapse
Try running command prompt as Admin and type
bcdedit /set nointegritychecks on
Then try again to install the 64 bit driver. It should work
I have just found the answer for Prime2007, i have a telecom treo 700wx and the previous codes for the bootloader didnt work for me either however if you go into your dailpad and press ##8778# your phone will reboot into bootloader also there is not colored strips just the treo logo with some numbers at the top.
If you want to exit without making changes you will have to pull out your battery
Unfortunally this doesn't work, as mentioned, with things such as Radio ROM update only...
If anyone finds out how to make it work for those I'd be greatly appreciative.
hey guys .. i follows all your step . but i still cant run the ruu sucessfull .. help please.. thanks
completed the tutorial exactly, and continued taking the same problem.
I get the same error. Help please.
Do you have a G3 or a G4 device? (G3 seems to work under Vista, G4s do not.)
l3v5y said:
Do you have a G3 or a G4 device? (G3 seems to work under Vista, G4s do not.)
Click to expand...
Click to collapse
Is G4 my prophet.
No have a solution?a new utility updater for Vista is posible?
Thanks.
Hi Guys,
Glad to see WM6 on the Tornado...
Pulled my Cingular 2125 out of the bin and trying to get it upto WM6.
The problem I'm having is that I need to SuperCID it but SPVServices isn't working.
I get the "ALL OK" RAPI init was Successful when I run SPVServices.
Then I click the "CID Tool (Alpha) Link" but it only displays a blank screen.
I have successfully App-Unlocked and installed the Certs.cab
Any help would be appreciated.
What OS no ur PC are you using? FYI, it must be done on XP
OS & IE Versions...
Sorry, forgot to mention...
Windows XP, IE 7. Thought there might be an issue with IE7 so I uninstalled it and tried again with IE 6. Same results.
Try it on other computer ?
Gonna try on my work PC tomorrow (or actually later today).
Just wondered if others had experienced this..
Odd, never heard of a blank screen issue, most errors are saying that it can't write the to the correct memory area or it just wont run at all under vista..
Phil
[EDIT: Good to see you about again kyphur ]
try to supercid with lokiwiz (wizard sim unlock and supercid tool). it works on tornados too
before this make sure that the phone is fully app-unlocked.
ps: skip the enablerapi.cab step
Ah yes, LokWiz my old friend... Wizard was my second HTC Device (Blue Angel being my first).
I used SDA_ApplicationUnlock.exe, is there a sure-fire way to confirm that my Tornado is App-Unlocked?
Success!!
Go figure, worked right off the bat on my work PC, that's just not fair!
Well, thanks you guys have really got your stuff together here.
We'll see how my 12 year old daughter likes WM6 SmartPhone Edition.
i JUST BOUGHT A NEW O2 EXEC, AND TRIED MY BEST TO UNLOCK cid AND SIM, O2 APPARENTLY SHIP THEM UNLOCKED, SO I TRIED AND IT WAS. TRIED TO cid UNLOCK BUT NO LUCK KEPT GIVING ERRORS. SO I BEGUN THE INSTALL CROSSBOW LATEST, AND IT THEN WAS STUCK ON O2 SPLASH SCREEN, TRIED TO REFLASH WITH THINGONASTRING, NOW ITS STUCK ON BOOTLOADER, SAYING V2.01 AT BOTTOM AND SERIAL OR USB (WHEN CONNECTED), I HAVE LOOKED AND TRIED ALL OPTIONS, I TRIED UNI_EXTBOOTLOADER, AND THE OTHER ONE WHEN I WAS STUCK IN SPLASH SCREEN. NOTHING IS WORKING, THEN I TRIED TO SEE IF I COULD INSTALL OFF CD WITH O2 EXEC, BUT CANNOT FIND RUU. THE ONLY WAY I CAN NOW GET INTO BOOTLOADER IS FIRAT ATTACHING THE USB CABLE THEN BOOTLOADING, I CANNOT DO IT WIHOUT USB CONNECTED, BUT IF I TOOK THE USB OUT AFTER I HAVE GOT IT INTO BOOTLOADER, IT STILL STAYS ON. WHEN I ALSO PRESS THE RESET WHILST USB CONNECTED, THE LIGHT ON O2 EXEC FLASHES RED EACH TIME PRESSED?
ANY HELP WOULD BE GRATEFULL.... COULD THIS BE VISTA??? AS THATS THE OS I USE.
Please help, this is supposed to be a christmas present... i just couldn't help myself!!!!
vistar said:
Please help, this is supposed to be a christmas present... i just couldn't help myself!!!!
Click to expand...
Click to collapse
Hi vistar,
Hopefully, you will have it sorted out by Christmas!
Yes, it is Vista problem and you need to change the USB Vista driver in your PC to XP driver.
I don't mean changing the Windows Mobile Device Center to Active Sync 4.5!
But the USB drivers. Look here:
http://forum.xda-developers.com/showthread.php?t=313001
http://forum.xda-developers.com/showthread.php?t=291723
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
I believe that the first post should solve your problem. If not try the others. Basically, in Device Manager of your PC, the USB driver should be the old XP driver dated 2004!
Any other year won't do you good!
Merry Christmas!
Happy New Year!
KOR!
It is highly recommended NOT to use Vista ... even with the proposed driver patch.
I have developed a Radio ROM issue because of this: http://forum.xda-developers.com/showthread.php?t=347375
If you are using Vista, it is highly recommended for you to use Virtualisation and install XP.
I have been using XP under VMware forever without problems as far as flashing my Qtek is concerned ... until my Vista mis-adventure that is. I know that VMWare is not free, but you may want to give http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx a try.
I flash my two Universal at least once a day under Vista with no problems at all.
Flashing Radio, CE ROM and ExtROM with Vista hasn't created any problem for me.
Vista like XP automatically install latest update from Microsoft site, this update also includes drivers too.
Just before flashing make sure that your old 2004 driver is not changed to the latest 2006 or 2007 driver!
That's all folks,
KOR!
will try the threads above thanks, i have tried in vista, and also i use vmware too, with xp pro spâ. which seems to work better but get error ăđă, radio update error, i think i have wiped the radio??? as when the first screen comes up it says:
from,
Radio:
EXT Rom:
Bla bla:
to:
Radio: 2.?.??
EXT Rom: 2.2.??
Bla bla: 2.2.??
I cant remember what numbers came up, but it was blank at top and version numbers at bottom.
any help would be grateful
ok i got it to work , through vmware, i ran PsiDOC_WM5_20041_Taster, which worked think its WM̀ still but its back on, I want WM̉ though, i'll try again.. some advice wouldn't go a miss. thanks.
Note: If anyone has problems blame vista..... Good OS, Bad PDA Partner...
ok every rom i try fails with the following: Error 114, Radio Rom Upgrade error.
why is this??? i have looked through the wiki and forum, people have had this problem before, but no answers.
I have this when WM5 loads up,
1.09.00
42.42.p8
2.00.41 WWE
and bootloader v2.01 (G4)
just incase this info is needed.
thanks, i will leave it on WM5 till an answer is given, preferably before christmas...lol.
thanks guys for at least helping me.
vistar said:
thanks, i will leave it on WM5 till an answer is given, preferably before christmas...lol.
thanks guys for at least helping me.
Click to expand...
Click to collapse
If you have tried all the links I have given, you could have easily upgraded the ROM to Windows Mobile 6.
Read carefully, my above post #3.
Did you know that you could just flash the CE ROM (Main ROM), if the Radio is not flashing.
KOR!
KOR support center !!!
How do i Flash that alone? do i just remove the radio file from the WM6 folder and run RUU again??? just to confirm...
Thanks M8 much appreciated.
vistar said:
How do i Flash that alone? do i just remove the radio file from the WM6 folder and run RUU again??? just to confirm...
Thanks M8 much appreciated.
Click to expand...
Click to collapse
Read the four links, I have given you.
1. nk.nbf (CE ROM - Main ROM)
2. ms_.nbf (Extended ROM - Storage ROM)
3. radio_.nbf (Radio ROM)
If the ROM is in .exe format, than excute the ROM without hooking your universal to the PC. In the temporary folder, you will find all the files.
Read,
KOR!
sorry what i meant was how do i flash the files to the device??? i have all the files ready..
do i remove radio from folder then execute RRU? or do i use a different way?
Thanks for your support KOR!!!
the later worked perfectly on my G4 device, i ran the update without the device attached, put into bootloader, and found all files in temp directory, then removed the radio file. connected the bootloaded device, then ran the update, it worked straight away, only in xp/vmware though.
Thankyou..... I really mean that KOR..
vistar said:
Thanks for your support KOR!!!
the later worked perfectly on my G4 device, i ran the update without the device attached, put into bootloader, and found all files in temp directory, then removed the radio file. connected the bootloaded device, then ran the update, it worked straight away, only in xp/vmware though.
Thankyou..... I really mean that KOR..
Click to expand...
Click to collapse
Hi Vistar,
You are welcome. If you download the drivers from the first link in post #3, then you can use Vista without any problems to flash your device.
Just make sure that the driver is dated 2004 before flashing the device. Check the driver for the Portable Devices ->USB Disk in the Device Manager of your PC.
Best Regards,
KOR!
BTW, I did reply to your PM.
King of Rapture™ said:
I flash my two Universal at least once a day under Vista with no problems at all.
Flashing Radio, CE ROM and ExtROM with Vista hasn't created any problem for me.
Vista like XP automatically install latest update from Microsoft site, this update also includes drivers too.
Just before flashing make sure that your old 2004 driver is not changed to the latest 2006 or 2007 driver!
That's all folks,
KOR!
Click to expand...
Click to collapse
Perhaps that's because both your Unis are G3 - and mine is a G4.
I am very new to flashing ROM's on phone, i have read thru most of the related threads and followed the steps with no sucess. Appreciate if someone can help me with detailed steps
Mobile - T-Mobile HTC Touch Pro2
OS - Win 6.5 (T-Mobile ROM)
RHOD210 32M MI-BC
SPL-0.87.0000
PC Details - WinXP with Active Synch
Queries on HARDSPL
Downloaded CDMA HARDSPL (RhodiumW-HardSPL_V1_10R3) and tried to do a automatic flash (while it is starting the application) the following message is displayed on the phone "This package is not intended for your device type, high chance of bricking exiting now" clicked ok on the phone and tried to continue (also during this time the Active sync disconnects and does not connect later, i have to unplug the usb) the install and it has been at 0% for 2-3 min and i get the error 262. I tried running the HARSPL in admin mode but still no luck
After spending some time reading the threads i decided to do the SSPL Manal "SSPL-Manual-RhodiumV1_10", i followed the instructions and copied the exe to the phone (in the windows explorer>mobile folder) but i am unable to run the exe on the phone (don't know what i am doing wrong).
1. Am i using the correct HARDSPL? Please send me the correct steps and point me to correct HardSPL.
2. If the Active Synch is disconnected, will the Hardspl still work
3. I have also read about Task29, do i have to run this after hardspl
vuday_raj said:
I am very new to flashing ROM's on phone, i have read thru most of the related threads and followed the steps with no sucess. Appreciate if someone can help me with detailed steps
Mobile - T-Mobile HTC Touch Pro2
OS - Win 6.5 (T-Mobile ROM)
RHOD210 32M MI-BC
SPL-0.87.0000
PC Details - WinXP with Active Synch
Queries on HARDSPL
Downloaded CDMA HARDSPL (RhodiumW-HardSPL_V1_10R3) and tried to do a automatic flash (while it is starting the application) the following message is displayed on the phone "This package is not intended for your device type, high chance of bricking exiting now" clicked ok on the phone and tried to continue (also during this time the Active sync disconnects and does not connect later, i have to unplug the usb) the install and it has been at 0% for 2-3 min and i get the error 262. I tried running the HARSPL in admin mode but still no luck
After spending some time reading the threads i decided to do the SSPL Manal "SSPL-Manual-RhodiumV1_10", i followed the instructions and copied the exe to the phone (in the windows explorer>mobile folder) but i am unable to run the exe on the phone (don't know what i am doing wrong).
1. Am i using the correct HARDSPL? Please send me the correct steps and point me to correct HardSPL.
2. If the Active Synch is disconnected, will the Hardspl still work
3. I have also read about Task29, do i have to run this after hardspl
Click to expand...
Click to collapse
1. no, you have a RHOD210, so you need this one: http://forum.xda-developers.com/showthread.php?t=550131
2. activesync is needed when you start the Hard-SPL exe but after that at one point it will go off, that's normal.
3. not really, except if you flash a ROM and you have weird issues. then it can be helpful to reformat the OS+data area.
cmonex said:
1. no, you have a RHOD210, so you need this one: http://forum.xda-developers.com/showthread.php?t=550131
2. activesync is needed when you start the Hard-SPL exe but after that at one point it will go off, that's normal.
3. not really, except if you flash a ROM and you have weird issues. then it can be helpful to reformat the OS+data area.
Click to expand...
Click to collapse
Thanks for the suggestion, it worked like a dream but when i tried to install the custom ROM (after installing the ROM "Energy.RHODIUM.28244.Sense2.5.Dec.21.Christmas.Edition") it rebooted but got a grey screen, tried installing the same ROM couple of times and hard rebooted couple of time but no success. I then installed a ROM "Energy.RHODIUM.23138.Sense2.5.Sep.13" which worked.
1. My question is how to find which compatible custom ROM's?
2. After the HardSPl the current SPL 0.85 olinex, but i have read some threads where the current version is 1.00 olinex. Do i have to install this SPL on the phone? or the current 0.85 will work? are the latest custom ROM's available need a specific SPL version?
vuday_raj said:
Thanks for the suggestion, it worked like a dream but when i tried to install the custom ROM (after installing the ROM "Energy.RHODIUM.28244.Sense2.5.Dec.21.Christmas.Edition") it rebooted but got a grey screen, tried installing the same ROM couple of times and hard rebooted couple of time but no success. I then installed a ROM "Energy.RHODIUM.23138.Sense2.5.Sep.13" which worked.
1. My question is how to find which compatible custom ROM's?
2. After the HardSPl the current SPL 0.85 olinex, but i have read some threads where the current version is 1.00 olinex. Do i have to install this SPL on the phone? or the current 0.85 will work? are the latest custom ROM's available need a specific SPL version?
Click to expand...
Click to collapse
1) GSM roms will work, CDMA ones won't.
2) no, 1.00 is the CDMA one. 0.85 is GSM one.
(Q) Cannot HardSPL T-mobile HTC Touch pro2
Guys I need help here am using window 7 home premium, I have windo
Mobile - T-Mobile HTC Touch Pro2
OS - Win 6.5 (T-Mobile ROM)
RHOD210 32M MI-BC
SPL-0.87.0000
PC Details - win 7 with WMDC
But keep getting an error message that server appears to be down...can anyone tell me how to get pass this server problem ?
kollins said:
Guys I need help here am using window 7 home premium, I have windo
Mobile - T-Mobile HTC Touch Pro2
OS - Win 6.5 (T-Mobile ROM)
RHOD210 32M MI-BC
SPL-0.87.0000
PC Details - win 7 with WMDC
But keep getting an error message that server appears to be down...can anyone tell me how to get pass this server problem ?
Click to expand...
Click to collapse
Try to disable your anti-virus, see if that works
x12CHRIS18x said:
Try to disable your anti-virus, see if that works
Click to expand...
Click to collapse
I did disable the antivirus but I keep getting the same error message..
kollins said:
I did disable the antivirus but I keep getting the same error message..
Click to expand...
Click to collapse
download this.....http://forum.xda-developers.com/showthread.php?t=578660... then try it again
Good day.
I have an HTC Arrive on Sprint (CDMA, of course) that I'm trying to update to WP7.8. Specifically, I'm trying to use the HTC Arrive 7.8 Sianto Edition AL ROM.
I used this guide to downgrade the SPL to v.1.25... and the MID number is correct.. I then open up the downloaded ROM folder, and click on ROMUpdateUtility. It skips most of the steps that the user guide for the DFT, but I suppose I could attribute that to it being in the ROM folder itself and selection of the ROM being unnecessary.
Whenever I execute the ROMUpdateUtility file, after I have set the phone into bootloader mode (volume down + power button), it skips right to the flashing process. However, it then sits at 0% for a few minutes and exits with error code 262, which, according to documentation:
ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
Click to expand...
Click to collapse
The phone itself still works; it's not a brick. What exactly is going on here? How do I flash it correctly? If this is in the wrong section, just let me know.
Hello. I just recently flashed my Arrive to Wp7.8 with no problems. I chose the LEAD rom though. May I ask why you want the Sianto Edition? I have seen in the thread for that rom that a few people are having issues installing it. I flashed the LEAD rom with no issues and it is great.
You said that you did downgrade your SPL, did you also install both RSPL and HSPL? I don't know if it makes any difference, but as soon as the HSPL installed and the phone rebooted into the boot loader, I began the installation of the new rom. When you attempt to flash it are you seeing "Cotulla" on you phones boot loader? Also be sure that the bottom portion says USB and not Serial. If it says Serial, unplug the phone and plug it back in, it should then turn to USB and you can proceed to flashing.
Hope this helps
Edit - also, are you running the RUU as Admin? You must Run As Administrator when flashing. Right click the EXE and Run As Administrator
x_orange90_x said:
Hello. I just recently flashed my Arrive to Wp7.8 with no problems. I chose the LEAD rom though. May I ask why you want the Sianto Edition? I have seen in the thread for that rom that a few people are having issues installing it. I flashed the LEAD rom with no issues and it is great.
You said that you did downgrade your SPL, did you also install both RSPL and HSPL? I don't know if it makes any difference, but as soon as the HSPL installed and the phone rebooted into the boot loader, I began the installation of the new rom. When you attempt to flash it are you seeing "Cotulla" on you phones boot loader? Also be sure that the bottom portion says USB and not Serial. If it says Serial, unplug the phone and plug it back in, it should then turn to USB and you can proceed to flashing.
Hope this helps
Edit - also, are you running the RUU as Admin? You must Run As Administrator when flashing. Right click the EXE and Run As Administrator
Click to expand...
Click to collapse
Yeah, some idiot (who shall remain nameless because my ego is fragile) didn't do HSPL after RSPL. Installed fine after that.
Sorry to bother you guys :silly:
Glad to here you got it installed!