hey guys!
so i wanted to root my moto g6 on my laptop and everything was going smoothly. i downloaded a new rom, TWRP and the adb. when i went to install the motorola drivers, the installer got stuck on stage 2 and then a small dialogue box appeared entitled motorola driver installer which stated "the parameter is incorrect". when i clicked OK. the dialogue box closed and another software with the name of motorola driver installer opened but that could not do anything. i ultimately exited it too. after i exited the driver the main software which was hung continued and after some time stated that the installation is complete. however whenever i search for fastboot devices mine does not show up.
i have searched the net for a solution even ran a chkdsk which was a total waste of my time. now i need help with this. can someone suggest another solution?
I also encountered this issue. Did you managed to fix it?
Related
I've had my NT for about a week and was able to sideload just about everything I wanted without doing a root. Then the dreaded 1.4.1 upgrade struck and I was unable to do anything more. I was able to revert back to 1.4.0, and do a factory reset to get everything working again. Then decided to take the plunge and use Indirect's root process. (yes, it was a big decision because I said I would avoid it if possible).
The problem is, I can't past the first step. I've enabled USB debugging and downloaded the files I need, but the NT will not show up in the device manager with the "!" symbol. I've read through all the threads and tried a number of different things, but the NookandZergy program will not identify the NT.
I think I'm stuck, if I stay where I am I will get hit with the OTA upgrade again, but I can't seem to work through the process to change it.
Any ideas?
Hello @Barry4405 read this: [FAQ] NT Tips & Tricks, How to's | NEWBIE? Having issues? - Please READ! the DRIVERS ISSUES section.
Veronica
Or, rather I should say, "What am I missing ??"
What you are experiencing is a drivers issue use the link i posted below, there you will find a link to a step by step guide to setup drivers and fix this problem.
Veronica
SUCCESS !!!
This forum is AMAZING. I double checked the link you suggested and found what I had missed. It took me about four attempts but I finally was able to get the driver to work, and everything worked great after that.
Thank you so much!
OK, thanks to my own ineptitude I am back to square one.
After installing the root I somehow messed up the launcher, couldn't get to ADW and had no web access. I figured the quickest fix would be to start over again. I did an install of 1.4.0 and wiped everything clean. I followed the instructions that I used before to get the ADB drivers working, and they will not work. Everytime I connect the NT it shows up as drives E and F and windows insists on installing the drivers, even though I have disabled the auto installation.
I've used USBDeview utility and checked and double checked the USB debugging, it still insists on installing drivers for it.
What am I missing???
OK, I think I solved it. Shortly after I sent the last message it occured to me, "I don't need to look for and install the drivers I need, they're already there from the last time." Sure enough, I connected the NT and ran Zerg and..Bazinga. I have a rooted NT again.
Hello guys,
Ive been lurking here for a while and i finally thought about joining the gang.
I cant find the LG E510 thread here so please move my thread if this place is inappropriate. Thank you.
I updated this E510 via the LG mobile support software and the install [after downloading firmware] got stuck at around 4% then at 14%
The software prompted me to remove the phone from connection, pull out the battery then try again. Now its stuck at boot screen.
I can start up the "Emergency Mode", where its the only way my PC can recognize the device connected. I tried using the LG software again but i get this:
Hard reset is said to be VolDown + Home + Power On yet it doesnt work, only gets to logo.
This is an unrooted phone that why i used LG-provided update software.
THe PC can detect the devices and installed drivers. The software can too, but this error is persistent.
A friend said something about disabling the LG modem in the device manager but i still get this error.
I have ADB which i used sometime ago with my HTC but the ADB says device not found.
Any help would be appreciated.
Thank you very much.
*** SOLVED
I dont know what exactly made it work but i did the following.
Disabled [not uninstall] all other devices installed by the phone except the LG Android Platform
- disable and restart. if uninstall is used windows will just install it again after restart. disable.
- may be a problem with my PC that it has difficulties connecting with the phone if the other child devices are on
Uninstalled the Update Software and Installed it again
This time i clicked Options > Update Recovery
- prompted for my Phone Model + SN or just the IMEI <- brainfart on my part shouldve seen this earlier
The software downloaded the exact same firmware V10H_00.kdz and installed it. Success!
Maybe there was something bad with the first one i downloaded being on WiMax connectivity.
I feel so stupid right now being unobservant and all...
Anyway thank you!
Hi,
First of all, excuse some error typing. My english is better reading than writing!
To go direct to the point, I, by mistake, erased BMM via app. Then I did a reboot and the problem occur.
The thing is: On this phone, I haven't BMM or Safestrap to do the kexec thing to load the ROM. I think with fastboot command and the right file I was able to resolve the problem. BUT, the phone in Windows is recognized as UNKNOWN DEVICE, and even on other pcs with Windows (which I installed the moto drivers to test too, either in x86 or x64) it still is not recognized. In Linux world I'm new (using Sabayon). I installed the fastboot and adb (its working), but I don't know how to install the proper driver for the razr to try in.
Today I found this thread http://forum.xda-developers.com/showthread.php?t=2047750 and after reading it and searching, I found this too: http://forum.xda-developers.com/showthread.php?t=2055839. I think this case is possible my situation too.
I just want a way to restore this phone. Preferably, if possible, just installing again the BMM in some way, or, at least, take it recognizable in windows to flash in RSD.
Did you solve your problem? Long time since I've been here, last time.
No! Since I was expecting to the support of the people here...
I being busy these days and don't have time to try to figure out how to solve this problem.
Thanks for your concern.
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Twink225 said:
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Click to expand...
Click to collapse
It's hard to understand all of that but it sounds like perhaps you deleted some bloat that you should have, you sound like having driver issues, and possibly wrong TWRP version. Need to clear that up and then reinstall the stock Disney ROM.
I'd start here it has all the tools/TWRP/ROM's you need.
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
So sorry hun, toshiba is driving me nuts and I'm having a bad add moment or three lol. I read about you retiring. so I tried hard not to bother you. now I'm really confused. I've read your nabi2 general info post and even ran across your youtube vids. the problem is I'm not familiar with adb. & the included NabiLabGUI drivers, win10 either fails to finish saying it was interrupted. or it just won't install the 32 bit drivers, I thought I as suppose to use.
The 64bit driver 3 out of 4 install but, I can not get the Google Inc, driver to install properly even with the inf file. (ie the android_winusb.inf ) it says the system can't find the file, it can install the older versions from NabiLabGUI or naked drivers. but doesn't show in add/remove and it still won't detect the tablet most of the time lol.
Pda also has conflicts with adb, I got the nablab disney option to detect it but still failed to install twrp saying it can't find devise and I noticed in device manager 2 driver problems that will not let me update manually or they go missing if I try to force windows to reinstall. (device descriptor request & set address failed)
I must be missing something big, I also tried the 15sec and minimal adb. I assume because the tablet won't fully boot up, windows doesn't know what to do with it. when I tried different cables. windows 10 enterprise won't play nice at all now. so I will format again to be safe but lost what to try next.
I guess my questions should be is there a work around or a full inf version of the newer drivers for NabiLabGUI2015 that might work with this demonic disney nabi2.
&
Is NabiLabGUI compatible with .net framework 4.6 advanced services? (I may have to downgrade o/s. on the nabhacks site is says .net 4.5 is a prerequisites.) I don't know much about the app but saw 4.6 comes preinstalled, I can't install 4.5 yet, I saw there has been compatibility issues. and it won't let you revert versions easily if at all.
I'm to tired of this tab to think straight anymore and so grateful any help I'm in way over my head here.
Update
I lost the battle but I won the war, now google & supersu are messing with me as usual but it boots so I win lol :victory::silly:
I bought a " Figo Atrium 5.5 ". The Figo website has instructions to flash the device to 6.0 Marshmallow instead of Lollipop. I believe these instructions are incomplete. Here is the link, I'll detail for you what I've tried using their recommended software SPFlash https://support.figoglobal.com/support/solutions/articles/16000047848-android-6-0-atrium-5-5
I downloaded and extracted both files on Windows 8 64 bit desktop, the SPFlash tool and the other the Atrium ROM itself. The very first instruction is installing the drivers which I do using the install.bat file from the "Driver_Auto_Installer_v1.352.00" folder. I believe my install fails at this point. Opening the Flash_Tool exe after installing the drivers (the tool does say they installed properly) I never get any information in the Chip Info in the Flash_Tool. It appears those drivers are not installed properly.
Researching this, I came across videos that suggest the drivers were not being installed properly because the drivers are Not digitally signed. I followed the instructions to fix the problem by booting to Advanced StartUp options then choosing to run the OS with digital signing checking disabled. Now on installing the drivers I get the popup asking me if I am sure I want to install the drivers I choose Install Anyway. The driver install tool just sits there for a couple of minutes doing nothing, then the popup message comes back asking again, am I sure I want to install the drivers. This is an endless loop, the application never attempts to install the drivers. The phone is plugged into the the PC at this point because I assume it must be for windows to see the phone. Note, at no time except the End of the instructions does it tell me to have the phone plugged in. This confuses me greatly. I don't know if the phone should be plugged into the pc at this point or not. Can someone who if used to doing these kinda flash jobs look over these instructions and help me figure out what I'm doing wrong. Thank you. I will do my best to answer back with more info, I'll be home all day watching this thread.
( btw, the forum on that site is moderated. I have tried over two weeks ago to post forum messages about my issues, but the moderators never posted any of my messages - it seems customer service is non existent)
Please mark this as Solved. I fixed my problem with a bit more research. Figo gives incomplete and also incorrect information on upgrading the Rom ( as you can see) Nowhere do they tell you in the instructions that you need USB Debugging Enabled or how to do it. This is a critical step or the drivers will never see the phone. The drivers did correctly install the first time as I suggested. That was the incomplete information. The incorrect information is this: They tell you to take the battery out to flash the device - which will never work because the phone needs power for the drivers to flash the device. What you have to do while the phone is On and Connected to PC is remove the battery then put it back in - then the phone will flash. This is critical step 2 they were wrong about. I suspect it has something to do with a bad Chinese translation.