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.
Hi people,
I recently decided to update my touch diamond to wm6.5.
Already got HardSPL 1.93 some time ago together with the swift rom.
Now I downloaded this rom:
BOGYSOFT WM6.5 Build 23060
http://forum.xda-developers.com/showthread.php?t=552162
And followed the instructions carefully, put the rom on the internal storage and started the update process as usual.
After it had finished installing I already noticed it took the phone way to long to completely boot into windows.
After a few reinstalls I finally got it to work but it was very slow and often I couldnt even unlock the damn thing.
At this point I cant even get into windows anymore.
Now ofcourse I want this rom removed from my phone, but is that even possible when I cant boot it into windows??
I need to have an USB connection to put on another rom, so is that possible without windows?
Thanks for your help!
I got the same problem. anybody help us?
I had a problem with an earlier version of this ROM, and the fix turned out to be quite simple.
I flashed my stock ROM back on and then re-flashed BOGYSOFT, ever since then been no problems what so ever.
I had flashed a few different ROM's to try before this it's possible I suppose that there may of been some corruption with repeated flashing.
I think the hardspl is affecting the phone's stability, cause returned back to the stock after flashing some cooked roms and it's bad more than before.....
any news?
mb76 said:
I had a problem with an earlier version of this ROM, and the fix turned out to be quite simple.
I flashed my stock ROM back on and then re-flashed BOGYSOFT, ever since then been no problems what so ever.
I had flashed a few different ROM's to try before this it's possible I suppose that there may of been some corruption with repeated flashing.
Click to expand...
Click to collapse
Yes but dont you need to acces the phones internal storage to add a new rom?
Cause I dont know how to do that when I'm not even able to acces windows.
Anybody?
Is my phone bricked or is there a way to connect to the internal storage without WM?
Now it doesnt even boot the rom anymore,
The image has even dissapeared from my internal storage.
It is now stuck in the Bootloader telling me to trigger the USB host.
Any ideas?
My Diamond has been pretty unreliable over the last couple of days, but I used MTTY to format the internal flash, loaded the latest Gen.Y ROM (I don't think it really matters which ROM tho) and now it works perfectly again. Plus to me it seems a bit faster. Anyway I couldn't be happier.
If you can get into the bootloader with USB I'd certainly give the instructions in this flash a go (post 3 or 4 only if you're on Windows XP).
http://forum.xda-developers.com/showthread.php?t=540290
thanks mate!
So i have been using Custom ROMs for about a year now with no problems. However, recently i flash to the Valkyrie Firestorm 4.4 (i think) leo and when i attempted to restart my fone it would either hang on the sony erricson logo or it would boot up like it does after a flash. As in it would run the customisation and wipe all my contacts and other information, but strangely enough the clock would remain on the correct time.
This has happened with every firestorm i have tried, which are: 4.4 leo, 4.4 manila and the 4.5 leo. I am going to try a different ROM to see if i still get the problem. has anyone had this problem?
I've re-flashed my hard-spl multiple times to no avail.
Yup I've had the same problem with itje's touch it 14 rom. I have no idea why this is happening, it already occured twice with me.
I had the same problem with the valkyrie 4.4 rom, Itje's Toucht-it Leo v10 and Toucht-It Xperience v2, UnOff 6.5. And also with other versions of itje's Touch-it because i remember seeing the HTCpedia.com customization screen a lot
Every time my phone hung and then when i push the reset button it take's a long time and then it is back to first run. or it does nothing and stays at the touch-it start-up screen.
Could it be a hardware failure like something with the backup batery in the phone? when power goes off it doesn't save data and then when you turn it on it thinks it is first run?
I can always tell when it is going to happen if the favourite programs on the programs tab dont work anymore. When I want to start a program from the tab it says "location not found" or something. After that I will likely have a system freeze and after that I have a hard reset, same sympoms as Aerox912.
So maybe it has something to do with the programs tab?
I am having the same issue with Christians 3.201 build.
Also during the installation it will often hang on the install of Opera or Opera Beta.
But I tried re-downloading and reflashing 6 times before I gave up and went back to an older ROM.
Looking forward to the next version so I can try again. I really like the Firestorm but I also really like the Panels.
Now I just need to find out how to install the SPB Mobile Shell 3 as a panel like on Christians and I would probably stay with my SEX1 build.
Using itje's touch it 15 RC2 and it sometimes, for no reason, phone just reboots. It used to happen with version 14 as well. Never used to have that problem before then.
I tried with rotastrains Blaze rom. the latest edition and i am still getting the same issues. I too, can tell when it is going to happen. When the programs can't be run anymore or if the phone freezes and then i need to turn it off, i can almost guarantee that will happen.
Im glad to see im not the only one with the problem, but isn't there anyone with a solution? I've tried everything and i really cant put up with having to wait 15 minutes until my phone is usable everytime it restarts.
Guys, i had this problem with my Diamond recently & i can say that it's more than frustrating.
try this option, I'm not sure if this is the EXACT same process for the Xperia but it did solve my issues. Perhaps scheduling a daily backup of PPCPIMBackup will help keep info up 2 date when the dreaded lockup happens?
hope this helps
flash a stockrom and then the custom rom and the problem should be gone
Why would that help?
I now tried cristians rom, and had the same problem again within one day. I'm now gonna try the MTTY (format) option, see if that helps...
mobilkungen78 said:
flash a stockrom and then the custom rom and the problem should be gone
Click to expand...
Click to collapse
This simple solution seems to work fine for me. Thanks man!
The MTTY solution for formatting the phones ROM area worked just fine for me
Can you point me the mtty formatting method? Please.
I also had this problem once at my x1 and once at my girlfriends diamond. Seems a reflash with a stockrom and after that flash the custom rom again solves this problem.
Atleast it worked for me.
I put on the R3AA014 ROM and am still seeing the problems.
Is there another Stock ROM that would work better?
And I have tried to look up the mtty method and all I find are people talking about it, but not the actual method.
Any help would be appreciated.
Drokare said:
I put on the R3AA014 ROM and am still seeing the problems.
Is there another Stock ROM that would work better?
And I have tried to look up the mtty method and all I find are people talking about it, but not the actual method.
Any help would be appreciated.
Click to expand...
Click to collapse
Maybe it isn't a software problem but a hardware problem. Incase no rom fix it.
toontoonizer said:
The MTTY solution for formatting the phones ROM area worked just fine for me
Click to expand...
Click to collapse
Could you please describe the process.
I tried the The DEFINITIVE MTTY Thread but the task 29 command did nothing... Though i'm not sure what should happen.
For the Xperia, I heard that the command is Task 28 instead of Task 29 for the MTTY process
someguyyy said:
For the Xperia, I heard that the command is Task 28 instead of Task 29 for the MTTY process
Click to expand...
Click to collapse
Hm... i tried that but that did nothing.
happened to me many times..most frequent is my X1 will restart itself every half an hr...very frustrating
SOLUTION:
Format Your SD card (don't be lazy and just delete the old stuff and put new rom file in there).....put a fresh copy of the .nbh file in root.
Hard reset after flash.
Problem should be gone
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
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.