I am having major issues getting adb to work for me. I have uninstalled, tried installing custom and even tried a couple scripts I found to get it to work. Everything I try and every tutorial on how to get adb to work with it isn't working for me. I am running win7 x64 which is where I think the problem is. Everytime I plug in the nook color it automatically installs the nook driver instead of the custom driver. I even turned off the automatic install of drivers. Any help on this would be amazing as I just got honeycomb to boot with no issues but can't get any gapps installed. Thanks in advance.
http://forum.xda-developers.com/showthread.php?t=1419505
I prefer the adbWireless app. Less work to set up.
wdenker said:
I am having major issues getting adb to work for me. I have uninstalled, tried installing custom and even tried a couple scripts I found to get it to work. Everything I try and every tutorial on how to get adb to work with it isn't working for me. I am running win7 x64 which is where I think the problem is. Everytime I plug in the nook color it automatically installs the nook driver instead of the custom driver. I even turned off the automatic install of drivers. Any help on this would be amazing as I just got honeycomb to boot with no issues but can't get any gapps installed. Thanks in advance.
Click to expand...
Click to collapse
Good luck getting ANYTHING to work on honeycomb. It is not even close complete and never will be.
Sent from space
Related
did a clean install of KnoxRaid 4.0
eveything is working smoothly i love it!!
however i am getting an issue with viper4android.
i am able to install via apk, then grant SU permission. I even get to finish installing the super quality drivers then reboot.
but it doesnt seem to save. after reboot and then going back to viper4android it still asks to install driver.
can anyone help?
thank you
whoohaaah said:
did a clean install of KnoxRaid 4.0
eveything is working smoothly i love it!!
however i am getting an issue with viper4android.
i am able to install via apk, then grant SU permission. I even get to finish installing the super quality drivers then reboot.
but it doesnt seem to save. after reboot and then going back to viper4android it still asks to install driver.
can anyone help?
thank you
Click to expand...
Click to collapse
I had that problem when I owned my S3. I simply installed an older version. I had to also install busybox, but it was worth it.
Hope this helps.
Coming from where the wind begins.....
Kamau54 said:
I had that problem when I owned my S3. I simply installed an older version. I had to also install busybox, but it was worth it.
Hope this helps.
Coming from where the wind begins.....
Click to expand...
Click to collapse
thank you but unfortunately that didnt work.
i tried reinstalling supersu and busybox, reboot, then tried installing the update viper4android and 2 older versions. No Dice..
Hi, first time poster although I've been lurking around xda for years. Anyway I rooted my htc one and generally it works well. I have encountered a few problems though and would be extremely greatful for any assistance. Googling hasn't given me any proper solutions yet. So here we go
1. After rooting I no longer have access to MTP so I can't transfer files
2. Busybox does not seem to want to install. It either resets my phone or says it hasn't been installed
3. I tried to uninstall the drivers for my phone but when I do my device manager becomes non responsive
Ultimakaiser said:
Hi, first time poster although I've been lurking around xda for years. Anyway I rooted my htc one and generally it works well. I have encountered a few problems though and would be extremely greatful for any assistance. Googling hasn't given me any proper solutions yet. So here we go
1. After rooting I no longer have access to MTP so I can't transfer files
2. Busybox does not seem to want to install. It either resets my phone or says it hasn't been installed
3. I tried to uninstall the drivers for my phone but when I do my device manager becomes non responsive
Click to expand...
Click to collapse
meh got it fixed and not sure how to delete this
My brother has an LG G2 (verizon), I rooted his phone for him because he's not much of an android enthusiast himself. He wanted to get rid of some bloatware on stock rom so he downloaded a root unintaller, and in the process of it, he uninstalled something he wasn't supposed to. I don't know exactly what process/apk it was, but it was a system file. Now almost every system app force closes, (phone,mms,contacts,settings). I tried a factory reset, and the problem remains. He is still rooted, and I know the best workaround would be to flash a new rom (custom or stock, i dont really care), but that's where the problem comes in. I am trying to install this:http://forum.xda-developers.com/showthread.php?t=2715496 AutoRec to get a custom recovery, so I can flash a new rom, but because settings instantly force close, I cant enable to install from unknown sources. I tried to adb push the apk, but after about an hour of trying, adb doesn't recognize the device. I tried both a wired, and wireless adb attempt (idk if its even possible to adb push an apk via wireless, but I tried, and it says my device is unauthorized, so didn't work. Is there any workaround to my problem? I downloaded an app that enables usb debugging, but adb still doesn't recognize, even after i installed the driver. Been at this for hours with no luck, would be great if one of you knew a way to fix this dilemma.
FuzionRain said:
My brother has an LG G2 (verizon), I rooted his phone for him because he's not much of an android enthusiast himself. He wanted to get rid of some bloatware on stock rom so he downloaded a root unintaller, and in the process of it, he uninstalled something he wasn't supposed to. I don't know exactly what process/apk it was, but it was a system file. Now almost every system app force closes, (phone,mms,contacts,settings). I tried a factory reset, and the problem remains. He is still rooted, and I know the best workaround would be to flash a new rom (custom or stock, i dont really care), but that's where the problem comes in. I am trying to install this:http://forum.xda-developers.com/showthread.php?t=2715496 AutoRec to get a custom recovery, so I can flash a new rom, but because settings instantly force close, I cant enable to install from unknown sources. I tried to adb push the apk, but after about an hour of trying, adb doesn't recognize the device. I tried both a wired, and wireless adb attempt (idk if its even possible to adb push an apk via wireless, but I tried, and it says my device is unauthorized, so didn't work. Is there any workaround to my problem? I downloaded an app that enables usb debugging, but adb still doesn't recognize, even after i installed the driver. Been at this for hours with no luck, would be great if one of you knew a way to fix this dilemma.
Click to expand...
Click to collapse
Just return it to stock using the guide on the main page. You can disable apps via App Manager without having root. If he does root it again, tell him to rename files to .bak instead of deleting them...
I successfully installed Android M, and things were mostly okay. Titanium Backup won't load. It force closes, and having a problem with Dolphin Browser flashing a handful of times and then erroring out...unable to use. Other than that, everything seemed to be working perfectly. However, I needed to be able to restore my app settings, and I know Titanium Backup needs root. So, I thought maybe that's why it was force closing. So, I decided the easiest way to root would probably be using the Nexus Toolkit. I used that, which seemed to go normally, but the phone won't boot now. It just goes black. ADB seems to be able to communicate with it in this black screen state (via Nexus Toolkit, for example), but I can't get anywhere. I tried re-flashing the boot and bootloader, but it didn't help. I am seeking the wisdom of the elders.
YOu are going to have to start all over. SO factory reset. to clear out everything and get a fresh M load.
The toolkit is for Android L. So it overwrote things that Android M needed.
Once you have a fresh install. Go here http://www.androidauthority.com/android-m-root-613760/ and root.
all you need to do os flash a m kernel(despair kernel) and the latest SuperSU, and youll have root. flashing the latest supersu with a m kernel will not work.
Thank you for the feedback. I am mostly in business. I can't get BusyBox to install, though. The app runs fine, but actually installing it from within the app does not work...says it was not successful. I have tried the other location, which didn't work also. Any thoughts? Thanks much; greatly appreciate the assist.
mystik1 said:
Thank you for the feedback. I am mostly in business. I can't get BusyBox to install, though. The app runs fine, but actually installing it from within the app does not work...says it was not successful. I have tried the other location, which didn't work also. Any thoughts? Thanks much; greatly appreciate the assist.
Click to expand...
Click to collapse
I'll do some more research and get back to you on this one. Not exactly sure how busybox is running on the new file structure.
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Kov8 said:
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Click to expand...
Click to collapse
Hi Kov8.
I was running CM 11.1 for ovation and experienced the same thing. My solution was to install a newer version.
To save your data, set up an SD card (be sure you have enough extra room for your data) with the TWRP 3.0.1-0 version here:
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
Load TWRP and look for the File Manager. I think it's under "Advanced." You can use that to copy or move your data to the SD card.
After that, consider upgrading to AOSP or LNOS. I can install AOSP without much difficulty, but LNOS doesn't go well. More on that in a later post.
If you need more detailed information, look at this post and download the pdf at the end of the first post:
https://forum.xda-developers.com/nook-hd/general/install-cyanogenmod-12-1-barnes-noble-t3211119
Kov8 said:
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Click to expand...
Click to collapse
Yes. I've been reading that all the recent ROMs do that.
The solution is to do a standard shutdown followed by a hard shutdown (by holding the power button for 8 seconds).
I suspect that going straight for the hard shutdown caused some file system errors that made installing new ROMs very difficult.
I'm OK now, though.
Thanks for the detailed reply! I will try.
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Kov8 said:
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Click to expand...
Click to collapse
That's funny. I just downloaded two copies from that link.
For version 3.2.1-0, it sounds like you're looking at the version from the team win website. I haven't tested that one thoroughly, but I have tried out their version 3.1.1-0. It works pretty well. It gave me some minor error messages here and there, but if I just repeated what resulted in the error, it generally went through on the second attempt without an error.
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Kov8 said:
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Click to expand...
Click to collapse
Mind telling how you managed to update twrp from 3.0 1 to the latest? I successfully installed 3.0.1 to my nook hd+, then flashed 3.2.1 img to recovery, now the device stuck at boot.
I simply downloaded to img file from their website (for ovation, my device), placed on the micro-sd, and installed it from TWRP itself. As simple as that.
Are you sure that you got the correct version for your device?
I also always verify the integrity of roms after writing them to a card. I've seen bad cards.