[Q] Back to ICS from CM10 - Atrix 2 - Motorola Atrix 2

Hello,
I followed step-by-step this thread.( http://forum.xda-developers.com/showthread.php?t=1982982 )
Since I ve been a listener and this is first time caller, Im not allowed to reply in Developer section until 10 post are made.
This is my first post and need help.
Everything works just as the DEV explained. The bugs are the known ones, and it works...fine.
But, things like the camera bug (3rd party apps cant use it, like instagram, guess Skype, Google Now, etc...), screenshots and auto-rotation made me want to go back. (I could manage the APN thing by following one of the replier's advices)
So, question is: Is out there a more stable CM10 ROM? (I know the link I related isnt from actual CM10, yet a modified one. But after reaserch I found that the original CM10 also have this same known issues). If there isn't. Is there a way to go back to a bug-free ICS version?
If there is, I would need a step-by-step guide.
Thanks in advance for all replies.
______
Motorola Atrix 2 - CM10/MagicMod ROM

WaltLlanos said:
Hello,
I followed step-by-step this thread.( http://forum.xda-developers.com/showthread.php?t=1982982 )
Since I ve been a listener and this is first time caller, Im not allowed to reply in Developer section until 10 post are made.
This is my first post and need help.
Everything works just as the DEV explained. The bugs are the known ones, and it works...fine.
But, things like the camera bug (3rd party apps cant use it, like instagram, guess Skype, Google Now, etc...), screenshots and auto-rotation made me want to go back. (I could manage the APN thing by following one of the replier's advices)
So, question is: Is out there a more stable CM10 ROM? (I know the link I related isnt from actual CM10, yet a modified one. But after reaserch I found that the original CM10 also have this same known issues). If there isn't. Is there a way to go back to a bug-free ICS version?
If there is, I would need a step-by-step guide.
Thanks in advance for all replies.
______
Motorola Atrix 2 - CM10/MagicMod ROM
Click to expand...
Click to collapse
Sure you can go back to stock ICS.
Find the FXZ file for your region here: http://sbf.droid-developers.org/edison/list.php
Follow The noob guide on how to flash FXZ here: http://forum.xda-developers.com/showthread.php?t=1396650

HELP!!
Waiting4MyAndroid said:
Sure you can go back to stock ICS.
Find the FXZ file for your region here: http://sbf.droid-developers.org/edison/list.php
Follow The noob guide on how to flash FXZ here: http://forum.xda-developers.com/showthread.php?t=1396650
Click to expand...
Click to collapse
I followed the steps to flash the SBF and give my Atrix 2 the stock ICS version again.
I did the whole process and clicked START
After a while, several minutes, it showed
"FAILED FLASHING PROCESS, FAILED FLASHING PROCESS. 5/20 REBOOT-BOOTLOADER -> NO ARRIVAL MESSAGE NOTIFICATION; PHONE DISCONNECTED"
And in the result column it shows FAILED
I made sure the battery was full before begin the process, and I haven't touched the phone at all since it started.
What do I do? It's still plugged and the screen's off (Don't sure if the phone is off). I havent touched a thing.
This is the SBF I downloaded:
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip
from here: http://sbf.droid-developers.org/edison/list.php
EDIT:
When still plugged in, I pressed the POWER button, and nothing happened, Thought it was off.
I closed the RSD and unplugged the phone from PC and tried to turn it on. NOTHING HAPPENED.
No LED light, No Moto logo, nothing.
Removed battery, tried again....nothing...at all. ¿Dead?
Is it totally screwed? Nothing to do about? PLEASE HELP ME!. Im about to die.

WaltLlanos said:
I followed the steps to flash the SBF and give my Atrix 2 the stock ICS version again.
I did the whole process and clicked START
After a while, several minutes, it showed
"FAILED FLASHING PROCESS, FAILED FLASHING PROCESS. 5/20 REBOOT-BOOTLOADER -> NO ARRIVAL MESSAGE NOTIFICATION; PHONE DISCONNECTED"
And in the result column it shows FAILED
I made sure the battery was full before begin the process, and I haven't touched the phone at all since it started.
What do I do? It's still plugged and the screen's off (Don't sure if the phone is off). I havent touched a thing.
This is the SBF I downloaded:
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip
from here: http://sbf.droid-developers.org/edison/list.php
EDIT:
When still plugged in, I pressed the POWER button, and nothing happened, Thought it was off.
I closed the RSD and unplugged the phone from PC and tried to turn it on. NOTHING HAPPENED.
No LED light, No Moto logo, nothing.
Removed battery, tried again....nothing...at all. ¿Dead?
Is it totally screwed? Nothing to do about? PLEASE HELP ME!. Im about to die.
Click to expand...
Click to collapse
If your phone is ATT version MB865, then you used the wrong SBF. The one to flash is
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip md5=2BF9CCD528C05D26523ACC5B38AC76C6
I believe your phone is soft bricked with a dead battery. Find a way to charge your battery and try to RSD again.

Waiting4MyAndroid said:
If your phone is ATT version MB865, then you used the wrong SBF. The one to flash is
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip md5=2BF9CCD528C05D26523ACC5B38AC76C6
I believe your phone is soft bricked with a dead battery. Find a way to charge your battery and try to RSD again.
Click to expand...
Click to collapse
Actually, I think he is, sorry to say, super-hardbricked. Take a look here, it has all the proper explanations about bricks:
http://forum.xda-developers.com/showthread.php?t=1937112
If he was on ICS and an AT&T phone and flashed a non-AT&T firmware, he is most likely screwed. We have seen this way too many times, sorry to say, but to the OP, Please read more before trying these type of things and use search and not get too antsy before attempting things. This phone even though it has a bootloader lock, you can still very easily hard brick it.
The OP, just might get lucky and be able to charge his phone with an external charger, but I am pretty sure that will not do it.
I would go on ebay or craigslist and buy a working A2 with a cracked screen (much cheaper this way), and change out the board with your screen and such, and you should be back in business.
@Waiting4MyAndroid, next time you try to help someone ask them for more information, so you/we can be of better help, this guys is obviously a noob, and if we knew which region he was from and which phone he has, we/you could have given him the EXACT link to the correct file, and then walked him through what and what not to do. I am not trying to be a jerk. I am just saying that most people do not search or read these forms, they ask in a dire need and even when you give a link to read something, they are in panic mode and still do not read, and just do what they think is the thing you just mentioned, even though it may not be the right thing. I know this has been covered so many times, but I have learned that no matter what people do not read or search no matter what you mention, that is why we see soooooooo many of these types of posts over and over.

jimbridgman said:
Actually, I think he is, sorry to say, super-hardbricked. Take a look here, it has all the proper explanations about bricks:
http://forum.xda-developers.com/showthread.php?t=1937112
If he was on ICS and an AT&T phone and flashed a non-AT&T firmware, he is most likely screwed. We have seen this way too many times, sorry to say, but to the OP, Please read more before trying these type of things and use search and not get too antsy before attempting things. This phone even though it has a bootloader lock, you can still very easily hard brick it.
The OP, just might get lucky and be able to charge his phone with an external charger, but I am pretty sure that will not do it.
I would go on ebay or craigslist and buy a working A2 with a cracked screen (much cheaper this way), and change out the board with your screen and such, and you should be back in business.
@Waiting4MyAndroid, next time you try to help someone ask them for more information, so you/we can be of better help, this guys is obviously a noob, and if we knew which region he was from and which phone he has, we/you could have given him the EXACT link to the correct file, and then walked him through what and what not to do. I am not trying to be a jerk. I am just saying that most people do not search or read these forms, they ask in a dire need and even when you give a link to read something, they are in panic mode and still do not read, and just do what they think is the thing you just mentioned, even though it may not be the right thing. I know this has been covered so many times, but I have learned that no matter what people do not read or search no matter what you mention, that is why we see soooooooo many of these types of posts over and over.
Click to expand...
Click to collapse
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app

Waiting4MyAndroid said:
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
No worries. I was going by his join date of Dec. 2012, and only having posted five times, for noting that he was a noob. I have found that a lot of people can talk the talk well in here, but have maybe used another phone that is not like the A2 and tend to easily mess it up. Especially if this is their first android.

Waiting4MyAndroid said:
Jim your advice to me is well taken. Usually I do ask more questions before I offer advice. In this case the OP "seemed" knowledgeable due to the fact his phone was on CM10/MagicMod. I guess everyone should be treated as a NOOB until proven other wise! Hopefully the OP can still recover his phone with a charged battery.
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks VERY MUCH for your help. And yes, this is my first Android, and first time flashing, and as you supposed, noob.
:/ I want to believe it is the battery and with a charging will revive, but I don't know. The "super-hardbrick" thing makes more sense to me.
IT WAS FULLY CHARGED, it can't drain 98% in a few minutes, can it?...
Aaaaanyways, I will see if by charging the battery and trying it will show a light.
(Will it charge the battery in this state? or I'll have to make it by other means?)
Thanks @Waiting4MyAndroid and @jimbridgman for replying.
EDIT: When I plug it in the wall, nothing happens. No LEDs, no Moto logo, just black screen. It doesn't shows life signals. Same happens when plugged to the PC.

WaltLlanos said:
Thanks VERY MUCH for your help. And yes, this is my first Android, and first time flashing, and as you supposed, noob.
:/ I want to believe it is the battery and with a charging will revive, but I don't know. The "super-hardbrick" thing makes more sense to me.
IT WAS FULLY CHARGED, it can't drain 98% in a few minutes, can it?...
Aaaaanyways, I will see if by charging the battery and trying it will show a light.
(Will it charge the battery in this state? or I'll have to make it by other means?)
Thanks @Waiting4MyAndroid and @jimbridgman for replying.
EDIT: When I plug it in the wall, nothing happens. No LEDs, no Moto logo, just black screen. It doesn't shows life signals. Same happens when plugged to the PC.
Click to expand...
Click to collapse
If that is the case then you will have to try either the Macguvyer method:
http://forum.xda-developers.com/showthread.php?t=892026
Or find someone with a similar phone that works, that will let you use their phone to charge your battery with (another A2 or a bionic).
Those are just so you can see if it is a battery issue, but at this point, I am thinking you are hardbricked.
Do you have an AT&T branded phone (there will be an at&t logo at the bottom front of the phone under the capacitive buttons)?

jimbridgman said:
If that is the case then you will have to try either the Macguvyer method:
http://forum.xda-developers.com/showthread.php?t=892026
Or find someone with a similar phone that works, that will let you use their phone to charge your battery with (another A2 or a bionic).
Those are just so you can see if it is a battery issue, but at this point, I am thinking you are hardbricked.
Do you have an AT&T branded phone (there will be an at&t logo at the bottom front of the phone under the capacitive buttons)?
Click to expand...
Click to collapse
Yes, its an AT&T device. I'll try to charge the battery.
/In the case its hardbrick, there's nothing we can do, right? AT ALL?/

WaltLlanos said:
Yes, its an AT&T device. I'll try to charge the battery.
/In the case its hardbrick, there's nothing we can do, right? AT ALL?/
Click to expand...
Click to collapse
You can try and get AT&T to exchange it for a refurb, just tell them you charged it overnight and woke and it was like this. The only thing is that you must have, had the phone less than a year to qualify for this, and you MUST be in the US.
Otherwise you can buy an A2 on ebay or craigslist with a broken screen and put your good screen on that phone and be back in action. There is a thread in the general section that is a sticky on how to exchange your screen with the phone you get that has a broken one. This will be only if you are out of the year warranty or bought this phone and use it outside the US.
http://forum.xda-developers.com/showthread.php?t=1746094

jimbridgman said:
You can try and get AT&T to exchange it for a refurb, just tell them you charged it overnight and woke and it was like this. The only thing is that you must have, had the phone less than a year to qualify for this, and you MUST be in the US.
Otherwise you can buy an A2 on ebay or craigslist with a broken screen and put your good screen on that phone and be back in action. There is a thread in the general section that is a sticky on how to exchange your screen with the phone you get that has a broken one. This will be only if you are out of the year warranty or bought this phone and use it outside the US.
http://forum.xda-developers.com/showthread.php?t=1746094
Click to expand...
Click to collapse
I'm out of US, so I guess the warranty thing won't work. (Damn, I guess if I get out of this, will NOT ever try to handle upgrades, and flashing and this stuff) I bought the Atrix 2 from e-bay..Its (was) pre-paid.
Thank you so much for everything. And well, sorry for the inconveniences.
By the way, can you explain to me, what did I do exactly to the phone? I mean, what I understand is that I took out the "software" that ran everything in the device (including powering on) and didn't replace it with the new one since the process didn't complete. So in the end, I took the "soul" out of it, leaving just the dead "body". Does it make sense?

WaltLlanos said:
I'm out of US, so I guess the warranty thing won't work. (Damn, I guess if I get out of this, will NOT ever try to handle upgrades, and flashing and this stuff) I bought the Atrix 2 from e-bay..Its (was) pre-paid.
Thank you so much for everything. And well, sorry for the inconveniences.
By the way, can you explain to me, what did I do exactly to the phone? I mean, what I understand is that I took out the "software" that ran everything in the device (including powering on) and didn't replace it with the new one since the process didn't complete. So in the end, I took the "soul" out of it, leaving just the dead "body". Does it make sense?
Click to expand...
Click to collapse
What you did was flash a non AT&T firmware to the device, which causes the phone to "hardbrick" AT&T has some checks built into the hardware that will make the phone "die" if this is done. So if you do get another one, just make sure that you ONLY flash the proper AT&T FXZ file on the SBf-droid.com site, they say which ones are AT&T.
You can flash all the "ROMS" you want, you just can not use a firmware (FXZ) that is not AT&T based, so if you bootloop or softbrick, you need to make sure you use this FXZ file for AT&T ICS:
334.7 MiB 2BF9CCD528C05D26523ACC5B38AC76C6 ATT US InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip http://sbf.droid-developers.org/edison/InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
My guess is that you did not use this file before, and RSD lite began to flash the bootloader, then went to reboot, and the checks happened and saw that the wrong bootloader was flashed and that set off an efuse that "bricked" the phone.

warrenty
Check to see if u have warranty still with motorola. Just give some lame excuse. Dont mention anything about roooting or roms or ull be f'ed. I sent then 2 hard bricked phones so on my 3rd A2 now. Just pay for shipping and it will be back in ur hands in hopefully less than 2 weeks.
Cant enter link cause im newb but motorola com go to service look for a2 and
Its on the bottom left column just enter imei#

widekyle said:
Check to see if u have warranty still with motorola. Just give some lame excuse. Dont mention anything about roooting or roms or ull be f'ed. I sent then 2 hard bricked phones so on my 3rd A2 now. Just pay for shipping and it will be back in ur hands in hopefully less than 2 weeks.
Cant enter link cause im newb but motorola com go to service look for a2 and
Its on the bottom left column just enter imei#
Click to expand...
Click to collapse
That only works, if Motorola warranties the phone in the Country that you live in.

jimbridgman said:
That only works, if Motorola warranties the phone in the Country that you live in.
Click to expand...
Click to collapse
I live in Colombia, and I bought the device on April 2012 on ebay, had it shipped internationally with USPS.
Do you think I can claim warranty for Motorola directly? Obviously not mentioning anything about ROMs, flashing, and anything. But what can I say?

WaltLlanos said:
I live in Colombia, and I bought the device on April 2012 on ebay, had it shipped internationally with USPS.
Do you think I can claim warranty for Motorola directly? Obviously not mentioning anything about ROMs, flashing, and anything. But what can I say?
Click to expand...
Click to collapse
Nope, you can not get moto to warranty it. You are better buying another phone. I would buy one that will be warrantied in your country, just in case something like this happens.

Related

[HELP] What do I do now? Captivate dead.

Yessss another dead captivate thread.
I think I'm gonna go die now.
I followed the video guide to install a custom ROM, in the development thread to the letter, and now my phone wont even turn on... (now that im thinking about it, I think I may have left the debugging mode OFF before I went to flash back to stock, maybe thats why?)
I got into download mode, plugged the phone into odin3 JF6 one click, it started and at some point during the process it said "removed" even though I didnt touch anything, and then i got a weird msg saying my device is not recognized, keep in mind the drivers were installed properly, and I had everything double checked before i flashed....
wtf do I do now? Cant boot at all or go back into download mode. this is my third galaxy, got it two days ago ffs.
My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.
1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App
bobbylx said:
My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.
Click to expand...
Click to collapse
I'm not sure if I was looking at the right place, but I think its 10.12. I'll do a search and see what comes up, thanks for your help.
JayPhill89 said:
1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'll try that, thanks.
Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.
G.Hook said:
Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.
Click to expand...
Click to collapse
I've tried every possible key combination out there and nothing works. I think my best bet is a Jig, unfortunately the source didnt have any transistors in stock so im SOL for now.
Use JIG ... It will be your last help.
Use it as a paper weight.
If you look up samsung captivate jig on ebay you will find some pre built. I bought one not long ago just to have and it works just fine.
I hope this helps. Best of luck to you.
Sent from my GT-I9000 using XDA App
Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.
Check out this link for a jig. And there is a video to show you how to build one. Or mobiletechvideo guy sells them for 17 bucks.
http://forum.xda-developers.com/showthread.php?t=889128&highlight=usb+jig
Sent from my SGH-I897 using XDA App
newter55 said:
Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.
Click to expand...
Click to collapse
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
rsnt said:
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
My first captivate went fubar within my 30 days and I damaged the nv_data.bin on my second captivate and was stuck with the test IMEI. Samsung fixed my second one for free. Now I'm at the point where I'm totally sure about what precautions I need to take to keep me out of trouble but I'm not sure if I want to risk it again, heh.
The cheap jig does work. It helped me when I accidentally unplugged my phone during an odin flash.
Yes, you make a good point. You will find that most of the guides are written by people like myself who have an early revision or a phone from the initial release. For most of us, from what I've read and experienced, our phones are really hard to brick, ie, button recovery always works, odin one-click works, etc.
I honestly don't know all the differences now between revs. The first hiccup was the phones missing button recovery/download, and now it seems that people are having issues using the Odin One-click that we have been using for months.
I would recommend with your next phone check the rev or manufacture date, then search the forums for people with similar or same revs that have been successful at flashing and find out what they did.
good luck
@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App
newter55 said:
@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App
Click to expand...
Click to collapse
I agree with you completely. I tend to take it for granted that button recovery works for me and that good old odin one-click does too. It seems we need to start collecting data and making new guides.
Something like,
If you have rev, 1006, 1007,1008 go here,
If you have rev 1009 to 1012 go here,
etc.
latest update,
Two cables, and six resistors later, my phone won't go into download mode, lol, I'm not even sure I did things right, I'm gonna try stripping the same cable, used in one of those videos on how to make a jig, I still have three extra resistors.
I'm starting to think its because of it being with rogers. im gonna search the forums.
A micro usb breakout board is the simplest method for constructing a jig.
Wow, I guess I'm lucky that the used Captivate I picked up for my gf is an older one at 1007. Root procedure for her went without a hitch.
From stock rom, all set up and in daily use, WITHOUT ROOTING first.
Put clockwork update.zip on her sdcard.
Reboot into recovery.
Reinstall packages twice to get into clockwork recovery.
Wipe data/factory reset.
Flash Cognition.
Profit.
She's been using it this way for two weeks and loves it so much more than stock.
What was so complicated about the procedure you followed? Or was it the same as this but it just didn't work?
rsnt said:
...and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
I think you may have a good point. Eventually your carrier will stop replacing bricks for you. If you still have the inclination to play with flashing, investing in a jig would definately be a wise investment and if I were in your shoes, I wouldn't flash anything without one. I made a jig for myself before I ever flashed anything but luckily I have never had to use it, probably because I took the time (about a month and a half of trolling around here reading.) to research what all was involved with what I was about to jump into. Just something to consider in case you want to try again. Good luck!

[Q] Static from headphone jack (questions about Moto service)

Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.
lkrasner said:
Hi, my headphone jack has always been pick about having things plugged in just right, usually the slightest bit of ling screws it up. Finally today, it just started giving serious static in right side. when music or any sound starts it goes away, but the volume is very low on that side. It only does it when there is power (battery is in), so I think it is a bad connection in there. I have some questions regarding this.
1. How horrible is the Motorola service? they say 5-7 days, but is that really the case (In the U.S.). My warranty is still good, I'll just flash back to stock.
2. will opening the phone up void my warranty? I am somewhat experienced with electronics, so I could probably fix it, but I don't wantt to void the warranty in case it doesn't work.
3. I also have a stuck pixel on my screen that has been there since I got the phone (New). Will they fix that as well even though I can only select one problem on the application form? Should I mention it as well so that they might fix it?
Thank you,
-lkrasner
P.S. Unfortunately this means that I might be unable to do much for a while when I send my phone away. I hope you guys get ICS without me, and I will be waiting to try it out myself.
Click to expand...
Click to collapse
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.
jimbridgman said:
Just do a mis-flash or delete the system partition and take it into a store and tell/show them it does not boot, that you picked it up off the charger and it was like that, and you need a replacement. They will send you a replacement and you have 30 days to return your "broken" phone. I have done this 4 times with my A2s.
Click to expand...
Click to collapse
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Edit: If this does work I owe you something huge, plus I would get my screen problem fixed
EDIT 2: would I be better off just deleting something that would just stop if from booting past the boot logo (big M) so it wouldn't be so obvious that I just killed it with is basically sayins so on the fastboot screen. If so what could I delete that wouldn't prove I had rooted, probably nothing now that I say that.
lkrasner said:
But my AT&T warranty is up?!?! will it still work? I still have my 1 year moto warranty.
Click to expand...
Click to collapse
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.
jimbridgman said:
That is the Moto warranty, AT&T will just help you "file" it since it is done through them anyhow.
Just don't call moto yourself.
Click to expand...
Click to collapse
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.
lkrasner said:
sweet, I will try that, what should I do to brick just erase system with fastboot? isn't that really obvious? or are all the employees just stupid. Obviously I need to do something recoverable so that i can get it back if it doesn't work.
Click to expand...
Click to collapse
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
The secret is to act dumb, pretend like you know nothing bout flashing and this site... just act like it just went nuts and started this, and it will not boot.
Ask for the advanced replacement.
jimbridgman said:
Do anything that will make it either boot loop or stick on the dual core/moto boot screen. Whacking system/boot should do that, and you can still flash it back to stock before you send it back if you really want to.... they are just going to fully refurb it and re-sell it...
Click to expand...
Click to collapse
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
if it is borked when you take it to the store they can't see that it is rooted cause it won't boot... all they are going to do it call their 1-800 number and help you file a support request... then the person the phone will let you know of the "requirements" and ask if the phone has any visible water damage, yadda yadda...
Then they will send you a new phone and you should get it in 3 or so days and you are supposed to send the old one back in the SAME box... so you will already have flashed the fxz and been using the phone the whole time you waited for the new one to show up... just don't forget to send it back... I did and waited until 25 days later, and I was bugged mercillessly by att...
Just make sure you factory wipe and take out your sim and SDcard, and battery door... they do not send anything but the core of the phone, no batt or batt door or anything.
lkrasner said:
OK, and they will not be able to see root then, and if they flash it back to stock it will no longer be rooted, so I should be fine. I opened a service request with Moto earlier, do you think that will be a problem? Should I wait until it expires so they don't get suspicious that I bricked it on purpose.
Click to expand...
Click to collapse
@jim on playing dumb,hilarious ..i do that when i upgrade my phone.im such an ass when i upgraded to a2 from xperia x10 that i didnt even bother restoring it to stock, i left cm7 on it,custom bootlogo ,said "free xperia team" on boot.i just pretended i didnt know what happend. it was so enjoyable.
service rep - "it appears to be rooted"
My response - "What do you mean rooted? It has roots like a plant?".
@krasner
You worry to much,they cant prove anything.just brick it and youll be fine.u could even play dumb as u crack a smile while doing so and they still really cant do anything to prove u did it and have to exchange it.
Sent from my MB865 using xda premium
worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it
lkrasner said:
worked beautifully! I deleted build.prop and default.prop, so it just went to a black screen after the moto logo. when the guy called the warranty center he said it was "extremely defective and clearly in need of replacement."
After I walked out, I went home, booted into bp tools, taking me to cwm and used adb to push the two files back. The phone already shipped.
However I am thinking of selling it BNIB and getting something else, any ideas what I could get for it
Click to expand...
Click to collapse
Maybe 150. It wont be "NIB" you will not get a box, batt, back cover, etc. With the replacement.
Sent from my SAMSUNG-SGH-I747, running CM9, using xda premium

Hard Bricked My US Cellular S3, I think, please help!

I haven't tried the jig, but all the other symptoms such as dead screen,functionless buttons and all are there, so I think it is Hard Bricked. It's really weird what happened, I rooted my S3, it was working perfectly, then I unlocked the bootloader, it was perfectly fine even after that, then using ROM Manager I installed clockwork recovery mod, it was was working great. Then, I deleted my android market using ES File Explorer, and the guide for replacing the market told me to look for Vending.apk and then delete it, I looked but couldn't find it, so I 100% remember I tapped the search button in ES File Explorer and searched for Vending.apk, then suddenly a window popped up with names of files flashing but it didn't say searching or anything just three dots (...) and under there were two options YES and NO. I pressed No, it closed and then popped up again so this time I pressed Yes. then the names of files kept flashing and then it finished but didn't give me any search result, But my Phone memory was showing Empty, only the sd card folder was there and nothing else so I closed the app and opened it again, still the phone memory was empty, I was freaked out, so I restarted the phone and then, it never started :crying: I don't know what happened. Please help?
odin back to stock and start over....your device is far from hardbricked.
Really?? Can you please tell me step by step what to do?? I'm a complete noob at this!
droidstyle said:
odin back to stock and start over....your device is far from hardbricked.
Click to expand...
Click to collapse
My device does not go into download mode, nor in recovery, it's buttons are useless and there's a completely dead screen.
droidstyle said:
odin back to stock and start over....your device is far from hardbricked.
Click to expand...
Click to collapse
have you tried a different battery?
I forgot to mention, it's brand new, this happened the second day I bought it. So, the battery is flawless and perfect.
droidstyle said:
have you tried a different battery?
Click to expand...
Click to collapse
No its dead for sure. He tried to unlock the us cellualr S3 which would result in a perma brick.
You don't need to unlock the bootloader of the us cellular S3. That is why everything is labeled "verizon unlock" and stuff.
con247 said:
No its dead for sure. He tried to unlock the us cellualr S3 which would result in a perma brick.
You don't need to unlock the bootloader of the us cellular S3. That is why everything is labeled "verizon unlock" and stuff.
Click to expand...
Click to collapse
ahh i missed that detail...yes i agree its dead for sure! jtag or new replacement time.
Since it's only a couple days, take it back into USCC store. You're in your 15 day Window, they should swap it for a new one. Act dumb, don't tell them you rooted it. Just say you heard it buzz and it died. They'll mark it down as defective and give you a new one
How the hell was I supposed to know that? The US Cellular S3 is completely identical to the Verizon one, the only difference is the carrier logo, I rooted it with the Verizon S3's guide everything went perfectly fine, so I continued to do all the other stuff. I just got it 2 days ago :crying: . Huff, I've sent it for JTAG to a friend.
droidstyle said:
ahh i missed that detail...yes i agree its dead for sure! jtag or new replacement time.
Click to expand...
Click to collapse
ShazzyK-IDEOS said:
How the hell was I supposed to know that? The US Cellular S3 is completely identical to the Verizon one, the only difference is the carrier logo, I rooted it with the Verizon S3's guide everything went perfectly fine, so I continued to do all the other stuff. I just got it 2 days ago :crying: . Huff, I've sent it for JTAG to a friend.
Click to expand...
Click to collapse
a simple google search would of told ya that...
http://lmgtfy.com/?q=is+the+bootloader+unlocked+on+the+usc+galaxy+s3
research then flash dont flash then research!
tallgrasshawk said:
Since it's only a couple days, take it back into USCC store. You're in your 15 day Window, they should swap it for a new one. Act dumb, don't tell them you rooted it. Just say you heard it buzz and it died. They'll mark it down as defective and give you a new one
Click to expand...
Click to collapse
Great idea, but, I'm not in the US. I bought this phone from a guy who brought it from the US, I got it for half the price of an S3 here. So now, I don't know what to do, I gave it to friend, I hope he'll fix it, but if he's unable to can I give it to Samsung?
True, well said :'( I messed up big time.
droidstyle said:
a simple google search would of told ya that...
http://lmgtfy.com/?q=is+the+bootloader+unlocked+on+the+usc+galaxy+s3
research then flash dont flash then research!
Click to expand...
Click to collapse
Hi everyone,
I think my fiance might have hard-bricked his (new! Less than 24 hrs old!) Verizon Samsung Galaxy S III. He researched, rooted, set up bit-defender and it was working fine but when he tried to copy music files onto the micro-SD, they appeared to have gone onto the hard-drive instead and made his phone uber sluggish. We had some friends over, so he dropped the issue for a while and then went back to try to fix it only to make things worse. I know there isn't enough detail there about what *else* he tried to do, but when he came to bed last night he was kicking himself for not researching it enough and mentioned that he tried taking the batter out, resetting it, taking the sim card out, resetting it, telling bit defending to wipe the phone, etc. but all it would do last night was just display the 'samsung' logo then go to black.
This morning, I found your threads and tried to do the power+down+home advice that I've seen on a few threads here but it didn't work (obviously).
I suggested using the micro-SD adapter to try to explore the files on a PC, so we might look into that later.
Is there anything else you guys would recommend? I'm thinking the only thing to fix it now is the dopey route. :silly:
-Ami
Your phone is Soft Bricked not hard bricked, otherwise it wouldn't even turn on, Use A USB JIG to force it into download mode, then reflash with Odin.
Aminarra said:
Hi everyone,
I think my fiance might have hard-bricked his (new! Less than 24 hrs old!) Verizon Samsung Galaxy S III. He researched, rooted, set up bit-defender and it was working fine but when he tried to copy music files onto the micro-SD, they appeared to have gone onto the hard-drive instead and made his phone uber sluggish. We had some friends over, so he dropped the issue for a while and then went back to try to fix it only to make things worse. I know there isn't enough detail there about what *else* he tried to do, but when he came to bed last night he was kicking himself for not researching it enough and mentioned that he tried taking the batter out, resetting it, taking the sim card out, resetting it, telling bit defending to wipe the phone, etc. but all it would do last night was just display the 'samsung' logo then go to black.
This morning, I found your threads and tried to do the power+down+home advice that I've seen on a few threads here but it didn't work (obviously).
I suggested using the micro-SD adapter to try to explore the files on a PC, so we might look into that later.
Is there anything else you guys would recommend? I'm thinking the only thing to fix it now is the dopey route. :silly:
-Ami
Click to expand...
Click to collapse
ShazzyK-IDEOS said:
Really?? Can you please tell me step by step what to do?? I'm a complete noob at this!
Click to expand...
Click to collapse
If you're such a noob and unprepared for a brick, maybe you shouldn't have ventured down custom ROM/unlock avenue?
Just a thought.
Sent from my SCH-I535 using Tapatalk 2
ShazzyK-IDEOS said:
Your phone is Soft Bricked not hard bricked, otherwise it wouldn't even turn on, Use A USB JIG to force it into download mode, then reflash with Odin.
Click to expand...
Click to collapse
Yeah, this morning it won't even turn on no Samsung, no hope. Lesson learned... hopefully not a very expensive one.. :fingers-crossed:
Aminarra said:
Yeah, this morning it won't even turn on no Samsung, no hope. Lesson learned... hopefully not a very expensive one.. :fingers-crossed:
Click to expand...
Click to collapse
Pull the battery, put it in and let it charge for a while couple hours. Then hold vol - , home and power. If it week go into download/Odin mode you're fine. If so then go to the development thread stickies and follow droid style guide section 6
Sent from my SGS3 running Eclipse Touchwiz
Great thought, but let me tell you before my Galaxy S3 I owned a Wildfire S, tinkered with it every bit, OC,Rom,bootloader and everything, before that I owned a Huawei U8150, my first android, I literally went bezerk modding that thing. So, I'm not a noob at this,I was a noob at this different Carrier different software kinda thing, I thought the phone was the same and indeed it is, but the difference is that the Verizon's Bootloader is locked. I'm well familiar with everything, I just messed up by not researching that if the bootloader was unlocked already, mainly because I was a bit too excited about getting my S3.
1ManWolfePack said:
If you're such a noob and unprepared for a brick, maybe you shouldn't have ventured down custom ROM/unlock avenue?
Just a thought.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
tallgrasshawk said:
Since it's only a couple days, take it back into USCC store. You're in your 15 day Window, they should swap it for a new one. Act dumb, don't tell them you rooted it. Just say you heard it buzz and it died. They'll mark it down as defective and give you a new one
Click to expand...
Click to collapse
Yup!

Verizon S3 Wont turn on after proper rom flash

Ok, Phone was rooted suscessfully, Unlocked bootloader, was running a 4.2.2 Rom.
Buddy found the MS HD 10.0 Rom and wanted to try it. US phone. I looked at all the details and didnt see anything about it not being compatable.
Flashed the rom, went through all the GUID steps selected roms , styles etc etc, and It said completed "click here to reboot" So i did so.
Went black screen and now wont DO ANYTHING. cant get into download mode, recovery, a vibrate out of the phone, anything. Took the battery out for a min and plugged it in and get the orange light. Put the battery back in and STILL NOTHING. Please help! Buddy phone and he needs it
It's best to think of the international gs3 and us gs3 as two different phone. Because they are.
Flashing firmware meant for a different phone will result in a hard brick. Sorry
corbn89 said:
It's best to think of the international gs3 and us gs3 as two different phone. Because they are.
Flashing firmware meant for a different phone will result in a hard brick. Sorry
Click to expand...
Click to collapse
So its Done? :/..... He has a best but warranty . any way they can tell its been software tampered with at this point? So he can get a free one lol
As was said above, MS HD ROM is for the international S3 (i9300). It is important to make sure you are in the right forum before downloading and flashing any ROMs. Unfortunately, many still make this mistake. The only way to fix is to replace the phone or send it to these guys:
http://mobiletechvideos.mybigcommerce.com/
You can try and send it for JTAG repair (places like mobile tech) and they may be able to revive it.
But I'm not sure if places like best buy can positively confirm it was a bad flash if the phone is completely dead. I wouldn't think so but I'm not 100%
corbn89 said:
You can try and send it for JTAG repair (places like mobile tech) and they may be able to revive it.
But I'm not sure if places like best buy can positively confirm it was a bad flash if the phone is completely dead. I wouldn't think so but I'm not 100%
Click to expand...
Click to collapse
How about the Download Jig
If you are talking about Black Tie Insurance from Best Buy then you are fine and this is not fraud. Insurance is for boo boo's like dropping, smashing, flashing failures, drop in the toilet...all of that. They do not care if phone was rooted or misflashed. Insurance is not fraud, trying to get free replacements from the carrier under warranty by lying is.

My Phone turn off suddenly, help me please!!

Hey guys. I have a problem I tried to speak Spanish as forums but got HTCMania solve anything.
Before I thought it was problem of CM 11 that I turned off the phone suddenly (not restart, it shuts down) and occurred 1 time every 3 or 4 days, now increasingly occurs more often, yesterday I turned off the phone 6 times, this night while sleeping 3 times went out. It made me late for work again because the phone was turned off and the alarm did not go off ... following tips, did not solve anything. I factory reset everything I installed the stock ROM without root or anything, I installed Paranoid Android, SlimKat, Illusion ... nothing, with all the ROM I just turn off the phone. Not have more than 3 ½ months of use and this has been happening since 1 month. I gather it can be battery problem or the device itself, but it is something that has no solution for me. I live in Venezuela and bought me phone my mother and sent from Spain, along with the bootloader already unlocked, the warranty is not going to accept me or have possibility to send. I have searched a thousand Internet sites (Venezuela because the outside you can not buy anything here) and I do not find the battery moto G, to buy and to me installed in a technical service, but even on Amazon U.S. found nothing .
I fell into despair because I can not find any solution, I've calibrated the battery and also keeps shutting off, so I already was without resources, ideas and nothing to do but to stay with the phone and continuously be aware that if the phone turns off,,,, I have to turn it on again, buy an alarm clock to not be late for work again.
Continue pending if anyone can give me some solution, try anything, because nothing I lose ... buy a phone in this country is an impossible task because notice that a regular phone range Moto G (which is cheaper) costs Complete 4 months my salary.
Again thank you very much for your help and am awaiting any news that they can provide me. Hughs
I can't help you, nor I'll even bother trying.Your phone probably has some hardware fault ( too much gaming on it? ).
But what I wanted to tell you is that, you shouldn't have screwed around with your phone, if you can't afford to lose it. You should have never unlocked the bootloader in first place.
A lesson has been learned.
liveroy said:
I can't help you, nor I'll even bother trying.Your phone probably has some hardware fault ( too much gaming on it? ).
But what I wanted to tell you is that, you shouldn't have screwed around with your phone, if you can't afford to lose it. You should have never unlocked the bootloader in first place.
A lesson has been learned.
Click to expand...
Click to collapse
I unlocked the bootloader because I live far from the site where phone was bought. if phone got any problem I can't send it to warranty anytime so whats suposed I must to do? to be on stock frimware and don't root my phone? so all we must do that? then can't understand why there are lot of scene about root ROMs and all that. of course I know my rosks when I unlock my bootloader and root my phone but is my decission, if noone must unlock the bootloader then this kinds of forums would be useless.
Anytime, this community is the best for this kind of scene, root, ROMs and all around that.
I didn't play too much just played a bit, you really think that suposed hardware problem is because I rooted my phone? I bought it 3 1/2 mounth ago and I didn't have any problem, just 1 mounth ago started with this. I think is a factory problem, maybe hardware maybe battery, but not around root or ROM installed.
I was asking just because maybe someone got the same problem and can help be. I appreciate your cooperation like all kind of cooperation but need solutions, not lessons of what I souldn't do.
Thanks anytime
Replacement batteries can be found on eBay. I'd try that first.
SbM_ said:
Replacement batteries can be found on eBay. I'd try that first.
Click to expand...
Click to collapse
They can't import stuff there that easy, thats one of his main problems.Probably eBay is not an option for him.Not 100% sure about that tho.
liveroy said:
too much gaming on it? ).
You should have never unlocked the bootloader in first place.
A lesson has been learned.
Click to expand...
Click to collapse
What are you saying??? Are you kidding?!?
gaming on a phone dont destroy it :/
"a lesson has been learned" nope because he did not understand what happened
1- you should fomated all your phone ( use TWRP recovery), then flash stock Firmware.
2- after that,you turn off your phone BY YOU and plug chager for 1 day.
3- restart your phone and check.
4- it's my solutions. :thumbup: ,hope it's help.
Sent from my XT1033
agalam84 said:
I unlock my bootloader and root my phone...
Click to expand...
Click to collapse
as u wrote seems an hardware problem so not solvable itself.
u can relock the bootloader the bootloader and remove warning at boot if u want maybe motorola accept it in warranty, i havent clear if u can sent it to them...
when your problem start? after that u did something or itself, maybe something with bootloader
i hope u can solve your problem
AXD96 said:
What are you saying??? Are you kidding?!?
gaming on a phone dont destroy it :/
"a lesson has been learned" nope because he did not understand what happened
Click to expand...
Click to collapse
With that said, I don't think you'll understand even if I paint it for you.
Try reading my post again, give it a thought for a while, eventually it will come to my mind what I'm saying and why.
liveroy said:
With that said, I don't think you'll understand even if I paint it for you.
Try reading my post again, give it a thought for a while, eventually it will come to my mind what I'm saying and why.
Click to expand...
Click to collapse
sorry I do not want to be rude but he want a solution not a moralist

Categories

Resources