Database Develop

spv m3000 stuck at 98% with rom

Great my wizzard is stuck
its on 98% then de blue/green bar on my phone turned red en stays that way it doesnt do anything anymore, after a while my computer says the installation is finished, (SOMETIMES i get an error that has something to do with memory on my computer. or it says usb connection got lost or something)
i can reboot my phone but its going straight in the boot menu with those collors, i can try the downgrade rom again but it keeps getting stuck at 98%
anywone some suggestions?
I tried to install the folowing: CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe
becose i wanted to unlock my phone (dont know if its locked or not)
I tried a few other roms but they wont install at all
I forgot some info:
ipl/spl 2.18 so i have/ (HAD) a G3
gsm 01.04.10
os 2.18.1.3
it is an orange m3000 (i have a t-mobile simcard)
im using my sim in another phone do i need the simcard in the m3000 ?
well a few minutes later:
i put my simcard in my phone, but it still hangs
i tried in now on 2 computers but both are stuck at 98%
on my second pc i get the message ERROR [302] : UPDATE ERROR
The ROM update Utility has encountered communication errors during the update process. The program will guide you stem-by-step to recover from te errors so you can continue with the update.
2 choices to click: View Document or Recovery
lol i did the Recovery it made me put out the battery and reboot the phone en replug the cables
well ill try again then... :|
did it about 8 times now, keep getting stuck at 98% notice that the bar becomes red at 98%
anywone please any suggestions? im afraid i bricked my phone

There are 24 people who look at this topic and nowone has a clue what i need to do???

kaasaanfiets said:
I tried to install the folowing: CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe
becose i wanted to unlock my phone (dont know if its locked or not)
I tried a few other roms but they wont install at all
I forgot some info:
ipl/spl 2.18 so i have/ (HAD) a G3
gsm 01.04.10
os 2.18.1.3
it is an orange m3000 (i have a t-mobile simcard)
im using my sim in another phone do i need the simcard in the m3000 ?
Click to expand...
Click to collapse
is a 1.04.10 radio a valid radio for a 2.xx rom?
If you are stuck, the only/best way to recover is to flash an official rom from your carrier. You can get to the bootloader so you are NOT bricked. You are just flashing roms that have a CID that doesn't match your phones. Try the button rom or the wizard love rom that the unlocking stickies mention repeatedly.
Were your IPL/SPL 2.18 before you started?
Read the Wiki, Read the stickies. For every person that says the process doesn't work there are 100 that it works flawlessly for and 99% of the time those that can't get it to work don't follow all the steps in order or just outright skipped steps or substituted with what THEY thought was better. There is a reason for each and every step in the guides. IF you follow them properly you WILL NOT have any issues.
For the situation you are in now: STOP trying to flash custom roms, you MUST get your phone back to a usable state before you go down that path again. Use your carriers latest available rom to recover your device.
Also you are lucky to get an answer at all because your question is asked in almost every single new thread and every single ROM thread. The answers are already easily found if you take the time to look yourself.

thanks man, i tried the original orange rom and it worked.
RUU_Prodigy_2180103_21801103_OR_NL_DUT_Ship.exe
im so happy, thank you for all your helpful comments
2.18 before i flased is yes.
i wanted to copy a new rom to my device, but i thought it was cid locked.
so i followed step by step the guide from faria
http://forum.xda-developers.com/showthread.php?t=263116&highlight=stuck+at+98%
but i think the problem was that i did not have an aku2 or whatever that means.
Im sorry if im being rude, but you people do a wonderful job on those roms and step by step guide's but u forget that there are people that have no clue what aku2 means when i google is, it says a new rom from t-mobile with wm5 but it doenst say how somewone can check for themselfs if they have an aku2 rom...
Im verry sorry for those noob questions but it look like a heva the same rom that i had before i messed it all up.
so can i install a new rom from here? like one of these?
Pro Black 3[1].0.1.exe
CB-AIRAF.exe
?

