Hello all,
EDIT (20180902 @ 1230 EDT): So, it must be a driver issue on my desktop machine, as I was able to communicate with the phone using my laptop (the original computer I used to root the phone). If anyone cares to explain anything to me regarding my original post, feel free, but consider the original issue solved. I have other issues that are unresolved though, such as the lack of operational wifi/BT (no MAC address) that I would gladly accept help with.
I'm attempting to turn an old Stratosphere into a portable Kali Linux device, and I thought the first step would be to root it. I followed these instructions: "https://rootzwiki.com/topic/7840-kernel-guide-root-your-stratosphere/" and everything seemed top be fine, however, now I have no MAC address (among other things) so I cannot connect to wifi. Much googling later, still no resolution found.
So, I ended up installing the CWM recovery by following this: "https://rootzwiki.com/topic/11949-recovery-clockworkmod-recovery-v-5027/". I did a heard reset, factory reset, and rebooted. Now, when attempting to flash the stock ROM using Heimdall and running heimdall detect, I get an libusb error -12, and even though Heimdall then reports "device detected", I cannot flash the ROM (get same libusb error).
I'm new to this whole process. I'm not an Android developer, programmer, etc. I consider myself relatively computer-literate. I have a little bit of Linux experience, but I'm currently using Win10 for all of this experimentation. I'm not sure what I've done wrong, or how to fix it. Why did the MAC address disappear? I have no BT either. I always thought the MAC address was a hardware parameter, but I'm assuming that flashing the rooted image is what has caused this issue.
Anyway, the Stratosphere is running Android 2.3.6. Any help would be appreciated. Thanks in advance
Related
i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
Hello everyone from XDA!
I've been reading several different posts on the Samsung Galaxy S2 GT-i9100, and though many have been helpful (thank you!), I just can't seem to find the solution I'm looking for.
Not long ago I upgraded the stock firmware from Bell Canada (forget the specs) to:
Android version: 2.3.5
Baseband version: I9100XXKI4
Kernel version: 2.6.35.7-I9100XWJK3-CL647431 [email protected] #2
Build number:: GINGERBREAD.XWKJ3
My phone was also rooted.
Recently, however, I've been trying to upgrade to ICS but without success---and I've tried a number of ways, from the XDA forum to various websites around. I suspect the problem may be with my computer (USB related) and not the phone. I'm not sure, I'm not an expert, which is why I come to you for help, please.
The first and only attempt of ever upgrading the firmware (see above) was a success; as per directions, I used Odin: the PIT, PDA, PHONE, and perhaps CSC as well. It has been some time since the ugrade, and in the mix of trying new and different firmware (without success) I have forgotten exactly what happened.
So my problem, now, is that any time I try to upgrade to ICS (or another firmware for that matter) my computer ends up crashing when the flashing of the phone reaches the "boot.ini" stage. My computer (Windows XP Professional) crashes and a blue screen appears with an error---something to do with USB.
I just can't seem up update my phone.
The phone still works perfectly fine, but I really want ICS. I have tried with and without Kies installed. In fact, Kies even allows me to upgrade to a newer version (though it's not ICS) than I currently have. Unfortunately, though, when I try upgrading via Kies, I am also unsuccessful.
Could this just be my computer's USB? The drivers? If you have had similar experience and know the answer please help!
Hookah-Hoodlum said:
My computer (Windows XP Professional) then crashes and a blue screen appears with a USB error.
Click to expand...
Click to collapse
This screams to me it's the computer.
Have you tried on a different one?
Hookah-Hoodlum said:
The phone still works perfectly fine, but I really want ICS.
Click to expand...
Click to collapse
I agree it sounds like a problem with your PC. You can bypass that problem by using Mobile Odin.
As ctomgee says, a blue screen error indicates a problem with your computer, not phone.
The way you are trying to get ICS also seems strange, the current way to get it would be:
Root phone and install CWM using Chainfire kernel.
Download and put the ICS rom on your sd card.
Boot into CWM, wipe everything and install the rom.
Reboot and you have ICS.
What file were you trying to use to upgrade to ICS?
Thanks
@ ctomgee: I've considered using a friends computer but I'm worried about damaging their computer by having an error appear.
@ oinkylicious: Thanks, I never knew about mobile Odin. I'll check it out.
@Kaze105: I appreciate the steps, thank you. The new firmware is GT-I9100_XEU_I9100XXLPB_I9100XXLPB_I9100XEUKH2.tar.md5 and Kernel_I9100XXLPB.tar.md5, respectively.
If any of you have links or suggestions as to favorite roms, kernels, or the like, well I'm open to suggestions!
Hookah-Hoodlum said:
@ ctomgee: I've considered using a friends computer but I'm worried about damaging their computer by having an error appear.
Click to expand...
Click to collapse
Can't hit the target if you don't take the shot...
I'm having a similar problem.
I decided to root my galaxy s2 with the CF-kernel (so this is my initial flash, and mobile odin is no alternative).
But every time I start (in Odin), my computer crashes.
I tried it on a "native" Windows XP x86 system and in a virtual machine with Windows XP x86(because I am using Linux only).
On my second machine with Windows 7 64bit, I cannot install the device drivers correctly (the CDC component fails to install), so Odin (and Kies as well) does not recognize the Device.
Is there any suggestion or alternative to Odin especially for Linux systems?
Thanks in advance!
Edit: enabling USB 2.0 for the virtual machine and reinstalling the USB-drivers did the trick (the native windows system has no USB 2.0). Now it hangs on connectionsetup, but that's another problem.
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.
So after flashing 10/17/15 release of Tesla Arc_Flash I am unable to connect to the phone through adb without deleting the driver and adding it as an adb device. I have installed the LG G3 Verizon drivers but I am still not able to connect. In the device manager it shows that the drivers aren't there but also that they are there as a portable device. hxxp://tinypic.com/r/30ua82f/8
Also the command prompt is below. Brand new adb server started.
hxxp://tinypic.com/r/71myr4/8
Any help would be appreciated. If you need logs or anything else I am happy to provide it. Also since I feel this may get asked... Yes I have USB Debugging turned on. Have tried with Root for adb on and off and nothing seems to work. I can get it to connect through network but I don't want to constantly have to look for the IP address and port. This was also an issue in the previous release of Arc_Flash so please let me know.
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from http://www.lg.com/us/support-mobile/lg-LGVS985. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
roirraW "edor" ehT said:
Hi! Exactly what drive did you install and where did you get it from? Here is where I get the driver from. Try rebooting the PC (without the phone connected) after installing the driver. Using the original cable that came with it, connect the phone to a different USB 2.0 port than you had tried previously - it can take up to 10 minutes to finish loading the driver. When it's complete Device Manager should have a listing for the phone in the Modem section, which isn't currently listed in your screenshot. Until you can get that solved you won't be able to reach it with adb.
Have you searched the Tesla ROM thread to see if anyone else has had the issue, in case it's specific to Tesla?
Click to expand...
Click to collapse
I searched the ROM thread but found nothing matching what I am experiencing but I followed everything even close to it. I installed those drivers just now and restarted both computer and phone. Still comes up as an unknown driver. There is no modem section inside of the computer still. I can manually add the drivers but it still doesn't seem to help.
Also to add. I also have tried to add it as a modem and it gives Windows Error code (10) that it can not start the driver. I forgot to mention. Windows 10.
Well, I've connected to my phone via adb and used the LG flash tools on Windows 10 last week or the week before, although I have my insider updates set to Fast Ring and I kinda regret it because there was a recent huge push of a beta Windows, and they've broken how I had my video associations set up and I can't get my subtitles to work any more either. Sorry for off topic. My point is since Windows 10 is considered a constant "change in progress", and especially for people like me who joined to get "insider" builds, it's hard to tell what makes things not work. My main reason for even being on Windows 10 is to see what they come up with in their insider builds, but I guess when it mucks with my video enjoying ability, I start losing my patience.
I would seriously consider trying a different PC, or if you have the capability of performing a fresh Windows installation, even of Windows 10, that very possibly would fix it. Or if you just recently, within the last 30 days, upgraded from an earlier Windows to Windows 10, and didn't perform a clean installation, you can revert the upgrade through the the Windows settings. No idea if reverting would solve the problem, either, though.
As @bweN diorD pointed out in another similar thread just yesterday or the day before, when someone in your situation ends up trying a different PC, then everything goes smoothly. As far as the cause, there's too many variables.
If you can't use anyone else's PC, there's an outside chance that you could even do it at a library computer, as long as you don't reboot the PC (which I usually recommend after initially installing the driver, but sometimes things work fine without that). Rebooting a library PC usually undoes all changes, putting it back exactly the way it was.
Let us know how you make out.