[DFT][Updated!#3] HSPL / RSPL for HTC WP7 First Generation - Windows Phone 7 Development and Hacking

DFT HSPL RSPL WP7F3
DarkForcesTeam proudly presents RSPL / HSPL
for phones HTC WP7 First Generation
(Short name is “WP7F”)
This is first big step to customization and community development for these devices.
History:
15.02.2012 Updated release. Revision #3.
Changes:
Was added support for 'SCHU1000' and 'PD291200' MIDs
Removed OTA update inside RSPL and HSPL, this allows to keep HSPL after HTC OTA Zune update.
Added warning screen about 4.XX and 5.XX
But still NO support for 4.XX and 5.XX
Support for CDMA devices: GoldC and SparkW
Wizard UI: only WWE support remains.
NOTE for ROM chefs:
SparkW custom ROMs must has "SPAW1000" MID instead of "PC402000".
This is done to protect from flashing Spark custom ROM to Spark_W and reversed.
18.08.2011 Updated release. Revision #2.
Changes:
Improved wizard GUI on non DPI 96 systems.
Added support for "PD291300", "PD291500" two new Schubert MIDs.
Replaced RSPL and HSPL for Spark from 1.10 to 1.20.
01.08.2011 Initial release. Revision #1.
WARNING TO ALL:
Do NOT use RSPL / HSPL with Mozart 4.XX and other RUU ROMS with MANGO.
All WP7F devices affected: MOZART, GOLD, SCHUBERT, MONDRIAN, SPARK!
It will damage your device. Not a joke.
MORE INFORMATION HERE
Read the next few messages for more information.
This release supports those WP7F devices:
*Gold (HTC Pro 7,T7575)
*Mozart (HD3,T8697,T8698,T8699)
*Mondrian (Surround,T8788)
*Spark (Trophy,T8686)
*Schubert (HD7, HD7S, T9292,T9295,T9296)
*HTC Gold C (HTC Arrive)
*HTC Spark W (Trophy Verizion)
Most of these devices have several MIDs (ModelID, looks like “PC921000”).
Current release supports only some limited number of MIDs. This was designed to minimize possible harm to user’s devices.
List of supported MIDs:
Gold: “PC92****”, “PC921000”
Mozart: “MOZA1000”, “PD67****”, “PD671000”, “PD671200”
Mondrian: “PD26****”, “PD261000”, “PD261100”
Spark: “PC401000”
Schubert: “PD29****”, “PD291000”, “PD291100”, "PD291200", "PD291300", "PD291500"
!Please note that on SPL screen MID is only 7 symbols, without last one.!
Programs stops any operations if unknown MID detected. If your device have unknown MID, please report about it in this thread. Specify your MID, device name, ROM versions. It’s nice, if you can give a link to download ROM.
Basic stuffs to know:
SPL is Secondary Program Loader. It allows to flash ROMs to device.
Without working SPL device is fully bricked, you can’t restore it. It’s why all operations with SPL are dangerous.
OSPL is Original SPL. This SPL comes with stock ROM and doesn’t allow to flash custom stuffs.
RSPL is Reloaded SPL. It load only to RAM, so it doesn’t persistent. It’s enough to soft reset device to get OSPL back.
HSPL is Hard SPL. It’s permanently flashed to internal device memory and replaces OSPL. After soft reset you still have HSPL instead of OSPL.
This release consists from RSPL and HSPL wizards.
For regular users, who flash ROMs rather rare, it can be enough to use only RSPL.
For advanced users and ROM makers, it can be useful to install HSPL.
IMPORTANT NOTES
1. Before doing any operations be sure you have battery level more than 50%!
Sometimes in SPL mode WP7F devices DO NOT charge. You may got a cold brick if it power down during SPL or RADIO update!
2. Stock RUU ROMs have two NBH inside, SPL_Signed and RUU_Signed.
So it's not possible directly flash stock ROM, you need extract files and remove SPL_Signed.nbh at least.
3. Rememeber if you have HSPL and you flashing stock RUU_Signed.nbh you lost HSPL!
4. Supported OS: Windows XP, Windows Vista, Windows 7.
Warranty Issues
Be warned, using RSPL may void your warranty.
If you need to send your device to a Repair Centre, make sure that it looks like stock! Install stock official ROM before go to Repair Centre.
Disclaimer
This product is free to use at your own risk. We take no responsibility for any conflict, fault, or damage caused by this procedure. No warranties implied or otherwise, are given if you agree to use this product. No problems were found while testing this product on several different devices, your experience may vary.
Use of the Product for commercial purposes is strictly prohibited.
It’s not allowed to make changes to this package; it must be distributed as original release.
Last version (R#3)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official DFT site (Chinese)
-DFT, 18.08.2011

Launching RSPL
DFT_RSPL_WP7FG1_LAUNCH allows you to load RSPL on the device:
1. Extract ALL files from RAR archive.
2. Run DFT_RSPL_WP7FG1_LAUNCH (with administrative rights to access USB)
3. Mindfully reads information text. Press “Next” button.
4. Reset your device and hold “Volume Down” button during reset to enter OSPL mode.
5. Connect your device to PC via USB cable.
6. Now you may need to install proper USB drivers. They come with Active Sync / Windows Mobile Device Center.
7. Install drivers if required.
8. Make sure device show “USB” at the bottom instead of “Serial”.
9. Press “Next” button in the wizard. It should detect your phone.
10. If you are using WCEUSBHS driver under Windows Vista/7 (for MTTY or MAGLDR TTY for example), you should apply “Windows XP compatible mode” in the properties of EXE file to get connection.
11. After successful connection it should show device codename and allows to choose installed OSPL version.
12. You should look at the screen and select OSPL version in drop down list box. You need do this because it’s not possible to detect installed version via USB.
If your current SPL version doesn't present in the list, you can choose nearest version,
BUT ONLY IF IT HAS SAME FIRST NUMBER!!
Example: You have 4.XX on the device. Do NOT choose 1.XX 2.XX 3.XX.
13. Press “Next”. Wait until comes final page.
14. Read and close window
15. Look at the device – it must reboot to RSPL.
16. If you see RSPLX.Y.Z and “CotullaRSPL” on the screen – the task done! Otherwise, please report in this thread about your problems.
17. Put some feedback in this thread for community and developers.
Installing HSPL
DFT_HSPL_WP7FG1_INSTALL allows you to install HSPL on the device:
1. Launch RSPL on the device like described above.
2. Be sure that you close RSPL wizard window.
3. Run DFT_HSPL_WP7FG1_INSTALL.exe (with administrative rights to access USB)
4. Mindfully reads information text. Press “Next” button.
5. Proper drivers already must be installed in RSPL step.
6. Press “Next” button in the wizard. It should detect your phone.
7. If you are using WCEUSBHS driver under Windows Vista/7 (for MTTY or MAGLDR TTY for example), you should apply “Windows XP compatible mode” in the properties of EXE file to get connection.
8. After successful connection it should show device codename and allows to choose HSPL or OSPL version to install. OSPL means you install stock SPL back.
9. Check device codename, if something wrong turn off computer and run to the nearest forest. Grab some water with yourself.
10. Press “Next”. Wait until comes final page.
11. Device will reboot and start to boot OS.
12. Reset it and enter SPL mode again. Be sure there HSPLX.Y.Z and “CotullaHSPL” appear.
13. Put some feedback in this thread for community and developers.

Example of HSPL screen on HTC Schubert:

Issues with MANGO RUU ROMS.
List of such ROMs:
It's not full list. Maybe some other ROMs affected by this too.
Thread about this ROMs.
RUU_Gold_S_HTC_Europe_3.02.401.01_Radio_5.69.09.29 a_22.50.50.21_Signed_GOLD_RELEASE.exe
RUU_Mozart_S_HTC_Europe_4.06.401.00_5.69.09_RELEAS E.exe
RUU_Mozart_S_HTC_RUS_4.06.411.00_5.69.09_RELEASE.e xe
RUU_Schubert_S_HTC_Europe_4.05.401.02_Radio_5.69.0 9.29a_22.50.50.21_Signed_SCHUBERT_RELEASE.exe
RUU_Spark_S_HTC_Europe_4.06.401.00_5.69.09_RELEASE .exe
About issue:
After running RSPL on MANGO OSPL, you can't flash device via SPL.
Windows Phone 7 OS is still booting and working.
Instead of full SPL screen you will see only one the first line:
You device will be "HALF BRICKED", because you can use OS, but can't flash anything else.
At the current moment it's IMPOSSIBLE to recover such devices. And I am not sure it will be ever possible.
What you must NOT do:
Before running RSPL wizard check your SPL screen.
There current SPL version at top: "X.Y.Z 2250 "
When wizard asks you to choose your current SPL version, be sure it's present inside versions list.
If your current SPL version doesn't present in the list, you can choose nearest version, BUT ONLY IF IT HAS SAME FIRST NUMBER!!
Example: You have 4.XX on the device. Do NOT choose 1.XX 2.XX 3.XX.
Generally it means that you must NOT run RSPL wizard after MANGO RUU ROM installation. You must flash older version (with 7004 or NoDo) and then run RSPL.
Installed OS version doesn't important. Only SPL version important.

reserved 4

reserved 5

Great work Cotulla you've done it again, broken through that barrier that just keeps our devices from being something wonderful.

I am so excited!!!!!!!!!!
I've been waiting on this for ages!

I just want to confirm, Does this support *Schubert (HD7,HD7s, T9292,T9295,T9296) for the install of HSPL? When I launch the install HSPL program it does not show up as a supported device, but when you launch the Launch RSPL it shows up as a supported device. Thanks.

Enter your device to SPL mode (Hold VolumeDown during reset) and look at the screen:
if you see there "PD29****”, “PD291000” or “PD291100" - it should work
You need run HSPL program _only_ after successful run of RSPL program!

great news. thanks alot to cotulla/dft.

Hey Cotulla, thanks for yet another break through from DFT. ive got the Bell HD7 (t9295) and thought id check..with the RSPL my model is not identified. the MID is PD291300. OS 7.10.7712.60 (mango) SPL 2.16.2250.0(117476)
this is the stock Bell Rom from ansar http://forum.xda-developers.com/showthread.php?t=1015699

Thank for the great work. HSPL loaded on my T-Mobile HTC HD7 PD29110.

thanks a lot to dft,HSPL loaded on my Mozart PD67***

great work cotulla
so we Can expect soon the Mango rtm build ?

thank you soooooooo much to share this tool

thanks cotulla!thanks DFT!

Does this work for the att hd7s -- pd29150 ANY HELP HERE PLZ

And my HD7 will run Android ?

Great work!
Thanks to Cotulla and DFT!

Related

htc rom tool: new software to deal with ROMs (NEW RELEASE 1.1.0)

htc rom tool: new software to deal with ROMs (NEW RELEASE 1.1.4)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------
htc rom tool version 1.1.4
by Dark Simpson
--------------------------
DISCLAIMER: I WILL NOT BE RESPONSIBLE IF YOU BRICK YOUR DEVICE USING THIS TOOL
This small application makes process of working with ROM's for some new HTC devices are bit more comfortable. htc rom tool will contain several instruments to deal with ROMs or it's parts.
Now, these instruments are implemented:
1. ROM builder. With this tool you can build a ROM (*.nbh) from a rom parts (*.nb) in a comfortable interface.
The built ROM is correctly signed (with my own cert), checked for errors and is ready to download into device. The device MUST be CERTIFICATE CHECKING unlocked for this (you need to use HACKED SPL for your device), or you will get an error while flashing (it is not fatal for your device I think, but keep attention on this fact!).
There is a possibility to add new devices to build ROM for by editing program's configuration file. This is described inside the "htcrt.ini" configuration file.
In the next versions these tools will be added:
- ROM extractor (to extract all *.nbh file or only a several needed parts from it)
- Splash tool (to deal with all kinds of ROM splash screens in a comfortable manner).
- ExtRom tool (to extract and rebuild "extended ROMs")
- System tool (to extract and rebuild an OS part and, maybe, to edit some contents inside unpacked system like initial registry and so on...)
---------------
Version history
---------------
1.1.3
Now and later you can get it here:
http://www.real-radio.ru/htcrt/
1.1.0
There is a new, rewritten, fully customizable dynamic engine that allows to add support for almost any of new HTC devices
+ Updating devices list automatically through your internet connection
+ Checking of blocks file sizes to meet specified criteria for device
+ Possibility to pad smaller blocks with 0x00's to the specified size
+ Coloring of block with respect to it's status
+ New checks and configurable warnings to protect from user mistake when building
+ Saving and loading projects
+ Command line support
+ Other additions
You can see other infos in the about - information of the program.
PLEASE HELP TO IMPROVE DEVICES CONFIG FILE: If you have knowledge about internals of htc devices rom files you can help me to improve, test and check different configurations for htc devices or to add new devices into program. If you want to participate please contact me. Firstly, you can check and validate existing config file's entries for different devices. If you want to add new one - I need to know all identifiers and names of all blocks and the default sizes of different blocks (as in the original firmware) if this is applicable to prevent user mistake in future And of course if you want to cooperate with me you woud like to understand syntax of the htcrt devices config ini file
!!! Now I have a big lack of time, and I think that I will be able to start working on devices config file only with second half of January 2008 Now you can start to collect infos, make corrections and additions to config and to debug them without my participation...
1.0.1
- ! Fixed bug with filepaths with spaces in ROM builder
- Added user warning when flashin IPLs or SPL in ROM builder
- Added new devices
1.0
- The initial release
Thanx a lot
Hey guys, I need to know your opinions about this
Write down all found bugs and your wishes here, please...
I'm waiting til you add the extractor and bits (as I havent got any nbh files etc to play with)
But looks very nice and cool
looks nice, could develop into a great tool
Can this tool sign the ROMs properly or the build ROMs r to b used with SSPL?
Yes, this tool signs resulting ROM file with my own certificate and if SSPL is not validating block hashes to be signed with OEM or HTC certificate while flashing (it may check blocks to be signed properly, but not to validate), than it can be used with SSPL. Of course, the CID checking must be eliminated in loader too, or you will need to type in the utility a valid CID.
Note, that with Artemis USPL this utility works without problems.
will the HTC StarTrek support in future?
Yes, soon I will release new config with the following devices:
Artemis
Trinity
Herald
Hermes
Athena
Breeze
Gene
Love
Startrek
So it does not support older htc models like Universal?
Edit: I see the config file only Artemis & Trinity.
If the format of ROM files for devices like Universal is different than of devices I posted in previous topic, then yes, my tool will not support these models...
great job Dark Simpson
Thanks again..!
Dark Simpson said:
...or you will need to type in the utility a valid CID.
Click to expand...
Click to collapse
I could enter in boot mode on my Artemis device and I got follow info:
ARTE1000 HTCE
It's means that my CID key is HTCE?
Thanks !!
Thank u ^^;
Pocha, I think if you can flash ROM signed not by HTC in your apparatus, then you probably:
1. Have bought IMEICHECK unlock
2. Using new shiny USPL
In both cases you can leave CID for 11111111... Else (if your device have standard unmodified SPL) you can't flash ANYTHING except original HTC's (or operator's) ROM and in this case htc rom tool will not help you...
Unfortunatly for me, I bricked my Artemis when I tried to upgrade to WM6 two weeks ago, my Artemis is SIM Unlock and Cid Locked, I bought it with no carrier, and I can't use ROMs in other languages..., when my Artemis is back I will upgrade SPL and I will try your program
Thanks !!
Then try this tool and confirm the results..if u could flash then this is the BIG moment for all of us here.gr8 job simpson
Thanks for this great tool
Attached htcrt.ini with support for the following devices:
Hermes
Trinity
Artemis
Love
Herald
Athena
Kaiser
Elf
Cheetah
Breeze
Excalibur
Oxygen
Startrek
StarTrek log:
ROM build process started...
Ceating temporary unsigned ROM file...
Writing ROM header...
Writing ROM contents:
cWindows.nb: 100%
Preparing destination...
Preparing ROM signer...
Signing ROM and copying it to destination...
ERROR: Signing process is not successful. Signer service
output:
ImageHash version 1.0
ImageHash Error: Invalid value for max packet size.
[there is going usage]
An error ocurred during signing ...
I used the original OS.nb from Dopod P800W shipped ROM (= HTC Artemis) to test your program but found following error:
ROM build process started...
Ceating temporary unsigned ROM file...
Writing ROM header...
Writing ROM contents:
OS.nb: 100%
Preparing destination...
Preparing ROM signer...
Signing ROM and copying it to destination...
ERROR: Signing process is not successful. Signer service
output:
ImageHash version 1.0
ImageHash Error: Invalid value for max packet size.
What happened? Any hint?

[UPG][TRBL]How-to fix: Update/Flash doesnt work, stops at 0% or 5% (invalid model ID)

Update doesn't work at all / stops at 1%
Short answer: Your device is needs HardSPL. See links at bottom to get it, read on to understand the difference between Standard/Developer Edition!
Long answer:If your Diamond refuses to be updated completely, you're probably missing HardSPL. The SPL is the device's bootloader. It controls what can be flashed and what not. In order to flash anything not signed by HTC or your cell operator, you will need a "custom" version, called HardSPL.
There is two versions of HardSPL, the links are at the bottom, but please continue reading the next section before downloading.
Update stops at 0%
Short answer: You're running the normal HardSPL and you're trying to flash an unsigned (not signed by olinex) ROM. You need the developer version which fixes the 0% issue. Link is at the bottom of this post. Read on to understand the difference between Standard/Developer Edition!
Long answer: First you need to understand that there are two definitions of "signed". HTC and the mobile operators sign ROMs so that the RUU flash utility allows them to be flashed. Usually this is what the word "signed" in the filename means.
Then there is another definition of signed: The developers of HardSPL introduced their own signing process. They want to ensure that people flashing cooked ROMs can rely on a certain quality standard. The normal version of HardSPL will only allow ROMs signed by OliNex to be flashed. If the ROM you are about to flash is signed, it will say so in the thread you got it from. If it isn't signed, you will need the developer version of HardSPL. That one will allow any ROM to be flashed. Get it at the bottom of this posting.
A note on this: The signing process by olinex makes sure that the ROM you're about to flash won't brick your device. It doesn't mean all other ROMs are necessarily evil.
Update stops at 5%/Invalid Model ID is displayed
Short answer: The model ID hardcoded in the ROM image doesn't match the ID of your device. Read on for a fix.
Long answer: Don't Panic. Your Device isn't broken
Each Diamond Model has it's own ID. My German MDA Compact IV is a DIAM200. Other models are DIAM150/DIAM300/DIAM100....
Now ROMs might be configured to be flashable to a specific Model ID only, even though technically they would work fine on any Model ID.
In that case the ROM needs to be "reconfigured" - this process works for full ROMs as well as Radios.
If you are running a foreign Version of Windows or have Regional Settings other than English US configured, please set them to English U.S. temporarily. Otherwise NBHUtil will not function correctly.
First you'll need OliPro's NBH Util (0.92 works for the Diamond).
Fire it up, switch to "Extract NBH"
Select the nbh of the ROM/Radio to be flashed and hit Go
Extract the components you need. Radio/Splash/OS. If there's an SPL in there, you can safely discard/ignore it. You have HardSPL for that.
Make note of the Target CID, Version, Language and Chunk Size. FYI the Model ID is the problematic setting here. If it says DIAM10000 and you have a DIAM300 you're screwed.
Switch to the Build NBH tab and select the Diamond as target
Note how the Model ID is preset to DIAM*****. The wildcard allows any device
Change target CID, Version, Lang & Chunk size to the values you wrote down.
Select each saved component under the NBH items
Hit Build NBH and save the file as RUU_signed.nbh to a folder of your choice and flash it with the DiamondCustomRUU.exe or ROMUpdateUtility.exe
Donate to OliPro because he just made your device useful
Hope I could help
Link to the standard HardSPL requiring ROMs to be signed by olinex: http://forum.xda-developers.com/showpost.php?p=2305307&postcount=1
Link to the developer HardSPL allowing any ROM: http://forum.xda-developers.com/showpost.php?p=2312363&postcount=2
NBH Util 0.93 is attached to this post. Oli: can you point me to the original thread containing the 0.93 version? I couldn't find it anymore.
Screenshots for "Update stops at 5%/Invalid Model ID is displayed"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshots continued
Screenshots for "Update stops at 5%/Invalid Model ID is displayed" - continued
Screenshots - last part
Screenshots for "Update stops at 5%/Invalid Model ID is displayed" - continued
I dont have doctor
When i select Diamond from Target device NBH Items box doesnt appear in my NBHUtil?? See attachment.
dtosun said:
I dont have doctor
When i select Diamond from Target device NBH Items box doesnt appear in my NBHUtil?? See attachment.
Click to expand...
Click to collapse
That looks like a problem with your system. Do you have the latest .NET Framework installed? Do you have another computer or a clean installation you can try on?
Yes, ı try it several computer but there is no success? could you please do modified nbh file for my diamond200? This will be good solution
I solve my problem, the problem is language setting, when i set my language settings to English, everything is fine
Thanks for your help.
dtosun said:
I solve my problem, the problem is language setting, when i set my language settings to English, everything is fine
Thanks for your help.
Click to expand...
Click to collapse
Do you mean your Windows XP regional settings ?
Yes, you are right.
Why don't you build a DIAM***** nbh file and put on this forum!
For many got it can be a general thing for all users!
because you need a different .nbh for each ROM in the forum and i don't think he wants to do that...
mihaixl: Just what racerx_ said. Would you rather have the single fish or learn how to fish yourself ?
dtosun: thanks for the involuntary debugging help. i added a note to the original docs.
maybe a mod can cleanup the postings?
Tones thanks for this, but i have not done it yet, i don't know which one to pick, i have the ERROR 294, and the update stops at 1%
not 5 or 0
should i go with the olnix rom then the HK version?
HTCDiamond22 said:
Tones thanks for this, but i have not done it yet, i don't know which one to pick, i have the ERROR 294, and the update stops at 1%
not 5 or 0
should i go with the olnix rom then the HK version?
Click to expand...
Click to collapse
You need HardSPL, yes. I updated the original posting. Please follow the Guide For the 1.93 HK WWE ROM you need the developer edition.
HARDSPL works thanks, but only thing now is that i miss my TF3D bottom effect, the moving tiles don't move anymore.
this is because of the HK rom.
this is a perfect how to.....
stupendous effort m8 thx a ton for all the directions and thx again to oli m8 for the utility
all TC and my rgrds
outkasted said:
this is a perfect how to.....
stupendous effort m8 thx a ton for all the directions and thx again to oli m8 for the utility
all TC and my rgrds
Click to expand...
Click to collapse
Thank you. mhm nice warm fuzzy feeling.
I just updated the original posting, I tried to make things more clear and easier to understand. Everyone: let me know if something doesn't make sense to you.
Mods: I'll risk sounding selfish. Wanna stick this? with proper care it might evolve into a basic ROM flashing FAQ... Maybe I'll port it over to the Wiki as well...
I realize there's _ a lot _ stuck already, but a lot of that could be consolidated in as little as 2 or 3 index threads. I'm willing to do that, please contact me via pm if you want.
cptsunshine said:
Mods: I'll risk sounding selfish. Wanna stick this? with proper care it might evolve into a basic ROM flashing FAQ...
Click to expand...
Click to collapse
ditto. this thread is essential for upgrading if your in a different area and need info about the nbh util. Changing the timezone on the home pc works like a charm! thnx cpt for the faq.
Edit: Never mind, thanks.

Asus P750 Kitchen - Beta Rom Released by Jerome!

*********************************
Jerome! has released a beta rom - see below for details - please help to test
*********************************
I noticed that a P750 Kitchen was released at asusmobile.ru, problem is that it is Russian base.
Using the following steps I was able to compile a rom that worked, abliet one I could not understand
1) grab your preferred kitchen from http://asusmobile.ru/board/viewtopic.php?t=14829 ( I used Manila Version)
2) extract
3) Copy your OEM files to the OEM folder
4) Run Build_ROM.cmd from root
5) When BuildOS comes up select your packages, press play, close when done
6) When prompted to select "B" or "X" to backup or delete dump folder
7) When NB0 Kitchen starts enter password: mrtoto
8) Load ROM and select PegasusP.nb0
9) Fill in and Select ROM version ,ROM date , CPU speed or pagepool size you want and click [Pack Image].
10) Select [XPR Compression] or [LZX Compression] and click [Build NB0]
11) Wait until you see the words "ROM.NB0 complete" in the message box, Exit the nb0 Kitchen and wait until you see its done
12) Open PegasusP.nb0 in a hex editor and change the bytes at offset 00001c5c from 00 10 85 05 to 20 00 00 0a, save.
13) Extract the attached ASUS_P525_NB0_Kitchen ENG.rar, open ASUS_P525_NB0_Kitchen.exe, load your nb0 and choose fix crc.
Flash by copying to root of SD card, hold power up, voice record in, joystick down while pressing reset and the bootloader will initiate a flash.
Next step is to convert to english, I have seen a tut at http://forum.xda-developers.com/showthread.php?t=312704 on how to translate, just wondering if there is an easier way that someone here may know of as with my limited knowledge I am likely to have missed something.
I tried dumping a rom from the guys at pdamobiz.com to use as base but packagetool would not work (no RGU?)
So anyway that is where I am at, if anyone wants to help that would be great as I reckon there is a few people out there that could do with an English P750 kitchen - I intend on getting this working at some point although time is limited.
HAt's off to the tool creators and contributors here at xda-devs, pdamobiz.com (feel like releasing a kitchen Undetect?) and asusmobile.ru.
Oh yeah if you decide to do anything I said and break stuff then don't cry to me, I have had a few bad flash's but each has recovered, YMMV.
dmozk said:
I notoced that a P750 Kitchen was released at asusmobile.ru, problem is that it is Russian base.
Using the following steps I was able to compile a rom that worked, abliet one I could not understand
1) grab your preferred kitchen from http://asusmobile.ru/board/viewtopic.php?t=14829 ( I used Manila Version)
2) extract
3) Copy your OEM files to the OEM folder
4) Run Build_ROM.cmd from root
5) When BuildOS comes up select your packages, press play, close wheen done
6) When prompted to select "B" or "X" to backup or delete dump folder
7) When NB0 Kitchen starts enter password: mrtoto
8) Load ROM and select PegasusP.nb0
9) Fill in and Select ROM version ,ROM date , CPU speed or pagepool size you want and click [Pack Image].
10) Select [XPR Compression] or [LZX Compression] and click [Build NB0]
11) Wait until you see the words "ROM.NB0 complete" in the message box, Exit the nb0 Kitchen and wait until you see its done
12) Open PegasusP.nb0 in a hex editor and change the bytes at offset 00001c5c from 00 10 85 05 to 20 00 00 0a, save.
13) Extract the attached ASUS_P525_NB0_Kitchen ENG.rar, open ASUS_P525_NB0_Kitchen.exe, load your nb0 and choose fix crc.
Flash by copying to root of SD card, hold power up, voice record in, joystick down while pressing reset and the bootloader will initiate a flash.
Next step is to convert to english, I have seen a tut at http://forum.xda-developers.com/showthread.php?t=312704 on how to translate, just wondering if there is an easier way that someone here may know of as with my limited knowledge I am likely to have missed something.
I tried dumping a rom from the guys at pdamobiz.com to use as base but packagetool would not work (no RGU?)
So anyway that is where I am at, if anyone wants to help that would be great as I reckon there is a few people out there that could do with an English P750 kitchen - I intend on getting this working at some point although time is limited.
HAt's off to the tool creators and contributors here at xda-devs, pdamobiz.com (feel like releasing a kitchen Undetect?) and asusmobile.ru.
Oh yeah if you decide to do anything I said and break stuff then don't cry to me, I have had a few bad flash's but each has recovered, YMMV.
Click to expand...
Click to collapse
Just want to let you know I'm working on it, expect some beta ROM's here soon So watch this space!
Hi, i wonder... will this work on O2 Xda Zset , it is made by Asus.
Cheers.
Nice one, I have not had a chance to do anything further. Look forward to seeing your work.
great
Hi is great was looking for one
First screenshots of BETA 0.1
Hi there,
I'm proud to present you the following progress status update:
VGA Windows Mobile 6.1 WWE SYS 21109 / XIP 20933 booting
GSM/3G/WIFI working
99% Interface is in English
20 MB of free RAM after boot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All credits to
Barin for the original kitchen (Asusmobile.ru )
Sorg for the VGA modification
Calkulin SYS from Diamond
MRtoto/VIVI for the P525 kitchen
More to come soon!
Looks great I have a P750, and i'm looking for a good rom -- can't wait to see what you come up with
Just wondering -- are you planning on implementing Asus`Multihome too?
(http://forum.xda-developers.com/showthread.php?t=481616)
Also since its VGA will you be porting the P522w software over? (Camera, UrTime, etc.??) Just wondering cause Sorg's original one has replacement problems but they weren't as clean as the original
pear-i said:
Looks great I have a P750, and i'm looking for a good rom -- can't wait to see what you come up with
Just wondering -- are you planning on implementing Asus`Multihome too?
(http://forum.xda-developers.com/showthread.php?t=481616)
Also since its VGA will you be porting the P522w software over? (Camera, UrTime, etc.??) Just wondering cause Sorg's original one has replacement problems but they weren't as clean as the original
Click to expand...
Click to collapse
My plan is to make a 'clean' rom soon. All the basics should be working. When this works I'll focus on porting some applications. Feedback and ideas of which it should contain besides the Camera, Urtime, Multihome, let me know.
Again good work, are you planning on releasing your kitchen when stable?
dmozk said:
Again good work, are you planning on releasing your kitchen when stable?
Click to expand...
Click to collapse
Yes, I will, when I finished translating the OEM files, they are still Russian now. Just to make clear, it's not my kitchen, I'm modifying the work of Barin, Vivi etc etc.
Time for a bèta release - testers wanted
To digg out all the bugs I've created a beta release. I will need your help in testing and reporting bugs. Please reply in this thread when you find something odd:
Please note this is a beta release. Not intended for every day use, however, I have been running this build for a week now and it's working well for myself. There might be things that I've broken though.
Also, since this is a bèta release, I will not be held responsible for any problems on your device. Flash at own risk.
How to upgrade:
- Place the PegasusP.nb0 file on a non-sdhc storage card (128 megs or more)
- Plug in power
- Press and hold the following keys when softresetting:
Voice record - Joystick down - Slider button up (e.g. power on button)
Wait until device restarts. Do not interrupt!
File contents:
Asus P750 Rom WWE 6.1 VGA Build 5.2.20933
Download here:
http://www.megaupload.com/?d=EJ0LA3WZ
Used sources (credits to)
Barin's asusmobile.ru kitchen
Mrtoto NB0 Kitchen
BengBeng asuspda.net XIP 20933
Sorg VGA Drivers
Vivi and all the others involved in the P525/p750 stuff
Calkulin's Diamond SYS 20931
Please report any issues you encounter! Except for:
Known issues:
- When clicking on softkey to open a menu e.g. contactsmenu, the size is bigger than normal.
- Core systems settings as Power, Device info, Brightness still in Russian.
- Some ASUS apps still in Russian like Asus switcher, CPU mode, Asus profiles, Wakeupsource
- Sometimes after first boot "unknown usb driver" message appears. Reflash the rom to resolve.
Nice one - testing now.
Jerome - any chance of uploading elsewhere, can't seem to grab anything from megaupload today for some reason..
dmozk said:
Jerome - any chance of uploading elsewhere, can't seem to grab anything from megaupload today for some reason..
Click to expand...
Click to collapse
Here's your RS link:
http://rapidshare.com/files/201120253/PegasusP.nb0
MicMeo said:
Here's your RS link:
http://rapidshare.com/files/201120253/PegasusP.nb0
Click to expand...
Click to collapse
Thankyou kind sir.
Got it flashed, on boot stuck in endless align screen page loop - soft/hard reset no good. Have reverted to previous rom, for what its worth my bootloader reads as below:
2007/12/05 20:06:37
IPL: iplPegP_4H3
dmozk said:
Got it flashed, on boot stuck in endless align screen page loop - soft/hard reset no good. Have reverted to previous rom, for what its worth my bootloader reads as below:
2007/12/05 20:06:37
IPL: iplPegP_4H3
Click to expand...
Click to collapse
Anyone else experienced the same? I've flashed mine more than 50 times and never had this kind of error. There is a lang unlock tool available. Perhaps it has got to do with that?
I've upgraded from an Extreme Ultralite Rom VGA WWE 3.1.0.7. Perhaps you can flash this one too and check if the same error occurs?
The bootloader of my device is exactly the same. This is a radio/bootloader/gps/free ROM update, just the OS.
thanks for the same
it seems great till now
well i just wanted to ask you is there anyway we can have a manila version in vga p750.
just asking .
cause it take a lot of memory installing it with cab.
if it can be done on the Rom itself it will be great.
prioin said:
thanks for the same
it seems great till now
well i just wanted to ask you is there anyway we can have a manila version in vga p750.
just asking .
cause it take a lot of memory installing it with cab.
if it can be done on the Rom itself it will be great.
Click to expand...
Click to collapse
Doing some testing on OEM packages for the Diamond in the P750 kitchen now...
Jerome! said:
Doing some testing on OEM packages for the Diamond in the P750 kitchen now...
Click to expand...
Click to collapse
hi ,
that will be just brilliant,
Keep up the good work
looking forward for the same
see if i am of any help.
Regards
Prio

Omnia 4 (B7350) custom ROM's 6.1/6.5 RU/WWE

17.02.12 Photoalbum database file fix to Storage Card (save 10th of mb of stolen space in mainstorage by mediaalbum database)
19.05.11 ROM Kitchen based on OSBuilder incl. SYS/OEM WM 6.5 (Build 21895) RU
Kitchen: DOWNLOAD
13.05.11 WM 6.1 Lite (Build 21054) 128DPI for SAMSUNG OMNIA B7350 (pagepool 8mb)
WWE(ENG): DOWNLOAD
Change log same as for 08.05.11 version.
08.05.11 WM 6.1 Lite (Build 21054) 128DPI for SAMSUNG OMNIA B7350 (pagepool 8mb)
RU: DOWNLOAD
How to flash at Post 2. Main difference - you dont need to flash langpack and take out battery as for older release (03/04/11).
Change log to older rel.:
-option to turn off autolockscreen;
-more hardware buttons customizable;
-no samsung dialer (video calls not avaliable).
03.04.11 WM 6.5.1 Lite (Build 21895) 128DPI for SAMSUNG OMNIA B7350 (pagepool 16mb)
WWE(ENG): DOWNLOAD
RU: DOWNLOAD
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Lite" (RUS/WWE)
-extra lang packages;
-software: GoogleMaps, DIOdict, Samsung Today;
-other garbage from samsung;
-My Phone (can be downloaded via Marketplace);
-Windows Live/Live Search (can be downloaded via Marketplace);
-MS Money, Weather widgets (can be found on internet);
+voice commander (only in WWE)
+HTC Task Manager;
+game Bubble breaker;
+Samsung Task manager;
+Samsung Alarms (only in WWE);
+Samsung FN Launcher;
+Transcriber (WWE);
+Home Screen Customizer incl. widgets -Weather, Progs..etc (for Titanium)
+added hidden wm 65 feature - screen vibration (option in sound settings)
+added hidden samsung sound settings (suxx)
Bugs/mods:
+Modified keyboard driver- assignable button "WIN" Hold;
+New keybacklight settings;
+Option "disconnect" replaced by "restart" in Shutdown menu;
+tweaked touch driver settings and smart touch (from HTC) (only WWE);
-Some menu's missing in Media Browser.(Due incompatibility with wm 651) Can use standard WM media browser instead.
-b7350 dialer doesn't show photo on incoming call ( Due incompatibility with wm 651) can use standard windows dialer or other.
Free file memory ~ 240 MB, Page pool 16 MB.
1. Flasher and instructions at post 2.
2. I'm not responsible for any damage due flasher or custom ROM to your device.
3. Is possible to change hardware keyboard layouts via registry in any ROM (this post)
4. Enjoy!!!
5. If you like my work pls PAYPAL
6. If you need to revert to original ROM or want to see official latest updates go here (need to be registered to view)
How to flash my custom ROM's to b7350?
FLASHING INSTRUCTIONS OF CUSTOM ROMS FOR B7350 V.1
Must have before flashing:
1. You will need only THIS flasher program. (Notice that flasher is patched against cheksum and other samsung protection and do not try to flash PHONE or BOOT files via this loader to avoid unexpected problems).
2. Also this PHONE bin part or another from this device (to enable other fields in flasher)
3. Only this dummy CSC part.
4. Any Langpack.lp0 (if you dont have here is one)
4. PDA image file of custom firmware(post 1)
How to flash:
For first time open loader and choise Model: "Orsay" in "PHONE" section -> choise phone part.bin
1. Choise in "PDA" section custom ROm(nb0). "CSC" field -Dummy CSC. "LangPAck" field -Langpack file lp0.
2. In "download mode" tick on only "PDA", "CSC", "Langpack" (Important "Boot", "Phone boot", "Phone" and other must keep unticked!!!)
4. Switch off device and disconnect from PC. Hold "Volume down"+"Lock"+"Power on" buttons till Downloading mode will appear. Now connect to PC.
If device is connected youl see green bar in flasher.
3. Press Start. Downloader asks you to reformat partitions- press Yes.
After updating phone reboots and shows error during lang customisation -its ok! When screen goes off- reinsert battery and power phone up again.
RESERVED
B7350 service manual
Thnx! Now try it!
WWE link is updated
First of all, thank you for your work. I never thought I see a customised ROM for Omnia 4. Still, before I try it, can you tell me what are the advantages of this ROM besides some removed apps and more free RAM. Is it speedier? Thanks.
albireox said:
First of all, thank you for your work. I never thought I see a customised ROM for Omnia 4. Still, before I try it, can you tell me what are the advantages of this ROM besides some removed apps and more free RAM. Is it speedier? Thanks.
Click to expand...
Click to collapse
yes its far quicklier/ classic windows GUI with Start on top!
Any chances to preserve Samsung Home in a future ROM version? I kind of like it, I can put all my shortcuts there.
you can use wm titanium - its quicklier, smoother and has wonderful tool HSC (Home screen cutomizer 1.51)incl in this rom that includes shortcuts, weather and other usefull plugins for titanium. Samsung home is a garbage circa 5-6 mb of file space and memory.
AWESOME!
Thanks a lot buddy, hope to see more of this coming from u
Glad that u cooked using WM6.5!
did u test the rom for a while? any kind of SOD bug?
cheers
What file should I put in Eboot image when I flash?
albireox said:
What file should I put in Eboot image when I flash?
Click to expand...
Click to collapse
NOTHING!!!!Boot image is bootloader image. Dont touch it, instead you are flashing official rom with non cracked flasher
Choise only "pda" csc" and "lang" images also tick on "pda.csc.lang" rest remain unticked.
If pda/csc/lang is corrupt during flashing or some other reason, you can always reflash. If you corrupt with PHONE/Boot downloading -will be just a bricked device after.
Sorry for the noob question, but at first, I didn't have the "start" button active. After i reconnected the phone it worked. Thanks.
albireox said:
What file should I put in Eboot image when I flash?
Click to expand...
Click to collapse
read 2nd post carefully!
i think u can't flash eboot or u will mess things up
jmsmartins said:
read 2nd post carefully!
i think u can't flash eboot or u will mess things up
Click to expand...
Click to collapse
jmsmartins said:
AWESOME!
Thanks a lot buddy, hope to see more of this coming from u
Glad that u cooked using WM6.5!
did u test the rom for a while? any kind of SOD bug?
cheers
Click to expand...
Click to collapse
Im trying to patch flasher to avoid flashing of other sections by assident
Russian version is already 4 days old. There is nothing dangerous in those roms. Friend is running english version for 2 days so far no problems.
Personally, me was using this device only for rom cooking. I dont own omnia 4, i still have old best i780!
BTW from i780 and "brothers" i took some useful software that is applied to new rom.
hi
i'm testing your rom and it looks great!
some programs/settings are not fully compatible but that's ok.
i have one small issue: when i change background image, the lockscreen image doesn't change. who can i overcome that?
cheers
Im not sure if its normally in wm 651, but if it doesnt appear after softreset than its so. Im using wm 653 on i780 now.
Running the rom for a few hours. So far, it works perfect, it seems a little faster than with the stock rom. I use SPB Mobile Shell and this is a little faster too. I like the fact that I can configure windows button (long press action) and also that I can get rid of auto correct features (that work only on english anyway).
The problem with EBoot was my fault, I just couldn't click on "Start" with no eboot image loaded, but after I restarted the phone everything worked as it should.
All in all, great first rom for our Omnia 4 phone, Heineken, keep up the good work
Thank you!
"If you wanna do good- do it yourself."
Added:
Have you discovered any serious bugs?
Heineken, no serious bugs so far but I noticed that when I answer a call it takes around a second between the time I press the Answer button and the moment I hear the caller. I don't know if this is because of the ROM or this is just the way this phone behaves. But, I didn't noticed that earlier. Also, after I restart the phone, I receive a message "The file InitHomeDown cannot be opened". It's not a real problem, because after I close this window, everything works as it should.
I'm still happy with this rom, as I said no major problems so far.

Maybe solution for HALF BRICKED DEVICE

Original HSPL post: here
About issue:
After running RSPL on MANGO OSPL, you can't flash device via SPL.
Windows Phone 7 OS is still booting and working.
Instead of full SPL screen you will see only one the first line:
You device will be "HALF BRICKED", because you can use OS, but can't flash anything else.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some HTC OEM Update contain a new Spl.
Maybe this way it will be possible to fix this issue.
if you have an half bricked device simply post this details:
device model
Dev unlock state (chevron...)
oem version (exemple 2250.21.40600.401)
& if possible rom link.
And i will told you what to try...
Thanks
Hope this works.
HTC Surround T8788
No Dev unlock anymore
OS Version 7.10.7720.68
Frimware Ver. 2250.21.40500.502
Bootloader Ver. 4.5.2250.0(129685)
My HTC Surround T8788
Original ATT ROM, No Dev unlock
OS Version 7.10.8107.79 (from 7720 with cab sender)
Frimware Ver. 2250.21.40300.502
Bootloader Ver. 4.3.2250.0(128976)
Tried cab sender with mondrian_2250.21.15204.502.cab, mondrian_2250.21.40300.502.cab, mondrian_2250.21.40500.502.cab, no luck.
HTC 7 PRO
OS: 7.10.7720.68
Firmware: 2250.10.10701.207
Hardware Revision: 0002
Bootloader: 3.2.2250.0
I have posted logs on my thread:
http://forum.xda-developers.com/showthread.php?p=21246069
It would be most apreciated if you can help us in this matter.
Thank you
waiting for your reply
luca
kaemen said:
HTC 7 PRO
OS: 7.10.7720.68
Firmware: 2250.10.10701.207
Hardware Revision: 0002
Bootloader: 3.2.2250.0
I have posted logs on my thread:
http://forum.xda-developers.com/showthread.php?p=21246069
It would be most apreciated if you can help us in this matter.
Thank you
waiting for your reply
luca
Click to expand...
Click to collapse
Hi kaemen
it seem that you do not use the good oem update.
try to found the good one, try zune.
you can also try to edit registry
if you operator doesn't deploy oem updated via zune.
change operator info in registry.
[HKEY_LOCAL_MACHINE\System\Platform\DeviceTargetingInfo]
"MobileOperator = ATT-US"
"MOName = AT&T Wireless"
"OEMDeviceName = PACIFIC_ATT_US"
I cant get a registry tool working.
When I open them they close again. I tred regeditor 1.2 xap and other ones..#
what now?
kaemen said:
I cant get a registry tool working.
When I open them they close again. I tred regeditor 1.2 xap and other ones..#
what now?
Click to expand...
Click to collapse
I have the same issue with the registery tool.
But I can open the tool but he don't save it, all the changes that I make.
You tried this: http://forum.xda-developers.com/showthread.php?p=19873059#post19873059 ?
info
device model: HTC Trophy touch-it
Dev unlock state (chevron...) No unlock
oem version 2250.21.40600.401
& if possible rom link. http://forum.xda-developers.com/showthread.php?t=1269652
hope you have some info...
beckersf said:
device model: HTC Trophy touch-it
Dev unlock state (chevron...) No unlock
oem version 2250.21.40600.401
& if possible rom link. http://forum.xda-developers.com/showthread.php?t=1269652
hope you have some info...
Click to expand...
Click to collapse
Hi
yes try to install this cab spark_2250.21.50001.707 this will install new spl if this work ,after that you will need goldcard to downgrade spl & reinstall hspl.
"You device will be "HALF BRICKED", because you can use OS, but can't flash anything else."
I wish I could... Yesterday I downgraded to NoDo and wanted to reupdate to Mango properly and while I was updating to Mango the Updateprocess failed. The Phone never booted back to NoDo and is stuck at the boot. Currently I am messing around with the GoldCard stuff
A crash or similar failure (even the cable coming unplugged) during the update will always leave the phone in a broken state. That has nothing to do with half-bricked bootloaders.
You can probably put the phone in recovery mode and connect it to Zune like that, and Zune should be able to restore the backup that was taken prior to the update beginning. That will put you back on NoDo.
Well from what I understood I here with a half-bricked bootloader (one line left on the tri-colored screen) and the phone wont be detected by windows at all =( (Correct me if I got something wrong)
Try booting to the Recovery mode, not the SPL mode. Hold the Camera button while booting. Zune *may* be able to see that mode.
However, if the SPL itself was damaged by a failed update (possible but a bit weird, unless you were using HSPL before), that may not work and you may need goldcard.
my updateerror log tells me it cant find the path....
couldnt I just create the missing paths to fix this error?
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\QC_8x50_ULDR_BOOT.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {DE19F4CF-9586-45CF-B803-CC4BA0313E12}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: QC_8x50_ULDR_BOOT cannot find a path to highest expected version of: 2250.21.30201.207
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\7E90549D-201C-4FF7-8982-14E76DE90FD4.100.pks\QC_8x50_ULDR.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.30201.207 GUID = {6939BB9F-56E4-47F3-AF2A-01DDFB414825}
bootloader update
lilila said:
My HTC Surround T8788
Original ATT ROM, No Dev unlock
OS Version 7.10.8107.79 (from 7720 with cab sender)
Frimware Ver. 2250.21.40300.502
Bootloader Ver. 4.3.2250.0(128976)
Tried cab sender with mondrian_2250.21.15204.502.cab, mondrian_2250.21.40300.502.cab, mondrian_2250.21.40500.502.cab, no luck.
Click to expand...
Click to collapse
Does someone know how to reapply the latest version of firmware for this phone, 40500.502? Cab Sender will not apply the update because of no applicable update (because it is already applied). I need this to repair my half bricked SPL htc surround.
HTC 7 PRO
OS: 7.07.7008.0
Firmware: 2250.09.12001.531
Hardware Revision: 0002
Bootloader: 4.5.2250.0(129185)
HTC Surround
OS: 7.10.7720.68
Firmware: 2250.09.10307.661
Hardware Revision: 0003
Bootloader: 4.2.2250.0(129185)
You can use Gold Card method. That's just the only option i can recommend.
My device is half-brick (tri-colored but without serial/usb) but with "USB Host mode" available (Power button + Vol Down + Camera Button).
Here's how I do it.
http://forum.xda-developers.com/showthread.php?t=1429318
After that it's all OK now.
Try this at your own risk.
what xboxmod said is 100% correct, i bricked my phone and was able to repair it through a simple firmware-update ( the internet-sharing one).
BUT: it's still not flashable. The white block should contain "SERIAL" or "USB", but it's empty. So you don't win anything. You just loose the oportunity to inter-op your device (htc-interop was released 3 days after i updated -.-').
so, a half-bricked phone has only 1 disadvantage: you can't flash it.
this kind of repair don't help to fix this.

Categories

Resources