Related
I recently had a problem with my XDA 1. It started running VERY VERY slowly (kind of like a computer that was infected with 10000 spyware programs). The battery was constantly showing that it was going to shutdown but yet seemed to still operate.
I tried doing a backup to SD Card while it was on the cradle, yet after about 4 minutes of usage it would automatically soft reset - interrupting the backup.
So i thought stuff it, i don't care about the data i will just do a hard reset. Now, after doing the hard reset i can't even get it to turn on. The O2 Screen comes up and the light flashes on and off every few seconds. It does this for about 45 seconds then switches off again.
Does it sound like the mainboard is gone? Could it just be the battery? Are there any home repairs ideas? I do have a second xda i can pull apart if i must to test what is wrong with this one.
Thanks.
Adrian
boot problem
if a desktop pc were to exhibit these sort of problems then i would definitely suspect a motherboard problem. if you are still under warranty then straight back to the store is the place for you. if not then scour the forums for solutions fixes or suggestions, there are some very experienced people on here - not me -
ian
since it's still under warrenty I strongly advice to replace it or at least to get it repaired by the center ... but if you tend to feel it's a challenge for you to fix it your self, then you may do the following to eleminate the possibility of S/W problem ...
1. Flash the ROM with a new OS image. This should solve any ROM problem.
2. Make sure you didn't turn on the "Calib/Debug" option in the GSM menu of the boot loader.
BTW, was the radio part OK while having this problem ?
actually its not under warranty, i bought it off a friend when he upgraded to his XDA II. Im not sure what the radio version was, i jsut put any details in there because i couldnt boot to find out what it was at.
Can you flash the rom without having to boot it up? Are there the instructions on how to do it on this site?
Thanks.
Hi.
I just got my p500 that went to repair( i bricked the phone) and they fixed it and updated to 2.2.2 but im having some issues.
The phone doesn't turn off the screen, even tough its set'd up to and i have to lock it in order to turn off the screen and sometimes just turn back on even without a text or call and i have to again lock it. Other problem is that the phone does not recognize that it's connected to the pc by usb.
I already tried do a reset by restoring the factory settings but it didn't solve anything.
Does anyone know how to fix this? I didn't want to sent it back to repair because it took a long time for they to fix it.
Thanks
All p500 tht was repaired by service hav this prob, I think its due to faulty motherboarf tht they using.
So that means that i will have to send it back =/ Theres really nothing i can do? I even thought it was all software related and if i flash the phone with the 2.2.2 room (im afraid that downgrading the room will brick the phone) but i don't know if this is possible to do with 2.2.2 and because i haven't found how to root this version.
I had the same problem too after get back my O1 from warranty, really feel disappointed with the service.
Anybody can help except sending back to that stupid service centre ?
Did yours took too long to? Mine took almost a month to get back from repair and it came with all this problems.
Im disapointed with the service too.
You should hav been careful in the first place.
Its a dead end now.
I don't see how its a dead end now.
I should have been careful at the first time while was trying different rooms with different methods and that's why the phone died. I sent it to repair and they replaced the motherboard from what i understood. So if it a new motherboard and i havent change anything since and im having these problems i don't see it as a dead end but as a responsibility from lg or the company that repaired the phone and my provider to repair ir. So maybe the first time since it was my fault it would be my responsibility , but they didn't question that and i didn't say anything. After they repair it but with a malfunctioning piece it's their responsibility to fix it. At least that is how i see it.
Im going to have to sent it back to warranty to repair and i hope it doesn't come with the same problems again.
Ok its not a dead end oO''
I understand ur rage... But I jst warning other users to take precautions while messing with the phone. Or they wud also qq over a bricked box..
Gudluck with the service..
Cheers.
Thanks.
I subscribe your adivce.
I have been thinking of reinstall the firmware(the original from lg) to see if it solves the problem, but im having a issue. I can't connect the phone to the computer(only transferring things to the sd card and install or open from there) and i don't know if i can root it with this version i have now, 2.2.2.
Does anyone know how can i do this with the android version and without connecting it to the pc?
PROBLEM SOLVED
I was planing on sending the phone to repair on monday, but at the time and with the phone here i didn't want to give up so i thought of rooting it and reinstalling the firmware, but nothing worked and the phone didn't recognize that it was connected to a computer. So i kept search other ways to reinstall the firmware and came across a website that talked about a "secret menu" code for the phones and i remembered that this phones must had one and that from there i could do something, i did. From there i did a factory reset and, unlike the ones i did before by going to settings-privacy, when the phone rebooted it told me right way that it was connected to the computer. I also tested the problem with the screen light and so far, so good.
So, if anyone else has this problem(sannielyk reportedly had) what i did was entering the "secret menu" code : 3845#*500# and did the factory reset from there.
Apparently it was a software problem or something that wasn't installed right by the lg service. But so far everything is good, and i hope it keeps that away.
Thanks for the help
Edit the title as [solved].
Goodjob bro.
Cheers.
Done.
Thanks
Thx a lot to griffin_1.
I tried ur "secret menu code" to reset the phone & it is really work , now problem solved.
No need to waste time back to the lg centre.
You're welcome. Glad i could help and that sending the phone to lg could be avoided in this situation.
Oh man you saved my life. I don't know how to thank you. Thanks, thanks, thanks a lot, it really worked.
Thanks griffin_1.
I had the same problem and i was going to send it back to LG service. but ive fixed it with the secret code . Thanks again.
hey people i did send my lg p500 to repair becouse something went wrong the change my mainboard and the ime well done , then i got the 2.2.1 as stock rom
good then i did upgrade to Noijins megatron then the problem starts sometimes
if i just use power amp and want to go to the facebook app the phone simply start blinking the buttons like u would overclock your phone.
then it just reboot from alone i think i got the problem 4 or 5 times a day and i simply start beliving that maybe the gprs or the module might be done for the internet.
so i think should i send it to the repair again ? i even try to flash my baseband
same error at the new roms.
i hope you can help me griffin
got the same trouble like u since lg change my motherboard.
griffin_1 said:
PROBLEM SOLVED
I was planing on sending the phone to repair on monday, but at the time and with the phone here i didn't want to give up so i thought of rooting it and reinstalling the firmware, but nothing worked and the phone didn't recognize that it was connected to a computer. So i kept search other ways to reinstall the firmware and came across a website that talked about a "secret menu" code for the phones and i remembered that this phones must had one and that from there i could do something, i did. From there i did a factory reset and, unlike the ones i did before by going to settings-privacy, when the phone rebooted it told me right way that it was connected to the computer. I also tested the problem with the screen light and so far, so good.
So, if anyone else has this problem(sannielyk reportedly had) what i did was entering the "secret menu" code : 3845#*500# and did the factory reset from there.
Apparently it was a software problem or something that wasn't installed right by the lg service. But so far everything is good, and i hope it keeps that away.
Thanks for the help
Click to expand...
Click to collapse
try this
zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
Please forgive me for the long arse post, details are sometimes a good thing. At this point Im positive I have techherpes. I got a bad Modem last week and on the same day this. Last week I got the test letting me know ICS was available for my note so I followed all directions and downloaded Kies, after 4 attempts finally got a good DL. During the ICS update I got an error and was prompted to use the recovery feature. No dice on recovery so I took the phone to the ATT service center and they set up a return. I got my new phone on Friday and call Sumsung support to get a walk through. The tech said it would be advisable to wait until today before trying the upgrade which I did. I tried it again and the end result was the same as the first. I don't consider myself a technology dullard, hell its what I do for a living but I'm obviously doing something wrong?
At this point I still have the original phone in the return box waiting to be shipped and another phone showing:
ODIN MODE
PRODUCT NAME: SGH-i717
CUSTOMER BINARY DOWNLOAD: NO
CURRENT BINARY SAMSUNG OFFICIAL
Below that is a pic of a phone, yield sign, pc
Firmware upgrade encountered and issue. Please select the recovery mode in Kies and try again.
I spoke with another Samsung tech tonight who tried to walk me through a factory reset, vol up+down+power which brings me back to the same screen above briefly flashing the Samsung logo. She went ahead and setup a RMA and told me that it would be 5-7 days plus shipping. I said hell I'm in Austin can I drive up and have you fix it I can do the vol down+power buttons which will take me to the screen letting me know a custom OS will cause critical problems bla bla blah and when I press the up vol button I go back to the ODIN MODE screen.
Should I simply take it back to the ATT service center again, not sure they will be so accommodating since I have been down this road once already. Ive only had the original phone for just over a month and I have the insurance plan through them. All data was backed up before both attempts.
Maybe you got a bad Kies download. It's my impression it's a little squirrely, from my own experience and reading of others'. Why don't you remove and reinstall it. It seems unlikely that you got 2 bad brand new phones.
That is very possible. I had to DL it 4 times before I finally got a DL that would complete. Ill go that route and see what I can do. Does the current status of the phone mean that its bricked?
Thanks,
Chris
I don't know much about that, but I think it would be pretty bad to be able to brick a phone that easily following manufacturer's directions. In Kies there is an option for something like an emergency firmware fix, in case you need to try that. But I'd go the normal route first. I had some trouble with mine when I did the download, and had to try more than once. The download took forever, and I understand the servers were swamped when AT&T put out the notice. Also had to disconnect the phone and try more than once, but in the end everything was fine. Good luck.
kat3k said:
I don't know much about that, but I think it would be pretty bad to be able to brick a phone that easily following manufacturer's directions. In Kies there is an option for something like an emergency firmware fix, in case you need to try that. But I'd go the normal route first. I had some trouble with mine when I did the download, and had to try more than once. The download took forever, and I understand the servers were swamped when AT&T put out the notice. Also had to disconnect the phone and try more than once, but in the end everything was fine. Good luck.
Click to expand...
Click to collapse
Yep, I tried the night I got the text and the first DL took 45 minutes with a 30mb connection. When I tried the installer it failed so I wiped it and tried again. After 4 similar attempts all taking the same amount of time to DL I finally got one that launched. The result was where Im at now with the first phone. Fortunately ATT had me one the next day and I was able to restore. I called Samsung support and the tech told me to wait until Sunday or Monday before I tried it again since Kies would be going down Sat night.
I wiped Kies and installed it this am, 3 minutes to DL and it launched the hotfix. It seems to have gone through several more steps this time so I think I know where the issue was, or at least I wont blame myself 100% for now. When I removed Kies it appears to have also removed my backups? I did another backup using two other software options just to be safe.
When I connected the phone after the new install Kies wont connect to it. I previously tried the emergency recovery since the phone directed me to go this route with no success. Im off to the ATT service center in a few and Ill see if they will go the extra mile again.
Kies wouldn't connect to my phone either at time of update, so I ended up going through the Emergency Firmware Recovery which worked. Then I had to restore my backup. I'd try that again if I were you.
Refs. rehistr
Took the phone into the ATT service center today and as soon as they looked at me they said ICS failed? They told me that their entire day had been spent on skyrockets and notes. They weren't able to correct mine so they are sending me another. I wont be attempting the update on this one for awhile. It would be nice if the replacements came with ICS so that I didn't have to worry about it. I tried the emergency firmware update which would get to 27% and also fail.
just root your phone, no more worries about bricking
Hi guys! First off, I know this sounds like a common problem, but I've looked through several times and haven't found a solution yet.
I have a SGS2, came as 2.3.3 stock but upgraded a while back to 2.3.5 through Kies. It was working perfectly for as long as I remember.
About a month ago the battery started acting weird going from 80% to 20% in no time, heating up too, I do remember dropping the phone once during this period, but it was nothing (just thought I should include this, also, I usually leave the phone plugged into the charger overnight as I do not have a power source at work (i work outdoors) i probably need a battery replacement)
The screen brightness would sometimes flicker and then POOF! The phone shuts off...At first this would happen at any activity, nothing specific, BUT, I have noticed that it intensifies with the Facebook app.
Anyways, usually plugging the phone back into the charger and powering it up would bring it back online, but not this time. It would get stuck looping the animation of the 'S' at the beginning and no booting up. I have a valid warranty card which I'm guessing will get the phone either fixed or replaced but I need help to try to salvage whatever info I can get my hands on, preferably everything, but my memos are most important to me.
Thanks for the help!
sherief87 said:
Hi guys! First off, I know this sounds like a common problem, but I've looked through several times and haven't found a solution yet.
I have a SGS2, came as 2.3.3 stock but upgraded a while back to 2.3.5 through Kies. It was working perfectly for as long as I remember.
About a month ago the battery started acting weird going from 80% to 20% in no time, heating up too, I do remember dropping the phone once during this period, but it was nothing (just thought I should include this, also, I usually leave the phone plugged into the charger overnight as I do not have a power source at work (i work outdoors) i probably need a battery replacement)
The screen brightness would sometimes flicker and then POOF! The phone shuts off...At first this would happen at any activity, nothing specific, BUT, I have noticed that it intensifies with the Facebook app.
Anyways, usually plugging the phone back into the charger and powering it up would bring it back online, but not this time. It would get stuck looping the animation of the 'S' at the beginning and no booting up. I have a valid warranty card which I'm guessing will get the phone either fixed or replaced but I need help to try to salvage whatever info I can get my hands on, preferably everything, but my memos are most important to me.
Thanks for the help!
Click to expand...
Click to collapse
are u rooted
try flashing the stock rom again and check if u face the same issue
I'm not rooted. I tried doing that using odin and got the stock firmware from sammobile. same thing happens, stuck at the boot.
a friend suggested i try to flash the stock ICS version, same thing.
sherief87 said:
I'm not rooted. I tried doing that using odin and got the stock firmware from sammobile. same thing happens, stuck at the boot.
a friend suggested i try to flash the stock ICS version, same thing.
Click to expand...
Click to collapse
Weird. It shouldn't boot loop. You sure your version is GT-I9100 and not GT-I9100G? Since I'm in Riyadh, the latest version for GB here (Saudi Arabia) was JPKJ2, but that's for GT-I9100, dunno about the G version.
Sent from my GT-I9100 using Tapatalk 2
okay so with the help of a friend and this awesome forum, i managed to install cwm, from there i could take a nandroid backup, but i cant mount the phone as a drive or anything to copy the files, and i'm guessing i cant use this backup i just took to restore later because it'll just get me stuck at the same place im at now
i read that i can use unyaffs to extract files from the resultant backup image, so my question is, before i do a wipe, is there any other method through which i could get a backup of my stuff? the things i would very much like to get a copy off are my messages/notes/whatsapp history and pretty much anything really
thanks for the help!
First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months. I haven't installed any new apps in a few weeks, but my phone has been doing any regular updates. Today, my phone completely locked up about 5 separate times (about 2-3 hours apart for each). Each time, the only way to get my phone back was by pulling the battery (even the 10+ second press of the power button didn't work)... annoying, but manageable.
After the last lock up, my phone got stuck on the SAMSUNG logo (not the S-III logo). I let it sit there for about 45 minutes, and it was pulsing the entire time. Finally, I gave up and pulled the battery one more time. After putting it back in, the phone gets to the S-III logo, but the S is not pulsing. I've let it sit on that for over an hour - with no luck.
The failed root threads all suggest installing ODIN, rooting, wiping everything, then installing a stock firmware. I'm really hoping there is something else I can try, since wiping my phone would be extremely painful at the moment...
Anyone have any ideas?
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Sadly as this may be, mine derped out exactly like yours one week after I bought it. It would randomly reboot, lag a lot until the day I woke up to that brilliant Samsung boot screen and nothing more helped.
Had not done anything to it so I returned it for a replacement. Turns out I had a faulty unit.
Sorry bro, guessing it's the only thing that will get yours sorted again. While I know in every product there will always be faulty units, I'm seeing dead sgs3 threads very frequently, I'm guessing Samsung's build quality isn't that good...
Sent from my GT-I9300 using XDA Premium App
It might be worth remembering ...
shaunco said:
First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months.
...
Click to expand...
Click to collapse
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
JJEgan said:
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Click to expand...
Click to collapse
I would love to backup my data, but since I had a stock bootloader (not CWM or one of the others) and the PIT seems gone, I'm SOL.
xclub_101 said:
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
Click to expand...
Click to collapse
Yeah, bad wording on my part. When I bought it (the first day Amazon sold the I9300), it had 4.0.4. It has had 4.1.1 since mid-October. My comment of it "working great" was in relation to the random lockups (and now the stuck at logo issue).
Lucky for me, the phone is a work phone, so I bought a new I9300 at Fry's this morning and at least got my service and all my apps back, along with the data for the apps that were nice enough to put it on the SD...
This means my focus has shifted from returning my old I9300 to a working state to simply getting data off of it. If the bootloader shows "no product", it seems that the partition table is shot. Loading a new partition table would destroy the underlying data... so, is there anything I can do (even things that are physically destructive to the phone) to get the data (even as a single binary blob) off the internal 16GB storage?
As I said, I'm happy to rip this thing to pieces, if there is a way.