Database Users

DX Completely Bricked, SBF Wont Help

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.

2.2 Odd Problem

Hey guys,
So I flashed the ROM rubiX Focused 0.3 and somehow couldnt get my phone past the activation screen. No big deal. I couldn't get access to the bootstraper either. So I use my good old Handydandy 2.1 SBF and revert my phone back to stock. I then use a copy of the .604 update to hopefully prep my phone to install the 2.2 ota Leak. Well I am getting ready to 1 click root it after installing 604 and move su around and I happen to check my version number under about phone and I have 2.2. WTF? I am not super upset or anything I just dont understand how? The System version and the Base band version both match the 2.2 OTA but honestly How did I get it?
If no one can answer this its fine, just thought I would throw it out there since it was bugging me.
Thanks!

Anyone else stuck with D12?

Had my Fascinate since launch date. Waited and saw the DI01 come through/ tried to update my phone...install failed miserably..no matter how many times I tried, even did full restore.
I was going to try to get a full DL09 and flash it to my phone, I have Odin, downloaded the .tar file. But got frustrated. I'm pretty computer literate, but for some reason this stuff just escapes me. Anyway went to VZW today and ordered a warranty replacement, should be here Friday. Hopefully this one works and I will either wait for the rumored 22nd release date of Froyo or I will try and download it and flash it...if I can do it.

What hardware version?

Why didn't u post here before u ordered a replacement. It really seem s like the problem was not the phone but what u did.
Sent from my SCH-I500 using XDA App

Kaze105 said:
Why didn't u post here before u ordered a replacement. It really seem s like the problem was not the phone but what u did.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I did nothing other than what the phone told me to do. If you had read what I posted I have had the phone since day 1 launch. Have not attempted to root or put any other version of firmware on my phone.
So don't come at me sideways about it. I did nothing to my phone...yet

Sorry to hear about your issues, but we probably could have helped you out with getting updated. There was a phone in a local VZW store that is stuck on DH12 as well cause the DI01 update kept failing.

Skrazz said:
What hardware version?
Click to expand...
Click to collapse
i500.04
Firmware 2.1-update1
Baseband S:i500.04 . DH12
Kernel Version 2.6.29
Build number SCH-I500.DH12

imnuts said:
Sorry to hear about your issues, but we probably could have helped you out with getting updated. There was a phone in a local VZW store that is stuck on DH12 as well cause the DI01 update kept failing.
Click to expand...
Click to collapse
It's all good man. Getting a brand new phone as opposed to a refurbished one. I understand what to do, I get the general idea as to how, I can read the steps but I am more of a visual learner, so pictures to go along with these install steps would help someone out like me.
I also work for a VZW Premium Retailer. Corporate stores don't like us much, so kinda shocked the Sales Rep that I had as much knowledge about the phone as I did. It's actually a known software problem with the phones. As well as the issue that if you use the unlock pattern on the phone and fail at it 19 times or more it will lock the phone out...it will ask you for the gmail information that you provided but even that will not work, resetting the phone to stock will not work...I was told this by a Samsung Tech Agent that it was a known software issue with their devices.

Got my new phone today.DL09 on the Baseband....now on to root, and Froyo...hopefully

Godspeed, good sir...
Sent from my SCH-I500 using XDA App

AC has a nice guide and package for the latest froyo leak.
forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/59348-odin-full-eb01-froyo-leak-packaged-w-root-new-clockwork.html

Soulchaer said:
I did nothing other than what the phone told me to do. If you had read what I posted I have had the phone since day 1 launch. Have not attempted to root or put any other version of firmware on my phone.
So don't come at me sideways about it. I did nothing to my phone...yet
Click to expand...
Click to collapse
Huh? Im not trying to come at you sideways as it says in your first post, you tried to flash DL09, had problems and then went to verizon for a replacement. (Hence the reason why I said some people here could have helped possibly).
Either way, hope you get froyo onto your fine, good luck.

