Related
I've created this thread, as to not clutter the LVSW thread any more than it currently has.
Clearly (even though some don't believe it) there is an issue with th latest ROM releases and users doing a standard, succesful ROM update and being introduced to the IWSAU (Imaginary White Screen After Updating)
Those that currently have the IWSAU, there are fixes that seem to currently work. I've copy pasted some of my posts from the LVSW thread and hopefully others can posts here too with answers.
1. Download the FULL update from LVSW's first post.
2. Use NBHextract to rip the NBH file into seperate files.
3. Flash SPL-1.01MFG to your device
4. Flash OS.nb to device.
5. Enjoy a non white version of this great rom.
** Note to LVSW and other chefs reading. It appears there is some errors occuring when using the 1.13SPL and the latest RUU flash util and the latest roms. The information being flashed doesnt appear to be going where it should be on the rom and is causing this White screen. It is a bug.
I've repacked LVSW's latests rom, with an earlier RUU util and the force SSPL option only and works perfectly. Its something wrong with the newest combo of files and utils causing an issue.
Click to expand...
Click to collapse
Also, to add confusion to the matter. This is the results of the following
DOPOD 838 PRO - HERM100
15/3 LVSW Pro - Flases perfectly
20/3 LVSW ROM - White screen from update RUU
25/3 LVSW ROM - White screen from update RUU
Black 1.2 (with 1.13SPL) - White screen from update RUU
Black 1.2 (original) - Flashes perfectly
DOPOD 838 PRO - HERM200
15/3 LVSW Pro - Flases perfectly
20/3 LVSW ROM - Flases perfectly
25/3 LVSW ROM - Flases perfectly
Black 1.2 (with 1.13SPL) - Flases perfectly
Black 1.2 (original) - Flashes perfectly
I-MATE JASJAM - HERM100
15/3 LVSW Pro - Flases perfectly
20/3 LVSW ROM - Flases perfectly
25/3 LVSW ROM - White Screen after RUU update
Black 1.2 (with 1.13SPL) - White Screen after RUU update
Black 1.2 (original) - Flashes perfectly
However, all flash perfectly when using MTTY and the OS.nb...
Theres clearly something wrong. All tested same machine, same files, everything identical just different hardware.
Click to expand...
Click to collapse
Checked for bad blocks, was one of the first things i thought also...
Its strange, as its the welcomehead.96.png file that doesnt obviously display, but also the background image of the theme as well, so im wondering if its a section of the rom thats not flashing right, or possibly due to previous flashes etc being done, anything resdidual (shouldnt be) is left causing the issue.
I've just spent time creating a RUU 3.5 updater with the OS, SPL 1.30Oli and radio 1.38.0.10 and it flashed with white screen. I then lodaed the OS in to Rom Koch, removed the welcomehead.96.png file, replaced it with the same one, compile then used in the same flash, and it flashed perfectly fine, with no white screen.
Its buggng me as i don't want to have to mess around each update to get them, but also to help others. I enjoyed the double click update easyness of previous roms and im wondering if these new ones could possibly be in the compiling in the rom maker?? Maybe it effects certain hardware revisions??
Anyway, mostly speculation as i don't have the talents to investigate more, other than trial and error things like im doing. Im lucky to have 3 Hermes devices here to test on. So far the Dopod 838Pro HERM200 has flashed everything perfectly fine. The Dopod 838Pro HERM100 has the most white screen fails, and the JasJam inbetween.
Click to expand...
Click to collapse
I did a full official dopod rom update, then tried the latest LSVW one. same white screen.
Rinse and repeat but this time with older RUU util and OS only, worked perfectly.
Im convinced it has something to do with the NAND and the smaller image/larger storage space hack now more than ever.
I took the 15/3 LVSW rom, and ram it through the storage patch.
Flash Dopod HERM100 - White screen (where before this was my saving rom it seemed and 100% worked every time)
Flash JasJam HERM100 - Worked perfectly
Flash Dopod HERM200 - White screen (where before this was my saving rom it seemed and 100% worked every time)
Obviously more and more people are downloading this and trying it out and its now appearing that the original couple "doing it wrong" where actually right and are experiencing a common issue now.
Click to expand...
Click to collapse
LVSW rom uses Custom RUU v3.5, this RUU unpacks either the old hermes RUU (for bootloader <=1.09) or the new hermes RUU (for bootloader >= 1.11). In the later case, the standard RUU always does a 'task 28' to format the storage (ie: hard-reset) after every rom flash. I did some tests with Olipro before releasing it and we thought that removing the 'task 28' was fine (since we don't want a hard reset after flashing any NBH that doesn't contain OS), and as we didn't got any issues flashing several OS versions we thought it was fine this way, but probably this is what is causing the problem.
Have any of you having this 'white screen' issue tried to just do a 'hard reset' after flashing LVSW rom? Did it fixed the problem?
IM re-creating the issue now and flashing a problem rom as i type.
I did a hard reset with keys and stylus, and made no difference.
Im going to do a Task 28 in MTTY after this flash and see if it makes any difference, and will get back to you.
ok, can you also try with the standard / unmodified HTC RUU? You can extract it from the file RUU_Inside.exe in htc's 2.11 rom or in imate's new rom.
Hi guys,
so yesterday night I was working the whole time with the white screen stuff! Installing of different roms did not bring any success removing the white screen.
Sorry maybe for the wrong words, which I am using, but I am still a newbie, but my white screen is gone after doing following steps, if I remember right:
I flashed the original vodafone complete rom from the manufacturer on my vpa compact III. This seems to work. But then after finishing the installation in the restart the start screen with the vodafone bootscreen I saw the two words "No GSM" and the vpa compact stucked in the windows screen. Then I tried to use the brickregenerationstuff from pof , with no really success. After that I installed again the new lvsw complete version and again I had the white screen problem, but in this moment I was glad to have the white screen problem, than the no gsm screen . After that I made absolutely the same like before installing the vodafone stuff! I installed the previous LVSW version with extrom etc. After that the white screen was no longer there.
I am not sure, what I did and why the hell the white screen was no longer there, because I made the same thing before installing the vodafonestuff.
It sounds a bit confusing, but it was confusing .
Maybe this helps somebody to extract some information, which can help somebody else.
pof said:
LVSW rom uses Custom RUU v3.5, this RUU unpacks either the old hermes RUU (for bootloader <=1.09) or the new hermes RUU (for bootloader >= 1.11). In the later case, the standard RUU always does a 'task 28' to format the storage (ie: hard-reset) after every rom flash. I did some tests with Olipro before releasing it and we thought that removing the 'task 28' was fine (since we don't want a hard reset after flashing any NBH that doesn't contain OS), and as we didn't got any issues flashing several OS versions we thought it was fine this way, but probably this is what is causing the problem.
Have any of you having this 'white screen' issue tried to just do a 'hard reset' after flashing LVSW rom? Did it fixed the problem?
Click to expand...
Click to collapse
So which SPL is better to use - <=1.09 or >1.09?
If this is the issue, then may be the solution is just changing to right SPL and full upgrade afterwards?
Hi There,
I also tried the latest LVSW and Black 1.2. Both give me the white screen issue, whereby the 'Today' screen is a blanket white and nothing can be read until you highlight over them via the scrollwheel or a screen tap. It's as if the background on the mainscreen as default has disappeared and no amount of resetting the background via settings will fix this.
I am using the 1.38.0.10 radio with the 1.13.oli. Prior to this, I was using the first LVSW release, I think on the 11th March.
Anyone know a solution to this?
Thanks in advance, and keep up all the great work here!
J
p.s my device is originally an orange M3100 SPV, or HERM100 if that helps in any way.
Dopod 838 Pro No Problemo
Hi,
I had a dopod 838 Pro which is hermes100 and i just flashed it without any problem. I was using WM Black Ed v1.2 with 1.13 Oli Spl.
Thanks
Cheers..
I also experience the issue, using 1.13.oli spl 1.38.00 radio, Ill see what I can come up with later on when I get home from work.
someone: test this procedure:
enter bootloader mode.
run mtty
issue task 28, close mtty.
flash with CustomRUU, select 1.11.
see if you get a whitescreen.
if you do, re-enter bootloader, issue task 28 again.
see if you still get a white screen.
also, I've been thinking... if you are removing a bmp image from the OS NB then the OS is still the same size (or smaller) therefore, if NAND blocks aren't getting wiped they STILL won't get wiped when you reflash the new equal size or smaller NB, and THEREFORE it is *nothing* to do with the SPL or CustomRUU.
The SPL merely flashes binary data, it doesn't give a hoot what that might be, therefore, if it's buggering up, then the structure of the image is buggered up, it's nothing to do with the SPL.
I've just followed your destructions using your CustomRRU (v4) and am experiencing the same issue.
My symptoms:
Have to tap once to start screen calibration
White second boot loader screen
White text on the home screen
If iLauncher is installed, the iLauncher graphics become corrupted (untested with Black Edtn 1.2).
This could be a shot in the dark, but could this be caused by IMGFG?
Hope this helps!
Ok after being up all night last nite working on it, I'm ready to give a few more methods a shot.
pof: If I run task 28 (hard reset) and close mtty...then I should run the custom RUU to install the ROM and select SPL-1.01 in the beginning right?
I'm just a little scared with SPL-1.01 as I'm not as protected like Oli's SPLs would.
akarandomjames said:
Ok after being up all night last nite working on it, I'm ready to give a few more methods a shot.
pof: If I run task 28 (hard reset) and close mtty...then I should run the custom RUU to install the ROM and select SPL-1.01 in the beginning right?
I'm just a little scared with SPL-1.01 as I'm not as protected like Oli's SPLs would.
Click to expand...
Click to collapse
no, all you'll get is a message calling you an idiot for not knowing that you can't flash a ROM with 1.01
Yea I actually did read that and flashed back to 1.04 before anything.
I attempted to redownload LVSW's latest release 3/26/07 and flashed it on my device...still white.
NOW I'm going to try the mtty method after learning and understanding mtty a little bit more.
I enjoy wasting 25 minutes each flash ^_^
Just want to confirm that this worked for me. Had the white screen problem with LSVW 3/25, 3/26 and WBME 1.2.
1. Download the FULL update from LVSW's first post.
2. Use NBHextract to rip the NBH file into seperate files.
3. Flash SPL-1.01MFG to your device
4. Flash OS.nb to device.
5. Enjoy a non white version of this great rom.
Click to expand...
Click to collapse
Now running LSVW 3/26. Very snappy! After getting it running correctly I reflashed to HARD-SPL v4.
I would also like to confirm that Flashing via Mtty has also worked for me. NO MORE WHITE SCREEN...
Even though that was the SOLUTION to the problem...I still wonder what the real source of the problem was.
ok...i wanted to flash with mtty. but when i start mtty, i get "cmd>" instead of "USB>". What is wrong?
Nothing is wrong. HARD-SPL V4 will show CMD>. Once you flash SPL 1.01 MFG, it will show up as USB>
I have a problem in that when I try the above I enter lnb OS.nb but I get a command error. Dont suppose anyone has any ideas?
mart_haj86 said:
I have a problem in that when I try the above I enter lnb OS.nb but I get a command error. Dont suppose anyone has any ideas?
Click to expand...
Click to collapse
yes, you're not running 1.01MFG or worse... you're running the unpatched one without being supercid.
type task32 then try it again.
also, if task32 returns Level=FF... I hope your OS boots or you're in trouble
not a total idiot . . . yet I can not figure out how to get rid of the ATT animated splash screen on the new AT&T branded rom.
I can change the main splash and welcomehead file, but not what I am supposing is the subsplash.
I have even cooked my own ruu nbh with just a subsplash which has worked on black roms, but seemingly has no effect on this rom
any ideas?
The only thing I can help you with, and I am sure you looked is try here.
Is the splash your talking about the annoying animated one, that has the load startup volume? I have tried a few roms myself and it has never shown up since using those.
the animated att gif and sound files are located in either the extended rom or the OEMOPERATORS folder. You just have to delete them before you cook your rom. Or post cooking, you just either overwrite or delete the two files in your windows folder... and another option too is to point your registry settings to your own files. should be in the HKLM/Software/HTC/AnimatedGif
Sorry if I'm not being clear on the exact locations of those files because I'm at work and I don't have my kitchen supplies here with me. But it should't be hard now that I've pointed you in the right direction.
thanks guys
I reflashed using the ATT branded ROM so that's why I got the animated startup (subsplash doesn't even show) so I'll reflash and reset it before it goes into the customizations.
Seems like it goes through two configurations - one from ? and the other from the extended rom - using "pimp my black v2" to unlock extended rom. However I can not delete any files located on the extended rom. Am I doing something wrong? I want to create my own autoconfig with just the things I need/want. I'd love to NOT install all the ppt stuff. Where is that autoconfig coming from?
apposite said:
I reflashed using the ATT branded ROM so that's why I got the animated startup (subsplash doesn't even show) so I'll reflash and reset it before it goes into the customizations.
Click to expand...
Click to collapse
I believe it's not in the ext rom, but the ROM itself. Disable it here: HKLM/Software/HTC/Startupanimation.
apposite said:
Seems like it goes through two configurations - one from ? and the other from the extended rom - using "pimp my black v2" to unlock extended rom. However I can not delete any files located on the extended rom. Am I doing something wrong? I want to create my own autoconfig with just the things I need/want. I'd love to NOT install all the ppt stuff. Where is that autoconfig coming from?
Click to expand...
Click to collapse
PTT is in the ROM not the ext rom. We're stuck with it for now.
my GSM module has something wrong,i think.when i flash 6.0.it was failed.when i flash 6.1 which without radio.nbh. it was successful.and then,first time boot up.sys must be reboot.OK,reboot.it stop in the secondsplash.it can connect pc with the activesync.but the phone screen is the secondsplash....i dont know why...pleaes help me..
thanks~~
I'm having almost the same problem. When booting, my phone gets stuck at the second splash screen every time. I tried reflashing numerous different ROMs, but I get the same problem every time. Occasionally, with a Dopod factory ROM, I get it to boot to the "no SIM" menu in Chinese, but after tapping through the menus, it just restarts and gets stuck at the 2nd splash screen. I searched all over the internet for various radio ROMs, but I can't find ones specific for the Cavalier. I tried some for different HTC WM6 phones, but it stops at 7% and tells me that the ROM isn't right for the device. I'd like to try a new radio ROM if I can, so if anybody has one, can you post it???
ttknf said:
I'm having almost the same problem. When booting, my phone gets stuck at the second splash screen every time. I tried reflashing numerous different ROMs, but I get the same problem every time. Occasionally, with a Dopod factory ROM, I get it to boot to the "no SIM" menu in Chinese, but after tapping through the menus, it just restarts and gets stuck at the 2nd splash screen. I searched all over the internet for various radio ROMs, but I can't find ones specific for the Cavalier. I tried some for different HTC WM6 phones, but it stops at 7% and tells me that the ROM isn't right for the device. I'd like to try a new radio ROM if I can, so if anybody has one, can you post it???
Click to expand...
Click to collapse
I don't think this has to do with the radio. From my experience in testing out cooked ROMS and trying to cookm my own ROMS for the Cav, the filesystem is a bit temperamental with too many flashes. I have had to format my ROM filesystem half a dozen times to fix small glitches such as incomolete flashes and hard locks. I can throw together a radio ONLY update for you but I doubt it will fix anything. This post describes how to unbrick (or format you phone) but you will lose ALL of your data and do it at your own risk.
http://forum.xda-developers.com/showthread.php?t=428589&highlight=brick
ookba said:
I don't think this has to do with the radio. From my experience in testing out cooked ROMS and trying to cookm my own ROMS for the Cav, the filesystem is a bit temperamental with too many flashes. I have had to format my ROM filesystem half a dozen times to fix small glitches such as incomolete flashes and hard locks. I can throw together a radio ONLY update for you but I doubt it will fix anything. This post describes how to unbrick (or format you phone) but you will lose ALL of your data and do it at your own risk.
http://forum.xda-developers.com/showthread.php?t=428589&highlight=brick
Click to expand...
Click to collapse
I've already followed this process with MTTY numerous times, it had no effect. Also, when I did info 8 and task 2a, there were no bad blocks to begin with. Is there something else that can be done w/MTTY to fix things? It'd be great if you could dump that radio.nbh onto this thread just to see if that'll fix things.
ttknf said:
I've already followed this process with MTTY numerous times, it had no effect. Also, when I did info 8 and task 2a, there were no bad blocks to begin with. Is there something else that can be done w/MTTY to fix things? It'd be great if you could dump that radio.nbh onto this thread just to see if that'll fix things.
Click to expand...
Click to collapse
Here is the Radio (05_GSM.nb) in the nbh. It's the one from the Dopod shipped ROM but I checked the versions and the HTC one is the same version. Copy this nbh file to your ROM Update folder and flash away. Hard SPL is recommended. This is a straight radio dump and I am not responsible if you brick your phone.
Haven't uploaded yet, will upload shortly.
ookba said:
Here is the Radio (05_GSM.nb) in the nbh. It's the one from the Dopod shipped ROM but I checked the versions and the HTC one is the same version. Copy this nbh file to your ROM Update folder and flash away. Hard SPL is recommended. This is a straight radio dump and I am not responsible if you brick your phone.
Haven't uploaded yet, will upload shortly.
Click to expand...
Click to collapse
Are you gonna upload that radio rom?
So, I flashed my frist rom back in April. I tried out the Energy Rom. Last night I tried out the Core Cell Evo Rom. This Rom started to give me trouble so I flashed to the current energy rom. I'm still new to this, so I think I may have made some kind of mistake that I'm not aware of.
I noticed that when I flashed to the new energy rom, the splash screen for the cell rom came up. Now whenever I try to change the date and time on my phone, it kinda locks up. I think it still functions, but because the screen is frozen I can't see what to press so I end up doing a restart. Does anyone know how I can remove all the remnants of the cell rom? I thought when you flash a new rom, it's supposded to completely get rid of the old rom?
First run TASK29, then flash preffered ROM, after that do HARD RESET, and then it must be OK
Some ROMs include a new splash screen, and some don't. The EnergyROM series doesn't include a splash screen, so that's why you can still see the Core splash screen.
You can find utilities to replace this if you search for "splash screen".
Task29 won't affect this (i.e. it doesn't touch the splash screen, nor the radio either), but it does a good job at wiping the ROM area itself.
If the problem still happens after a task29 and a flash (i.e. the lockups), then you should post about this in the thread relevant to the ROM you're running.
Thanks for the info guys. I'm at work but I'll try out the task29 thing when I get home. I didn't post this in the energy rom thread because I didn't want to seem like I was directing my problem at that rom until I had a good idea of what was going on. If the problems still persist, then that's where my next post will be.
You can always reflash a stock ROM. That will give you the original spash screen back and then you can flash the custom ROM again.
Well, it wasn't the splash screen that I was worried about. Seeing the splash screen made me think that the core cell rom was conflicting with the energy rom. After hearing what steviewevie had to say on the subject, I know otherwise. I'll also install a custom splash screen later now that I know that can be done to.
You can go here for the steps to change the splash screen its actually pretty easy and fun.
http://forum.xda-developers.com/showthread.php?t=576703
Ok, I ran Task29 and I've installed the stock rom. Do I need to do another HardSPL before I can flash a new rom?
No you only need to perform the hardspl once which you have already done so from now on when changing roms just make sure to task 29 then flash new rom and thats it
creglenn said:
No you only need to perform the hardspl once which you have already done so from now on when changing roms just make sure to task 29 then flash new rom and thats it
Click to expand...
Click to collapse
Oh? I didn't use the stock rom that was put up on this site. I actually downloaded the Tilt 2 rom from the HTC site. So I thought that would have made some kind of difference.
sigma20xx said:
Oh? I didn't use the stock rom that was put up on this site. I actually downloaded the Tilt 2 rom from the HTC site. So I thought that would have made some kind of difference.
Click to expand...
Click to collapse
HardSPL was designed to stay on the phone, even if you flash stock ROMs. You have to specifically run the relocker utility (from the HardSPL thread) if you want to go back to the stock SPL (e.g. for warranty return).
MOD Note
I'm moving your thread to General. This has nothing to do with ROM development. Custom ROM usage yes, but not Development.
Russ741
Hi everyone!
I managed to root my DHD last night, used the tool to get S-OFF and ENG-OFF thing, well, everything that I could. I changed my radio, and installed a custom rom, everything went well. Then, I decided I'd want a new theme..... And then everything goes... yeah..
I installed Android Revolution and chose CommonSense as my new theme.
Well, I as I read that you need to use CWM Recovery and install the theme as a .zip from there, so I did. Put the .zip in my sd root and installed the theme from there. But it seems that was not the way to do it.
And as I read the instructions, that was definitely not the way to do it.
So, now my phone boots, HTC with big letters comes up, and then it changes to HTC Quietly Brilliant with a twitch. After being on Quietly Brilliant, it goes to black for 400 ms, and changes back to Quietly Brilliant and starts to loop that.
I tested that I can still do fastboot, and go to CWM Recovery from there..
But, I firstly decided to come up on here to ask what should I do now?
You can reflash the rom or find a working theme and install so that the boot loop will be gone.
Sent from my Desire HD using XDA App
its only a bootloop chillout there are 3 options, 1. find the version of that thme for your rom and flash it again. 2. flash your rom again. 3. push your framework-res.apk to/system/framework/ using adb
Yeah, I think it's being fixed right now.
I tried installing theme again.. THE RIGHT WAY and the RIGHT THEME. But, that didn't help, so now I'm flashing the rom again.
It's a great relief that it was just a "bootloop chillout"
Thanks for your help Lopio & AndroHero!
c4tlub3 said:
Yeah, I think it's being fixed right now.
I tried installing theme again.. THE RIGHT WAY and the RIGHT THEME. But, that didn't help, so now I'm flashing the rom again.
It's a great relief that it was just a "bootloop chillout"
Thanks for your help Lopio & AndroHero!
Click to expand...
Click to collapse
if your going to mod your device expect many bootloops best idea is before you flash anything, do a nandroid backup in recovery, it only takes a minute and if anything goes wrong you dont have to mess about flashing a new rom, you can just restore your old one
next time, backup before you flash from the CWM.
if u have a boot loop, you just need to re-flash the rom.