INFO:- White screen after ROM flash

[mxlaser]

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.


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.


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.


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.

[pof]

LVSW rom uses Custom RUU v3.5 (http://forum.xda-developers.com/showthread.php?t=298737), 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?

[mxlaser]

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.

[pof]

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 (http://forum.xda-developers.com/showthread.php?t=298520) or in imate's new rom (http://forum.xda-developers.com/showthread.php?t=299597).

[adomad]

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.

[eznil]

LVSW rom uses Custom RUU v3.5 (http://forum.xda-developers.com/showthread.php?t=298737), 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?
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?

[jpxdude]

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.

[solid_wizard]

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..

[mart_haj86]

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.

[Olipro]

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.

[oliber]

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!

[akarandomjames]

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.

[Olipro]

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.

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

[akarandomjames]

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 ^_^

[SomeJoe]

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.


Now running LSVW 3/26. Very snappy! After getting it running correctly I reflashed to HARD-SPL v4.

[akarandomjames]

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.

[pello]

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

[SomeJoe]

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

[mart_haj86]

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?

[Olipro]

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?

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

[pello]

just want to say that i flashed the os with mtty successfully.....

[mart_haj86]

Is does report back FF, however I can get into my current OS ok, I used the 1.01MFG from the wiki pages, should I use yours instead?

[TechBill]

A question to those whom have a white screen issue,

Did you flash by selecting the Bootloader and Hard-SPL or did you selected "Force Using SSPL" instead?

[Olipro]

Is does report back FF, however I can get into my current OS ok, I used the 1.01MFG from the wiki pages, should I use yours instead?

in a word? YES

[mart_haj86]

Thanks Olipro you really are a great help, thanks for your time, Im SuperCID unlocking now, I guess I locked it before?? and once thats done I will load your version of 1.01MFG and press on from there. Thanks

[Olipro]

Thanks Olipro you really are a great help, thanks for your time, Im SuperCID unlocking now, I guess I locked it before?? and once thats done I will load your version of 1.01MFG and press on from there. Thanks

the SPL ignores the CID, doesn't change it so if you have a CID, you need to flash my patched one.

[jcespi2005]

the SPL ignores the CID, doesn't change it so if you have a CID, you need to flash my patched one.

So, in my understanding, the issue gets with a combination of CustomRUU and HardSPL? im i right?

[Olipro]

So, in my understanding, the issue gets with a combination of CustomRUU and HardSPL? im i right?

here's the definitive test;

flash with SSPL... see if it still is problematic, if so, we have an NBH issue.

if not... flash with Hard-SPL and with the new HTC RUU (not the one from CustomRUU)

[joshkerr]

I'm unclear how to do these steps:

3. Flash SPL-1.01MFG to your device
4. Flash OS.nb to device.

There is no information regarding doing a flash from a .nb file. Also, is there anyway to fix the white screen problem without having to load a terminal like MTTY?

[oliber]

3) See the Wiki (http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG) with 1.01 Olipro MFG here (http://forum.xda-developers.com/showthread.php?t=296722)
4) See above.

At least, i presume you're referring to your 1.01 Olipro MFG package? Excuse my n00bism, but i assume we would be flashing Spl-Olipro-MFG.nb on first?

[Olipro]

3) See the Wiki (http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG) with 1.01 Olipro MFG here (http://forum.xda-developers.com/showthread.php?t=296722)
4) See above.

At least, i presume you're referring to your 1.01 Olipro MFG package? Excuse my n00bism, but i assume we would be flashing Spl-Olipro-MFG.nb on first?

DO NOT TRY TO FLASH 1.01.Oli WITH LNBS.

package it as an NBH and flash that way.

[joshkerr]

I put the hard-SPL on my device. I opened MTTY and I don't get the option to enable USB even though the bootloaded is loaded and the device is connected. why?

Can someone post step by step instructions to fix this?

[joshkerr]

I do not know how to make an NBH file. Can you please make this easier for me? I'm new to this. (Obviously.)

[Olipro]

I do not know how to make an NBH file. Can you please make this easier for me? I'm new to this. (Obviously.)

sure, do you have a gun?

just kidding.

use ROM koch to generate it, or my ROMBaker, or manually with nbhgen, your choice.

[joshkerr]

I will paypal $20 USD to the person who helps me get the white screen away. Offer only available for the next 20 minutes.

[joshkerr]

sure, do you have a gun?

just kidding.

use ROM koch to generate it, or my ROMBaker, or manually with nbhgen, your choice.

Do I only need to package the OS.nb with ROM Cooker? What should the saved file name be?

[joshkerr]

Okay, I give up. Where did I put that gun?

I FART IN THE GENERAL DIRECTION OF YOUR WIKI.

[LegolasTheElf]

Check your PM I can fix it!

BTW, I should mention that I do have special tools that Oli made special for me to fix these things.. Also, I will actually do the typing/etc. for you to fix it. This is a full-service solution! :)

[finch]

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.

can you post the RUU you used? I think I am getting it. If I use the RUU I hope you will post and the .nbh file for this update it should work?

I am running Vista and I have done the updates from here but I cannot get the NBHextract to work??? That is why I would like to try your RUU if I am reading this right.

Thanks to everyone.

[finch]

Check your PM I can fix it!

BTW, I should mention that I do have special tools that Oli made special for me to fix these things.. Also, I will actually do the typing/etc. for you to fix it. This is a full-service solution! :)

Can you post for us all?? Why is it private?

O sorry I see why it private. Oli made tools and you are CHARGING ppl for help. Hey I have never had anything bad to say about this site until now. IMHO you should leave the site and start your own website charging ppl for help using tools someone else made you. I thought this site was for sharing. I have donated cause I have been so happy with all everyone does. Maybe Oli should charge you or are you giving him all the money since he did all the work. INstead of logging into a persons pc POST A PUBLIC FIX. I would never let someone of your moral caliber into my pc.

If this was not a one person helping and teaching the next I would not feel so pissed off. I am a mod at a different kind of site and we would never stand for a member talking down to others the way you do and charging people for what others have done for free.

I am sorry but I have read many post today with you arguing and just being plan nasty to many here.

So sad for XDA.

[oliber]

Ok, what i did!

Flash Hard-SPL 1.10 Oli (http://forum.xda-developers.com/showthread.php?t=296722) to the device
Used ROMBaker (http://forum.xda-developers.com/showthread.php?t=294523) to create a LVSW-2007-03-26 OS with SPL 1.01 MFG Olipro

Uber nub guide to doing this:
Extract 03_OS.nb from RRU_signed.nbh within the LVSW release (using ROMBaker or NBHExtract)
Add Spl-Olipro-MFG.nb as SPL
Add 03_OS.nb as OS
Ensure the above are in the Workshop directory of the packager when you add them!
Click Generate NBH
Copy output RRU_signed.nbh to same directory as, and run ROMUpgradeUt.exe

[Olipro]

this is less than ideal... there's something screwy with the images, the fact that a single file can be removed to fix it is disturbing.

[finch]

Congrats. Any chance you posting it?

[Olipro]

Congrats. Any chance you posting it?

post what? what are you talking about

[finch]

post what? what are you talking about

Sorry I shuold have quoted oliber. I meant the nbh he complied.

[mxlaser]

My testerments exactly.

LegolasTheElf, seriously "I" created this thread as i told you there was a problem. You argued black and blue there wasn't and others and myself were simply idiots who couldnt read.

Clearly it was you who was the idiot, as clearly there was and still is an issue.

Dont post yoru crap in my thread, offering to get paid to fix a problem than can be publically fixed for free...

Currently the method i posted right at the start is the only 100% sure fire fix NOT to get the white screen. All your doing is preying on the noobs that are to scared and doing what "i" suggested to fix their white screens.... Maybe i should be getting some interlectualy royalties from you when your ripping (oops sorry charging) these people off...

Either contricute to this thread with helpful, free public fixes, or f**k off and solicit elsewhere for your rip off, noob preying bullshit scam.

"ooh, i know how to work MS remote desktop and click a few files i read on a forum, so should chrage noobs for that privalige" Wow all those certificates must be doing you so well if you have to constantly beg for $2.50 a minute on a public forum...

You'd of earnt more money from donations like others have by being a genuine, nice helpful person.

Anyway, back kon to me and others HELPING, FOR FREE those experiencing the white screen.

I am almost 100% certain this issue resides with the HARD SPL and the extra storage patch.

After hours and sleepless night, and so many flashes i think the NAND in my dopod was hot enough to fry a breaky for me, i've come to the comclusion, i have 100%, no issue success with all ROMS, using 1.01MFG and MTTY flashing each part seperatly. Not one time has a white screen appeared, with ANY rom, and i've tested all the current WM6 roms.

I d/l'd and tried the latest LVSW rom (26/3) and have exactly the same issue when using the packaged RUU to install it. However, when i use MTTY, its perfect every time.

I would suggest the following steps

1. Load into the bootloader mode (HOLD POWER/OK buttons and press soft reset)

2. Flash SPL-1.01MFG onto your device (Read wiki info and file links here (http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG))

3. Once flashed, reboot and do step one again to get back into boot mode. You should now see your boot as 1.01MFG

4. Use NBHextract to extract 06_OS.nb file from RUU_signed.nbh file found in downloaded rom package.

5. Load up MTTY, follow steps in the wiki for the 1.01MFG on how to flash OS.nb (OS.nb is the 06_OS.nb file renamed to make it easier)

6. Once flash is complete, the latest rom is installed and you won't have a white screen

7. Now flash Hard SPL v4 onto your devic for saftey reasons.

And this fix is EASY to do, 100% works every time, and completly free. Its a orkaround obviously until the issue is resolved however it works, its safe as long as you follow it accuratly and best of all, im not hitting you up/begging you for $2.50 a minute to help you either!

[Olipro]

I am almost 100% certain this issue resides with the HARD SPL and the extra storage patch.

I've got someone flashing with SSPL right now.

let me inform you I have NOT changed the flashing procedure at all, that is stock HTC code aside from bad blocks, so it has FUCK ALL to do with me.

however, the test will be to try flashing with 1.09 and then with a CID only patched 1.11, so that will also be tried if SSPL is successful.

if SSPL is not successful, or someone already knows it isn't, please pipe up, because we'll prove once and for all it's jack shit to do with the bootloader.

[Olipro]

SSPL flash completed.

the result? WHITE SCREEN.

proving once and for all that it's a problem with the image, not the SPL.

I would suggest LVSW fix his image.

and before anybody says any stupid fucking comments: SSPL is 1.09 with 3 single patches that a) set SuperCID and b) remove cert signing, the NAND interactions etc are completely unmodified, since it's failing with SSPL, this conclusively proves there's an issue with the NBH.

end of story, that's all she wrote

[mxlaser]

I've got someone flashing with SSPL right now.

let me inform you I have NOT changed the flashing procedure at all, that is stock HTC code aside from bad blocks, so it has FUCK ALL to do with me.

