Hi there,
I know this forum probably isn't too busy anymore given this phone's age, but I was hoping someone might have an idea. My Atrix 2 isn't my primary phone - hasn't been since I replaced it with a 2014 Moto X back in, well, October of 2014. However, I absolutely love the built-in Tasks app in the Atrix 2, so I still used the phone as my "task phone" that had many recurring tasks set up (house maintenance items, recurring finance things, etc).
However, as of a couple months ago, the phone gets stuck on the AT&T splash screen and won't ever move past. At this point, my plan (unless someone has another idea that will work) was to reflash the ROM (its just the stock AT&T ICS build) as I had read that should likely fix the issue, and can be done without data loss. My problem is that RSD Lite will not recognize the phone, at all. I've installed the Motorola drivers that I found on another thread here (I think, I'd have to go back and see exactly which it was), but RSD Lite won't see it.
Any thoughts?
Thanks!
Related
First of all, I would like to thank the owners of this forum for providing such a great resource for simpletons like me to use. While in real life I'm an Air Force officer, when it comes to Android rooting/modifications/etc. I know close to nothing.
Before I begin, I would like to let you all know that I HAVE searched Google and this forum for answers to my problem. While I have found solutions that look promising, I am still not comfortable with them as many of these threads are from the September/October timeframe (i.e. they're OLD!)
Here is my situation:
I bought/rooted my phone back in September. I can't remember exactly how I did it, but it WAS through USB debugging mode and a command prompt on my PC. I believe I downloaded a series of Motorola drivers, etc. but my memory is hazy at best. I successfully rooted my phone (got the little Superuser Ninja listed under my applications) and apps that required root all worked. I never put any custom themes/images/etc. on my phone - I only used it for Wireless Tether.
Shortly after rooting I was having Star Wars envy and put the custom bootscreen and sounds on my phone from the R2D2 Droid 2.
Then.. everything was fine for several months. I accepted the OTA update from Verizon sometime in October? and I am running version 2.3.2.. with my phone still rooted.
Now, here's my problem:
My microphone AND external speaker have both stopped working on my phone two days ago and I need to return it to Verizon under its warranty. I understand that Verizon will NOT accept my phone if it is rooted and if tampering is evident (i.e. custom bootscreen).
My question is this:
What is the easiest/simplest way to unroot my phone and return it to the stock bootscreen and sound files? I don't want a Verizon technician looking at my phone and saying, "What is this?"
While rooting my phone has nothing to do with the hardware.. I know they'll look for ANY reason to deny my warranty claim. The fact that my external speaker and external microphone have died on this phone are HARDWARE issues that Motorola should be liable for.. and in its current state my phone is unusable for making calls (nobody can hear me) and I need a new one.
I hope someone in this forum can point me in the direction of the proper solution.
Again, I'm sorry for posting a question to a problem where there already may be an answer.. but I don't want to take any chances.
Thank you.
btw I CAN make calls.. but I have to use a bluetooth headset!
Excellent question. If one can do, one ought to be able to undo.
Boot into recovery (google the button combo, it should include the power button and some other button(s)) and then use the speaker buttons on the side to navigate to factory reset. This will return your phone to how it was when you first took it out of the box. Hope this helps
Sent from my DROID PRO using XDA App
Hi, I have had my moto defy for a while so I decided to root. I mucked around with root for a month or so and then run a custom rom (LiquidArc Gingerbread). That worked fine, for about 3 reboots.. then it got stuck on the Red M (I left it for 10 mins and it was still stuck).. so I ran RSD Lite v4.9 and flashed the Australia Telstra (my current provider) from: and - developers. com / sbf:defy.
RSD Lite told me it had passed, and then said to restart the phone, I did and now nothing... Black screen, EDIT: White L.E.D sometimes, no bootloader, bricked. It is still recognised in RSD and I have tried the same .sbf three times now but still no success.
I have read through http://forum.xda-developers.com/showthread.php?t=1066816 but I am not sure where to go from now.
If anyone could help me that would be super!
EDIT: I know cannot even get it detected in RSD Lite.. I have a White L.E.D as soon as I plug the phone into the computer... I have also tried the jump-start method with a spare USB cable I had..
I think I'm bricked too =/
Fastboot and RSD options both freeze/lock up on me.
I am able to get into recovery but my clockwork version 4.0.0.4 which is causing some SD Card detection issues.
Stuck in a bad way right now, can you get into both RSD and Fastboot options?
RSD does not freeze but it cannot detect the phone any more. It used to, and thats when I tried flashing three times, but now, nothing.
imnew,,,,,,
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I have sent it in for repairs... They are going to phone me the cost of the repairs in a couple of days...
Look into this thread:
Motorola Defy > Defy Android Development > [DEV][ROM] CyanogenMod 7 (Android 2.3.4)
they have much xperience with these things
Sent the phone to Motorola..
I expected to pay for the repairs and would have done so happily, but it came back 10 days later free of charge with a fresh install of 2.2
I won't be messing with custom rom's for a while
wahaha...i'm done with motorola products now...you want to hear my story?
I bought motorola defy last year when it came out. I was very happy and so i continued flashing froyo which was blazing fast over Eclair...but my multitouch started giving me trouble. I sent it to motorola. They returned my phone after 2 months. YES 2 MONTHS !
They had all kind of reasons behind it...but when i got my phone back i was soo happy you can't imagine how i felt when i held it in my hands...but then i wanted to check other 2.2 roms as well if they would fix the multitouch problem but they didn't and one day, the phone started to react strangly, random reboots, not turning on, battery drain and all sort of things even with the stock rom...
I sent motorola my phone back again and i recieved it after a month...when i tried turning it on, it didn't turn on...so i had to send it back again for another month...and in the end i told them to keep their product and refund me...they did refund me but it took them another month to do so...
Motorola has a really poor customer service, i advice you guys to ask for refund and get Galaxy S, it goes for the same price now lolz
Hi all,
I bought a Samsung Galaxy Rugby Pro LTE SGH-i547C (the Canadian version, with Telus) about a month ago, but now it won't turn on (although I can get into Download mode).
Full story: Yesterday I decided to root it (after unlocking it through Telus), and today I wanted to install the Liquid Smooth ROM, as it looked pretty sweet, but that didn't go as planned. After following the steps the first time, nothing happened to the phone's interface, so I did it a second time. This time, when it rebooted at the end of the installation, It got past the first two screens (name of model, and just "Samsung"), then it turned off.
What I've tried so far: First I tried applying the stock images (about 10 Mb, from http://forum.xda-developers.com/showthread.php?p=34463311#post34463311) through ODIN, but that made no difference, except that in one of the boot modes, instead of the Clockwork interface I, get the default interface (the background having an Android alien on its back, and a red triangle with an exclamation point above it). In these interfaces, I also wiped pretty much all that I could wipe, but to no avail.
Next I tried applying two of the stock ODIN images (500-600 Mb, from the same link) through ODIN, but when it starts with the SMD, I get a message "SMD header check fail: boot.img" on my phone, and ODIN thinks for a while, then stops, saying 1 fails and 0 successes.
So here I am, asking for help. Would any of you have any ideas, or explanations (in layman's terms!) of what has happened / what I should do to get my phone useable again? Thanks in advance.
P.S. Also, I should mention I'm doing all the accessing through VMWare Fusion running Windows XP, on Mac OS 10.7.5
Just an update on the situation - Telus gave me a brand new phone (without me paying anything), same model, because I bought mine less than a month ago, and they provide all new phones with such a warranty. All they did was check it wouldn't turn on, and I was good to go.
That being said, I still would be interested to know how to solve my previous situation in general, as I plan to get more into this sort of stuff.
Also, I got into a detailed discussion on reddit about the situation and some experimentation, which might be useful in solving the situation. It's located at /r/AndroidQuestions/comments/1du4j8/galaxy_rugby_pro_not_turning_on_after_failed_rom/
I played around with my Droid X (installed CM and the like) years ago, but I haven't tried to do anything with my Razr Maxx HD since I'm in grad school. I've just been keeping it up to date with OTA updates, but I'd like to try roms again, namely the newer CM.
From what I've read, I need an earlier version of the OS in order to unlock the bootloader or root the phone.
I've also read (and have found from some personal experience the past couple days) that it is impossible to use RSD lite (6.1.4) to downgrade to literally any OS older than the one currently installed.
Is there anything I can do with this phone? Can I, either with or without RSD Lite, get to an earlier version? Can I at least root it so I can use Ti backup?
Or is there literally nothing I can do with this phone?
Two final, quick questions. Is anyone still working on this phone, or is it too much a pain andeveryone has moved on?
Finally, now that Moto is google, is the Moto X (and future phones) more dev friendly? Or do I need to think about moving away from Moto if I want to play around with my phone?
Sorry this is a repeated question, I guess I'm mostly bummed about what I've found and just want to be 100% sure I'm not able to do anything before I give up.
Unfortunately, there is nothing you can do. Pretty much if you want to mod a Moto now, you need to get a Dev X or a M/HD that has the bootloader already unlocked.
RikRong said:
Unfortunately, there is nothing you can do. Pretty much if you want to mod a Moto now, you need to get a Dev X or a M/HD that has the bootloader already unlocked.
Click to expand...
Click to collapse
recently turned my MHD in for an insurance claim (cracked screen)... didn't think about receiving a different MHD with up to date OTA's. LUCKILY received one with 9.18.79... so I can still obtain root... but lost being unlocked but like RikRong stated above... those are pretty much your only options now.. best of luck.
I haven't used my OnePlus One in several months since I got my Nexus 6. I've been meaning to sell my OPO, but got lazy about it. Now I can't be, and I need money for rent. A friend/co-worker who's in serious (in my opinion) need of a new phone wants to buy it off me.
My OPO was on LiquidSmooth 4.4.4 but obviously it's out of date, so I tried to update it. I tried once before to update it with a 5.1 ROM, but it kept failing. I remember there was something about the firmware or baseband version that needed to be flashed to go from KK to LP, but it was several months ago, and I can't remember what exactly it was. And for the life of me, I can't find it.
I tried to find what it was, and in my searching I found that CyanogemMod Official 13 had a built-in baseband updater. So that's what I tried. TWRP version was/is 2.8.7.0. Maybe that was the problem?
Anyway, CM13 (the most recent snapshot) installed, seemingly fine, but it won't recognize my SIM card. I try reinstalling it, and it still won't recognize the SIM. Moreover, it doesn't even detect a cell signal (it should, as all cell phones in the US are required to have 911 emergency access, even if you're not actually paying for phone service). And then it starts rebooting. Not a bootloop, because it boots. Then a few minutes later, it reboots. Continuously.
So I try a different ROM. The latest Resurrection Remix (I have it on my Galaxy S4 and it works fine). Same thing.
The even weirder thing is that I figure I should just restore my latest nandroid, but it's not there. In fact, nothing's there. Nothing visible through TWRP's file manager or backups. Not even old pictures, which I didn't delete. I didn't delete any storage (because I wanted my backup, just in case, duh). But TWRP still shows that there's 26GB available. So obviously, there's something there. I just can't see it. My fault for not saving the nandroid elsewhere, but Humpty Dumpy has already fallen.
I have Wugfresh's toolkit (yeah, yeah, I know...), and tried restoring it to stock, and it won't do it.
I've used ADK in the past, but it has been way to long for me to remember specifics, and it has apparently been updated with the newer Android versions. Obviously, I've looked at the sticky thread about restoring your OPO to stock, but it hasn't been updated in a while. So I'm worried about using those instructions. I've looked up youtube videos, and they're all too old as well. I'm also worried that I'd be using the wrong version of ADK. I'm not scared of using ADK, as long as the instructions are correct and clear. I'd be using Windows 8, if that matters.
So what I'm asking (begging) for is instructions on how to make this phone work properly again. Quickly. I've tried doing the research myself, and haven't found my solution. I'd keep at it, but time is getting short, and I can't afford that. Literally. I can't afford the hours spent (it's 1am and my the office closes at 4pm), and I can't afford being late on my rent. A couple weeks ago I spent way too much up in Phoenix to go see Guns N' Roses (at least I got a kickass T-shirt). Entirely my fault. Also my fault for not realizing how desperate my financial situation was about to be, and for waiting to ask for help until now. And I'm not going to ask to borrow money. I just can't.
Finally, and I know it's taboo to ask "what's the best ROM?", because I've answered that question myself with "there isn't one - try them out for yourself and find which one's best for you". But as I said, I'm out of time., and I haven't been keeping up with what's going on with OPO's development. My friend is not like us. His phone's a LG cheapo POS from years ago that's on 4.1JB. He uses it for calls, texts, and podcasts. He doesn't need root, or even custom recovery for that matter. In fact, I'd prefer if it didn't have root (although custom recovery might be nice, just in case). So if I can get this damn thing working properly again, what'd be a good ROM for my firend? OPO's official Oxygen? Are they still updating it? Stability is the primary concern, but if there's something that gets regular (and stable) updates, that'd be good too. With an updater that's built-in, simple, and wouldn't need and XDA forumite to do it for him. Because it'd be nice that he could get updates with Google's security patches. But since he's still using a 4.1 phone, he's obviously not all that concerned about that issue. But still, that'd be nice.
Thank you (fingers crossed).