kaasaanfiets said:
thanks man, i tried the original orange rom and it worked.
RUU_Prodigy_2180103_21801103_OR_NL_DUT_Ship.exe
im so happy, thank you for all your helpful comments
2.18 before i flased is yes.
i wanted to copy a new rom to my device, but i thought it was cid locked.
so i followed step by step the guide from faria
http://forum.xda-developers.com/showthread.php?t=263116&highlight=stuck+at+98%
but i think the problem was that i did not have an aku2 or whatever that means.
Im sorry if im being rude, but you people do a wonderful job on those roms and step by step guide's but u forget that there are people that have no clue what aku2 means when i google is, it says a new rom from t-mobile with wm5 but it doenst say how somewone can check for themselfs if they have an aku2 rom...
Im verry sorry for those noob questions but it look like a heva the same rom that i had before i messed it all up.
so can i install a new rom from here? like one of these?
Pro Black 3[1].0.1.exe
CB-AIRAF.exe
?
Click to expand...
Click to collapse
You will not be able to install a CUSTOM rom until you CID unlock. I don't believe the Black 3.0 rom is available for the Wizard. It is a Hermes rom. There are several WM 6 roms available for the wizard, you should probably look in the WM6 sub-thread once you get yourself completely CID unlocked.
The tutorial tells you everything you need to know, even if you don't know anything about anything. Just read the instructions follow the links to download the roms/tools that it is talking about. If you don't understand the instructions you can post in that thread and the authors or others will help you there. Though they most likely will not respond until you show that you have read and at least have an idea of what you are trying to do, where you started where you are and where you would like to end up. If you don't understand the instructions there is always the IMEI unlockers site that will give you a utility to do it if you want to pay them for it.
Why are you trying to upgrade? Do you need to upgrade? Are you willing to void your warranty on your phone? Can you live without it if something drastic happens and you truly do brick your device, in most cases you will not be able to exchange your phone under warranty? If you haven't defined the first question or answered no to any or all of the other questions you shouldn't be rom flashing, especially not with unapproved roms that aren't supported by your carrier. You need to measure the potential gains against the risk of doing these things to determine if it is right for you. Once you get unlocked and flash a couple of roms you will see that it is easy and relatively safe as long as you read and follow the instructions they are tried and true and do work if they are followed properly.
I would suggest using this thread to unlock your device: http://forum.xda-developers.com/showthread.php?t=285435

Zzan said:
You will not be able to install a CUSTOM rom until you CID unlock. I don't believe the Black 3.0 rom is available for the Wizard. It is a Hermes rom. There are several WM 6 roms available for the wizard, you should probably look in the WM6 sub-thread once you get yourself completely CID unlocked.
The tutorial tells you everything you need to know, even if you don't know anything about anything. Just read the instructions follow the links to download the roms/tools that it is talking about. If you don't understand the instructions you can post in that thread and the authors or others will help you there. Though they most likely will not respond until you show that you have read and at least have an idea of what you are trying to do, where you started where you are and where you would like to end up. If you don't understand the instructions there is always the IMEI unlockers site that will give you a utility to do it if you want to pay them for it.
Why are you trying to upgrade? Do you need to upgrade? Are you willing to void your warranty on your phone? Can you live without it if something drastic happens and you truly do brick your device, in most cases you will not be able to exchange your phone under warranty? If you haven't defined the first question or answered no to any or all of the other questions you shouldn't be rom flashing, especially not with unapproved roms that aren't supported by your carrier. You need to measure the potential gains against the risk of doing these things to determine if it is right for you. Once you get unlocked and flash a couple of roms you will see that it is easy and relatively safe as long as you read and follow the instructions they are tried and true and do work if they are followed properly.
I would suggest using this thread to unlock your device: http://forum.xda-developers.com/showthread.php?t=285435
Click to expand...
Click to collapse
I bought my phone second hand (i dont have a receet of something) so i dont have any warranty anymore
i like my phone but i have troubles with sms the recever keeps getting old of no messages so that why a want another rom
i would be a shame if i brick it, but im willing to try
im doing the steps from your link now, ik istalling te rom at the second point but it still is stuck on 98% :|
is there another 1.5 rom? that i can try? i read someting about the love rom

