Related
Hello Guys,
I am thinking about Flashing back to my original ROM that came with my Xperia. I tried other ROMs, primarily Itje's, and they are just brilliant, but I am not sure how they be used as everyday ROMs. The Touch-IT 4.5 has the battery leakage issue, some SMS issue, and I really don't like the new Start Menu thing with TouchFlo. Even though they have a fix with for the Start Menu thing, you lose the Programs tab, since the new TouchFlo is not meant to be like that. I understand that there must be more solutions for that ROM, but I will be honest, even after reading as much as possible AND searching, it's just so impossible to go through those 100s of pages.
I also tried the WM 6.5 Beta ROM. Again, excellent work on Itje's part, but I just don't think I am ready for WM 6.5 yet. It's just not stable and that is understandable since it's BETA.
Anyway, with that said, since I am not very experienced with Flashing, I had a question. What happens to a phone if the ROM image (Kovsimg.nbh) that is chosen to Flash the phone with, from an SD Card, is corrupt? Does the phone get stuck in the middle of everything, and the phone ends up as a brick, or are there any ways to prevent this from happening?
I am just asking this because I am not certain... the ROM I backed up COULD be corrupt, I mean I don't know. There were no errors when I backed it up, and followed the tutorial with no problems.
Any help is appreciated, thank you very much guys!
I just got out of that situation. Tried flashing by micro sd way. Took out batt and micro sd, then used the USB flashing tool to flash a new rom.
Thanks for your response, dadeadman, but after reading your reply, I am a bit more confused (Sorry). Please correct me if I am wrong, but are you saying that you tried Flashing with the SD, it was unsuccessful (for whatever reason), you then took out your battery and the SD Card, and Flashed it through USB using the RUU Flashing tool? If this is correct, then can you explain how the phone even connects to the computer with an OS (ROM) on it? I would assume that if the flashing process gets corrupt, the phone ends up with no bootable OS, right?
Sorry for the confusion, I hope it made sense .
You have to put it in bootloader mode then connect the usb. The white bottom portion of the bootloader screen will say USB, though the mobile device cnetre/activesync cannot detect. However you are still able to flash a working rom with the RUU Flashing tool.
dadeadman said:
I just got out of that situation. Tried flashing by micro sd way. Took out batt and micro sd, then used the USB flashing tool to flash a new rom.
Click to expand...
Click to collapse
Nice, thanks a lot for your reply man, that makes me feel much better !
I'm sorry for this post, because the answer is probelly somewhere on this forum. But I can't find it.
I have my diamond for about a year now and I like to install a custom rom with windows mobile 6.5. But I can't seem to figure out what I need for this.
I already chosen a rom, but I have no idea if it is any good, because there are so many roms out.
http://forum.xda-developers.com/showthread.php?t=563245
So my first question, is this rom any good?
Second question, what type of hard SPL do I need, Do I need the normal one that requires roms to be signed or do I need the developers edition?
Third question. Do I need MTTY for this or can I first try it without MTTY?
And the last question, if I don´t like the rom is it easy to install the original rom again or do I need to do something special for that.
I hope you guys can answer my questions so I can start flashing my rom.
Grtz, Eric
EDIT: I tried installing hard-SPL unsigned, but get an error that it can't connected to my phone. But it is connected using windows mobile device center
why do you want to flash a new rom?
ive recenetly done the same, i wanted to flash my rom as the original was tied to vodafone and some of the features like youtube, facebook, and opera wouldnt work as they wanted vodafone connection ( im on virgin mobile).
anyway after much trial and error i in the end found it versy easy.
3 simple steps. first flash your bootloader
i found the best and easiest one was spl olinex version 4.0
u need to softboot to do this ( hold the down volume and switch on phone, have usb cable connected then use the flash util provided with the above.
once thats done you need to flash rom the radio
again the one out there that seems the best to use is version 1.00.25.05 diamondruu radio
again soft reset so you get the try colour screen and run the flash rom update ( takes about 2 mins at most)
finally choose your version of win mobile 6.5 ( i got windows revoluton 7.1 ultra clean edition)
do soft reset again, then run the flash update and again this takes about 5-10 mins for this)
all worked perfectly for me and it was my first try.
though i will be changing it as the revolution is missing some vital aspects i like.
i know its basic but hopeully you can see its not the daunting prospect some people make out though any rom upgrade carries a minot risk i found this to be as easy as 1,2,3
good luck
cloudedhopes said:
why do you want to flash a new rom?
Click to expand...
Click to collapse
Because I would like some new features on my phone. Like wm 6.5 or a new version of manilla. It's getting a little boring having the same phone for over a year.
@miramele, thanks for your response. I'll give it a try tomorrow and hope I won't brick my phone.
let us know how you get on, it took me several attempts as each time i was trying while within the phone itself, if you hold the down volume key and power on the phone you get the tri colour screen, in this mode i had 100% success each time.
doing it within the OS with phone on it just stuck at 0%.
And since then i have re flashed it with a diff version of wm 6.5 that i prefer and all is good.
the version i flashed to is the manila 2.1 with the latest touchFLO 3d so ive not even bothered with Spb mobile shell though may add this later.
miramele said:
let us know how you get on, it took me several attempts as each time i was trying while within the phone itself, if you hold the down volume key and power on the phone you get the tri colour screen, in this mode i had 100% success each time.
doing it within the OS with phone on it just stuck at 0%.
And since then i have re flashed it with a diff version of wm 6.5 that i prefer and all is good.
the version i flashed to is the manila 2.1 with the latest touchFLO 3d so ive not even bothered with Spb mobile shell though may add this later.
Click to expand...
Click to collapse
Thanks for the advice, if I understand correctly I have to get to the tri-color screen and then install hard-spl? But can I connect to my laptop while in this mode?
I'm gone try it tomorrow because I didn't have any time today.
Thanks for all the help, especially miramele.
I made the step and am now running a custom rom without any issues. Many thanks for the help and for pulling me over the line.
Hello,
I know you guys got some excellent walkthroughs, roms, programs and threads where you've helped a lot of people out but I could really use some personal feedback. I had hoped to fix my phone using one of the excisting threads but unfortunalty I can't get it to work with those.
My problem is one I've seen more of in here, I used the SE updater and it froze at 53%, I did what the program said, reconnected and it froze again at 12%, and again, again, etc. So I disconnected thinking it might be a bad USB port. But then the updater didn't recognise my phone at all. So I used the mtty program suggested in some of the threads and I got past the red/green/blue screen but now it's stuck at the Sony Ericson logo, as if WM6.1 is gone.
This is what the red/green/blue screen currently states:
KOV110
SPL-0.78.0000
MicroP1-787
MicroP2-707
From what I gather this means I can't flash roms, right? I tried making it a hard-spl but when I use the tool it says it can't connect.
So is there anyway to get a rom on it and bring it back to life?
Thanks inadvance!
Get an original rom from here : http://forum.xda-developers.com/showthread.php?t=475482
copy .nbh file from the package onto your sd card and rename it to : Kovsimg.nbh then bring phone into boot loader via : vol down + power.
It should flash the rom now. i the problem is still present after that you
have to deal with mTTy but first try the flash...
i think you could also bring phone into bootloader without sd card inserted then connect usb cable, display should now print 'USB',and after that start rom update utility.
regards
meska said:
Get an original rom from here : http://forum.xda-developers.com/showthread.php?t=475482
copy .nbh file from the package onto your sd card and rename it to : Kovsimg.nbh then bring phone into boot loader via : vol down + power.
It should flash the rom now. i the problem is still present after that you
have to deal with mTTy but first try the flash...
i think you could also bring phone into bootloader without sd card inserted then connect usb cable, display should now print 'USB',and after that start rom update utility.
regards
Click to expand...
Click to collapse
Thank you for your reply, I will do as you said although I've already tried something similiar to this. I believe the problem was that I couldn't flash roms from my SD since I don't have the hard SLD. But I will try it anyway as soon as I get home.
In the mean time I would love to hear more ideas about how to fix my phone.
Ronnet said:
Thank you for your reply, I will do as you said although I've already tried something similiar to this. I believe the problem was that I couldn't flash roms from my SD since I don't have the hard SLD. But I will try it anyway as soon as I get home.
In the mean time I would love to hear more ideas about how to fix my phone.
Click to expand...
Click to collapse
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.
original roms will still work with original spl... but nevermind =P
laurence0609 said:
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.
Click to expand...
Click to collapse
My phone can still power on in the sense that it shows the Sony Ericson logo or that I can access the three collor screen. But it won't launch WM6.1. I also have a problem with updating to hard DSL. It does recognise my phone because without it connected the program finds nothing and with the phone connected it wants to start updating. It says ''updating from image version: (emply) to image version: 1.00.X1 Ipress next and it opens a progress bar on both my X1 and the PC. But it never goes beyond 0% and then gives me an connection error. I think it has something to do with not being able to get passed the Sony Ericson logo. I mean the hard-DSL program does recognise my mobile but activeSync is never active because my PC doesn't recognise a WinMobile phone (since it wont go past the Sony Ericson screen)
meska said:
original roms will still work with original spl... but nevermind =P
Click to expand...
Click to collapse
Really? That might fix my device then. Could you suggest a rom from the long list? Perhaps one that works on all versions? Because I'm dutch but my mobile has always been in english so I'm not sure what rom version I had. Except that it was identified as an R2 Rom by the Sony updater before it killed my X1...
Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that
Mopral said:
Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that
Click to expand...
Click to collapse
I'm now downloading the initial dutch R1 firmwire, could that one work?
Mopral said:
Go here
Find the latest stock rom for your country (and perhaps your carrier) and flash it
No need to have Hard SPL for that
Click to expand...
Click to collapse
Alright so I got an R1 original rom (I now realize that the R3's were originals aswell) and it worked! I'm not sure if it was the different rom or the formatting with FAT32 that did but it works again. So I'd like to thank everyone who was kind enough to reply.
The device is incredibly slow now but now I can use the hard-DSL installer, right? DOes anyone have a suggestion for a good rom to use?
laurence0609 said:
You really need have to flash the HardSPL first as, based in your above post, you still have not done that. It will be useless to flash cooked ROM with that. If you can still power on your phone and you have an activesynch in your computer, i suggest you download the HardSPL first and update your phone using your PC. If you are successful doing that, then you can flash all you want.
Click to expand...
Click to collapse
DON'T hard-spl if you're going to flash a stock ROM. And especially if you're going to use SEUS.
Try flashing the R3A first. The R1s are way slow, as you've seen.
There's a lot of beautiful ROMS for our device but most of the new ones face one problem SOD (Sleep of Death) when the device goes to sleep you can't wake it up.
What "causes" SOD?:
* Bad Flashes
* Residual code for flashing you device a lot
* Newer SYS cooked in ROM
I've been searching for a solution and this is what I've found.
qbus00 said:
That's something which I have to do...
I'll downgrade SYS to 21896 soon which does not face SOD problem.
Click to expand...
Click to collapse
wuub said:
MTTY is a software that allows you to format internal storage before you flash a new rom.
By doing this you will make sure that no residual files or past informations are kept in the system. This usually fixes random crashes and weird behaviours on PDAs.
This is the DIAM100 thread but i've been using on D2 without trouble : http://forum.xda-developers.com/showthread.php?t=540290
Click to expand...
Click to collapse
From HD2 ROM Thread
rjd1 said:
I started having issues similar to this and a few other non-normal issues with NRG ROM. I ended up loading carrier ROM again, re-flashing 2.08 radio and then 23544 COokie ROM and all cleared up. It appears alot of risidual code happens with the HD2 ROMS regardless of AS or SD card ROM loading. I added to my flashing every 2 weeks or so - I am a flashaholic...
Click to expand...
Click to collapse
doloop said:
Hi,
(To make it short, follow the red sentence to format your phone to avoid roms problem.)
I hex-edited RomUpdateUtility.exe so it runs task 29 right after flashing ruu_signed.nbh
Task 29 formats your phone memory (=binfs). It prevents weird error appearance when you flash new Roms.
you stile need something to flash, it may be a radio, a splashscreen nbh or a blank nbh file (shadrack repack provide a tiny blank nbh).
Usually you don't need anything more than the file provided in the packs. so:
Just unzip and run task29.exe .
Eventually, you may replace ruu_signed.nbh with the radio/splashscreen of your choice.
When update status reach 99%, press vol down button, and keep it pressed until the phone reboot to the three color bootloader.
After the phone reset itself, your old rom will be gone, so it can't boot to winmo: binfs has been formated, your phone memory is clean.
if you fail to press vol down key and your phone get stuck on the white screen, just remove your battery, then try again: press power, and keep vol down pressed immediatly next, until the phone get to RVB bootloader.
When your phone is back to RVB bootloader screen, use the leocustomruu.exe provided with your favorite rom package to flash a new rom, or flash it from memory card using standard procedure.
Repack by ShaDrac (Recommended):
http://forum.xda-developers.com/showpost.php?p=5848003&postcount=19
No radio needed, smaller, faster.
Video tutorial by [★]
http://forum.xda-developers.com/showthread.php?t=621930 (Video 9: How To Perform A Task 29 Without MTTY)
direct link: http://www.youtube.com/watch?v=DtTDuc4V4cU
To do:
remove the "reset" command from task29.exe, to stay into boot loader screen. Then, one should flash the new rom immediatly using their cook's flash utility.
Original files
http://www.megaupload.com/?d=J3OELQ8I
RS mirror, by Sardelisp
http://www.rapidshare.com/files/361617741/Radio_2.08.50.05___task29.zip
Edit, distribute, repack, comment and spread these files as much as you want.
Click to expand...
Click to collapse
I've tried some of these suggestions, but none work. I tried Task29 flashing a boot screen and everything was erased. I flashed a new ROM and guess what? SOD even with task29
If you want to try any of these procedures do it "At your own risk" task29 for Topaz will flash a custom boot screen and erase your WinMo.
Use it at your own risk
And you, got any solutions that want to share?
PS. I'm sorry for my english, remember I'm El Toro not "The Bull"
I have an ATT Pure and have flashed every ROM on here that is in English and not once has one failed to boot or contiunue running till I get tired of it. You do have to use HARDSPL with all of them. My only ROM issue are the ROMS that have everything in the Start menu instead of separate folders. It seems so disorganized but that is a different topic.
I just wanted to point out it must be your phone or you have not used hardSPL or maybe your phone vendor bugged it so you can't flash a new ROM.
Oh I also noticed you say it's and ATT thats unlocked. That could be the issue. Mine is not unlocked. BTW being unlocked would mean it is not an ATT unit any more right?
Solarenemy68 said:
I have an ATT Pure and have flashed every ROM on here that is in English and not once has one failed to boot or contiunue running till I get tired of it. You do have to use HARDSPL with all of them. My only ROM issue are the ROMS that have everything in the Start menu instead of separate folders. It seems so disorganized but that is a different topic.
I just wanted to point out it must be your phone or you have not used hardSPL or maybe your phone vendor bugged it so you can't flash a new ROM.
Oh I also noticed you say it's and ATT thats unlocked. That could be the issue. Mine is not unlocked. BTW being unlocked would mean it is not an ATT unit any more right?
Click to expand...
Click to collapse
Thanks for replying, my pure is Hardspl'd with the latest 2.51 Olinex. It's unlocked meaning Sim Unlocked that I could use it with any Operator that uses a Sim Card, and yes I could flash every single ROM that it's posted in this Topaz ROM Development thread. I've been using Dutty WWE Official Test ROM since he posted it and no problems have come up at all. The "new ROMS" are the ones that caused the SOD even our chefs have suffered from this bug. So it's not the device.
I never had the SOD happen to me. And i have htc pure too.
Apparently, the great majority of us do not have this problem, and have never heard of it. As long as MTTY is run, I've never heard of anyone having a sleep of death issue.
eltoro said:
There's a lot of beautiful ROMS for our device but most of the new ones face one problem SOD (Standby of Death) when the device goes to sleep you can't wake it up.
What "causes" SOD?:
* Bad Flashes
* Residual code for flashing you device a lot
* Newer SYS cooked in ROM
I've been searching for a solution and this is what I've found.
From HD2 ROM Thread
I've tried some of these suggestions, but none work. I tried Task29 flashing a boot screen and everything was erase. I flashed a new ROM and guess what? SOD even with task29
Qbus13 Com2 ROM with SYS downgraded doesn't face SOD.
If you want to try any of these procedures do it "At your own risk" Keep in mind that HD2 task29 files are intended for that specific device not for the Topaz I put them here just for reference, If you want to try the task29 for Topaz I could post it here, It will flash a custom boot screen and erase your WinMo.
And you, got any solutions that want to share?
PS. I'm sorry for my english, remember I'm El Toro not "The Bull"
Click to expand...
Click to collapse
Standby?
I've ran a few Rom's here from energy 6.5.5 to Dutty R6 - R10
with the latest 6.5.x builds, every once in a while after coming back from standby the device will be unresponsive. The touch screen seems to not do anything, but the hardware keys work fine, typically placing it back to sleep and waking it up again seemed to fix it... I have had to pull the battery once.
This didn't happen on the 6.5 builds, only 6.5.5.
Mostly running Energy Aprl and May releases.
I had SOD. I've solved it by changing my SIM card since previous one was more than 10 years old. With new one I never had this problem.
I'm using NhatHoa TopazRom 23563 WWE so far no SOD after 2 days of using it.
I flashed the Dutty's Topaz Sense 2.5 Holy Grail R10 |WWE| rom last night and get my phone goes into the SOD pretty much every time I leave it alone for more than 10 minutes. I have an HTC Pure as well. From the searches I've done it seems solving this problem is pretty much a turkey shoot. I just wish there was a concrete solution, as I kind of like being able to use my phone.
reptiletim said:
I flashed the Dutty's Topaz Sense 2.5 Holy Grail R10 |WWE| rom last night and get my phone goes into the SOD pretty much every time I leave it alone for more than 10 minutes. I have an HTC Pure as well. From the searches I've done it seems solving this problem is pretty much a turkey shoot. I just wish there was a concrete solution, as I kind of like being able to use my phone.
Click to expand...
Click to collapse
The same thing happened to me with that ROM but if you flash Dutty's Topaz Holy Grail R11 WWE it's fine no SOD
On the Touch Pro 2, Tilt 2 section they have a lot of theories about what causes SOD http://forum.xda-developers.com/showthread.php?t=648134
but still no solutions.......
They said that Task29 is the solution but is not I'm posting the Task29 files if you want to try it yourself
INSTRUCTIONS:
Originally Posted by SacTilt
Some of you are making this too difficult. I've posted this before, as this is all that needs to be done. Task29 does not remove your radio or your splash screen. It only clears the ROM, therefore, all you need to do is run Task29 and then flash your ROM. This is how I do it from the PC.
Connect to PC via Active Sync/WMDC.
Execute Task 29.
When phone boots to "Touch Pro 2" screen (or whatever your splash screen happens to be), I hold down the volume down button while hitting the reset button.
Once I'm on the Bootloader screen, and it shows "USB", I flash the new ROM from the PC as I normally would.
When the phone vibrates, indicating the ROM upgrade is complete, I disconnect the phone from the computer.
Click to expand...
Click to collapse
Of course in this case will be your Topaz, Pure, Touch Diamond 2 boot screen
CREDIT:
all credit goes to doloop
Originally Posted by doloop
Hi,
I hex edited RomUpdateUtility.exe so it runs task 29 right after flashing ruu_signed.nbh
As every one understand this command format the rom,
Just unzip and run task29.exe . You may replace ruu_signed.nbh with the radio of your choice.
After the phone reset itself, your old rom will be gone, so it won't boot: binfs has been formated, your phone memory is clean.
You'll need to power up in bootloader mode (press vol down right after power key), then use the leocustomruu.exe provided with your favorite rom package, or flash it from memory card using standard procedure.
Click to expand...
Click to collapse
This files are for Topaz only it will replace your Boot screen or if you want to replace it with another boot screen or radio is up to you. I like the boot screen because the process is faster. **Use it at your own risk**
ive done a lot of research and still cant find a solution. im sort of a newb, heres the problem my wifes TP2 when she turns it off and turns it back on the phone gets stuck on bootloadr screen, tried to hard reset but wont do anything. but when i plug it with usb to my laptop if i soft reset it will boot up.I read that alot of people had the same problem and just had to install a coocked rom, well i did i installed energys rom but it still had the same issue. Now its back to stock rom. any info on how to fix this is appreciated and thnx in advance.
Get it replaced under warranty
if you were able to flash a cooked rom, you must have installed hard-spl.
when did you do this, after the problem appeared to be able to flash the energy rom, or before? maybe this could be the problem...
http://forum.xda-developers.com/showthread.php?t=606078
here is a thread on the subject already.
Huthus said:
if you were able to flash a cooked rom, you must have installed hard-spl.
when did you do this, after the problem appeared to be able to flash the energy rom, or before? maybe this could be the problem...
Click to expand...
Click to collapse
well the first time her phone did it i googled the problem and it brought me here, a thread that said stuck at bootloader screen and their solution was flashin a cooked rom. well it got the phone to boot after i did that but every time if she turns it off and back on it gets sutck at the tri color screen. i installed hard spl when i was flashin rom.
here is a thread on the subject already.[/QUOTE]yea been at that thread also,but my problem is that when i turn the phone off and when i turn it back on it wont boot up it just gets stuck there, like i stated above i already flashed hard spl and flashed a energy rom but it still does the same thing. i flashed the phone back to the original rom but is still gets stuck, the phone works as long as she dont turn it off but after awhile her ram goes up to like 80 so i have to turn it off, and to turn it back on i have to use my laptop. and thanx for the help guys i really appreciate it. and phone dont have warranty i bought it on craigslist.
Since it's going to the tri-color bootloader screen, seeing as normally to get to that screen you would hold volume down on boot, have you checked inside the back of the case to make sure there isn't dirt/debris jamming the volume down button? If the volume adjusts normally once you do get it booted, that may not be it, or maybe it's just a short in the key.
Also, both the stock ROM and energy ROMs are bad about eating ram, and need to be rebooted regularly. Maybe try one of the ROMs that doesn't, like a Jackos rom, which you can leave running for days without a reset. Might not solve your problem, but might at least take some of the bother out of it.
FL5 said:
Since it's going to the tri-color bootloader screen, seeing as normally to get to that screen you would hold volume down on boot, have you checked inside the back of the case to make sure there isn't dirt/debris jamming the volume down button? If the volume adjusts normally once you do get it booted, that may not be it, or maybe it's just a short in the key.
Also, both the stock ROM and energy ROMs are bad about eating ram, and need to be rebooted regularly. Maybe try one of the ROMs that doesn't, like a Jackos rom, which you can leave running for days without a reset. Might not solve your problem, but might at least take some of the bother out of it.
Click to expand...
Click to collapse
I take it you haven't used the latest NRG ROM. Mine runs for several days.
stevedebi said:
I take it you haven't used the latest NRG ROM. Mine runs for several days.
Click to expand...
Click to collapse
You've got me, there. The last energy rom I tried was a little bit ago, and was a Maxsense version at that. Even still, it soundly failed my Opera Mobile 10 test on a clean flash off of a fresh boot (it would autokill OM 10 to free up ram without any other apps open). Any rom that does that goes straight into the bin as far as I'm concerned.
I have been meaning to drop one of the more recent builds on to see if that was just a bad experience. Maybe try one of the titanium versions, just to make sure I'm giving it a fair shake. Either way, this has now gotten at least a bit off topic. =P
stevedebi said:
I take it you haven't used the latest NRG ROM. Mine runs for several days.
Click to expand...
Click to collapse
yea i have the sep 18 nrg rom on mine wich now runs very good. well after a couple reboots with the phone plugged to my laptop, i unplluged it and tried a soft reset and thank god it booted normal, i then powered the phone off and turnd it back on and it worked. dont know what the problem was but i appreciate everyones help.
There is different things that you can do to try and resolve your problem. Start by finding a rom that you would like to install on your phone and save the file to your SD Card. FL5 Mentioned Jacko's rom and I swear by it as well. I run the showlite version modified to my liking and still have on average about 80 mbs of ram open.
2nd thing to do would be a Task 29 which will pretty much formats your phone. This is important to do because if there is any "debris' left over from any of the roms you have installed, this will take care of that. "Debris" at times cause issues that you cannot pinpoint and interfere with the rom that is currently installed. It is also important that you do this step second because once you do a Task 29 you will not be able to flash through USB. At least, I have not been able to do so. I flash from my SD Card. You can get Task 29 here-->http://forum.xda-developers.com/showthread.php?t=649191
Once you do that, flash your rom from your SD Card by following the directions here-->http://forum.xda-developers.com/showthread.php?t=550540
Hopefully this fixes your problem. If it doesn't, you don't have to soft reset to free up ram. I use software called "cleanram" and usually run it on level 3 which means that it thoroughly finds processes taking up ram and reclaims it. You can also schedule a daily, weekly, hourly clean under the settings menu. You can find that here-->http://forum.xda-developers.com/showthread.php?t=514333
Best of luck.
Oooooooooooo yeah! Task 29 is absolute magic. Completely wipes your NAND before a flash to remove the chance of old ghost files from past ROMs jacking up your system. If you've followed any of the flashing tutorials on the board then you've definitely been doing this step, and thus this shouldn't have been your problem. Not everyone has problems if they skip it, but all sorts of seeminly otherwise random problems can pop up otherwise.
marduk79 said:
2nd thing to do would be a Task 29 which will pretty much formats your phone. This is important to do because if there is any "debris' left over from any of the roms you have installed, this will take care of that. "Debris" at times cause issues that you cannot pinpoint and interfere with the rom that is currently installed. It is also important that you do this step second because once you do a Task 29 you will not be able to flash through USB. At least, I have not been able to do so.
Click to expand...
Click to collapse
Eh ? I don't know what's going wrong for you, but that's completely untrue. After running task29, you need to unplug the phone from the PC, put the phone into the bootloader (e.g. press reset while holding down the Volume Down button), wait for it to come up and say "Serial" at the bottom, then plug it back in and it should say "USB". Then you can flash via USB (which is safer than flashing from SD card, since it does more checking).
FL5 said:
You've got me, there. The last energy rom I tried was a little bit ago, and was a Maxsense version at that. Even still, it soundly failed my Opera Mobile 10 test on a clean flash off of a fresh boot (it would autokill OM 10 to free up ram without any other apps open). Any rom that does that goes straight into the bin as far as I'm concerned.
I have been meaning to drop one of the more recent builds on to see if that was just a bad experience. Maybe try one of the titanium versions, just to make sure I'm giving it a fair shake. Either way, this has now gotten at least a bit off topic. =P
Click to expand...
Click to collapse
The 20 Sep ROMs have the option of using quick menu. With that option, even with Sense 2.5 and CHT (a RAM hog), I have 88 Mb available on a normal basis. I don't use Opera 10 (also a RAM hog), but I think it would work with the new ROM.
You have to manually select the Quickmenu option.
well the problem with her phone is fixed. but now my hardware keys stay on dim but they stay on, im gonna try doin task 29 and reflashing a rom see if that takes care of my issue.
Well just for future references, I had all of the above problems and tried all of them. Issue did not go away until I did the following steps..:
Run Task 29
Flash new ROM (Issue still exist)
Flash New Radio (Issue still exist)
Reflashed Hard-SPL (This somehow fixed the issue....)
starmena said:
Well just for future references, I had all of the above problems and tried all of them. Issue did not go away until I did the following steps..:
Run Task 29
Flash new ROM (Issue still exist)
Flash New Radio (Issue still exist)
Reflashed Hard-SPL (This somehow fixed the issue....)
Click to expand...
Click to collapse
well i just did all of it and the freakin keys wont go off, n e one have any other suggestions? and thanks to every one for their help.