Could you help me? I'm on DH12 and voodoo v.2... i'm trying to basically go back to stock with all the bloat and no root so that I can return the phone...if I choose to... which steps should I take? a direction to a post will suffice... Thank you...

Azaurath said:
AC has a nice guide and package for the latest froyo leak.
forum.androidcentral.com/verizon-fascinate-rooting-roms-hacks/59348-odin-full-eb01-froyo-leak-packaged-w-root-new-clockwork.html
Click to expand...
Click to collapse
Locked and loaded...BADASS...Thank you to all the Devs who make this **** happen. Without your tireless efforts, dedication, relentless question answering..we the masses would be lost..

yuhang said:
Could you help me? I'm on DH12 and voodoo v.2... i'm trying to basically go back to stock with all the bloat and no root so that I can return the phone...if I choose to... which steps should I take? a direction to a post will suffice... Thank you...
Click to expand...
Click to collapse
First you should disable voodoo.
Then follow this post. It should wipe your phone and put a completely stock version of DL09 on it.
Just make sure to use the PDA button in Odin only.
*OFFICIAL* DL09.tar.md5

Azaurath said:
First you should disable voodoo.
Then follow this post. It should wipe your phone and put a completely stock version of DL09 on it.
Just make sure to use the PDA button in Odin only.
*OFFICIAL* DL09.tar.md5
Click to expand...
Click to collapse
You don't even have to disable voodoo. Just flash that and you're done.

Personally I've learn once you do an OTA update, it will not allow you to do it again. It has happened to me when I've tried to do every offical update more than once

thank you for the quick information, I will try it now and report back.

Root AWS Dell Streak 2.2.2 FRG83G

Well, hopefully don't get yelled at but at a dead end. Have tried superoneclick, universal androot, and z4root. None work. Don't want to brick this so have not tried flashing a superboot.
Any thoughts?

Broken said:
Well, hopefully don't get yelled at but at a dead end. Have tried superoneclick, universal androot, and z4root. None work. Don't want to brick this so have not tried flashing a superboot.
Any thoughts?
Click to expand...
Click to collapse
I have the same aws streak came with the 2.2 build 333 or wherever you want to call it. I was able to use superoneclick, I had usb debuging on, and its the newest version of super. "But" I had to install the drivers off the dell website or it wont work. to be safe I downloaded all of them for the streak and installed them.
That might be your problem.

My build is slightly newer. gausb1a134100
Will try drivers at dell. I used the ones on the sdcard.
Update:
Tried drivers on Dell website and same thing. Fails.

homer4evr said:
I have the same aws streak came with the 2.2 build 333 or wherever you want to call it. I was able to use superoneclick, I had usb debuging on, and its the newest version of super. "But" I had to install the drivers off the dell website or it wont work. to be safe I downloaded all of them for the streak and installed them.
That might be your problem.
Click to expand...
Click to collapse
Hi, I'm doing research on all the firmware versions, could you post your baseband version?

GAUSB1A133300-AWS
Sent from my Dell Streak using XDA App

Woot, finally got it. Realized the psneuter didn't work and had been trying the rage one after.
Tried it during boot with rage and that did it.

Thanks!
If you could do one more favor: could you hit the system update button in settings and post the URL it gives you? you dont need to update if you dont want, but the URL would be really helpful. I've almost got all the data I can on the aws version.

http://mobileupdate.dell.com/LandingPages/Streak/Retail/uptodate/en/index.html

I meant to homer, I know yours is up-to-date since it's newer than all ours

TheManii said:
I meant to homer, I know yours is up-to-date since it's newer than all ours
Click to expand...
Click to collapse
Im running streakdroid, it just tells me that I have a update for that. A few weeks ago (maybe two) I tried it and it told me I was up to date.
But now Im wondering if there is one waiting for me I might do a restore to stock and check

