G4 Wizard extremely slow/green boot screen after upgrade - 8125, K-JAM, P4300, MDA Vario Software Upgrading

Hey guys,
After an upgrade (I don't remember which ROM I used, but I do remember it contained an .nbh ROM instead of an .nbf) I am getting the following boot screen with green horizontal lines as opposed to the Tmobile screen I am used to. It does not show the radio version for some reason.
{
"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"
}
The device boots EXTREMELY slow, and when it does come up, it does not respond to screen taps as usual. Also the screen jumps around every few seconds, shifting the display over to the right, and wrapping the corresponding line back to the left as shown here.
Activesync will not start and the device will not charge. The radio and protocol versions are not present in device info.
Flashing certain ROMs causes the device to stick on the tri-color bootloader, but I can always flash ROMs from there. Currently I am using the Wizard Love ROM. I want to reflash the original Tmobile 2.26 ROM (WM5), but depending on the RUU I use, I get different errors...
ERROR [238] : FILE READ
ERROR [294] : INVALID VENDOR ID
ERROR [300] : INVALID UPDATE TOOL
I had installed HardSPL at one point, but I uninstalled it and reflashed the Tmobile G4 IPL & SPL (Default 2.26.0001 that the phone came loaded with). I have disassembled the offical Tmobile ROM and reflashed these images (seperately, one at a time):
91000000 000c0000 9d2afeb1 SPL_2
90000000 00000800 75895195 IPL_2
96000000 00280000 6b60114a GSM_0
80040000 03900000 f46dd463 OS_0
92000000 00030000 2a4129c5 Splash Screen
9d000000 00010000 093cf0a5 HTC Logo_0
The only thing I can figure is maybe the bootloader got corrupted somehow, but I don't know where to find a SAFE image to reflash. I have bootloader_v5_15.nb0 from XDATools, but I don't want to take the chance of bricking my MDA.
I've only found one other case of the green boot screen on the net, but there was no resolution. Anyone have any clues?

dragoncub said:
Hey guys,
After an upgrade (I don't remember which ROM I used, but I do remember it contained an .nbh ROM instead of an .nbf) I am getting the following boot screen with green horizontal lines as opposed to the Tmobile screen I am used to. It does not show the radio version for some reason.
The device boots EXTREMELY slow, and when it does come up, it does not respond to screen taps as usual. Also the screen jumps around every few seconds, shifting the display over to the right, and wrapping the corresponding line back to the left as shown here.
Activesync will not start and the device will not charge. The radio and protocol versions are not present in device info.
Flashing certain ROMs causes the device to stick on the tri-color bootloader, but I can always flash ROMs from there. Currently I am using the Wizard Love ROM. I want to reflash the original Tmobile 2.26 ROM (WM5), but depending on the RUU I use, I get different errors...
ERROR [238] : FILE READ
ERROR [294] : INVALID VENDOR ID
ERROR [300] : INVALID UPDATE TOOL
I had installed HardSPL at one point, but I uninstalled it and reflashed the Tmobile G4 IPL & SPL (Default 2.26.0001 that the phone came loaded with). I have disassembled the offical Tmobile ROM and reflashed these images (seperately, one at a time):
91000000 000c0000 9d2afeb1 SPL_2
90000000 00000800 75895195 IPL_2
96000000 00280000 6b60114a GSM_0
80040000 03900000 f46dd463 OS_0
92000000 00030000 2a4129c5 Splash Screen
9d000000 00010000 093cf0a5 HTC Logo_0
The only thing I can figure is maybe the bootloader got corrupted somehow, but I don't know where to find a SAFE image to reflash. I have bootloader_v5_15.nb0 from XDATools, but I don't want to take the chance of bricking my MDA.
I've only found one other case of the green boot screen on the net, but there was no resolution. Anyone have any clues?
Click to expand...
Click to collapse
After removing HardSPL and reverting back to official t-mobile bootloaders,you shud have reflashed back to official T-mobile 2.26 completely,instead of dissambling the official rom and flashing the files seperately.The Roms are packaged together with certain other supporting strings and commands,which support and help the whole process of flashing a Rom image.It has a directory structure .
Try to flash the official T-mobile,hope it'll work,all these Errors are either due to corrupt Rom files which you downloaded,incompatibility of the rom or bootloaders are not accepting the RUU. Download the Roms again or from some other site and use another RUU like RUU_MUN,replace the RUU_MUn with RUU in the Rom and flash,hope it'll work.

After I flashed the original IPL & SPL, I did try to flash the original Tmo ROM (MDA_software_update_226102_22610105_022511.exe). That's when I started getting the errors. Only after that did I try flashing each .nb seperately.
These are the results I got from trying to flash the original ROM with different RUUs:
MDA_software_update_226102_22610105_022511.exe - 294 INVALID VENDER ID
Wizard_RomUpgradeUtility_noID - 300 INVALID UPDATE TOOL
RUU MUN - 238 FILE READ
I've also tried re-downloading MDA_software_update_226102_22610105_022511.exe to no avail.

dragoncub said:
After I flashed the original IPL & SPL, I did try to flash the original Tmo ROM (MDA_software_update_226102_22610105_022511.exe). That's when I started getting the errors. Only after that did I try flashing each .nb seperately.
These are the results I got from trying to flash the original ROM with different RUUs:
MDA_software_update_226102_22610105_022511.exe - 294 INVALID VENDER ID
Wizard_RomUpgradeUtility_noID - 300 INVALID UPDATE TOOL
RUU MUN - 238 FILE READ
I've also tried re-downloading MDA_software_update_226102_22610105_022511.exe to no avail.
Click to expand...
Click to collapse
Ok,perhaps the Rom which had .nbh ROM instead of .nbf was not meant for wizard devices,it might have corrupted the extended_rom or some other essential system files,coz if it had corrupted the Bootloaders than the phone will never boot into bootloaders mode.
ok,try to do the HardSPL again and upgrade to any wm6 rom and check if this resolves the issue.As it still boots up and displays official original IPL/SPL 2.26.0001,it means bootloaders are fine,doing HardSPL and reflashing to upgraded wm6 Rom,might resolve this issue and after wards if you wish to revert back to official TMO,than do the procedure again by removing HardSPL.
BTW,Have you tried 'Hard Reset' the phone.

hi zabardast_1,
How can I hardspl my pda if its only in the bootloader mode? Hardspl cannot detect the device(my pda). Do you also know where i can download original t-mobile rom? and how to download it?
ipl 2.26.0001
spl 2.26.0001
THanks in advance

xpxj said:
hi zabardast_1,
How can I hardspl my pda if its only in the bootloader mode? Hardspl cannot detect the device(my pda). Do you also know where i can download original t-mobile rom? and how to download it?
ipl 2.26.0001
spl 2.26.0001
THanks in advance
Click to expand...
Click to collapse
Activesync doesn't work in Bootloaders,there must be working OS on the phone to get activesync.
T-mobile official wm5 rom :-
http://rapidshare.com/files/38880130/ruu_prodigy_226102_22610105_022511_tmous_wwe_ship.exe.html
otherwise download and try wizard_love rom :-
http://rapidshare.com/files/17792050/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar

zabardast_1 said:
Activesync doesn't work in Bootloaders,there must be working OS on the phone to get activesync.
T-mobile official wm5 rom :-
http://rapidshare.com/files/38880130/ruu_prodigy_226102_22610105_022511_tmous_wwe_ship.exe.html
otherwise download and try wizard_love rom :-
http://rapidshare.com/files/17792050/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar
Click to expand...
Click to collapse
I will download these roms... And i'll get back to you for the results. Thanks a lot zabardast for the reply.

White Screen
zabardast_1 said:
Activesync doesn't work in Bootloaders,there must be working OS on the phone to get activesync.
T-mobile official wm5 rom :-
http://rapidshare.com/files/38880130/ruu_prodigy_226102_22610105_022511_tmous_wwe_ship.exe.html
otherwise download and try wizard_love rom :-
http://rapidshare.com/files/17792050/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar
Click to expand...
Click to collapse
Hi, I am almost but not quite in the same predicament that he is in, except I am stuck in the White screen and I can not get to the Bootloaders mode. I press the camera and power button to get into the screen and I only get the white screen. I have flashed my rom a couple of times now and this is definetly different for me. Is there another button besides the camera button that will get me back to the bootloaders screen?
Your help is much appreciated.

kfletch said:
Hi, I am almost but not quite in the same predicament that he is in, except I am stuck in the White screen and I can not get to the Bootloaders mode. I press the camera and power button to get into the screen and I only get the white screen. I have flashed my rom a couple of times now and this is definetly different for me. Is there another button besides the camera button that will get me back to the bootloaders screen?
Your help is much appreciated.
Click to expand...
Click to collapse
First, post the vital data of the phone to determine the DOC chip version of the phone.
Secondly,its not clear from your post what method or Rom you tried to flash. The only way to get into Bootloaders (multicolored screen) is by pressing Camera + Soft Reset or Camera + Power On button,but keep pressing & holding down Camera button till it restarts and gets into Bootloaders.

Related

No Radio ROM version

Hi
i have been given a XDAIIs by O2 from a mate to try and correct the botch update he tried to do.
He Download the ROM update from O2's web site, run the install but something happened half way though the Radio ROM procedure and it failed.
Now there is No radio Version when GetDeviceData.exe is run and the Phone function dont work too.
I have tried to install the manufacture Radio ROM and various others, but they all fail.
My guess as there is no version on the ROM the install process falls over trying to determin what the current version is.
IS there a way around this?
If no one can help he will have to send it back under the warranty.
Follow the wiki instructions for a radio upgrade!
http://wiki.xda-developers.com/index.php?pagename=BA_Radio_1.15_Upgrade
As i have Said.
These attemps have all failed.
i have even tried the devise in bootloader mode, the install does get further, it actually has the progress bar appear BUT it gets to 12% and an error occures see below
{
"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"
}
You are using the upgrade files for the wrong device. Extract a BlueAngel ROM Upgrade package using WinRAR or from Temp. Add the radio, nk, and ms files that you want. Then add MaUpgradeUt_noID.exe and run it. Should work no probs then.
Thanks
thats is what i have been doing.
i have used the factory shipped Radio ROM with no lucj what so ever.
FYI
the info for the beginning part of the Upgrade install
as you see the is no version in the Radio image version.
i have used the Manufactures shipped ROM from HERE O2 ones.
extracted the file to a folder removed the ms_.nbf & nk.nbf placed MaUpgradeUt_noID.exe in the folder and run it.
try radio 1.15
Tried that too, think i tried every radio version i could find.
RMA time by the looks of it i think
Forget the radio at the moment, can you flash an o2 CE ONLY
I reckon he can flash the CE ROM only. If not, then the device is probably faulty. If he can, then I reckon he's just missing a step somewhere. I had the exact same problem on my Qtek 9090. The Radio ROM would not upgrade, and gave the EXACT same error at the same percentage.
All I did was extract the ROM Upgrade file I obtained from the device manufacturer (maybe you are not using the one for your device) and replaced Radio ROM file and added the MaUpgradeUt_noID.exe and ran it
He could also use GetDeviceData and edit the Radio ROM file to be same operator code. Then use normal update without MaUpgradeUt_noID.exe
Anyway, I hope one way or another you get this solved
Cya
right i managed to get this from the devise
PH20B 0 B
WWE E
1.31.00 0 0
1.31.139
probably left there when he did the upgrade to TuMa 1.3.
so i assumed that THIS
is the shipped ROMs for the device.
got the nk.nbf file out of it, used downgrade from WM5 and now have CE back on the devise.
now what is my next step MDAIIIUser????
well using the same methord and the same files now flash the ONLY the radio rom out of that o2 Extraction.
Done that and it Fails
as priviosly posted.
So you are saying with the extracted 02 files you can flash the ce but not the radio even though you are doing the EXACT same thing.
Also the wiki radio 1.15 upgrade as written does not work when you try to follow it step for step.
You have tried radio upgrades with
- the type II methord,
- the no ID application
- and also a type I radio with fix.bat.
Well if that is the case you have done just about everything that I can think of. If not you need to tell me what you have not tried.
Here are my last two thoughts.
1) The upgarde you are doing is dirrect and you are NOT using a UBS hub
2) You have tried the upgrade from a different PC running XP with NO Fiirewall.
After that... welll sorry I cant help and you need to send it in, Well at least it has an ofical CE on it.
Yip MDAIIIUser that is the case i have tried every procedure on the forums & Wiki, all have failed.
I am using the USB sync Cable
&
I have NO firewall on the PC
My guess is that while the owner was running the official O2 ROM upgrade, during the Radio ROM update he did some thing really bad. I dont know what, he said to left it but you know some people they dont like admitting to mistakes, :O
I have just handed it back to him saying there is nothing i can do to it to fix it, send it back,
Now he is waitning for a returns pack under warranty.
Thanks for the Help guys, much appreciated. Keep Up the Good Work.
Oh what fun we all have here.
Hi all,
I'm having exactly the same issue.
Just to say: I wasn't able to fix it anyway!
The problem was the following:
Using an Orange SPV M2000 with an original ROM that was very old, I contacted Orange whether they would release a new ROM. They said, Yes in two months. But they didn't. So I took a ROM from T-Mobile and I ran fine.
Then I wanted to sell the device to a friend. For he wouldn't have troubles with GPRS settings I wanted to have back the original Orange ROM.
I contacted Orange support and they sent me a ROM.
I flashed my device with it at no error. When I had to reset it, I noticed "No GSM".
Since then, I'm unable to use GSM and BT.
I tried to get a warranty repair, but they just said, that I flashed a wrong software and that it is my fault... They would have to replace the mainboard at costs of CHF 650.- (=500$).
Now i bought another broken device at ebay to get the mainboard from it.
Orange CH has 2 roms on there site (GER + FRE) (which are also on wiki).
Now if you did flash your device with the wrong software then you would not be able to start it. If they sent you a rom update then it will contain 3 parts CE, EXT Rom and radio) and it is not likly that they would extract the radio rom and load one from a different device.
So your flash went bad possible due to a bad file.
As allways the best is to start over, flash a original rom get that to work and move from there.