however, the test will be to try flashing with 1.09 and then with a CID only patched 1.11, so that will also be tried if SSPL is successful.

if SSPL is not successful, or someone already knows it isn't, please pipe up, because we'll prove once and for all it's jack shit to do with the bootloader.

Sorry i should of clarified what i meant a bit better... Your bootloader is 100% fine, no issues whatsoever!! :Dand thank you for it!! i didnt mean to offend as its nothing to do with that as such.

where i think the issue lies is that our devices, when flashing are expecting certain sizes of files. Your boot loader is the start, followed by the flashing procedure etc. Im convinced (although without proof just my own workings and problem solving) this issue is flashing, but the rom isnt the full expected size it should be.

As i said, its confusing and interesting that removing/adding a single file and re-compiling makes a massive difference and it flashes.... I decided it wasnt the roms though, as i can flash 100% everytime using MTTY.

i don't think your bootloader has anything to do with it, other than its all part of the pack.... :D:D sorry for the confusion! :)

[mxlaser]

SSPL flash completed.

the result? WHITE SCREEN.

proving once and for all that it's a problem with the image, not the SPL.

I would suggest LVSW fix his image.

and before anybody says any stupid fucking comments: SSPL is 1.09 with 3 single patches that a) set SuperCID and b) remove cert signing, the NAND interactions etc are completely unmodified, since it's failing with SSPL, this conclusively proves there's an issue with the NBH.

end of story, that's all she wrote


Thats good news, but it isnt just LVSW's version experiencing this issue though. But at least it narrows it down to "what is the fault"

And, once again, sorry for the way i typed where i thought the issue was without clarifying my thinking on it as i knew it wasnt the HARDSPL as such, just got in the crossfire of my explanation due to being the first thing there...

i do seriously however beleive its a compiling/flashing/extra storage issue with the roms.

[Olipro]

i don't think your bootloader has anything to do with it, other than its all part of the pack.... :D:D sorry for the confusion! :)

ok, but it certainly seemed that way.

anyhow... I suggest you try dumping his ROM into an IMGFS and then DON'T REMOVE ANY FILES. but instead, reconstruct it the same way as before and flash it... see if it whitescreens then.

I get the feeling LVSW is constructing his ROMs differently to you, and the way you're doing it makes them valid again; it's not the file removal that fixes it, it's the reconstruction, so try it.

(or better yet, remove the file, and add it back again)

[mxlaser]

ok, but it certainly seemed that way.

anyhow... I suggest you try dumping his ROM into an IMGFS and then DON'T REMOVE ANY FILES. but instead, reconstruct it the same way as before and flash it... see if it whitescreens then.

I get the feeling LVSW is constructing his ROMs differently to you, and the way you're doing it makes them valid again; it's not the file removal that fixes it, it's the reconstruction, so try it.

(or better yet, remove the file, and add it back again)

WIll do now.

And once again, sorry for my shit explanation... what im thinking and my methods aren't always conveyed the right way when trying to explain it. add into it my shit typing as the keyboards crappy and keys dont press and no wonder im misunderstood! :)

Anyway, thanks for all the great effort and the bootloader. I only suggest going to 1.01MFG as i dont know if the 1.30 hard SPL allows you to flash OS files in MTTY, if yes, how :)

[oliber]

Just finished upping the bake that i managed to http://www.megaupload.com/?d=AGCNBYHB.

Please note: THIS IS SUPPLIED WITH ZERO WARRANTY! If it runs away with your [dog/cat/wife/child/gimp/all of the above], it wasn't me!

Please don't credit me for this, i've only followed the instructions on this thread so far! :)

As per above post, this is LVSW-2007-03-26 OS + SPL 1.01 MFG Olipro.

If you want LVSW-20070326 OS on it's own, check the LVSW thread, this is provided to assist people with the whiteout to get up and running.

[joedoe]

Can the source of the problem be in tadzio's more storage tool?

[finch]

Just finished upping the bake that i managed to http://www.megaupload.com/?d=AGCNBYHB.

Please note: THIS IS SUPPLIED WITH ZERO WARRANTY! If it runs away with your [dog/cat/wife/child/gimp/all of the above], it wasn't me!

Please don't credit me for this, i've only followed the instructions on this thread so far! :)


Thanks but I just finished the mtty upgrade.

[Penske MB]

Can you indicate the file? OS only??

thx

Just finished upping the bake that i managed to http://www.megaupload.com/?d=AGCNBYHB.

Please note: THIS IS SUPPLIED WITH ZERO WARRANTY! If it runs away with your [dog/cat/wife/child/gimp/all of the above], it wasn't me!

Please don't credit me for this, i've only followed the instructions on this thread so far! :)

[finch]

My testerments exactly.

LegolasTheElf, seriously "I" created this thread as i told you there was a problem. You argued black and blue there wasn't and others and myself were simply idiots who couldnt read.

Clearly it was you who was the idiot, as clearly there was and still is an issue.

Dont post yoru crap in my thread, offering to get paid to fix a problem than can be publically fixed for free...

Currently the method i posted right at the start is the only 100% sure fire fix NOT to get the white screen. All your doing is preying on the noobs that are to scared and doing what "i" suggested to fix their white screens.... Maybe i should be getting some interlectualy royalties from you when your ripping (oops sorry charging) these people off...

Either contricute to this thread with helpful, free public fixes, or f**k off and solicit elsewhere for your rip off, noob preying bullshit scam.

"ooh, i know how to work MS remote desktop and click a few files i read on a forum, so should chrage noobs for that privalige" Wow all those certificates must be doing you so well if you have to constantly beg for $2.50 a minute on a public forum...

You'd of earnt more money from donations like others have by being a genuine, nice helpful person.

Anyway, back kon to me and others HELPING, FOR FREE those experiencing the white screen.

I am almost 100% certain this issue resides with the HARD SPL and the extra storage patch.

After hours and sleepless night, and so many flashes i think the NAND in my dopod was hot enough to fry a breaky for me, i've come to the comclusion, i have 100%, no issue success with all ROMS, using 1.01MFG and MTTY flashing each part seperatly. Not one time has a white screen appeared, with ANY rom, and i've tested all the current WM6 roms.

I d/l'd and tried the latest LVSW rom (26/3) and have exactly the same issue when using the packaged RUU to install it. However, when i use MTTY, its perfect every time.

I would suggest the following steps

1. Load into the bootloader mode (HOLD POWER/OK buttons and press soft reset)

2. Flash SPL-1.01MFG onto your device (Read wiki info and file links here (http://wiki.xda-developers.com/index.php?pagename=Hermes_BootloaderMFG))

3. Once flashed, reboot and do step one again to get back into boot mode. You should now see your boot as 1.01MFG

4. Use NBHextract to extract 06_OS.nb file from RUU_signed.nbh file found in downloaded rom package.

5. Load up MTTY, follow steps in the wiki for the 1.01MFG on how to flash OS.nb (OS.nb is the 06_OS.nb file renamed to make it easier)

6. Once flash is complete, the latest rom is installed and you won't have a white screen

7. Now flash Hard SPL v4 onto your devic for saftey reasons.

And this fix is EASY to do, 100% works every time, and completly free. Its a orkaround obviously until the issue is resolved however it works, its safe as long as you follow it accuratly and best of all, im not hitting you up/begging you for $2.50 a minute to help you either!



THANKS!!!

worked 100% just like you said. You are a prime example of why someone else got my blood pressure up.

I am going to donate $10 to XDA and $10 to the developer of your choice. PM me who.

Thanks a million.

[Penske MB]

I assume it is an OS only ROM, right?? I would really like to try that!!!


Just finished upping the bake that i managed to http://www.megaupload.com/?d=AGCNBYHB.

Please note: THIS IS SUPPLIED WITH ZERO WARRANTY! If it runs away with your [dog/cat/wife/child/gimp/all of the above], it wasn't me!

Please don't credit me for this, i've only followed the instructions on this thread so far! :)

[oliber]

I've updated the post above to clarify, this is LVSW-20070326 + SPL 1.01 MFG Olipro to assist users with the whitescreen effect.

[Olipro]

I've updated the post above to clarify, this is LVSW-20070326 + SPL 1.01 MFG Olipro to assist users with the whitescreen effect.

can someone try this;

Dump NB files from LVSW.

recreate NBH using nbhgen (nothing else) and try it

[Penske MB]

I love to do that Oli, but I am a noob...

I rather pay for it. When WM6 came out, I'll be first to get my copy. Currently wait on the i-mate's new PDA with WM6 pre-load.



can someone try this;

Dump NB files from LVSW.

recreate NBH using nbhgen (nothing else) and try it

[TechBill]

Saw the result in another post

[mxlaser]

OK, Olipro:

Dumped OS.nb from LVSW 26/3

Made a new NBH as suggested. Flashed using RUU, had the same white screen. Flashed using MTTY and worked.

now this was OS only, RUU obviously had the SSPL i chose to force SSPL.


I'll be able to type up, and post all my testing results (in the hope someone picks up something i missed) later tonight (its 12:26pm here in Oz, so supposed to be working)

Finch:

Appreciate your kindness mate. I'd be hard pressed to choose between JasJamming, LVSW and Olipro...

[waffle418]

oli im trying it now... let you know how it goes... its loading using hardspl so im not too worried

[Olipro]

oli im trying it now... let you know how it goes... its loading using hardspl so im not too worried

yeah, I should point out... this can't do any harm.

[waffle418]

yeah, I should point out... this can't do any harm.

lol yeah the whole reason I got the balls to run this test!

[LegolasTheElf]

LegolasTheElf, seriously "I" created this thread as i told you there was a problem. You argued black and blue there wasn't and others and myself were simply idiots who couldnt read.

Clearly it was you who was the idiot, as clearly there was and still is an issue.

Dont post yoru crap in my thread, offering to get paid to fix a problem than can be publically fixed for free...

Currently the method i posted right at the start is the only 100% sure fire fix NOT to get the white screen. All your doing is preying on the noobs that are to scared and doing what "i" suggested to fix their white screens.... Maybe i should be getting some interlectualy royalties from you when your ripping (oops sorry charging) these people off...


Let me take your rants in order:

1) You posted saying there was an issue. I didn't believe you. Thought you couldn't read. I still think you (mxlaser) in particular are a wanker, but, apparently you were right. There is an issue. Oli and I have been working hard in the background to test a fix, and figure out the exact issue. We think we have an answer to why, but, still doing a few more tests.

2) Fix for free: sure. And, I *could* change my own oil too. But, for those people who aren't as gifted as you with computers :rolleyes: may not know how to do it, and may not know how to do some of the stuff I know how to do. Besides, since Oli is a friend of mine, I can get him to make me stuff on the fly that pertains to the situation I'm seeing at the moment I'm seeing it.

