[Tutorial][Bell Atrix]What need to be done before Warranty Service?
It applies all the Bell Atrix, doesn’t matter you have Orange FR 2.1.1 or UK 2.2.3 on the phone or whatever
Simple Version:
Make sure you have CWM Recovery on it(http://forum.xda-developers.com/showthread.php?t=1019143)
Download the stock system.img (http://www.multiupload.com/T6L5RS2WH1), if you have the backup by nandroid, you can skip this step
Enter CWM Recovery to restore system.img only, then do Wipe out Data&Cache, or Force Close will be with you!
Install GingerBreak to root your phone, you can download from here: http://forum.xda-developers.com/showthread.php?t=1044765
Install CMW Recovery again, but this time, choose CHARGE MODE in order to uninstall the custom recovery
Use GingerBreak to un-root the phone
Do a factory again, then you are ready to throw this phone to any Bell Retail Store for repair
Just remind that Bell will take 4~6weeks to get your phone fixed, if you need a loaner phone, it’s $25+tax, ask before borrow since some store doesn’t even have smartphone to lend…
Full Detail Version coming soon...
Thanks, good tut to have.
Stock Bell Atrix on Rogers with updated radio, Rooted, deodexed, Honeycomb theme, and frozen!
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
hoodlikegaza said:
Why wouldn't you just a sbfflash...?
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Because there is no Bell SBF available (to date)
scorneil said:
Because there is no Bell SBF available (to date)
Click to expand...
Click to collapse
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
thegregulator said:
Yes, but in your tutorial you're just removing root access and custom recovery. You're not changing the firmware from the phone back to 0.3.7 (Bell firmware) because there isn't a Bell SBF to flash (you're right about that). If one was already running 2.1.1 or 2.2.3 with root access, they could simply reflash their respective SBF's and it would produce the same results as your tutorial. Maybe I'm missing something from your guide, but as far as I understand, once you've flashed a different SBF, there is no way of getting back to official Bell. Your guide seems to be a roundabout way to get back to stock 2.1.1 or 2.2.3 for warranty purposes, while a simple reflash would produce the same results.
Click to expand...
Click to collapse
You are right, however stock system.img(from original bell firmware, not 2.1.1 or 2.2.3) already has the right prop file and bell bloatware, comparing 2.1.1 or 2.2.3, im too lazy to look for bloatware and changing by root. this seems the easiest way for me.
other than the radio version, i dont think motorola could find out this is flashed Atrix but anyway, I am still waiting for my atrix back
ks2hot4u said:
With glad root and webtop mod on stock firmware would it be ok to just return the stock web top files and unrooted for warranty?
Click to expand...
Click to collapse
better do a factory reset and unroot
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
But thats the thing if you brick your device, this guide won't help as the phone is a brick.
As for hardware issues, this is the exact reason for this thread IMHO, something useful to me as my fingerprint reader is slightliy off physically which results in the device thinking that fast swipes are taking place when they are not. now I can use this when I am ready to take my device in without being harrassed about software.
With my N1 even with the bootloader unlocked they still took in the device if it was proven to be a hardware defect (again had a problem with my power button - just my luck i guess) Doubt bell would do the same.
binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
who would use this for anything other than a hardware issue? anyone who can follow this guide can also follow a SBF flash instruction to solve their software issues
binary110 said:
I work for bell. and all I have to say about this thread is that it should be closed and deleted. I actually thought these kind of guides were frowned upon...
If the phone was working 100% before you starting screwing with it, we shouldn't have to honor your warranty. Thats why ROOTING VOIDS Warranty.
If you screw up your windows load, Best buy doesn't say, heres a new pc. They say, here's a bill for the techie. We work on commission in these stores, and i hate wasting my time with some moron who shouldnt have screwed with what he couldn't fix. /rant
Its annoying to deal with people who brick their phones, and then give bs excuses as to why its not working. I usually do my best to help people, but its better to tell us the truth and have us help, then lie through your teeth that its a problem with the device.
It costs me extra hours of work to deal with DOA phones, and it costs everyone including motorola tons of $$$ for stuff that is screwed up by the consumer.
Why can't the people who don't know what theyre doing, leave the dangerous stuff to the guys who know how to fix their own problems?
Edit: the exception to this is true hardware issues. But those don't seem to come up all too often with this phone, just battery life issues.
Click to expand...
Click to collapse
QFT, but......we are referring to hardware isssues here, not software.......and rooting has nothing to do with that.
Sent from my Blue Myst GladiAtrix on Bell using the XDA Premium App.
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
binary110 said:
I agree, its totally cool for hardware issues, but i'm thinking about the guys who have the lower half of the touch screen not working because they screwed the software up. 9/10 issues with any smartphone is software related.
Click to expand...
Click to collapse
since no one seems to be able to replicate this issue (to my knowledge) that would imply that it IS hardware related and not software
Rediculous
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
binary110 Your completly in the dark if you think this phone or any other smartphone wont have defects and hardware malfunctions.
My Atrix has wicked bad screen response when plugged into any power source with stock charger or other... im not returning mine as this is a minor issue. Although my roomates cant hold gps, drops calls constantly, misses calls and msgs for lack of signal and has constant reboots since stock with only root to obtain webtop mod.
So according to your logic he dosent deserve to have his 500+ $ phone replaced cuz it will cost motorola money and your lazy ass some commision ??
THIS IS THE WRONG FORUM FOR YOU !
Click to expand...
Click to collapse
I never said the phone was not capable of being defective. I said that when someone brings it in for an issue that they caused themselves. The phones are more often screwed up by a customer, than they are actually defective.
90% of the charger issues are from using a charger different than the motorola one that came with the phone. Especially the ones with the screen response. I noted it on my atrix as well. I also have replaced a customers phone for this.
This IS a valid reason to replace the phone.
But this is also easily noticeable BEFORE you go through the process of rooting/modding the phone. and as such, you should take it up with the place your purchased it before modding it.
Its like buying a car, ripping the engine apart right away. only to find that it runs like crap after you've ripped it apart... You probably should have done a test drive before purchasing. Do you understand what i mean?
Furthermore, your friend has a legitimate issue, I'm talking about people who brick their phones and play stupid. As well, I can tell you're a part of the generation who feels they're entitled to everything under the sun from the carrier you deal with. Yet, no cable company fixes your damn television. And especially not if you screw it up yourself.
Its not apples to apples, in the sense that the cable company doesn't subsidize your tv. but even if you got a tv as a promotion through them, they'd send you to the manufacturer. Which is what i'd prefer to do with people who do stupid stuff and want it fixed.
Don't act like my time isnt worth money just because youre a needy consumer. What i'm saying is just man up, tell us you screwed it up, and we will do everything we can help.
For you to be trolling the way that you are, its obvious that this ISNT THE FORUM FOR YOU.
Thank you.
By the way, Watch your language on the forums.
seven2099 said:
absolutely true.
best chances for full repair is flash stock SBF 2.2.3 and then if you really wanna get technical, simply edit your prop file for cosmetic purposes.
NFHimself has this crazy way of flashing close to stock images but thats pretty much retarded as there's no point as it really doesnt mean any closer to stock than this crap and is fickle/easy to detect as it is if Motorola was looking for it.
Click to expand...
Click to collapse
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Be nice guys... We are all Canadian, we love peace, don't we?!
In my case, my touchscreen's digitalize is 100% broken, it's either hypersensitive or non-sensitive at all... It happened on Bell Stock rom but I was trying to flash sfb to see if it could be fixed...
Unfortunately, i got my repair back today and still the same issue, i asked the bell staff to try the touchscreen and she said the phone is not boot up properly...
Oh well, after 90s, I ask her to try again, she clicked "BACK" 10 times in order to get back, and 5 times to run Bell Self-serve
well, I really unsatisfied with the result and I had to left the phone there and waiting for another 2 weeks, AGAIN!!!
I have 3yr contract with Bell so it has to waste time and money to get my phone fixed cuz its carelessness and impatience are wasting my money and time... The $30 loaner phone sucks and cannot even been changed...
well, looks like a little away from the topic but I've just out of the store...
even according to the repair menu, the bell stock sbf has been applied on and change of the part which i know its not the digitalize, the phone is still unusable...
AT&T users are lucky since they have their own stock sbf to flash when they wanna a repair but poor Bell users they have to use those tutorials like mine to do repair, OR UNLOCK THE BOOTLOADER AND I WONT ASK FOR WARRANTY
btw, maybe that's the reason why Apple is cool, they can get your iPhone replaced in maximum 60min not 60days even there is just a dust in screen
NFHimself said:
Uhm, what? How did I get dragged into this PMS fest?
Ridiculous.
Click to expand...
Click to collapse
see what you caused?
jk
I understand where binary was coming from but again this thread isn't for that reason. At the same time I bet we can all say we wish carriers like bell and rogers were completely full of staff like you that come with the line we will do whatever we can to help. most times reps come off as just going through the motions or looking for whatever reason to close the case.
So I was on atomic fusion and tried to flash another gb rom. Somewhere during the odin process it seemed to be stuck and I stopped it and tried again to get a red screen of death. I tried everything to get to d/l mode but nothing. So I called att and I have about a week left in my warranty so I went that route. Am I gonna be charged 400 dollars when they find out I was rooted with roms not theirs? I'm really nervous, I should have never flashed to gb, its to freeking complicated for me to understand all the bootloading and kernal stuff. Any thoughts or experiences to help ease the pain? Thanks
Prolly shouldn't have flashed if you weren't confident. In yourself.
Sent from my SGH-I897 using XDA Premium App
If your phone shows any signs of life they will most likely be able to tell that you are not stock.
Your fine, I did the same thing as you are doing. I just acted like a clueless idiot and they never suspected a thing, but it was with Rogers not AT&T.
Sent from my Galaxy S Firefly 3.0
For all the topics asking this question I'm yet to see anyone come back saying that they have been refused, or charged extra after a new one is already sent out. In all likely hood they don't even check because they don't really care. If it is a hardware issues they are gonna have to swap pieces or even the main/motherboard which will come with stock pre-loaded at factory. If it is software they will just use what ever method they designed into the phone to force rewrite over what was in there before.
Now if you were taking it to a service center, where they are going to take a look in hopes of getting that very phone back into a working condition then maybe... just maybe. But if the phone does not boot then they are just gonna add it to the rewrite pile and give you a referb (or new if you ask nicely enough). This is why they always say "you might lose all your data so make a backup before hand."
Thanks, that makes me feel better, now all I have to do is survive a couple days without it. I won't be making that mistake again. What did I do wrong? I had no problem going from phoenix ultimate to atomic fusion. I was gonna try to go to cog5, I thought I was doing it right. All I did was use the odin that it said to use and it seemed to be stuck. What do you do when it freezes up during the odin process? Are you screwed no matter what you do? Should I have used the odin that takes you to stock 2.1 first? I'm really trying to understand all this but there's just so many ways about everything.
I bought a brand new Note 4 from my local T-Mobile store. I rooted it, and only added Wanam Xposed.
I used Wanam to hide my root status so that I could use T-Mobiles softcard payment app.
I wanted to sleep for an hour, and I shut off my phone. When I woke up, I turned on my phone, and it got stuck on the white T-Mobile screen.
I could not get by it. I pulled the battery, etc, and it only would boot to the white t-mobile screen,
I was able to restore the phone to original with Samsungs online restoration program.
Here is my concern. Do I have a defective phone? I think I can still return it. (They may charge me $50.00)
The phone works now, but im just worried that I might have a bad one? Could it be defective? or did I cause the freeze by installing Wanam? or something else I did?
I would appreciate your comments and advise since there are many people on xda with much more experience and technical knowledge about this than I have.
Thanks in advance!
Mr Global said:
I bought a brand new Note 4 from my local T-Mobile store. I rooted it, and only added Wanam Xposed.
I used Wanam to hide my root status so that I could use T-Mobiles softcard payment app.
I wanted to sleep for an hour, and I shut off my phone. When I woke up, I turned on my phone, and it got stuck on the white T-Mobile screen.
I could not get by it. I pulled the battery, etc, and it only would boot to the white t-mobile screen,
I was able to restore the phone to original with Samsungs online restoration program.
Here is my concern. Do I have a defective phone? I think I can still return it. (They may charge me $50.00)
The phone works now, but im just worried that I might have a bad one? Could it be defective? or did I cause the freeze by installing Wanam? or something else I did?
I would appreciate your comments and advise since there are many people on xda with much more experience and technical knowledge about this than I have.
Thanks in advance!
Click to expand...
Click to collapse
No need to return the phone, as you were able to restore it. The freeze was likely caused by something you installed that didn't play nicely with another app/program. Fresh install and make sure to pay close attention to what you're putting on your phone, and what settings w/i Wanam may or may not bork something else. Enjoy!
Mr Global said:
I bought a brand new Note 4 from my local T-Mobile store. I rooted it, and only added Wanam Xposed.
I used Wanam to hide my root status so that I could use T-Mobiles softcard payment app.
I wanted to sleep for an hour, and I shut off my phone. When I woke up, I turned on my phone, and it got stuck on the white T-Mobile screen.
I could not get by it. I pulled the battery, etc, and it only would boot to the white t-mobile screen,
I was able to restore the phone to original with Samsungs online restoration program.
Here is my concern. Do I have a defective phone? I think I can still return it. (They may charge me $50.00)
The phone works now, but im just worried that I might have a bad one? Could it be defective? or did I cause the freeze by installing Wanam? or something else I did?
I would appreciate your comments and advise since there are many people on xda with much more experience and technical knowledge about this than I have.
Thanks in advance!
Click to expand...
Click to collapse
You have a defective xposed. No need to return it.
BAD ASS NOTE 4 & GEAR S
BACARDILIMON said:
You have a defective xposed. No need to return it.
BAD ASS NOTE 4 & GEAR S
Click to expand...
Click to collapse
Milagro you aren't telling people to just go return it
nano303 said:
Milagro you aren't telling people to just go return it
Click to expand...
Click to collapse
I only say that when people to stupid to take the advise given to them. Arguing that it can't possibly be the dirty flash they just did. They post to cry not for advice. So I give them what they wanna hear lol.
BAD ASS NOTE 4 & GEAR S
BACARDILIMON said:
I only say that when people to stupid to take the advise given to them. Arguing that it can't possibly be the dirty flash they just did. They post to cry not for advice. So I give them what they wanna hear lol.
BAD ASS NOTE 4 & GEAR S
Click to expand...
Click to collapse
People can be stupid man I agree lol. Do you think it's worth rooting my phone now? Was waiting for lollipop but my new laptop came in and I'm ready to root! Been waiting for 5.0 for a while
nano303 said:
People can be stupid man I agree lol. Do you think it's worth rooting my phone now? Was waiting for lollipop but my new laptop came in and I'm ready to root! Been waiting for 5.0 for a while
Click to expand...
Click to collapse
See this I would say depends. I have had the best battery life ever with stock. I rooted to remove bloat but it broke a lot. They tied everything together. So went back to stock and haven't moved. Gonna stay till official deodex 5.0 drops lol.
BAD ASS NOTE 4 & GEAR S
BACARDILIMON said:
See this I would say depends. I have had the best battery life ever with stock. I rooted to remove bloat but it broke a lot. They tied everything together. So went back to stock and haven't moved. Gonna stay till official deodex 5.0 drops lol.
BAD ASS NOTE 4 & GEAR S
Click to expand...
Click to collapse
Lol Wanam is now updated to work with 5.0. so really, what's a couple more weeks to wait. Don't want to go thru the hassle of downloading the whole update and Odin back to stock. Rather just let it drop via OTA. Honestly my first phone since the Evo I have not rooted yet. It's crazy because once I do. I know it'll be like having a new phone. Can't wait bud!
I just got my nexus 6, two and a half weeks ago. I am coming from a Verizon galaxy nexus, so I'm pretty good at unlocking, rooting, installing roms, and the like. I bought it at best buy because I broke my gn, and being they are the only ones that had any in stock, and I need a phone or im lost, I was on vacation visiting family. So I got the none branded one called Verizon got it up in running in five minutes after the 20 min wait to talk to someone.
The first few days I played with it as is never had a problem. So I unlocked it, rooted it and still not any problems. Then a few days later I noticed the speaker would crackle not big thing just noticed it. After that though another weird thing started happening if I answered the phone then decided to use speaker phone i could not hear the other person and they could not hear me, and going back off speaker didn't help till we hung up and recalled.. It does not do it ever time just sometimes.. I had not installed a rom just kept it Google 5.1.1, I really like the new Android. But I did unrooted, relock, factory reset. Then did it all again. Still get some of the problems but not as much. This last problem really pist me off. I had been in 4 states and service from Verizon was great in all but one of them. The one that it didn't not work in was in Missouri not even when I got to Springfield. It was late at night so none of the ton Verizon stores I seen were open, I could dial but not have net service. I tried restarting phone even did a factory restore after trying everything I could think of. That reset screwed me though because it made it a useless since I had no net and was unable to set it back up.. Also I couldn't stop at the ton of Verizon stores in the morning bc they didn't open till later in the day and I needed to get home. The weird thing is almost as soon as I crossed into OK the phone loaded up and started working internet and all.
So my question is, is this normal with these phones? And is their any way to make the radio better? It was on global in that setting so I switched to USA. Still seems to work fine now at my house.
Any help or tips would be much appreciated. Or should I try and do a warranty through Motorola?
I really like this phone and its a major improvement over the gn since we at Verizon got skipped with nexus 5. This battery is a beast 12+hrs doing a crap load of stuff on it rocks
Rbh50815 said:
I just got my nexus 6, two and a half weeks ago. I am coming from a Verizon galaxy nexus, so I'm pretty good at unlocking, rooting, installing roms, and the like. I bought it at best buy because I broke my gn, and being they are the only ones that had any in stock, and I need a phone or im lost, I was on vacation visiting family. So I got the none branded one called Verizon got it up in running in five minutes after the 20 min wait to talk to someone.
The first few days I played with it as is never had a problem. So I unlocked it, rooted it and still not any problems. Then a few days later I noticed the speaker would crackle not big thing just noticed it. After that though another weird thing started happening if I answered the phone then decided to use speaker phone i could not hear the other person and they could not hear me, and going back off speaker didn't help till we hung up and recalled.. It does not do it ever time just sometimes.. I had not installed a rom just kept it Google 5.1.1, I really like the new Android. But I did unrooted, relock, factory reset. Then did it all again. Still get some of the problems but not as much. This last problem really pist me off. I had been in 4 states and service from Verizon was great in all but one of them. The one that it didn't not work in was in Missouri not even when I got to Springfield. It was late at night so none of the ton Verizon stores I seen were open, I could dial but not have net service. I tried restarting phone even did a factory restore after trying everything I could think of. That reset screwed me though because it made it a useless since I had no net and was unable to set it back up.. Also I couldn't stop at the ton of Verizon stores in the morning bc they didn't open till later in the day and I needed to get home. The weird thing is almost as soon as I crossed into OK the phone loaded up and started working internet and all.
So my question is, is this normal with these phones? And is their any way to make the radio better? It was on global in that setting so I switched to USA. Still seems to work fine now at my house.
Any help or tips would be much appreciated. Or should I try and do a warranty through Motorola?
I really like this phone and its a major improvement over the gn since we at Verizon got skipped with nexus 5. This battery is a beast 12+hrs doing a crap load of stuff on it rocks
Click to expand...
Click to collapse
The speaker issue is definitely a known issue. RMA is the only solution.
Crap that really sucks. Thank you though for the reply. Do you know with the RMA if I have to send the phone back first and wait, or will they send a replacement first? Also do they replace with a new one or reman?
I was really hoping it was something in the settings
Rbh50815 said:
Crap that really sucks. Thank you though for the reply. Do you know with the RMA if I have to send the phone back first and wait, or will they send a replacement first? Also do they replace with a new one or reman?
I was really hoping it was something in the settings
Click to expand...
Click to collapse
Not sure, best to call and find out.
Rbh50815 said:
Crap that really sucks. Thank you though for the reply. Do you know with the RMA if I have to send the phone back first and wait, or will they send a replacement first? Also do they replace with a new one or reman?
I was really hoping it was something in the settings
Click to expand...
Click to collapse
May luck out and get new but at this point in the cycle probably refurb. Have to send in first or have creditcard they can hit for what it worth now to send first. Credit hit will be deleted once they show it coming back.