kaasaanfiets said:
I bought my phone second hand (i dont have a receet of something) so i dont have any warranty anymore
i like my phone but i have troubles with sms the recever keeps getting old of no messages so that why a want another rom
i would be a shame if i brick it, but im willing to try
im doing the steps from your link now, ik istalling te rom at the second point but it still is stuck on 98% :|
is there another 1.5 rom? that i can try? i read someting about the love rom
Click to expand...
Click to collapse
The Wizard Love rom is another that people use when the Button rom doesn't work for them. I don't have a link to it but I am sure it is linked in the Upgrading or G4 sub-forums. Maybe even in the Wiki. Sorry haven't been spending much time in the Wizard forums as I only flash my wizard when something breaks, or a new feature is added -- My wife uses that phone now .
There is always the pay to unlock website but you should be able to get it unlocked with either button or the wizard love rom.
Just out of curiosity how long do leave it sitting at 98% before you determine that it is stuck? All roms "stick" at a few points during the flashing process. If you didn't wait at least 5 minutes or get an error on your PC you probably didn't wait long enough. Best advice I have on this is disable all power management/screen savers on your PC set up the flash. Once it starts leave the room and close the door for no less than 30 minutes. This way you can be sure that you didn't interrupt it. For a Wizard the flash should complete in 10 minutes or less. For the Hermes it can take a full 30 minutes depending on your flashing method an which components you are flashing. It is normal to hang for a few minutes at different points during the flash process, just because there is no transfer doesn't mean something isn't being decompressed/written on the device from what has already been transferred over.

Zzan said:
The Wizard Love rom is another that people use when the Button rom doesn't work for them. I don't have a link to it but I am sure it is linked in the Upgrading or G4 sub-forums. Maybe even in the Wiki. Sorry haven't been spending much time in the Wizard forums as I only flash my wizard when something breaks, or a new feature is added -- My wife uses that phone now .
There is always the pay to unlock website but you should be able to get it unlocked with either button or the wizard love rom.
Just out of curiosity how long do leave it sitting at 98% before you determine that it is stuck? All roms "stick" at a few points during the flashing process. If you didn't wait at least 5 minutes or get an error on your PC you probably didn't wait long enough. Best advice I have on this is disable all power management/screen savers on your PC set up the flash. Once it starts leave the room and close the door for no less than 30 minutes. This way you can be sure that you didn't interrupt it. For a Wizard the flash should complete in 10 minutes or less. For the Hermes it can take a full 30 minutes depending on your flashing method an which components you are flashing. It is normal to hang for a few minutes at different points during the flash process, just because there is no transfer doesn't mean something isn't being decompressed/written on the device from what has already been transferred over.
Click to expand...
Click to collapse
Yes well i waited the first time for like 15 minutes then my computer shut down the update programm
today i waited like 30 minutes cos i even had dinner.
Well ill try the love rom some other time cos i need my phone to work sunday becose i need tomtom
thank you for your information i appreciate it verry much
i noticed that the original rom that does work: RUU_Prodigy_2180103_21801103_OR_NL_DUT_Ship.exe that one, also flashes red and green while installing so i guess thats normal...

[TUT]Flashing the easy way