3) Actually, no. You're method could result in a brick. 1.01MFG will still cause a brick in many circumstances. The original 1.01MFG that you used does NOT fake the SuperCID setting. You're just LUCKY it didn't screw up on you.

Oli and I think we might have figured a way to do this SAFELY. Once we get it done, we'll post.

4) You really need to take a chill pill. We VOLUNTEER our time--I post a LOT of helpful stuff. I don't even ask for donations. All I ask for is that **IF YOU WANT TO USE MY SERVICES 1-on-1**, to pay for it. If you don't want 1-on-1 advice/help, then you don't need to pay. I'll still help generally, but, I can't really devote an hour or more of time to ONE person if they can't figure it out themselves. I'll answer specific questions, but a general "how do I do this thing" is slightly outside of what almost anyone will do on here. Especially when we're only seeing the issues out of relative noobs. We didn't have any reason to suspect that it was more than just not reading directions.

I might add, there's a WHOLE lot of people who brick their phones in general on here. Yet Oli, Pof, myself, and many more who know what they're doing don't.. Even when we didn't have Oli's cool BL's to save us. Given the fact that people brick their phones and then whine, while most of the more senior members don't have problems, leads one to believe that gee.. It's because they don't read. Your bad attitude just makes us not want to release this stuff at all. I mean, Jas even said he'd not release Black 1.3 for a day or so because he didn't want to be attacked like me.

So, chill. And, do me a favor--don't tell people to use 1.01MFG -- it's a good way to brick their phone if they don't know what they're doing.

[tadzio]

Can the source of the problem be in tadzio's more storage tool?


I thought about this, and came to the conclusion that the whitescreen symptoms do not match any possible malfunction scenario I can think of.

Some background information: My version of the Imgfs tools are modifications to mamaich's tools. His BuildImgfs (which is my "ImgfsFromDump") copies all the files into an in-memory image and keeps track of the used memory blocks in a map quite similar to a FAT. BuildImgfs then searches for the highest used sector and outputs this number as used space. Nonetheless he writes this in-memory image to a file that has the same size as the original. My version, on the other hand, takes this highest used secto, rounds it up to the next full block of 128k, and then writes out the file only up to that address.

My next modifications are in ImgfsToNb (make_imgfs). The original mamaich tools place the imgfs image to where it was before, while my version puts it to where the partition table says it should be. The difference is 256kByte - another region Microsoft reserved for flash updates through Windows Update.

The next modification is that I patch the partition table so that the Imgfs partition ends (and the Storage partition starts) right behind the rounded-up 128k block containing the highest used sector.

My last modification is that I do not write back the extracted "extra" 8-byte sector headers in the Imgfs partiton, but create new ones - four bytes a running counter, the next four the constant value 0xFFFBFFFD. Most sectors in the original ROMs have that signature. Some have F8, F9 or FA in place of the FB; unused blocks have FF. As I moved (see above) the whole Imgfs 256kB to the front, it wouldn't have made much sense to keep the original values.



So, what could have gone wrong?

1. I may have screwed up the rounding up of the last used sector to the last used block. I don't think I did, as this is not a very complicated operation :-), but let's assume for a moment that I did. Alternatively, already mamaich's code might have a bug where his memory map does not cater for all the files. I haven't analysed his code, so I can't tell.

In this case, the Storage partition would overwrite some of the files in the imgfs (the ones right at the end of the image). If I understand the whitescreen symptoms correctly, the "welcomehead*.*" (forgot the exact name) is not displayed. As ImgfsFromDump goes through the list of files in the order given by Windows, i.e. in alphabetical order, and if I indeed cut off the Imgfs partition so early that welcomehead*.* is missing, then all files "behind" it should also be missing. I think that would lead to much more desastrous results than just a white screen. As I said, symtoms do not match.
But anyway, just to make absolutely sure, could someone just check if that file and other files whose names start with x, y, or z are uncorrupted in lvsw's ROM?

2. It could also be that I put the whole Imgfs is the wrong place. However, I do not modify the start of that partiton in the partition table, so if I put it in the wrong place, the boot loader would not be able to find the header and thus the whole imgfs at all, and consequently the phone wouldn't boot at all. So, again, the symptoms do not match.


3. The four bytes in the sector headers may actually mean something. However, so far it was consensus that they may get used for Windows Update, but not during normal operation (as they are outside the visibility of the file system). And the relationship between a sector four-byte-value and its contents had been lost in all ROMs ever compiled with mamaich's tools, with no visible side effects so far.

4. It may be that lvsw's ROM's Imgfs size is, coincidentally, very near a 128kB sector boundary. I do not exactly know what the bootloader will do when it encounters bad blocks in the imgfs area during flashing. I would assume it skips the block, pushing the rest of the imgfs up in address space. Then, again, the imgfs would leak into the area reserved for Storage (if the bootloader is a bit stupid; if it's smart, it should sense that there's not enough spare good blocks, and warn the user). The result is the same as in #1 above.

The ultimate proof would be the following experiment, which I cannot currently perform due to lack of time. But maybe someone else can do it:

- extract lvsw's ROM into bepe's kitchen. You need also dumprom, ROMMaster, and bepe's Package tool. I can provide detailed instruction if someone wants them.

- recreate lvsw's ROM without any changes, flash it and check if the problem persists. Note that some posts here suggest that even flashing a perfectly good ROM on a device that had the problem will not cure it, so you probably should use the posted method to fix the problem before you flash the recreated lvsw ROM.

- if the problem is still there, recreate lvsw's ROM using the original mamaich's tools, and flash it. If that then fixes the problem, my imgfs tool versions are at fault.

Any volunteers?

However, I have a feeling that lvsw uses some techniques we do not yet know when he makes his ROMs. One indication is that in his previous version it wasn't possible to dump default.hv to .rgu files. And maybe something has gone wrong with his techniques. (Don't get me wrong - I still admire what he did and does for the community!)

Cheers
Daniel

[waffle418]

lol yeah the whole reason I got the balls to run this test!

Oli, using the extract .nbh and recompile, it did not work and I'm staring at a white screen.

[waffle418]

trying koch's kitchen.... running the nbhgen.exe and nbhextract.exe had no effect

[Olipro]

Oli, using the extract .nbh and recompile, it did not work and I'm staring at a white screen.

ok, problem does not lie with the NBH.

someone dump LVSW's OS into an IMGFS using a different toolset
then reconstruct the dump, I'm thinking original IMGFS + aChef/aWaiter.

bepe's presumably is also valid, so either one

[mxlaser]

Let me take your rants in order:

1) You posted saying there was an issue. I didn't believe you. Thought you couldn't read. I still think you (mxlaser) in particular are a wanker, but, apparently you were right. There is an issue. Oli and I have been working hard in the background to test a fix, and figure out the exact issue. We think we have an answer to why, but, still doing a few more tests.

So im a wanker because i got frustrated as did MANY others at your blatant "we're idiots" attitude. Simply put, i KNEW there was a problem, and you dismissed it thinking you were top shit. As far as wankers go, that easily tops the definition. You personal opinion of me matters nothing to me. Your attitude sucked. Olipro, Pof, LVSW and many others have been not only polite, but also very thankful for me helping them out a bit as well. (it seems)

2) Fix for free: sure. And, I *could* change my own oil too. But, for those people who aren't as gifted as you with computers :rolleyes: may not know how to do it, and may not know how to do some of the stuff I know how to do. Besides, since Oli is a friend of mine, I can get him to make me stuff on the fly that pertains to the situation I'm seeing at the moment I'm seeing it.
I appreciate Oli's a friend, and your working on this with him. However, in reality if it wasn't for my "wanker'ish" attitude to you dismissing me and others with our problems, you and Oli and others wouldnt be working on a fix, you'd still be in your own world praising yourself for public ridiculing me and many others.

3) Actually, no. You're method could result in a brick. 1.01MFG will still cause a brick in many circumstances. The original 1.01MFG that you used does NOT fake the SuperCID setting. You're just LUCKY it didn't screw up on you.

Hence why i said, follow my way exactly to what i've said, and as they are only flashing OS, and they can still get into bootloader, flash HArdSPL, and reflash in case of bad blocks, its more than possible to recover at this time.


4) You really need to take a chill pill. We VOLUNTEER our time--I post a LOT of helpful stuff. I don't even ask for donations. All I ask for is that **IF YOU WANT TO USE MY SERVICES 1-on-1**, to pay for it. If you don't want 1-on-1 advice/help, then you don't need to pay. I'll still help generally, but, I can't really devote an hour or more of time to ONE person if they can't figure it out themselves. I'll answer specific questions, but a general "how do I do this thing" is slightly outside of what almost anyone will do on here. Especially when we're only seeing the issues out of relative noobs. We didn't have any reason to suspect that it was more than just not reading directions.

I might add, there's a WHOLE lot of people who brick their phones in general on here. Yet Oli, Pof, myself, and many more who know what they're doing don't.. Even when we didn't have Oli's cool BL's to save us. Given the fact that people brick their phones and then whine, while most of the more senior members don't have problems, leads one to believe that gee.. It's because they don't read. Your bad attitude just makes us not want to release this stuff at all. I mean, Jas even said he'd not release Black 1.3 for a day or so because he didn't want to be attacked like me.

I message JasJamming about the release. Obviuosly you spin it to be the attack, but had he released it and had all this issues, the headaches would of been far worse. As it is, i praise the fact he's held onto it and waits till this issue is resolved as its the best thing for everyone concerned.

I didnt mind you telling me i did it wrong once, but having to repeatedly tell, describe and go off that it was done right, your blatant intolerance for noobs obviously has finally broke, as you have no patience or respect for us.

The fact also you dismiss me and everyone without first asking us to qualify the problem for you to dismiss this yourself, i find it pathetic.


So, chill. And, do me a favor--don't tell people to use 1.01MFG -- it's a good way to brick their phone if they don't know what they're doing.

Its a workaround that in most cases can be resolved and works. It worked before any of the HardSPL files and custom RUU files where around.

Anyway, i don't want a bitch fest. I also don't want you thinking your top shit and trying to belittle people when in fact, so far, you've not only pissed me off a LOT, and a lot of other people that have posted a displeasure in your manner and tone in which you "try" to help.

Your opinion im a wanker is overshadowed by the thanks i've received for actuallly helping people, and the comments you've received about soliciting and generally not helping and preying on others misfortune.

The 10mins it takes to write an indepth guide would help heaps of people, but of course, would then reduce your $2.50 minute income so instead your working behind the scenes and continuing to attack me rather than saying "look i was quick to dismiss, that pissed you off, sorry for being an arse, lets fix this, can you share your results"

I'll be donating money to Oli (as your firend, maybe he can shout you a drink) as a thanks for all his efforts as he's really tried to help, not just behind the scenes but verbally in this thread as well.

[jasjamming]

CAN EVERYONE JUST SHUT THE FUCK UP ONCE AND FOR ALL!

get over it and move on, this is now really getting out of hand!

