Database Info

Almost bricked !! really ! help needed before it dies !!!

Bonjour
I upgraded to WM6 (pdaviet) 2 months ago (I guess..), and problems started to appear a few weeks ago. First it just was hard to boot sometimes, had to reboot several times to get it up and running, but when it could start everything was fine. Then since yesterday, it became harder. And today, couldn't start it at all. Tried several times, and everytime the screen went melted, corrupted, like if it couldn't stand an o/c, but it always runs at normal speeds. I guess it has something to do with the battery and the way WM6 handles it (or at least the implementation we have on our prophet).
I tried to hard-reset, I left it a long time on the format screen (before the actual HR) and it handled it for long enough, but the same thing started while setting up WM.... too bad !
While writing this message I tought I could try to downgrade, and I did using AKU3.3-Jester-b1.
I had no problem while the phone was in guest mode after the HR.
Everything went nice during first step upgrade, but on final reset it did the same thing, and now..... it cannot start at all !!!!
Someone has an idea ? I own a G4 and it has the following roms :
IPL 2.10, SPL 2.20, GSM 2.47 (or something like that)
It won't charge (but my batteries are full, I've got an external charger), it won't start from battery nor from power, even if the battery is removed.
Damn, at least I guess I can return it like that to orange, since it cannot start one can't see the modified rom...
If anyone has a suggestion, it is more than welcome ^^
Thanks !
Niko

huh !
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.

lastnikita said:
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.
Click to expand...
Click to collapse
Hey LastNikita,
I had the same problem ! The white scanlines thing just after re-updating a WM6 version (pdaviet), because I was tired of the constant reset issue.. suddenly, the update went wrong, and I stupidly followed the "recovery" process, which tells u to remove the battery... bang ! screen went corrupted !
Like you, I tought it was over... but I noticed that if you connect your phone and PC with USB, and keep pressed power (ON/OFF button on side) + camera after reseting (little hole on bottom - press during 5 sec!), the PC recognizes a USB device (not the usual phone drivers...) at this moment, I launched the Jester 3.3 (step1) update, in order to downgrade from the ugly WM6 pdaviet... My phone was not yet fixed (still with white scanlines), but at least, I could hear again the WM "start" sound, the scanlines would also "move" across the screen borders when I touched the screen, which made me imagine I was on the calibrating process... also, while connected to PC, after a while, ActiveSync would launch, asking for 1st time synch... this kept me confident as the phone (software) seemed to be reacting fine although HW prob...
I completely charged the phone again (till green light) then kept on reseting the phone (until I hear the WM sound) hoping the lines would finish scanning and come back with the normal .. and guess what, it did !!! Of course, PIGHEAD as I am, I wasn't totally happy it recovered with WM5, so i digged for a better rom, and I can tell you I'm very happy with the smart1 (wizard version) which works fine, but still has some minor bugs as Live Messenger not working... but runs fine (specialy when pressing the ON/OFF button !
PS: Make sure the ALWAYS completely switch off your phone (ON/OFF for 3 secs) before removing the battery... it did happen again... when I stupidly trusted the "recovery" process, again !
DUHHHH !!!!
PS: at least, now you ALL know !
Kokiri

Finally ok for warranty )))
Thanks for sharing mate
I finally managed to downgrade to my original Orange rom, and I'm in the process of putting the original Orange splash screens back (I made the nk.nbf but I can't find the right utility to upgrade... "Update utility cannot open the requested file").
BUT I still have that HW problem afterall.... so I guess it still has to go back to warranty right ? This isn't a big deal since Orange is VERY prompt (I guess I'll get it tomorrow or monday morning, the delivery guy brings a new one and goes back wiv my phone, quite nice !), and I have a button which is stucked (from the begining) anyway ^^
While I'm writing this my phone is docked and synced, and it seems fine.... but, I guess, as soon as I will reset it will start over again.... I'll keep you posted.
Anyway, I'm no longer desesperate and that's good news (for me ^^)
++
niko

yip
ok, everything's back to original.
Actually, it works well when docked, but it freezes/melted screen as soon as I tried to use it on battery, so that I'm quite sure it has something to do wiv WM6.... I'll post that on some crossbow threads this weekend if I have time enough (there are so many of them now !)....
But once more, if YOU read this, keep that in mind.
Hope you guys won't have that kind of failure while trying it.
++
niko

