Vogue 19588 Kitchen

[kgphat25]

Originally Posted by boggsie

Can you elaborate? I am not sure that I follow you. I don't doubt what you have said, I'm just not sure that I understand it.

Best regards,
-boggsie

PPST_080407_7500_SPCS_2.03.sa.CAB
PPST_080516_7500_SPCS_2.04.sa.CAB

Oh awesome you have the actual cab, lol, this would probably be better than my bootleg one .

Well what I basically did was break apart the Sprint ROM using the Vogue Kitchen tools, then went into the \OEM\OEMDrivers folder, opened the Vogue_Drivers.rar from the PPC Kitchen, and replaced the dlls in the archive with the ones from the Sprint ROM. And just cooked my ROM.

The new PPST I made was from the PPST cab file in the Sprint exe itself, that's were I got the 4.20 version of PPST.exe, but it wasn't complete (I dunno why) and it reset my PRL completely and I was stuck on roaming, until I checked somethings and fixed the problem. The new cab I made is fine now, I tested it twice after re-flashing and my PRL is still 60613, and the phone isn't stuck on roaming anymore.

I also added the d3dm_ati.dll drivers and the new ddi drivers along with ahi2dati.dll, and libgles_cm.dll to the drivers archive, and then used the registry in the ROM to local hook the ATI drivers instead of the htc_d3dm.dll but my phone wouldn't show the OS (got past my splash screens and got the WinMo startup sound but screen was blank), lol my try at incorporating the 3D drivers .

Edit: Actually the PPST_080516_7500_SPCS_2.04.sa.CAB that you posted still has the 4.19 version of the exe, I dunno if that matters though since it has more things in it as well . Here is the cab I made, don't mind the name, I just kept the similar to the PPST_080407_7500_SPCS_2.03.

[boggsie]

Originally Posted by kgphat25

Oh awesome you have the actual cab, lol, this would probably be better than my bootleg one .

Well what I basically did was break apart the Sprint ROM using the Vogue Kitchen tools, then went into the \OEM\OEMDrivers folder, opened the Vogue_Drivers.rar from the PPC Kitchen, and replaced the dlls in the archive with the ones from the Sprint ROM. And just cooked my ROM.

I should have been so smart.

I broke apart the Sprint 3.02, the Sprint 3.03 and the Altell 3.04 into separate folders and then hand-assembled a most current (or at least I thought) OEMDrivers directory. Then I went through the process of assembling a Vogue_Drivers.rar that matched, as best as I could manage, the PPCKitchen Vogue_Drivers.rar. The results were ... um ... less than what I had hoped to accomplish. I use wireless bluetooth for phone calls and that is the first thing that I tested and it didn't work quite right, so I gave up.

Your method would seem to be much less problematic.

Originally Posted by kgphat25

The new PPST I made was from the PPST cab file in the Sprint exe itself, that's were I got the 4.20 version of PPST.exe, but it wasn't complete (I dunno why) and it reset my PRL completely and I was stuck on roaming, until I checked somethings and fixed the problem. The new cab I made is fine now, I tested it twice after re-flashing and my PRL is still 60613, and the phone isn't stuck on roaming anymore.

I also added the d3dm_ati.dll drivers and the new ddi drivers along with ahi2dati.dll, and libgles_cm.dll to the drivers archive, and then used the registry in the ROM to local hook the ATI drivers instead of the htc_d3dm.dll but my phone wouldn't show the OS (got past my splash screens and got the WinMo startup sound but screen was blank), lol my try at incorporating the 3D drivers .

Edit: Actually the PPST_080516_7500_SPCS_2.04.sa.CAB that you posted still has the 4.19 version of the exe, I dunno if that matters though since it has more things in it as well . Here is the cab I made, don't mind the name, I just kept the similar to the PPST_080407_7500_SPCS_2.03.

This _IS_ very interesting. The PPST_080516_7500_SPCS_2.04.sa.CAB is from the decompiled / decomposed 3.03 sprint rom ... but NOT from the post-flash and post-customization Sprint Vogue phone. I wonder if something occurs that would patch the file? How else could we account for the rev'd PPST.exe that you pulled from the phone?

Best regards,
-boggsie

EDIT: I would have thank'd you, too - but my thanks button got taken away for a day or so. I think, when you thank others too much in a given time-period, there is a script that takes away the thanks button.

[kgphat25]

Originally Posted by boggsie

EDIT: I would have thank'd you, too - but my thanks button got taken away for a day or so. I think, when you thank others too much in a given time-period, there is a script that takes away the thanks button.

Lol its no prob.

[Kreigz]

This stuff with the pst cab file sounds pretty interesting ... anyone try it out on a XV6900?

[fredcatsmommy]