PLEASE :)

[joshkerr]

I originally had the white screen error and LegolasTheElf logged on to my workstation and helped me fix the issue. He was very professional and was quick to debug the issue. He had access to some of the developers who wrote the tools we use to upgrade our phones which in the end was very helpful. It took him about an hour to resolve the issue. The whole experience cost me $95 which when compared to the cost of a new phone seemed worthwhile.

My problem had more to do with the bootloader and less with the OS. Oli's 1.10 and prior versions seemed to work okay but when 1.30 was on there, it didn't work at all. I'm really not too familiar with any of this so you should really ask LegolasTheElf.

[joedoe]

@tadzio:

Wow, you message deserves to be published in a scientific magazine. Thank you for the detailed explanation. However as a professional programmer I know that there is no completely bug free programs (well, almost).

Just two points:

1. I believe that previous LVSW builds didn't have that white screen problem
2. Latest WM VI Black Edition produces white screens also.

And both are using now the more memory tool. Sure it may be just a co-accident, who knows...

[Olipro]

Hence why i said, follow my way exactly to what i've said, and as they are only flashing OS, and they can still get into bootloader, flash HArdSPL, and reflash in case of bad blocks, its more than possible to recover at this time.

no, you're wrong I'm afraid, if they haven't SuperCID'd their device, this will NOT work.

they MUST use the modified 1.01 I created to be able to do what you're suggesting if they haven't SuperCID'd... and if they manage to make their OS stop booting, well then they're right up shit creek.

[mxlaser]

no, you're wrong I'm afraid, if they haven't SuperCID'd their device, this will NOT work.

they MUST use the modified 1.01 I created to be able to do what you're suggesting if they haven't SuperCID'd... and if they manage to make their OS stop booting, well then they're right up shit creek.

I stand corrected. What needs to be done to tweak my way to make it safer, yet still get it to work as a current workaround so it can be fixed.

[Olipro]

I stand corrected. What needs to be done to tweak my way to make it safer, yet still get it to work as a current workaround so it can be fixed.

what we really need to do is determine the root cause of the problem.

that's why I feel the OS files should be dumped into a folder as files and the reconstructed with a separate toolchain (buildimgfs anyone?) and then converted to the nb with aChef/aWaiter and flashed.

[mxlaser]

I originally had the white screen error and LegolasTheElf logged on to my workstation and helped me fix the issue. He was very professional and was quick to debug the issue. He had access to some of the developers who wrote the tools we use to upgrade our phones which in the end was very helpful. It took him about an hour to resolve the issue. The whole experience cost me $95 which when compared to the cost of a new phone seemed worthwhile.

My problem had more to do with the bootloader and less with the OS. Oli's 1.10 and prior versions seemed to work okay but when 1.30 was on there, it didn't work at all. I'm really not too familiar with any of this so you should really ask LegolasTheElf.

So, it took an hour to flash an OS that takes no more than 10 mins.

Im not going to argue or bitch about this. LegolasTheElf, yoru charge what you want, and do it however you want. Its your life.

Im here to try and help people for free, and so far have had a fair few kind possts and PM's thanking me for that.

Im going to bow out now, as im sick of all the shit and bitch fights.

[Olipro]

So, it took an hour to flash an OS that takes no more than 10 mins.

Im not going to argue or bitch about this. LegolasTheElf, yoru charge what you want, and do it however you want. Its your life.

Im here to try and help people for free, and so far have had a fair few kind possts and PM's thanking me for that.

Im going to bow out now, as im sick of all the shit and bitch fights.

might I suggest the topic be put back on track now and someone please pick up the gauntlet and try dumping and rebuilding this ROM

[LegolasTheElf]

@mxlaser Listen you little bitch. I posted a cab to fix a problem immediately after I saw it (commmgr). I uploaded the first non-radio installer. I was also johnny on the spot when the previous rom was suspected of having an issue and created an OS only version immediately. I've been on here, and doing a lot of stuff to HELP people like YOU be able to run WM6 on their phone.

Why do you insist on pumping up your own ego? Everything you've posted to me is rude, nasty and very condescending. I'm not suggesting, and have NEVER suggested that I'm top shit around here. I think Oli, Pof, Dutty, and many more are better than I at this whole phone thing.. But, you seem intent on making everyone thing you're the best. You're really nothing. You have a workaround that isn't even that great. If you can't get into activesync and aren't supercid, and are running 1.01mfg, you can brick your phone. But, I didn't see YOU creating any fail-safe way to fix the issue, you're just posting a crappy workaround.

For those with a white screen, downgrade to the NON EXTRA ROM VERSIONS and we'll have a solution for you soon. Listening to mxlaser can brick your phone if you're not careful.

[LegolasTheElf]

I originally had the white screen error and LegolasTheElf logged on to my workstation and helped me fix the issue. He was very professional and was quick to debug the issue. He had access to some of the developers who wrote the tools we use to upgrade our phones which in the end was very helpful. It took him about an hour to resolve the issue. The whole experience cost me $95 which when compared to the cost of a new phone seemed worthwhile.

My problem had more to do with the bootloader and less with the OS. Oli's 1.10 and prior versions seemed to work okay but when 1.30 was on there, it didn't work at all. I'm really not too familiar with any of this so you should really ask LegolasTheElf.
Thanks Josh!

Although, we're still figuring out the exact cause, but, you'll be good to go :)

[Olipro]

Thanks Josh!

Although, we're still figuring out the exact cause, but, you'll be good to go :)

of course... he's eating ramen noodles for a week now.

[mxlaser]

Look, this is pathetic, and clearly being stupid.

Every forum has a multitude of personalities in it, ours clash clearly. I'll back off, hopefully you do the same.

My fix works. I didnt claim anything else other than that. I understand there are a lot of people that simply fail to read or do the basic things and its frustrating for you and many others on here, i get pissed of many times, reading fixes then two posts later "how do i do this" about the post above.

Your riled up, the "listen you little bitch" gave that away :p, so we'd better leave this here. Both have our views, and its not progressing this fix at all... so lets get back to that and maybe try to be at least civil to one another.

[Olipro]

can someone tell me how many bytes are in the LVSW OS.nb please? (right click the file go to properties, give me the exact BYTE value)

[sassenach74]

might I suggest the topic be put back on track now and someone please pick up the gauntlet and try dumping and rebuilding this ROM

I'm willing to try this when i get home from work (urgh night shift) as I was one of the original posters with this problem. I am currently using black v1.1 atm just so my phone is usable (no white screen issue with going back to this one).

I'll grab a few hours sleep when i get home (stayed awake the whole of last night reading the wiki), then if it hasnt been done by anyone else, ill do it and post the results.

Neil.

[TechBill]

can someone tell me how many bytes are in the LVSW OS.nb please? (right click the file go to properties, give me the exact BYTE value)

03/26/2007 10:43 PM 59,504,640 06_OS.nb

[vp3G]