"Mr. Clean" AKU 2.3 ROM - G4 Version (2.24.0001)

Please note, this is a TEST ROM and may not work.
I do not have a G4 version Wizard to test on, so some brave soul with the hardware in question is going to have to give it a try. Be aware, while I have double checked everything and this should work, FLASHING THIS ROM MAY BRICK YOUR DEVICE.
Once this is confirmed working on a G4 version Wizard, I'll update this post.
The contents of this ROM are functionally the same as the standard Mr. Clean ROM. For more information on Mr. Clean please read the original Mr. Clean thread:
http://forum.xda-developers.com/viewtopic.php?t=52775
Download:
ftp://xda:[email protected]/MrClean_RUU_WIZARD_2240001a_AKU23_WWE.zip
Readme:
-------------------------------------------------------------
Mr. Clean AKU 2.3 ROM v2.24.0001a for HTC Wizard (G4 version)
-------------------------------------------------------------
The ROM of choice for tinkerers and hobbyists is back, and this time the big baldy is ready to take on the G4 variant of the HTC Wizard. Because this ROM is designed specifically for Wizard units with the G4 flash chip it WILL NOT WORK on the original Wizard. If you have an original Wizard, you must use the 2.24a version of Mr. Clean.
---------------
WHAT DO I NEED?
---------------
-A CID Unlocked HTC Wizard with a G4 Flash Chip
-Windows PC with a USB port
-ActiveSync 4.0 or higher installed
-MrClean_RUU_WIZARD_2240001a_AKU23_WWE.zip
-------------------------------------------------------
HOW CAN I TELL IF I HAVE A G3 or G4 VERSION FLASH CHIP?
-------------------------------------------------------
There is an easy way to tell which version flash chip you have in your Wizard.
Simply look at your boot screen and check the IPL/SPL version.
2.xx = G3 Flash Chip
2.xx.0001 = G4 Flash Chip
-----------------------------
WHAT DOES CID UNLOCKING MEAN?
-----------------------------
A CID lock normally prevents you from using any ROM aside from an official ROM provided by your carrier/OEM. Trying to upgrade a CID locked device with an unofficial ROM can damage your Wizard. DO NOT try to upgrade your Wizard if you have not CID unlocked it.
If you wish to search for a free solution, please check the forums on http://xda-developers.com. Be aware however, that free solutions are only available for certain ROM versions. As of this writing there are no known free solutions for the G4 series Wizard, but this may change in the future.
A viable alternative to waiting for a free solution is to visit http://imei-check.co.uk. This company charges 20 British Pounds (approx 40 US Dollars) to perform a SIM and CID unlock on your Wizard. It claims to handle all versions of the Wizard hardware, so if you have a G4 version, this may be your only option. It is generally accepted as the place to go for SIM and CID unlocks.
*Note - I have NO affiliation with IMEI-Check. I am simply including the information as a service to the reader.
---------------------------------
HOW DO I FLASH THE Mr. Clean ROM?
---------------------------------
1) Unzip MrClean_RUU_WIZARD_2240001a_AKU23_WWE.zip to a folder on your hard drive.
2) Make sure your Wizard has at least a 50 percent charge on the battery.
3) Connect your Wizard to the PC via the USB cable.
4) Run the program ROMUpdateUtility_Wizard_NoID.exe in the ROM folder.
5) Follow the prompts to update your Wizard.
6) When you get to the UPDATE screen the version listed should be 2.24.0001a_MRC. If not STOP NOW. You have the wrong ROM.
7) Once you start the upgrade, your Wizard will reset to a rainbow colored screen. This is normal.
8) The Wizard then switches to a blank screen with a progress bar. It may pause for a few minutes at 98%. This is normal.
9) Once the update has completed, the Wizard will reset and present you with the initial configuration.
10) Calibrate the touch screen and let the customization option complete.
11) After the customization completes, the Wizard will reboot a final time and the upgrade is finished.
-------------------------------------------------------------------
WHAT IF I HAVE A WIZARD (G3 VERSION) AND WANT TO INSTALL MR. CLEAN?
-------------------------------------------------------------------
If you have a G3 version Wizard, then you need the file MrClean_RUU_WIZARD_224a_AKU23_WWE.zip.
When i reached step 6 of "How to Flash" i get this:
{
"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"
}
i should not continue right?
Tried to proceed, everything went ok till the "progress bar" part.. Phone turned to rainbow color, and this is what i got:
About to give this ago.. stay tuned!
no joy! I got Error 300 like the poster above me.
Maybe there's something incompatible with the noid version of the uploader that is refusing to let us upgrade?
allo gamescan;
correct if im wrong:
but if u try to install this rom into a g3 wizard a dont see how it could brick it.
because the rom checks the machine chip before flashing as the official roms that include the 2 versions.
so if u flash this rom into a g3 the only thing that not gets updated its the bootloader.....as it would not be compatible.
are you using the g3 update utilitys in the g4 roms?
because it coud be potencialy fatal.
as the haked update utilitys that we can find were made from roms prior to g4.
for the testers;
unless this rom has a 2.5 or above haked update utility u need to have the device cid unlocked because it will be no way u will be able to install it.
regads
faria
faria: my device is fully CID unlocked with the imei-check solution, as I can flash the 2.x versions of the imate and tmobile USA roms on my tmobile UK device.
sporkguy said:
faria: my device is fully CID unlocked with the imei-check solution, as I can flash the 2.x versions of the imate and tmobile USA roms on my tmobile UK device.
Click to expand...
Click to collapse
i wrote above;
unless this rom has a 2.5 or above haked update utility u need to have the device cid unlocked because it will be no way u will be able to install it.
im quite aware that if you have cid unlocked you will be able to install any rom,from any provider. i have flashed my with every possible rom plus my own.
sporkguy said:
no joy! I got Error 300 like the poster above me.
Maybe there's something incompatible with the noid version of the uploader that is refusing to let us upgrade?
Click to expand...
Click to collapse
Do you still have the T-Mobile 2.24 BETA ROM that I had you download the other day? If so, I'd love for you to try a few things.
First, upzip the T-Mobile ROM and the Mr. Clean ROM to two separate folders.
Now, make a new folder and *copy* the Mr. Clean ROM installer files to the new folder.
After than, copy the RUUGetInfo.exe from the T-Mobile folder and overwrite the one in the new folder. Click on the RUU Wizard (NoID) and try to run the upgrade.
If that fails, I want you to copy the RUUGetInfo.exe from the Mr. Clean folder and overwrite the one in the new folder. Now, copy the RUU Wizard from the T-Mobile folder into the new folder. Click on the RUU Wizard (DO NOT click on the NoID version) and try to run the upgrade.
If that fails, I want you to once again copy the RUUGetInfo.exe from the T-Mobile folder into the new folder. Click on the RUU Wizard (DO NOT click on the NoID version) and try to run the upgrade.
What were're trying to do here is track down where the version info is getting conflicted. I suspect it is because the hacked RUUGetInfo.exe is setup to always report a low version of the ROM so that the upgrade utility will allow downgrading. However, if the upgrade utility sees a G3 ROM on the device (which it always will with the hacked RUUGetInfo) it'll freak when you try to flash a G4 ROM to the Wizard. At least, that's what I'm going with right now. By swapping out a "normal" RUUGetInfo, I'm hoping that the upgrade utility will be happy because it will see a G4 ROM on the device and know that it is flashing a G4 ROM. The only "catch" that I foresee with this is that because it will be able to read the true value of the ROM, downgrading to earlier IPL/SPL versions will not be possible.
faria said:
allo gamescan;
correct if im wrong:
but if u try to install this rom into a g3 wizard a dont see how it could brick it.
because the rom checks the machine chip before flashing as the official roms that include the 2 versions.
so if u flash this rom into a g3 the only thing that not gets updated its the bootloader.....as it would not be compatible.
Click to expand...
Click to collapse
Yes. If someone manages to flash this to a G3 based device IT WILL BRICK. The software should prevent the flashing, but if you manage to override the safety check and force the flash, IT WILL BRICK.
It is foolish to the extreme for someone to try to flash this file to a G3 version Wizard.
As I mentioned earlier, I don't believe the flashing utility is the issue, I believe it is in what the RUUGetInfo utility is reporting to the flashing utility since the hacked version of the RUUGetInfo utility reports a fixed version number all the time.
Hopefully with Sporkguy's testing, we'll be able to successfully package a ROM that can be used by owners of CID unlocked G4 version Wizards. Of course, once the specifics are known, then that will also make it easier for others to package up custom ROMs for the G4 version Wizards as well.
thanks for the reply gamescan.
lets crack this....
it is my belive that there is an eazyest way ....
as far as i know the only diference betwin the g3 and g4 devices is the bootloader ipl/spl ,so we can take any rom and remove the ipl/spl ,therefore the rom would be OS+EXTENDED-ROM+RADIO+SPLASH AND HTC LOGO, and so we would be able to install this rom in any chipset version because we would not touch the bootloader and then we would have 1 rom for all ,and avoid confusion ,specialy to newbies.
the proof of this[as you know] is in the newest official roms ,after we take it apart it contains 2 ipl and 2 spls ,so that tells us that apart from the ipl/spl there is nothing diferent about the roms,since the official rom install in in the g3 and g4 chipsets.
forgive me if im wrong.
If you check the prior thread, you will see that did not work. A flash of GSM + Splash + Ext ROM failed with the same error 300.
The only way anything is going to get solved is with testing and careful deduction. Random guessing or untested assumptions will only confuse things.
gamescan said:
If you check the prior thread, you will see that did not work. A flash of GSM + Splash + Ext ROM failed with the same error 300.
The only way anything is going to get solved is with testing and careful deduction. Random guessing or untested assumptions will only confuse things.
Click to expand...
Click to collapse
a just flashed the latest 2.24 rom taken from an official rom that contains the 2 ipl/spls into a g3 wizard without probems[without the ipl/spl].so its not an random guess or untested assumptions. he got the error 300 because the wizard its locked.
i will be posting the rom soon ,i just nedd to finish integrating NETCFv2 into it .this should also work with cid unlocked g4,
godbye.
I'll try the above shortly - i'm just waiting on getting a copy of Sprite backup so I can come back again. (I'm getting tired of reloading all my stuff back onto the device every other day!)
Will let u know how it goes!
gamescan said:
After than, copy the RUUGetInfo.exe from the T-Mobile folder and overwrite the one in the new folder. Click on the RUU Wizard (NoID) and try to run the upgrade.
Click to expand...
Click to collapse
Error 300
If that fails, I want you to copy the RUUGetInfo.exe from the Mr. Clean folder and overwrite the one in the new folder. Now, copy the RUU Wizard from the T-Mobile folder into the new folder. Click on the RUU Wizard (DO NOT click on the NoID version) and try to run the upgrade.
Click to expand...
Click to collapse
Error 238 - File Read
(The UU Cannot open the requested file)
If that fails, I want you to once again copy the RUUGetInfo.exe from the T-Mobile folder into the new folder. Click on the RUU Wizard (DO NOT click on the NoID version) and try to run the upgrade.
Click to expand...
Click to collapse
Error 238 again
Ok, so i've never flashed my device bofore, and i'm dumb and i overlooked the first step of checking to see if i had a 3g or 4g.
I downloaded the program, and updated the rom. It installed, and it loaded up, i saw the pretty MR clean bootscreen (at which point i realized how dumb i was but i looked at the version in the loading screen, and i did say it was 4g, but this was AFTER the flashing of the rom, so i donno if that was just changed cause of hte flashing), and then it started installing the customizations. Then, my mind rests and i chat away for a bit with my friend on aim, and i glance over my phone. Its off, hmm i guess it had to restart, ok lets turn the baby on! umm why aren't you turning on? Huh? No? NOOOOOOOOOOOOOOOOOOOOOOOO!!! MOTHERFU$()*#&(CKER PIECE OF SHS$(T*( AHHHHHHHHHHHHHHHHHHHHHH
Its deAD! It won't turn on! Oh god what have i DONE!!!!!
HELPPPPPPPPPPPPPP
PS i have a tmobile USA version of the MDA vario
f18viper said:
Ok, so i've never flashed my device bofore, and i'm dumb and i overlooked the first step of checking to see if i had a 3g or 4g.
I downloaded the program, and updated the rom. It installed, and it loaded up, i saw the pretty MR clean bootscreen (at which point i realized how dumb i was but i looked at the version in the loading screen, and i did say it was 4g, but this was AFTER the flashing of the rom, so i donno if that was just changed cause of hte flashing), and then it started installing the customizations. Then, my mind rests and i chat away for a bit with my friend on aim, and i glance over my phone. Its off, hmm i guess it had to restart, ok lets turn the baby on! umm why aren't you turning on? Huh? No? NOOOOOOOOOOOOOOOOOOOOOOOO!!! MOTHERFU$()*#&(CKER PIECE OF SHS$(T*( AHHHHHHHHHHHHHHHHHHHHHH
Its deAD! It won't turn on! Oh god what have i DONE!!!!!
HELPPPPPPPPPPPPPP
PS i have a tmobile USA version of the MDA vario
Click to expand...
Click to collapse
Before looking into it being a more serious problem, do you by chance know what your battery charge was before starting this escapade?
The phone won't charge via USB when it's in bootloader or flash mode, and flashing has a decent current draw, so...could it have hit empty?
heh, it does say several times, in this very thread, that this rom is experimental and intended for G4 chips ONLY.
Hell, we've even been discussing why it doesnt work on my G4 device yet, and you still tried it? Brave, man, brave
I'd Probably try flashing it again by putting it into bootloader mode (take out battery, put back in again and press and hold the camera button whilst plugging in USB) - and sticking an older official rom on there.
Best of luck lol
Yeah i don't think brave is the word, dumb and impatient sounds better i think.
Well i don't think its the battery cause it did load, and I calibrated the screen and everything, and then it started installed the customizations, and then it went blank, so it did have a chance to start charging again.
I did only have a 60% charge though, i'm gonna try to sawp a battery a guy at work who's got a similar phone (its not the same, i hope htc uses the same batteries for its models)
At this point, NOTHING WORKS!!!!!!!!!!!!!!!!!!!! No buttons, not plugging in pressing the reset buttons, nada, nothing , zip just a blank dead piece of plastic. I took ou tthe battery countless times, ahh i'm lost
I broke my pretty thing
f18viper said:
Yeah i don't think brave is the word, dumb and impatient sounds better i think.
Well i don't think its the battery cause it did load, and I calibrated the screen and everything, and then it started installed the customizations, and then it went blank, so it did have a chance to start charging again.
I did only have a 60% charge though, i'm gonna try to sawp a battery a guy at work who's got a similar phone (its not the same, i hope htc uses the same batteries for its models)
At this point, NOTHING WORKS!!!!!!!!!!!!!!!!!!!! No buttons, not plugging in pressing the reset buttons, nada, nothing , zip just a blank dead piece of plastic. I took ou tthe battery countless times, ahh i'm lost
I broke my pretty thing
Click to expand...
Click to collapse
Exactly the same thing happened to mine at exactly the same stage (customizations), my battery was at 100% before flashing and have tried another battery too. It was totally dead, no flashing LED's even when left on charge, couldnt get into the bootloader by holding the camera button and plugging in the USB cable either. Luckily it was swapped over for a new one within a few days....
Oh mine was on the other rom the ""Mr. Clean" AKU 2.3 ROM" but the same result.... so put very bluntly, you are buggered
Exactly the same thing happened to mine at exactly the same stage (customizations), my battery was at 100% before flashing and have tried another battery too. It was totally dead, no flashing LED's even when left on charge, couldnt get into the bootloader by holding the camera button and plugging in the USB cable either. Luckily it was swapped over for a new one within a few days....
Oh mine was on the other rom the ""Mr. Clean" AKU 2.3 ROM" but the same result.... so put very bluntly, you are buggered
Click to expand...
Click to collapse
Ughh i don't think i'm going to be able to swap it. This sucks severly. Is there any possible way to access the bootloader? Possible breathe life into this thing?

Please HELP. SPL 1.09 and stuck

hi guys,
i was excited about the new Radio upgrade, so i tried to flash it. i got an error, because my SPL is 2.05. so i tried to unlock the phone using jerpelea's guide, flash to 1.09 -->success, then WWE (1.10) but an error occured saying invalid vendor ID during WWE flash. now i have SPL 1.09 on my phone and my phone is stuck on the 2nd boot screen of jerpelea's WM6.1 beta 4 ROM. my phone is fully unlocked using jerpelea's unlock guide, that's how i got to install SPL 1.09 successfully. how can i recover my phone? please help.
Update 1: i tried to flash back the original dopod 595 WM5 ROM. i mixed the RUU updater from the latest official ROM with the nbh from dopod WM5 ROM. the flashing works. when it's 100%, the phone reboots and, i got back to the same problem. stuck at 2nd/3rd boot screen. i now have IPL-0.90 and SPL 1.09 on my phone. Please help me to recover my phone. i've tried to hard SPL shown in the wiki guide, doesnt work. says invalid vendor ID crap. i really dont know what to do now.
Update 2: when the device boots, it stucks on the 2nd/3rd boot screen and if the USB cable is attached, for a brief moment, windows can detect the phone and i can even browse the content of the phone from my PC. but after that, the device disconnects itself and just remain stuck at the 2nd/3rd boot screen. the device appears to be totally freezed/hang. even the LED charging indicator will not turn off when i unplug the device from computer
i believe what i need to do now is to make a nbh image that is signed to i dont get any corrupted image message when trying to flash. i used HTC ROM editor to mix and match the SPL and IPL file so that i can downgrade the SPL to 2.05 and upgrade it again later. but i dont know how to sign nbh files.
If i were you I'd use this one =)
futureshock said:
ok i found it i didn't read further the 1st page on sspl thread
edit:
have repacked it with runme.bat and 77.7er SSPL ...
Radinly_1.54.30.10
Click to expand...
Click to collapse
At least I did and it worked =)
and then I'll highly recommend this WIM6.1 release by FutureShock: http://forum.xda-developers.com/showthread.php?p=2094056#post2094056
GL =)
I've GOT IT!!! using various mix and match method, im flashing the phone now!!! fingers crossed it'll boot later
UPDATE: DOESNT WORK! PLEASE HELP
It sure will.. Even I got it to work really fine
crap!. doesnt work. it's still SPL 1.09 and stuck at 2nd boot screen.
is there a ROM editor that works for meteor? can someone please suggest one that can be used to sign the nbh file.
jerpelea, or futureshock, please help
not good news
I think I know what do you mean. My device was in very same state like yours few mnonths ago.
Try to run mtty and the command "info 2" without quotes.
Do not forget to disable USB on activesync settings before running mtty.
You will get an answer which includes the CID of your device.
If not (this was my case), you have to send it to the repair center probably.
My device CID was Qtek_A07 (RUS) and I have tried to instal the first official WWE 1.34 ROM update (combined from SPL.nbh and ROM.nbh) and it replaced only the SPL, and the ROM update crashed.
There was not way out so I sent it to the repair center.
The WWE images are expecting the device with CID Qtek_Z12.
PiGeonCZ said:
I think I know what do you mean. My device was in very same state like yours few mnonths ago.
Try to run mtty and the command "info 2" without quotes.
Do not forget to disable USB on activesync settings before running mtty.
You will get an answer which includes the CID of your device.
If not (this was my case), you have to send it to the repair center probably.
My device CID was Qtek_A07 (RUS) and I have tried to instal the first official WWE 1.34 ROM update (combined from SPL.nbh and ROM.nbh) and it replaced only the SPL, and the ROM update crashed.
There was not way out so I sent it to the repair center.
The WWE images are expecting the device with CID Qtek_Z12.
Click to expand...
Click to collapse
this is what i get with mtty
Cmd>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCE
what's the meaning of this? is there any hope?
i ran the format command anyway. device reboots and still stuck at the windows mobile logo screen. what should i do next?
alexnvidia said:
this is what i get with mtty
Cmd>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCE
what's the meaning of this? is there any hope?
i ran the format command anyway. device reboots and still stuck at the windows mobile logo screen. what should i do next?
Click to expand...
Click to collapse
why did you format ?
try to reflash 1.09 spl
and after this wwe one of 1.34 roms to get 1.10 spl
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
but i dont know if you have the knowledge
jerpelea said:
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
Click to expand...
Click to collapse
jerpelea: First of all I will say thank you for taking all that time you do spend on the ROM cooking/building/making/what-ever-is-the-right-name and I/we really appreciate it!
jerpelea said:
but i dont know if you have the knowledge
Click to expand...
Click to collapse
I think that comment was really unnecessary!
As a n00b I know how hard it is to understand what’s happening. I did read the wiki’s and still I didn’t get HOW TO upgrade a ROM until I found a great post in FutureShock’s thread
darkDirk said:
First of all:
It's fantastic what you are doing with wm6.1 and the Breeze, Futureshock !
I am new and trying to upgrade it myself, but at first I didn't have any luck.
Here is a simple newby step-by-step manual:
- Download and extract a MTeoR-FutureShock-WM61-xxxx.x.rar
- Check your Mteor battery in more then 50 % full
- connect the Mteor to the computer via usb and check if Activesync works
- go with DOS (cmd line) to the directory and start runme.bat
- On the Mteor press camera and powerbutton at the same time.
- then immediately press any key on the computer to continue the batch script.
- now you should see the 3-color bootscreen
- press any key to start the rom-update program and follow its directions.
When the update is finished (in less then 5 minutes), then wait untill the first boot is complete.
If you don't get the 3-color bootscreen or you the update on the Mteor stays on 0 % and the rom-updater displays an error, try testing this:
On the Mteor start the explorer and in the root directory (press UP once) find SSPL.EXE en start it.
If the Mteor won't start the program and there is an error like "insufficient trustlevel".
You need to remove the application lock on your Mteor.
Run SDA_ApplicationUnlock.exe on your PC with Activesync working and then install SP_AllowCertificateInstall.cab on the Mteor.
You will find those two in the .rar in ".\opt Software\Unlock Tools"
Then redo from the start.
Then, Have fun !! (Futureshock & DarkDirk)
P.S. works on a BREE100 with IPL-0.90 and SPL-2.05.
Click to expand...
Click to collapse
But I still do not know what SSPL, SPL, IPL or whatever there is does to me or/and the phone.
Anyway. Thanks for all the work.
if someone has a corrupt CID just send me an pm...
jerpelea said:
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
but i dont know if you have the knowledge
Click to expand...
Click to collapse
with all the respect what you do for this community, isn't taht you who advice us to update the SPL before trying your images?
in this thread http://forum.xda-developers.com/showthread.php?t=384398 you should probably higlight that the update should be done only on WWE devices.
jerpelea said:
If you bothered to read the Wiki, you would have seen this:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
If you can't bother to read the wiki, don't play with roms!
Actually, I did read that, and a couple of problems:
1) Boot Loader is 1.09
2) OS won't load, so can't use any of the ActiveSync-based methods for downgrading to an older version, such as 1.04.
3) CID appears to be corrupted, as per the earlier output pasted.
from other forum ...... so read wiki
http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES
but i dont know if you have the knowledge
Click to expand...
Click to collapse
i did try to read as much as i could but apparently i didnt come across that. when i flashed to SPL 1.09, the device booted up just fine. it is when i try to update to WWE 1.10, the update process failed and bricked my phone. for your information, i was following the exact steps described by you in your unlocking/SSPL guide. you mentioned upgrade to SPL 1.09, then WWE 1.10. this is exactly what i did. i dont know what went wrong. im sure if im as knowlegable as you are, i wouldnt have screwed up my phone. my bad.
just to be fair, your method did work when i updated my dopod 595 (WWE device) to your WM6.1 beta 4 ROM. but i never upgraded my SPL to 1.10. i only thought of upgrading SPL when you posted the new radio release and that's where i screwed up.
anyway, what is important here is, is my phone unrecoverable? im reading the links you posted as i type, and i'll give the methods. maybe based on your experience, you could suggest some ways to do it. thanks.
alexnvidia said:
hi guys,
i was excited about the new Radio upgrade, so i tried to flash it. i got an error, because my SPL is 2.05. so i tried to unlock the phone using jerpelea's guide, flash to 1.09 -->success, then WWE (1.10) but an error occured saying invalid vendor ID during WWE flash. now i have SPL 1.09 on my phone and my phone is stuck on the 2nd boot screen of jerpelea's WM6.1 beta 4 ROM. my phone is fully unlocked using jerpelea's unlock guide, that's how i got to install SPL 1.09 successfully. how can i recover my phone? please help.
Update 1: i tried to flash back the original dopod 595 WM5 ROM. i mixed the RUU updater from the latest official ROM with the nbh from dopod WM5 ROM. the flashing works. when it's 100%, the phone reboots and, i got back to the same problem. stuck at 2nd/3rd boot screen. i now have IPL-0.90 and SPL 1.09 on my phone. Please help me to recover my phone. i've tried to hard SPL shown in the wiki guide, doesnt work. says invalid vendor ID crap. i really dont know what to do now.
Update 2: when the device boots, it stucks on the 2nd/3rd boot screen and if the USB cable is attached, for a brief moment, windows can detect the phone and i can even browse the content of the phone from my PC. but after that, the device disconnects itself and just remain stuck at the 2nd/3rd boot screen. the device appears to be totally freezed/hang. even the LED charging indicator will not turn off when i unplug the device from computer
i believe what i need to do now is to make a nbh image that is signed to i dont get any corrupted image message when trying to flash. i used HTC ROM editor to mix and match the SPL and IPL file so that i can downgrade the SPL to 2.05 and upgrade it again later. but i dont know how to sign nbh files.
Click to expand...
Click to collapse
run terratem
type info2
if it sais A07 then just flash rusian 1.34 rom and enerithing will be fine
application unlock it
run sspl 77.7
flash wm6.1
if it says enithing else you need to locate your original rom
till now i found that it sais a07 in most cases
BR
alexnvidia said:
i did try to read as much as i could but apparently i didnt come across that. when i flashed to SPL 1.09, the device booted up just fine. it is when i try to update to WWE 1.10, the update process failed and bricked my phone. for your information, i was following the exact steps described by you in your unlocking/SSPL guide. you mentioned upgrade to SPL 1.09, then WWE 1.10. this is exactly what i did. i dont know what went wrong. im sure if im as knowlegable as you are, i wouldnt have screwed up my phone. my bad.
just to be fair, your method did work when i updated my dopod 595 (WWE device) to your WM6.1 beta 4 ROM. but i never upgraded my SPL to 1.10. i only thought of upgrading SPL when you posted the new radio release and that's where i screwed up.
anyway, what is important here is, is my phone unrecoverable? im reading the links you posted as i type, and i'll give the methods. maybe based on your experience, you could suggest some ways to do it. thanks.
Click to expand...
Click to collapse
it depends on the info displayed on terraterm
for A07 you can use the russian rom to recover
this is what i got from terraterm. same as mtty.
Cmd>info 2
CID: Wait interpreter timeout
HTCSF kEØ(HTCE
Cmd>
i did flashed back to my original ROM after the first stuck in WM screen incident. and amazingly the flashing process works after several mix and match. after the original (WM5) ROM completed flashing, my IPL is downgraded back to 0.9 and SPL is still 1.09, and im still stuck at the WM logo screen (this time WM5 logo).
terraterm is a tool like mtty
what is your orignal rom??
just try to flash over sdcard... (look in wiki4more infos about that)
futureshock said:
terraterm is a tool like mtty
what is your orignal rom??
just try to flash over sdcard... (look in wiki4more infos about that)
Click to expand...
Click to collapse
i tried SD card flashing too yesterday. it says not allowed. i have already flashed over the original dopod 595 ROM and my phone is now WM5. the flashing is 100% successful, but it is still stuck at the second boot WM screen.
i think im in a really screw up position now. i have SPL 1.09 and IPL 0.9. i dont know what is corrupted now. is it the CID? SPL?
cid you can check with mtty and info 2...
if that so... just do what i have wroted in pm...
you could also just try the old htc rom (w. SPL 2.05)
futureshock said:
cid you can check with mtty and info 2...
if that so... just do what i have wroted in pm...
you could also just try the old htc rom (w. SPL 2.05)
Click to expand...
Click to collapse
both mtty and terraterm give me the same msg when i type info 2. it says time out (refer above for exact error message).
the original dopod 595 rom has SPL2.05. and it was successfully flashed into the phone. when the phone reboots, it is still stuck at 2nd boot screen (WM logo). i checked, the SPL is still 1.09, but IPL has been downgraded to 0.9.

Bricked phone? Upgrade rom error.

Hey guys,
So heres the deal. I tried to flash a rom and then all my colours were screwed up. (I was going from a 6.5 rom to topaz rom from L26.). I then read a bit and saw that it had to do with the spl. So silly old me went got the 1.14 stock SPL from the reverting spl section in the HardSPL thread and saw that it was a nbh file, so renamed it to BLACIMG and tried flashing it. It then finished and now my device is stuck on the tricolour screen stating that theres a Upgrade rom error - try again.
I really have no clue what to do now . Help would be muchos appreciated since I don't want my HD to die.
Thanks in advance guys,
/a
antrak said:
Hey guys,
So heres the deal. I tried to flash a rom and then all my colours were screwed up. (I was going from a 6.5 rom to topaz rom from L26.). I then read a bit and saw that it had to do with the spl. So silly old me went got the 1.14 stock SPL from the reverting spl section in the HardSPL thread and saw that it was a nbh file, so renamed it to BLACIMG and tried flashing it. It then finished and now my device is stuck on the tricolour screen stating that theres a Upgrade rom error - try again.
I really have no clue what to do now . Help would be muchos appreciated since I don't want my HD to die.
Thanks in advance guys,
/a
Click to expand...
Click to collapse
(1) Take out your SD card.
(2) Go into bootloader (turn off phone. hold volume down button while powering on)
What does your SPL say? Is it version 1.14.0000 now? If it is you should be ok. All you need to do to fix it is connect it to your computer via USB and run USPL 2.5. You should then be able to load a rom. What rom is it that you are wanting to load now? Is it a WM 6.1 or 6.5 rom? If it's a WM 6.1 rom is it based on the new HTC 1.56 rom?
antrak said:
Hey guys,
So heres the deal. I tried to flash a rom and then all my colours were screwed up. (I was going from a 6.5 rom to topaz rom from L26.). I then read a bit and saw that it had to do with the spl. So silly old me went got the 1.14 stock SPL from the reverting spl section in the HardSPL thread and saw that it was a nbh file, so renamed it to BLACIMG and tried flashing it. It then finished and now my device is stuck on the tricolour screen stating that theres a Upgrade rom error - try again.
I really have no clue what to do now . Help would be muchos appreciated since I don't want my HD to die.
Thanks in advance guys,
/a
Click to expand...
Click to collapse
Oh, and if you had/have HardSPL, never never NEVER load a stock SPL without first loading a stock rom based on that SPL.
It says:
BLAC100 32M
SPL-1.14.0000
MicroP-Blackstone (LED) v6
Upgrade rOM code error
Please try again.
Alright, but do I need a activesync connection for it since I can't powerup my phone.
I'll try the USPL thing you said now.
Learned my lesson about the stock rom before stock spl .
Thanks alot for the fast reply mate,
/a
--EDIT
about the other thing, its L26 V2.0 Topaz rom. Think it's based on 1.56 since he talks about using USPL aswell to install it, should I still do the thing you said? I'm in tricolour screen now with the upgraderom code error on the screen and in the white lower part it says USB, so it recognizes it.
antrak said:
It says:
BLAC100 32M
SPL-1.14.0000
MicroP-Blackstone (LED) v6
Upgrade rOM code error
Please try again.
Alright, but do I need a activesync connection for it since I can't powerup my phone.
I'll try the USPL thing you said now.
Learned my lesson about the stock rom before stock spl .
Thanks alot for the fast reply mate,
/a
Click to expand...
Click to collapse
No problem! When it's in the bootloader with the SD card out, plug in the USB cable and plug it in to your computer. Does it change from Serial to USB at the bottom after a few moments? If it does, then you can run USPL and flash another rom. If you are not familiar with USPL then you can download and read about it here.
Just saw your edit. Since you are wanting to flash a rom based on HTC 1.56 code then you will have to flash the original HTC 1.56 rom first. This is because it will raise your SPL level to 1.54. If you do not do this first and try to install a cooked 1.56 based rom over a 1.14 SPL you will have huge issues.
Read the guide in my signature. It explains upgrading to a cooked 1.56 based rom with an older/original SPL version step-by-step.
Alrighty.
So I'm at the point where theres USB in the tricolour screen. How would I load up the stock 1.56 rom? First do the 2.5 USPL and then?... My phone will still probally be stuck then aye? And as the 1.56 stock rom I see everywhere are .exe files which load up through activesync (which is no option since my phone is still stuck o_o) how would I do it? Should I try reverting back to a stock 1.14 rom or am I talking nonsense now? So confused my heads starting to burst!
Geez, I've been flashing for a long time but never delved so deep into this.
Thanks for all the help mate!
Haha no worries. Just eating pizza and watching tv like a lazy ass anyway
If you haven't downloaded the original HTC 1.56 rom yet, open my guide and click the link in step (1d) and select the right one for you (my guess is WWE).
Once you have it downloaded you will need to extract the .EXE using WinRAR or something similar so that you get the RUU and the .NBH file out of it. After you have that done, follow step (5) and on in my guide. You actually do not need to run USPL to load an original HTC rom unless the rom you are trying to load is a different CID than your device.
Basically, download the original HTC rom, extract it and run the RUU with your phone connected in the bootloader showing USB. If it says something about invalid vendor ID then do the exact same thing but run USPL first (steps (5a) through (5e) in my guide.
cRaCKwHoRe said:
Haha no worries. Just eating pizza and watching tv like a lazy ass anyway
If you haven't downloaded the original HTC 1.56 rom yet, open my guide and click the link in step (1d) and select the right one for you (my guess is WWE).
Once you have it downloaded you will need to extract the .EXE using WinRAR or something similar so that you get the RUU and the .NBH file out of it. After you have that done, follow step (5) and on in my guide. You actually do not need to run USPL to load an original HTC rom unless the rom you are trying to load is a different CID than your device.
Basically, download the original HTC rom, extract it and run the RUU with your phone connected in the bootloader showing USB. If it says something about invalid vendor ID then do the exact same thing but run USPL first (steps (5a) through (5d) in my guide.
Click to expand...
Click to collapse
Righto, downloading a 1.56 rom now. I'll let you know what will happen through a edit. Enjoy your pizza.
--FIRST EDIT
Damn, can only find rapidshare links. This'll take a while... x.x. I don't get why people use rapidshare!
--SECOND EDIT
Found a ftp mirror, will be done in 4 min. Yay!
Good deal, will check back in a bit.
Edit 1: Haha yes Rapid**** is exactly that...
Okay great . I started the whole thing, everything worked fine and the install went up to a whole 1%. Then it failed due to... (...backlight going off on my phone closing the usb connection I think ) and now the RUU can't connect to my phone anymore. Giving a [260] error. Argh!
Gonna try restarting my PC, hope that will help.
-EDIT
Got a vendor ID thingie error now, so gonna try flashing the stock rom with USPL as in your guide. Damn these phones! If this works (it's 2 am here now o.o) I'll be drinking a beer at midnight.
(regardless of if it works or not I think I'll get a beer soon .)
antrak said:
Okay great . I started the whole thing, everything worked fine and the install went up to a whole 1%. Then it failed due to... (...backlight going off on my phone closing the usb connection I think ) and now the RUU can't connect to my phone anymore. Giving a [260] error. Argh!
Gonna try restarting my PC, hope that will help.
-EDIT
Got a vendor ID thingie error now, so gonna try flashing the stock rom with USPL as in your guide. Damn these phones! If this works (it's 2 am here now o.o) I'll be drinking a beer at midnight.
(regardless of if it works or not I think I'll get a beer soon .)
Click to expand...
Click to collapse
LOL just make sure you drink the beer as suggested in step (7)!!! Otherwise you could end up back in step (1)
How goes it now? I'm a few Captain Morgan and Coke's deep myself at the moment...
cRaCKwHoRe said:
LOL just make sure you drink the beer as suggested in step (7)!!! Otherwise you could end up back in step (1)
How goes it now? I'm a few Captain Morgan and Coke's deep myself at the moment...
Click to expand...
Click to collapse
Haha, I kind of did step 7 a bit sooner and finished it around 5B, perhaps repeating step 7 will improve my HD it's performance.
The stock rom is working! I had a error connecting first with the USPL but after rebooting my pc and doing it again it worked a charm. Now I'm just trying to download the 2.8 Dutty rom to flash it through USPL.
I'll post back if it worked!
Thaaaanks Crack! You saved my HD from sure, inevitable damnation.
antrak said:
Haha, I kind of did step 7 a bit sooner and finished it around 5B, perhaps repeating step 7 will improve my HD it's performance.
The stock rom is working! I had a error connecting first with the USPL but after rebooting my pc and doing it again it worked a charm. Now I'm just trying to download the 2.8 Dutty rom to flash it through USPL.
I'll post back if it worked!
Thaaaanks Crack!
Click to expand...
Click to collapse
Woohoo we are making progress
Yippie it worked! Thanks a ton mate! Really helped out alot with the fast replies and all.
{
"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"
}
Proving I completed -all- the steps , mirrored text makes it even more fun to read!
I'll be off to bed now, I'll be waking up in 4 hours for work. Yay!
Thanks alot bud.
(Accept the friends invite. )
antrak said:
Yippie it worked! Thanks a ton mate! Really helped out alot with the fast replies and all.
Proving I completed -all- the steps , mirrored text makes it even more fun to read!
I'll be off to bed now, I'll be waking up in 4 hours for work. Yay!
Thanks alot bud.
(Accept the friends invite. )
Click to expand...
Click to collapse
!!!!! Dude that is hilarious!!! Glad you got it working! And I will definitely accept
antrak said:
Yippie it worked! Thanks a ton mate! Really helped out alot with the fast replies and all.
Proving I completed -all- the steps , mirrored text makes it even more fun to read!
I'll be off to bed now, I'll be waking up in 4 hours for work. Yay!
Thanks alot bud.
(Accept the friends invite. )
Click to expand...
Click to collapse
F***ing hilarious mate, love it, but dude, you have way to much time on your hands!!!
Glad you finally got it sorted, well deserved beer!!
Help! I was flashing new rom and my computer crash during flashing... 68% and crash!!! Now phone is in tricolor mode Upgrade ROM code error. Please try again and it´s Serial mode it wont go USB mode when I connect it. Can anyone help me or do I have one useless HD?? Specification: I do with "Dummies guide for flashing 1.56 roms" I was last step, flashing Dutty´s V.2.9 ROM when this happent.
Rauuno said:
Help! I was flashing new rom and my computer crash during flashing... 68% and crash!!! Now phone is in tricolor mode Upgrade ROM code error. Please try again and it´s Serial mode it wont go USB mode when I connect it. Can anyone help me or do I have one useless HD??
Click to expand...
Click to collapse
The fact that you have the phone in bootloader, even if its not working means your phone isn't bricked...yet!!
Do a hard reset, i.e. take battery out for about 5 seconds. Put it back in and then hold down vol up & vol down and press power button. You will be shown a grey screen. Press vol up to hard reset.
Then return to bootloader screen again and hopefully usb should reappear to try reflashing
Fallen Spartan said:
The fact that you have the phone in bootloader, even if its not working means your phone isn't bricked...yet!!
Do a hard reset, i.e. take battery out for about 5 seconds. Put it back in and then hold down vol up & vol down and press power button. You will be shown a grey screen. Press vol up to hard reset.
Then return to bootloader screen again and hopefully usb should reappear to try reflashing
Click to expand...
Click to collapse
It won´t reset it. When it should be start restore it goes straight in tricolor, same error.
Maybe flashing whit SD-card? Is there some instruction how to flashing in SD-card.

[Q] Stuck in cyclic restart after Radio ROM upgrade!?!

Hi, i am from Turkey,
I have a Touch Diamond (Diam100) bought from Norway. I just loaded a new radio ROM onto my phone (I am security unlocked and sim unlocked and hard SPL'd, thanks to Olinex!) and everything looked to work fine, the status bar got to 100% and the phone rebooted as usual after a new ROM load
However - it is completely stuck in a cyclic reboot. I get the HTC startup screen and then it just reboots again and again. I tried a hard reset and got the confirmation message that it was restored OK, press volume up to boot. However it does the same reboot again and again
I tried some thing like that:
*Try to install "RUU_Diamond_HTC_NOR_1.93.409.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship" stock rom, but it freezes at %13
*Try to install stock radio rom "Diamond_Radio_1.00.25.05" bu it freezes at %95!
*Try to install stock spl, everything looked to work fine, the status bar got to 100% and the phone rebooted as usual after a new ROM load but the problem seems again!
i can install cooked roms, but after restart this problem happens again and again!
Can you help me please? I love my phone very much.. (
(sorry for my poor english)
Hi, try MTTY your phone. log in to use search in these fora and find "The definitive MTTY thread". It's a bit of...homework to do but will get you out of this.Your issue is caused by certain undeleted items which remain after a rom flash as far as i've learned.I hadn't have to do it until after several ROM flashes but guess sooner or later everybody faces it.Well it's time you did it too...
Cheers
[email protected] said:
Hi, try MTTY your phone. log in to use search in these fora and find "The definitive MTTY thread". It's a bit of...homework to do but will get you out of this.Your issue is caused by certain undeleted items which remain after a rom flash as far as i've learned.I hadn't have to do it until after several ROM flashes but guess sooner or later everybody faces it.Well it's time you did it too...
Cheers
Click to expand...
Click to collapse
hi, i tried it step by step. but nothing happens
Hi,
Dude, that's frustrating, however as i understand it's a stock SPL you've presently got on your phone, right? I don't know which SPL version you've had before but just in case, try to update to HSPL version 1,93. Then try flashing a ROM you like.If problems persist MTTY your phone again after having upgraded HSPL.
And a word of advice based on own experience: Not all radios are compatible with all ROMs and vice versa...
Hope you're soon going to get this right,
Regards from Greece
merinos said:
Hi, i am from Turkey,
I have a Touch Diamond (Diam100) bought from Norway. I just loaded a new radio ROM onto my phone (I am security unlocked and sim unlocked and hard SPL'd, thanks to Olinex!) and everything looked to work fine, the status bar got to 100% and the phone rebooted as usual after a new ROM load
However - it is completely stuck in a cyclic reboot. I get the HTC startup screen and then it just reboots again and again. I tried a hard reset and got the confirmation message that it was restored OK, press volume up to boot. However it does the same reboot again and again
I tried some thing like that:
*Try to install "RUU_Diamond_HTC_NOR_1.93.409.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship" stock rom, but it freezes at %13
*Try to install stock radio rom "Diamond_Radio_1.00.25.05" bu it freezes at %95!
*Try to install stock spl, everything looked to work fine, the status bar got to 100% and the phone rebooted as usual after a new ROM load but the problem seems again!
i can install cooked roms, but after restart this problem happens again and again!
Can you help me please? I love my phone very much.. (
(sorry for my poor english)
Click to expand...
Click to collapse
before you upgrade the radio, whether it has been unlock device with the XDA Unlock Application ..? try to hard reset your device after that make sure the device go to the boot loader (3 colors screen) and reflash with the official ROM!! then unlock the device and immediately you can do to upgrade the radio (at the time of upgrading the radio make sure the SIM card removed)
[email protected] said:
Hi,
Dude, that's frustrating, however as i understand it's a stock SPL you've presently got on your phone, right? I don't know which SPL version you've had before but just in case, try to update to HSPL version 1,93. Then try flashing a ROM you like.If problems persist MTTY your phone again after having upgraded HSPL.
And a word of advice based on own experience: Not all radios are compatible with all ROMs and vice versa...
Hope you're soon going to get this right,
Regards from Greece
Click to expand...
Click to collapse
hi, i can not change the hspl, i tried again and again, but nothing changed.
(hspl olinex 1.93 signed and unsigned versions)
i tried to change the hspl to stock spl, installation was going and everything was ok (%100 inst.) but after restart, spl 1.40 olinex in bootloader mode again!
i don't know how can i change this 1.40 spl. i think the main problem is spl and radio rom.
{
"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"
}
Hakim Rahman said:
before you upgrade the radio, whether it has been unlock device with the XDA Unlock Application ..? try to hard reset your device after that make sure the device go to the boot loader (3 colors screen) and reflash with the official ROM!! then unlock the device and immediately you can do to upgrade the radio (at the time of upgrading the radio make sure the SIM card removed)
Click to expand...
Click to collapse
hi, my device is security unlocked, and hspl version is olinex 1.40.
i can not acsess to os, it just stay in the touch diamond screen .
thanks for the solution.
merinos said:
hi, my device is security unlocked, and hspl version is olinex 1.40.
i can not acsess to os, it just stay in the touch diamond screen .
thanks for the solution.
Click to expand...
Click to collapse
you have to do is to Hard Reset your device and reFlash

Categories

Resources