Yesterday, I upgraded my new white dell streak to from 1.6 to 2.2 using the QDLtool. BTW, its easy as pie, it took about 30 mins, even with the extra task for using a 64-bit OS!!! I used the phone as i would normally yesterday and everything, GPS, internet, Facebook, etc worked perfectly.
Today, I try to do anything web related (i.e. Market, internet, Facebook, etc.) and I get 'A network error has occurred' message. I have tested the phone service and it seems to be working fine.
Has anyone else ran into this or have ideas of what I might try? Thanks in advance, cheers.
SOLVED
****PROBLEM SOLVED****
I FEEL LIKE A NOOB FOR THIS...
At any rate, I solved this problem by resetting the APN to default.
Settings > Wireless & networks > Mobile networks > Access Point Names > Press the 'Menu' key > Reset to default > check the radio button under ATT US.
Data network seems to be working fine at this time. I will post if anything changes.
How much experience did you have before using the QDL tool with installing custom ROM's? I just got a Dell Streak White and haven't had any success. Although I haven't messed with the QDL tool after hearing of some folks bricking their phone, and not having a way out. This is my first android phone and I am a little nervous and inexperienced with hacking/installing custom ROM's.
sukemecuke said:
How much experience did you have before using the QDL tool with installing custom ROM's? I just got a Dell Streak White and haven't had any success. Although I haven't messed with the QDL tool after hearing of some folks bricking their phone, and not having a way out. This is my first android phone and I am a little nervous and inexperienced with hacking/installing custom ROM's.
Click to expand...
Click to collapse
No experience at all for me. I had never even touched an android phone prior to the streak.
I haven't heard of anyone bricking their phones with QDL when following the guide, many have bricked them by other means though. It took 10 minutes from unzipping the download to rebooting into 2.2 for me. The software did all the work. I have heard of several people successfully unbricking with QDL.
Some people have issues with getting drivers installed but the tool will not act without the correct drivers so there is little risk there. If stock 2.2 is your goal there is no easier way that I have seen. After QDL is done I think the process on to 1.5.5 is easier also.
There is a guide at streakdroid.com
sukemecuke said:
How much experience did you have before using the QDL tool with installing custom ROM's? I just got a Dell Streak White and haven't had any success. Although I haven't messed with the QDL tool after hearing of some folks bricking their phone, and not having a way out. This is my first android phone and I am a little nervous and inexperienced with hacking/installing custom ROM's.
Click to expand...
Click to collapse
Qdl is simple. Its mostly automated. I havent seen anyone brick it with qdl yet. Drivers can be a pain, but fairly simple if your familiar with windows at all. Easier with vista/seven in my opinion.
Sent from my Dell Streak using XDA App
jeremyritzmann said:
Qdl is simple. Its mostly automated. I havent seen anyone brick it with qdl yet. Drivers can be a pain, but fairly simple if your familiar with windows at all. Easier with vista/seven in my opinion.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
that's good to know. I have quite a few options. I have a linux machine with ubuntu, an older win XP with 32 windows, and a W7 64 bit machine. The XP machine is hella slow though, so the W7 machine is my preferential option. A smidge concerned about the extra step since it's a 64 bit machine. I'm going to look into it tomorrow since I am off work for the rest of the year for the holidays. I'll report back with my results.
I'm coming from rooting my G2..Now I'm gonna try to root my girls streak. I advised her to get the phone and now feel bad shes still stuck with 1.6. I'm gonna attempt this tomorrow as it sounds easy. Just wondering why you don't have to root in order to update. Is there no root necessary to update?
sukemecuke said:
that's good to know. I have quite a few options. I have a linux machine with ubuntu, an older win XP with 32 windows, and a W7 64 bit machine. The XP machine is hella slow though, so the W7 machine is my preferential option. A smidge concerned about the extra step since it's a 64 bit machine. I'm going to look into it tomorrow since I am off work for the rest of the year for the holidays. I'll report back with my results.
Click to expand...
Click to collapse
The extra 64-bit steps were easy to do. I did install the wrong driver at first. I installed the 'Modem 9002' driver instead of the 'Diagnostic tool 9002'. I just went back to 'Device Manager', removed the wrong driver and installed the correct one. After that, make sure you install ADB drivers and then use the QDL tool. As stated previously by others, the tool does all the work. I hope this helps. let us know how things go.
sukemecuke said:
How much experience did you have before using the QDL tool with installing custom ROM's? I just got a Dell Streak White and haven't had any success. Although I haven't messed with the QDL tool after hearing of some folks bricking their phone, and not having a way out. This is my first android phone and I am a little nervous and inexperienced with hacking/installing custom ROM's.
Click to expand...
Click to collapse
My previous experience comes from hacking a few iphones, then I switched to android devices. The biggest difference I have seen is that the android hack require more command line tasks than the iphone. DO NOT FEAR THE COMMAND LINE, MAKE IT YOUR B****!!!!!
But a tip I'll give is, ALWAYS follow the guides STEP BY STEP, and make sure you know where the files you are working with are!!! A lot of the bricks come from poor file management i.e. the fastboot or update.pkg file not in the correct directory or file name is wrong and needs to be changed.
The QDL tools was suggested for the white streak as it slightly different from the black unit in the form a of preventative hacking measure, at least that is the only different that I am aware of.
Do your research and good luck, cheers
keep us posted
ccb04 said:
I'm coming from rooting my G2..Now I'm gonna try to root my girls streak. I advised her to get the phone and now feel bad shes still stuck with 1.6. I'm gonna attempt this tomorrow as it sounds easy. Just wondering why you don't have to root in order to update. Is there no root necessary to update?
Click to expand...
Click to collapse
Nothing I have read required the streak to be rooted before hand but my device was rooted. i have not rooted the build yet either. If she isnt going do anything that really requires rooted then she may not even need it. But 2.2 is pretty smooth so far and she will most likely benefit from having the better device with 2.2 than being rooted, IMHO.
The entire process took about 30 minutes and after fixing the APN issue the only other problem I had was what UI i was going to use.(Currently running Laurncher PRO - with the purchased key...AWESOME!!!!!)
QDL Tool how to (I used the streakdroid guide):
http://streakdroid.com/?page_id=92
http://forum.pocketables.net/showthread.php?t=8214
For 2.2 rooting use the z4root downloadresearch first as I have not used this)
http://www.androidzoom.com/android_applications/tools/z4root_ngtp.html
Good luck, cheers
asher73 said:
The extra 64-bit steps were easy to do. I did install the wrong driver at first. I installed the 'Modem 9002' driver instead of the 'Diagnostic tool 9002'. I just went back to 'Device Manager', removed the wrong driver and installed the correct one. After that, make sure you install ADB drivers and then use the QDL tool. As stated previously by others, the tool does all the work. I hope this helps. let us know how things go.
Click to expand...
Click to collapse
Since I've tried other methods of installing ROM's previously by using the W7 machine it wouldn't work. So I did a system restore to get rid of the previous stuff. Now it won't even let me install the the ADB drivers can be downloaded from Dell: ftp.dell.com/Handheld/R288920.exe
It just say's error on install. So I tried it on my super old XP machine which was brutally painfully slow. And it won't even update the driver manually. It just says "The specified location does not contain information about your hardware." I will say that under device manager on the XP machine it just lists it in other, like it should, as a Generic Volume instead of the Qualcomm stuff. Weird.
So just outta curiosity, since this froyo build puts your baseband at "00", wouldn't it be possible to then use's dells officially 2.2 unlocked rom and flash it through recovery? I mean using the update.pkg file from your sd card?
It sounds like it worked, but did it? If so which method did you end up using?
In the streakdroid guide there is a command line task you needed to execute before doing anything. To the best of my knowledge that task set WIN 7 to run in a testing mode which allowed for the ADB drivers to be installed properly.
asher73 said:
It sounds like it worked, but did it? If so which method did you end up using?
In the streakdroid guide there is a command line task you needed to execute before doing anything. To the best of my knowledge that task set WIN 7 to run in a testing mode which allowed for the ADB drivers to be installed properly.
Click to expand...
Click to collapse
I was wondering if you had to do the command line portion prior to installing the ADB drivers. Going to give that a go. Wish I could just get it to work with the XP machine, but I can't get it to recognize in the device manager that it's plugged in without turning the device on. It makes the sound as if it realizes a device is connected, but nothing ever shows up in the device manager. grrrrrrrrr
sukemecuke said:
that's good to know. I have quite a few options. I have a linux machine with ubuntu, an older win XP with 32 windows, and a W7 64 bit machine. The XP machine is hella slow though, so the W7 machine is my preferential option. A smidge concerned about the extra step since it's a 64 bit machine. I'm going to look into it tomorrow since I am off work for the rest of the year for the holidays. I'll report back with my results.
Click to expand...
Click to collapse
good deal. if you need any help with anything you can catch me on google talk. [email protected]
sukemecuke said:
I was wondering if you had to do the command line portion prior to installing the ADB drivers. Going to give that a go. Wish I could just get it to work with the XP machine, but I can't get it to recognize in the device manager that it's plugged in without turning the device on. It makes the sound as if it realizes a device is connected, but nothing ever shows up in the device manager. grrrrrrrrr
Click to expand...
Click to collapse
What kind of machine are you using? xp/vista/7?
This sounds easy...I will try tonight using Streakdroid guide...good to hear from someone doing this with a White Dell Streak and being successful.
I have read that others have flashed the 2.2 *.pkg with success. The QDL installs dell's 2.2 during its process. I stopped there and have had no issues othe than the APN. Now that I think about it, I think that the QDL 2.2 is meant only to write over the device itself with out any of the specific carrier bloatware. And because of that it did not know what APN to the use until I re-registered.
At any rate, I think this link may help you out:
http://www.streaksmart.com/2010/11/how-to-get-official-android-22-update-on-dell-streak.html
Let me know.
sukemecuke said:
I was wondering if you had to do the command line portion prior to installing the ADB drivers. Going to give that a go. Wish I could just get it to work with the XP machine, but I can't get it to recognize in the device manager that it's plugged in without turning the device on. It makes the sound as if it realizes a device is connected, but nothing ever shows up in the device manager. grrrrrrrrr
Click to expand...
Click to collapse
I did do the command line portion before the ADB install. But that portion is meant for the 64-bit win 7. what happened when you tried it on win 7?
the streakdroid guide:
http://streakdroid.com/?page_id=92
jeremyritzmann said:
What kind of machine are you using? xp/vista/7?
Click to expand...
Click to collapse
using the W7 64bit machine. This is where I am at.....at about 8 hours in at this point. I've pretty much given up for today though.
Just copied and pasted from another forum:
Ok so I have the option of 2 machines to try this on.........and I'm going on about 7 hours with no luck with either of them. One is a hella old laptop with Windows XP on it. The other is a newish laptop with 64 bit W7 on it. I originally tried it with the XP machine. I can get the drivers DLed and installed successfully on the XP machine, on the W7 machine is immediately says failed when I try an install. I should preface this with saying that I previously had the Dell PC suite installed on the W7 machine using a different version than what's listed in the streakdroid guide. Then onto plugging in the phone on the XP machine if I do that battery out the volume up/down method it makes the sound as if something is plugged in, however it isn't visible in device manager. Not that is matters since I can't even get the drivers installed on the W7 machine, but it's the same. Makes sound as if something is plugged in, but nothing under device manager. When going through the guides it say's it should fail on install when hooking up the device for the first time........wel nope not on either machine. It installs it correctly as a mass USB storage device. Dammit.
Related
How do I run OS, and rom loaders on a MAC. I would like to load a rom that fixes the wifi problem with my Verizon XV6800. Please can someone help. Thanks
You don't.
Unless your Macintosh has an intel processor and has some sort of Windows emulation (bootcamp parallels, wine, etc.), you can't. There isn't a way to do this straight from OS X.
Syncing your PDA with Mac is easy with the help of The Missing Sync or PocketMAC but updating your firmware, you'll have to use the next best PC in your area.
Good luck
Windows XP
Can anyone send me windows XP so I can duel boot and flash my XV6800 rom? I have parallels but no windows. Thanks
tgantt said:
Can anyone send me windows XP so I can duel boot and flash my XV6800 rom? I have parallels but no windows. Thanks
Click to expand...
Click to collapse
No. That's asking for wares which is against forum policy. You can download a trial from Microsoft and use it that way.
Be careful when running ROM upgrade tools within a VM on a mac. I got stuck in bootloader and the VM wouldn't see my phone at all. I had to find a PC in my closet to break it out I can only say this is true with Parallels though - VMWare may work better in this case but I've got no way of knowing.
try flashing from your microSD card
allanak said:
Be careful when running ROM upgrade tools within a VM on a mac. I got stuck in bootloader and the VM wouldn't see my phone at all. I had to find a PC in my closet to break it out I can only say this is true with Parallels though - VMWare may work better in this case but I've got no way of knowing.
Click to expand...
Click to collapse
I had the same trouble.....funny my old treo could be flashed in a Parallels VM with no problem, and ESN repairs on sanyos also work in it.
I noticed that if you keeep the mouse moving, it will be more likely to complete the flash....however that makes no sense!
Thanks
Thanks for the replys. Sorry for asking for wares.
I used the QDLtool to unstick my Streak so I am now on a pre release of 2.2. I am trying to upgrade to Steve's 1.5.3 but cannot even get the blasted streakmod recovery to flash as it keeps saying "waiting for device" on the cmd window but my Streak is in Fastboot_Mode. If I was able to fix my phone via QDL a few days ago then the drivers are all installed correct, right? I am running a 64 bit of Windows 7.
This is starting to overwhelm me...
I have played with W7 and drivers before. Other people have used W7, but it can be fiddly. If its possible, do yourself a favour and use XP.
Sounds like you still have drivers to install. I know I had to run an installation .exe file before the proper drivers were installed (XP).
Sent from my Dell Streak using XDA App
thestreaker said:
I have played with W7 and drivers before. Other people have used W7, but it can be fiddly. If its possible, do yourself a favour and use XP.
Sounds like you still have drivers to install. I know I had to run an installation .exe file before the proper drivers were installed (XP).
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Unfortunately, the only other pc in our house runs Vista. The computer I had before this one had XP but it had bad capacitors and fried the mobo.
I can't understand why I would need more drivers if I was able to use the QDLtool a few days ago with no problems on this same laptop. Who knows... they have minds of their own it seems.
Hopefully I can get it figured out bc its driving me insane!
Have you tried the solution in this guide:
http://forum.xda-developers.com/showthread.php?t=776883
I have to go through this method everytime I go into fast mode
Sometimes it feels like I have to bring an altar and a live chicken out just to get the drivers working
I use win 7 64
I have been trying to find Windows 7 drivers for my Streak and have had zero luck getting anything to work. I am trying to root my device but without getting the drivers to work I think I am stuck. I have searched this forum and others but have had no luck.
Any help please? Thank you.
i just finished putting djsteves 1.9 on and i was like you. i was lost with all of the write ups and what not. here is what i did to figure it all out.
dl all files and then run the tutorial. i know there is extra stuff that is not needed but i got mine done and it wasnt too hard,
http://streakdroid.com/?page_id=92
start there and then just follow skip the first part about how to install rom. that is last.
The drivers are actually on the MicroSD card that came with your Streak. Look for Dell_PC_Suite.
That installs the ADB drivers as well as the PC Suite (that I just ignored from that point onwards)
That's how I got the drivers to work for Rooting my Streak on Windows 7 x64
Dell.com...
http://support.dell.com/support/dow...dateid=-1&formatid=-1&source=-1&fileid=433681
I have looked at all the other problems that people have been having, but it appears that nobody else has had this, I feel like a special NooB..
Ok, coming from my Droid Eris, got the Razr last night and it has
6.11.744XT912... It is trying to update, but I havent installed it yet, most likely 748 or newer... However, I don't think this is a phone problem...
I have followed all the simple steps for Doomlord's, Zergrush... To the best of my knowledge. clicked on ADB application and it disappears so fast, I must assume it installed ADB drivers... I orginally was directed to Moto's site for their drivers and it installed 5.4 x64 drivers, have since uninstalled it and found a link with 5.2 drivers to see if that was causing it....
what happens is this... I press any key to continue and I get
--- STARTING ---
--- WAITING FOR DEVICE
The system cannot find the path specified.
And For EVERY line of code there after as well....
This is seriously getting to me now, I have the phone plugged in, in Charge Only Mode... proper debugging and unknown sources selected... but WTF?!?
Anyone have an idea? I know its gotta be something simple..
Brynn
not sure what kind of computer you have, but have you tried the 32 bit drivers?
I tried installing my Razr's 64 bit drivers the other day and couldn't get my computer to recognize it. I then remembered from modding my previous phone (Droid 1) that I needed the 32 bit drivers. Installed those and connected to my Razr no problem.
I am running Windows 7 x64, with an I7-2600k....
I can try the 32bit drivers and see if that makes a difference...
Ok, just tried it, uninstalled the 5.2 driver and took the link to Moto USB Drivers and downloaded the MotoHelper and Driver 5.4.0... It did not give me a choice of 32 or 64 bit.... I did see it install the ADB drivers too.... But atlast, still no change.....
This so makes me wish I had gotten the Nexus last night....CM9 ICS is calling me.... will feel so much better when I get something on this phone that I can use until the ICS update OS comes out.... (any ROMS available now for it? used to CM7 on my Eris..) Don't really want to start uploading apps and such until this is rooted and updated...
Possible solution
I had been having the same issue, then I found a post in a thread that stated to change the USB connection setting to Mass Storage by pulling down the notification tray after plugging the phone into your computer. Worked fine for me that way.
nope, no dice.... I have tried that in every setting within the past 16hrs... PC mode didnt help, and just tried USB Mass Storage again.... since I just reinstalled the drivers... it did install the drivers as I switched modes, but still no change....
Ok.. just so you all can hide the fact that you might just be as big a NOOB as I feel at the moment....
I have figured out why I am getting this error.... apparently my phone is already ROOTED!!!!.... I downloaded Root Explorer and Root Browser and it seems to work with no errors....
Nice Huh!
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
1stx2 said:
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
Click to expand...
Click to collapse
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
travisn000 said:
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
Click to expand...
Click to collapse
It's absolutely crazy isn't it? Please let me know if you figure out the problem. I don't consider myself a noob about rooting/romming/etc but this is making me feel like i just started today!
EDIT:::: I finnally got my phone to connect to my moms laptop but it still wont connect to mine. I got CASUAL to recognize the phone but I'm kind of scared to do it now since my first phone connected perfect the first time and when I started having other problems and needed to send it back and usb debugging WOULD NOT work. I don't want to leave it stock but I don't want to go through what I went through with the first phone again
Ok, I finally got my phone rooted, unlocked using casual. I had to use my moms laptop ( hp, windows 7, 32 bit ) to unlock it, our desktop ( windows xp 32 bit ) to use odin and my laptop to transfer music, vidoes, etc..... Now i absolutely hate installing drivers and windows in general. You would think being 1 of the top-of-line smartphones, **** like this wouldn't be so difficult.
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
travisn000 said:
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
Click to expand...
Click to collapse
Yep that's the same thing that happened on my windows xp based desktop, it would boot into download mode but it wouldn't recognize the phone. It's got to be a driver related issue though. I had similar issues with my gnex but that was nothing compared to this catastrophe.
Sent from my SCH-I605 using Tapatalk 2
I finally got mine done.. gave up on windows drivers and went back to linux.
I had to switch to a disto that used gksudo & dpkg in order for the CASUAL app to work properly (..my distro of choice is PCLinuxOS, but it doesn't use gksudo or dpkg).