For those with a white screen, downgrade to the NON EXTRA ROM VERSIONSHate to stick my nose in this firestorm, but by "NON EXTRA ROM VERSIONS", do you mean sans "BIG storage", or sans "Extended ROM" (which I didn't think WM6 ROMs had anyway)?

[chymmylt]

03/26/2007 10:43 PM 59,504,640 06_OS.nb

I have the same size for 2007/03/25 just for the record :D

[LegolasTheElf]

Hate to stick my nose in this firestorm, but by "NON EXTRA ROM VERSIONS", do you mean sans "BIG storage", or sans "Extended ROM" (which I didn't think WM6 ROMs had anyway)?

It might be the tadzio big storage issue that's causing the problems. I've created a test rom to see if that's the issue. We'll know soon.

So, you can always flash the NON BIG STORAGE rom.. Extended rom is irrelevant!

[vp3G]

So, you can always flash the NON BIG STORAGE rom.. Extended rom is irrelevant!Thanks for clearing that up. And the NON BIG STORAGE rom is the one you posted here (http://forum.xda-developers.com/showthread.php?p=1187346&highlight=extrom#post1187346), correct?

[LegolasTheElf]

Thanks for clearing that up. And the NON BIG STORAGE rom is the one you posted here (http://forum.xda-developers.com/showthread.php?p=1187346&highlight=extrom#post1187346), correct?

No!

Let us finish this up and we'll post it.. I have a rom that's being tested now. Please, just grab a drink, watch some TV and it'll be finished soon :)

[vp3G]

No!

Let us finish this up and we'll post it.. I have a rom that's being tested now. Please, just grab a drink, watch some TV and it'll be finished soon :)No problem, just trying to figure out which ROM you were referring to. :)

[weinson]

No!

Let us finish this up and we'll post it.. I have a rom that's being tested now. Please, just grab a drink, watch some TV and it'll be finished soon :)

I realize folks are still trying to figure out the cause of the White Screen issue...my question is if I am someone who successfully upgraded to a new ROM (in my case the LVSW Rom posted the other day) am I at risk of the White Screen appearing in the future (sort of on its own volition, after a soft or hard reset), or once I have installed the new ROM and it is up and running, am I all set?

Said another way, once you have your newly cooked ROM with the "Non Big Storage" (as you refer to it) should the prudent user flash that ROM, or not worry if all is copasetic?

As you see from my sig, I have SPL 1.30Oli (Hard SPLv4) installed on my device (and had in installed before I flashed the LVSW ROM) ... so I presume I have some level of protection already layered in.

[LegolasTheElf]

I can't tell you much yet, as I don't want to have to retract the wrong bits, but, there has been a case where a hard-reset has caused the problem. HOWEVER, I wouldn't worry about it.. It's not like it's just going to happen one day when you wake up and use the phone. You're good for now.

[chymmylt]

I realize folks are still trying to figure out the cause of the White Screen issue...my question is if I am someone who successfully upgraded to a new ROM (in my case the LVSW Rom posted the other day) am I at risk of the White Screen appearing in the future (sort of on its own volition, after a soft or hard reset), or once I have installed the new ROM and it is up and running, am I all set?

Said another way, once you have your newly cooked ROM with the "Non Big Storage" (as you refer to it) should the prudent user flash that ROM, or not worry if all is copasetic?

As you see from my sig, I have SPL 1.30Oli (Hard SPLv4) installed on my device (and had in installed before I flashed the LVSW ROM) ... so I presume I have some level of protection already layered in.

I also have one of the successful installations. I have hard reset several times and even reinstalled successfully several times (I have not yet managed to white screen mine.) I am quite confident if it flashed correctly to your phone you are good and only have to worry about the white screen if you update the phone with a rom that is affected and are randomly unlucky. If you are good and going, I'd not flash it again until things get sorted out (unless you're joining the team of people trying to sort things out) but if you want to ensure you have a day to day working phone, leave it alone till the issue is figured out and I think you'll be just fine :D

[weinson]

Thanks to you both for the quick responses ... I will sit tight with my current ROM (which is damn zippy) and hope that you come up with something to perhaps prevent this risk before I get the itch to try out either Black v1.3 or WXML 0.3 (whichever is released first).

Thanks for all the hard work you are doing for those of us who, while not tech-phobic (and are willing to flash new ROMs/Radios with frequency), are not tech-literate enough to solve these problems for ourselves.

[moisha]

I realize folks are still trying to figure out the cause of the White Screen issue...

I believe LVSW already figured out that the issue is with using custom RUU to flash over already installed hard SPL. So if u flashed OK - you are OK.

BTW do u remember the SPL u had before the flash ?

regards

[vp3G]

I believe LVSW already figured out that the issue is with using custom RUU to flash over already installed hard SPL.No, RUU, Hard-SPL, and flashing "techniques" in general have long since been ruled out. It appears to be something within the ROM image itself.

[chymmylt]

I believe LVSW already figured out that the issue is with using custom RUU to flash over already installed hard SPL. So if u flashed OK - you are OK.

BTW do u remember the SPL u had before the flash ?

regards

I had 1.13.oli when I did it. I flashed both LegolasTheElf os only rom and then I did the full update that was posted to begin with. I install both without issue - rom works perfectly.

When installing I used RUU v3.5 and selected 1.11 and ticked hard spl if that helps anybody

[jcespi2005]

here's the definitive test;

flash with SSPL... see if it still is problematic, if so, we have an NBH issue.

if not... flash with Hard-SPL and with the new HTC RUU (not the one from CustomRUU)

that means more secured system flash with SSPL than HardSPL?

[jasjamming]

what we really need to do is determine the root cause of the problem.

that's why I feel the OS files should be dumped into a folder as files and the reconstructed with a separate toolchain (buildimgfs anyone?) and then converted to the nb with aChef/aWaiter and flashed.


OLI, i have a rom constructed from a DUMP from my hermes using the original imgfstools
will send to u later when i get home

[jpxdude]

Not sure how much this will help, but i've tried flashing the new LVSW and Black 1.2 numerous times with the same white screen problem, even bricked my device at 2% flash last night, but had my device saved by oli's excellent hard-spl (thanks!!!)

I decided to flash the old LVSW 20070311 OS Only rom, and surprisingly that works fine, no white screen issue.

Seeing as these images are being flashed fine through mtty, and I was able to flash the OS only via an old RUU updater, this suggests the problem exists within the current/new RUU updater which some hermes devices don't like :-/

yes, I'm probably talking out of my piehole, but want to be constructive somehow.

Good luck to all on progress with this issue :)

[LinoX]

I saw that since the 25/03 version the rom contains a new IPL..
Could it be what's causing the problem?
It seems like that the white screen is something not correctly initialized for hardware..

[Olipro]

I saw that since the 25/03 version the rom contains a new IPL..
Could it be what's causing the problem?
It seems like that the white screen is something not correctly initialized for hardware..

can I ask; those who are having the white screen; do you have any Manufacturer (real) bad blocks?

those who have no problems, do you have any?

[weinson]

Not sure how much this will help, but i've tried flashing the new LVSW and Black 1.2 numerous times with the same white screen problem, even bricked my device at 2% flash last night, but had my device saved by oli's excellent hard-spl (thanks!!!)

I decided to flash the old LVSW 20070311 OS Only rom, and surprisingly that works fine, no white screen issue.

Seeing as these images are being flashed fine through mtty, and I was able to flash the OS only via an old RUU updater, this suggests the problem exists within the current/new RUU updater which some hermes devices don't like :-/

yes, I'm probably talking out of my piehole, but want to be constructive somehow.

Good luck to all on progress with this issue :)

For what it is worth, my upgrade process was similar. I had previously upgraded to Hard SPL and upgraded my radio ... so I did the OS only upgrade (using the older RUU updater, since the new one was not out a few days ago, and the OS only ROM posted by LegolasTheElf) and all worked fine.

[zyw]

can I ask; those who are having the white screen; do you have any Manufacturer (real) bad blocks?

those who have no problems, do you have any?

Since I had previously upgraded to Hard-SPL1.30olipro (thanks oli), ...only flashed the LVSW260307 os rom,using your new RUUV3.5.
No white screen issue.
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x1E500
Partition[3], type=0x4, start=0x21600, total=0x19200

CE Total Length(with sector info) = 0x43CB000
CE CheckSum Length(without sector info) = 0x42C0000

[oliber]

With SPL-1.30.Olipro i get the output below (i can try to flash earlier SPLs and rerun again?)

The device is a M3100 (around a week old!), the device had the white screen issue, but now does not, after flashing HardSPL-1.10-Olipro, followed by the OS with SPL 1.01 MFG Olipro

Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x1BB(443) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

[LinoX]

So it seems that bad blocks are causing this..
(but two cases aren't good for statistics) :)

[Halldor]

can I ask; those who are having the white screen; do you have any Manufacturer (real) bad blocks?

those who have no problems, do you have any?

This was my first hunch! It does not make sense that some and not ALL are having problems. So the only explainable outcome is that this is a hardware issue and not a software issue? Still scratching my head though.....:confused:

[jpxdude]

Hi There,

Doing an info 8, this is what I get (looks kinda scary):

info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x17B(379) is BAD block !!!
Block 0x1F8(504) is BAD block !!!
Block 0x1FB(507) is BAD block !!!
Block 0x1FE(510) is BAD block !!!
Block 0x34A(842) is BAD block !!!
Block 0x35A(858) is BAD block !!!
Block 0x392(914) is BAD block !!!
Block 0x3BC(956) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x1E500
Partition[3], type=0x4, start=0x21600, total=0x19200

CE Total Length(with sector info) = 0x43CB000
CE CheckSum Length(without sector info) = 0x42C0000

I am currently using IPL 1.01 AND SPL 1.30.Olipro

The steps I had taken were as follows:

I went from LVSW 11th march which had 1.10.oli and radio 1.34 to LVSW 20070325 with radio 1.38 and spl 1.13.oli. This gave me white screen.

Tried black 1.2, white screen
downgraded back to LVSW, died at 2% flash, but recovered thanks to hard-spl 1.13.oli. Flashed back to LVSW 20070311 OS only, so radio 1.38 is intact and no white screen :-/ Decided to flash latest hard-spl 1.30.Olipro afterwards, then carried out 'info 8'

My device is a HERM100 on UK Orange M3100 SPV.

[nittin_sp]

Ya hard rset solves it
COOL

[weinson]

I am happy to check my device for bad blocks and share the results if that would be helpful in diagnosing the root of the problem... but need some guidance as to how to generate the block information folks are sharing ... presumably some app I need to have/run.

[jpxdude]

I am happy to check my device for bad blocks and share the results if that would be helpful in diagnosing the root of the problem... but need some guidance as to how to generate the block information folks are sharing ... presumably some app I need to have/run.

Hi There,

You need to find and download the mtty.exe application.

1. Disable 'allow USB connections' in activesync
2. Put your hermes in bootloader mode by holding the power + ok button on either side, then poking the hole below to soft-rest (brings you to tri-color screen)
3. Connect USB cable.
4. Run mtty.exe
5. Under first dropdown box, select usb connection where it say com1 etc..
6. press enter twice, then type info 8 and press enter.
7. Copy and paste result here :)

Let me know if you have any more issues.

Thanks!

[JR_de]

Here my info 8 results - I have no white screen problem.

Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

[MasterOfDesasters]

Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

[fleafly]

I do have the white screen problem.

Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x3FB(1019) is Reversed block

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x19E00
Partition[3], type=0x4, start=0x1CE00, total=0x1DA00

CE Total Length(with sector info) = 0x3AA7000
CE CheckSum Length(without sector info) = 0x39C0000

[Olipro]

Right... exactly what I thought, it's people with devices that have physical bad blocks that are getting it, and those of us with perfect NAND's get no problem at all, no wonder I never spotted it.

OK, later on I'll code up another SPL to address this issue.

what needs to be done is for the NAND read routines to remain unpatched otherwise it looks like the device tries to read its corrupt NAND and resultantly fails.

FUCKING FUCK SHIT BOLLOCKS!

[adomad]

White screen issue:

Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x10(16) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x1E500
Partition[3], type=0x4, start=0x21600, total=0x19200

CE Total Length(with sector info) = 0x43CB000
CE CheckSum Length(without sector info) = 0x42C0000

[Lobstrick]

After Formating by combination of three keys i have white screen an after soft reset i have windows screen :)

USB>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1700
Partition[2], type=0x25, start=0x3000, total=0x19F00
Partition[3], type=0x4, start=0x1CF00, total=0x1D900

CE Total Length(with sector info) = 0x3AC7800
CE CheckSum Length(without sector info) = 0x39E0000

[fiendz]

Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x3A8(936) is BAD block !!!
Block 0x3A9(937) is BAD block !!!
Block 0x3AA(938) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x19300
Partition[3], type=0x4, start=0x1C400, total=0x1E400

CE Total Length(with sector info) = 0x3962000
CE CheckSum Length(without sector info) = 0x3880000

[LegolasTheElf]

IF YOU'RE GOING TO BOTHER TO POST YOUR BAD BLOCKS, AT LEAST TELL US IF YOU'RE GETTING THE WHITE SCREEN OR NOT! BAD BLOCKS WITHOUT A DESCRIPTION OF WHITE SCREEN OR NOT IS USELESS!!

[weinson]

IF YOU'RE GOING TO BOTHER TO POST YOUR BAD BLOCKS, AT LEAST TELL US IF YOU'RE GETTING THE WHITE SCREEN OR NOT! BAD BLOCKS WITHOUT A DESCRIPTION OF WHITE SCREEN OR NOT IS USELESS!!

Assuming folks tell you whether or not they have the white screen, does this block information help, or are we chasing red herrings? Happy to send my block information if it is useful, but no need to waste my time (or others) if (a) no one is looking at it, and/or (b) this is not going to help figure out the problem.

[LegolasTheElf]

I wouldn't be posting about how annoying it is to get info 8 pastes, without what the status of the white screens are if I didn't think it was useful.... :rolleyes:

[TwoPlus1]

Has anyone cured there white screen by installing the OS via MTTY and if so can you point to or give clear instructions on how to do it please?:D

[fiendz]

Seeing as this is the thread attempting to resolve the white screen issue, one may safely assume that I posted my readout in an attempt to help you guys fix an issue which I am experiencing, and not just for silly shits and giggles, wouldn't you think?

But all in all, yes, I had the whitescreen issue with flashing lsvw's rom.

[TwoPlus1]

info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x1A1(417) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

LVSW 26-03-2007 :p

[charon72]

hmm then i theory i should be able to flash lvsw 26032007

did a mtty

Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x19300
Partition[3], type=0x4, start=0x1C400, total=0x1E400

CE Total Length(with sector info) = 0x3962000
CE CheckSum Length(without sector info) = 0x3880000

and checks out fine.. no bad blocks

have been holding out flashing it to see how things r developing....

