Related
First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
okeven said:
First off, I have read every thread mentioning error 260, every wiki about upgrading, and have not been able to fix my problem.
I am trying to upgrade to Schap's newest 6.0 ROM, not the 6.1. I currently have the OEM 5.0 ROM that came on the device from AT&T. I can connect via activesync perfectly. No issues there at all. When I run the upgrade program, it gets all the way to the status bar showing 0% or 1%, then the phone and computer disconnect the activesync connection, the phone goes back to the today screen, and my computer shows error 260.
I have seen posts saying I need to install HardSPL. I tried that and get error 260 there also.
I have seen posts about installing JumpSPL, I tried that and it only locks the phone up. I must do a soft reset to bring it back to life.
I found the instructions on upgrading the ROM via the SD card. I followed those and renamed the .nbh file and copied it to the fat32 formatted sd card in the phone. Where do the rest of the files go??? The .nbh file cannot possibly contain the entire rom, right? The instructions leave that part out from what I can see.
Help!
Device is a AT&T 8525. Thanks!
Click to expand...
Click to collapse
Try a different USB port first, fire the device into bootloader mode manually and see if the device is detected by windows as "HTC USB SYNC"........use a hardwired port NOT a USB Hub aswell.
I tried a different USB port. It is not being plugged in to an external USB hub. I went into the bootloader screen and my computer makes the sound that a USB device was plugged in and it does show in the device manager as "HTC USB SYNC". What now?
Now try to do an update, Sounds like a problem associated with the connection of the device to your machine...usually caused by messed up USB drivers or a conflicting program.
Just tried. Same error again. Tried restarting the computer and tried it again. No dice.
this is the answer
hey man, how u doing. I was getting those errors too, I actually have a Tilt, I got error 200, and 260 trying to change my rom, I was about to give up. then I tried something I didn't think of, I updated my device center software from Microsoft and then miraculously everything worked after that. If you have XP update your Active sync software to the latest one and everything should work after that. Hope this helps.
and one more thing, make sure you install HardSPL v1 (or later when its released) first before trying to install the ROM.
I don't think anything is wrong with your usb drivers
I had actually checked to make sure I had the most recent version already and I do. I cannot install HardSPL either, since it gives me error 260 there also.
Error 260 is an open port error... I believe you have already tried resetting your device, but have you rebooted your pc prior to this procedure... I am grasping at straws for you, since you said you have tried soft resetting to no avail... I believe MrVanx stated to put the phone in bootloader mode and try to run the update utility that way... It works for me...
Can you try this on a different pc? If so, does it work? I have a post on another forum that you might find interesting... I did not compile it on my own, but cannot recall where I got it from... anyway, the link is HERE...
Hope this helps you out...
I have restarted the computer multiple times. I just tried it on my laptop and that did not work. I can boot the phone to the bootloader, but how do I install it from there?
That should be the easiest part... once you have it in bootloader mode, connect it via usb and then launch the update utility...
I get error 260 doing that also. argh!!!
i know how u feel
i had your problem several times. you want to know how i fixed it?
i didn't...
first i tried everything you and the guys mentioned and... nothing. then it worked the next day by itself.
the second time i couldn't connect i was really mad because the errors came sporadically. i tried installing AS, uninstalling, hard resetting the device, changing usb ports, anything logical and illogical and it worked on changing usb ports (but not on the first change).
now i'm at my girlfriends, had no problems until i saw farias new rom and wanted to flash it. guess what connection error
p.s. i've read trough and trough, but i've found no solution
what version and OS?
okeven said:
I get error 260 doing that also. argh!!!
Click to expand...
Click to collapse
yeah, I thought u would dget that again. i don't believe the error is originating from your phone, its more from the computer. what operating system are you using and whats the version number for activeSync or MS Device Center you are using?
I had that error on my home pc and on my girlfriend's laptop prior to updating my device center software. My pc is running Vista ultimate x64 and my girlfriend's laptop is running Vista Home Premium x32. I'm on her laptop right now, the version of device center is 6.1.6965. when I get home I will see which version is on my computer, I remember seeing "beta" on the one I got at home, lol, I didn't know Microsoft sent out beta software through its msupdate.
okeven, someone replied with good suggestions to the thread that u accidentally started over in the kaiser forum. you might want to check that out
I have version 6.1.6965 also. It does not say anything about it being a beta version, but with Microsoft, isn't everything in beta stage?
I did try the "official wm6 AT&T" version. Upgraded just fine. Tried upgrading to another one. Failed with error 260. What is different with the official upgrade program compared to the unofficial ones. THAT is the problem.
help
hi guys,
i have the same problem always the code 260, and also, my tytn's screen become within light, and without any boot number, ni radio, anything appears, please help me,,
thanks,
Finnaly
Hi guys
I also have the 260 problem but i resolved it:
1º- connect pda and make a active sync connection
2º run RUU
3º the 3-color screen will appear and update will stop with the 260 message error. be sure you can install the "qualcomm cdma technologies msm driver" at this moment, by an internet connection.
4º after the driver is installed, the word "USB" will appear in the white strip of the 3 color screen;
5º run RUU again and that´s all!
I´ve tried it in windows 7 ultimate 32-bit
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
lxlx said:
hi,
I had the same issue on my second flash... I resolved it by ignoring all .exe's (which I like in general).
So I copied the .nbh onto the card, renamed to Kovsimg.nbh, bootlader mode, done
cheers
Click to expand...
Click to collapse
Hermes use HERMIMG.nbh ... kovsimg.nbh is for Xperia X1 ..
Hi gys, I think that this is my first post, but I want to share some solution for with you. The most important think with "connection" errors is to have HSPL installed correctly. I was trying to install on my HD2 universal ones, like Hard spl v7 and 9, but problems occured. So after trying everything, I found HSPL (on this forum) just for HD2. After that, everything wass like a charm
Now including Guide 3, porting sys and xip from newer versions of windows mobile, so now you can have 6.5.x on your phone if you want to cook it in yourself.
[From MoDaCo]
This was written for the Omnia 2 SCH-i920 VERIZON WIRELESS phone
First Guide
This will be the first installment of Guides to building/cooking your very own ROM. I know there is a lot of talent out then and if we can pool it together we can make our phones even better (or at least better looking).
This first part is rather easy and just gets your feet wet as there are a LOT of things to learn about cooking. If you are patient you can make some amazing roms. The only thing I ask is that you make one for the rest of the community as well. It's all well and good to make your own custom rom, but to not share some of your work will not further others in their quest for the "perfect" phone.
Stock DC23 Rom from Samsung (PDA only not CSC):
http://www.4shared.com/file/AyPwHiDe/i920_DC23_Stock7z.html
Second Guide
Okay guys here is part 2 of my ROM cooking tutorial.
I think I you may have to reset the Read-Only Flag on the initflashfiles.dat I cannot remember.
I just have one word of caution for you guys wanting to create your own ROMs. If you find cracked cabs (yeah I know they are out there) DO NOT post them nor the ROMs created with them here at MoDaCo. It is against their policy.
I'm attaching the part 2 guide and the batch file for opera.
Ok, thought I done everything right. I read your guide down to a t and flashed it after taking vzwtones out. Phone booted to windows splash screen and now it's stuck on a white screen. it's been a couple minutes but it did this last time I tried to make my own rom. I don't know what I missed or didn't do right. Does it normally take forever to load like this?
did you try to flash without taking anything out of the rom?
What is the size of the rom?
no didn't try it without taking anything out. I will do that next. Size of rom after taking vzwtones is 284mb. I downloaded this file. I have izarc as an extractor and I took the 001 off the end and left everything else in tact.
Ok, flashed without taking anything out of rom. It's not working either. I notice everytime a rom doesn't work there is no verizon start sound...so I know ahead of time when the rom won't work. All I done this time was click buildos. I am using windows xp under vmware 7 still with sp3 installed. Could that be a factor, even though I've been able to install other roms successfully?
Now it's on a white screen. I'm just gonna see if maybe it will boot up after all...even if it takes all night...unless you have some idea what I may be doing wrong lol
If you don't see the orange load screen after vzn screen, then it won't load.
Why are you using VMware? I don't think that would be a reason why it wouldn't work, but I don't know since I don't use it.
seen the orange windows screen...then it went to white screen and it remained on there ever since my last post.
I use vmware because I tried to install the mit drivers on my windows 7 home premium 64 bit but I couldn't find a driver to work...then octans wouldn't work on 7. I have since redone my computer so I may try again to free up space lol. but now I am trying wozzers kitchen so i am hoping it will boot up. didn't take anything off
darn wozzers don't work either. it got stuck on the verizon screen. never went to windows welcome screen. Geez. What am I doing wrong? I guess I'm gonna see if it's becuz of vmware if I can actually find the driver for my puter. or my phone is messed up...but like said earlier...other roms work on it?
are you looking for Mit drivers for win 7 64-bit?
I have attached the win 7 64-bit drivers for Omnia 2. Yes they work in OCTANS full version, and yes they work for the SCH-i920 verizon Omnia 2
sweet gonna try and see if that works out. Thanks.
well windows 7 is not working out for me. I am just having bad luck all around. octans won't recognize my phone. i did the steps from modaco and installed samsung 4.34 cdma modem...then I rebooted and upgraded the mit to the one you gave me...still no luck. Nothing.
guess i gotta keep vmware and just keep trying to make the rom. I just don't know what i am doing wrong..i think it has to be the file itself.
Did you press f8 and boot into disable signed driver mode? When you system is on and you turn off the phone, open up devices and printers. Watch the i920 icon appear as you plug the phone into the usb port (no usb hubs). Does the icon have an exclaimation point on it?
I did it under device manager. Yeah I pressed F8. When I installed the driver after unplugging and replugging phone in it came up with a red box with two options (guess it's the driver not signed box) but I went ahead and installed it and it said installed successfully.
is the samsung cdma modem 4.34 the right one? I tried finding one that said 4.1.34 but I couldn't find one under google.
It's just weird that even installing the dc23 rom and wozzers kitchen rom without modification it didn't even boot on my phone. I took the 001 out on the dc23 and unzipped with izarc. I'm stuck. It seems like it works for everyone else..i've gotta be doing something wrong?
Attached is the screenshot of the drivers successfully installed.
Win7 has a strange way of dealing with these drivers. you have to play with it a bit. Sometimes just reseting the device will make it okay. Make sure you setup OCTANS before you connect the phone. Are you getting any error messages in OCTANS when you connect the phone? it should display something.
you have to restart after installing the unsigned drivers, and yes hit f8 again to allow disable driver signing.
Yeah it didn't install. I checked the version and it looks nothing like yours. Gonna try it again lol. I didn't restart after installing..it didn't even ask to. Maybe this will work now. Only thing that octans showed was the ondevice string when i hooked phone up. Everytime i disconnect and reconnect it would show ondevice with a string of numbers at the end.
Got it! I followed your instructions and it finally let me use the unsigned driver! Now I am trying to do the rom again and see if it will work under windows 7. I hope I finally fixed the problem.
Thank u.
ok octans flashed successfully with no errors. Now I just gotta see if phone will go past windows orange screen or the white screen that it tends to get stuck on. One problem fixed...fearing another problem may arise.....
.
update...it is on the white screen now...prob 3 min now. I will rebuild the rom w/out removing anything and try again.
you have to be quick.
Have device manager open and waiting.
Connect the phone. (you should see the Omnia 2 logo, and hear the usb tones from the win7 machine)
if there is an samsung icon with an exclamation mark on it, OR if the other drivers are installed, expand mobile devices and then...
Right Click "Samsung MITs USB Sync"
click update driver software...
click "Let me pick from a list of device drivers on my computer" (mayhave to click browse first can't remember)
then click "Have Disk..."
navigate to the i8000 win7 -64bit drivers
click open/ok then wait
by now your phone will have shut off and no longer show up in device manager.
reconnect the phone, wait for the USB tones...
then click "Next"
This may take a couple of tries and if you use a laptop like me you may have to redo this whole procedure everyonce in a while.
After you do it correctly the first time just restart the computer and hit f8 disable signed drivers again.
You should be GTG. If you ever have a problem again, try to disconnect/reconnect the phone, or even restart the phone with the stylus, before reinstalling the drivers.
Let me know how it goes.
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.
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!
Hey all,
I’m not sure if this is the right place, but I hope so (feel free to move this as necessary). A few months ago, I got a Razr XT910 on Rogers. It came with 2.3.5, and so I decided I would give ICS a shot. I successfully managed to get Team Kang’s ICS 4.0.4 running on it, through CWM. That went through fairly easily.
Now, however, I’m trying to get the thing back to its stock ROM (which I already have), and have been trying to get it going through RSDlite (newest version downloaded as of yesterday).
Now I’m not a pro at this stuff, but I wouldn’t say I’m completely inept… but I can’t get it to revert. Mainly because I can’t even get RSDlite to recognize my phone, due to the MTP Usb driver failing to install. (Specifically, it says Code 10: cannot start for the error message). I’ve googled, and searched through here, but all the work arounds don’t work. (Uninstalling, selecting generic drivers manually, etc). I had chalked it up to being an issue with Win7 x64, so I tried a fresh install of XP pro x86 (through a VM), and I get the exact same error in XP.
I don’t know what I’m missing, or what I’ve messed up. It was a fresh install of XP, I downloaded the Moto driver helper as well as a new version of RSD lite. I can’t for the life of me figure out how to get this driver working. I seem to be able have made step by step progress getting there, but I would really like to have this last piece of the puzzle solved, so here I am. Any help/tips would be appreciated!
If any more info is required for help, just let me know, I’ll get you what I can!
Apotheos said:
Hey all,
I’m not sure if this is the right place, but I hope so (feel free to move this as necessary). A few months ago, I got a Razr XT910 on Rogers. It came with 2.3.5, and so I decided I would give ICS a shot. I successfully managed to get Team Kang’s ICS 4.0.4 running on it, through CWM. That went through fairly easily.
Now, however, I’m trying to get the thing back to its stock ROM (which I already have), and have been trying to get it going through RSDlite (newest version downloaded as of yesterday).
Now I’m not a pro at this stuff, but I wouldn’t say I’m completely inept… but I can’t get it to revert. Mainly because I can’t even get RSDlite to recognize my phone, due to the MTP Usb driver failing to install. (Specifically, it says Code 10: cannot start for the error message). I’ve googled, and searched through here, but all the work arounds don’t work. (Uninstalling, selecting generic drivers manually, etc). I had chalked it up to being an issue with Win7 x64, so I tried a fresh install of XP pro x86 (through a VM), and I get the exact same error in XP.
I don’t know what I’m missing, or what I’ve messed up. It was a fresh install of XP, I downloaded the Moto driver helper as well as a new version of RSD lite. I can’t for the life of me figure out how to get this driver working. I seem to be able have made step by step progress getting there, but I would really like to have this last piece of the puzzle solved, so here I am. Any help/tips would be appreciated!
If any more info is required for help, just let me know, I’ll get you what I can!
Click to expand...
Click to collapse
You cant go back to gingerbread after installing ICS as far as i know.