Odds of bricking N1 when flashing ROMs - Nexus One Q&A, Help & Troubleshooting

Hi all,
Got a burning question. I'd love to try some new ROMs on my AT&T Nexus One, but I'm afraid that I'll make the phone absolutely unusable and bricked when I do so. I just bought the phone and got it yesterday, so I'm obviously not wanting to waste that money.
So the question is, how likely are you to brick a phone when flashing ROMs, and if it gets bricked (or something else bad), is it possible (and how easy) to restore the phone to a usable state?
Thanks,
T.J.

Its difficult to brick, the only suggestion is to stay away from flashing radios unless you really have to. However, you should absolutely wait at least a month to make sure your hardware is in good condition, otherwise if you find out, after unlocking it, that your 3.5mm Headset jack has died you'll have no recourse. I didn't wait and now I have dust underneath my screen.

Okay, I figured it was only flashing the radio that would really jack things up. Do you have to do that for most ROMs, or do the ROMs that require it let you know in advance?
And right on, waiting makes sense. I'm just horribly impatient!

No ROMs for N1 that I know of require any particular radio. i.e. you can just leave it as the stock radio if you like.
As above though, it's worth waiting a little while to make sure you don't have any hardware defects you want to return the phone for.

GlenH said:
No ROMs for N1 that I know of require any particular radio. i.e. you can just leave it as the stock radio if you like.
As above though, it's worth waiting a little while to make sure you don't have any hardware defects you want to return the phone for.
Click to expand...
Click to collapse
Good deal. I'll give this a go for a month or so, make sure nothing's busted then look at flashing some stuff then. Thanks.

GlenH said:
No ROMs for N1 that I know of require any particular radio. i.e. you can just leave it as the stock radio if you like.
As above though, it's worth waiting a little while to make sure you don't have any hardware defects you want to return the phone for.
Click to expand...
Click to collapse
Kinda true there, but if you use the Froyo radio on older builds like cm 5.0.7, then the camcorder is broken and the phone will reboot if you try to use it.

futango said:
Kinda true there, but if you use the Froyo radio on older builds like cm 5.0.7, then the camcorder is broken and the phone will reboot if you try to use it.
Click to expand...
Click to collapse
I'll end up waiting for the official Froyo release anyways, since I figure they'll drop it before a month or so is up, then I figure there won't be any issues with the Froyo radio.

Related

AT&T Exchanges - Your Nightmare Stories!

