Is there any word when a method to root and install custom firmwares on the Arc (such like Cyagonmod or something)?
I've tried just about most of the common methods I've found so far, and I've gotten nothing.
The only thing I can think of is the fact that the Arc is suspiciously similar to the Nexus 7, so it would be great if someone with one can look into their root and see if a port can be made for the Arc.
Thank you all!
Sent from my highly modified Kobo Arc
Okay, I know nobody really replied, but I'm not going to give up yet! I tried to use Bin4ry's "Root Many Android" method, but that would require that my Arc be connected via ADB, which, for some reason won't work. The Arc has no USB drivers, and I had already installed the Android USB drivers via the SDK manager, but when I do ADB devices, nothing shows up. Has anyone else tried to do this?
I'm also interested in this.. when I connect the Kobo to my computer via usb and hold pwr+vol up windows sees a "OMAP4470" device (this is the name of the TI processor I believe). i tried installing the drivers here http://forum.xda-developers.com/showthread.php?t=2135611 but i can't actually see the device in my device manager.. and also wasn't able to install the hardware manually.. hope that helps
Related
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!
I'm sorry if this is a bad post, I'm new to these forums. I used the viperMod tool to install CWM, rebooted, and I now get the 1a brick error described the the developers section. However when I try to fix it using adb (which I have installed correctly), it doesn't work.
To be specific, my computer (running windows) doesn't recognize that I've hooked it up in devices. I do an adb devices and get "List of devices attached" and nothing shows up. Each time I plug in the prime, I get the usual beep that windows recognizes it is attached, however it does 3 real quick beeps and then nothing happens. I think if I could get it hooked up properly the fix described in the developers section would work, but for some reason my computer doesn't like it.
Any suggestions and/or help would be greatly appreciated!
This might sound a little silly but have you installed the drivers?
If you have the drivers installed windows should detect the device correctly and you'll be able to use adb. There is a link to universal drivers in the dev section, or you can get ASUS' from their support website.
I had the drivers installed properly prior to the CWM installation. However, the 3-tone beep does indicate that the drivers are not installed. Unfortunately the prime isn't showing up in device manager at all, so I need to figure out how to re-install the drivers and see what happens from there. Is it possible to install drivers for a device that doesn't show up in device manager?
Ok, so I can't install the drivers for the device. The only thing device that pops up in device manager is "Full Android on Emulator" in "Other devices". I try to install drivers for it, and it does not like either the universal drivers or the drivers from ASUS.
Why would windows not recognize it as an android device like before? I haven't touched the drivers which I had installed and previously worked. I feel like the only thing stopping me from unbricking the device is a connection issue. Any suggestions?
Well, here was my fix in case someone else had this problem:
In device manager under "Other Devices", I selected "Full Android on Emulator". I selected to install drivers, and browse to drivers. Now where the stock ASUS drivers would not work, the universal driver posted in the dev section worked, although it thought the device was some samsung phone.
It turns out that was OK. I followed the unbrick instructions from 1a in the dev section and all is well.
I appreciate the geniuses who post all these fixes and mods. Great work!
People!, I'm about to pull all my hair out on this one
Vibrant is soft bricked in a boot loop after a incomplete flash, I am able to get it into download mode but both my windows machines say USB device isnot recognized, and thus, I cant use ODIN to return to stock. When I try to manually point windows to the samsung drivers I get nothing…
So far I have tried drivers from:
-Bay_wolf's AIO Vibrant Toolbox 2.5
-USB drivers for vibrant from samsung support site
-Drivers from samsung keyes
Side notes that might help: I was perviously using a Hellybean Rom. My device displays "Galaxy S gt-9000" on boot... not sure when that came to be but maybe some rom changed some important recognition stuff??...
I found this thread http://forum.xda-developers.com/showthread.php?t=1008383 but no help...
Any help would be greatly appreciated!!
Try a different USB cable. This happens more than you'd think. Even cables that have worked just fine hundreds of times.
Also.... Locate the drivers in system/device manager and delete them manually and try to install them again. Unplug device and install fresh ones from either aio toolbox or Kies, then plug phone back in.
Best of luck!
Toast6977 said:
Try a different USB cable. This happens more than you'd think. Even cables that have worked just fine hundreds of times.
Also.... Locate the drivers in system/device manager and delete them manually and try to install them again. Unplug device and install fresh ones from either aio toolbox or Kies, then plug phone back in.
Best of luck!
Click to expand...
Click to collapse
Thanks a ton for reply but, sadly, no dice.
Tried connecting the phone, getting the "unrecognized device" prompt, finding "unknown device" in device manager, right clicking to uninstall. rebooting my machine, using various install methods to re-install drivers, re-connecting, and nothing.. same issue...
I lost the original cable a while back, but can't accept that NONE of the other 5 cables used are all broke... specially if the computer recognizes something going on... is it worth buying a new one?
Losing hope here, been like this for 4 days now, think it's time to go get a new phone. :crying:
Even so, it would have been nice to get what was a perfectly working phone back if only to keep it as a mp3 payer.
If anybody in New York, NY has a working odin set up that can do this for me, I have a 6 pack of your favorite beer with your name on it.
It could be a hardbrick such as bootloader getting corrupted that happened to my Sony Xperia Play (now an expensive paper weight).
I assume you boot into download mode by holding the two volume buttons, then connect the cable? Have you tried on a different PC? It can also be the weak powered USB port on the PC. Also when you uninstall the Samsung driver, check the option to also delete USB driver and uninstall any drivers. Also which version of the driver are you using, have you tried version Samsung USB Driver 1.5.3? And the drivers from here: http://www.samsung.com/us/support/owners/product/SGH-T959ZKATMB#
For what its worth, the gt i9000 screen appears after your on a custom GB boot loader and Odin back to stock (or probably Odin flashing any other ROM) you can change it by flashing the GB boot loader again. My phone says its a i9000 too, but I'm just about lazy enough to not bother changing it, lol.
So that's unrelated.
eksasol said:
It could be a hardbrick such as bootloader getting corrupted that happened to my Sony Xperia Play (now an expensive paper weight).
I assume you boot into download mode by holding the two volume buttons, then connect the cable? Have you tried on a different PC? It can also be the weak powered USB port on the PC. Also when you uninstall the Samsung driver, check the option to also delete USB driver and uninstall any drivers. Also which version of the driver are you using, have you tried version Samsung USB Driver 1.5.3? And the drivers from here: http://www.samsung.com/us/support/owners/product/SGH-T959ZKATMB#
Click to expand...
Click to collapse
Ok, faith momentarily restored. But I have questions:
-What do you mean when you say "check the option to also delete USB driver and uninstall any drivers"? I dont get such a prompt from right clicking on "unknown device" and selecting uninstall? Is there another method to uninstalling drivers?
-In the link attached, I can only find "Device(Install),USB Driver (Software) (ver.1.0)" not the 1.5.3 version mentioned. What am i doing wrong here? currently searching google for the 1.5.3 but finding nothing.
I get into download mode by holding volume- up + power. Have 2 PCs ( win xp and win 7) and a mac running mountain lion (but never ever have been able to get Heimdall to work, so devoting time to odin.)
Thank you for the time + help, guys, I really do appreciate it in the time of utter un-nerdness.
If the device is already installed it will have a check box that said "Delete the driver software for this device." If its unknown then obviously not. By "uninstall any driver", I mean uninstall any Android drivers you current have installed and reboot before you reinstall the new driver.
Although I doubt it will make a difference than the one I linked above, you can try the Samsung driver version 1.5.3: http://www.mediafire.com/?r0uc3h413qcy80z
If you did manage to get into download mode and see this: http://images.google.com/search?num=10&hl=en&site=&tbm=isch&source=hp&q=download+mode
Then it mean there is a very good chance you can restore the phone, if you can find a computer to recognize it and Odin to see a COM port.
I definitely think it would be worth the money to go buy an OEM USB cord. I can't tell you how many times I have seen this and a new USB is the fix.
sent from the depths of helly bean
OK guys...
My friend, who also owns a Vibrant, let me borrow the cable that came with the phone for the last 2 days.
Tried to make ODIN work on both PCs at home, gave Heimdall a shot on my mac, even hijacked a computer at work for the better part of the morning and freshly installed USB drivers 1.5.3 before connecting. All for nothing... “Unknown device” across the board....
At first I felt that with being able to get into download and have SOME kind of a reaction from connecting to PC had to be a good sign. Almost completely convinced that there is some unknown, unworkable hardware problem present. Definitely, officially, unremarkably out of ideas here.
Nothing is beautiful and everything hurts.
Last thoughts? Options at this point?
Also, tried One-click Unbrick tool on mac. I got a "is your phone plugged in, is it on download mode?" error, but anyone reading this down the line with a similar problem should check it out.
http://forum.xda-developers.com/showthread.php?p=15330252
Hi there
I have seen some posts where users are having difficulty connecting Xperia to their PC or ADB. Therefore, I am writing this guide to help you all.
The guide was prepared using Windows 7 Ultimate but should work with Windows XP and Windows 8.
Firstly, Sony uses a different driver for their Xperia devices and therefore, sometimes you are unable to install drivers for your devices especially for ADB commands.
IF YOU ARE LUCKY
There are few ways to get around to install drivers for your device. The most convenient and easy is you plug in your device and wait for automatic detection of your device. Make sure you have USB connected as MTP in MY XPERIA in SETTINGS of your phone. The device drivers would be automatically installed by Windows update.
METHOD
If suppose you can not install your drivers, connect your xperia and then on your PC, go to My computer > Properties>Device Manager.
You should see an undetected hardware with a yellow exclamation mark over it. Open it and click on update my drivers. Then choose GOOGLE DRIVERS by choosing hard-drive. This should install the drivers for you. If this doesnot work. Try the attachment with the post where the drivers are modified to work with Sony Xperia Devices.
Follow the same steps but this time choose the attachment folder to search for drivers. It might say, the drivers are not verified. Just Ignore it and carry on installing them. You will need to unzip these files.
IF suppose you do not see any exclamation mark while you connect your xperia. Just go to control panel and add new hardware. Select, I will choose my device and then install from hard-disk. Select the folder where you have unzipped the files and you are good to go. The name of new hardware is not important as windows will read the drivers files and install drivers for Xperia.
This will install all drivers for your device. If there are two or more drivers while installing them. Redo the steps and install all of them individually.
Suppose your ADB still doesnot work, then
FOR ADB DRIVERS :
Download the ADB Universal Drivers and connect your device. Then hit install. The ADB drivers will be automatically detected and installed.
Further, if these tricks fail, you can delete the unknown driver from your control panel and then try finding it again by using refresh button(scan for new hardware changes) in device manager.
Another trick is to click on unknown drivers and delete them. Connect your phone to the PC and restart your phone. Then scan for new hardware in device manager. The drivers should be installed for your device.
If still there are some problems, I will try to help you out.
DOWNLOAD LINKS
DOWNLOAD GOOGLE DRIVERS FOR MTP/ PC ETC
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
DOWNLOAD UNIVERSAL ADB DRIVERS HERE :
http://adbdriver.com/upload/AdbDriverInstaller.exe
Sony Xperia Drivers for ADB.
DOWNLOAD FROM HERE
reserved
it works on win 8.1?
jatinrungta said:
it works on win 8.1?
Click to expand...
Click to collapse
No,I dont know who reads this tutorials anyway wnen there already 10 of them for this particular issue.
Sent from my Xperia U using Tapatalk
XperianPro said:
No,I dont know who reads this tutorials anyway wnen there already 10 of them for this particular issue.
Sent from my Xperia U using Tapatalk
Click to expand...
Click to collapse
true that, thought it would work beacuse it is posted this week
XperianPro said:
No,I dont know who reads this tutorials anyway wnen there already 10 of them for this particular issue.
Sent from my Xperia U using Tapatalk
Click to expand...
Click to collapse
jatinrungta said:
true that, thought it would work beacuse it is posted this week
Click to expand...
Click to collapse
These drivers are seem to work perfectly on Windows 7 and it should work just fine on any other windows!
Hnk1 said:
These drivers are seem to work perfectly on Windows 7 and it should work just fine on any other windows!
Click to expand...
Click to collapse
nope, windows 8+ is different
I'm getting a lot of problems with drivers for this device, seems Sony's guys did it just to say:
"Ok, now this device got some drivers, lets play poker :"
It's serious. To get ADB driver working was a lot of work, just got it working because our friend Ashu1307 posted this link for me ( maybe it can work for ya= http://forum.xda-developers.com/showthread.php?t=2552505)
Ok, that's nice since it was the only driver that's not working on windows 7.
I said windows 7
Now I'm on windows XP, tryied 2 machines already, and this goddam piece of **** don't have any driver working. Nothing, neither MTP, nor fastboot nor ADB nor flashmode (mass storage works, the ones I've quoted are detected, but don't work)
PC companion is another thing I'm hating. First I have to download the Web Installer, 27MB of nothing, since after the download it has to update because the sony's website offers outdated file. THen I download support zone, which detects phone but not the model.
What do I do? I'm going weird just about to break this phone on the wall, I never had so much problems on motorola's or samsung's or enen old sony ericsson's devices.
Before,my PC used to display an error whenever I tried to transfer files from my pc to my Xperia Sola.But after changing the kernel,I could transfer files with ease.So,do you think the problem in the kernel is related to this error?
I never had problem with drivers.
Trying another computer, still having the problems, I use the DoomKernel, do you think it has to do with it ?
As the title describes...
Short story: First time I ever tried to do something with a mobile and I´ve fail...annoying...
Done everything as the thread describes over and over but the program cant find the device.
Tested to download the program and installed it several times, made the adjustments in my Z1 as the thread describes several times...started the sony companion ...tried to install usb drivers instead...
The phone seems connect to my computer as usual but this program cant find it!
Theone thing that I havent done yet is to replace the usbcable but....
Anyone got any suggestions?