confused
I am having the same problem except the screen showing white scanlines everything else is working on the handset. Could it be a LCD Problem?

Me too...
I have the same issue (black/colored vertical lines and a white screen). I think it has to do with upgrading to WM6 or with overclocking with batteryStatus, not sure. This are the suspects in my opinion....
Now I downgraded to WM5 but the problem seems to persist, I disabled batteryStatus and will see if the situation improves... crossing fingers

Uhm ... possible Overclocked!
I have read 3 threads with same errors!
how much was your highes clock? do you use it for navigation? long time on highest clock or only for speed up?

i dont have a problem with scan lines but with my prophet i use the scaling option and go max to 234 i also set to 234 when using certain apps.
is this damaging to my prophet?
at the moment trying to upgrade to PDAViet 4.0.0.0.3 with a world of pain but thats another topic!

FUZE flashing problems! DPAD screwed up!

So my FUZE was working fine since I bought it when it first came out. It was on Stock ROM, Radio, and SPL. I decided to flash the EnergyROM to try out the new Manilla. I installed the Hard-SPL, flashed the 1.12.25.19 radio, and then flashed EnergyROM 2.0 32209. First thing I noticed was that the DPAD was HORRIBLE.
It would not correctly sense what I am pressing! I press home, and some times it doesn't register anything, sometimes it thinks I pressed left. I try the back button but it thinks I pressed right. I have had this thing since it came out so I know how to use the DPAD now, but whatever happened has completely screwed it up! I thought it was the ROM so I went to the leaked AT&T Test ROM which is also VERY nice. But the problem is still there, the DPAD just does NOT work correctly.
Also, I was unable to send an SMS earlier until I soft reset the phone. That had never happened before either.
Since it is not the ROM, it is either the Radio or the SPL. What I don't understand is that many many people have installed both the same Radio and SPL without any problems. How can I fix my DPAD?

petard said:
So my FUZE was working fine since I bought it when it first came out. It was on Stock ROM, Radio, and SPL. I decided to flash the EnergyROM to try out the new Manilla. I installed the Hard-SPL, flashed the 1.12.25.19 radio, and then flashed EnergyROM 2.0 32209. First thing I noticed was that the DPAD was HORRIBLE.
It would not correctly sense what I am pressing! I press home, and some times it doesn't register anything, sometimes it thinks I pressed left. I try the back button but it thinks I pressed right. I have had this thing since it came out so I know how to use the DPAD now, but whatever happened has completely screwed it up! I thought it was the ROM so I went to the leaked AT&T Test ROM which is also VERY nice. But the problem is still there, the DPAD just does NOT work correctly.
Also, I was unable to send an SMS earlier until I soft reset the phone. That had never happened before either.
Since it is not the ROM, it is either the Radio or the SPL. What I don't understand is that many many people have installed both the same Radio and SPL without any problems. How can I fix my DPAD?
Click to expand...
Click to collapse
Did you try flashing back to the stock ROM? If that doesn't work, I wonder if flashing back to stock everything (ROM, radio, SPL) might kick out the bugs (?)

Did you hard reset after flashing? That might be your problem. And what programs/settings did you install? I would hard reset-don't run UC-then see if the dpad is working fine.

I had the problem without installing anything over the ROM itself. When you flash a ROM, it hard resets, so what does hard resetting again do? I spent like 2 hours getting it the way I like it so I don't want to hard reset again. I tried reflashing the radio but it still had the problem right afterwards, but now it seems to have stopped. This is very weired.
EDIT: It started doing it again but if I put the phone to sleep and bring it back, it normally fixes it. What an annoying problem. I am going to try to flash a different radio and see what happens. I just like this radio so much its GPS actually works decently.

petard said:
I had the problem without installing anything over the ROM itself. When you flash a ROM, it hard resets, so what does hard resetting again do? I spent like 2 hours getting it the way I like it so I don't want to hard reset again. I tried reflashing the radio but it still had the problem right afterwards, but now it seems to have stopped. This is very weired.
Click to expand...
Click to collapse
No, it doesn't do a full hard reset when you flash. A lot of crap is left over, and if you just start using the ROM, you get a bunch of random bugs, like, say your DPAD doesn't work. You're supposed to hard reset when the the phone asks you to align the screen. It's a must. Seriously, hard reset and start over and all of your problems will go away.