[TwoPlus1]

Seeing as this is the thread attempting to resolve the white screen issue, one may safely assume that I posted my readout in an attempt to help you guys fix an issue which I am experiencing, and not just for silly shits and giggles, wouldn't you think?

But all in all, yes, I had the whitescreen issue with flashing lsvw's rom.

Assumption is the Mother of All **** Up's!;)

[mart_haj86]

Im having the issue aswell, have installed olipro1.01MFG and OS only for now. I only have one bad block, would this be normal?

Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0xA4(164) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

[weinson]

I wouldn't be posting about how annoying it is to get info 8 pastes, without what the status of the white screens are if I didn't think it was useful.... :rolleyes:

Well, figured I would make sure...

I do not have the white screen (thankfully). My most recent upgrade process was to first go to Hard SPL v4, then to flash the ROM only upgrade. I previously had gone to an earlier version of Hard SPL and upgraded my radio.

This last flash of OS was from Black v 1.2 (customized for cingular by CUSTEL) to the OS referenced in my signature below. My block information is below.

Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

Cmd>

[LegolasTheElf]

hmm then i theory i should be able to flash lvsw 26032007

With no factory bad blocks, you'll be safe. Go and flash it and enjoy! :)

[LegolasTheElf]

We think we have this nailed.. Look for a fix later tonight/day/morning, what-ever-the-hell time it will be in about 12-24 hrs from now :P

In the meantime, here what to do:

Downgrade to Oli's 1.10.Oli. Choose "Force SSPL". You will need activesync working.

Reinstall OS ONLY by creating an .nbh that is ONLY the OS! NO BOOTLOADER and NO RADIO! Oh, and if you want, I'd recommend the ExtRom for lvsw..

I'm not posting an RUU here yet, because I really don't want n00bs bricking their devices after downgrading from 1.30.Oli... I'll think about posting the .nbh if I get success reports back en masse.. (It'll work. We've tested it already.)

[charon72]

With no factory bad blocks, you'll be safe. Go and flash it and enjoy! :)

thank you :P

that was the reply i were waiting for.

dont like bricking.....


Update..

Flashed without any problems :) happy now

[vp3G]

Reinstall OS ONLY by creating an .nbh that is ONLY the OS! NO BOOTLOADER and NO RADIO! Oh, and if you want, I'd recommend the ExtRom for lvsw..For those of us who flashed your repackaged nbh (without ExtROM), what are we missing?

[Olipro]

We think we have this nailed.. Look for a fix later tonight/day/morning, what-ever-the-hell time it will be in about 12-24 hrs from now :P

In the meantime, here what to do:

Downgrade to Oli's 1.10.Oli. Choose "Force SSPL". You will need activesync working.

Reinstall OS ONLY by creating an .nbh that is ONLY the OS! NO BOOTLOADER and NO RADIO! Oh, and if you want, I'd recommend the ExtRom for lvsw..

I'm not posting an RUU here yet, because I really don't want n00bs bricking their devices after downgrading from 1.30.Oli... I'll think about posting the .nbh if I get success reports back en masse.. (It'll work. We've tested it already.)

Look, bitch, don't steal my fucking thunder thanks... you offer your consultation support, fine, but at the same time, don't start taking the bloody piss with the assistance I'm willing to offer you... which includes associating yourself with Hard-SPL... pof deserves credit for working with me to test the modifications I made.

And for FUCKS SAKE don't tell people to downgrade, that's just not kosher... ask me, don't start pretending to be a fucking expert.

that said, don't worry about PM'ing me, I hold no grudges... I just get fucked off

In other news however, a new Hard-SPL will be released soon after testing to fix the white-screen issue.

[LegolasTheElf]

For those of us who flashed your repackaged nbh (without ExtROM), what are we missing?

Not 100% sure yet.. Just some basic HTC stuff.. Doesn't make a huge difference, just makes it prettier -- sorta..

I haven't dissected everything from the extrom yet. When I have time I will look and see what it does.

[vp3G]

Not 100% sure yet.. Just some basic HTC stuff.. Doesn't make a huge difference, just makes it prettier -- sorta..

I haven't dissected everything from the extrom yet. When I have time I will look and see what it does.OK, thanks. I must have missed where ExtROM became relevant again with WM6. :confused:

[Murcielago]

Right... exactly what I thought, it's people with devices that have physical bad blocks that are getting it, and those of us with perfect NAND's get no problem at all, no wonder I never spotted it.

OK, later on I'll code up another SPL to address this issue.

what needs to be done is for the NAND read routines to remain unpatched otherwise it looks like the device tries to read its corrupt NAND and resultantly fails.

FUCKING FUCK SHIT BOLLOCKS!
Are you sure about that ? Check the post right above yours and he doesn't have any bad block and has the white screen issue....

[Murcielago]

Look, bitch, don't steal my fucking thunder thanks... you offer your consultation support, fine, but at the same time, don't start taking the bloody piss with the assistance I'm willing to offer you... which includes associating yourself with Hard-SPL... pof deserves credit for working with me to test the modifications I made.

And for FUCKS SAKE don't tell people to downgrade, that's just not kosher... ask me, don't start pretending to be a fucking expert.

that said, don't worry about PM'ing me, I hold no grudges... I just get fucked off

In other news however, a new Hard-SPL will be released soon after testing to fix the white-screen issue.
:):):) At last, one of the real experts is telling him to shut up....
No offense LegolasTheElf but your interventions are really annoying sometimes
I just checked and I don't have any bad blocks so I'm gonna flash it and test it :)

EDIT : just flashed it and everything is OK -- YESSS

[tadzio]

White screen issue:

Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x10(16) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x1E500
Partition[3], type=0x4, start=0x21600, total=0x19200

CE Total Length(with sector info) = 0x43CB000
CE CheckSum Length(without sector info) = 0x42C0000

Interesting - you have a ROM that was not storage-optimized by my tools, and still have the whitescreen issue. Seems to become more unlikely that they are the root cause for the problem.

Cheers
Daniel

[mxlaser]

Obviously its known im sufferign white screen :P:P

Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x42(66) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

So i take it, even one bad block is bad?? Currently the above is using LSVW 26/3 flashed using MTTY and stock 1.01MFG SPL.

[vp3G]

Interesting - you have a ROM that was not storage-optimized by my tools, and still have the whitescreen issue. Seems to become more unlikely that they are the root cause for the problem.Just curious how you were able to tell this -- I assume by the CE sizes?

CE Total Length(with sector info) = 0x43CB000 (= 71,086,080)
CE CheckSum Length(without sector info) = 0x42C0000 (= 69,992,448)

-- vs. --

CE Total Length(with sector info) = 0x38BF800 (= 59,504,640)
CE CheckSum Length(without sector info) = 0x37E0000 (= 58,589,184)


My next question would be... where'd he get a non-optimized ROM?

[tadzio]

Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x3A8(936) is BAD block !!!
Block 0x3A9(937) is BAD block !!!
Block 0x3AA(938) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x19300
Partition[3], type=0x4, start=0x1C400, total=0x1E400

CE Total Length(with sector info) = 0x3962000
CE CheckSum Length(without sector info) = 0x3880000

Another interesting one - the bad blocks are in the Storage area, not in the Imgfs. It surprises me that this could affect the OS operation. The flashing process does not touch Storage (other than formatting it, but there it'd certainly not try to use spare reserved blocks, but instead simply make Storage a bit smaller).

So I have a feeling the explanation for the whitescreen issue will have to go deeper than "all bad blocks will cause the whitescreen issue".

In other words: even if your TyTN does not have any bad blocks, I'd currently strongly recommend against flashing lvsw's latest ROM!

Cheers
Daniel

[mxlaser]

Is the such a tool that will let you essentially flash/format/wipe your entire NAND allowing for a fresh slab as it were.

Then flash OS, radio etc etc....

Would that fix a bad block, or is a bad block now a permanant thing we all deal with?

[sassenach74]

In other words: even if your TyTN does not have any bad blocks, I'd currently strongly recommend against flashing lvsw's latest ROM!

Cheers
Daniel

Dont really think its fair to say just LSVWs latest, as i never even flashed that rom, i flashed the black v1.2 and got the white screen. Just letting you know so you dont think it has to do with that particular rom only.

Neil.

[tadzio]

Just curious how you were able to tell this -- I assume by the CE sizes?

The 'total' (size in sectors) of partition 2 (which is the imgfs) is the interesting number. I have an original ROM where partition 2 is 0x1E100, which is already rather big. adomad's ROM has 0x1E500, so it's even bigger. That means that either it must come from a different base ROM (very likely), or the size was enlared by an unknown tool (unlikely).
"tadzio-ized" ROMs typically have a size of around 0x17000 to 0x1B000, depending on how much stuff was added/deleted to/from the ROM.

My next question would be... where'd he get a non-optimized ROM?

WMXL 0.1 and 0.2 were not optimized, for example.

Cheers
Daniel

[vp3G]

The 'total' (size in sectors) of partition 2 (which is the imgfs) is the interesting number. I have an original ROM where partition 2 is 0x1E100, which is already rather big. adomad's ROM has 0x1E500, so it's even bigger. That means that either it must come from a different base ROM (very likely), or the size was enlared by an unknown tool (unlikely).
"tadzio-ized" ROMs typically have a size of around 0x17000 to 0x1B000, depending on how much stuff was added/deleted to/from the ROM.Very interesting, thanks for the info! :)


WMXL 0.1 and 0.2 were not optimized, for example.Yeah, I figure it can't be the LVSW 3/26 ROM (unless there's a non-optimized version floating around somewhere). And this is where people posting their 'info 8' with no additional info with regard to what they had prior to flashing, what they flashed to, and how they got from "a-to-b" isn't terribly helpful. :rolleyes:

[LegolasTheElf]

:):):) At last, one of the real experts is telling him to shut up....
No offense LegolasTheElf but your interventions are really annoying sometimes
I just checked and I don't have any bad blocks so I'm gonna flash it and test it :)

EDIT : just flashed it and everything is OK -- YESSS
If you don't like my help, you can always add me to your ignore list. Other people can benefit from my help.

However, I see that my help was still good enough to help give you the balls to flash the rom...

This is why I don't post a lot on here; fuckwits who attack me because I'm trying to help. Oli was pissed because HE wanted to tell everyone what had been found; he was NOT pissed that I posted something that was wrong!

[rdtce]

Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

Updated from SPL-1.01 MFG by running the whole package...

[moisha]

That means that either it must come from a different base ROM (very likely)l

yes. diff source.

[Owycx]

Hi guys,

Don't know if this helps, but I was running 1.11 oli and upgraded to LSVW Edition (2007-03-25) no white screen. I ran an info 8 just to see and I had no bad blocks, sorry didn't save the log. I decided to upgrade to 1.30 oli. Upgrade went fine, but it booted into the white screen. Fortunately, a hard reset fixed it, however I ran info 8 again and got this:


Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x3A8(936) is BAD block !!!
Block 0x3A9(937) is BAD block !!!
Block 0x3AA(938) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x1E500
Partition[3], type=0x4, start=0x21600, total=0x19200

