Hi there!
I'm a citizen of India and I recently bought an Indian manufactured phone. This phone is the Karbonn A3+.
The specifications of which, I can't give you since this is my first post. Now, coming to rooting this phone, I've tried EVERYTHING. And, when I say, EVERYTHING, I mean it. I've tried, Universal Androot, z4root, Framaroot, Bin4ry, Rootx, SuperOneClick, and the old traditional cmd method by pushing busybox, superuser and all the other files onto the device.
Now, I ended up realizing that my phone's drivers weren't on the manufacturers' website, and were nowhere to be found on the internet. Hence, I downloaded an application called PDA Net + on my phone, and got the corresponding computer software application from their website. That gave me PDA Net for my computer and once I plugged in my device, it installed the following drivers :
1) USB Composite Device ; 2) Android ADB Interface.
The device is yet not recognized by the computer and only when placed on "Mass Storage" can it be detected for file transfer. Sometimes, it is detected to some extent but on some applications (such as bin4ry) it says "error : device not found".
Desperate need of help. Thanks.
MicroFox
Mihir Parekh said:
Hi there!
I'm a citizen of India and I recently bought an Indian manufactured phone. This phone is the Karbonn A3+.
The specifications of which, I can't give you since this is my first post. Now, coming to rooting this phone, I've tried EVERYTHING. And, when I say, EVERYTHING, I mean it. I've tried, Universal Androot, z4root, Framaroot, Bin4ry, Rootx, SuperOneClick, and the old traditional cmd method by pushing busybox, superuser and all the other files onto the device.
Now, I ended up realizing that my phone's drivers weren't on the manufacturers' website, and were nowhere to be found on the internet. Hence, I downloaded an application called PDA Net + on my phone, and got the corresponding computer software application from their website. That gave me PDA Net for my computer and once I plugged in my device, it installed the following drivers :
1) USB Composite Device ; 2) Android ADB Interface.
The device is yet not recognized by the computer and only when placed on "Mass Storage" can it be detected for file transfer. Sometimes, it is detected to some extent but on some applications (such as bin4ry) it says "error : device not found".
Desperate need of help. Thanks.
MicroFox
Click to expand...
Click to collapse
I found this guide for the A3: http://forum.xda-developers.com/showthread.php?t=2165554...if you are lucky it will work for your device.
justmpm said:
I found this guide for the A3: http://forum.xda-developers.com/showthread.php?t=2165554...if you are lucky it will work for your device.
Click to expand...
Click to collapse
I haven't thoroughly searched for a root tool for the A3. I will tomorrow morning. Any idea other than this? Because, if this doesn't work, does that mean I am stuck with an unrooted device?
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.
Anyone in here can help me please? I tried to root my samsung galaxy player 4.0. I read lots of topics about rooting using superoneclick V2.2. I enable USB debugging mode, unmount my SD, installed samsung kie on my computer, plug in the cable and click connecting. And I run superoneclick.exe as Admin and I click ROOT! But after few mins, few lines show up and the root not work.
Here is the picture of the rooting result after waited few mins, still nothing happen. Please Help, I dont wanna try again until I find out if I did anything wrong. It has something to do with ADB interface or something?
Have you loaded an insecure kernel using Odin?
SusieGalaxy880 said:
Anyone in here can help me please? I tried to root my samsung galaxy player 4.0. I read lots of topics about rooting using superoneclick V2.2. I enable USB debugging mode, unmount my SD, installed samsung kie on my computer, plug in the cable and click connecting. And I run superoneclick.exe as Admin and I click ROOT! But after few mins, few lines show up and the root not work.
Here is the picture of the rooting result after waited few mins, still nothing happen. Please Help, I dont wanna try again until I find out if I did anything wrong. It has something to do with ADB interface or something?
Click to expand...
Click to collapse
The easiest way to gain root would be to flash a ROM that has root already. Such as this stock ROM: http://forum.xda-developers.com/showthread.php?t=1512331
nop, duno what is that. Im new android user, I only have this device for few days. In youtube video, those ppl never mention any other step.
1) install samsung kie
2) enable USB debugging mode
3) unmount SD card
4) pluged in usb cable (i click connect on my device, it is in mass storage, or I shouldn't have to click anything? I Just plug in the cable and hit root on superoneclick?)
These kinda more difficul steps,, and i dont wanna mess any of those because if any step goes wrong, I duno how to fix it. Aren't most people use the easy way to superoneclick to root and successful? I just want to know which step I did wrong for my fail root. I dont wanna mess with any deeper or more diffiuclt stuff.
SusieGalaxy880 said:
nop, duno what is that. Im new android user, I only have this device for few days. In youtube video, those ppl never mention any other step.
1) install samsung kie
2) enable USB debugging mode
3) unmount SD card
4) pluged in usb cable (i click connect on my device, it is in mass storage, or I shouldn't have to click anything? I Just plug in the cable and hit root on superoneclick?)
Click to expand...
Click to collapse
You shouldn't have connected mass storage.
I think my problem is the driver not propertly installed + I click connect to mass storage on the device.
I heard we need
1) Microsoft.NET Framework 4+ (I have win 7, so already has)
2) Samsung USB driver to mobile phone (samsung Kies come with that usb driver.)
3) Do I also need to install the Android SDK/ADB driver?
SusieGalaxy880 said:
I think my problem is the driver not propertly installed + I click connect to mass storage on the device.
I heard we need
1) Microsoft.NET Framework 4+ (I have win 7, so already has)
2) Samsung USB driver to mobile phone (samsung Kies come with that usb driver.)
3) Do I also need to install the Android SDK/ADB driver?
Click to expand...
Click to collapse
From my experience just have Windows 7 doesn't ensure have framework 4+ so check for a download on that.
If your USB debugging mode is ON then you shouldn't get the "connect mass storage" option on the device at all, so double check that (uncheck and recheck it if necessary.
Personally I choose to skip Kies entirely and just download the drivers only, but the first time you plug the player in with Debugging on windows should do it driver search thing down by the clock and it installs (i think 3) different drivers for the player (different then the mass storage driver) if you jumped in to superoneclick before that finished that may have been part of the problem, if you didn't get those to install then sounds like a driver issue.
I just tried the 2nd time, the result is the same. FAILED!!!
I window update everything including the microsoft.NET framework 4+. Restart computer.
Uninstall samsung kies and the prior samsung driver, and I downloaded the newer V1.4 Samsung USB driver for mobile phone from XDA forum and installed, restarted computer.
I didnt press any key while on the device to get into mass storage mode.
I plug in the cable, on USB debugging mode + unmount SD card.
I wait for driver software installation "READY TO USE" as u can see in the new picture, with all the check mark on. This time i though I can make it throught, but as u can see the result on left side, almsot similar result. =(
"No such file or directory" not an single OK. If successuf rooting, i see people get 'OK' on each step. This time i really follow each every step, still fail!!!
I have no idea what is the problem? Everyone seem successful ROOT first time.
Did I miss an very important step or my device already mess up somehow?
I only didnt install ADB driver, but no one talk about needed to install that before ROOTING.
SusieGalaxy880 said:
I just tried the 2nd time, the result is the same. FAILED!!!
I window update everything including the microsoft.NET framework 4+. Restart computer.
Uninstall samsung kies and the prior samsung driver, and I downloaded the newer V1.4 Samsung USB driver for mobile phone from XDA forum and installed, restarted computer.
I didnt press any key while on the device to get into mass storage mode.
I plug in the cable, on USB debugging mode + unmount SD card.
I wait for driver software installation "READY TO USE" as u can see in the new picture, with all the check mark on. This time i though I can make it throught, but as u can see the result on left side, almsot similar result. =(
"No such file or directory" not an single OK. If successuf rooting, i see people get 'OK' on each step. This time i really follow each every step, still fail!!!
I have no idea what is the problem? Everyone seem successful ROOT first time.
Did I miss an very important step or my device already mess up somehow?
I only didnt install ADB driver, but no one talk about needed to install that before ROOTING.
Click to expand...
Click to collapse
have you tried resarting your player then enable usb debugging then plugging in the USB?
Also where did you get your Superoneclick?
I didnt restart my device before rooting.
I got the superoneclick from XDA main page the offical one with 500+ page of posts and reply. "Superoneclickv2.2 -shortfuse.zip"
Try using doomlords rooting toolkit, it worked for me.
http://forum.xda-developers.com/showthread.php?p=18805532
thanks for info, but I duno how to use the DooMLoRD's Easy Rooting Toolkit. Any instruction? I have no idea why my device is so diffiuclt to root, as other people rooted very easy
I used version 2.3.3 to root mine.
Got to shortfuse.org and scroll down to the 2.3.3 download link.
I tired the 3rd time today, failed again, same outcome. This time I follow each step carefully, and I used superoneclick v2.3.3 Before ROOT, I make sure all the "READY TO USE" check mark on. But still hang at Shell Rooting device step #5. I patient waited for 20mins, still hang at this step.
I shoulda try root when I got it first day. Is there possible some mess up app might cause this? I never heard anyone have any diffiuclty Rooting their galaxy player 4.0 YP-G1 US version with superoneclick after so many tried. I officially give up. I only have this device for 1 week..............
Kernal Version 2.6.35.7-G1UEKI8-CL562400 [email protected] #2
Build # Gingerbread.UEKI8
Firmware V2.3.5
Model Number: YP-G1
I found a very important issue might cause this failed. When I check the unzip folder, the Expoits folder IS NO FILE, EMPTY, but when I check the original zip file, it has 3 important files "GingerBreak,psneuter, zergRush" files (on the v2.2) I try unzip on desktop, pull out this Exploit folder, pull out the file, none work. I even uninstall winRAR and restall the newer version. These 3 files on the exploit folder in superoneclick v2.2 seem CANNOT pull out of the zip file no matter what I try. I think on shell Rooting device step #3 started the problem cuz cannot locate these few important exploit files. I just found out the unzip folder have no those file (psneuter,zergRush), while the original zip file has, and I cannoot pull out those file out of the zip folder NO MATTER WHAT I TRIED. Both superoneclick v2.2 and v2.3.3 exploit folder, i cannot get those file out of the zip folder.
Got rooted successful the 4th tired. Problem is my antiviurs always remove the psneuter & zergRush files in exploit folder when I extract everytime. And I didnt notice this problem. So I was rooting without these 2 important files in superoneclick folder. Now I disable antivirus, so i can extract those file and start rooting, after done rooting, i turn antivirus back on.
another problem
daniel644 said:
have you tried resarting your player then enable usb debugging then plugging in the USB?
Also where did you get your Superoneclick?
Click to expand...
Click to collapse
can someone help me i have the ``firmware uprade encountered....``
i can go to the the warning but
-if i press up to continue it return to firmware....
-if i press down the same thing
thanks.
Hello, im looking proper guide how to root and install Google Play Store on Lenovo S850.
I was on old firmware with playstore, upgraded to 4.4.2 and lost playstore after update via Lenovo Smart Assistant. Checked with root-checking with no root result. Ty in advance.
nazzier5463 said:
Hello, im looking proper guide how to root and install Google Play Store on Lenovo S850.
I was on old firmware with playstore, upgraded to 4.4.2 and lost playstore after update via Lenovo Smart Assistant. Checked with root-checking with no root result. Ty in advance.
Click to expand...
Click to collapse
I made THIS THREAD about Lenovo S850 rooting method and it prooved to be successful. Next time you want something, search before. Good Luck!
bogdann8 said:
I made THIS THREAD about Lenovo S850 rooting method and it prooved to be successful. Next time you want something, search before. Good Luck!
Click to expand...
Click to collapse
i tried it. but when "wait for the progress bar to show 0% and connect the phone (still swiched off)" then it nothing do, i tried it 3 times.
nazzier5463 said:
i tried it. but when "wait for the progress bar to show 0% and connect the phone (still swiched off)" then it nothing do, i tried it 3 times.
Click to expand...
Click to collapse
Ok, so you set flashtool like I said in my thread but there's no progress when you connect your switched off phone to PC. That's probably because your phone isn't recognised properly. I don't know if there's any driver installed on your PC, but you have to reinstall it somehow. The best method I encountered is to connect switched off phone and, when windows prompts, choose to install drivers from specific folder (try ADB folder or FlashTool, there's drivers for xp/vista/7 in each one that worked for me). This is a point when you must figure out by yourself, depending on your situation. Let me know if something changes.
Hello,
I just bought an S850 and I can't even install the drivers. When I connect the phone to the PC, it detects it, but it doesn't ask for drivers. It just says that Windows didn't found any drivers for this device and then it disappears from the Device Manager. Tried to manually install the .inf files, but then I get an error message saying that these files cannot be installed manually. So basically I'm stuck at the very beginning of the root process
Any help is greatly appreciated!
VasileffBG said:
Hello,
I just bought an S850 and I can't even install the drivers. When I connect the phone to the PC, it detects it, but it doesn't ask for drivers. It just says that Windows didn't found any drivers for this device and then it disappears from the Device Manager. Tried to manually install the .inf files, but then I get an error message saying that these files cannot be installed manually. So basically I'm stuck at the very beginning of the root process
Any help is greatly appreciated!
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showpost.php?p=57671051&postcount=5
Hello Friends!
I'm from Argentina, and recently bought an oppo find x (chinese version].
The first thing I wanted to do was install more locale 2, so that I can have most of my apps in Spanish.
Of course before I created this topic I searched if there's a solution out there, and I found this thread:
https://forum.xda-developers.com/find-X/help/install-locale-t3818383
I followed that, step by step but doesn't work.
Indeed I tried the "long" version of it here: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
But with no luck. The problem is that I never get the prompt notification on my phone allowing usb debuggin (step 11).
So I think the problem must be in the drivers, that for some reason my windows doesnt install the drivers of my phone (but I can Transfer files with no problem....that's strange).
But where can I get those drivers? They're not even in oppo page.
This problem is driven me crazy, even more cause I think I'm the only one with this issue!!!
PLEASE HELPPPP
New information: I tried with another PC (with Windows 10) and with another cellphone (vivo x21). With both devices and both PC the problem is the same: when I write the command adb devices no devices appear, despite I have the USB debugging enabled in my phone. If I write the command adb shell it says no devices/emulators attached.
I'm have no clue what to do now.
Hello everyone.
I have found a solution. I leave it here, in case someone is in this 1% like me with problems with adb:
The problem was the drivers: apparently my windows doesn't have the correct driver to support ADB android interface, and it doesn't get installed automatically with windows update.
So, what I did was download the drivers from here: http://adbdriver.com/downloads/
And ready, problem solved.
Now my google assistant doesn't work with more locale....but that's another problem...