Develop Bugs

INFO:- White screen after ROM flash

I've created this thread, as to not clutter the LVSW thread any more than it currently has.
Clearly (even though some don't believe it) there is an issue with th latest ROM releases and users doing a standard, succesful ROM update and being introduced to the IWSAU (Imaginary White Screen After Updating)
Those that currently have the IWSAU, there are fixes that seem to currently work. I've copy pasted some of my posts from the LVSW thread and hopefully others can posts here too with answers.
1. Download the FULL update from LVSW's first post.
2. Use NBHextract to rip the NBH file into seperate files.
3. Flash SPL-1.01MFG to your device
4. Flash OS.nb to device.
5. Enjoy a non white version of this great rom.
** Note to LVSW and other chefs reading. It appears there is some errors occuring when using the 1.13SPL and the latest RUU flash util and the latest roms. The information being flashed doesnt appear to be going where it should be on the rom and is causing this White screen. It is a bug.
I've repacked LVSW's latests rom, with an earlier RUU util and the force SSPL option only and works perfectly. Its something wrong with the newest combo of files and utils causing an issue.
Click to expand...
Click to collapse
Also, to add confusion to the matter. This is the results of the following
DOPOD 838 PRO - HERM100
15/3 LVSW Pro - Flases perfectly
20/3 LVSW ROM - White screen from update RUU
25/3 LVSW ROM - White screen from update RUU
Black 1.2 (with 1.13SPL) - White screen from update RUU
Black 1.2 (original) - Flashes perfectly
DOPOD 838 PRO - HERM200
15/3 LVSW Pro - Flases perfectly
20/3 LVSW ROM - Flases perfectly
25/3 LVSW ROM - Flases perfectly
Black 1.2 (with 1.13SPL) - Flases perfectly
Black 1.2 (original) - Flashes perfectly
I-MATE JASJAM - HERM100
15/3 LVSW Pro - Flases perfectly
20/3 LVSW ROM - Flases perfectly
25/3 LVSW ROM - White Screen after RUU update
Black 1.2 (with 1.13SPL) - White Screen after RUU update
Black 1.2 (original) - Flashes perfectly
However, all flash perfectly when using MTTY and the OS.nb...
Theres clearly something wrong. All tested same machine, same files, everything identical just different hardware.
Click to expand...
Click to collapse
Checked for bad blocks, was one of the first things i thought also...
Its strange, as its the welcomehead.96.png file that doesnt obviously display, but also the background image of the theme as well, so im wondering if its a section of the rom thats not flashing right, or possibly due to previous flashes etc being done, anything resdidual (shouldnt be) is left causing the issue.
I've just spent time creating a RUU 3.5 updater with the OS, SPL 1.30Oli and radio 1.38.0.10 and it flashed with white screen. I then lodaed the OS in to Rom Koch, removed the welcomehead.96.png file, replaced it with the same one, compile then used in the same flash, and it flashed perfectly fine, with no white screen.
Its buggng me as i don't want to have to mess around each update to get them, but also to help others. I enjoyed the double click update easyness of previous roms and im wondering if these new ones could possibly be in the compiling in the rom maker?? Maybe it effects certain hardware revisions??
Anyway, mostly speculation as i don't have the talents to investigate more, other than trial and error things like im doing. Im lucky to have 3 Hermes devices here to test on. So far the Dopod 838Pro HERM200 has flashed everything perfectly fine. The Dopod 838Pro HERM100 has the most white screen fails, and the JasJam inbetween.
Click to expand...
Click to collapse
I did a full official dopod rom update, then tried the latest LSVW one. same white screen.
Rinse and repeat but this time with older RUU util and OS only, worked perfectly.
Im convinced it has something to do with the NAND and the smaller image/larger storage space hack now more than ever.
I took the 15/3 LVSW rom, and ram it through the storage patch.
Flash Dopod HERM100 - White screen (where before this was my saving rom it seemed and 100% worked every time)
Flash JasJam HERM100 - Worked perfectly
Flash Dopod HERM200 - White screen (where before this was my saving rom it seemed and 100% worked every time)
Obviously more and more people are downloading this and trying it out and its now appearing that the original couple "doing it wrong" where actually right and are experiencing a common issue now.
Click to expand...
Click to collapse

LVSW rom uses Custom RUU v3.5, this RUU unpacks either the old hermes RUU (for bootloader <=1.09) or the new hermes RUU (for bootloader >= 1.11). In the later case, the standard RUU always does a 'task 28' to format the storage (ie: hard-reset) after every rom flash. I did some tests with Olipro before releasing it and we thought that removing the 'task 28' was fine (since we don't want a hard reset after flashing any NBH that doesn't contain OS), and as we didn't got any issues flashing several OS versions we thought it was fine this way, but probably this is what is causing the problem.
Have any of you having this 'white screen' issue tried to just do a 'hard reset' after flashing LVSW rom? Did it fixed the problem?

IM re-creating the issue now and flashing a problem rom as i type.
I did a hard reset with keys and stylus, and made no difference.
Im going to do a Task 28 in MTTY after this flash and see if it makes any difference, and will get back to you.

ok, can you also try with the standard / unmodified HTC RUU? You can extract it from the file RUU_Inside.exe in htc's 2.11 rom or in imate's new rom.

Hi guys,
so yesterday night I was working the whole time with the white screen stuff! Installing of different roms did not bring any success removing the white screen.
Sorry maybe for the wrong words, which I am using, but I am still a newbie, but my white screen is gone after doing following steps, if I remember right:
I flashed the original vodafone complete rom from the manufacturer on my vpa compact III. This seems to work. But then after finishing the installation in the restart the start screen with the vodafone bootscreen I saw the two words "No GSM" and the vpa compact stucked in the windows screen. Then I tried to use the brickregenerationstuff from pof , with no really success. After that I installed again the new lvsw complete version and again I had the white screen problem, but in this moment I was glad to have the white screen problem, than the no gsm screen . After that I made absolutely the same like before installing the vodafone stuff! I installed the previous LVSW version with extrom etc. After that the white screen was no longer there.
I am not sure, what I did and why the hell the white screen was no longer there, because I made the same thing before installing the vodafonestuff.
It sounds a bit confusing, but it was confusing .
Maybe this helps somebody to extract some information, which can help somebody else.

pof said:
LVSW rom uses Custom RUU v3.5, this RUU unpacks either the old hermes RUU (for bootloader <=1.09) or the new hermes RUU (for bootloader >= 1.11). In the later case, the standard RUU always does a 'task 28' to format the storage (ie: hard-reset) after every rom flash. I did some tests with Olipro before releasing it and we thought that removing the 'task 28' was fine (since we don't want a hard reset after flashing any NBH that doesn't contain OS), and as we didn't got any issues flashing several OS versions we thought it was fine this way, but probably this is what is causing the problem.
Have any of you having this 'white screen' issue tried to just do a 'hard reset' after flashing LVSW rom? Did it fixed the problem?
Click to expand...
Click to collapse
So which SPL is better to use - <=1.09 or >1.09?
If this is the issue, then may be the solution is just changing to right SPL and full upgrade afterwards?

Hi There,
I also tried the latest LVSW and Black 1.2. Both give me the white screen issue, whereby the 'Today' screen is a blanket white and nothing can be read until you highlight over them via the scrollwheel or a screen tap. It's as if the background on the mainscreen as default has disappeared and no amount of resetting the background via settings will fix this.
I am using the 1.38.0.10 radio with the 1.13.oli. Prior to this, I was using the first LVSW release, I think on the 11th March.
Anyone know a solution to this?
Thanks in advance, and keep up all the great work here!
J
p.s my device is originally an orange M3100 SPV, or HERM100 if that helps in any way.

Dopod 838 Pro No Problemo
Hi,
I had a dopod 838 Pro which is hermes100 and i just flashed it without any problem. I was using WM Black Ed v1.2 with 1.13 Oli Spl.
Thanks
Cheers..

I also experience the issue, using 1.13.oli spl 1.38.00 radio, Ill see what I can come up with later on when I get home from work.

someone: test this procedure:
enter bootloader mode.
run mtty
issue task 28, close mtty.
flash with CustomRUU, select 1.11.
see if you get a whitescreen.
if you do, re-enter bootloader, issue task 28 again.
see if you still get a white screen.
also, I've been thinking... if you are removing a bmp image from the OS NB then the OS is still the same size (or smaller) therefore, if NAND blocks aren't getting wiped they STILL won't get wiped when you reflash the new equal size or smaller NB, and THEREFORE it is *nothing* to do with the SPL or CustomRUU.
The SPL merely flashes binary data, it doesn't give a hoot what that might be, therefore, if it's buggering up, then the structure of the image is buggered up, it's nothing to do with the SPL.

I've just followed your destructions using your CustomRRU (v4) and am experiencing the same issue.
My symptoms:
Have to tap once to start screen calibration
White second boot loader screen
White text on the home screen
If iLauncher is installed, the iLauncher graphics become corrupted (untested with Black Edtn 1.2).
This could be a shot in the dark, but could this be caused by IMGFG?
Hope this helps!

Ok after being up all night last nite working on it, I'm ready to give a few more methods a shot.
pof: If I run task 28 (hard reset) and close mtty...then I should run the custom RUU to install the ROM and select SPL-1.01 in the beginning right?
I'm just a little scared with SPL-1.01 as I'm not as protected like Oli's SPLs would.

akarandomjames said:
Ok after being up all night last nite working on it, I'm ready to give a few more methods a shot.
pof: If I run task 28 (hard reset) and close mtty...then I should run the custom RUU to install the ROM and select SPL-1.01 in the beginning right?
I'm just a little scared with SPL-1.01 as I'm not as protected like Oli's SPLs would.
Click to expand...
Click to collapse
no, all you'll get is a message calling you an idiot for not knowing that you can't flash a ROM with 1.01

Yea I actually did read that and flashed back to 1.04 before anything.
I attempted to redownload LVSW's latest release 3/26/07 and flashed it on my device...still white.
NOW I'm going to try the mtty method after learning and understanding mtty a little bit more.
I enjoy wasting 25 minutes each flash ^_^

Just want to confirm that this worked for me. Had the white screen problem with LSVW 3/25, 3/26 and WBME 1.2.
1. Download the FULL update from LVSW's first post.
2. Use NBHextract to rip the NBH file into seperate files.
3. Flash SPL-1.01MFG to your device
4. Flash OS.nb to device.
5. Enjoy a non white version of this great rom.
Click to expand...
Click to collapse
Now running LSVW 3/26. Very snappy! After getting it running correctly I reflashed to HARD-SPL v4.

I would also like to confirm that Flashing via Mtty has also worked for me. NO MORE WHITE SCREEN...
Even though that was the SOLUTION to the problem...I still wonder what the real source of the problem was.

ok...i wanted to flash with mtty. but when i start mtty, i get "cmd>" instead of "USB>". What is wrong?

Nothing is wrong. HARD-SPL V4 will show CMD>. Once you flash SPL 1.01 MFG, it will show up as USB>

I have a problem in that when I try the above I enter lnb OS.nb but I get a command error. Dont suppose anyone has any ideas?

mart_haj86 said:
I have a problem in that when I try the above I enter lnb OS.nb but I get a command error. Dont suppose anyone has any ideas?
Click to expand...
Click to collapse
yes, you're not running 1.01MFG or worse... you're running the unpatched one without being supercid.
type task32 then try it again.
also, if task32 returns Level=FF... I hope your OS boots or you're in trouble

RBS WM6.1 ROMS and Hard Reset ...Possible Solution thread and thoughts

I wanted to install PDACorner v22 RBSN over NRBSN and I flashed defore the See here for more info Dr Puttingham solution suggested ROM via SD.
I have done the SD Flash once more with my WWE ROM 3.54 and in both ROMS the ORDER of flashing parts on my Tytn 's screen was
Code:
IPL,Bootloader,ExtROM,GSM,OS
I know we all use dutty's nbh tool v1.1 for compiling RUU_Signed.nbh .
I dare to make a thought about this tool makes the RBS ROMS to Hard Reset, because it makes the order of flashing
Code:
IPL,Bootloader,OS,GSM
meaning it flashes the Radio after the OS.
Both Stock ROMS with EXTRom flashes the Radio before the OS.
So is there any chance of changing the order in dutty's tool and do the Radio flash before the OS???
In that way we can check if THIS is the problem (and solution) of Hard Resets
Please post your thoughts on my theory and I will contact dutty about this thread to see if he can change his tool

lagoskon said:
I wanted to install PDACorner v22 RBSN over NRBSN and I flashed defore the See here for more info Dr Puttingham solution suggested ROM via SD.
I have done the SD Flash once more with my WWE ROM 3.54 and in both ROMS the ORDER of flashing parts on my Tytn 's screen was
Code:
IPL,Bootloader,ExtROM,GSM,OS
I know we all use dutty's nbh tool v1.1 for compiling RUU_Signed.nbh .
I dare to make a thought about this tool makes the RBS ROMS to Hard Reset, because it makes the order of flashing
Code:
IPL,Bootloader,OS,GSM
meaning it flashes the Radio after the OS.
Both Stock ROMS with EXTRom flashes the Radio before the OS.
So is there any chance of changing the order in dutty's tool and do the Radio flash before the OS???
In that way we can check if THIS is the problem (and solution) of Hard Resets
Please post your thoughts on my theory and I will contact dutty about this thread to see if he can change his tool
Click to expand...
Click to collapse
The only problem here, is that I remove the radio from my stock rom before flashing, and I have had no HR or freezing problems.
Edit: Though.. atm, a single rom flash doesn't last much more than a day...

interesting thread
I don't take shortcuts, I follow the dr's order down to the T, and does take a good half an hour to 45 min to get things running, I will monitor of quicker way of doing it, if it saves me time, I would love to know too, so .. here I am watching with anticipation.

zocster said:
I don't take shortcuts, I follow the dr's order down to the T, and does take a good half an hour to 45 min to get things running, I will monitor of quicker way of doing it, if it saves me time, I would love to know too, so .. here I am watching with anticipation.
Click to expand...
Click to collapse
I'm from Mars m8
NEVER FLASH RADIO WITH CUSTOM ROMS TOGETHER
ONLY RADIO
ONLY CUSTOM OS
OR RADIO WITH OS FROM ORIGINAL SHIPPED HERMES WM6.1 ON mars

anryl said:
ORIGINAL SHIPPED HERMES WM6.1
Click to expand...
Click to collapse
there's no official shipped wm6.1 for hermes as i know

I know all this about not flashing Radio all the time with roms. I just say that the sequense of parts is not the same.
It should be IPL,SPL, Nothing , OS without flashing radio and NOT IPL,SPL,OS, Nothing which is the case now

lagoskon said:
I know all this about not flashing Radio all the time with roms. I just say that the sequense of parts is not the same.
It should be IPL,SPL, Nothing , OS without flashing radio and NOT IPL,SPL,OS, Nothing which is the case now
Click to expand...
Click to collapse
Whatever the order of the pices, wouldnt the firmwear still have to go to the same places in the chip? Or you would end up in brick town.
Didn't someone say the HR's where due to part of the chip not being overwritten, and when you flash another rom, (that isnt a FULL shipped) it ended up causing incomparability issues?

veyka said:
Whatever the order of the pices, wouldnt the firmwear still have to go to the same places in the chip? Or you would end up in brick town.
Didn't someone say the HR's where due to part of the chip not being overwritten, and when you flash another rom, (that isnt a FULL shipped) it ended up causing incomparability issues?
Click to expand...
Click to collapse
Remember guys the Real Big Storage ROMs overwrite the ext_rom portion to use as the extra storage, since it wasnt designed to do this we can assume that sometimes it might not work correctly.
Sure the tools and everything work fine with it all most of the time.
The reason flashing an official ROM seems to remedy the issues with Hard Resets is that if you reflash everything, the flash memory is refreshed back to the correct OS and ext_rom arrangement, then flashing an RBS ROM onto this area should in theory work fine thanks to the "spring clean" of the memory area.

mrvanx said:
Remember guys the Real Big Storage ROMs overwrite the ext_rom portion to use as the extra storage, since it wasnt designed to do this we can assume that sometimes it might not work correctly.
Sure the tools and everything work fine with it all most of the time.
The reason flashing an official ROM seems to remedy the issues with Hard Resets is that if you reflash everything, the flash memory is refreshed back to the correct OS and ext_rom arrangement, then flashing an RBS ROM onto this area should in theory work fine thanks to the "spring clean" of the memory area.
Click to expand...
Click to collapse
Thanks for clearing that up, though it was long those lines! (So close, but so far)

veyka said:
Thanks for clearing that up, though it was long those lines! (So close, but so far)
Click to expand...
Click to collapse
It wasnt until recently that I experienced any hard reset issues with any of the ROMs here, i noticed that leading up to a Hard Reset or freeze at the boot screen things such as file operations and running programs seemed to fail...with access denied errors and etc..
Also programs failed to save registry data aswell, coreplayer repeatedly asked for the activation key (which ofcourse ive got).
Leading me to believe that the storage portion of the OS was not working correctly...and since thats the part we have (pardon the term) misused )) then perhaps a reflash to the old configuration to give the storage area a flat format would do the trikc...which it did.
So its definatly advised, even if you havent experienced the issues, to one in a while before you flash a new ROM, flash an official ROM which uses and ext_rom aswell to give it a quick clean out.

