Anyone know how i would run the new unlocker on a 64bit vista computer? i cant get the computer to run the sleep4.exe file... As thats the first file i see that it runs im not sure if the other files work or not. I would really like the try the new roms/radio. Dont think it will happen tonight though.
Well i ended up doing something and it worked. No clue what i did though. Good old Vista x64. Shows that 2 wrongs can make a right after about 5 hours of banging your head against a wall.
I had no problem putting any ROM on my phone with vista 64 except the first DCD version of the leaked rom. His new version went on without a hitch.
While trying to do the bootloader i got an error every time i ran it saying it wasnt compatible. i figured all the sleep app did was reset the device so i just restarted it real fast and continued with the bat file and everythign went smooth. sad part is it took me for ever to realize this. once that was on everything installed great.
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.
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
ichihaifu said:
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
Click to expand...
Click to collapse
Sounds like the cable is faulty. Borrow a new one to test or get a cheap one off eBay.
flumpster said:
Sounds like the cable is faulty. Borrow a new one to test or get a cheap one off eBay.
Click to expand...
Click to collapse
While I find that unlikely, I will try to look for a new one. But meanwhile lets assume that its not indeed the case, is there anything I could do at that point?
ichihaifu said:
While I find that unlikely, I will try to look for a new one. But meanwhile lets assume that its not indeed the case, is there anything I could do at that point?
Click to expand...
Click to collapse
Why do you find that unlikely?
There are cases exactly the same as yours all over this forum where the cable can charge the prime but cannot be used to install drivers etc.
http://forum.xda-developers.com/showpost.php?p=37662700&postcount=539
http://forum.xda-developers.com/showthread.php?p=39303129&highlight=cable#post39303129
flumpster said:
Why do you find that unlikely?
There are cases exactly the same as yours all over this forum where the cable can charge the prime but cannot be used to install drivers etc.
http://forum.xda-developers.com/showpost.php?p=37662700&postcount=539
http://forum.xda-developers.com/showthread.php?p=39303129&highlight=cable#post39303129
Click to expand...
Click to collapse
Hmm, alright. Just because I havent really roughed up the cable at all and everything worked fine until the said date.
But for now theres no way to try another cable, I'l look for new one next week.
ichihaifu said:
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
Click to expand...
Click to collapse
I gained root on 4.1.x via twrp and supersu, just after unlocking it. I am not shure if reinstalling 4.1.was really useful...but I did.
I was working on restoring my HTC one to stock since my SIM slot happened to break. In the process I must have messed something up and I can no longer get into any version of android, I am stuck at the bootloader screen.
My thinking is that if I run the RUU I will be able to kick myself out of this and have a functioning device, my problem is that I can't get windows 8 to identify my phone in fastboot to run the RUU.
Has anyone had any luck with wine on OS X or is there another way I can flash a firmware to my phone?
broopa said:
I was working on restoring my HTC one to stock since my SIM slot happened to break. In the process I must have messed something up and I can no longer get into any version of android, I am stuck at the bootloader screen.
My thinking is that if I run the RUU I will be able to kick myself out of this and have a functioning device, my problem is that I can't get windows 8 to identify my phone in fastboot to run the RUU.
Has anyone had any luck with wine on OS X or is there another way I can flash a firmware to my phone?
Click to expand...
Click to collapse
VMWare or Virtualbox works far better on OSX and I'd trust that vs Wine any day of the week. Got an old windows xp disc laying around?
I don't think XP would work since I have USB 3 drives on the MBP, but if it would thats an easy fix. I think I can find one laying around my house.
Okay, so you installed Win 8.1 and are having driver issues. You are not alone, 8.1 does not recognize your phone, so what to do right? Do you want to wait until HTC releases a driver that works? Sure you could, but you want a fix now don't you. Well, you are left with only 2 choices. Either downgrade to Win 8 or dual boot Ubuntu, or your favorite Linux distro. I tried both, and both solutions work. So, for all the 8.1 fastboot questions, there it is. I hate to be the bearer of bad news, but it is what it is. none of this works well, or at all on 8.1. I am back to Win 8, and it's all good again. Don't upgrade if you want to play for now.
hack14u said:
Okay, so you installed Win 8.1 and are having driver issues. You are not alone, 8.1 does not recognize your phone, so what to do right? Do you want to wait until HTC releases a driver that works? Sure you could, but you want a fix now don't you. Well, you are left with only 2 choices. Either downgrade to Win 8 or dual boot Ubuntu, or your favorite Linux distro. I tried both, and both solutions work. So, for all the 8.1 fastboot questions, there it is. I hate to be the bearer of bad news, but it is what it is. none of this works well, or at all on 8.1. I am back to Win 8, and it's all good again. Don't upgrade if you want to play for now.
Click to expand...
Click to collapse
your right but HTC has already fixed the problem it's called hboot 1.55. If your already s-off and on hboot 1.55 windows 8.1 is no problem at all. getting your phone to 1.55 s-off on a 8.1 pc is the problem. I had to return to windows 8 only long enough to get the newest firmware flashed and immediately returned to windows 8.1 and fastboot works fine.
Note: I use acronis true image to backup and restore my windows drive between windows 7 - 8 - 8.1, it only takes about 15-20min to fully change OS from one to the other and back. I have windows on a 120gig SSD and all my programs installed to D:\ and E:\ drives, it works really well.
Great news on the 1.55, there have been so many questions about it, I felt the need to post something to help. I wonder then if the converted GPE's that are on 1.54 will get the new Hboot. My converted Dev Edition already has it. Would certainly solve a lot of problems.