Unemployed, in the middle of a job search, and my Tilt succumbs to the RLoD. Yay!
Looks like the only solution is to obtain a replacement phone from AT&T. As a flash-aholic (thanks, Dutty ), I'm really wondering about their replacement policy, as some have mentioned that they'll bill your account for the replacement phone in some cases. (I obviously refuse to pay for a replacement phone when mine is dead after only three months... much less pay full price for a refurb!)
It's been determined that this problem is NOT isolated to reflashed phones; since stock ROMs succumb to it as well, my flashing has nothing to do with the problem. Obviously, I can't flash back to the original ROM because the phone is a brick. However, because it's a brick, they won't know I've flashed a custom ROM until they repair it somehow.
So is the charge billed to my account only as long as it takes for me to return the broken phone? Is it only billed if I fail to return the broken phone? Will it show up down the road when they realize I loaded a custom ROM? (Again - unemployed, so can't afford to pay for another phone anyway.)
Finally, and most importantly - has anyone with the RLoD (or any other phone issue) returned a custom ROM-loaded phone to AT&T? If so, what was your experience?
Thanks so much - using my old Sony Ericsson Z500a for the past week has been ridiculous, and I really want to know if I can make the call to AT&T or not...
ok, well first of all pay attention to the warnings... 3 months old or not when you flashed the different spl, or cooked rom you voided the warranty.. yes the phone could be defective, but any manufacturer can refuse repairs or charge you for the repairs since it was flashed with a non htc/att rom..
As far as the return process... its an advanced type rma in 99% of the cases meaning they will ship you a refurbed unit with the materials needed to ship yours back... if they dont recieve your defective phone within so many days they will charge your account for the replacement(this is to prevent fraud, obviously). I have also heard in some rare cases where people were charged for the replacement after the repair facility notified of an unapproved rom/bootloader on the phone. and in some cases people get away with it...
so its 50/50 shot... i would do everything possible to return it to a stock bootloader and rom before sending back (which in your case you might just have to roll the dice..)
ive exchange many phones and i dont flash to stock roms and ive never had a issue
I was in the exact same position as you about a month ago. I got the RLOD about 4 days into using my tilt and it had been running the HTC stock rom for 3 days, I flashed it the day after I got it.
When the RLOD hit, I was really worried. I was in the 30 day return period, so all I had to do was take it to the store and get a new one. I knew they wouldn't be able to tell in the store, as the consumer and retail end is really non-technical. I was afraid that if they revived the phone at ATT tech or HTC that they would find out.
This said, I built a little contraption at work that hooked up to my 12v car battery and wires into the battery prongs on the tilt. I figured the tilt could handle 12v without catching on fire - it did. However, I'm completely sure they any data will be completely unrecoverable, and the only thing that will salvage is the case. I figured they have no way to call you on a total phone fry, because it could be lots of things that cause that. However, you should have heard the noise it made. I almost made a video, but it was too incriminating. 12v is devastating to a phone, it was cool! I cooked a 600 dollar piece of equipment and got a new one!
That was over a month ago, no word from anyone. Also, I saw on the RLOD post that one user said HTC replaced the whole motherboard as that was the issue - if this is the case I'm sure that all of your old data stored on the ROM in the motherboard goes in the trash as well, as they probably don't take the time to machine re-solder used boards.
Your probably fine, as all RLOD's seem non-relivable. If you want to make a 12v fryer, it's easy. I took a lot of time on mine, because it was fun, but the gist of it is to get a wire from positive to positive and negative to negative from your 12v to your phone. If you do this, please be careful, and DONT touch the wires together because it will cause and arc and melt your prongs - no good. I built a full fryer with a switch and everything, but it was overboard.
My 2 cents.
Also, to avoid this I am sticking with the ATT rom from here on out. It's too risky for something so expensive. I have my phone the exach was it was with the stock HTC minus a few small things. doing a hard reset and pulling the battery before customization works miracles. Almost everything else is available in cabs.
xconradx said:
Also, to avoid this I am sticking with the ATT rom from here on out. It's too risky for something so expensive. I have my phone the exach was it was with the stock HTC minus a few small things. doing a hard reset and pulling the battery before customization works miracles. Almost everything else is available in cabs.
Click to expand...
Click to collapse
The AT&T ROM is by far the most boring and least productive IMO. Couldn't you flash to the HTC ROM and be fine under warranty/returns?
redsrule2500 said:
The AT&T ROM is by far the most boring and least productive IMO. Couldn't you flash to the HTC ROM and be fine under warranty/returns?
Click to expand...
Click to collapse
It is boring, but when you get rid of bloatware and install the joys that HTC has available its pretty much the same as the stock HTC rom. You can still get the cube and today screen and everything else in cabs.
I think your voiding by hardSPL, not by having the stock HTC ROM. The egg comes before the chicken.
Just a thought...
Does anybody think that there is a correlation between phones being sent back to AT&T with HardSPL still on the device and the fact that HardSPL has not worked on the latest display driver (1.57.00, 1.81.00 and 1.82.00) equipped Kaiser's?
shogunmark said:
i would do everything possible to return it to a stock bootloader and rom before sending back (which in your case you might just have to roll the dice..)
Click to expand...
Click to collapse
You are correct - I'll have to roll the dice, as there's no way I can return it to stock condition. It won't start.
Thanks for your comments, everyone. So far, I've got:
someone advising that sending it back is a 50/50 chance
someone who has returned several phones with non-stock ROMs without repercussion from AT&T
someone worried enough that they fried the phone completely (awesome!)
So now I only need to hear from one last person: someone who HAS had to pay for a replacement phone from AT&T. For any reason, but specifically because you had a custom ROM on it...
Thanks again, all!
Lol...I've returned 2 tilts to at&t with flashed roms, and I haven't had a problem yet...That's right I'm working on my 3rd tilt since october ^_^ I LOVE AT&T
Maknificent said:
Lol...I've returned 2 tilts to at&t with flashed roms, and I haven't had a problem yet...That's right I'm working on my 3rd tilt since october ^_^ I LOVE AT&T
Click to expand...
Click to collapse
Thanks. Whulp, guess I'll make the call today then!
How can i get online on my Laptop
with the help of My Phone At&t Tilt ?
is there a cab for it ? or ?
Please Help
ilordvader said:
How can i get online on my Laptop
with the help of My Phone At&t Tilt ?
is there a cab for it ? or ?
Please Help
Click to expand...
Click to collapse
PLease do not post this question here, this is not related to the topic... please do some more reading or post in the general subfora...
shogunmark said:
PLease do not post this question here, this is not related to the topic... please do some more reading or post in the general subfora...
Click to expand...
Click to collapse
sORRY
drokkon said:
Thanks. Whulp, guess I'll make the call today then!
Click to expand...
Click to collapse
So made the call yesterday, got the replacement phone today, less than 24 hours from TX to CO. Great customer service, but I couldn't get them to pick up the overnight shipping as some had said I could. $12 ain't bad though.
Hopefully my custom ROM-flashed brick won't do me in for $500, but I'll let y'all know if it does.
*Anxiously awaiting* =subscribed=
xconradx said:
This said, I built a little contraption at work that hooked up to my 12v car battery and wires into the battery prongs on the tilt. I figured the tilt could handle 12v without catching on fire - it did. However, I'm completely sure they any data will be completely unrecoverable, and the only thing that will salvage is the case. I figured they have no way to call you on a total phone fry, because it could be lots of things that cause that. However, you should have heard the noise it made. I almost made a video, but it was too incriminating. 12v is devastating to a phone, it was cool! I cooked a 600 dollar piece of equipment and got a new one!
Click to expand...
Click to collapse
I've heard that a few seconds in the microwave can work wonders without the fireworks. Hopefully I'll never have to try that route...
arexben said:
*Anxiously awaiting* =subscribed=
Click to expand...
Click to collapse
Are you bricked too? Or merely curious as to the fate of us cursed few?
In other news, my replacement unit won't stay connected to the cell network. Even when it occasionally shows 4 bars, I can't make or receive calls. OS is sluggish too. Guess I'll flash the radio, maybe the ROM, then maybe send THIS one back too.
Does anyone know if my new IMEI number might affect my phone performance? Meaning, do I have to call AT&T and let them know my new handset's IMEI number?
drokkon said:
Does anyone know if my new IMEI number might affect my phone performance? Meaning, do I have to call AT&T and let them know my new handset's IMEI number?
Click to expand...
Click to collapse
short answer is no...
drokkon said:
Are you bricked too? Or merely curious as to the fate of us cursed few?
In other news, my replacement unit won't stay connected to the cell network. Even when it occasionally shows 4 bars, I can't make or receive calls. OS is sluggish too. Guess I'll flash the radio, maybe the ROM, then maybe send THIS one back too.
Does anyone know if my new IMEI number might affect my phone performance? Meaning, do I have to call AT&T and let them know my new handset's IMEI number?
Click to expand...
Click to collapse
You and I have had identical issues! After I got my replacement, I couldn't make or receive calls even with service. It's not the ROM or radio, it's ATT. I had to call and get to a higher level tech, because everyone else told me there were zero problems with my account and that I must have bad reception at my house. I knew for a fact I have full service at home. Whenever I tried to call it would beep 3 times (beep (pause) beepbeep)... after about 2 hours he finally got it to work, but I have no idea what he did. I did have to read him my IMEI about a thousand times though, and he was digging pretty deep to find whatever he got to fix it.
Good luck. Since I had so may issues ATT gave me 25 off my next 2 bills, which was cool.

I Returned My Tilt....but Only Reflashed The At&t Rom!

What are my chances of being denied a refund? I didn't even know that they could detect the hard spl stuff....crap!
Depends on how hard they decide to check, so there's probably a good chance you'll be fine.
scary man ive got no clue though
is it service or return?
return in the 30 day period...i better get my $$$ back....
So, not to make you any more scared, but I believe their terms state that if you voided your warranty, they get to keep your Tilt and charge you full price for a new one.
On that note, however, they'll actually have to CHECK and LOOK for HardSPL, which there is a good chance they won't. But anyway, you should take this as a learning experience, and you should've read the stickies in the Upgrading Forum.
As I said before, I don't mean to scare you, I'm just divulging some information I remember seeing.
I've actually sent in 2 different previous phones with actually the cooked roms obviously still on them and they never made any mention of it.
Nowadays though I wouldn't do it just to be safe, but hopefully you will be as lucky as I was.
im on my 4th tilt i returned 3 of them for various reasons to the ATT store within the 30 days, and they didnt give me any hassle (there all morons and dont bother to check for rom stuff).
As long as you picked up a new phone from them there is nothing they can do now.
Returned my CID unlocked wizard and no problems (flashed back to cingular rom though).
I don't think you'll have a problem. From what I hear all they do is charge it, make sure it turns on and hard reset it.
redsrule2500 said:
What are my chances of being denied a refund? I didn't even know that they could detect the hard spl stuff....crap!
Click to expand...
Click to collapse
How did you reflash the ATT ROM?
I've been wanting to try out other peoples ROM's but what if they all suck? I always want to be able to go back to the ATT rom if I want.
Where do you get the ATT ROM?
any 1 know how to find out when a phone was bought, or to see when the warrenty expires?
I forget where I found the AT&T ROM....Anyone know ?!
redsrule2500 said:
I forget where I found the AT&T ROM....Anyone know ?!
Click to expand...
Click to collapse
www.htcamerica.net
Or here http://forum.xda-developers.com/showthread.php?t=335568
The thread about how to restore you phone to send it back in.

Root or Not to Root?

I have recently purchased a Nexus One and i must say it is an amazing phone, but also very expensive! I just spent £370 on buying this brand new phone. Which brings me onto my main point, should i risk rooting or not?
I am confident with the rooting proccess and have rooted my hero etc etc, but i was happy to do so because i could also reinstall an official RUU incase something went wrong. However as we know with the N1 its not that simple. I want to be able to use features such as trackball to wake, and using the lights for notifications, being able to install market enabler and apps like autokiller and also being able to theme my nexus - but to do small things like this i still need to root my phone and void my warrenty.
So ive decided to ask you guys on wether you think it is worth my rooting my nexus one, and voiding my warrenty, or making do with no true customisational potential?
(Also silently hopeing someone finds a way to lock the bootloader :'( )
thanks
Just root it already. No regrets. I asked the same question.
But
But what if anything goes wrong with the phone over the next year? Just seems unecassary that i have to loose my warrenty to be able to make small customisations to the phone
I didn't root my phone in the first 5-6 weeks or so then once I had seen there were no obvious hardware faults I rooted it. It might be safe to take a similar approach.
Is totally up to you.. 2 things:
If you are affraid of bricking your phone due to flashing, don't be. Rule of thumb is always do Nandroid. And flash all you want. The exceptions are Radio's which pose higer risks of bricking.
That leaves hardware issues. If your screen cracks, battery explodes or button cease to function, HTC might switch your phone regardless if you have unlocked boot-loader or not. But im not sure how HTC customer service are in UK. People have done it in US and HTC didn't even raised an eyebrow to this.
edit:
like nDrg says, is to roadtest your phone for some weeks, see if no dust crops up under the screen, or other things starts to defect. Errors on new phones usually reveal themselves in the first weeks.
rooted just after 1 day i receive it lol and Froyo inside my nexus one since Yesterday Yes From France ^^
Hmm
Ok thanks for your feedback. I was having a think and i decided to wait untill froyo comes officially to UK, and if thats not good enough to keep me happy then i will root. Thanks

[Tutorial][Bell Atrix]What need to be done before Warranty Service?

[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.

Phone sometimes off (because I removed Google Apps? Or switched motherboard?)

Ok so I decided to remove all google related apps using console in recovery before booting into a freshly flashed ROM
First of all...the keylayout was all weird
As if it had not autodetected my tmobile keyboard (I have a rogers motherboard)...it was like that when I first put in the motherboard
So I rebooted into recovery and reinstalled google apps
I restarted and everything was fine.
I skipped signing in...
Then I removed all google apps from terminal emulator
And rebooted
It worked fine...everything was OK
But sometimes when I pick up my phone its off for some reason. I have to turn it back on.
Is this because I removed all google apps? Or is it just my motherboard flash memory getting worn out? Its the second phone it has been in...
Or is this because I have a rogers motherboard in a tmobile phone. Because there's one more thing I've noticed. With DangerSPL I boot into fastboot by pressing Call + Power. But with the 2708+ kernel spl Call + Power or Back + Power don't work. I have to go through Camera + Power then Back.
Hmmm...well I'm gonna leave it probably on adb logcat overnight and if it turns off ill see what's wrong
The roger's MoBo differs a little of the T-Mo one, starting by the KB layout.
You can check this wiki for some reasons to don't be using the 2708+ mod in Roger's MoBo, in section "Why not convert to a EBI0 Radio?": http://wiki.cyanogenmod.com/wiki/Full_Update_Guide_-_Rogers_Dream_EBI1
If you check on that same wiki, the Roger's version of G1 uses a 3.x radio, not the 2.x ones. If you install a 2.x radio on a Roger's... it will do some crazy things
By changing from a radio to another and all that, you'll not lose the avaibility to flash any of the roms that you're already using, the only thing needed to be changed is the kernel to use the apropiated specs of a Roger's MoBo.
Good idea to ckeck the logcat, and if u see some kernel hangs, it wouldn't be an bad idea to try with a 32A (Roger's) kernel and radio.
Hmmm well it didn't turn off
Logcat looked fine
Alls fine I guess
If anything starts going wrong I guess ill try
And maybe one day if I find a good reason to buy all the jtag tools ill fix my old one
frankdrey said:
...And maybe one day if I find a good reason to buy all the jtag tools ill fix my old one
Click to expand...
Click to collapse
I'll feel jealous if you do it... I can't buy that thing 'cause the place in the world that I live, and not having much money is a big trouble also
Wish you lot of fun if you get that stuff
Can't you buy it online?
And I'm short on money too (I'm only 15)
Hopefully it doesn't cost much
frankdrey said:
Hopefully it doesn't cost much
Click to expand...
Click to collapse
I don't think so, voltage regulators, soldier, so many cables needed, etc... it isn't just a cable USB-like, it's like 6 cables that must be soldered to the phone's MoBo, with electricity regulator and all that thing, kinda lab experiment thing xD!
And... who said I'm just short of money? Have to work to can at least live is a really common case here where I am. Not to mention have enough money conditions to buy electronics and PC's, it's kinda paradise here
Anyway, happy flashin' 'n playin' on ur phone
Do you have any issues with telephone or data service after changing the motherboard? I noticed the service manual calls for tuning the phone again after a motherboard change, so I wondered if it is really that sensitive or not. I have a broken phone with a good motherboard I wanted to use to fix another one with a bad motherboard, so I wondered if I could expect to run into trouble or not. Both are T-Mobile phones.
I would think just reflash radio, spl, and ROM and you're all good to go.
It works fine so far.
frankdrey is correct. i have gone threw 30+ g1s, i swap motherboard all the time (never a rogers into a ebi0 but im sure its ok) havent ran into any problems with the swap, but i always have rooted them and upgrade all about them. only real difference is that if for some reason you need to know the imei you cant look behind the battery but need to check in settings. common sense i know but just telling you the only difference i could see.
Thanks guys. I appreciate the real world experience, which is as I suspected. On the IMEI, I just moved the data sticker too. No trouble with GSM calls, or wifi. There's no 3G in the area though to check that.
PJK2011 said:
Thanks guys. I appreciate the real world experience, which is as I suspected. On the IMEI, I just moved the data sticker too. No trouble with GSM calls, or wifi. There's no 3G in the area though to check that.
Click to expand...
Click to collapse
Ah yes 3g probably will not work
Only 2g
3g works just fine, no difference in data speeds when swapping motherboards
demkantor said:
3g works just fine, no difference in data speeds when swapping motherboards
Click to expand...
Click to collapse
Oh alright
I think its tmobile only
I'm not sure but I remember hearing that the rogers antenna....
Oh wait...were only switching the motherboard
The antenna is separate
Well then nevermind...
Thanks. Both motherboards are T-mobile.
PJK2011 said:
Thanks. Both motherboards are T-mobile.
Click to expand...
Click to collapse
Oh then it definitely will be fine

Categories

Resources