CE Total Length(with sector info) = 0x43CB000
CE CheckSum Length(without sector info) = 0x42C0000


Hope this helps. BTW, I switched back over to XDA Live .30 for unrelated reasons and it installed and is running fine.

[jcespi2005]

Hi guys,

Don't know if this helps, but I was running 1.11 oli and upgraded to LSVW Edition (2007-03-25) no white screen. I ran an info 8 just to see and I had no bad blocks, sorry didn't save the log. I decided to upgrade to 1.30 oli. Upgrade went fine, but it booted into the white screen. Fortunately, a hard reset fixed it, however I ran info 8 again and got this:


Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x3A8(936) is BAD block !!!
Block 0x3A9(937) is BAD block !!!
Block 0x3AA(938) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x1E500
Partition[3], type=0x4, start=0x21600, total=0x19200

CE Total Length(with sector info) = 0x43CB000
CE CheckSum Length(without sector info) = 0x42C0000


Hope this helps. BTW, I switched back over to XDA Live .30 for unrelated reasons and it installed and is running fine.

seems the issue cames from combination of BAD BLOCKs (the root origin) and HardSPL 1.30Oli... like Olipro points in 136

now think we are in the right way to see the light in this issue :)

thanks to Olipro and tadzio for putting time in this

[vp3G]

No white screen after flashing LVSW 03-25 (OS+Splash Only, used RUU 3.6). Starting point was LVSW 03-15 and Hard-SPL 1.30.

Subsequently extracted ExtROM (from LVSW 03-26 full ROM), flashed it with RUU 4.0 and did hard reset. Still fine.

Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

[LinoX]

If bad blocks are in the user storage area and the OS can't boot maybe because at the first initialization the os explodes some files/folders (IE /my documents, /documents and settings, /*.vol and so on)
The white screen could be because one of this file goes in the bad block..
Conclusion: unmarking a REALLY-BAD block is dangerous.
Oli's bootloaders should not do it while flashing but they should have a "checkflash" command to check if each "bad" block is really bad (IE write a random sequence of byte and then re-read it and compare with the previous)..
Olipro is the man, I'm sure he'll overcome this issue ;)

Go Oli, go.. :)

[DJopek]

White screen:

Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x71(113) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

[internetworker]

HI,

Here's another bad block...


Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x182(386) is BAD block !!!
Block 0x3A8(936) is BAD block !!!
Block 0x3A9(937) is BAD block !!!
Block 0x3AA(938) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x19300
Partition[3], type=0x4, start=0x1C400, total=0x1E400

CE Total Length(with sector info) = 0x3962000
CE CheckSum Length(without sector info) = 0x3880000

==========================================

1.Started with when i was flashing with LVSW 2007-03-25(was running WMXML with SPL1.04, radio was 1.27), white screen immediately happened after the last reboot. My radio is not 1.34

2.Flashed with LVSW 2007-03-20 and worked for me, then flashed to BLACK 1.2, and SPL 1.30 Olipro. Even tried to hard reset again and everything worked. Though "info 8" still shows bad block.

3. After a few days, hard reset, and i got the stupid "White Screen" again.

4. I tried using mtty to make my SPL to 1.01MFG and then pushed the OS.nb from BLACK 1.2 and it worked for me. After that made my SPL to 1.30Olipro again.

5. A couple of days later, hard resetted and guess what? the damn "White Screen" happened again. Then i had to go through the whole process again. So as far as i know, the problem still happens with no solution.

Would it be solved if i flashed it with a "Shipped ROM" ?????

Lenny
HERM100(Dopod838pro)

[jpxdude]

I tried putting LVSW 25/03/07 Full version back on which gave me no bad blocks after info 8, but still white screen.

I then hard reset a few times, checked with info 8 via mtty, still no bad blocks. I then decided to install hard-spl 1.30.Olipro and checked info 8 which gave me this:

Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x17B(379) is BAD block !!!
Block 0x1F8(504) is BAD block !!!
Block 0x1FB(507) is BAD block !!!
Block 0x1FE(510) is BAD block !!!
Block 0x34A(842) is BAD block !!!
Block 0x35A(858) is BAD block !!!
Block 0x392(914) is BAD block !!!
Block 0x3BC(956) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

I tried some of the various fixes around the forum apart from mxlasers fix without success at the moment. I will update if anything changes.

Thanks,

**Edit

Right, so I followed the mxlaser method, and got rid of the white screen problem (thanks mxlaser!). Things look like their working good! Set SPL first to 1.04 then straight to 1.30.Olipro. Things seem great, but I still get the exact bad block error as above when doing an info 8. This also only occurs with the 1.30.Olipro SPL. Anyone know if this is cause for concern, or a remedy of sorts?

Thanks in advance!

[mxlaser]

Your welcome, but its not my idea as such.

Its just the prvious way you flashed an OS before all the custom RUU stuff.

Glad its working... hopefully the workaround i've suggested is a very short term solution and a real fix is possible...

Credit obviously goes to the pioneers at the start of all this flashing, like Olipro, pof et all :)

[aatjitra]

@mxlaser

you are great, buddy... i follow exactly your step and no white screen for me !... thanks !...

[Olipro]

If bad blocks are in the user storage area and the OS can't boot maybe because at the first initialization the os explodes some files/folders (IE /my documents, /documents and settings, /*.vol and so on)
The white screen could be because one of this file goes in the bad block..
Conclusion: unmarking a REALLY-BAD block is dangerous.
Oli's bootloaders should not do it while flashing but they should have a "checkflash" command to check if each "bad" block is really bad (IE write a random sequence of byte and then re-read it and compare with the previous)..
Olipro is the man, I'm sure he'll overcome this issue ;)

Go Oli, go.. :)

bad blocks can't be unmarked because a write test is performed and if it fails due to the block actually being bad then it's remarked... otherwise nobody would have any bad blocks on their phone :P

the issue stems with trying to read them, that's what seems to be the issue, I never saw pof last night so I've not had a chance to test the new SPL so I'm afraid I can't release it yet.

but guys... seriously, stop flashing the bloody 1.01MFG for fucks sake... at least use the modified one.

[Murcielago]

If you don't like my help, you can always add me to your ignore list. Other people can benefit from my help.

However, I see that my help was still good enough to help give you the balls to flash the rom...

This is why I don't post a lot on here; fuckwits who attack me because I'm trying to help. Oli was pissed because HE wanted to tell everyone what had been found; he was NOT pissed that I posted something that was wrong!

You're just making me laugh.... you must have found your MCSE exams in a surprise pocket... it's a MVP that tells you that
See you

[Clarkster]

I also have a hardware bad block and had the white screen on my 8525. Flashing with mtty OS only worked fine though.

I assume it might be best for 'new flashers' to wait for a release that can fix it for them, as the machine is still useable, and flashing manually using some of these methods can be dangerous.

[mross]

Well, I know I'm rather noob but maybe someone more clever could think it out...
We have many attempts to flash our devices with "white screen effect".
Some of us reports that have bad blocks, but in different areas. Think that mayby this is way with no way out.
Symptom remains the same always. White screen.
Important is that in fact - system works good (eg filesystem, core, etc...). After taping a screen with stylus - we can calibrate it and go on.
Then we have today screen with no background, a telephone pad with no background, media player with no background... :) In fact it's such annoying that we can't use our system.
We can even use our camera and record a video or take a picture, but we can not see it.
But not always... if we use "full screen" mode - we can see our films... :) - strange? isn't it?
Maybe system after flash have some "very small" defect concerning missing ability to scaling down bitmaps or something?
Maybe some stupid modification of graphical engine of our phone after flash will result in getting fully healthy system?
Maybe someone wiser will think it out? :)

[oliber]

mross,

Olipro, pof, Legolas and a few others are working on the issue, as you would have seen if you had read the entire thread!

Also, please remember that these guys DO NOT MAKE MONEY from thier efforts (apart from 1 to 1 support services), if you tried a ROM, it bricked you're phone, it is at your own risk and you should not EXPECT support, unless you pay for it!

[skyyguy]

Both result in the white screen problem referenced above. I've tried to read through all of the posts; and I must be missing something if there is an actual fix listed. The other thing I notice is the audio for ring tones etc isn't on either.

I really appreciate the efforts of everyone working hard on this; and I enjoy the ability to play with something new. Hopefully this is resolved soon.

[outz]

The only roms I've installed were the standard cingular ones, as well as Kyphers xda live 0.10 0.20 and 0.30 (which I am currently using) - I haven't ever had a white screen problem. Over the course of the past few months I've also used SPL-1.01MFG, and now I've been on SPL-1.10.oli for the past few weeks. I'm posting my info 8, just incase anyone still needs the info.

USB>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x1F8(504) is BAD block !!!
Block 0x3FB(1019) is Reversed block

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x1E500
Partition[3], type=0x4, start=0x21600, total=0x19200

CE Total Length(with sector info) = 0x43CB000
CE CheckSum Length(without sector info) = 0x42C0000
USB>

[mross]

I do not expect support unless I pay for it :) ... hm...
Anyway, did anyone with white screen effect tried to put into "white" phone registry file from "healthy" fresh flashed one?
Mayby we do not need new bootloader...

[joedoe]

mross,

Olipro, pof, Legolas and a few others are working on the issue, as you would have seen if you had read the entire thread!

Also, please remember that these guys DO NOT MAKE MONEY from thier efforts (apart from 1 to 1 support services), if you tried a ROM, it bricked you're phone, it is at your own risk and you should not EXPECT support, unless you pay for it!

I do not understand your post. mross just wants to be useful in resolving the problem and I don't see any reason why his thoughts should be rejected in such a rude way.

[joedoe]

Ok, let me put on table one more idea: both releases which produce the white screen effect (LVSW 2007-3-26 and Black Edition v.1.2) have ATI driver patch embedded. And the problem, BTW, is connected to the image rendering.

[mross]

:) I'm noob but think that you're right....
Anyone knows how to "unpatch" the system from "ATI patch"?
Maybe those with white screen have little bit differnt GE from others???

[Olipro]

SPL-1.35 is released... flash to your phone and re-flash the OS if necessary

[mxlaser]

So, if we put SPL 1.35 on our devices then flash using the RUU wrapper a full NBH file, would that then clear any bad blocks?

I have a bad block on the last test on the list. is it possible to remove/repair that?

Besides that, just want to put out a big hats of to Olipro... Yet again, done a great job for us! :)

What was the issue/culprit in the end?

[Olipro]

So, if we put SPL 1.35 on our devices then flash using the RUU wrapper a full NBH file, would that then clear any bad blocks?

I have a bad block on the last test on the list. is it possible to remove/repair that?

