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?
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
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.
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 .
I've read lots of comments, these very unwanted random hard-resets are suppose to be a common bug, however the suggested fixes dont seem to work for me, anyone else having the same issue?
Note: The issue must be software related, it only started happening to me immediately after a ROM update a few months back.
What usually happens:
- Install a ROM -> Configure It -> Install Apps... all looks good
- At some random point (could be days or weeks) the phone will lock up (usually on the password screen)
- A soft reset is required to rectify the lock-up
(i.e. the red button on back of phone)
- Phone hard-resets itself
Suggested Solutions:
1) Upgrade to HardSPL 1.93 - made no difference
2) I have tried running MTTY a few times, also no difference
3) Try different ROM's, I thought it might be just a bug with the WWE ROM, but it happens with the Energy ROM too
Just out of interest:
Interestingly, my wifes phone, which I do exactly the same updates on (same phone, same ROM, same Radio, etc), is working completely fine...
Hi
i had the same problem...for solve the problem, just flash the stock rom...you can download from htc website...than you can flash any rom you like and everytjing will work fine.
for any help just ask!
businello2000 said:
Hi
i had the same problem...for solve the problem, just flash the stock rom...you can download from htc website...than you can flash any rom you like and everytjing will work fine.
for any help just ask!
Click to expand...
Click to collapse
Hi, thanks for suggestion, although yep I tried that too. There is no stock ROM for an imported phone on Optus, but I just used the stock Telstra one that was on the forums, then after a while went back to the WWE ROM, and the same issue still occurs.
No other ideas for resolving the hard reset issues?
Next time it happens, I might try pulling the battery out instead of using the reset button on the back of the phone.. but clearly something is wrong :-/
i have had this a couple of times, about 6 months ago and last week. i just flashed a different ROM, flashing the same one again didnt help, so just downloaded a different one and went with that.
seems to be ok now
flash this rom and do a hard reset after flashing:
http://uploading.com/files/WY03RBG2/Stock rom noSPL no Radio.rar.html
I've also posted the same link here:
http://forum.xda-developers.com/showpost.php?p=4057376&postcount=3
matrix77 said:
flash this rom and do a hard reset after flashing:
http://uploading.com/files/WY03RBG2/Stock rom noSPL no Radio.rar.html
I've also posted the same link here:
http://forum.xda-developers.com/showpost.php?p=4057376&postcount=3
Click to expand...
Click to collapse
Thanks again for suggestions so far, but above fix only lasted about 5 days before another intermittent phone crash & subsequent hard reset, much the same as I have had experimenting with a range of stock and other ROM's :-/
I don't think the fix is as simple as just putting a Stock Rom -> Hard Reset -> MTTY -> New Rom -> Hard Reset. Im pretty sure its a software problem, but I dont see how the problem can survive such rigorous formatting...
Is noone else having the problem? Sounds like most are solved with 1 use of MTTY.
I searched a lot and found your thread.
I was upgrading my friend's Diamond, when he tells me that it hard resets itself without a reason. At first I thought it was the ROM's problem, so I switched to another one. But after I flashed the ROM, during the process of setting up the phone (settings, softwares), at some random point of installing random software, the phone says that the software was not installed successfully. After several re-flash, re-install, and ROM switching, it appears to me it's not a software problem.
It seems that it's at some point when the internal storage (not the NaviNAND) reaches a specific size, the device would fail and hangs (or not, randomly, but you can't install anything further), after a soft-reset, it will hard resets itself instead, it looks like some "badblocks" (sort of) on the internal storage NAND to me.
Is there a way to figure out if my theory's correct? I'm wondering if there is any tool that can run some diagnose on the internal NAND. If I'm correct and there is tool that can do so, it must have the ability to mask the bad pages on the NAND, right?
EDIT: There's a way to re-produce the situation. Just download some big apps (several MBs big) and install them in order. It will almost always hang at the same point.
The only solution is:
1st MTTY and run task 29 to format the device to make it clean and no left over stuff from the last ROM.
2nd Install different ROM
If you have bad sectors in the device, MTTY might not help much here, I guess.
Hi maddie, yes you might be onto something, I assume you already tried the usual fixes: (Stock Rom -> Hard Reset -> MTTY -> New Rom -> Hard Reset)? You can tell it to format the NaviNAND during the hard reset.
I think my issue might be different to yours though, as mine does not happen 'when installing software' mine happens days/weeks after setting up the phone.. It usually goes down like this: I pull the phone out of my pocket -> its locked on the password screen usually (cant type) -> pull the battery out or press the soft-reset button -> bang.. phone hard-resets.
I will make 1 suggestion though, instead of using all the nice fancy mods, and SPB Mobile Shell (looks like sense ui), I went back to a boring old stock rom, and well after 1 month its still going.. I absolutely hate it, but I dont want to buy another phone quite yet, so gonna go old-skool.
Let me know how you go, and as above if you did all the standard suggestions? It sounds like you need to somehow instruct the phone not to use those bad memory spots, but ive no idea if such a tool exists im afraid.
maddie said:
I searched a lot and found your thread.
I was upgrading my friend's Diamond, when he tells me that it hard resets itself without a reason. At first I thought it was the ROM's problem, so I switched to another one. But after I flashed the ROM, during the process of setting up the phone (settings, softwares), at some random point of installing random software, the phone says that the software was not installed successfully. After several re-flash, re-install, and ROM switching, it appears to me it's not a software problem.
It seems that it's at some point when the internal storage (not the NaviNAND) reaches a specific size, the device would fail and hangs (or not, randomly, but you can't install anything further), after a soft-reset, it will hard resets itself instead, it looks like some "badblocks" (sort of) on the internal storage NAND to me.
Is there a way to figure out if my theory's correct? I'm wondering if there is any tool that can run some diagnose on the internal NAND. If I'm correct and there is tool that can do so, it must have the ability to mask the bad pages on the NAND, right?
EDIT: There's a way to re-produce the situation. Just download some big apps (several MBs big) and install them in order. It will almost always hang at the same point.
Click to expand...
Click to collapse
I got the same problem recently and I am still trying different way to solve it.
My Hard-reset happen:
After flashing new rom -> Installation of software ->
-> launching programs -> when some got may holding or loading without response
-> Soft-reset (red bottom) -> It automatically Hard-reset....
Similar thinking with you, I think that maybe one of those reasons leading the hard reset:
1. Device got bad sector while flashing for different roms;
2. New Radios got bug and crash with the new version of roms;
3. Too many things stored in Internal Storage;
kenleekwanho said:
1. Device got bad sector while flashing for different roms;
2. New Radios got bug and crash with the new version of roms;
3. Too many things stored in Internal Storage;
Click to expand...
Click to collapse
I like this logic, im in the position of owning 2 HTC Diamonds with identical ROM, Radio, Applications, 1 works perfectly, 1 is resetting.
It 'probably' indicates that its hardware related, I doubt its Radio (due to the other phone working fine), so could be Internal Storage or Bad Sector.
Im not even close to filling up my internal storage though, so if its storage related, perhaps a particular sector is the problem (like maddie was mentioning).
Thanks for all your opinions!
It's the first time for me to think it's the Radio's problem. It comes to me now it seems this situation starts when I flashed the 1.15.25.14 radio. I will try another radio and update here.
I dont 'think' its Radio, but worth a shot.
I cant consistently reproduce my issue, so it could take me a month to find out if ive fixed the issue.. and there are a lot of variables in a month. But sounds like you have a way of reproducing it consistently, gl.
OK, it doesn't seem to work. I think that's it..
Maybe I should start looking at the bootloader commands..
ive got the same issue, but only with some ROMs, for example, the AZTOR X3 and GEN.Y D2 didnt work, but gen.y 1.4 worked for me.
I tried MTTY method to re-flashing, it seems fine to my diamond right now.
i have the same problem, i have tried about 10 different roms, but i don't think it's software related, i think it might be the phone overheating causing a faulty component, it started 2 days ago for me and usually after 5-10 min it crashes, and it started happening when the weather heated up and it will crash quicker if i try to charge it, anyone notice this?
Has anyone found a solution to this?
For me it started when I installed the Gen Y rom with the android dual booter (but not android itself). I have tried MTTY, Stock ROM but Im still experiencing the problem. I suspect it has something to do with the dual boot.
I get the same thing. soft reset = hard reset.
I have tried several ROMs but now the phone hangs on the loading screen
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