• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Please help! Endless rebooting

Status
Not open for further replies.
A

alvinlwh

Lurker
I only got my Atrix (UK-Orange) 2 days ago and updated it from 2.2 to 2.3. Yesterday I decided to root it using this guide (cannot post link but it is a guide from Android Authority).

The root seem to work although I got some error message in step 5 (I think!). I proceed to download Root Checker which confirmed that my Atrix is rooted. Then I downloaded Root Uninstaller and proceed to uninstall some of the Orange bloatware. The phone seem to be working fine through the evening. And then at around midnight, the screen keep shutting off on me (no I am not that noob to have adjusted down the time out settings). I had to swipe my finger to turn the screen back on like every 5 seconds. Other than that, it seem fine.

Today daytime, it was working fine, and my Lapdock arrived. Slotted it in at the office and it starts and works just fine. Got home in the evening to charge the Lapdock and played around with it for about an hour (battery status from 1 to 5 lights but battery icon still flashing) before I went to do and have dinner.

At that time, I did not touch the phone or the dock, but I did notice that instead of shutting of the dock screen, the phone's screen keep flashing up on the dock's screen and goes away after a second or so. I was thinking at that time, why did the screen saver not kick in?

Anyway, after cleaning up, I went to the dock and continue using it for about 15 minutes, then I get a whole load (meaning 8-10) popups on the phone screen informing me of force stops. At this point, I still can carry on using Firefox on the Lapdock for another 5 minutes.

Then everything just went blank. I undocked the phone and try to redock it again, and the dock says no HDMI. Tried it a few times, same thing. Tried a restart, and the phone gets to the fingerprint unlocking stage and stops. I unlocked it and it goes into Android and the load of force stops started. I cannot even shut them down fast enough when the phone will reboot itself. It end up doing this endless cycle of startup and reboots. If I leave it alone at the fingerprint unlocking stage, it will wait a while and reboot.

I cannot get into Android at all and therefore cannot even enable USB debugging as suggested here (again cannot post links, but guide is from android advices) to try and install factory firmware.

Is the phone bricked? Is there anyway to recover it other than to send it into Motorola? I got it off ebay as almost new (rear instruction sticker still on) but clearly not new. Hopefully someone can help me in fixing this as I do not really have warranty.
 
