Hi Folks,
I plugged my device into Zune as per usual, was told there was an update ready so set the process in motion. The update b0rked half-way through, citing a connection error and left my device unusable.
I then had a read and downloaded one of the default ROM's from the dev thread and flashed it through the bootloader and the device fired back up and worked! Stupidly, I then allowed it to try and update again and the process repeated.
Now I can't seem to flash anything. I can get into the bootloader and start the process but it gets to a certain number (which depends on the ROM I'm trying to flash) then I get the 'Flash write error happened - please check your PDAphone' - or words to that effect.
I then have to pull the battery to even get the thing to fire up or do anything.
This has got me confused and enraged.
Has anyone got any words of wisdom to share?
Cheers
maybe goldcard?
but i think it's time to visit service centre
Thanks for the reply, mate.
The frustrating thing is that the flash worked originally, and I just can't understand why it won't work again in identical circumstances.
I need a Y cable for the gold card solution, right?
Sent from my HTC Desire S using XDA App
Just as quickly as it started behaving like a f***er it's now sorted itself out.
I tried running a flash when I got in this afternoon and it worked fine! The poxy thing is now running as you'd expect.
I'm a bit wary of updating though, after the last two efforts. Any suggestions on how to avoid the dreaded 'interrupted connection' error?
Tried the update from a different PC with a different (HTC branded) USB lead and the same thing happened as before.
Now I'm stuck again, not getting past 10% with the reflash.
****e.
Sent from my HTC Desire S using XDA App
Hi guys need help!!! Just bought a used m7 was ok when i took it decided to clean when i powered it up it shows the normal white screen with htc but after that it shows on screen a ph n indication of connecting to pc and does not boot up what do i ve to do? Thanks for any assists
Sent from my LG-P500 using xda premium
I'd try starting your own thread, mate, with as much information as you can dredge up in the title and description.
Thanks will do that
Sent from my LG-P500 using xda premium
I finally managed to flash the default operator ROM, after 15-20 attempts. The device is now working and it's going back to the service centre for updating!
Related
Hey guys,
Hoping someone can help out here, although I'm guessing I will need to do this: http://forum.xda-developers.com/showthread.php?t=991072
My phone has been prompting for the last 36 hours or so to do the OTA update which I had been putting off due to wanting to retain root (done with SuperOneClick) and not having time to follow the instructions for that. I had wireless turned off last night, and this morning when I turned it back on it downloaded the update without asking, but still asked before attempting to install. It's been asking me every hour since and I've said 'Later' every time.
Anyway, I stepped away from my desk for half an hour at work this afternoon and came back to find my device boot-looping. I don't expect anyone at work would have touched it, I just don't know what led up to this behaviour. I get the Motorola animation, then the AT&T "Rethink Possible" animation, and then the screen goes blank and the LED blinks red about 120 times at about 3 times the speed of a normal notification and then it starts over again.
The only reason I'm concerned about doing the SBF flash is that this is a SIM-Unlocked device on Telstra network in Australia and I really don't want to loose wifi functionality. Other than that I'm quite comfortable doing so. The phone had only been rooted, I hadn't done the deodex ROM or any mods.
Does anyone have any suggestions?
WheelieBin said:
Hey guys,
Hoping someone can help out here, although I'm guessing I will need to do this: http://forum.xda-developers.com/showthread.php?t=991072
My phone has been prompting for the last 36 hours or so to do the OTA update which I had been putting off due to wanting to retain root (done with SuperOneClick) and not having time to follow the instructions for that. I had wireless turned off last night, and this morning when I turned it back on it downloaded the update without asking, but still asked before attempting to install. It's been asking me every hour since and I've said 'Later' every time.
Anyway, I stepped away from my desk for half an hour at work this afternoon and came back to find my device boot-looping. I don't expect anyone at work would have touched it, I just don't know what led up to this behaviour. I get the Motorola animation, then the AT&T "Rethink Possible" animation, and then the screen goes blank and the LED blinks red about 120 times at about 3 times the speed of a normal notification and then it starts over again.
The only reason I'm concerned about doing the SBF flash is that this is a SIM-Unlocked device on Telstra network in Australia and I really don't want to loose wifi functionality. Other than that I'm quite comfortable doing so. The phone had only been rooted, I hadn't done the deodex ROM or any mods.
Does anyone have any suggestions?
Click to expand...
Click to collapse
Seems like if it did try to install it failed somewhere not allowing for full boot... have you tried pulling the battery also try and find out if it is running 1.5.7 also try booting in recovery and factory reseting. And also don't you only lose wifi when flashing 1.5.2? I might bw wrong about that though
Sent from my MB860 using XDA Premium App
drock212 said:
Seems like if it did try to install it failed somewhere not allowing for full boot... have you tried pulling the battery also try and find out if it is running 1.5.7 also try booting in recovery and factory reseting. And also don't you only lose wifi when flashing 1.5.2? I might bw wrong about that though
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Sorry, I should have specified... yes, I have pulled battery - issue persists. I hadn't gone as far as a factory reset, but it's definitely less dramatic than a reflashing, so trying that now...
OK, factory reset seems to have done the trick - it was still on 1.2.6, I'll do the update to 1.5.7 with the v2 Root Process now and see how I go.
WheelieBin said:
OK, factory reset seems to have done the trick - it was still on 1.2.6, I'll do the update to 1.5.7 with the v2 Root Process now and see how I go.
Click to expand...
Click to collapse
Congrats friend! Glad to hear you're out of that boot loop.
Sent from my MB860 using XDA Premium App
first i wanna thank you guys for this awesome forum
i have an AT&T aria phone that randomly reboots
LIBERTY PVT SHIP S-OFF
HBOOT-1.02.0000
MICROP-831b
TOUCH panel-stn21_03
radio-7.16.35.11
Nov 4 2010
the phone is rooted with CWM v2.5.0.1 istalled.
i flashed the original ATT rom 2.2 from HTC website and it didnt fix it
i flashed shipped att rom and it didnt fix.. also flashed rooted rom yet no luck
1-i tried to unlock the bootloader with HTCDEV.COM but it gives me error message
fastboot oem get_identifier_token
...INFO[err] command error
2-i tried to use the revolutianary website and no luck either
3-i tried to put the original img on the sd card LIBEIMG.zip and booted into bootloader but the phone didnt recognize the file at all.
i am a newbie in the android word but i can swear i did every thing by the book in these last 3 steps** at least as i could understand**
p.s: i dont know wut or who did this to this phone
This is sort of a long shot, but did you happen to install a 32GB SD card around the time the problem started happening?
If not, did you change ANYTHING else? new SIM card? new charger? etc.
nope i did not install 32 GB card..
i dont know exactly what happened to this phone.. i took it AS IS..
when i first got the phone it had the original at&t 2.2 stock S-off ... i was lucky to flash CWM using fastboot..
i think if i can install HBOOT again and turn S on this might solve the problem... or may be i need to do something to the partitions but as i told u im a newbie in here
i am sure it is a software problem due to the error message i get when i try to unlock the bootloader...
I tried everything: stock AT&T Froyo rom, returned to S-on, new sd card, new sim card. Also returned to HTC for "repair," but it still rebooted so I returned to HTC for another try.
BTW, I used the Unrevoked method to root/S-off the phone, and the S-on method listed in the development forum to take the phone back to stock. Both with no problem (several times). The S-on was a little trickie, had to load stock AT&T rom, then follow the S-on instructions, which includes loading the stock AT&T Froyo rom again.
I'll report the results of my 2nd HTC repair on the 2 Arias reboot problem thread.
Sent from my MB860 using XDA
i am trying to install HBOOT 1.03 but no luck.. i think if there is a way to reflash the hboot this would solve the problem
gdjy said:
i am trying to install HBOOT 1.03 but no luck.. i think if there is a way to reflash the hboot this would solve the problem
Click to expand...
Click to collapse
Don't try to do that. HBOOT 1.03 will not fix your problem, it'll only make it worse (not being able to easily S-OFF). You should avoid HTC's official bootloader unlocking method -- it's worse than Revolutionary.
thank u drumist...
i tried already but no luck.. it says device ID error..
i am so desperate in here.. is there anyway i can fix this aria??
To my surprise I had called HTC and found out that my phone was still under warranty. As I said above, the phone is now back at HTC for a 2nd try. I will let you know what they found as soon as I get the phone back -- it took about a week last time.
Drumist was very supportive in my effort to find the problem, and against his advice and out of desperation, I did restore the HBOOT, and, as he said above, it did not solve the problem. The phone was back to being completely stock -- ATT Froyo 2.2 and S-ON -- and it sill had random reboots --taking anywhere from 1 minute to almost an hour before rebooting. Which is really annoying when trying to troubleshoot. I even re-rooted and S-Off'd the phone using Revolutionary, and still had the problem. I then returned the phone to stock again prior to sending it to HTC for repair. Checked one more time... still random rebooting. As I am now using another phone -- Atrix 4G -- solving this has become more of a challenge.
The other thing that's amazing is that I have 2 ATT Arias with exactly the same problem!
I wonder if it is a location thing. You don't happen to reside in SE Pennsylvania do you?
the same thing has been happening to me. it just started happening recently.
about 10-20 times a day the phone just buzzes and goes straight to the white HTC turning on background.
it's very annoying.
charbo187 said:
the same thing has been happening to me. it just started happening recently.
about 10-20 times a day the phone just buzzes and goes straight to the white HTC turning on background.
it's very annoying.
Click to expand...
Click to collapse
I have to agree with you, it is really annoying. Luckily I dont use my phone very often. I dont think it is location based, as I'm in eastern Iowa.
Ok. Just got my Aria back from HTC after their 2nd attempt at at fixing the random reboot problem. It rebooted within 5 minutes of turning it on! And twice after that.
The only thing I did was put in the battery. No SD or SIM card, and I did not plug in a battery charger. I didn't even have a chance to connect to my wifi.
I will call HTC tomorrow and anticipate sending it back to HTC for a 3rd try.
I really thought they would send me a new phone after the 2nd attempt at fixing it. Although now I'm really curious about what could be causing this.
It's interesting that that there are more reports about this problem. I had rooted and installed multiple roms before restoring it to stock AT&T Froyo prior to returning it to HTC for repair. Has anyone had this random reboot problem on a phone that was never rooted?
Oh well. I will probably be sending it back to HTC tomorrow, and will keep you posted about the results.
Sent from my MB860 using XDA
I am having the same issues...luckily I now have the HTC One X, however I do still use the Aria as a dedicated GPS, which is frustrating having CONSTANT reboots.
This also only happened recently...I wonder what the issue could be...
Reboot saga
Just spoke to HTC about their failed 2nd attempt to repair my phone. They told me the repair records state that they replaced the "main board," which I assume is like the mother board.
If that is true, I would assume that would be like getting a new phone. If that doesn't fix it, I am truly baffled. The ONLY thing I did was put the old fully charged battery in the phone to test it -- without a SIM or SD card . Could the problem be related to the battery? Since I have another Aria (with its own battery) with the same problem, I doubt it.
Regardless, HTC is having me send it back for a 3rd try to fix it, and they sent me a prepaid shipping label this time.
They said if the 3rd repair attempt doesn't fix it, they would send it to a higher level repair facility for a 4th try! I can't complain about HTC's commitment to trying to repair my phone.
From the responses on this thread, this has become a recent problem. Mine started about a month ago. Any theories out there?
Thanks for sharing your experiences yar, however I'll be dealing with the reboots cause I cant go that long without my phone.
Another thought I had while driving yesterday, Do your guy's that reboots, happen usually after you press the lock button? I've noticed after I send a text message and I hit the lock button is mostly when it will restart. Anyone think it would be that button causing the problem or maybe the HTC Sense Lockscreen?
While I'm waiting for HTC to return my phone after their 3rd attempt to fix this problem I have been experimenting with my other Aria.
I booted into CWM and left it there for over an hour and the phone did not reboot. Does this helps isolate the problem?
Also, has anyone managed to stop a random reboot problem?
Sent from my MB860 using XDA
Just got my Aria back from HTC after their 3rd attempt, and it rebooted within 10 minutes. I even used a new battery, thinking that somehow that was causing the problem. No sim or sd card, and I did not even log onto wifi. They claim they replaced the "main board." Its hard to believe they actually tested it.
Probably beating a dead horse, but I will take HTC up on their offer to send it to the next level of service for a 4th try at fixing the problem. Can't believe it wouldn't be more cost effective to just send me a new phone at this point... but then there might not be any new Arias available.
Sent from my MB860 using XDA
try setting the Aria data comm to Edge only
I've been following this thread with interest since I have an Aria with AT&T "service" and have been experiencing the random reset problems described here. I have not rooted the phone and have the stock 2.2.2 release side loaded through HTC Sync. After several attempts to isolate the problem, I think I may have stumbled across something that works (so far, no reboots in the last 11 hours, but, that is not conclusive evidence yet). Try using the "hidden test feature" by entering *#*#4636#*#* on the dialer keypad. Then under the "Phone information" section select "GSM only". I understand that this forces the phone to use only the Edge data format.
I think there may be a problem with the Aria's firmware that communicates with the 3G network. I was able to use 3G successfully in the past year, but, something must have changed recently in the way AT&T configured this network or at least I suspect that a recent network change has caused these problems with our phones. You would think that AT&T and HTC would be aware of such a problem by now since I imagine many of us are affected. I'm leaving my phone on Edge until I see evidence that the problem has been resolved.
RWB Jr said:
I've been following this thread with interest since I have an Aria with AT&T "service" and have been experiencing the random reset problems described here. I have not rooted the phone and have the stock 2.2.2 release side loaded through HTC Sync. After several attempts to isolate the problem, I think I may have stumbled across something that works (so far, no reboots in the last 11 hours, but, that is not conclusive evidence yet). Try using the "hidden test feature" by entering *#*#4636#*#* on the dialer keypad. Then under the "Phone information" section select "GSM only". I understand that this forces the phone to use only the Edge data format.
I think there may be a problem with the Aria's firmware that communicates with the 3G network. I was able to use 3G successfully in the past year, but, something must have changed recently in the way AT&T configured this network or at least I suspect that a recent network change has caused these problems with our phones. You would think that AT&T and HTC would be aware of such a problem by now since I imagine many of us are affected. I'm leaving my phone on Edge until I see evidence that the problem has been resolved.
Click to expand...
Click to collapse
I will have to give this a try, as for HTC and ATT knowing, they probably don't care and I dont really blame them this is a 2 year old phone.
Hello,
I having big problem on my Atrix. Out of nowhere he stopped working, I've tried everything - taking out the battery (which had 40% when it happened), sim card, connecting to original wall charger. Nothing. I'm pressing the power on button and it doesn't turn on.
:crying:
If anybody have any idea, I begging you to help me.
Thank you and good day.
P.S. I forgot to mention that the phone is with me only a month, worked perfectly
Hello again,
I would like to add something that I noticed about the phone and maybe someone could use it to get ahold of the problem. Every now and then (few hours mostly but sometimes minutes) the phone turn on, get past the boot sequence but then get stuck and shut off again.
Last time I connected the phone to the pc, the pc recognize that there is a device but not past MOT ADB device to the MB860 like it did before. This time it got stuck in the "UNLOCKED" screen and shut off again.
I will be hugely thankful for someone who can point to the problem and even find way to fix the problem.
Did you install any custom rom?
Sent from my GT-S5570 using xda app-developers app
Yes, Jokersax cm10 rom.
Luckily the phone resumed to work but I'm scared to **** it will happen
do you have ATT or INTL Atrix?
Same thing happened to me..few months ago when trying to flash nutrino..dont worry it is software related..i tried everything. but oneday it started working again out of nowhere
Sent from my MB860 using xda app-developers app
I have a tablet NaviaTec, running ICS. Google doesn't help, because this tablet is not so popular cuz it's very cheap. Sometimes when I charge it overnight, in the morning I get Encryption unsuccessful screen. I read 5-6 different threads but all are different methods for different devices. This has been happening for almost a month, couple times a week.
Have you attempted in the past to see if encryption is on under security settings ?
Sent from my HTC Vision using xda app-developers app
No it's not, I will encrypt it then respond if something happens. Thanks
Couldn't even encrypt it. I get stuck on Andy the Android screen. Doesn't move from there.
Oh sorry, didn't read that it would take more than hour. heh, will try again.
OK, bump first of all
Secondly, I tried to encrypt it, it took whole night + 12h, then I came home from school and saw Encryption unsuccessful message. Any help?
Hey. I guess the last thing to try is to at least do a factory reset. Since this is not a well known manufacturer i really dont know what else to do
Sent from my HTC Vision using xda app-developers app
sorry my english is not good
My stock, never-rooted GT-I9300 (4.1.2, I9300BWELK1, JZO54K.I9300XXEMC2) is plagued by boot loop problems. It first started about 3 months ago, where the blue charge LED would suddenly come on and the phone would not wake from sleep. I pulled the battery, then when it was turned on it showed the initial S III logo, then the O2 logo followed by the glowing Samsung logo. Then repeated from the O2 logo endlessly. I pulled the battery again, then the next morning restarted it without the SIM or SD card in, and it had done a partial factory reset - i.e. lots of phone contacts were there with the texts, but all the settings had reverted to default. Later that day while on charge the same thing happened again, and I sent it away to O2 for repair.
When it returned, the same thing happened 6 weeks later although this time it was on when it froze and went straight to the O2/blue LED stage. Another repair (I'm fairly sure these 'repairs' were just factory resets...), and 6 weeks later exactly the same. Back to the O2 shop for another repair.
This time they replaced the 'main board' and when it came back it had a different Wi-Fi MAC address. This time only 6 days elapsed before the same fault arose again, and finally I was eligible for a replacement handset. This lasted 2 days before a boot loop condition occurred again! This time, being sure it couldn't be a hardware fault I tried my own /data and /cache wipe, which worked. I skipped all but the must-have apps, and I thought this was going to be stable but once more this past weekend the boot loop happened again (I've got my restoration procedure down to about 15 minutes thanks to the practice!)
I don't know what could be causing this and I'm fed up with resetting my phone. Are all S IIIs this unstable? I've never had a phone that required a factory reset within 18 months! When it is in the boot loop, I can access recovery and download modes, but safe-mode start-up has no effect.
The last remaining candidates I can think of are a problem with my SIM card, or a defect with my SD card... or an app. Can anyone suggest the best way to troubleshoot this? I'd really really rather not have to skip importing my settings as I have among other things many SSIDs I don't easily have access to re-create.
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
What ROM are you on? 4.1.2?
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
kernalk said:
Yes, 4.1.2. I don't recall this behaviour before I got the OTA update from 4.1.1 though
Click to expand...
Click to collapse
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Skander1998 said:
No, not all S3 owners experience this, a factory reset solves most of these issues however, if it doesn't, a trip to the Samsung service center will help.
I'd say it's probably a dodgy app, or some kind of unstable firmware update for your region/carrier, since hardware replacements didn't help with it.
Click to expand...
Click to collapse
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
kernalk said:
Hmm. Thanks for the reply. I'm not sure I know anyone else with and S III on O2-UK but it seems to be news to O2, so I assumed it must be fairly rare.
I'm not sure about dodgy apps; testing them one app at a time isn't really feasible as it can take up to 6 or 7 weeks to fail judging by past performance. Are there any logs or similar that I can pull out somehow in the event of a boot loop? I've seen about logcats but I am not sure if this would be of use
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Everything to carries is "news".
I can't help with logs and whatnot, so I'll leave that to someone else.
You can always flash and downgrade to the older firmware that didn't give you a problem, if the problem persists, it is indeed an app.
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Even when rooted, informative logs are nigh on impossible to get
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
That doesn't fill me with confidence!
Thanks again for the replies. I'm not wild about downgrading. I liked the improvements! Is it possible to downgrade in a carrier supported way? Retaining warranty compliant has been rather useful in the past few months!
Sent from my GT-I9300 using xda app-developers app
You can flash any official via odin.
Sent from my GT-I9300 using Tapatalk 4
Well late Friday night it did it again. Not sure when exactly as I was asleep. Woke up in the middle of the night and went to check the time, Looked at my phone to find the blue LED on when it should have been red for charging or green for fully charged, and it was very hot - wouldn't turn on either. Pulled the battery but it kust went into the loop. I was away from home so I couldn't do any troubleshooting and had no choice but to wipe.
This time I didn't restore settings and the only apps I installed were SMS Backup & Restore and Puzzle Alarm (I know this isn't the culprit as I only started using it this week!). Gone are all my precious wifi SSIDs but otherwise I'm not sure I've noticed the difference.
So I'm now not connected to my work wifi, nor have I set up my work email or Lync - two of the things I use my phone for must after Facebook which I've also not reinstalled. Facebook mobile web is really hard to use by comparison.
By chance I popped into the O2 shop later that day and had the fortune to bump into a Samsung rep who had never heard of this and agreed that I was unfortunate to have these problems (how touching!) and suggested I speak directly to Samsung support rather than O2 which I will do this week. I will also contact O2 about a replacement SIM and look into replacing the SD too.
This is really silly. I'm not keen on downgrading the software because the first thing either Samsung or O2 will do is upgrade it again. Frankly at this point I'm fed up with the whole thing but I've got a year left on the contract and even a pretty much new handset like mine won't fetch enough.