Awww
The issue is what would you restore stock to? If you go back to 318/319/339/340 they wont give you an update to 341. (Im not even sure if 333 can be updated to 341 since no other 3xx -> 3xx update is given for stock streaks)
There's bound to be at least a 3rd aws version (either donut or ecliar that i dont know about)
Dont bother updating your streak if you just want 341, from what i know it shouldnt work.

Mine came with 333. I sure it was upgraded to that by the seller. But I would like to know what the difference is with 341.

Externally there shouldnt be any real difference, except that 341 is Android 2.2.2 and all other 3xx builds are Android 2.2

Ok restored to stock 333. Tried update said I was good. Here's the link. http://mobileupdate.dell.com/LandingPages/Streak/Retail/uptodate/en/index.html still only 2.2.1. That sucks I want 2.2.2
Sent from my Dell Streak using XDA App

Oh you still have a copy of 333? Would it be possible for you to upload it? Its not available on the dell servers (at least not with all the other versions)

I have no Idea how to do that. I get all you would need is the rom backup file but where and how to put I have no clue.
Also I never did a backup before I set the phone up so I would have to revert back to my stock backup, do a factory reset than nandroid. I just dont want to post all my personal info from my rom dump.(gmail.passwords.....)
Side note: when I did the update check the url that first came up was diff. from the one I copied. The url that first came up had 333 somewhere in it.I do rember seeing it for a split second.
I took this off the dell website (http://mobileupdate.dell.com/PackageProductionLocations/Streak_318_12821_00.pkg ) and have been playing around with the #'s one would think that by changing the 318 & 12821 you could find the other builds but I tried 341 & build #'s (_341_14***)and I got nothing. Anything else I could try

did it look like http://mobileupdate.dell.com/?version=GAUSB1A33300 ?
I've been systematically working my way though them looking for updates. The only lastest pkgs I'm missing are the two AWS ones (333,341) and the starhub branded ones (320).
If you did have a nandroid dump of 333 just dont upload the userdata.img (this is true of nandroid in general, all your data is in userdata, the other imgs are the systemdata that only has the android files)
If it is a hassle you dont have to go though the work, what I really want is the original pkg, pkg.dec and the recovery image anyway. (that's why I asked for the update url so I could grab them myself)
If you wanna see my progress, I put everything on the wiki: link

That's a lot of info! I do think it looked like that link but I wasn't really looking I just happened to see the numbers than nothing. Where would I upload the files? Never had to upload just download.

Dropbox/filefront/rapidshare/smoke signals if you're not sure you've removed your personal data, you could password it and pm me a link.

so what you are saying is there is a version of 2.2.1 and 2.2.2 floating around for the streak?
has anyone been able to try these on the unlocked streaks preloaded with 2.2?

[Q] Factory Replacement DX

Hey all,
my trusty froyo dx finally died on me, and today I received what looks to be a newer model dx. My questions are..
Are there any ways to tell what "gen" this new dx is? (subtle changes etc)
this device already came preloaded by Verizon with system 4.5.596, will i have any issues when I plan to root using z4?
Thanks a bunch

Yes, it won't work. If you want root, you have to SBF to froyo.

Are there any ways to tell what "gen" this new dx is? (subtle changes etc)

phillybizzle said:
Hey all,
my trusty froyo dx finally died on me, and today I received what looks to be a newer model dx. My questions are..
Are there any ways to tell what "gen" this new dx is? (subtle changes etc)
this device already came preloaded by Verizon with system 4.5.596, will i have any issues when I plan to root using z4?
Thanks a bunch
Click to expand...
Click to collapse
what makes it look like a "newer model".
It shouldn't be different? for the most part the droid X2 looks exactly like the droid X. so I don't think they would make changes to a phone that already has a successor
z4root will not work, you need to find a FULL sbf .340 stock and use RSDlite 4.8 and restore it to froyo. from there you can flash p3droid's rooted gb rom, which is essentially the same as the OTA