• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root SBF/Gingerbread killed 3G on my phone. Warranty replacement on its way.

G

greenless

Well-Known Member
Just a warning to anybody considering using the leaked version of GB. My DX died quietly in its sleep last night. Services will be held at VZW HQ when they receive the FedEx box I send to them.

Some background on my phone, to help figure out why this might happen:

 
Which SBF file did you use? I used the full 2.3.340 sbf file and was able to activate my phone just fine then rooted and flashed to the Gigerbread leak. Everything went fine for me. If you can still turn it on, I would recommend downloading the full sbf file and try it again. See if you can activate it after sbfing the phone.
 
I don't think it was the sbf but it could have been GB. I know everyone is loving it after a day or 2 but this is still an untested update. Assuming <5% of dx owners are rooted.then a percentage of them are the only ones to install it. We can see a small rate of failures here but it could be catastrophic on the total number of devices out there that could potentially receive this OTA. Point being, noone really knows how stable this is on the grand scale. Lol could also just be bad luck, dx's have been having problems with 3g. I don't think it should be written off as such and should go into the "possibly" an issue column.
 
So let me get this straight:

- You voided your warranty on your phone
- You then installed an unsupported, untested, unreleased version of software on it
- You then used an unsupported method of recovery
- And then, when it quit working, you submitted it for warranty replacement?

Nice. This is why phones get locked down in the first place, do you realize that?

When you SBF or install Gingerbread or whatever, the phone is overwriting all of the firmware that makes all the bits and pieces work. Your phone radio, your bootloader, all of that. A bad/corrupt SBF could easily cause this problem and it's your fault. It's not Verizon's fault.

Sorry, I just hate seeing all of these stories of people who screw up their own phones participating in this kind of process and then get warranty replacements from VZW. You brick your phone, deal with it. If I change my oil and forget to put the oil filter in, and then sieze my engine, I don't go to Subaru asking for a replacement.

Flashing your phone is not a joke. It's serious and can ruin your phone. Treat it appropriately.
 
binary visions said:
So let me get this straight:

- You voided your warranty on your phone
- You then installed an unsupported, untested, unreleased version of software on it
- You then used an unsupported method of recovery
- And then, when it quit working, you submitted it for warranty replacement?

Nice. This is why phones get locked down in the first place, do you realize that?

When you SBF or install Gingerbread or whatever, the phone is overwriting all of the firmware that makes all the bits and pieces work. Your phone radio, your bootloader, all of that. A bad/corrupt SBF could easily cause this problem and it's your fault. It's not Verizon's fault.

Sorry, I just hate seeing all of these stories of people who screw up their own phones participating in this kind of process and then get warranty replacements from VZW. You brick your phone, deal with it. If I change my oil and forget to put the oil filter in, and then sieze my engine, I don't go to Subaru asking for a replacement.

Flashing your phone is not a joke. It's serious and can ruin your phone. Treat it appropriately.
Click to expand...

I didn't 'submit' the phone for a warranty replacement. It was the Verizon tech that told me they were sending me another phone. I was truthful with them every step of the way, too, when getting tech support.

I didn't call them up and say "My phone is broken. Send me another one please!"

"You brick your phone, deal with it." What's with the hostility?
 
binary visions said:
So let me get this straight:

- You voided your warranty on your phone
- You then installed an unsupported, untested, unreleased version of software on it
- You then used an unsupported method of recovery
- And then, when it quit working, you submitted it for warranty replacement?

Nice. This is why phones get locked down in the first place, do you realize that?

When you SBF or install Gingerbread or whatever, the phone is overwriting all of the firmware that makes all the bits and pieces work. Your phone radio, your bootloader, all of that. A bad/corrupt SBF could easily cause this problem and it's your fault. It's not Verizon's fault.

Sorry, I just hate seeing all of these stories of people who screw up their own phones participating in this kind of process and then get warranty replacements from VZW. You brick your phone, deal with it. If I change my oil and forget to put the oil filter in, and then sieze my engine, I don't go to Subaru asking for a replacement.