Besides that, just want to put out a big hats of to Olipro... Yet again, done a great job for us! :)

What was the issue/culprit in the end?

to be frank, I don't know for sure... also, that bad block can be unmarked by flashing a valid OS, or if you want to know for sure, use mtty to issue "task 2a" if the block actually is bad, it'll say so and it won't repair it.

all I know is that if the issue lies with reading bad NAND (which I believe it does) 1.35 will fix it... so flash the bloody thing already (also, you might need to reflash the OS)

[LegolasTheElf]

Thanks goes out to OLIPRO, POF, and LVSW for creating such an awsome rom.

I've created a self-extracting/auto-installing version of the lvsw 3-26 rom INCLUDING radio, ExtRom, SPL 1.35.Oli and using Oli's brand-new CustomRUU.

This will FIX white screen issues. Download, install, enjoy WM6 -- white screen free!

Download LVSW 3-26-2007 here! With White Screen Fix! (http://rapidshare.com/files/23297362/lvsw.1.35.ruu4.1.exe)

And.. I don't want to hear bitching about how this release isn't without radio. My thought is that if your OS is screwed, there is always a chance the radio could be too. So, why not flash it and be safe... Yeah, I know.. Different ROM's, but, hey.. It won't hurt. Besides, 1.38.00.10 is a great radio.

[mzahiri]

Thanks goes out to OLIPRO, POF, and LVSW for creating such an awsome rom.

I've created a self-extracting/auto-installing version of the lvsw 3-26 rom INCLUDING radio, ExtRom, SPL 1.35.Oli and using Oli's brand-new CustomRUU.

This will FIX white screen issues. Download, install, enjoy WM6 -- white screen free!

Download LVSW 3-26-2007 here! With White Screen Fix! (http://rapidshare.com/files/23297362/lvsw.1.35.ruu4.1.exe)

And.. I don't want to hear bitching about how this release isn't without radio. My thought is that if your OS is screwed, there is always a chance the radio could be too. So, why not flash it and be safe... Yeah, I know.. Different ROM's, but, hey.. It won't hurt. Besides, 1.38.00.10 is a great radio.


FYI.

I followed the directions and i still do get the white screen. Using 8525

[test7875]

FYI.

I followed the directions and i still do get the white screen. Using 8525

Damn .... my phone is just getting worse ... :(

If only i could go back ..


Anyone else tried MXlaser option of going back to 1.01?
I know Legos said you could brick your phone.

oh well ...

Is there a ROM we can go back to without the issue?

[LegolasTheElf]

Do the update again and FORCE SSPL!

[mzahiri]

Do the update again and FORCE SSPL!

Thanks for the advice. I did force the SSPL and it worked.

Great job.

Now i have the latest rom.

[Penske MB]

hmm....

I guess I'll wait for next release... too many flashs...

thx

update:

Should I give a try??

LegolasTheElf??

Oh well, one more try..

[internetworker]

Hey mzahiri,

Since you mentioned it worked, can you mtty your device and do a "info 8" to see if there are still any bad blocks ?????????

[test7875]

FYI.

I followed the directions and i still do get the white screen. Using 8525

Did it ... white screen .. s orry

[Olipro]

Did it ... white screen .. s orry

look, it's not hard;

1) flash 1.35 using Force SSPL option from WINDOWS MOBILE.

2) flash LVSW WITHOUT using force SSPL (autodetect or select 1.11/1.13/1.30)

3) let the flash complete, you might need to wait a while for phone to boot, or perform a hard-reset if it fails.

[Olipro]

hmm....

I guess I'll wait for next release... too many flashs...

thx

update:

Should I give a try??

LegolasTheElf??

Oh well, one more try..

for gods sake... here it is again.

1) Flash 1.35 using Force SSPL option.

2) flash LVSW/Legolas, do NOT Force SSPL, either download new CustomRUU and autodetect, or manually select 1.11/1.13/1.30

3) allow it to flash and wait a bit for it to boot, if it still doesn't, perform a hard-reset

[internetworker]

Hi Oli,

Did what you have mentioned and it seems to have cleared most of the bad blocks except one. Anything that i could have been missing??? below are my before and after :

BEFORE
-------
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x182(386) is BAD block !!!
Block 0x3A8(936) is BAD block !!!
Block 0x3A9(937) is BAD block !!!
Block 0x3AA(938) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x19300
Partition[3], type=0x4, start=0x1C400, total=0x1E400

CE Total Length(with sector info) = 0x3962000
CE CheckSum Length(without sector info) = 0x3880000


AFTER:
-------
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Block 0x182(386) is BAD block !!!

Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1800
Partition[2], type=0x25, start=0x3100, total=0x18E00
Partition[3], type=0x4, start=0x1BF00, total=0x1E900

CE Total Length(with sector info) = 0x38BF800
CE CheckSum Length(without sector info) = 0x37E0000

So i assume this has not 100% solve the issue i guess. So far i have not seen any white screen yet. Will do a hard reset a couple of times to see if it comes back. Thanks for you help Oli...

[Olipro]

So i assume this has not 100% solve the issue i guess. So far i have not seen any white screen yet. Will do a hard reset a couple of times to see if it comes back. Thanks for you help Oli...

NO, THIS MEANS THAT YOUR DEVICE HAS *REAL* CORRUPT NAND, THEY ARE GENUINELY DAMAGED AND CANNOT BE RECOVERED.

[LegolasTheElf]

I can't believe how easy we make this for you to fix your phone, and you still can't figure it out. Let's do this once more, this time S-L-O-W-L-Y

1. Download my lvsw CustomRUU package onto your DESKTOP (or a folder of your choice that you will REMEMBER!)
2. Double click the package you just downloaded
3. Select ForceSSPL
4. Follow the prompts
5. Done

IF it doesn't work do this SECOND step:

1. Double click the package you just downloaded (and flashed with SSPL)
2. Select Autodetect
3. Follow the prompts
4. Done.

[outz]

NO, THIS MEANS THAT YOUR DEVICE HAS *REAL* CORRUPT NAND, THEY ARE GENUINELY DAMAGED AND CANNOT BE RECOVERED.

Since it is marked bad, a genuinely damaged block shouldn't affect device performance, is this correct?

[LegolasTheElf]

Since it is marked bad, a genuinely damaged block shouldn't affect device performance, is this correct?

It is a manufacturer bad block. There is NOTHING to worry about.

[Olipro]

Since it is marked bad, a genuinely damaged block shouldn't affect device performance, is this correct?

someone set up us the bomb, you have no chance to survive, make your time.

actually... it's fine, just means you lose a little bit of space unfortunately.

[outz]

someone set up us the bomb, you have no chance to survive, make your time.

actually... it's fine, just means you lose a little bit of space unfortunately.

Ok, thanks. My storage is Total: 47.23 and Program is Total: 48.68

[Penske MB]

for gods sake... here it is again.

1) Flash 1.35 using Force SSPL option.

2) flash LVSW/Legolas, do NOT Force SSPL, either download new CustomRUU and autodetect, or manually select 1.11/1.13/1.30

3) allow it to flash and wait a bit for it to boot, if it still doesn't, perform a hard-reset


Hi Olipro,

I did it and it works great!!

BTW, how do I check the info 8?? I see some of you testing the bad meneory corrupt. under CMD, but where do I find it??

[Olipro]

Hi Olipro,

I did it and it works great!!

BTW, how do I check the info 8?? I see some of you testing the bad meneory corrupt. under CMD, but where do I find it??

you need mtty... at this point, it really doesn't matter any more, I've fixed the problem so the output won't help

[Martinhdk]

Thanks goes out to OLIPRO, POF, and LVSW for creating such an awsome rom.

I've created a self-extracting/auto-installing version of the lvsw 3-26 rom INCLUDING radio, ExtRom, SPL 1.35.Oli and using Oli's brand-new CustomRUU.

This will FIX white screen issues. Download, install, enjoy WM6 -- white screen free!

Download LVSW 3-26-2007 here! With White Screen Fix! (http://rapidshare.com/files/23297362/lvsw.1.35.ruu4.1.exe)

And.. I don't want to hear bitching about how this release isn't without radio. My thought is that if your OS is screwed, there is always a chance the radio could be too. So, why not flash it and be safe... Yeah, I know.. Different ROM's, but, hey.. It won't hurt. Besides, 1.38.00.10 is a great radio.


Ok. I have been stuck with the white screen issue since Black 2.5. I am reading and trying whatever method but i have run out of options, so I recon something must be wrong somewhere i my blocks,,,or not. No BAD BLOCKS, but I get the fancy white screen issue whenever I try to install a Black rom. LVSW does not seem to cause same problem, and XDA live neither. But with black 2.5 and 3.x the bootscreens and background image does not show. So. Why not stick to LVSW. Simply because I hate not to be in control of things - and I wont give up eventhough I am not very good in programming stuff. (my job is normally to sell the bugger ;) )

I have read WIKI and all threads about issues concerning this, and I might have overseen something. Some of you friendly guys have given me hints of where to look, but I have not seen the light yet - maybe because I am simply to stupid to understand. But I feel I have been all over. I have wondered if it can have something to do with ExtRom or radio - even though Mr Ty is working like a charm with B2.0.

So Q is: CAN any of you guys that have faced the same problem, try to help me overcome this freaking situation before I go nuts - and everyone can read about another crazy dude that has gone BERSERK in a mall trying to make people swallow some unknown grey things that could look like a mobile phone from a distance.. (now its slipping - haha).

If so - here is situation:

- Have Black 2.0. Can install XDA live and older LVSW (seem to ues a different installer)
- Cannot install B2.5 and B3.x
- Have tried to install from SD cards
- Have tried by baking a new .NBH
- Have tried HardSpl V6, V7 and HardSPL 1.10
- Have tried SSPL
- Have tried three diff radios
- Have tried through ModifiedRUUupdater


EDIT; When launching i.e Pimp My Black .2 it comes with an error message: "An unexpected error has occurred in PMB...." and then in details;
" PMB AgumentException. An error message cannot be displayed because an optional resource assembly containing it cannot be found. at Microsoft.AGL.Common.MISC.HandleAr() at System.Drawing.Bitmap.__InitFromMemorystream() at System.Drawinf.Bitmap..ctor() at System.Reflection.runtimeConstructorInfo.InternalI nvoke() System.Reflection.runtimeConstructorInfo.Invoke() System.Reflection.ConstructorInfo.Invoke() at System.Resources.resourcesReader.CreateResource() at System.Resources.resourcesReader.LoadBitmap() at System.Resources.resourcesReader.LoadObjectV2() at System.Resources.resourcesReader.LoadObject() at System.Resources.RuntimeResourceSet.GetObject() at System.Resources.ResourceManager.GetObject() at System.Resources.ResourceManager.GetObject() at Pimp_My_Black.Mainscreen.InitializeComponent() at Pimp_My_Black.Mainscreen..ctor() at Pimp_My_Black.Program.Main"