lagoskon said:
I wanted to install PDACorner v22 RBSN over NRBSN and I flashed defore the See here for more info Dr Puttingham solution suggested ROM via SD.
I have done the SD Flash once more with my WWE ROM 3.54 and in both ROMS the ORDER of flashing parts on my Tytn 's screen was
Code:
IPL,Bootloader,ExtROM,GSM,OS
I know we all use dutty's nbh tool v1.1 for compiling RUU_Signed.nbh .
I dare to make a thought about this tool makes the RBS ROMS to Hard Reset, because it makes the order of flashing
Code:
IPL,Bootloader,OS,GSM
meaning it flashes the Radio after the OS.
Both Stock ROMS with EXTRom flashes the Radio before the OS.
So is there any chance of changing the order in dutty's tool and do the Radio flash before the OS???
In that way we can check if THIS is the problem (and solution) of Hard Resets
Please post your thoughts on my theory and I will contact dutty about this thread to see if he can change his tool
Click to expand...
Click to collapse
OK I FOUND IT WHAT YOU MEAN THE TOOL FOR IT IS htcRIE_0.4.0.49.exe as it opens the original ROM deletes ipl spl gsm and saves new orig rom with the order off flashing - splash splash extrom os

How-to fix: Problems with Bootloader ... and flashing.