I reverted to my stock radio and the problem seems to have disappeared. I will try it out more tomorrow.
How is anything left over? It just seems so odd because I can't ever find anything from before when I flash a ROM.
It seems that I can still get fast GPS locks with this radio too, so I guess the A-GPS fix is all in the ROM.

petard said:
I reverted to my stock radio and the problem seems to have disappeared. I will try it out more tomorrow.
How is anything left over? It just seems so odd because I can't ever find anything from before when I flash a ROM.
It seems that I can still get fast GPS locks with this radio too, so I guess the A-GPS fix is all in the ROM.
Click to expand...
Click to collapse
I have no idea how anything is left over, it just is. Here's what mskip's thread says:
mskip said:
[FONT=&quot]Flashing Via ActiveSync[/FONT]
[FONT=&quot]1. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer.[/FONT]
[FONT=&quot]2. REMOVE SIM and microSD CARDS!![/FONT]
[FONT=&quot]3. Turn phone back on and wait until it syncs with your PC.[/FONT]
[FONT=&quot]4. Run the Raphael_RUU.exe (or [/FONT][/SIZE]RaphaelWrapper.exe if thats included instead) [FONT=&quot]from the Roms Folder.[/FONT]
[FONT=&quot]5. Once phone finishes flashing and gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT=&quot](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT=&quot]6. Follow onscreen instructions to set up your New Rom.[/FONT]
[FONT=&quot]7. Once phone has gone through the customisation procedure then replace Sim and microSD Cards.[/FONT]
[FONT=&quot]8. Turn phone back on and set up as required.[/FONT]
[FONT=&quot]Flashing Via MicroSD Card[/FONT]
[FONT=&quot]1. Make sure your microSD is Formatted to fat32 using a PC (you dont have to delete all files but it is safer if you do).[/FONT]
[FONT=&quot]2. Download your prefered Rom from the Raphael Rom Develpoment Page and unzip/unrar it to your computer.[/FONT]
[FONT=&quot]3. Goto the Roms Folder and rename the .nbh file to RAPHIMG.nbh[/FONT]
[FONT=&quot]4. Copy the RAPHIMG.nbh file to the root of your microSD Card.[/FONT]
[FONT=&quot]5. Plug the microSD Card into the phone.[/FONT]
[FONT=&quot]6. Press and hold the volume down button, then press the reset button with the stylus. Release the volume down button when bootloader tricolour screen appears.[/FONT]
[FONT=&quot]7. Follow the onscreen instructions to start flashing.[/FONT]
8. Once phone finishes flashing and says Update Complete, reset with the stylus
[FONT=&quot]9. When it gets to the screen where it configures the stylus, HARD RESET[/FONT]
[FONT=&quot](hold the VOLUME DOWN and ENTER (center) Buttons, press the RESET button with the stylus tip, then release the RESET button but continue to hold the VOLUME DOWN and ENTER buttons until the reset screen appears)[/FONT]
[FONT=&quot]10. Follow onscreen instructions to set up your New Rom.[/FONT]
Click to expand...
Click to collapse
Here are flashing instructions from At0mAng:
Install Instructions
Read The Flashing Your First GSM ROM Guide
Make sure your battery is 50% charged or more
Power off & Remove SIM Card
Power back on and sync with PC
Flash ROM
Hard Reset where it ask you to align screen
Click to expand...
Click to collapse
They're not telling you to do the hard reset just for the heck of it; there's a very good reason for doing it. Not following the standard flashing instructions and then posting in the chef's thread that his ROM is buggy is just not cool.