Originally Posted by Kreigz

This stuff with the pst cab file sounds pretty interesting ... anyone try it out on a XV6900?

I've been told absolutely DO NOT install the ppst cab on the xv6900. I just flashed back to the 19209 build; 19588 just wouldn't get a lock but once or twice. Way too unreliable.

[myn]

Originally Posted by kgphat25

Oh awesome you have the actual cab, lol, this would probably be better than my bootleg one .

Well what I basically did was break apart the Sprint ROM using the Vogue Kitchen tools, then went into the \OEM\OEMDrivers folder, opened the Vogue_Drivers.rar from the PPC Kitchen, and replaced the dlls in the archive with the ones from the Sprint ROM. And just cooked my ROM.

The new PPST I made was from the PPST cab file in the Sprint exe itself, that's were I got the 4.20 version of PPST.exe, but it wasn't complete (I dunno why) and it reset my PRL completely and I was stuck on roaming, until I checked somethings and fixed the problem. The new cab I made is fine now, I tested it twice after re-flashing and my PRL is still 60613, and the phone isn't stuck on roaming anymore.

I also added the d3dm_ati.dll drivers and the new ddi drivers along with ahi2dati.dll, and libgles_cm.dll to the drivers archive, and then used the registry in the ROM to local hook the ATI drivers instead of the htc_d3dm.dll but my phone wouldn't show the OS (got past my splash screens and got the WinMo startup sound but screen was blank), lol my try at incorporating the 3D drivers .

Edit: Actually the PPST_080516_7500_SPCS_2.04.sa.CAB that you posted still has the 4.19 version of the exe, I dunno if that matters though since it has more things in it as well . Here is the cab I made, don't mind the name, I just kept the similar to the PPST_080407_7500_SPCS_2.03.

Just ran your cab. Then ran ppst.exe. I didn't receive the error "Backup EFS Failed" as I did before and it actually appears that satellite locks are signigantly faster. Time will tell if my problem of not locking after about a day will occur but I will report back tommorow.

Thanks

PS. I'd really love to see those ATI drivers instituted!

[Kreigz]

myn,

What network is your phone on? Verizon ... Sprint ... ?

Originally Posted by myn

Just ran your cab. Then ran ppst.exe. I didn't receive the error "Backup EFS Failed" as I did before and it actually appears that satellite locks are signigantly faster. Time will tell if my problem of not locking after about a day will occur but I will report back tommorow.

Thanks

PS. I'd really love to see those ATI drivers instituted!

[myn]

Sprint

[kgphat25]

Originally Posted by Kreigz

This stuff with the pst cab file sounds pretty interesting ... anyone try it out on a XV6900?

To put it simply, you should not be running other carriers PPST .

Originally Posted by myn

Just ran your cab. Then ran ppst.exe. I didn't receive the error "Backup EFS Failed" as I did before and it actually appears that satellite locks are signigantly faster. Time will tell if my problem of not locking after about a day will occur but I will report back tommorow.

Thanks

PS. I'd really love to see those ATI drivers instituted!

No prob, but about the ATI drivers, I've been researching around and I highly doubt that we will see fully working drivers on the Vogue (don't quote me pls I'm not an expert at all, very far from it ).

I only say that because all the driver dlls that we have are chip specific to the Diamond (Qualcomm MSM7201A) and the Kaiser (Qualcomm MSM7200), both are variations of the 7200 chipset, I guess. And since both the Titan and the Vogue are 7500, the chipset difference could be substantial enough that it cant be done, even though they are both powered by ATI. So unless HTC releases something on their own I dont think it will happen (doesn't matter to me though, I'm getting the Diamond then the Touch Pro when they are out, lol), but I do still hope that someone can come up with a way to get the drivers to work.

[brunes]

Originally Posted by kgphat25

To put it simply, you should not be running other carriers PPST .



No prob, but about the ATI drivers, I've been researching around and I highly doubt that we will see fully working drivers on the Vogue (don't quote me pls I'm not an expert at all, very far from it ).

I only say that because all the driver dlls that we have are chip specific to the Diamond (Qualcomm MSM7201A) and the Kaiser (Qualcomm MSM7200), both are variations of the 7200 chipset, I guess. And since both the Titan and the Vogue are 7500, the chipset difference could be substantial enough that it cant be done, even though they are both powered by ATI. So unless HTC releases something on their own I dont think it will happen (doesn't matter to me though, I'm getting the Diamond then the Touch Pro when they are out, lol), but I do still hope that someone can come up with a way to get the drivers to work.

If this is true how come NFSFan's ROMs have them?

http://forum.ppcgeeks.com/showthread.php?t=29399

Is there any way to get the ATI drivers into the kitchen?