Hey everyone!
Read lots of threads here on the xda-developers forum, many questions, many answers, lots of "good guys" who are willing and able to help (many have helped me, thank you goes to them and all the others).
The bottom line:
Saw many many questions concerning flashing, bad flashes, error messages and so on.
I really don't know WHY people won't go for the easy way?
Flashing from a PC involves a USB connection through Activesync/WMDC, an application, we all know the procedure thanks to racerx_ (http://trinityguides.info). There are so many things that can go wrong: think about it, from unplugging the device, app error, comm error, power drop, connection drop, system hang and so on.
I don't know about the rest of you but I have done it the hard way but also learned to do it the easy/safe way. There's nothing more to the story than flashing from SD card. Procedure is well described in the Wiki (http://wiki.xda-developers.com/index.php?pagename=Trinity_SDCardFlashing).
I mean, all you have to do is press three buttons and wait for the flash, no risky connection drops, error messages, driver incompatibilites (see Vista problems), no app hangs.
I have tried many ROMs from over here and except for my first two flashes (first was Des' Crash Proof SPL, second was a cooked ROM) I've made them all using the SD card method and never got an error nor a situation with it.
So here's the question: why won't people flash the easy way?

well, have you actualy tried this procedure before posting this?

banesi said:
well, have you actualy tried this procedure before posting this?
Click to expand...
Click to collapse
Read my post once again, carefully.

hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom
This procedure brings boot loader screen, with three colors, it doesn't bring anything similar to that image posted there.

banesi said:
hold Power button on right side and Camera button at same time and stick with stylus in RESET on bottom
This procedure brings boot loader screen, with three colors, it doesn't bring anything similar to that image posted there.
Click to expand...
Click to collapse
Follow the steps carefully.
1. SD card with FAT32 and no label (it can contain other files, no need to wipe it)
2. Renamed nbh file to TRINIMG.nbh placed on SD card root
3. Power+Camera+Reset
4. Follow instructions on screen (Power button to brgin flash and Soft reset when prompted at the end).
It don't get any easier!
It SHOULD work.

Totally agree, I don't understand why ppl persist with the multitude of errors that crop up from flashing via active sync.
Using the SD card you can chuck a few ROMs on board to test and just rename each in turn to TRINIMG.nbh, move it to the SD root and enter boot loader.
Before I test a new ROM I make a static settings image with SPB Backup so I can flash back to the old ROM and restore back to how it was in a jiffy.
Just to point out for some ppl, some of the ROMs here are packaged into EXEs, you will need to extract the contents and only use the file named RUU_signed.nbh.
This process can also be used to flash Radio ROMs in case you flash a ROM that includes a radio that you don't like/use.
Good thread

P3600i saga continues
I wonder if the SD Card method works on the P3600i? According to the Wiki, it doesn't bypass the SuperCID check.
Olipro has modified his SPL-Trin to work with the P3600i. But so far there's still no definite way to flash it. No Hard-SPL, splxploit don't work, same for JumpSPL. So maybe this is the way? Any opinions?

remofo said:
I wonder if the SD Card method works on the P3600i? According to the Wiki, it doesn't bypass the SuperCID check.
Olipro has modified his SPL-Trin to work with the P3600i. But so far there's still no definite way to flash it. No Hard-SPL, splxploit don't work, same for JumpSPL. So maybe this is the way? Any opinions?
Click to expand...
Click to collapse
No, sorry, it's not the way.
Flashing from SD card is not a workaround for bypassing SPL.
You still have to have some kind of a Hard SPL installed.
Please check the Wiki.

evojulz said:
This process can also be used to flash Radio ROMs in case you flash a ROM that includes a radio that you don't like/use.
Click to expand...
Click to collapse
...and also bootscreens.
In other words, this method can flash any nbh file which could be flashed through the update utility method.

Easy and reliable
Fully agree with you tnyynt!
I always flash using the SD method.
Sometimes I even download the new nbh and keep it on the SD and upgrade later on when having time, not connected to a Pc... (I also have all the cab I need on my SD card).
Quick, easy and reliable (done many times).
Would be fine if the nbh would be released on this forum (rather than the .exe package).
Would allow to download them directly from the Trinity. i.e.: no more need for a Pc !!!

I always use this method, it is the only one that works for me and it's the most convenient I think.

I tried this method several times, but I was never able to get it work.
Yes I followed instructions carefully, but no. I only get three colored bootloader screen, that's it. No button to start flashing, nor screen that looks like that photo in wiki.
I really wanted this to work, cause I have an OsX. Since I couldn't get it to work I had to install xp and use it as virtual machine. From there everything works just great. Because of that, I still have to have windows on my laptop :-(

Speed
About this method: is it faster, same or slower than usb? (consider an average SD card, no high-speed)

Sure SD is faster
g77 said:
About this method: is it faster, same or slower than usb? (consider an average SD card, no high-speed)
Click to expand...
Click to collapse
I flashed recently FinixNOver 3.0.2 (BTW - superb ROM) - only OS + splashscreens and it took 2.5 mins in SD (regular 2GB miniSD SANDISK). I think it is fast enough...

Hi!
I want to tell me,if anybody knows, if i make my device superCID i loose the waranty!
I try to flash it with Trinity_SDCard Flashing from wiki (i make 3 step) and after the reset when is in the grey screen and loading i saw in the up side of screen the number 00068002 and after that change to 3 colored screen!
Any help?

jukkus said:
I tried this method several times, but I was never able to get it work.
Yes I followed instructions carefully, but no. I only get three colored bootloader screen, that's it. No button to start flashing, nor screen that looks like that photo in wiki.
I really wanted this to work, cause I have an OsX. Since I couldn't get it to work I had to install xp and use it as virtual machine. From there everything works just great. Because of that, I still have to have windows on my laptop :-(
Click to expand...
Click to collapse
me second, i also have tried many times and still just can go to the tri-color screen.
i am using hardspl 1.20, and a 4GB sd card with fat32, will these matter?
thanks.

manos_23 said:
Hi!
I want to tell me,if anybody knows, if i make my device superCID i loose the waranty!
I try to flash it with Trinity_SDCard Flashing from wiki (i make 3 step) and after the reset when is in the grey screen and loading i saw in the up side of screen the number 00068002 and after that change to 3 colored screen!
Any help?
Click to expand...
Click to collapse
yes, super-cid will void the warranty.. use hard-spl.. there's no reason to super-cid your device if you're flashing cooked roms..

racerx_ said:
yes, super-cid will void the warranty.. use hard-spl.. there's no reason to super-cid your device if you're flashing cooked roms..
Click to expand...
Click to collapse
Ok, and thank's you very much!

ctrlaltdel said:
me second, i also have tried many times and still just can go to the tri-color screen.
i am using hardspl 1.20, and a 4GB sd card with fat32, will these matter?
thanks.
Click to expand...
Click to collapse
Interesting, I'm sure someone will shoot me down but I'm not convinced it works with all SDHC cards... is your 4GB SDHC?
I can't get it to recognise the NBH from my 8GB but I have flashed many times successfully from my 2GB. Not to bothered, as long as it works

Nope, I'm using 2Gb normal sd-card. Also tried 512Mb card.

Restore device to OEM without touchscreen

Hello out there.....
First of all i have to say THX to all these people which are really willing to help every1 with their great tutorials. Ive used alot of them already. Thanks.
And i have to say sorry for my english language, due Im german and i left school behind long time ago. I'm really taken pains to write this comment.
Now, in my case ive tried to restore my device (Xperia X1i) to OEM status step by step as its shown in this thread.
My worst issue is that my touchscreen aint work anymore after i flashed a custom ROM and that i got stock at the point where the ROM wants to configure the OS like "Tap the screen to continue with configuration".
Ive tried to flash way too much ROMs using HardSPL but the touchscreen wont let me do anything - no reaction.
So how can I restore the bootloader (SPL) on my device, when my touchscreen aint work? How can I take the following step without any working ROM ?
sirsycho said:
12. Run SSPL.KAIS.exe from your phone (make sure you do this on your actual device and not your PC)
Click to expand...
Click to collapse
I do not know what I did wrong, that the screen wont react anymore, but im sure that the SPL is the cause for this disaster.
I'm really desperate couz i already have sent the device to the SE Support, where they told me that there is an "extraneous" on my device although ive flashed the Stock ROM firstly... there was still something that bothered them...
After i got the device back the touchscreen worked again as funny, allthough the support did nothing on the device as they said in the delivery.
A bit skeptical but with alot of happiness i kept on flashing some ROMs after that.
Now, after i found a good ROM and kept this one on my device for some days the screen doesnt work again.....
This is what my bootloader says right now
Code:
KOVS110
SPL-0.72.OliNex
MicroP1-787
MicroP2-707
....seems like the HardSPL is still there......
Honistly i had to apollogize (maybe too late) that this part of using a cellphone (flashing a ROM using HardSPL etc.) is a big fish and that ive underrated it. Now i have a 400$-Device which aint work anymore
Ive read like all Tutorials here at xda-devs containing something about flashing a ROM or informations about SPLs; tried everything
I feel like im lost and fu**ed right now....
Is there any1 can help me with my problem?
Hopefully there is.....i pray for him

first flash a stock rom
then just run the hard-spl exe, and replace the ruu_signed.nbh file
why are you trying to use kaiser spl?
use the things found in the hardspl sticky in the xperia section

Wrong Tutorial
You're using tutorial for wrong device (HTC Kaiser)
The correct tutorial is in first post (extra how to: how to restore Stock SPL for warranty reasons.)
http://forum.xda-developers.com/showthread.php?t=431218
But before restoring original hardspl you should flash with original rom found in this thread http://forum.xda-developers.com/showthread.php?t=475482

wow thanks for your answers !!
i never thought ill get response.
Its really weird that i havnt found that tut before bcuz i was looking through whole board.
I will try do that tomorrow.
I hope that it will work then. Don't wanna pay 300$ for a new device

Else there is mtty to restore the bootloader

Aight i have done the steps showing in the tutorial.
1. I have flashed teh Stock ROM (R2A german - Vodafone)
2. I've used the RUU with the stockSPL given in that post.
Now my tricolour screen shows the following
Code:
KOVS110
SPL-0.72.0000
MicroP1-787
MicroP2-707
This is what it shall looks like OliNex said.
I hope this is all i had to do, to make use of my device's guarantee, cuz the touchscreen still doesnt work
Seems like i really have to send my Xperia to the Support again (now hopefully with a ROM + SPL they wont reject)
But if i send my device with "extraneous" again i have to pay another 15€ just for let them do a costs estimate -.-
I would like to get a reply before i make use of the support again.
Thanks for all your help

Glad to hear recovering to stock rom + spl worked out.
Your touchscreen doesn't work when you have booted up windows?
If that's correct then I suggest to send in the device for service. Although
it might not help I suggest updating your device with SE updating service (SEUS) first.
After the flash remove the battery for 10 seconds, then turn it on.
Hope it helps and otherwise servicing the device is free of charges

Haha!
That's what im doing right now, using SEUS
Thanks for the tip with the battery but i already tried that way too often
Edit:
Ok, touchscreen still aint work....
Time to contact the support...at 11:45 PM **WOOT
nvm....Ill wait till tomorrow
gn8 and thanks for helping me with my issue ^^

a few days ago I returned my silver X1 for the same issue, my touch screen (digitizer) doesn't work. Then right in front of SE support person, he justed took out the battery and rebooted. Then it worked. The thing is, I did the same thing several times earlier that day and it did NOT worked. I am worrying of getting the same problem again and I only have until november 30th until my 1 year warranty expires. I haven't tried any cooked roms and it is because of warranty purpose. Altough I'm not new to custom roms since I own an Alpine and a Prophet. I've been here for some time now.
The thing that holds me back testing cooked roms on my Xperia is the aftermath if in case my device goes half-dead. I almost always read the restoring on to official roms everytime I get here, but still the thousand dollar spent on my phone's tag price comes with a fear of who's gonna rescue if my phone won't work. And to add that spare parts aren't available here as of the moment. And yes I'm eager and very curious about almost everyone saying cooked 6.5 is faster than stock roms but though I haven't tested it I have to disagree for now on my case basis.
First, my Xperia doesn't come with a carrier lock. It's locally called "open line" in my country I guess technically called debranding. Then my phone has the generic r3a rom via seus I think it's generic uk. Lastly, for some reasons, the touchflo 3d doesn't work with my device I've tried it since r1 firmware time. Some response told me to unlock-debrand my phone first but I dont have to since it isn't locked. Still installing tf3d makes my phone hang, doesn't uninstall, doesn't show in the themes list if installed as a theme, and doesn't let me have another panel since it always stay as tf3d whenever I choose another one. And it is very unstable in my device. These happened even if I install it as a panel.
I feel handsets here are faster than handsets that are locked by a carrier so I'm thinking again since for now, my Xperia works for me as stock as it is.

Help! My Tilt2 froze halfway through a ROM flash...

I have done hundreds of ROM flashes and never seen this happen before. I have HardSPL installed and have already flashed this puppy several times. I am upgrading via MicroSD to EnergyROM Nov.9 21864 w/ Manila 2.5. It's stuck about halfway through the upgrade and I don't know what to do next in fear of bricking the phone or is it already too late? Should I remove the SD card and load a stock ROM onto it then try to enter bootloader mode again and flash? Please help!

Nevermind, I got tired of waiting for an answer so I went ahead and followed my own steps as above. It worked, I was able to get into bootloader and flash a new ROM. All is well.

You beat me in resolving the issue! I left my post below anyway
I would try flashing from your PC when the device is in Bootloader Mode. To get to the Bootloader mode if you don't know: press the power button while holding down the Volume Down button (do this from an off state). If you see what is mostly refered to as the tri-colour screen you are almost ready to flash from your PC. Plug in your USB data cable and wait for the driver to load and the screen text to go from Serial to USB on your device. Now run the .RUU file from the ROM you want to flash.
This method should work... if not, look on the Rhodium wiki. There may be some other methods listed that I don't know of to revive the device.

yeah, problem is there is NO 9 nov energy ROM for the GSM.......... it was an ut-oh............. but, just doing what you did with the good ROM and the SD, all fixed, look on NRG's "photon" and you'll see it happened to a couple of us.

Thanks for responding anyway. I flashed with the microSD card again, not with my PC, and it worked fine. Looks like I won't need to bring my Kaiser out of retirement after all.

hisandherturbo said:
yeah, problem is there is NO 9 nov energy ROM for the GSM.......... it was an ut-oh............. but, just doing what you did with the good ROM and the SD, all fixed, look on NRG's "photon" and you'll see it happened to a couple of us.
Click to expand...
Click to collapse
Actually there is a Nov 9 Manila 2.5, but last I checked he hadn't updated the Changelog or the title of the thread yet. Click on the download link and you'll see it there.
Anyway, I suppose this thread no longer serves much purpose so feel free mods to kill it or just let it die a slow painful death.

[Q] help

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.