I have updated and rooted my phone with Froyo 2.2. I need to send it back to verizon for a warranty replacement. After I SBF back to 2.1 I will have the stock software and no root. Does anyone know if there will be any issues sending this back? I am worried that the bootloader version got updated when moving to Froyo. Thanks for any help.
Have sent several phones back after rooted and sbfed so you will be good.
Even sent one back still rooted and nothing was said. Only problem I ran into was at a store and the tech seen the hack software on my sdcard.
Sent from my DROIDX using XDA App
Thanks for the info. Glad to hear it looks like the return will go over without an issue after an SBF.
OK, so i SBF'ed to 2.1, pulled the battery when it was done, then applied the OTA update to 2.2. Worked fine, then i rooted, but was having problems with the market. All apps showed up, but i had this huge list of items waiting to be downloaded and it didnt budge for hours. So i manually downloaded DX Bootstrapper from the market and tried to install the Tranquility rom. I didnt mount the system the first time i tried to install the Tranquility rom so i went back to do it, but this time i did a factory reset, and wiped the cache, then mounted the system and installed the zip. Then i was stuck on an Endless loop of the Tranquility logo. Attempted an SBF restore back to 2.1, and this time it just failed. Now the phone only turns on to the programming screen and i get this message:
Bootloader
30.03
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Transfer Mode:
USB
Should i just go back to Verizon, not sure if they have this in stock, and not sure what questions they will raise when they see this screen.
Well according to a birdman twitter post:
_mrbirdman_
do not flash back to 2.1 sbf after 2.2 0ta, keys/signature check has changed, if you go to 2.2OTA say goodbye to 2.1 forever....
and then he proceeded to say...
_mrbirdman_
Please retweet, everyones about to wake up! DO NOT DOWNGRADE TO 2.1 SBF FROM THE 2.2 OTA, YOU WILL BE BRICKED! UNTILL WE GET A 2.2 SBF LEAK
So until they leak a 2.2 SBF I don't think anything you can do. =(
They've got a thread over at droidforums with a number of people w/ the same problems too.
I got the same problem Now waiting for leaked 2.2 SBF :|
wow, im screwed.
if i tell verizon that i performed an SBF, will they refuse to replace my phone since i took it upon myself to try to service my phone on my own?
GoldenCyn said:
if i tell verizon that i performed an SBF, will they refuse to replace my phone since i took it upon myself to try to service my phone on my own?
Click to expand...
Click to collapse
i would tell them you were doing the ota it failed then just play dumb. It almost always works.
now the problem is that there are none in stock so im either gonna have to wait for a 2.2 SBF, or a replacement from verizon (and only god knows how long that will take).
I can't believe Motorola. For a company that is just barely getting their feet back on the ground after years of crappy phones - they sure not how to stick it to the consumer. I know we are just small percentage, BUT THAT'S THE POINT. Leaving it unlocked (aka no eFuse, etc.) would not really effect them much.
went to the store today, and they ordered a phone for me and it will be at my house tomorrow before 3pm by fedex. yay!
Even worse...p3droid warned that tranquility was meant to be applied over deodexed systems and the ota is not deodexed...yet.
Sent from my DROIDX using XDA App
GoldenCyn said:
went to the store today, and they ordered a phone for me and it will be at my house tomorrow before 3pm by fedex. yay!
Click to expand...
Click to collapse
That's kind of crazy when you think about it....intentionally brick your phone = get a new (though probably refurbished) phone.
I suppose it would be just about impossible for verizon to determine if the phone was bricked from their update or someone that tried to sbf but gone wrong.
Sent from my DROIDX using XDA App
hello first sorry my english,now let me see if i understaood....i was affreasid about updarte to oficial froyo ota....i am using a leaked froyo with some theme...and deleted some stock apps with root explorer...now my question is if i flash my droid with sbf file and gop back to stock 2.1 and wipe data and everything start over you know....than i upgrade to ota froyo....in this step i will be good??? with no bricked phone???? now my second question can i root this ota...and my last question is it worth since i alrady am in froyo with root with theme??? thanks i hope u undertand my englis hahaha bye and thanks in advance...
denpad2010 said:
hello first sorry my english,now let me see if i understaood....i was affreasid about updarte to oficial froyo ota....i am using a leaked froyo with some theme...and deleted some stock apps with root explorer...now my question is if i flash my droid with sbf file and gop back to stock 2.1 and wipe data and everything start over you know....than i upgrade to ota froyo....in this step i will be good??? with no bricked phone???? now my second question can i root this ota...and my last question is it worth since i alrady am in froyo with root with theme??? thanks i hope u undertand my englis hahaha bye and thanks in advance...
Click to expand...
Click to collapse
Yeah, that's the way to do it. sbf to 2.1 > ota > root.
But the only thinig I see that makes it worth it is if you have bad reception on your phone. OTA has new baseband version, which might help. Other than that, I don't really see any advantages.
As always, modder beware
Personally, I think Motorola will drop the anal attitude of locking down hardware in due time. Probably getting significant downplay from it. The number of people bricking the phones might be higher than other types? I don't know. Of course, only time will tell.
As for the OTAU. It's nice and buttery for an official release imo.
meshdub said:
Yeah, that's the way to do it. sbf to 2.1 > ota > root.
But the only thinig I see that makes it worth it is if you have bad reception on your phone. OTA has new baseband version, which might help. Other than that, I don't really see any advantages.
Click to expand...
Click to collapse
Ok thanks I think I stay with my leaked froyo
You are the reason Motorola has chosen to lock these devices down. It's awful that you bricked your phone through impatience, carelessness, or imprudence, but you shouldn't expect a free replacement because you couldn't follow directions or misunderstood them. These are probably low on stock because of all the consumers like you who did this. When you think about it, you take the one you initially bought out of circulation and then the replacement which you feel that you are owed. Maybe Motorola made enough, but since you bricked yours, another customer has to wait a week longer to get their first one. Thanks for that. If you are going to attempt these modifications you need to make sure you can handle it or have deep pockets.
Motorola locks these phones down for one reason "Verizon" or whatever carrier the phone is on. Motorola doesn't care if we are root or not but if Verizon says "jump" they say "how high". the better they lock it down the more the carrier likes them.
if we have root and can do things like get free wifi tether Motorola doesn't care they have already sold the phone but Verizon does because it takes from their pockets.
not Moto's fault.
iDroidNow said:
Motorola locks these phones down for one reason "Verizon" or whatever carrier the phone is on. Motorola doesn't care if we are root or not but if Verizon says "jump" they say "how high". the better they lock it down the more the carrier likes them.
if we have root and can do things like get free wifi tether Motorola doesn't care they have already sold the phone but Verizon does because it takes from their pockets.
not Moto's fault.
Click to expand...
Click to collapse
This not true, all I'm hearing is fanboyism. What about the Backflip or the Cliq? If you root the Backflip or the Cliq you will lose your manufacturer's warranty not the carrier's warranty. It Motorola's fault not anyone else. Even on the Motorola website they call it illegal when talking about rooting the Cliq, and rooting Android in general. You will your manufacturer's warranty if you root a Motorola Android even if it's on, Verizon, At&t, and or T-Mobile. The carrier's have nothing to do with this.
yea so this morning i manually installed the OTA froyo update and everything was going fine until it starts to reboot and then im stuck at the M logo. happened to me last week when i tried the leaked 2.3.15 update but i flashed it back and it worked. now i read somewhere that you cant use the 2.1 sbf because of the new bootloader. im thinkin my root has something to do with it because 3 guys i work with have the droid x stock and they all have the new update and im stuck here with a POS that doesnt wanna work. any help on how to fix this would be amazing
I think your only hope to get it fixed today would be to get down to your local Verizon store and have them flash the sbf of 2.2.
Tell them it failed on the update for some unknown reason...
yep did that. put me on the phone with tech support. sending me a new dx and im mailing them mine.
If you've had it longer than 30 days they will send you a refurbished X. You might want to check with Verizon. It may not even matter to you but good to know. I had to get a new BB Tour & it was a referb but I couldn't tell & all worked well.
Sent from my DROIDX using Tapatalk
yea they said they are sending me a refurb but as long as it works. i think im gonna get rid of it once the htc desire HD is released in the US
Has anyone ever returned a brick x and got the replacement with no problem or back billed?
Anyone with that story? Need info before returning my stuck bootloader X and I don't wanna be backbilled 500. Im broke as it is. Thx
P.s. I was able to do a factory reset and wipe cache before getting stuck at bootloader.
Im guessing no one ever gone brick after 2.2? Or ever return a brick x?
dadsterflip said:
Im guessing no one ever gone brick after 2.2? Or ever return a brick x?
Click to expand...
Click to collapse
if you read the forum you will see that many people have returned the x bricked. they go in to verizon and say the ota update messed up their phone and they need a new one or this one fixed.
Thx
Sent from my DROIDX using XDA App
no worries or if that doesnt work you can wait til 2.2 sbf comes out and possibly fix it on your own
I bricked my phone by using the wrong SBF. Like a DA, I didn't pay attn and used a SBF for verizon. However, my carrier is C Spire.
I am stuck at this:
Bootloader
30.04
Err: A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Can anyone point me to the correct SBF for C Spire to resolve this? Any help is much appreciated.
You're going to have to take it back to c spire and do a warranty return or you can send it to Motorola and they'll send you a new one back unless you're phone came with android version 2.2. If it came with 2.3.5 there's nothing you can do. Try this sbf file if it came with 2.2 http://www.filesonic.com/file/1301534444/SHADO_X6_3.2.6_SHADOW_BP_C_02.06.00R_AP_BP_Flex_21_signed_secure_cell_south_1ff_P3_USERBLD.sbf.gz
Thanks. I thought I may have to do the warranty exchange.
The link you attached is not working. Can you re-post it?
Again Thanks
jamcnew said:
Thanks. I thought I may have to do the warranty exchange.
The link you attached is not working. Can you re-post it?
Again Thanks
Click to expand...
Click to collapse
none of the sbf files would work for me, i was preloaded with 2.2. every time it resulted in the above referenced information exactly. there has to be a way to do it. i wish that i had a spare milestone x that i could mess with for testing. but after bricking 2 phones i am not willing to try it with my personal phone anymore.
edit: i can't remember, can you get to recovery?
ngholson said:
none of the sbf files would work for me, i was preloaded with 2.2. every time it resulted in the above referenced information exactly. there has to be a way to do it. i wish that i had a spare milestone x that i could mess with for testing. but after bricking 2 phones i am not willing to try it with my personal phone anymore.
edit: i can't remember, can you get to recovery?
Click to expand...
Click to collapse
No, I can't get beyond the Boot loader screen.
jamcnew said:
No, I can't get beyond the Boot loader screen.
Click to expand...
Click to collapse
my advice, before admitting defeat and taking it in for warranty, i would try every damn sbf i could find and use every method you can find. whats the worst that will happen? you brick it? too late. if you can get it to boot again somehow there is hope. try the same method over and over again. keep trying everything you can. THEN report back here and let the rest of us know =D
I've been working on this since Friday. The only sbf I've come across for C Spire is SHADO_X6_3.2.6_SHADOW_BP_C_02.06.00R_AP_BP_Flex_21_signed_secure_cell_south_1ff_P3_USERBLD.sbf.gz
I've yanked the battery, tried every imaginable button combo but that damned thing is stubborn. I'll probably go and do a warranty exchange later in the afternoon today. But if anyone here can point me to another sbf for C Spire, I'll try it out before I take it in. The one above is the only one I've been able to find.
I guess being on a small regional carrier makes it a little harder to get these things.
Thanks for the responses. I've warranty exchanged it now.
The replacement is on 2.2.2. Should I leave it alone or get the OTA update? I would like to put Cyanogenmod 7.1 on it.
Leave it alone. You can't run cyanogenmod nightlys on 2.3 because the nightlys are using froyo. If you do update you'll have to find the RC of cyanogenmod to put on it because it uses 2.3.7