Jump to content

Constant reboots


Recommended Posts

Guest Lord_Shaithis
Posted

I have been thinking my reboots were all caused by the various 2.1/2.2 roms floating around as they only happened after installing the hungarian rom and got better/worse with each install of another different rom....culminating in installing the 2.2 update which seems to have caused it to be a constant feature...

So, in trying to fix the issue I have tried going back to 1.5 official......after a nightmare of getting the touchscreen working (had to use that tiny 300k update that seems to blast a lot of settings/data), I have successfully re-loaded the 1.5 dec update and have a working touchscreen......but the reboots are still there :S

The reboots can happen as a boot-loop or at any time from the moment the OS has loaded, no pattern to them at all, except they happen extremely frequently...

Is this a general known problem that the phones can develop or could there still be something lurking deep in the phone causing it?

2 months left on guaranty and still not seen a replacement I am entirely happy with, oh the dilemmas :)

Guest Richard_Arkless
Posted
I have been thinking my reboots were all caused by the various 2.1/2.2 roms floating around as they only happened after installing the hungarian rom and got better/worse with each install of another different rom....culminating in installing the 2.2 update which seems to have caused it to be a constant feature...

So, in trying to fix the issue I have tried going back to 1.5 official......after a nightmare of getting the touchscreen working (had to use that tiny 300k update that seems to blast a lot of settings/data), I have successfully re-loaded the 1.5 dec update and have a working touchscreen......but the reboots are still there :S

The reboots can happen as a boot-loop or at any time from the moment the OS has loaded, no pattern to them at all, except they happen extremely frequently...

Is this a general known problem that the phones can develop or could there still be something lurking deep in the phone causing it?

2 months left on guaranty and still not seen a replacement I am entirely happy with, oh the dilemmas :)

The hungarian was a beta release of 2.1 so that is your problem right there, please update to 2.1 UK

Guest Lord_Shaithis
Posted
The hungarian was a beta release of 2.1 so that is your problem right there, please update to 2.1 UK

I've been looking for it for days....t-mobile removed it (last update they have is the 1.5 dec) and no where seems to have a download link.

Guest Richard_Arkless
Posted (edited)
I've been looking for it for days....t-mobile removed it (last update they have is the 1.5 dec) and no where seems to have a download link.

I think this may be the one http://support.t-mobile.co.uk/library/TMOB...20Android21.zip

but first you have to downgrade back down to 1.5, to do that follow this guide

http://android.modaco.com/content/t-mobile...e/#entry1318838

Edited by Richard_Arkless
Guest Lord_Shaithis
Posted (edited)

Thanks for the link, although still getting them and they are extremely strange....

Official UK 1.5 stabilised after I left it rebooting continually for ages......then ran for a few hours doing heavy-ish tasks.

Then upgraded to official UK 2.1 and got exactly the same thing. Rebooting endlessly, basically within 20 seconds of OS loading -IF it even got that far - then stabilised....

Updated to 2.2 and it never stabilises....

I just cannot imagine what would cause such a behaviour, currently leaning towards a dodgy RAM chip....but that's a wild stab in the dark.

Guess I need to get it doing endless reboots while running 1.5 or 2.1 stock to take it into the T-Mobile shop - joy!

EDIT: A-ha, found another thread about it......looks like I need a new system board.

Edited by Lord_Shaithis
Guest SpankyHam
Posted

Might be a silly question, but did you do a complete wipe before each upgrade? I know in the past I have had the same reboot problems when I forget to wipe before applying an update.

Not really sure how it could be a hardware problem specific to 2.1+.. If it was, I would have thought 1.5 would have crashed too.

Guest darkdevil1
Posted

I had exactly the same issue; stock 1.5 rom frequently rebooted on me. Shipped it to T Mobile for repair, they replaced the battery and did some soldering and the problem is gone!

Posted
The hungarian was a beta release of 2.1 so that is your problem right there, please update to 2.1 UK

That was pointless...

I'm on the HU update and never got the problem.

It has to be some other thing. Since he was at 2.2 I would guess it was the OC, but if he has the problem everywhere, try going back to 1.5 and go to T-Mo (if u have waranty).

Guest scoobydoo99
Posted
I had exactly the same issue; stock 1.5 rom frequently rebooted on me. Shipped it to T Mobile for repair, they replaced the battery and did some soldering and the problem is gone!

It would be good to know what soldering is required, my Pulse has been doing this for some time now, it's out of warranty so I'd have to stump up for the repair - not sure it would be worth it.

Guest Lord_Shaithis
Posted (edited)
Might be a silly question, but did you do a complete wipe before each upgrade? I know in the past I have had the same reboot problems when I forget to wipe before applying an update.

Not really sure how it could be a hardware problem specific to 2.1+.. If it was, I would have thought 1.5 would have crashed too.

I was wiping everything between flashes and using the time machine......1.5 also did reboot endlessly for a while before stabilising.

In fact, when putting it back to 1.5 ready for it's trip to the t-mobile shop, it even started rebooting while on the recovery screen....

Also, I was one of the people who couldn't run the OC kernel, I am guessing it's linked. So if you are reading this and get reboots on the OC kernel, be fearful for your pulse!

Edited by Lord_Shaithis

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.