Hello,
Does someone else have a similar problem?
Intro: some month ago I have successfully flashed my first HardSPL (1.40 OliNex), new radio (Radio v1.00.25.05) and several ROMs. Usually I flashed them directly from internal memory since I’ve found this way quite comfortable and IMHO also safer.
However, for flashing this way you have to able enter your bootloader...
And this is my first problem: after entering my bootloader I’ll get (after a while and a short show up of bootloader’s colorful screen) a grey screen with a message Trigger usb host…
After a while it is getting even scratches … and search and search ... so the only soft reset helps.
Does somebody possibly have a similar experience? Any tips?
FYI: my last ROM was A.Z.T.O.R. V7, however I admit, I didn’t make any hard reset after flashing (due to a mistake). Now I wanted to install a Duttys ROM. Since he recommends a newer version of HardSPL (1.93) I’ve been trying to upgrade… btw can somebody tell me where I can find it!? (I know where is the link, I have downloaded it personaly several times from differenet places, however there’s always written “signed” version on the *.nbh file! Is btw 1.93 signed version only?
And why can I see always just 1.40 in bootloader even when I’ve flashed 1.93 already?
And however I should rather ask this question Duttty personaly in his threat, why there is mentioned in bootloader ROM version 1.99 for V3.1 Duttys ROM?
Can you help me please to get out of this mess?
Many thanks in advance!
Regards, Marek
PS: Very last important question: when should I make the hard reset after flashing? Since it seems that my button tricky thing doesn really work, I am able to reset my XDA just from the menu... is there any problem? (When letting the system to start up properly first?)

[Q] About flashing newest stock rom with Hard SPL

Hi all, a question to anyone who may know the answer.
I have tried searching & reading but have only ended up twisting up my brain!
Ok, i have a touch diamond with Olinex unsigned 1.37 Hard SPL
I want to flash it with the newest HTC Europe stock rom but when i try to flash it, it starts and continues all the way to 100%, before giving me a error 270 - corrupted file image..
Tried downloading the rom again, different usb ports & pretty much everything else i can think of, to the point now that i just can't think of any other possible ways of doing it.
Can anyone help me out... pleeeeeeeease!

Sorry no quick answer as it soundsfrom your breif description like you are doing everything right...
What Radio and Rom are you on currently as this might give us some more clues as to what might be causing the issue?

I can freely flash between almost any rom that takes my fancy, just today i have flashed through aztor 2.0, duttys newest, vics 3.4, and the ultimate wwe.. trying to find a solution!
I can flash whatever radio i want, again with no issues. Maybe the links i have for the rom are corrupt? Like i said i've downloaded it twice, but still get that error after 100% completion.

adrenalin said:
I can freely flash between almost any rom that takes my fancy, just today i have flashed through aztor 2.0, duttys newest, vics 3.4, and the ultimate wwe.. trying to find a solution!
I can flash whatever radio i want, again with no issues. Maybe the links i have for the rom are corrupt? Like i said i've downloaded it twice, but still get that error after 100% completion.
Click to expand...
Click to collapse
You need to flash the newest stock rom using the internal storage method. Details are on the thread for the stock 2.03 rom

THe Internal Method is always the starting point....if that is not it then,
Yeah, when the error speaks about corruption, this generally means that there was a incompatibility issue. I've seen this problem and I don't recall if the incompatibility was the Hard SPL related or not. My suspicion is that it is .....

band27 said:
THe Internal Method is always the starting point....if that is not it then,
Yeah, when the error speaks about corruption, this generally means that there was a incompatibility issue. I've seen this problem and I don't recall if the incompatibility was the Hard SPL related or not. My suspicion is that it is .....
Click to expand...
Click to collapse
THe original 2.03 roms don't work on hard spl when used through the PC and give the error at the end on 100%.
Cooked versions flash succesfully normal ways however the original version will work properly via the internal storage method as discovered on the original 2.03 thread

I solved it by flasing the Olipro 1.93 hard SPL after flashing the stock 2.0 ROM.
As by everyone I had a corruption message on the screen after the 100% of flashing... So just flash Olipro 1,.93 over it and the diamond will startup with the new 2.03 ROM

can anyone give me a radio.nbh??

my GSM module has something wrong,i think.when i flash 6.0.it was failed.when i flash 6.1 which without radio.nbh. it was successful.and then,first time boot up.sys must be reboot.OK,reboot.it stop in the secondsplash.it can connect pc with the activesync.but the phone screen is the secondsplash....i dont know why...pleaes help me..
thanks~~

I'm having almost the same problem. When booting, my phone gets stuck at the second splash screen every time. I tried reflashing numerous different ROMs, but I get the same problem every time. Occasionally, with a Dopod factory ROM, I get it to boot to the "no SIM" menu in Chinese, but after tapping through the menus, it just restarts and gets stuck at the 2nd splash screen. I searched all over the internet for various radio ROMs, but I can't find ones specific for the Cavalier. I tried some for different HTC WM6 phones, but it stops at 7% and tells me that the ROM isn't right for the device. I'd like to try a new radio ROM if I can, so if anybody has one, can you post it???

ttknf said:
I'm having almost the same problem. When booting, my phone gets stuck at the second splash screen every time. I tried reflashing numerous different ROMs, but I get the same problem every time. Occasionally, with a Dopod factory ROM, I get it to boot to the "no SIM" menu in Chinese, but after tapping through the menus, it just restarts and gets stuck at the 2nd splash screen. I searched all over the internet for various radio ROMs, but I can't find ones specific for the Cavalier. I tried some for different HTC WM6 phones, but it stops at 7% and tells me that the ROM isn't right for the device. I'd like to try a new radio ROM if I can, so if anybody has one, can you post it???
Click to expand...
Click to collapse
I don't think this has to do with the radio. From my experience in testing out cooked ROMS and trying to cookm my own ROMS for the Cav, the filesystem is a bit temperamental with too many flashes. I have had to format my ROM filesystem half a dozen times to fix small glitches such as incomolete flashes and hard locks. I can throw together a radio ONLY update for you but I doubt it will fix anything. This post describes how to unbrick (or format you phone) but you will lose ALL of your data and do it at your own risk.
http://forum.xda-developers.com/showthread.php?t=428589&highlight=brick

ookba said:
I don't think this has to do with the radio. From my experience in testing out cooked ROMS and trying to cookm my own ROMS for the Cav, the filesystem is a bit temperamental with too many flashes. I have had to format my ROM filesystem half a dozen times to fix small glitches such as incomolete flashes and hard locks. I can throw together a radio ONLY update for you but I doubt it will fix anything. This post describes how to unbrick (or format you phone) but you will lose ALL of your data and do it at your own risk.
http://forum.xda-developers.com/showthread.php?t=428589&highlight=brick
Click to expand...
Click to collapse
I've already followed this process with MTTY numerous times, it had no effect. Also, when I did info 8 and task 2a, there were no bad blocks to begin with. Is there something else that can be done w/MTTY to fix things? It'd be great if you could dump that radio.nbh onto this thread just to see if that'll fix things.

ttknf said:
I've already followed this process with MTTY numerous times, it had no effect. Also, when I did info 8 and task 2a, there were no bad blocks to begin with. Is there something else that can be done w/MTTY to fix things? It'd be great if you could dump that radio.nbh onto this thread just to see if that'll fix things.
Click to expand...
Click to collapse
Here is the Radio (05_GSM.nb) in the nbh. It's the one from the Dopod shipped ROM but I checked the versions and the HTC one is the same version. Copy this nbh file to your ROM Update folder and flash away. Hard SPL is recommended. This is a straight radio dump and I am not responsible if you brick your phone.
Haven't uploaded yet, will upload shortly.

ookba said:
Here is the Radio (05_GSM.nb) in the nbh. It's the one from the Dopod shipped ROM but I checked the versions and the HTC one is the same version. Copy this nbh file to your ROM Update folder and flash away. Hard SPL is recommended. This is a straight radio dump and I am not responsible if you brick your phone.
Haven't uploaded yet, will upload shortly.
Click to expand...
Click to collapse
Are you gonna upload that radio rom?