I have read a few articles/post about flashing samsungs new udate from their website for the i920. I think the only thing the update does is patch the radio(qualcomm) for people who have been getting dropped calls or not receiving calls from time to time. After reading about some phones being bricked during the update, I decided to go ahead and try it myself as i have been having some minor issues with not receiving some calls.
Sure enough, during the update process the upgrade froze while at 31% during the update. I let it set for about 30 minutes and nothing ever happened so I had no choice but to unplug the usb cable and try to do a hard reset. My phone was totally bricked and I had to get a replacement today. I even tried flashing a custom rom to try and recover it and no luck.
It turns out that the upgrade provided by samsung is not an official one approved by verizon according to the VZW tech in the store. When I took my phone in I told them that it had just froze over night while I was charging it and that's how it was when I woke up in the morning, becuase I did not know if they were going to try and screw me over or not.
So I highly recommend that you stay away from this update if you can. IMHO it is not worth the trouble. Just wait for verizon to release an update.
I am sure this is posted else where but I wanted to have this in the CDMA section so that other users could easily see it, and they do not have to go through the trouble I did today.
I had no problems flashing the update. However, I also had no trouble with dropped calls BEFORE flashing the update, but started having dropped calls after the update.
So unless you are already having issues which need a fix, I would have to agree with das, and say wait. There is the bricking risk, plus it may cause more issues than it solves.
samsung has temporarily pulled the update from their site. Maybe they are fixing it so it does not screw up your phone...LOL..I hope so becuase usually when my wife calls me she has to do it twice as the call is dropped before I can answer it or my phone some times does not ring at all. It's not a constant problem but it is annoying.
Agreed on issues w/ ck24.
The update damaged my first i920 during flashing. Used Vista prem 32-bit following Samsung's official PDF and no SD card in unit. Doing some searching on the net shows that even if you follow the detailed instructions from Samsung's PDF, it may stick the phone @ 31%,. While not technically bricked, you'll have to use Octans (not mini) and Shemmy's help on Modaco, to get it back to OEM ROM. This happened to my first Omnia II (i920), VZW promptly gave me a replacement by just telling them the unit stopped working (which it did, after getting stuck @ 31%).
I originally flashed the first unit due to that unit not sending texts if a user leaves my local VZW cell tower (say like if they are in another state or out several cities away). The update fixes issues w/ the Qualcomm radio (secondary PDF stated this on Samsung's site, before they took it down). VZW's techs are completely unaware of the issue apparently, as they show/feign ignorance when asked about the update and the issues w/ the i920. This is unnacceptable on Samsung's part for not having better quality assurance before releasing it, and on Verizon's part for not having informed techs. The failure rate for the Samsung update is so bad, that as stated earlier, they temporarily removed the update from their site, do a search for the i920 on their site and scroll down to "software" at the bottom, then on "Install Guide, Others" and you'll see it's "temporarily unavailable". I'd wait till it's posted on VZW's official site for the phone @ supportdotvzwdotcom/clc search for "Omnia II." Just like they did w/ the i910.
I have successfully used Wozzer's Stock ROM to flash back to the original ROM via OCTANS. Found on the Modaco site.
Link to Wozzer's repackaged stock ROM 21863 (no changes made):
http://www.4shared.com/file/206401811/dae1c8b0/FlashRom.html
Robtao said:
I have successfully used Wozzer's Stock ROM to flash back to the original ROM via OCTANS. Found on the Modaco site.
Click to expand...
Click to collapse
Good job man, this is exactly to what I was referring to. I'm unable to post links until the noob lock is off, but I was referring to a specific post on Modaco under the i8000/i920 section. In it, Wozzer had done all the hard work w/ the stock ROM, and Shemmy successfully tested it to revert an update damaged i920 back to stock w/ Wozzer's ROM. I too can attest to successfully using Octans (not the mini one) to bring the phone back w/ this ROM. As long as the phone turns on (even to that "connect to PC" error screen), it'll work.
Getting the radio properly fixed however, that's another story. Will still wait for VZW to post the official Samsung (fixed) update on their i920 support section. Hopefully then I can get my Qualcomm radio working fine on this (my 3rd, and not by my hand) Omnia II.
I have sent my sensation back for repair after totally bricking it in the process of returning my device to s-on.
My phone was completely dead, no response from charging, no response from computer adb, fastboot just DEAD!
I tried to supercharge my battery to make sure the recovery was not to blame but no joy there either.
My question is, with my phone in this state, will htc repair be able to tell that i have voided my warranty?? I told them that this happened during an ota update
Any opinions or comments from those who have done the same would be appreciated.
bobsie41 said:
I have sent my sensation back for repair after totally bricking it in the process of returning my device to s-on.
My phone was completely dead, no response from charging, no response from computer adb, fastboot just DEAD!
I tried to supercharge my battery to make sure the recovery was not to blame but no joy there either.
My question is, with my phone in this state, will htc repair be able to tell that i have voided my warranty?? I told them that this happened during an ota update
Any opinions or comments from those who have done the same would be appreciated.
Click to expand...
Click to collapse
Hi,
Sorry to hear about your predicament.
Did you actually manage to get S-ON ?
If not ,then it will be obvious what you have done.
No point in lying about it .
Just come clean or they will think you are taking the p*$$
malybru said:
Hi,
Sorry to hear about your predicament.
Did you actually manage to get S-ON ?
If not ,then it will be obvious what you have done.
No point in lying about it .
Just come clean or they will think you are taking the p*$$
Click to expand...
Click to collapse
I bricked my phone in the final step of returning to s-on...fastboot reboot-bootloader.....ok.....no response from phone DEAD.
Since posting i have checked the tracker for my phone repair and it says that it has been shipped today with no mention of cost. Obviously i haven't recieved the device yet but it looks very promising.
After reading many nightmare stories regarding htc uk repair service, if the information that i have just seen on the tracker is true i.e. phone recieved on 22nd. - dispatched on 23rd., i think that is excellent service especially considering the nature of the fault.
I'll be more buoyant when the phone is in my hands though!
malybru said:
Hi,
Sorry to hear about your predicament.
Did you actually manage to get S-ON ?
If not ,then it will be obvious what you have done.
No point in lying about it .
Just come clean or they will think you are taking the p*$$
Click to expand...
Click to collapse
Yes, they will try to find every reason to make sure the repairs are not covered under warranty...if they dont, then you can say it was your Good Luck!!!
bobsie41 said:
I bricked my phone in the final step of returning to s-on...fastboot reboot-bootloader.....ok.....no response from phone DEAD.
Since posting i have checked the tracker for my phone repair and it says that it has been shipped today with no mention of cost. Obviously i haven't recieved the device yet but it looks very promising.
After reading many nightmare stories regarding htc uk repair service, if the information that i have just seen on the tracker is true i.e. phone recieved on 22nd. - dispatched on 23rd., i think that is excellent service especially considering the nature of the fault.
I'll be more buoyant when the phone is in my hands though!
Click to expand...
Click to collapse
Hi,
Hope all goes well.
Well, as I know, some people sent their sensation back to repair with ENG OFF and did not really got into any trouble with warranty problem.
Think about it...How would they know? You cant get the phone to boot up, so how would they? They will just reflash the phone through the original process or replace the board inside. They dont have the time and money to go looking for evidence of you voiding the warranty. Its cheaper for them to reflash the phone than to see what you did. Not sure how they do it, but I know they have a method that most of us cannot do. Wont cost them much, at all. Im sure its related to a jtag. They will hook up the board to a device that will reflash the software.
Matt
Just an update to the situation.
I recieved my phone back today fully repaired, new PCBA-mainboard etc. etc. un-branded, un-locked. Was told it would have the latest os installed but came with 2.33 but i've successfully upgraded it. Now to play (a lot more carefully this time!).
For those who totally brick there phone like i did, take heart from my escapade but, perhaps i was just lucky!
Hey guys. I have a chance to pick up a mint sensation locally for a cheap price. The seller is under the impression it is bricked. I've read through the threads for a while now but thought I would ask for some help/advice. The seller told me that he bricked the phone by trying to unroot it but has also said he was trying to "flash boot or something." He has made it clear that the phone will not turn on or show any signs of life. He has tried multiple batteries as well.
So, is there any way to ensure it is bricked? I had thought that maybe he messed up flashing a new rom.
If it is clearly bricked, what would be a good price to snag it for?
Would it be possible to buy it and contact HTC in regard to the warranty? What would this cost?
Thanks in advance,
PS; I have read about the inablility to charge after flashing CWM. I'm not sure if CWM was installed or not. I will ask that asap.
Sounds like an inappropriate file was flashed to hboot, in which case it's dead. Short of jtagging there is no way to fix it.
Thanks for the quick reply globatron. That sucks to hear that it probably is fried. Would the HTC warranty cover this type of repair?
MRpeabodyia said:
Thanks for the quick reply globatron. That sucks to hear that it probably is fried. Would the HTC warranty cover this type of repair?
Click to expand...
Click to collapse
No, they wouldnt as it was from user error.
Matt
Do you know for sure they wouldn't cover it? All morality aside it could be argued that it wasn't user error considering I'm not entirely sure what the seller did to it.
MRpeabodyia said:
Do you know for sure they wouldn't cover it? All morality aside it could be argued that it wasn't user error considering I'm not entirely sure what the seller did to it.
Click to expand...
Click to collapse
Well,morality aside you can always tell them that the OTA update bricked it.If you are a TMOUS customer you can try and contact T-mo first.They are usually easier to deal with than HTC.
NYCguy I read through your thread discussing your dealings with Tmous. I had thought about contacting them but they have been a huge pain for me lately. (Almost to the point of ending my contract). I shot HTC an email out of curiousity so I should hear back from them soon. I've had to replace a phone before via T-mobile and it was pretty smooth. I just don't want to do it all the time as this may look odd on their end.
NYCguy I read through your thread discussing your dealings with Tmous. I had thought about contacting them but they have been a huge pain for me lately. (Almost to the point of ending my contract). I shot HTC an email out of curiousity so I should hear back from them soon. I've had to replace a phone before via T-mobile and it was pretty smooth. I just don't want to do it all the time as this may look odd on their end.
Well I bought my "bricked" sensation. I spoke with the seller for a while and it seems he had rooted it, received notification of the OTA, and attempted to unroot it. He didn't give me specifics on the procedure he used but I'm going to read as much as I can, depending on when my monster child will let me, and attempt to fix this thing. I read about the battery tricks and will try those tonight. Any suggestions as this point guys?
Well after reading and tinkering with this thing for a while it seems I have the dreaded qhsusb brick. I already spoke with HTC and it is under warranty until November of 2013. My new question is, Will HTC be able to tell the device was ever rooted? A rom was never installed so it should be stock. Seems the seller made a mistake in trying to go from s-off to s-on. Just hoping I won't have to pay much to have a new one sent from the manufacturer.
Thanks
MRpeabodyia said:
Well after reading and tinkering with this thing for a while it seems I have the dreaded qhsusb brick. I already spoke with HTC and it is under warranty until November of 2013. My new question is, Will HTC be able to tell the device was ever rooted? A rom was never installed so it should be stock. Seems the seller made a mistake in trying to go from s-off to s-on. Just hoping I won't have to pay much to have a new one sent from the manufacturer.
Thanks
Click to expand...
Click to collapse
Well if it's a QHSUB brick that means the phone is truely DEAD.If you can't boot into bootloader,can't charge it and can't connect to a PC,then i don't see how could they tell if it was rooted or not.There is no way for them to tell.You just tell them you bricked it while trying to install the OTA update,or do as i did and contact T-mobile.
Good luck!
Thought I would update this thread for anyone who may stumble across it at a later date. I went ahead and sent my bricked phone into HTC. They repaired the phone and sent it back. I was suprised to see that they didn't send me a refurb.
I have to say that HTC were very easy to work with were quick in returning my phone.
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.
Hi,
I am sorry if this is a reproduction but, I am faced with a problem.
I am using an unlocked HTC One X at&t phone in India.
I had rooted the phone and tried to update the latest jellybean update from HTC website which, I could not.
Then, I read that it could be done on un-rooted phones so, I un-rooted the phone and tried doing the update.
The updated completed successfully but now, it is just switched off completely. Battery level was more than 60% while updating.
Now, the phone just wont start. Nor, does the led indicate the phone charging. There is no activity whatsoever. I tried charging it for more than 10 mins to check if its a battery issue but no indication whatsoever.
Kindly help me.
I apologize if I have repeated the question but I could not find an exact question to my issue.
Kindly provide solutions.
harshadbarge said:
Hi,
I am sorry if this is a reproduction but, I am faced with a problem.
I am using an unlocked HTC One X at&t phone in India.
I had rooted the phone and tried to update the latest jellybean update from HTC website which, I could not.
Then, I read that it could be done on un-rooted phones so, I un-rooted the phone and tried doing the update.
The updated completed successfully but now, it is just switched off completely. Battery level was more than 60% while updating.
Now, the phone just wont start. Nor, does the led indicate the phone charging. There is no activity whatsoever. I tried charging it for more than 10 mins to check if its a battery issue but no indication whatsoever.
Kindly help me.
I apologize if I have repeated the question but I could not find an exact question to my issue.
Kindly provide solutions.
Click to expand...
Click to collapse
It's bricked. S-ON + Super CID + OTA or RUU is a full on brick. You can try the unbricking thread but the chances of it working are low, you would need a linux boot disk/USB
Ultimately, you'll probably need to JTAG. There are some online companies that will do it for ~50.00USD
exad said:
It's bricked. S-ON + Super CID + OTA or RUU is a full on brick. You can try the unbricking thread but the chances of it working are low, you would need a linux boot disk/USB
Ultimately, you'll probably need to JTAG. There are some online companies that will do it for ~50.00USD
Click to expand...
Click to collapse
Oh Man!!
Could this procedure be any easier?
Thanks but i guess your diagnosis is right.
The thing is, we dont have many in India who can do all that.
Gotta figure out what to do with my piece now.
harshadbarge said:
Oh Man!!
Could this procedure be any easier?
Thanks but i guess your diagnosis is right.
The thing is, we dont have many in India who can do all that.
Gotta figure out what to do with my piece now.
Click to expand...
Click to collapse
Nope, can't be easier, that's one of the reasons rooting isn't recommended for most people.
Hm, I always thought the tech scene was pretty big in india. Guess I stand corrected.
exad said:
Nope, can't be easier, that's one of the reasons rooting isn't recommended for most people.
Hm, I always thought the tech scene was pretty big in india. Guess I stand corrected.
Click to expand...
Click to collapse
Yeah; it is but that all is on the software side.
Not many out here tinker with hardware nor bother to open up cell phones. Its a use n throw policy out here.
Well, it is a welcome change without connectivity for a day now. I want my phone to start up though.
harshadbarge said:
Yeah; it is but that all is on the software side.
Not many out here tinker with hardware nor bother to open up cell phones. Its a use n throw policy out here.
Well, it is a welcome change without connectivity for a day now. I want my phone to start up though.
Click to expand...
Click to collapse
There's a few online companies that do it. You'd need to mail the phone out of course. There's one that's popular that keeps getting mentioned on here but I can't remember their name. Good Luck!