Flashing your phone is not a joke. It's serious and can ruin your phone. Treat it appropriately.
Click to expand...

:D
troll.jpg
 
that wasn't hostility. a lot of people don't like to see people getting replacement phones because they tried doing something that voided the warranty. whether you lied or not is irrelevant. you are getting a new phone because you broke your's by voiding the warranty. when this happens, it adds fuel to the fire that phone manufacturers have to lock down their phones to avoid this. i'm not being rude about this either, as i am also guilty of getting a replacement after a botched sbf (i went into a bootloop with 30% battery and it didn't make it through the flash).
 
Dont feed the troll? What binary said was very valid. One of the biggest disclaimers with rooting, sbf, and whatnot is DO THIS AT YOUR OWN RISK.

If they did offer to give the OP one after telling them exactly what they did, chalk that up to good luck on their side.

I think I will also chalk this thread up to something you do and dont say anything about....
 
Wally World said:
I am sure you did not say " after I sbf'ed the leaked 2.3 gingerbread, all hell broke loose."
Click to expand...

If I said that, I woulda been lying. There's not an SBF for the Gingerbread leak, now is there? :P

The last tech that I talked to that set up the replacement said that since my phone is already a certified pre-owned phone, there's no telling what could be wrong with it. Who knows, maybe the reason it was sent back to VZW in the first place was because 3G wouldn't work?
 
greenless said:
I didn't 'submit' the phone for a warranty replacement. It was the Verizon tech that told me they were sending me another phone. I was truthful with them every step of the way, too, when getting tech support.

I didn't call them up and say "My phone is broken. Send me another one please!"

"You brick your phone, deal with it." What's with the hostility?
Click to expand...

If you, in fact, said to the Verizon rep, "I have a rooted, modified phone that I tried to install a user-modified version of the leaked Gingerbread upgrade on, then I tried to use the leaked SBF file to restore it back to factory settings and it still doesn't work" - and then, after hearing that, he offered you a replacement, then I apologize.

Shame on him, in that case. In the end, it all comes down to this: the more phones that users break trying to modify them and then getting warranty replacements, the more validation Motorola has for locking them down.

That last statement wasn't hostility. It was the blunt truth. If you brick your phone modifying it, you need to deal with it on your own.
 
What I find funny is some saying it was more than likley the phone with the issue not the SBF'ing or flashing of GB. No one really knows, sound to me more like a phone problem which they should replace it, now if he did not follow the correct procedure for sbf'ing then I would say it could be the issue.
 
Coolguy,where do you enter those numbers? dialer? Ive sbfed 4times now,I never heard of this until now,all ive done is the standard factory reset and *228 afterwords...this is good info....would it be too late to do it now,2 days after being on gb?
 
Greenless, don't take BV's statement as a personal attack on you. His statement is the code in which we (most of us) live by when we start rooting, ROMing, themeing, etc... I was certainly aware when I rooted that I was voiding my warranty. Therefore, anything I may have done in the process while doing such activities, I basically agreed to take responsibility for whatever happened to my device.

Sure enough I bricked it trying to flash Tranquility.... TWICE! The first time I was down for almost 3 days. The second time I knew what I was doing, so I was back up in a few hours. But neither time was I ever about to call Verizon or Motorola about it. It's like that sticker you find on the back of certain electronics that says, 'warranty void if broken'. I've broken that seal. I no longer have a warranty.

That's the deal you make when doing this stuff. Nobody's forcing us to root our phones and throw different ROMs on them. We just enjoy doing that. But turning a rooted device in after it fails... ESPECIALLY when it seems to have failed as a direct cause of doing so, is trying to have your cake and eat it too. And he's right, the locked down bootloaders are a direct result of people screwing up their phones while rooting/ROMing, and turning them in under warranty afterwards.

Which is why he (we) frown upon it. Because we criticize Moto for trying to interfere with the freedom of having the device when they lock it down. Then we see why they'te locking them down. It's frusterating.
 
You must log in or register to reply here.
Back
Top Bottom