Compatibility between HSPLs and ROMs - Touch Diamond, MDA Compact IV ROM Development

Hey there. I've been fooling around on these forums quite a bit since i got my diamond, and would like to thank everyone for all their hard work: i'd have replaced my diamond long ago if it wasn't for all the ingenuity found here.
I've been trying different ROMs, and lately (since 2.03 ROMs), my phone has started to reflash itself, after strange lock ups, and hangs at boot/splash frequently. I'm reflashing at least 3 times a day.
tl;dr: I have a DIAM130. Is there a particular HardSPL that is compatible with 2.03 ROMs? Are there particular HardSPLs compatible with only certain Diamonds? Basically, zomg y r der so many HSPLs and do they fit certain ROMs, or certain phone models? or what? Do you need a certain HSPL to boot 2.03 ROMs?
By reflashing itself, I mean it will lock up or begin to operate "laggedly", at which point i would soft-reset, leading to the phone reflashing itself (like first boot, asks me to align screen, set date etc).
EDIT: Thanks for the help everyone, my problem has been solved by reflashing stock SPL and 2.03 ROM, then proceeding with custom ROMs and SPL.

halpmf said:
Hey there. I've been fooling around on these forums quite a bit since i got my diamond, and would like to thank everyone for all their hard work: i'd have replaced my diamond long ago if it wasn't for all the ingenuity found here.
I've been trying different ROMs, and lately (since 2.03 ROMs), my phone has started to reflash itself, after strange lock ups, and hangs at boot/splash frequently. I'm reflashing at least 3 times a day.
tl;dr: I have a DIAM130. Is there a particular HardSPL that is compatible with 2.03 ROMs? Are there particular HardSPLs compatible with only certain Diamonds? Basically, zomg y r der so many HSPLs and do they fit certain ROMs, or certain phone models? or what? Do you need a certain HSPL to boot 2.03 ROMs?
Click to expand...
Click to collapse
right, so if i have managed to translate this into English correctly, you want to know why your phone is playing up, and is it due to the Hard SPL.
The various Hard SPLs have different functions available, mainly for testing purposes. The common one is 1.34 (which is what i have been using for about a year, and not had problems).
i would recommend flashing Hard SPL 1.34, then flashing one of the 2.03 stock ROMs (remembering to Hard Reset after flashing) and see if it 'crashes' or whatever (couldn't really tell from your post exactly what it was doing - it wont "reflash" itself).
If it still has problems, then flash the original SPL and ROM and send it back under warrenty (if it is still covered).

Some times these random crashes and weird occurrences are due to over flashing or "a bloated ROM" try different Hard SPL's if you would like. I'm using Hard SPL 1.93 (one of the newer ones and often recommended by chefs).
Take a look at the solution of this thread as a possible option to fixing your issue as well......http://forum.xda-developers.com/showthread.php?t=490182

Related

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

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

[Q] About flashing newest stock rom with Hard SPL

Hi all, a question to anyone who may know the answer.
I have tried searching & reading but have only ended up twisting up my brain!
Ok, i have a touch diamond with Olinex unsigned 1.37 Hard SPL
I want to flash it with the newest HTC Europe stock rom but when i try to flash it, it starts and continues all the way to 100%, before giving me a error 270 - corrupted file image..
Tried downloading the rom again, different usb ports & pretty much everything else i can think of, to the point now that i just can't think of any other possible ways of doing it.
Can anyone help me out... pleeeeeeeease!
Sorry no quick answer as it soundsfrom your breif description like you are doing everything right...
What Radio and Rom are you on currently as this might give us some more clues as to what might be causing the issue?
I can freely flash between almost any rom that takes my fancy, just today i have flashed through aztor 2.0, duttys newest, vics 3.4, and the ultimate wwe.. trying to find a solution!
I can flash whatever radio i want, again with no issues. Maybe the links i have for the rom are corrupt? Like i said i've downloaded it twice, but still get that error after 100% completion.
adrenalin said:
I can freely flash between almost any rom that takes my fancy, just today i have flashed through aztor 2.0, duttys newest, vics 3.4, and the ultimate wwe.. trying to find a solution!
I can flash whatever radio i want, again with no issues. Maybe the links i have for the rom are corrupt? Like i said i've downloaded it twice, but still get that error after 100% completion.
Click to expand...
Click to collapse
You need to flash the newest stock rom using the internal storage method. Details are on the thread for the stock 2.03 rom
THe Internal Method is always the starting point....if that is not it then,
Yeah, when the error speaks about corruption, this generally means that there was a incompatibility issue. I've seen this problem and I don't recall if the incompatibility was the Hard SPL related or not. My suspicion is that it is .....
band27 said:
THe Internal Method is always the starting point....if that is not it then,
Yeah, when the error speaks about corruption, this generally means that there was a incompatibility issue. I've seen this problem and I don't recall if the incompatibility was the Hard SPL related or not. My suspicion is that it is .....
Click to expand...
Click to collapse
THe original 2.03 roms don't work on hard spl when used through the PC and give the error at the end on 100%.
Cooked versions flash succesfully normal ways however the original version will work properly via the internal storage method as discovered on the original 2.03 thread
I solved it by flasing the Olipro 1.93 hard SPL after flashing the stock 2.0 ROM.
As by everyone I had a corruption message on the screen after the 100% of flashing... So just flash Olipro 1,.93 over it and the diamond will startup with the new 2.03 ROM

Problems after flashing roms.

After flashing some of the recent roms here on XDA, I seem to be having a bit of a problem.
After installing some programs,the program icons change in to windows logos and i'm unable to use them and my phone locks up instantly and only a hard reset will work.
If i do a soft reset i only get to the windows mobile screen or htc startup animation screen, then it freezes.
I have been flashing roms for a couple of years and have never had this problem,any help would be appreciated.
owz206 said:
After flashing some of the recent roms here on XDA, I seem to be having a bit of a problem.
After installing some programs,the program icons change in to windows logos and i'm unable to use them and my phone locks up instantly and only a hard reset will work.
If i do a soft reset i only get to the windows mobile screen or htc startup animation screen, then it freezes.
I have been flashing roms for a couple of years and have never had this problem,any help would be appreciated.
Click to expand...
Click to collapse
There's not alot we can tell you if you don't tell us about your device, rom, radio, hardspl etc setup.
I'm using C.T 6.4 original touchflo but have tried others. I have olinex 1.40 spl
and have a DIAM 100 model and radio 1.00.25.05
Try another ROM.............there is that freak of nature possiblity that the Hard SPL is incompatible (rare).
If another Rom persists, then move to Hard Spl 1.93. I know some Chefs recommend a specific Hard Spl at times but again it's rare.
Can i just flash 1.93 spl over 1.40 spl, or is there a different way of doing it.
*Edit* I just tried to install 1.93 spl and it didnt work it still says i have 1.40 spl,what am i doing wrong ?
These Hard SPL developer's edition has write protection. What you need is an APP called Jump SPL....http://forum.xda-developers.com/showthread.php?p=3328000#post3328000.....POST #10
I'm using CT 6.4 OrigTF Full with HSPL 1.93 with absolutely no problems (apart from a landscape bug that I solved by installing the original Diamond Volume Control). I highly recommend it, for me it's the best I've ever used in terms of speed, stability and functionality. Remember to Hard-reset after flash. You migh also have a bad flash or a bad download. If changing HSPL don't work, try to download the ROM again and re-flash.
When I upgraded HSPL from 1.40 to 1.93 I used a version with jump-SPL included, don't remember where I found it though.
Good Luck!
I always do a hard reset after a flash and have tried numerous roms but seem to have the same problem with all the roms.
Think i might have a problem with my diamond
Thanks for all your suggestions.
hello. I have a problem. I wanted to put new rom on friend`s Diamond but when it finishes, it says error 270, the image file is corrupted.On Diamond:Upgrade rom code error, please try again.What can I do now?I made soft reset and repeated again, nothing changes.I cannot even turn off the device.It only shows tricolor,security unlocked.(RUU Diamind HTC WWE 2.03.405.2 Radio signed diamond 52.51.25.26.1.09.25.23 ship.exe (100MB))
I am ok.Made it with a different rom.
O.k. I've tried a few different roms and hard spl today, and deleted my internal and phone storage and my phone is still not working properly.
It works fine after a flash and hard reset, but as soon as i turn it off then back on it freezes either on the diamond black boot screen or windows boot screen.
Looks like I need to get a new phone
Don't know if this is of any help but, when i cooked some roms for my "Artemis" i would get this sort of error if the rom was a little too big (I had added too many programs <5mb too much it would build and flash without error) it would work for a few days the slowly start to loose programs as if it had a virus or something deleting stuff slowly.
the only way to fix it was to flash a stock rom inc ipl,spl and radio then re-flash a custom rom, (a new custom rom alone would not cure it) i think the rom when flashing filled the area designated for the rom then started to overright the spl or ipl
just a thought? i don't know weather the diamond would suffer from the same problem with a bloated rom!
dose anyone know what the max size for a diamond rom is?
what happens if the rom is a little too big say 2mb?
Thanks,I've just flashed the new windows 6.5 rom which is working at the moment,but if it fails i'll give your idea a try.
owz206 said:
Thanks,I've just flashed the new windows 6.5 rom which is working at the moment,but if it fails i'll give your idea a try.
Click to expand...
Click to collapse
Man i had almost the similar issue in the recent times .. The only work around is to download and flash a stock Rom ( no matter which one it is ) , like what explained in the previous post . Use the stock fr a day or 2 , then flash it back .

can anyone give me a radio.nbh??

my GSM module has something wrong,i think.when i flash 6.0.it was failed.when i flash 6.1 which without radio.nbh. it was successful.and then,first time boot up.sys must be reboot.OK,reboot.it stop in the secondsplash.it can connect pc with the activesync.but the phone screen is the secondsplash....i dont know why...pleaes help me..
thanks~~
I'm having almost the same problem. When booting, my phone gets stuck at the second splash screen every time. I tried reflashing numerous different ROMs, but I get the same problem every time. Occasionally, with a Dopod factory ROM, I get it to boot to the "no SIM" menu in Chinese, but after tapping through the menus, it just restarts and gets stuck at the 2nd splash screen. I searched all over the internet for various radio ROMs, but I can't find ones specific for the Cavalier. I tried some for different HTC WM6 phones, but it stops at 7% and tells me that the ROM isn't right for the device. I'd like to try a new radio ROM if I can, so if anybody has one, can you post it???
ttknf said:
I'm having almost the same problem. When booting, my phone gets stuck at the second splash screen every time. I tried reflashing numerous different ROMs, but I get the same problem every time. Occasionally, with a Dopod factory ROM, I get it to boot to the "no SIM" menu in Chinese, but after tapping through the menus, it just restarts and gets stuck at the 2nd splash screen. I searched all over the internet for various radio ROMs, but I can't find ones specific for the Cavalier. I tried some for different HTC WM6 phones, but it stops at 7% and tells me that the ROM isn't right for the device. I'd like to try a new radio ROM if I can, so if anybody has one, can you post it???
Click to expand...
Click to collapse
I don't think this has to do with the radio. From my experience in testing out cooked ROMS and trying to cookm my own ROMS for the Cav, the filesystem is a bit temperamental with too many flashes. I have had to format my ROM filesystem half a dozen times to fix small glitches such as incomolete flashes and hard locks. I can throw together a radio ONLY update for you but I doubt it will fix anything. This post describes how to unbrick (or format you phone) but you will lose ALL of your data and do it at your own risk.
http://forum.xda-developers.com/showthread.php?t=428589&highlight=brick
ookba said:
I don't think this has to do with the radio. From my experience in testing out cooked ROMS and trying to cookm my own ROMS for the Cav, the filesystem is a bit temperamental with too many flashes. I have had to format my ROM filesystem half a dozen times to fix small glitches such as incomolete flashes and hard locks. I can throw together a radio ONLY update for you but I doubt it will fix anything. This post describes how to unbrick (or format you phone) but you will lose ALL of your data and do it at your own risk.
http://forum.xda-developers.com/showthread.php?t=428589&highlight=brick
Click to expand...
Click to collapse
I've already followed this process with MTTY numerous times, it had no effect. Also, when I did info 8 and task 2a, there were no bad blocks to begin with. Is there something else that can be done w/MTTY to fix things? It'd be great if you could dump that radio.nbh onto this thread just to see if that'll fix things.
ttknf said:
I've already followed this process with MTTY numerous times, it had no effect. Also, when I did info 8 and task 2a, there were no bad blocks to begin with. Is there something else that can be done w/MTTY to fix things? It'd be great if you could dump that radio.nbh onto this thread just to see if that'll fix things.
Click to expand...
Click to collapse
Here is the Radio (05_GSM.nb) in the nbh. It's the one from the Dopod shipped ROM but I checked the versions and the HTC one is the same version. Copy this nbh file to your ROM Update folder and flash away. Hard SPL is recommended. This is a straight radio dump and I am not responsible if you brick your phone.
Haven't uploaded yet, will upload shortly.
ookba said:
Here is the Radio (05_GSM.nb) in the nbh. It's the one from the Dopod shipped ROM but I checked the versions and the HTC one is the same version. Copy this nbh file to your ROM Update folder and flash away. Hard SPL is recommended. This is a straight radio dump and I am not responsible if you brick your phone.
Haven't uploaded yet, will upload shortly.
Click to expand...
Click to collapse
Are you gonna upload that radio rom?

[Q] Can't flash Hardspl after Kaiser immersion in water

First, the story: Kaiser / leaky shower / drip drip drip / RIP!
My kaiser has gradually come back from the dead after drying on my desk for a month.
I can no longer flash anything except the stock 6.1 winmo rom. I've tried all methods: SD & USB both work for the said stock rom but nothing else.
My tricolor screen reads: KAIS130/ SPL 3.28.0000 / CPLD-8
I'd like to flash android back on this thing but I can't Any clue?
I have mtty access too if it helps. When I flash anything through usb or SD card, I'm stuck at 0% or on the "loading screen".
I've read many threads here but no solution works for me. I'm not excluding the idea that something may have fried permanently in this kaiser so I'm more looking for some troubleshooting directions, to make sure.
Water immersion can cause a lot of problems, not so much from the water itself, but rather the deposition of metal across leads and junctions caused by electrolysis of the solder used to join components to the pcb.
Provided the damage is not too widespread it is sometimes possible to revive the device, however it requires a complete disassembly and careful inspection of practically every component and connection on the mainboard, and the careful brushing clean of any 'furry' component terminations or leads.
I am surprised that it actually boots and is able to be flashed with WM.
If it is a stock SPL then you will need to HardSPL it anyway, since it will not allow you to flash anything other than stock otherwise.
Note that as far as I am aware, 3.28 is a stock spl, rather than HardSPL which is usually 2.29 or above.
Another thing, have you tried running android from SD? I know it is not quite the same, but if it works on SD, there is no reason for it not to be nand'able
This is actually the second time my Kaiser has been drowned in water (first time is now referred to as "the 2009 faulty Roman air-conditionning incident" and it took 6months for the Kaiser to recover) and full disassembly and cleaning helped A LOT in both cases (green stuff inside). I can now say that my Kaiser is water-proof At least it's built like a tank - except for the cheap breakable plastic shell.
I tried so many complicated solutions that I didn't even try android on SD I'll look into it tomorrow.
PS: Latest stock rom from Hong Kong can't be flashed ("not allowed"), only my French rom is flashable.
Provided you can flash something 6.1 you can run android from SD, and also should be able to HardSPL it to allow flashing of other roms, including the android nand boot nbh.
I think it's incredible that your kaiser has survived this twice, I'd take good care of it from now on, third time you may not be as fortunate
coincoinlapin said:
First, the story: Kaiser / leaky shower / drip drip drip / RIP!
My kaiser has gradually come back from the dead after drying on my desk for a month.
I can no longer flash anything except the stock 6.1 winmo rom. I've tried all methods: SD & USB both work for the said stock rom but nothing else.
My tricolor screen reads: KAIS130/ SPL 3.28.0000 / CPLD-8
I'd like to flash android back on this thing but I can't Any clue?
I have mtty access too if it helps. When I flash anything through usb or SD card, I'm stuck at 0% or on the "loading screen".
I've read many threads here but no solution works for me. I'm not excluding the idea that something may have fried permanently in this kaiser so I'm more looking for some troubleshooting directions, to make sure.
Click to expand...
Click to collapse
if you flased the 1.65 radio version i have heard people having issues with it. i think somewhere on this forum there are instructions to get a different version on which wil then reopen your ability to flash the custom roms.
Yes
ghghgh14702 said:
if you flased the 1.65 radio version i have heard people having issues with it. i think somewhere on this forum there are instructions to get a different version on which wil then reopen your ability to flash the custom roms.
Click to expand...
Click to collapse
Radio could interrupt some things. But then again, with jumpspl or sspl (dont know which one is correct, the one with the froggy icon) makes you go into bootloader mode from ram if im correct. You should be able to hardspl then...
The radio version which does that is 1.65.17.10, which is not available from the Ultimate Radio Thread, for that very reason, it is only that particular radio, not the other radios in the 1.65 series that causes the problem.
I am using the 1.65 radio in my sig, and have flashed and reflashed many times, with no problems.
zenity said:
The radio version which does that is 1.65.17.10, which is not available from the Ultimate Radio Thread, for that very reason, it is only that particular radio, not the other radios in the 1.65 series that causes the problem.
I am using the 1.65 radio in my sig, and have flashed and reflashed many times, with no problems.
Click to expand...
Click to collapse
sorry, knew it was one of the 1.65, since he said he flashed an official rom if he has 1.65 it will be that version so I didn't look up the complete version as that was enough info for him.
I was too optimistic...The Kaiser recovered only for two days - I tried haret to load Android from SD, but it hung at some point.
Now there's a new error message, which also appeared after the first drowning: The sim door is open ... device will shut down in 10 secs. ZAP!
@MathijsNL
I'll have to look into your Froggy thing

Categories

Resources