Verizon Touch Pro2 MR2 Update includes Sense 2.5

[kgb247]

Originally Posted by CA3SAR

It feels alot snappier, quickest sense 2.5 ive ever used. Can anyone post a working taskbar?

check post #43

http://forum.ppcgeeks.com/showpost.p...1&postcount=43

[CA3SAR]

Sorry working taskbar icons or skin

[PPCFreak]

Anyone have transparent taskbar yet? Missing that already (want the top and bottom curtains transparent as well).

[jakdillard]

Quick tut on how to break this ROM down first off the ROM may not be booting when unlocked due to the SPL so to get around this find a nbh decompiler that breaks the ROM down into its part IE Radio.nb SPL.nb Splash.nb and OS.nb once you have these parts recompile the ROM by not adding anything other then the OS.nb rebuild the nbh then flash

[CA3SAR]

Transparent slider and no curtains

[Mr. X]

Originally Posted by jakdillard

Quick tut on how to break this ROM down first off the ROM may not be booting when unlocked due to the SPL so to get around this find a nbh decompiler that breaks the ROM down into its part IE Radio.nb SPL.nb Splash.nb and OS.nb once you have these parts recompile the ROM by not adding anything other then the OS.nb rebuild the nbh then flash

Uhhh if the OS fails to boot because the booting drivers reject the HSPL, then how does just extracting the os and flashing it going to fix this at all?

You have two options here, it seems the OS has a driver looking for an EXT rom that the HSPL is not set up for. so you can relock which i gues has been reported to work or dump the rom and remove OEM_FLASHDRV.DLL and OEM_FLASHDRV_1.DLL from the oem xip and the boot registry. they are un needed and this will fix the no boot issue.

[CA3SAR]

anyone have the reg edit for setting to point directly to all settings from the start menu?

[jakdillard]

Originally Posted by Mr. X

Uhhh if the OS fails to boot because the booting drivers reject the HSPL, then how does just extracting the os and flashing it going to fix this at all?

You have two options here, it seems the OS has a driver looking for an EXT rom that the HSPL is not set up for. so you can relock which i gues has been reported to work or dump the rom and remove OEM_FLASHDRV.DLL and OEM_FLASHDRV_1.DLL from the oem xip and the boot registry. they are un needed and this will fix the no boot issue.

I posted what worked for me

[jakdillard]

Originally Posted by Mr. X

Uhhh if the OS fails to boot because the booting drivers reject the HSPL, then how does just extracting the os and flashing it going to fix this at all?

You have two options here, it seems the OS has a driver looking for an EXT rom that the HSPL is not set up for. so you can relock which i gues has been reported to work or dump the rom and remove OEM_FLASHDRV.DLL and OEM_FLASHDRV_1.DLL from the oem xip and the boot registry. they are un needed and this will fix the no boot issue.

Sprint mr1 comes with that same driver in the XIP and so does the Cellular South ROM so I dont understand where you're going with this

[Mr. X]

Originally Posted by jakdillard

I posted what worked for me

Originally Posted by jakdillard

Sprint mr1 comes with that same driver in the XIP and so does the Cellular South ROM so I dont understand where you're going with this

Please edit your post not double post.

Im aware that the other roms have this driver, im also aware they are all different builds, which makes it possible that one reacts different then another.

And what im getting at is if that proses worked for you then the SPL has nothing to do with the no boot situation. because you would be flashing the same os that had booting problems to a device where the suspect SPL has not changed.