I've spent all day and night trying various attempts to root my son's Nabi.
I usually use Mac so am also hogging my other son's PC to attempt to get it to work.
I think I've got a couple of issues but not sure if it's me or the PC -
1 - The PDAnet program won't connect properly it tells me HTC Sync error -1 or -2
So I tried an older version of Nabilab which did connect to the tablet and provided the serial number through both ADB and Fastboot.
2 - I managed to boot in to TWRP but then when trying to recover it won't show me any files to install
I'm at a complete loss now as to how to root it. I'm just fed up of having to delete games for him to make room for new ones, despite having 32GB of space on his SD card.
Please help, I'm pulling whats left of my hair out!
you still having issues? one thing to try when installing PDANet is to select the samsung drivers instead of the HTC, these worked fine for me, NabiLab2 and NABILABGUI also have some PC drivers which work with both x32 and x64 PC's, I'm not sure on the MAC side of things. Nabilab is probably the easiest way of just rooting also. theres a couple of videos on you tube which may also help search for nabilab and root nabi 2
earwig999 said:
2 - I managed to boot in to TWRP but then when trying to recover it won't show me any files to install
Please help, I'm pulling whats left of my hair out!
Click to expand...
Click to collapse
What are you trying to recover or install? Once you find the right TWRP for your OS version should be as easy as installing SuperSU. https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
There is also this information that might be helpful http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Related
I've just recently rooted my CDMA Hero using the unrevoked method and I had a lot of trouble figuring it out. I some how got the adb drivers to install on my phone (I was so annoyed by the time they installed I wasn't even paying attention when they did) but now they have disappeared (I think because I downgraded the phone to get it out of a booting screen loop) and I can't get them to re install no matter what I do. Im running on windows 7 64 bit and even when the bubble pops up and says that new drivers are installing when I go to type in
Code:
adb devices
it tells me that no internal or external paths can be found. Any tips for installing these would be greatful. I want to still use adb in the future.
Yeah nevermind. I was charging my phone via computer and an installing drivers bubble just so happened to pop up after I had been tinkering with loading themes. Figured I'd go ahead and give a shot to see if it was the drivers I needed turns out it was.
No idea what really went down but I'm glad i got adb working properly lets hope it's more permanent
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.
I received a new Kindle Fire for Christmas(2015) and it is wonderful. However, I want to be able to test the apps I'm building on it. So far it has been a nightmare to root the device. I even tried RootKing, which didn't work at all. The main issue is finding XP drivers for the usb. I plug it in and I have some access to various directories, but not enough to get fastboot on there to finish the root process. Yes I did turn on debugging. Have tried four different programs, but nothing has worked. Currently running 5.1.1 on the Kindle. Can anyone point me in the right direction?
Tried:
root_fire.zip
Amazon-Fire-5th-Gen-Install-Play-Store.zip
AmazonFire5thGenSuperTool.zip
GadgetClass_Simple_Super_Tool-Fire-5th-Gen
And When I try to install drivers from other sources, it keeps telling me it can't find what it needs to install.
Thanks!
gilead7 said:
I received a new Kindle Fire for Christmas(2015) and it is wonderful. However, I want to be able to test the apps I'm building on it. So far it has been a nightmare to root the device. I even tried RootKing, which didn't work at all. The main issue is finding XP drivers for the usb. I plug it in and I have some access to various directories, but not enough to get fastboot on there to finish the root process. Yes I did turn on debugging. Have tried four different programs, but nothing has worked. Currently running 5.1.1 on the Kindle. Can anyone point me in the right direction?
Tried:
root_fire.zip
Amazon-Fire-5th-Gen-Install-Play-Store.zip
AmazonFire5thGenSuperTool.zip
GadgetClass_Simple_Super_Tool-Fire-5th-Gen
And When I try to install drivers from other sources, it keeps telling me it can't find what it needs to install.
Thanks!
Click to expand...
Click to collapse
Sounds like the forum is wrong, go here :
http://forum.xda-developers.com/amazon-fire
SOLVED! I am ROOTED! It Didn't Brick!
bibikalka said:
Sounds like the forum is wrong, go here :
http://forum.xda-developers.com/amazon-fire
Click to expand...
Click to collapse
I managed to cobble together the drivers I needed. Apparently XP needs
Universal ADB drivers AND MTA drivers in order to work. Once those are installed, it works wonderfully! Any way I can upload the file for others? Or do I need to place it on a server and link?
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
tokococo said:
Hi guys,
I have been searching for hours but I can't seem to find how to fix my problem.
I have a new Z5 Compact that I was trying to flash with the stock firmware but I somehow managed to brick it. I don't think I had the drivers installed properly when I tried to flash with flashtool but since flashtool didn't even detect my phone or appear to begin flashing it I don't know how I bricked it. Anyway after trying for hours to fix it on my own I can't seem to find the information that I need. I have installed the drivers properly as far as I can tell by allowing unsigned drivers on windows 10 but whenever I boot to flash mode the phone isn't detected. Nothing even comes up in Device Manager so there are no options to update drivers or anything. I just hold the volume down button, plug in the usb, the LED briefly flashes red before holding on green and then nothing happens. Neither Flashtool or PC Companion detect the phone and I have tried this on 2 different laptops running Windows 7 and Windows 10. If anyone has any instructions on how to get this to work on Ubuntu I'm willing to try that too as I also have Ubuntu installed but I am really at a loss for what else I can try.
Any help would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
civicsr2cool said:
sounds dumb but have you tried a different port and different cable? i ran into the same problem and found out one of the ports on my laptop doesnt work for data. flashtool is a major pain, it took me three pcs to find one that it worked with and then it took a good 5 tries and reboots to have a successful flash. flashing twrp and then xpower would be easier imo.
Click to expand...
Click to collapse
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
tokococo said:
Yeah, I have tried 7 ports and 3 cables across two different pcs. There's a desktop I can try on but I'll wait until tomorrow. It's really frustrating. I just wanted to root so that I could batch install my apps from Titanium but now I have got a brick. In the time that I have spent trying to fix it I could have selected and installed all the apps individually.
Click to expand...
Click to collapse
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
civicsr2cool said:
keep trying, it'll work after you figure out whats wrong with your install, flashtool is real finnicky. If your already soft bricked and only want root id suggest fastboot twrp 3.0.2 then flash xpower 3.0 and be done with it. the only real reason to use flashtool is to flash a new image onto the phone because you cant take an ota.
Click to expand...
Click to collapse
Thanks for your help. So I can do that without unlocking the boot loader?
tokococo said:
Thanks for your help. So I can do that without unlocking the boot loader?
Click to expand...
Click to collapse
bootloader has to be unlocked before doing any of this.
civicsr2cool said:
bootloader has to be unlocked before doing any of this.
Click to expand...
Click to collapse
Oh, you mean to do that once I have fixed my current issue.
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
RaunoT said:
Hmm, I seem to be having a smiliar issue, except instead of flashmode, mine isn't detected in fastboot mode, tried a crap load of drivers and usb ports etc..
EDIT: Got it fixed after following this guide
http://forum.xda-developers.com/z5-compact/general/unlock-bootloader-z5-compact-t3236237
Click to expand...
Click to collapse
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Just an update on what I have tried if anyone has any suggestions...
I tried inserting a SIM in case that would make any difference. I have also tried it on a desktop pc as well as the two laptops now which is windows 7, 8.1 and 10. The Windows 8.1 attempt was a clean install and I used the advanced boot method to enable the installation of unsigned drivers. I had high hopes for that but it didn't work. What I find curious is there is no activity when I plug the phone in, in flash mode. If I plug it in, in fastboot mode it searches for drivers and the device appears in device manager but with flash mode I get nothing. I'm beginning to think that perhaps the device itself has a faulty flash mode.
tokococo said:
I tried following that guide but when I try to install the driver it just says "The INF file you selected does not support this method if installation". You didn't happen to have that problem and find a workaround did you?
Click to expand...
Click to collapse
Sadly no :/
I managed to flash a Z5 Compact with the same model number without any issues on the same computer that won't detect my handset so I'm pretty sure that it's an issue specific to this handset. Thanks everyone for their suggestions.