It turned out to be the radio causing my problems not the ROM. I have never hard reset after flashing a ROM and never had a problem (and that time wasn't a problem because it was due to the radio ROM)
Not that I am asking for it, but unless there is actual proof that you need to hard reset, I don't think there is a point of doing it.

Ok the problem is back! So annoying. Does flashing the SPL hard reset the phone? I want to try going back to the stock SPL since that is the only thing it could still be, but I would rather not now if it hard resets.

Just get it over with and do a hard reset. Jeez, it's not that complicated.

roms and radios will not adjust the dpad i used the same rom u talk about and never had an issue

Hey petard, did you ever fix the issue with the D-pad ?
I have the exact same issue with my Fuze and can't figure it out.

It is a hardware issue. I had to replace it. My replacement worked fine until about 3 weeks ago where it just started to act up. I called for another replacement a couple days ago and should get it tuesday. They offered me a different phone (Epix or Incite) but I declined but told them to note it that I was offered a different phone.
In about 3 months (when my warranty ends) I will call for another replacement. If they have refurbed Touch Pro 2s by then I will ask for that, if not I will get another FUZE which will extend my warranty for 3 more months (you get 3 months or whatever was left of your original warranty, whichever is longer) and by that time they have to have refurbed Touch Pro 2s where I will then try to get one.

petard said:
It is a hardware issue. I had to replace it. My replacement worked fine until about 3 weeks ago ...
Click to expand...
Click to collapse
It figures, no easy fix. It's strange how it started to act up, mine crapped out right after a flash as well.
Good luck on aquiring the TP2 though.

Frozen/Extremely Slow - Please help!

Hello:
I have searched to forums, but did not find a thread that addressed my specific problem. I'm hoping that someone here might be able to help...
I have a Fuze running the EnergyRom August 1st build. I have not had any problems to date except for the occasional lag and the battery drain. I've never had to reset or anything.
Last night the phone was working fine, I set the alarm, plugged it in and went to sleep. At 2:30 this morning I woke up to my voicemail message on the phone. The phone had somehow called my voicemail. I hit the end key - no problem - but after that my touch screen would not function.
At first I thought the screen was broken somehow. (There are no cracks or spots; it hadn't been dropped. I did not get the "broken screen" or any black/white "noise" that others referred to in their posts.)
I did a soft reset, no result.
Hard reset, no result.
Then I realized that the screen actually works, but so slowly that it is almost imperceptable.
Right now I am on the align screen part of the boot-up. It is taking approximately 8-10 minutes for the phone to register each touch of the target and move to the next.
I assume that eventually it will boot, but my questions are:
Where do I go from there?
Should I just reflash?
What the heck happened???
Any and all advice would be appreciated. Thank you!

Flash back to stock ROM, then reflash a custom one.
Your issue will be resolved

Hi, Bruce. Thanks for responding.
I tried what you suggested, but still no luck. I flashed back to the HTC OEM ROM, then to EnergyROM 'Genesis' (SYS 23016). Now I am stuck on the "tap the screen to set up your Windows phone" screen.
No response at all when I tap the screen.
Any thoughts?

There's an empty text file you can put on your sd card that will let you skip alignment, but I don't remember what you need to name it. Try searching for skip alignment in this forum. Also, there's another recent thread in this forum where 3-4 other posters had sudden screen problems with that rom or one in the series. They may have had black screens. The phones still worked, like with MyMobiler, but the phones were messed up. Search for that thread to see if there's any help. This may be return time, I'm afraid.

When you flashed back to stock, did you see the same issues or only on Energy ROM?
I would say try another ROM.
As Ted said, many users had issues like this on his ROMs.

I looked it up, and the file you need is called "welcome.not" (no quotes). Just rename a blank text file that and put it on the root of your storage card.
Here's another thread on screen issues with that rom.

[Q] MSFT Employee HardSPL'd Device Messing Around

I have a device that used to belong to a MSFT employee. At Microsoft you can just hand in your device and they will put a new ROM on it for you. So first thing I did when I got it is to HardSPL (OliNex 1.90) it and load up a new ROM (the one on it was a couple of builds back, and GPS didn't work etc.).
The strange thing is that ROMS seem to be 'loosing' files (as far as I can tell - apps won't open etc.) after a few days of otherwise great operation. If the device is rebooted, it's almost like a hard-reset; although the installation takes next to no time: and it gets stuck on the splash. Hard resetting the device makes it work for a few days more. The device didn't have these problems with the MSFT ROM (which I stupidly didn't backup).
I have tried a few ROMs and they all seem to have the problem:
MagicROM_23541_Sense25_Mar01
TAELROM_v4.23541_SENSE_2.5_28FEB10_LD
Timolol_5100207TH (awesome ROM)
So my current plan:
Flash stock ROM.
Flash stock SPL.
Flash stock ROM (hoping it will clear anything funny MSFT put on it).
Hard SPL.
Flash Timolol Stock-Like (seems to have the problems the soonest - 2 days max).
Does anyone have any other ideas?
Thanks guys.

I assume since you posted in the Touch Pro2/Tilt 2 section, that you own one of those devices. The roms you have mentioned below are (I believe) for a touch pro/fuze device. That could be your problem. Although, I would assume that you have one as I'm sure a rom for a different device would even flash to the device period. If you have the right rom/device combo and its a touch pro, then you should post in the thread for the roms. More details such as network and device will help the most.

Ah crap - the dangers of having too many tabs open. Can I move the thread myself?

moitoius said:
Ah crap - the dangers of having too many tabs open. Can I move the thread myself?
Click to expand...
Click to collapse
i moved it for you good luck at finding a solution

I don't think it's a hot idea to flash the stock spl. I'm not sure that it can be over-written with hard spl-you'll have to ask in the hard spl thread. If you do it, you might be stuck with the stock rom. Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.

Farmer Ted said:
...Just try flashing the stock rom, then going to the custom one you want. That seems to work for a lot of people.
Click to expand...
Click to collapse
Thanks, that is significantly fewer steps . I will do that for now and report back in 2 or so days...

Small update - just flashed the latest stock Fuze ROM. Just before the customization app come up I saw that device.exe crashed... In any case, I will see what happens with the custom ROM.

You may need to reformat the memory of your phone. Having device.exe crash on a stock rom during bootup is kind of weird. I've never done it myself, but there are threads on it in the Leo forum. I wouldn't try the apps that they've put together, though. I guess you can search around for "Task 29" to find out how to do it properly.

Moved as not ROM Development.

@OP:
If the device was flashed on a regular basis, it's possible that the device flash memory is near end-of-life.
You could try running Raphael Diagnostics on it to see if that sorts it out.
HTH,

What is the lifespan (in terms of flashes) for a device like this?

Plus minus 2 days - it has been able to go as far as 5.
According to this post: http://forum.xda-developers.com/archive/index.php/t-514940.html
These are good options:
http://forum.xda-developers.com/showthread.php?t=435527
http://forum.xda-developers.com/showthread.php?t=491554
This one in particular: http://forum.xda-developers.com/showpost.php?p=3446141&postcount=16 (it applies to Rhodium, but people have had success with it).
Apparently Task 2a (equivalent of 29) is disabled on the OliNex 1.90 SPL - so I can't do a NAND format without reflashing the stock SPL (not that I would attempt that myself in any case ).
I'll run RaphaelDiagnostics and see if that comes up with anything.
Thanks for the help so far guys, I first want to see if the stock flash I did works (I smell a Wiki page).

I tried out the raphdiag-it's pretty cool. I've been having a few weird issues lately on my fuze. In particular, all of a sudden my boot-up time seems to have gotten slow (millisecond to idle thread went from 65-70 sec to 90-95 sec, and I hadn't messed with start up programs). Also, I have been having an issue with files on the main memory becoming corrupted, which has just been weird. Anyway, I ran an 'info 8' with mtty a few weeks ago, and it came up with 7 bad blocks, which seems normal. So, I ran raphdiag this morning, and ran the format nand routine. I was a little surprised, because after running it, I soft reset and the phone booted up normally like after a hard reset. I thought that it was going to wipe the entire rom memory clean, leaving only the radio, bootloader and splash screen. It didn't seem much different from a hard reset. The good news is that my startup is faster. With a setup I was using beforehand, the millisecond-to-idle-thread speed was 76 seconds, and after the format it was down to 71 seconds. However, I ran an 'info 8', and the memory analysis hadn't changed at all (same 7 bad blocks). I'm not sure if the formatting (task 29 or this) is supposed to clear that up, though.
I put both the raphdiag.nbh and a raphimg.nbh on the root of my normal 16 gb card. When you go into bootloader, it does a quick image update (takes about 2 seconds), then the screen tells you to push power for a rom update or push the action button to go into diagnostics. From there, you have maybe 4 or 5 choices. Scroll up and down with the up/down buttons, then push action. The first is a set of hardware tests, the second is something like 'run in/on', which appears to be a test scheduler. The 3d is the NAND format option, and I think the 4th and 5th options are 'calculate rom checksum' and then 'skuid', or something like that. To exit, I just soft reset, or used soft reset/vol down to go back to bootloader. After the format, I tried to flash (I think it called it re-flash), but it said there was no image present. You may need to do this on a clean card to get it to work (that is, format and then flash off the same card without swapping things out).
The diag tests are kind of cool. There's an auto mode that runs through all of them, but you have to do things to get it to work. The first is an LED test. The screen turns red, you stare at it for 5 min wondering what the hell is going on, then push the action button for the hell of it. Then the screen turns green. Push it a bunch more times, and it goes through shaded and checkered screens and whatnot, then it tells you it passed the test. There's a test for the slider, and you need to slide the keyboard in and out. The qwerty test was weird. It's configured for a touch pro (not a fuze), so I didn't know what the hell to do at first. The screen just says 'QWERTY_KBD_1', or something like that. I tried hitting the '1' button, and fn-1, and it did nothing. Then I just hit the top left button, and it said OK and prompted to hit 2. So, you just push all the keyboard buttons from left to right, top to bottom. There are also tests for the other hardware buttons, except for the 4 main buttons on the d-pad (home, back, send, end), which was kind of weird. If you think your power button or vol down button is effed, this tool will confirm/deny it for you.

Right, so the RaphDiag didn't brick your device. It's a bit risky - so I will first resort to less extreme measures - at least I know there is one success story.

I seriously wouldn't worry about it, but you may want to have a card reader available in case you need to remove raphdiag from you sd card to get a flash to work. It's possible that I didn't get the nand format to work properly, but I think I did it right, because the device definitely needed to cold boot. I was just surprised that there was still an OS there.

I'll take your word for it - BUT - in terms of gaining knowledge I am going to try the steps in the posts I found. If the NAND does need a format there is no doubt that I will land up doing it - but I will have first-hand experience.
This really needs a Wiki page once I am done; so I want to squeeze as much info out of the device as I can.
Can anyone else think of any gotcha's before I potentially brick it?

I ran the format a second time. It's really fast; it takes maybe 5 seconds. I haven't figure out how to exit from that part of the diag other than soft resetting, which leads to a cold boot. I'm surprised it's so fast. A hard reset takes about 30 seconds. I guess that it's working properly.

Farmer Ted said:
I ran the format a second time.
Click to expand...
Click to collapse
You are either very brave or very rich . Right, so here is hoping I have to go the final resort route - nothing yet though.

G2x continuously rebooting the lg logo screen

My phone runs perfectly fine until I enable Gps location. Once I enable GPS location, it freezes, then it reboots my phone and it slowly do a system check, then it continuously rebooting the lg logo screen. I tried taking out the battery and put it back in, even took out my battery for a day and it still does the same. I'm not sure if it's the hardware problem, but it's a pretty rare case, since I read most of the threads in forums, people said it can be fix once you pull out the battery, but somehow it's not working for me. Anyone knows the reason why? Btw, my phone is not rooted or used any 3rd party program.

Ah. Posted too soon. There's a master reset that I believe is Power and Volume Up. Try that.

Unfortunately, it's still not working. Is there any other possible way? Or else I have to call in and return it.

Try turning off the phone, then press power + vol down and hold it until you see the word android. This should do the factory reset.

efrem989 said:
My phone runs perfectly fine until I enable Gps location. Once I enable GPS location, it freezes, then it reboots my phone and it slowly do a system check, then it continuously rebooting the lg logo screen. I tried taking out the battery and put it back in, even took out my battery for a day and it still does the same. I'm not sure if it's the hardware problem, but it's a pretty rare case, since I read most of the threads in forums, people said it can be fix once you pull out the battery, but somehow it's not working for me. Anyone knows the reason why? Btw, my phone is not rooted or used any 3rd party program.
Click to expand...
Click to collapse
It sounds like the permissions are not correct, or perhaps that your ROM was not flashed correctly. I have seem this problem happen numerous times due to bad firmware flashes or ROM issues. I would just download a new copy of the latest CM 7 ROM or whatever your favorite ROM is and flash it through CWM.

Thanks guys for the help. I found out that you have to hold down first then power button for around 30 second and then the droid animation comes out. I was so close to returning it. Thanks!