alvinlwh said:
It is even worse now, after following this "guide" and here as well, it will not even boot to unlock screen! Step 1 and 2 worked, step 3 "moto-fastboot –w" will not work. It just shows me the list of commands to use with it. Skipped to step 4 and bam! Fail to boot message.:( looks like it is well and truely bricked! Really hate these a-holes posting rubbish "guides" on the internet!
Click to expand...

have you tried SBF? i had a similar problem and the only thing that worked was a fresh SBF. it's the riskiest thing you can do to an android phone but if it's a last resort...
 
jonjonjonjonjo said:
have you tried SBF? i had a similar problem and the only thing that worked was a fresh SBF. it's the riskiest thing you can do to an android phone but if it's a last resort...
Click to expand...

I am sick of "trying" anything else from the so called "experts" from the internet. I had sent my phone off to my family in ### where there are doggy shops with real experts that can do anything, including changing the IMEI.
(Not that I need to change the IMEI, but if these people can hack and slash the phones way beyond any stupid guides on the internet, they are real experts in my book!)
 
alvinlwh said:
I am sick of "trying" anything else from the so called "experts" from the internet. I had sent my phone off to my family in ### where there are doggy shops with real experts that can do anything, including changing the IMEI.
(Not that I need to change the IMEI, but if these people can hack and slash the phones way beyond any stupid guides on the internet, they are real experts in my book!)
Click to expand...

oh yeah, you got me. i claimed to be an expert, after all. get over yourself.
 
alvinlwh said:
It is a bit hard to get over myself when I followed the "expert" instructions, which are wrong and incomplete and bricked my brand new phone!
Click to expand...

all the more reason to try new things. if it's already bricked, why not keep trying possible fixes? anyway, looking at those guides, nothing there is wrong...neither would brick an atrix if followed correctly. so...
 
jonjonjonjonjo said:
all the more reason to try new things. if it's already bricked, why not keep trying possible fixes? anyway, looking at those guides, nothing there is wrong...neither would brick an atrix if followed correctly. so...
Click to expand...

I tell you what's wrong, the example I posted "moto-fastboot
 
jonjonjonjonjo said:
you're pissed because you copied and pasted an em dash instead of typing an en dash? when it didn't work, you didn't bother to try typing it out. that's not the guide's fault. you should never copy and paste into a dos prompt, for exactly that reason.

now you know.
Click to expand...

Oh really? Now it is my fault for following EXACTLY what was written by these so called "experts"? I copy and pasted to make sure I got the exact commands as they had posted. I am not the expert here, they are. So if they are the experts, why can't they get the instructions right? And you seriously expect an non expert to know the difference between an em and en dash by looking?!?!

And if you look at the comments on many of these so called "guides", and also on many android forums, I am not the only one having problems. Don't these lazy "experts" proof read anything they post knowing a wrong dash will screw up someone's phone?
 
alvinlwh said:
Oh really? Now it is my fault for following EXACTLY what was written by these so called "experts"? I copy and pasted to make sure I got the exact commands as they had posted. I am not the expert here, they are. So if they are the experts, why can't they get the instructions right? And you seriously expect an non expert to know the difference between an em and en dash by looking?!?!

And if you look at the comments on many of these so called "guides", and also on many android forums, I am not the only one having problems. Don't these lazy "experts" proof read anything they post knowing a wrong dash will screw up someone's phone?
Click to expand...

running an invalid fastboot command CANNOT screw up a phone. it says the command is invalid and impliedly it says "try again," not "HOW DARE YOU INPUT AN INVALID COMMAND? SELF-DESTRUCTING IN 10...9...8..."

you shouldn't have been messing around with this stuff anyway if you know nothing about it. phone bricks happen when people mess with stuff they don't know how to properly mess with.

aaaaaaaaand bye.
 
All squabbling aside... I'm running into the same problem with the continuous rebooting and the endless cycle of 'force close'-ing.

Has anyone here actually found a fix for this?
 
jonjonjonjonjo said:
running an invalid fastboot command CANNOT screw up a phone. it says the command is invalid and impliedly it says "try again," not "HOW DARE YOU INPUT AN INVALID COMMAND? SELF-DESTRUCTING IN 10...9...8..."

you shouldn't have been messing around with this stuff anyway if you know nothing about it. phone bricks happen when people mess with stuff they don't know how to properly mess with.

aaaaaaaaand bye.
Click to expand...

Let me get this straight, I do not know what to do, followed "step by step guides" from so called "experts" exactly, screwed up the phone and it is my fault?

I did not say it is the fastboot command that bricked the phone, I think it could be the fastboot command that started the events, I would not know would I since I am no expert. I also tried to flash SBF as you had suggested much earlier. I think that is what bricked my phone, but I do not know as I am not an expert. That is why I am looking at guides.

And guess what, I typed in the error message I got after I tried to reflash my phone, and saw that it is not just me that have the same problem. And the common replies from the "experts" like yourself? "Too bad sucker, your phone is bricked", "get a new phone sucker!" and now your "you shouldn't have been messing around with this stuff anyway if you know nothing about it" Real helpful you "experts"!

Alessandro Rossi said it best here, "Following your instructions now I brick my phone. I'm a stupid but you're a bast**d!!!!! Please don't write a tutorial next times if you don't know what you're talking about!!!"
 
I had the same issue.. im no expert.. but i kept doing searches to see if other people were having the same problems and what they did and if any solution.. only thing i can say what fixed my many reboots was the sim card.. i got a new sim card and now for a month is hasnt reboot at all.. but that was just my fix.. if it hasnt been something you have tried yet.. i would try that.. i did everything else out there that they said to do.. from the several formats to rooting and setting up another motoblur account and everything.. saw 1 post about getting a new sim card.. so i did that finally after everything else.. i hope this helps.. good luck..
 
In my case also the SIM card(s) caused the reboot problems. I found out that a small piece of board (thick paper) inserted between the metal clamp and the SIM-card pressing the card tighter to the contacts solved the problem.
 
This thread is out of hand with needless bickering and since the op has already posted-

"I am sick of "trying" anything else from the so called "experts" from the internet. I had sent my phone off to my family in ### where there are doggy shops with real experts that can do anything"

The problem is resolved and this thread is now closed!
 
Status
Not open for further replies.
Back
Top Bottom