So I have problem, I updated rom from sd card, it worked nicely, but when I try to update Radio, sd flashing app freezes in 'Update in Progress' state, in about 10 percents.
It takes about 1/2 hour to flsh radio rom. DON'T interrupt the flash or you will get a brick...
I will try it to leave flashing for several hours even status is not moving..
ultramag69 said:
It takes about 1/2 hour to flsh radio rom. DON'T interrupt the flash or you will get a brick...
Click to expand...
Click to collapse
I think what he is saying is if this happened the first time you tried flashing the radio you might have a brick at this point..
Best idea would be to try and flash shipped stock rom, you might get lucky and fluke it... WM06 from the carrier you originally had would be ok too as the radio might be able to be fixed but don't count on it...
Theres been limited success...
Good luck...
I managed to flash rom called Manilla 2d, sometimes I have no gsm message sometimes not, I tried to use mtty to access radioloader but there are always error message. It is possible to check physically(by opening case) if the radio stack is destroyed?
I installed WM5 via sd-card with radio rom, it was going really slowly, I thought it freezed again, but then finally it started moving, and finished instalation. Even now I cannot remember how many procedures I have done many different roms, radios, mtty procedures........ and finally radio works, wm works
Cool, glad to hear it.
Now would be a good time to flash Hard SPL V7. It can help you out of perilous situations. Please remember though, even though it worked this time round, it may not again. I personally DON'T flash the radio rom unless I REALLY have to. Either use cooked roms or edit the originals using Rom Koch. You can remove the rdio part and flash just the os.
Cheers...
ultramag69 said:
Cool, glad to hear it.
Now would be a good time to flash Hard SPL V7. It can help you out of perilous situations. Please remember though, even though it worked this time round, it may not again. I personally DON'T flash the radio rom unless I REALLY have to. Either use cooked roms or edit the originals using Rom Koch. You can remove the rdio part and flash just the os.
Cheers...
Click to expand...
Click to collapse
Great advice there. Find a radio you like and stick with that. With the Hermes being end of line there, you won't see many if any new Radio's available. In my experience the best ones to date are either 1.47 or the 1.56 radio.
Related
I wanted to install PDACorner v22 RBSN over NRBSN and I flashed defore the See here for more info Dr Puttingham solution suggested ROM via SD.
I have done the SD Flash once more with my WWE ROM 3.54 and in both ROMS the ORDER of flashing parts on my Tytn 's screen was
Code:
IPL,Bootloader,ExtROM,GSM,OS
I know we all use dutty's nbh tool v1.1 for compiling RUU_Signed.nbh .
I dare to make a thought about this tool makes the RBS ROMS to Hard Reset, because it makes the order of flashing
Code:
IPL,Bootloader,OS,GSM
meaning it flashes the Radio after the OS.
Both Stock ROMS with EXTRom flashes the Radio before the OS.
So is there any chance of changing the order in dutty's tool and do the Radio flash before the OS???
In that way we can check if THIS is the problem (and solution) of Hard Resets
Please post your thoughts on my theory and I will contact dutty about this thread to see if he can change his tool
lagoskon said:
I wanted to install PDACorner v22 RBSN over NRBSN and I flashed defore the See here for more info Dr Puttingham solution suggested ROM via SD.
I have done the SD Flash once more with my WWE ROM 3.54 and in both ROMS the ORDER of flashing parts on my Tytn 's screen was
Code:
IPL,Bootloader,ExtROM,GSM,OS
I know we all use dutty's nbh tool v1.1 for compiling RUU_Signed.nbh .
I dare to make a thought about this tool makes the RBS ROMS to Hard Reset, because it makes the order of flashing
Code:
IPL,Bootloader,OS,GSM
meaning it flashes the Radio after the OS.
Both Stock ROMS with EXTRom flashes the Radio before the OS.
So is there any chance of changing the order in dutty's tool and do the Radio flash before the OS???
In that way we can check if THIS is the problem (and solution) of Hard Resets
Please post your thoughts on my theory and I will contact dutty about this thread to see if he can change his tool
Click to expand...
Click to collapse
The only problem here, is that I remove the radio from my stock rom before flashing, and I have had no HR or freezing problems.
Edit: Though.. atm, a single rom flash doesn't last much more than a day...
interesting thread
I don't take shortcuts, I follow the dr's order down to the T, and does take a good half an hour to 45 min to get things running, I will monitor of quicker way of doing it, if it saves me time, I would love to know too, so .. here I am watching with anticipation.
zocster said:
I don't take shortcuts, I follow the dr's order down to the T, and does take a good half an hour to 45 min to get things running, I will monitor of quicker way of doing it, if it saves me time, I would love to know too, so .. here I am watching with anticipation.
Click to expand...
Click to collapse
I'm from Mars m8
NEVER FLASH RADIO WITH CUSTOM ROMS TOGETHER
ONLY RADIO
ONLY CUSTOM OS
OR RADIO WITH OS FROM ORIGINAL SHIPPED HERMES WM6.1 ON mars
anryl said:
ORIGINAL SHIPPED HERMES WM6.1
Click to expand...
Click to collapse
there's no official shipped wm6.1 for hermes as i know
I know all this about not flashing Radio all the time with roms. I just say that the sequense of parts is not the same.
It should be IPL,SPL, Nothing , OS without flashing radio and NOT IPL,SPL,OS, Nothing which is the case now
lagoskon said:
I know all this about not flashing Radio all the time with roms. I just say that the sequense of parts is not the same.
It should be IPL,SPL, Nothing , OS without flashing radio and NOT IPL,SPL,OS, Nothing which is the case now
Click to expand...
Click to collapse
Whatever the order of the pices, wouldnt the firmwear still have to go to the same places in the chip? Or you would end up in brick town.
Didn't someone say the HR's where due to part of the chip not being overwritten, and when you flash another rom, (that isnt a FULL shipped) it ended up causing incomparability issues?
veyka said:
Whatever the order of the pices, wouldnt the firmwear still have to go to the same places in the chip? Or you would end up in brick town.
Didn't someone say the HR's where due to part of the chip not being overwritten, and when you flash another rom, (that isnt a FULL shipped) it ended up causing incomparability issues?
Click to expand...
Click to collapse
Remember guys the Real Big Storage ROMs overwrite the ext_rom portion to use as the extra storage, since it wasnt designed to do this we can assume that sometimes it might not work correctly.
Sure the tools and everything work fine with it all most of the time.
The reason flashing an official ROM seems to remedy the issues with Hard Resets is that if you reflash everything, the flash memory is refreshed back to the correct OS and ext_rom arrangement, then flashing an RBS ROM onto this area should in theory work fine thanks to the "spring clean" of the memory area.
mrvanx said:
Remember guys the Real Big Storage ROMs overwrite the ext_rom portion to use as the extra storage, since it wasnt designed to do this we can assume that sometimes it might not work correctly.
Sure the tools and everything work fine with it all most of the time.
The reason flashing an official ROM seems to remedy the issues with Hard Resets is that if you reflash everything, the flash memory is refreshed back to the correct OS and ext_rom arrangement, then flashing an RBS ROM onto this area should in theory work fine thanks to the "spring clean" of the memory area.
Click to expand...
Click to collapse
Thanks for clearing that up, though it was long those lines! (So close, but so far)
veyka said:
Thanks for clearing that up, though it was long those lines! (So close, but so far)
Click to expand...
Click to collapse
It wasnt until recently that I experienced any hard reset issues with any of the ROMs here, i noticed that leading up to a Hard Reset or freeze at the boot screen things such as file operations and running programs seemed to fail...with access denied errors and etc..
Also programs failed to save registry data aswell, coreplayer repeatedly asked for the activation key (which ofcourse ive got).
Leading me to believe that the storage portion of the OS was not working correctly...and since thats the part we have (pardon the term) misused )) then perhaps a reflash to the old configuration to give the storage area a flat format would do the trikc...which it did.
So its definatly advised, even if you havent experienced the issues, to one in a while before you flash a new ROM, flash an official ROM which uses and ext_rom aswell to give it a quick clean out.
lagoskon said:
I wanted to install PDACorner v22 RBSN over NRBSN and I flashed defore the See here for more info Dr Puttingham solution suggested ROM via SD.
I have done the SD Flash once more with my WWE ROM 3.54 and in both ROMS the ORDER of flashing parts on my Tytn 's screen was
Code:
IPL,Bootloader,ExtROM,GSM,OS
I know we all use dutty's nbh tool v1.1 for compiling RUU_Signed.nbh .
I dare to make a thought about this tool makes the RBS ROMS to Hard Reset, because it makes the order of flashing
Code:
IPL,Bootloader,OS,GSM
meaning it flashes the Radio after the OS.
Both Stock ROMS with EXTRom flashes the Radio before the OS.
So is there any chance of changing the order in dutty's tool and do the Radio flash before the OS???
In that way we can check if THIS is the problem (and solution) of Hard Resets
Please post your thoughts on my theory and I will contact dutty about this thread to see if he can change his tool
Click to expand...
Click to collapse
OK I FOUND IT WHAT YOU MEAN THE TOOL FOR IT IS htcRIE_0.4.0.49.exe as it opens the original ROM deletes ipl spl gsm and saves new orig rom with the order off flashing - splash splash extrom os
Hi all, a question to anyone who may know the answer.
I have tried searching & reading but have only ended up twisting up my brain!
Ok, i have a touch diamond with Olinex unsigned 1.37 Hard SPL
I want to flash it with the newest HTC Europe stock rom but when i try to flash it, it starts and continues all the way to 100%, before giving me a error 270 - corrupted file image..
Tried downloading the rom again, different usb ports & pretty much everything else i can think of, to the point now that i just can't think of any other possible ways of doing it.
Can anyone help me out... pleeeeeeeease!
Sorry no quick answer as it soundsfrom your breif description like you are doing everything right...
What Radio and Rom are you on currently as this might give us some more clues as to what might be causing the issue?
I can freely flash between almost any rom that takes my fancy, just today i have flashed through aztor 2.0, duttys newest, vics 3.4, and the ultimate wwe.. trying to find a solution!
I can flash whatever radio i want, again with no issues. Maybe the links i have for the rom are corrupt? Like i said i've downloaded it twice, but still get that error after 100% completion.
adrenalin said:
I can freely flash between almost any rom that takes my fancy, just today i have flashed through aztor 2.0, duttys newest, vics 3.4, and the ultimate wwe.. trying to find a solution!
I can flash whatever radio i want, again with no issues. Maybe the links i have for the rom are corrupt? Like i said i've downloaded it twice, but still get that error after 100% completion.
Click to expand...
Click to collapse
You need to flash the newest stock rom using the internal storage method. Details are on the thread for the stock 2.03 rom
THe Internal Method is always the starting point....if that is not it then,
Yeah, when the error speaks about corruption, this generally means that there was a incompatibility issue. I've seen this problem and I don't recall if the incompatibility was the Hard SPL related or not. My suspicion is that it is .....
band27 said:
THe Internal Method is always the starting point....if that is not it then,
Yeah, when the error speaks about corruption, this generally means that there was a incompatibility issue. I've seen this problem and I don't recall if the incompatibility was the Hard SPL related or not. My suspicion is that it is .....
Click to expand...
Click to collapse
THe original 2.03 roms don't work on hard spl when used through the PC and give the error at the end on 100%.
Cooked versions flash succesfully normal ways however the original version will work properly via the internal storage method as discovered on the original 2.03 thread
I solved it by flasing the Olipro 1.93 hard SPL after flashing the stock 2.0 ROM.
As by everyone I had a corruption message on the screen after the 100% of flashing... So just flash Olipro 1,.93 over it and the diamond will startup with the new 2.03 ROM
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?
Hello, I've been having some weird issues with my phone, first of all, this is ROM related.
Whenever I flash to a new rom, after using the rom perfectly for 1-2 days, rebooting ect...
After the 3rd day, or having the phone on for more than 24 hours, eventually after rebooting the phone, it will give me the dreaded "Device cannot boot, please hold volume up to reset your phone.
Then the phone works fine and the issue repeats over and over again.
using latest htc radio rom and latest htc winmo 6.5 rom
I really like the phone, but these stupid retarded issues keep me from actually considering this a stable phone to use for long-term use.
I'm at my ends with this phone and will end up loading the stock t-mo rom and selling it.
glcK23 said:
Hello, I've been having some weird issues with my phone, first of all, this is ROM related.
Whenever I flash to a new rom, after using the rom perfectly for 1-2 days, rebooting ect...
After the 3rd day, or having the phone on for more than 24 hours, eventually after rebooting the phone, it will give me the dreaded "Device cannot boot, please hold volume up to reset your phone.
Then the phone works fine and the issue repeats over and over again.
using latest htc radio rom and latest htc winmo 6.5 rom
I really like the phone, but these stupid retarded issues keep me from actually considering this a stable phone to use for long-term use.
I'm at my ends with this phone and will end up loading the stock t-mo rom and selling it.
Click to expand...
Click to collapse
maybe a bad flash/rom? did you try downloading a new version of the rom and flashing...?
rvt1000 said:
maybe a bad flash/rom? did you try downloading a new version of the rom and flashing...?
Click to expand...
Click to collapse
Yes sir, this has happened to almost every rom I have tried. I even hard-resetted the device after installing a new ROM to make sure everything was clean.
glcK23 said:
Yes sir, this has happened to almost every rom I have tried. I even hard-resetted the device after installing a new ROM to make sure everything was clean.
Click to expand...
Click to collapse
odd.....sorry i don't know what to say to help, sounds like a hardware issue not being able to access the ROM files correctly. i guess you could either sell or swap back to stock and try warranty..
Here's what I'd do.
Flash back to stock SPL, and reflash to same ROM as when you first got the phone, remember to hard reset after flash and remove SIM / SD cards etc.
If that doesn't work, maybe try flashing via SD card, but at that point I would replace under warranty.
If stock SPL fixes it you may want to ask in the HardSPL thread.
Hope this helps, good luck
I've seen people say to flash a stock ROM before flashing a cooked one - why? Surely all the data from the last ROM is overwritten by the cooked ROM anyway, isn't it?
iridium21 said:
I've seen people say to flash a stock ROM before flashing a cooked one - why? Surely all the data from the last ROM is overwritten by the cooked ROM anyway, isn't it?
Click to expand...
Click to collapse
I'm not sure about the TP2 but on the hermes it was always recommended for going from an extended storage rom to a normal rom. Might have just carried over since then.
Doesn't make a difference, its a myth. The flash chip gets rewritten.
petard said:
Doesn't make a difference, its a myth. The flash chip gets rewritten.[/QUOTE
If custom ROM without radio You should flash stock ROM first(if you would like to have it)
Click to expand...
Click to collapse
petard said:
Doesn't make a difference, its a myth. The flash chip gets rewritten.
Click to expand...
Click to collapse
Not a myth, at least to some devices like the diamond, HD and the HD2 where members who decide to skip this step are finding themselves with very unstable devices that often turn off or restart on there own.
Flashing a stock rom or using the mtty tool erasers any artifacts that can be left behind when flashing cooked roms.
Flashing Procedures I use:
• flash stock rom or mtty tool found in sig.
• flash cooked rom
• hard reset twice
Never had any issues from automatic resetting of any kind!
ive been flashing since the wizard, and probably after 20 phones ive never flashed stock rom first. i actually stop hard resetting to.
intruda119 said:
ive been flashing since the wizard, and probably after 20 phones ive never flashed stock rom first. i actually stop hard resetting to.
Click to expand...
Click to collapse
As mentioned, some devices are more prone to it perhaps. There are a lot of threads that speak to members dealing with device resetting and other glitches and the remedy recommended is always the same.
For me, it's just habit now....
Only do this as a last ditch effort. Say u flash a custom rom, hard reset as u should, then configure the rom. But u seem to be getting odd screen freezes and problems that only u seem to get and not anyone else for that particular rom. U go into the thread of the rom asking and everyone says its just u. Well at this point u would flash stock rom, hard reset, flash same custom rom, hard reset, now the custom rom works perfect! Why? How th hell should i know? I just know what works!
I think that flashing a whole stock ROM each time is a bit over the top. If you want to be on the safe side, then do a hard reset on your old ROM, then flash the new ROM, then hard reset again. That should do as much as flashing the stock ROM would do.
I think main the benefit is because the CustomRUU doesn't perform a Hard Reset after flashing, where as the Stock RUU does.
Some people prefer to do a "task 29" nand format. Unless you've been flashing dodgy ROMs that go outside of where they are meant to then I think you'll be OK.
JM2c's
Dave
DaveShaw is the man so take his advice.
I have flashed over 40 ROMs (all from XDA or HTC) on my TP2 and I never flash back to stock. I have had no issues. I also did the same with my Tilt1.