It's done it 3 times now and it's very annoying. Obviously, everything is deleted. Anyone know why this might be and/or how to prevent it? Generally the phone crashes, I have to remove the battery and then it re-installs Windows.
Thanks
at45 said:
It's done it 3 times now and it's very annoying. Obviously, everything is deleted. Anyone know why this might be and/or how to prevent it? Generally the phone crashes, I have to remove the battery and then it re-installs Windows.
Thanks
Click to expand...
Click to collapse
That sounds like a hardware problem!
When my X1 ever crashed, I've never lost anything!
Which rom do you use, how do you do your backups?
I'm using a WinMo 6.5 ROM. Can't find the link at the mo, but it's a ROM designed to replicate an official SEX1 release - no junk or anything included.
I've only had this problem since using this ROM, but my handset was always notorious for screwing up factory resets. A few weeks ago my files slowly became corrupted until such time as the device became unusable.
You're probably using gtrab's R5.07.
I've noticed the reset bug as well. Out of interest, are you using the WinMo alarm feature?
Leddy said:
You're probably using gtrab's R5.07.
I've noticed the reset bug as well. Out of interest, are you using the WinMo alarm feature?
Click to expand...
Click to collapse
Hi Leddy. Yes to both. I re-flashed with a 6.5.3 ROM and am hoping all will be well now.
had the same problem with one of the touch-it ROMs. flashed to a new ROM and it never happened again.
Solution to this problem is to flash a stock rom and after that flash the custom rom back. It fixed my phone one time when I had this and also another diamond was fixed this way with the same problem
Same problem with the SXGU 1.5 Plus ROM. Massive shame. Just lost a load of stuff too!
this problem and any problem cannot be rom related unless everyone using the same rom experiences the same thing... in other words, if you experienced a problem after flashing any rom and others haven't with the same rom, then i suggest to check elsewhere like how u flashed, what u flashed before and so on....
problems after flashing are mostly solved by flashing a stock rom, task29 and flash via RUU and not SD method
not true.
this can and can not happen on the same rom.
there are two possibilities:
- it's rom related and many, but not all are getting it - change rom-version.
- something's messed up which task29 will NOT fix - flash stockrom
i had the second one and it took me some time to figure out that task29 didn't fix it. stockrom performs task28, if i'm not mistaken.
it's definitely NOT hardware related!
dude, if the problem lies within the rom, which means everyone using the same rom should experience the same very problem... if not then its either hardware related or files remained on the device from previous flashes that caused conflicts with the current rom
check this
Intratech said:
Never had this problem and I've been running Xperia X1.5 Home Plus since it's release. I suggest flash back to generic R3A ROM, task29 and then flash to whichever ROM you chose to run.
Click to expand...
Click to collapse
i can either be hardware or conflicts with previous files, but definitely not a rom issue since others have no problems...
and this goes for any rom its common sense to understand that
i remembered i had a perfect device few weeks ago, i flashed a rom and tested some stuff, didnt like it so i went back to the rom that was perfect, unfortunately, my device had tons of SOD and resets, i was pissed and had to use a rom i hated, but then i remembered someone sayign something about flashing stock rom again, so said so done, i task29 then reflashed that perfect rom, right now im still using it with no issues whatsoever
dude, you're not talking to a total n00b here... so maybe you could change your tone a bit?!
if your logic was to be true, everyone on the same rom would get SoD if the rom has it - but... and the same goes for this hardreset-thingy - it's not "either everyone gets it or noone", it's an individual bug. but some roms seem to be more prone to have it than others.
sometime this year (about february?) you'd see reports of this in almost every rom-thread. it's rather rare now... (assisted, but not only caused by task29)
and again: it's nothing to do with faulty hardware - or it would be uncurable.
dude.
edit:
and that "someone saying to flash stockrom..."? that could (!) have been me, as i left a note on that some time ago in task29-thread. (i said "could"!!!)
caliban2 said:
dude, you're not talking to a total n00b here... so maybe you could change your tone a bit?!
if your logic was to be true, everyone on the same rom would get SoD if the rom has it - but... and the same goes for this hardreset-thingy - it's not "either everyone gets it or noone", it's an individual bug. but some roms seem to be more prone to have it than others.
sometime this year (about february?) you'd see reports of this in almost every rom-thread. it's rather rare now... (assisted, but not only caused by task29)
and again: it's nothing to do with faulty hardware - or it would be uncurable.
dude.
edit:
and that "someone saying to flash stockrom..."? that could (!) have been me, as i left a note on that some time ago in task29-thread. (i said "could"!!!)
Click to expand...
Click to collapse
lol i dont think u understood me, as i said, it is not rom related...
if a problem was caused because of a fault in the rom, everyone using the rom would experience the same problem, its not logic, its common sense...
why do we task29? to remove files from previous roms right? which means that it has nothing to do with the rom... chances are it could be hardware related too, note i said chances... for who dont know, windows 7 isthe first OS from M$ that can actually wipe a partition clean, leaving no trace of anything behind that no forensic kit can detect... however we task29 our devices to remove these files that remain and cause conflicts with newely installed roms
if i delete solitaire.exe from the sys, cook a rom, no one would get solitaire to play by default, why? because its a default rom issue caused on my part so no one will get it to work just like that
sometimes before we think about criticizing something we use, we first should ask if anyone is having the same problem, if all does who used the same product, then the problem is the product itself, you dont have to be a noobie/senior to figure that out... its plain common sense
btw, sometimes i personally have 2 xperias here with me flashing, wanna know the weird thing? my own device causes problems when flashing roms at times, my friend's xperia flashes with no problems, no SODS nothing...
as i keep saying, its only rom related if everyone using the same rom gets the issue
rofl, stubborn he is...
okay, it's not rom-related as in "the rom is faulty". but just because noone else gets it with a certain rom doesn't mean it's not related to the rom at all. as i said, there was a time when many roms were affected (but never all users!), it was probably build-related (234xx - something around that).
it's not hardware. that's for sure.
but there are individual circumstances (something messed up in bootloader - well no, not bootloader, but in that area, you get me) which can cause this. most of the time these are cured with task29, but not always - then you need (!) stockrom.
so let's settle on this, shall we?
whoever experiences this, try task29. if it doesn't help, flash stockrom and try custom-rom again.
about your solitair.exe:
if it was always that simple, bugfixing would be very easy because everyone would expirience the same bugs. (if caused by rom) well, it isn't that way, we all know that.
read this, i've been the only one with this bug on that particular rom-version. and i've tried a lot of things. i even got itje to make a test-rom with his old kitchen because of this... (guess his reaction when i told him what cured it, hehe... )
lol dude, i know what u are trying to say, but to say because not everyone using the roms gets the problem doesnt mean its not rom related just doesnt make any sense, if its rom related then everyone using the rom should experience it, how can a product have a defect with only some people and not others when everyone is using the same exact product??? ever thought of the fact that it might be something else causing the problem outside the rom by forcing such issues to occur?
dont think my device never had issues, i did, but never once i re-developed a rom because of an issue... reflashing stock and task29 after fixed all my issues of instability... that rom i told you about that was perfect, you think i re-cooked it because my device was unstable? no, because i know that my device was perfect before so it was not the rom, but it was my hardware not functioning as it should when flashing, meaning the system was never clean of previous files, so conflicts occur... remember that poster who flashed a rom and the bootscreen from the previous was still on the device after flashing a new rom???? thats what im talking about
... but i do agree that it has something to do with the bootloader...
do you know that some of us have never seen the headphone icon on any stock rom via SEUS, some people seen it some havent, the only time i see the icon is when i flash a custom rom, but i have never seen it on any stock rom since i bought my x1 brand new from sony...
its either
My experience would lead me to disagree with both of you. If I flash back to my previous ROM, everything's fine; if I install Gtrab's or Spike's I get this damn bug, but it's different on each. With Gtrab's the phone formats itself; with Spikes' the phone boots into a black illuminated screen after a crash and requires re-flashing, or all data wiping.
It would be great if I could get back today's data though before flashing a stock ROM. Anyone know how I might?
Edit: It booted once when I connected the USB and took out the microSD, (I got my data!) but now it hangs on the SE boot logo. IE, ROM erased. I'll give the ROM one more shot since it really is brilliant other than this bug and an issue with the keyboard.
at45 said:
My experience would lead me to disagree with both of you. If I flash back to my previous ROM, everything's fine; if I install Gtrab's or Spike's I get this damn bug, but it's different on each. With Gtrab's the phone formats itself; with Spikes' the phone boots into a black illuminated screen after a crash and requires re-flashing, or all data wiping.
I'll try the stock ROM idea, but I haven't been able to find one. It would be great if I could get back today's data though before doing that. Anyone know how I might?
Edit: Oh, it boots if I 1) connect the USB and 2) take out the microSD card. Yay!
Click to expand...
Click to collapse
dude, if you havent tried to flash the stock rom you cannot say u disagree with us, try it first and see...
so many people are currently using x1.5 home plus, check the rom thread and see for yourself, no one else is having your issue... flash the stock rom, there is a thread with the stock rom on the rom forum... then report back to us.... btw, i too am using x1.5 home plus as from today and i reinstalled all my apps
Related
Some days ago, i've flashed my phone to get an "up-to-date" ROM. I chose "PDACornerIllusion 21139" of 2009.03.06. All went fine excepting the keyboard of my GPS wont work anymore (dunno why of course), so i re-flashed with another ROM.
I was surprised that my phone kept the CornerIllusion BootScreen, but i didnt care.
All of a sudden, after having soft reset the ROM i chose (the 2nd one), for an installation of some proggie. The ROM restart as brand new asking me to reset the screen, the clock, date etc... losing all my content and customizations. Then i couldnt sync with Outlook after the first sync i've done minutes ago (error code 800004005). I've decided to soft-reset the phone, and now, TF3D wont even start, (it selft tries to start several times, then gives up), AND the programs lists is all broken, no shortcuts left and the games folder is named *h1/4Eg+รง^, nothing works anymore.
I flashed with about 4 roms (including Aztor one), resulting in the same mess.
Does it have something to do with the first one "PDACornerIllusion 21139" and its still remaining BootScreen?
Can i flash my phone from its roots, to get rid of this ?
As it's maybe not the "fault" of PDACornerIllusion, i write this in this section of the Diamond general thread and made a double post at PDACornerIllusion development thread
I suggest you perform a hard reset before flashing any new rom and that you use the traditional "flash-from-PC-using-ActiveSync-connection" method to flash.
And above all I wish you luck!
What was the other ROM you flashed? I am curious.
rondol1 suggests you hard reset prior to flashing a new rom. I suggest you hard reset after flashing a new rom. Net result is probaby much the same. You could even just do a hard reset now with whatever is loaded and things will probably improve. Main thing is...whenever you flash a rom do a hard reset straight after loading it. I always do this religiously and with the exception of one recent rom I tried I have never had a problem.
First of all, thank you both for trying to suggest hints, i really appreciate it.
I've never hard reset the ROM before or after having installed a new one. I never have a problem before.
For the last 2 months, i was on NEON 1.28, then i've decided it was time to update seeing the new features of the more up-to-date ROMs
I've just reflashed it (an hour ago) with PDACornerIllusion 21139, i've hard reseted before and after. let's see how it turns out ....
I've tried NATALY, CLOUDY, MORNA & AZTOR, no luck with any of them, all died after a soft reset or after the 1st sync (reconnecting for a 2nd sync).
Maybe the problem comes from the very root of the phone (like BIOS in a PC, dunno), maybe something in there got corrupted. How to repair it if my guess exists and is it repairable?
dunnno said:
I've never hard reset the ROM before or after having installed a new one.
Click to expand...
Click to collapse
There in lies the problem.
I bet you will be fine from now on. Don't ask why you need to do the hard reset - as no one has been able to give a definitive answer - But it is a well known step that many chefs recommend post flash - just do it from now on and you wont regret it.
logger said:
There in lies the problem.
I bet you will be fine from now on. Don't ask why you need to do the hard reset - as no one has been able to give a definitive answer - But it is a well known step that many chefs recommend post flash - just do it from now on and you wont regret it.
Click to expand...
Click to collapse
completely agree with logger - hard reset after you flash any ROM. I haven't used PDACorner - so can't say for sure... but do the flash via CustomRUU once... when the new ROM is flashed... do a hard reset as soon as it's complete..
good luck!
let's see then, >>>>crossing fingers<<<<
I've had this happen a lot lately as well. Might have something to do with the newer SYS? Anyway, hard reseting hasn't always fixed it for me. However, flashing back to the Sprint stock ROM (or HTC stock for you GSM guys) then flashing a new custom ROM has always done the trick. Maybe because the stock ROMs are bigger and "clean" out the memory somehow? At any rate, flash stock and then you're good to go. No permanent damage.
no luck, after a 2nd soft-reset, the phone is asking "touch the screen to configure for the 1sy use blablabla", all data's lost again & again...
what do you mean by stock Rom ? the rom that came with my phone when i've bought it ?
I've got the same problem with the Diamond rebooting like a hard-reset. But I always did a hard-reset after a fresh install. I blamed it on the rom and tried several others, including donsalari's "Clean Basic Rom", the Gen.Y Sense 2.1 and 2.5 versions and an older Aztor rom. Same problem every time, the first reboot after changing the device locale works fine, then I set the whole phone up properly and on the next reboot it will come up as if had performed a hard reset.
Additionally, the file system on my internal storage got corrupted somehow, had to reformat. At some point, I also had the impression that data on the phone memory got lost gradually. First the Contact's numbers got replaced by some nonsense characters, then there were numbers and contacts missing, and finally I had no contacts at all. ActiveSync stopped working so I was in the middle of a trip without my phonebook...
I've got two hypotheses:
1) The Gen.Y bootloader messed with the phone (Had tried the Sense 2.5 Gen.Y rom before donsalari's)
2) Flash controller or Flash itself is broken
@dunnno: I suggest you rename the thread to something like "diamond hard-resets on 2nd reboot after rom install"
edit: oops, just realised I resurrected a very old thread... Maybe there's a fix already?
My diamond still suffers from this problem. I tried it again and again with different roms but everytime, at some point all my configuration is lost and the diamond reboots like after a fresh install. Can anyone please help?
I'm having this problem as well :|
Grr, I have to rely on my phone for so much, but it just doesn't want to work correctly.
Help is immensely appreciated.
Well, I got mine to work, I just flashed the stock HTC ROM and everything has gone back to normal. H3PO, I suggest you give that a shot if you are still having problems.
I had these problems when I first started flashing my Diamond with custom roms.
Now I always flash my carrier stock rom first, then hard reset, then flash custom rom, then hard reset and I never have any problems. I have no idea why flashing the stock rom first stops the problems but I haven't had any problems with the dozens of roms I've flashed using this method.
Also I always flash from internal storage, but others prefer using MTTY
I still have some problems with the Contact Database, but flashing some stock O2 Rom solved the "reboot as new" problem.
I had the first HardReset with FS v3.4 LEO-HORIZON, yesterday, then the second with FireStorm v3.4 Rhodium\TOPAZ, today.
Nobody gives any support in the chef's thread so I'm reaching out to you all.
The possibility to have a faulty harddisk is starting to make me -->
It happened out of the blue, after a normal softreset....
UPDATE: Stable on NRG ROM!
Code:
[QUOTE="Ersill, post: 4519631, member: 357935"]What the...?? Some program didn't launch so I check the root and there were only "Storage Card" and "Windows" folder along with plenty of " . " folders. I pressed the power bottom to shutdown and reboot and the welcome screen came up!
Unexpected HARD-Reset? :(
What did I do wrong?[/QUOTE]
Nobody knows? I'm afraid it could happen again! :(
Uhm, flash to something more stable...
I had the same problem with both Itje's and Firestorm's ROMs. It happened 4 times in 2 days with Itje's, and 6 times in a 2 week period. I noticed it when I went into flight mode and also when I switched off - on both occasions I was catching a plane (or was just getting off one.)
Hard reset, reflashing and still had problems. Solved by flashing to Energy's ROM which has so far been stable even after switching to flight mode.
odd...but agents roms are all stable for me...i flash and then hard reset and its goin strong so far...never had probelms with Itjes roms either(minus the connection setup constantly being an annoyance)
Or you can always use the OEM ROMs and see if that still produce the same results.
you can use vlite cobalt hardcore.very stable and fast.cheers
Sfkn2 said:
Or you can always use the OEM ROMs and see if that still produce the same results.
Click to expand...
Click to collapse
the problem is: flashing so many Rom's you have bits and pieces from one and bits and pieces from others because the flah process doesn't completly erase all the data that you don't need in the new Rom. it's not agent's or itje's fault. the solution for me was flashing a stock rom and after that flashing the custom rom that i want. you don't need to reflah stock spl. for 4 days i didn't have any hard resets. i will post again in a couple of days if the problem reappears. if not it means that everything is back to normal. i now that it takes more time but my advice is to flash a stock rom first everytime before flashing a custom rom. and don't forget to hard reset just after flahing. hope this solves your problems also as it did with me
i have never encouter any of these in either itje's or agent's roms...
u might wanna try reformat your sd card again and then flashing through your card
I've never got this problem
Me neither; especially not with the ROMs you mention...
i had this problem happen to me on agent's leo.. but with FS, it's as stable as ever!
Hard Reset might be able to solve some problems. It did for me. Hopefully for you
THANK you all guys! I was lost and scared but now I'm happy again
I'll try the "OEM ROM first" method and I'll give you updates.
I'm running the latest NRG rom. I hope for the best.
See ya!
had this problem too... I flashed to stock ROM and stock SPL (don't know if last is necessary). My x1 is in repair now (keyboard), after that I'll flash back to hardSPL/custom roms (or maybe I'll sell my x1)
pisulinu said:
the problem is: flashing so many Rom's you have bits and pieces from one and bits and pieces from others because the flah process doesn't completly erase all the data that you don't need in the new Rom. it's not agent's or itje's fault. the solution for me was flashing a stock rom and after that flashing the custom rom that i want. you don't need to reflah stock spl. for 4 days i didn't have any hard resets. i will post again in a couple of days if the problem reappears. if not it means that everything is back to normal. i now that it takes more time but my advice is to flash a stock rom first everytime before flashing a custom rom. and don't forget to hard reset just after flahing. hope this solves your problems also as it did with me
Click to expand...
Click to collapse
So i hardreset after i've flashed a custom rom, but do i also need to hardreset after an oem rom flash? thx
I have never encountered any sponaneuos hardresets. It's pretty odd. Have been using almost everyone of agents roms.
Maybe you accidentally pressed the hardreset button. Twice.
I've just started getting these issues with the latest Firestorm ROMS. Glad it's not just my phone... I'll try flashing OEM first before as suggested and see if that fixes the problem. Going from a fully functioning phone to a hard-reset one whilst at work is not too great an experience! At the moment I've completely lost all faith with my X1 :-(
I had exactly the same problem. I flashed many roms but still had this problem after I flashed to new roms. To solve it I flashed back to a stock rom (And stock SPL fyi) and I used it for about two weeks to test if it was the rom. The problem never happened again and now Im happy again on Agents FS 3.4
Hi,
My experience today is the motive of me writing this guide to help most of you out of this problem and eliminate the Fear that you will have of you blackstone might gone bad (hardware fault).
ok,
here is what happend to me today.
I had XannyTech Rom flashed on my phone and i really felt i found something interesting about another ROM so i decided to flash that one.
after a smooth flashing, the phone booted and i started syncing using myphone.
left the phone on the desk for a while, came back and found that the device is not responding to the power button, poked that red button and the phone get's stuck at the "smart mobility" screen!!
Hard resetted the phone and started over, again the phone hanged.
i thought that it's maybe a bad flash! so i downloaded the file again and flashed again.
still the same!!!!
decided to go to the old ROM ,
still after a while i get the same result!
notice that i hard resetted after each and every flash!
so what did i do?
[Guide]
Hard Reset the phone, check if it's a software you installed or if it happens even on a pure ROM.
If the problem still exist, Confirm it's not a bad flash! flash again the same ROM.
If you still have the same symtoms, go to HTC website and download the latest OFFICIAL ROM from there.
Run the RUU from your pc (Don't worry about HSPL, it's protected so you will NOT have to HSPL your device again, Thanks olinex)
Test your phone with the new official ROM (in my case -blackstone- it's a 6.1 rom ). Mostly everything will be back to normal.
flash the rom of your choice.
I don't have a real explaination about this (maybe someone with more experience can do) but it works! and even the ROM works faster .
Hope you find this usefull.
Regards,
Adel
I will remember this if it happens to me!
Thank you!
For me, with the HSPL, when I went back to original rom, I had a big problem with color. I flashed to old SPL too, and so, color where good after
Wiki
Not a huge problem, it's well documented
Understanding 1.56 Roms (Greenscreen issue & Flashing)
edit : oops, the link is accessable from the wiki
re the topic:
Looks like Viagra cant fix this issue then
anaadoul said:
Not a huge problem, it's well documented
Understanding 1.56 Roms (Greenscreen issue & Flashing)
Click to expand...
Click to collapse
Hi
You should fix your link and put wiki instead if forum
Jal84 said:
Hi
You should fix your link and put wiki instead if forum
Click to expand...
Click to collapse
it is good to see that you have followed the link
anaadoul said:
I don't have a real explaination about this (maybe someone with more experience can do) but it works! and even the ROM works faster .
Click to expand...
Click to collapse
Well, I am not sure, but it seems that Official ROMs not only flash your phone, but also "format" it.
You may want to have a look at this post (http://forum.xda-developers.com/showthread.php?t=540290) for more references, but the fact is that "flashing" means issuing some commands to the phone. These commands are all about uploading the ROM data in the appropriate section of the NVRAM/EEPROM (I am not an expert, but I think I am more or less near to reality with such a description).
In the Official ROM's case, more commands are issued and some of these commands "clean" completely your phone, making route for a clean installation and a good one.
I don't know (I am not a cooker, nor an expert) why cookers can't or won't issue those commands in their ROMs, but soon after flashing an official one, you have a "clean" phone that is not affected by random behaviour, due properly to the commands that only official one's issues during the flash.
Hope this may help
Regards
Ehol
Ehol said:
Well, I am not sure, but it seems that Official ROMs not only flash your phone, but also "format" it.
You may want to have a look at this post (http://forum.xda-developers.com/showthread.php?t=540290) for more references, but the fact is that "flashing" means issuing some commands to the phone. These commands are all about uploading the ROM data in the appropriate section of the NVRAM/EEPROM (I am not an expert, but I think I am more or less near to reality with such a description).
In the Official ROM's case, more commands are issued and some of these commands "clean" completely your phone, making route for a clean installation and a good one.
I don't know (I am not a cooker, nor an expert) why cookers can't or won't issue those commands in their ROMs, but soon after flashing an official one, you have a "clean" phone that is not affected by random behaviour, due properly to the commands that only official one's issues during the flash.
Hope this may help
Regards
Ehol
Click to expand...
Click to collapse
Good explaination!
also while i was extracting a shiped ROM i got an unknown nb file which might be responsible for this?
what you have said means that as long as you are flashing a larger sized ROM you should have no problem, but once the new ROM have a smaller size then you will face some issues?!
oh, one more thing.
after formating the phone with the stock ROM, i noticed that it runs much faster (around 15% performance increase) can anyone try flashing shipped ROM then the same one he was using and confirm this?
Anyone experienced issues with christians latest rom 5.120. Ive installed the full build however im running into problems.
hxxp://www.christian-web.nl/sections.php?section=Xperia_rom
Here goes, rom seems to install fine, however, when i come to install applications the system may pause and sometimes crash. At first i thought it was a currupt download so i tried again, ive installed only codewallet pro and spb finance 2.8. Eventually the system will lockup, and this will require a reboot with the sylus. When the system comes to restart it freezes at the 'XPERIA' logo screen, and doesnt get as far as the os. Ive tried flashing a number of times and even used task 29 to format internal memory to know success. Am i doing something wrong, ive used cooked roms before and have the correct spl, im not sure they would need reflashing now ? The previous rom which i cannot remember the version of worked fine, so i refuse to say its a hardware problem.
rom specific questions should be asked in the respective rom thread and this seems to be such a case
it's much more probable that the answer is already there or that someone of the regular users has had similar experiences (and can maybe even provide a solution) than opening a new thread in general section
gl
Alright people, I consider myself pretty smart when it comes to the world of WinMo, but this is a problem that I just cannot nail down. I have been using the OLD STAXXXSTYLE WM6.5.1 ROM for as long as I've had my Kaiser, and decided to upgrade to his last stable version, well I did and everything seemed fine. After 3-4 hours of using my phone, it went all unresponsive on me...no big deal so I soft-reset it.
Well, it took FOREVER at the initial bootscreen, then eventually continued on and went back to being all-"Oh hai, set me up plox!", like I had hard-reset it. So I chalked it up to weirdness and continued through and re-set it up and such.
Well, long story short, this has happened 2 or 3 more times since then. I just cannot figure out why it keeps doing this. I thought it was my HardSPL since I have read that this can happen with older versions, so I flashed upto 3.34DAVESHAW, and it still continues. I am running radio 1.71.09.01 and have never had any problems with this Kaiser up until now. ANY help is GREATLY appreciated. Thanks.
seems like bad rom. hard reset usually comes if there are unrepairable memory problems. I had this while using certain kitchen, after I changed to different kitchen and did the same mix of rom, all was good.
Before, when I extracted 20MB zip, some of the files always went wrong and hard reset followed.
in the FIRST post of staxxtanium ROM thread, the fourth line reads:
Unless you have Issues, Stock wont be necessary, Well I personally don't have issues but to be on safe side, flash stock first. Those previously on Ultimate X2.V11 its a MUST that you flash Stock first-
Click to expand...
Click to collapse
the chefs of nearly all WM6.5(.x) ROMs advise flashing stock ROM before flashing a WM6.5(.x) ROM (even if you already have a 6.5(.x) ROM). some chefs are more clear about the reason, i.e. most chefs will clearly state that this step will avoid unexpected hard resets later on. it seems staxxthedan did not feel it necessary to state the exact reason for his quote above. still, you are having an issue and this is the first suggestion staxxthedan gives for any "issues".
also, further searching would have revealed this solution.
um, what happens with another rom?
Wow, way to be an asshole ASCIIker. I have ALWAYS reflashed to stock before flashing to something else. And yes, it happens with ANY ROM from ANY cook that I have tried in the past few days.
well then you should clarify in your opening post with all pertinent information especially your flash procedure so that the obvious (to you and me) can be ruled out first hand.
not trying to be an asshole, i did try to help, given the limited information you provided. but the information was just that..."limited"!
hello mate
i have the same problem you posted here
my mobile is HTC TyTn II
i've tried many radio versions hardSPLs roms
and i cannot find any solution
my question is : did u found any solution since it's an old post? i hope yes
Auto Hard reset
hello mate
i have the same problem you posted here and my mobile is HTC TyTn II
i've tried many radio versions hardSPLs roms and i also cannot find any solution
Do u found any solution since it's an old post? i hope yes. I used Shifu and Gangster wm6.5
I tried with different Radios and Harspls but no lukc.
Your prompt action is highly apprecaited.