Database Develop

[Q] please help with nook color

I just recently hacked my nook color using the auto-nooker v 1.1.0
everything went smoothly and i had my device running fine. i wasn't able to log-in to my gmail account because everytime i was typing it kept changing my letters or adding new ones (this was incredibly frustrating) so i ended up skipping that step.
I powered my nook off after doing some exploring, hoping that we it re-started i would be able to log into my gmail account easier.
when I tried to power my device on it wouldnt start... i plugged it into my computer and it powered up to the "n" logo and adope information and then turns blank.
i have tried to un-plug, re-start my computer, take micro sd card in and out but nothing..
as of right now my nook color isn't working at all, if anyone has any suggestions on how to help me, please do.

Hey pinkll,
The first post in this section discusses fixing your problem:
http://forum.xda-developers.com/showthread.php?t=949699
The following is some advice on using Win Image 32, which is required in above link. This can be confusing.
A) Download the following software to your PC/MAC for formatting your XD card. This is the best one that I have found.
SD Formatter 3.0 for SD/SDHC/SDXC:
- Format your XD card. This step is very important to correctly write the EXT4 compatible bootable SD recovery.
B) You will need “Image Writer for Windows”
- I found that the “0.1 (truckstop) release” worked the best. The newer version seemed to always have some problem.
- Paste the unzipped folder to you C:\ directory. Put the EXT4 compatible bootable SD recovery file in the same folder. This will help prevent issues. This software is originally intended for a Linux environment and thank you to the developer for making it compatible with Windows.
- Make sure that the chosen device is your XD card. It automatically selects the correct one, but you never know. Go to “my computer” in windows and check to see what Letter has been assigned.
- Choose the EXT4 compatible bootable SD recovery file from Image writer directory.
- Click the “write” button. This will take a few minutes to finish.
- Now you can copy misc files to the flash drive. It is ready to boot your Nook into Clockwork Mod Recovery.
They don't trust me yet on this site, so I cannot post links to other sites. The required links are in my original post: http://forum.xda-developers.com/showthread.php?t=997764
Let me know it this helps.
SUBCAN

thanks for the response
i didn't remove that card before i re-started. i was unaware of this until a while after i crashed.
-i found a solution though. i wiped my device and started all over. it's now working great
thanks for much for the reply!!

[Guide] Absolute Newbie's Guide to Rooting a Streak 7 that has Stock Honeycomb

Obviously this guide owes a huge bunch of thanks to "TheManii", "Giveen" and other folks who can't be named on this forum. I have tested this on both a Streak 7 WiFi and a Streak 7 4G. In both cases they had the Stock Honeycomb already on them. So if you are coming from some other version of Android you may wish to reconsider
1) Download the Fastboot+ADB.zip file for Clockwork Mod 5.0.2.7 from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
2) Download the Clockwork mod 5.0.2.7 file from the XDA Developers thread (http://forum.xda-developers.com/showthread.php?t=1334487)
3) Go into Settings->Applications and turn on "Run Applications from Unknown Sources"
4) Go to Development Settings and select "USB Debugging"
5) Unpack the Fastboot+ADB file into a directory on your computer where you can find it again
6) Attach the Streak to your PC, and copy the "Drivers.zip" file from the root directory of the Streak (/sdcard) to the same directory where you unpacked the Fastboot file
7) Turn off your Streak after you have copied this file, and disconnect it from the PC
8) Unpack the drivers.zip file and find the "Setup.MSI" file. Execute this file to install the drivers you will need
9) Put your Streak into Fastboot mode - i.e. turn it off, then turn it on by pressing the Power button while holding the Vol DOWN (-) at the same time. This can take up to 20 seconds
10) You will get some red text followed by a white line saying something about Fastboot USB downloading is active
11) Connect the streak to the PC now, and it should install an Android ADB driver. Depending on what you have already setup you may get some drivers installed successfully, and some not. In general if you've been following this guide, you'll be ok
12) Open a command line for the folder where you have fastboot and your recovery image (ClockWorkMod) - in windows navigate to the folder, and hold the shift key while right clicking
13) On the command line type the following:
fastboot -i 0x413C flash recovery recovery.img (where recovery.img is the ClockworkMod or other recovery file)
14) On the command line type the following:
fastboot -i 0x413C reboot
15) Your device should now reboot
16) To get it to reboot into CWM, turn the Streak off, and then turn it on again while holding the Power Button and Volume UP (+) at the same time. This may take up to 30 seconds
From here you would follow the normal CWM options to install just the root files (Superuser7 for one example) or install a custom ROM.

It turns out steps 9 - 15 are also a great way to fix the problem when your Streak comes up and starts asking for a Password when you never setup a password. For some reason installing one of the custom ROMS also installs a version of CWM that is not as recent as the 5 series, which can lead to issues with the signature verification (i.e. when things go "boom", Android sees the partition as encrypted rather than just "locked"). So steps 9 - 15 allow you to put in a later CWM which does a proper wipe, and you're back in business. Have to reinstall apps, but the data is left alone.
Just in case I'm not the only one who has run into this

Ok, I used this guide to modify my Dell Streak 7 wifi. After I was done my screen kept flickering and I put it back to stock thanks to AndroidOVERALL putting together a post on how to complete the restore.
I have searched about the screen flickering but didn't find a resolution. Maybe I missed it, but it seemed that others had the same issue and it was either a hardware problem, the brightness was adjusted, or auto rotate was disabled. I tried adjusting the brightness settings and many other settings but the issue was not resolved until I returned everything to stock.
I have a Dell streak 7 wifi, US version with Honeycomb.
Please point me in the right direction if this issue has been resolved and I missed it. If not any suggestions?

Did you load a custom ROM after following these steps, or did you just reboot aft getting CWM installed. Usually the flickering comes from an issue with the video driver (so can be software if a bad driver, or hardware if it's only marginally in spec).

For any one who gets to the end of the steps and now can boot in go CWM but doesn't know what to do about getting rooted.
Very very Simple.
Download Superuser7.zip
http://www.tablet-cables.com/streak/tools/root/Superuser7.zip
Have your Streak booted normally and USB cable hooked up.
Move to the internal Memory Superuser7.zip
power off device
Power back on using Vol UP & Power Button
Select 2. Software upgrade via update.pkg on SD card and press power
CWM will load.
Select install zip from sd card and power to enter.
select Choose zip from internal sd card and power.
use Vol UP to go backwards to your files and select Superuser7.zip and hit power
move down to YES - Install Superuser7.zip and hit power
thats it. its rooted.
goto ++++++++ Go Back+++++++
and reboot system now
and let it reboot.
Not necessary, but I'd suggest running Superuser and hitting the Knob icon top right (settings) and scrolling down and updating Super User.
Hope this helps someone who may not know where to get Superuser7 and what to do after following the great guide above.

thanks!
nothing sucks worse than a bad download -- happend TWICE! (dayum!)
got rewt?

Help?
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?

blastedmax said:
I am trying to Flash superuser.zip after installing the clockwork.
But I keep getting the following screen. I do not have exterior sd card installed.
What can I do?
Click to expand...
Click to collapse
It's saying that it is looking for an SD Card and not finding it, so that certainly makes sense. However, it sounds like it is looking for "update.pkg" rather than "superuser.zip", so is it possible you accidentally selected the "Update" option in CWM rather than the option to select a file?

He doesnt have clockwork mod installed, you must have CWM installed to flash zips

OK, I have a new Streak 7 t-mobile with HC 3.2. I plug it to the pc running xp sp3, and it needs drivers for MTP and Streak7. I pointed to the Fastboot+ADB folder I extracted for the Streak7 driver and it installed Android ADB Interface. Pointing there for MTP fails to find a driver. I can't get to the internal SD to get the drivers.zip because my computer won't recognize the Streak until the MTP driver is installed. After installing an MTP driver from the net, I can see the internal and external SD. I copied everything to a single folder labelled STREAK in c:\ and unplug the Streak from the pc. I put the Streak into fastboot mode (Volume - & Power), wait about 10 seconds, then plug it into the usb port. The computer see the Fastboot device and needs a driver. I point it to the STREAK folder (former Fastboot+ADB) but it didn't find a driver it liked. I tried to install manually, but there is no Android 1.0 or Android ABD Interface devices in my list. I do see Android USB Devices, but it is empty when I click on it. ANYBODY else get this, and how do I move forward? I followed the guide to the letter, and appreciate all the work & effort you guys put into making these root methods available. The Streak7 is a cool little device, but I think it will be cooler once I root it. I have rooted my Epic 4g and the wife's Evo 4g on this same computer, and I do have the Android SDK installed (even though I don't know how to use it).
OK, so I used all the same files I have here and was able to successfully get Clockwork flashed & gain root. I dunno why the xp machines don't like these files. I tried 3 other xp laptops before getting to my wife's Windows 7 laptop, which worked just as described in the very well-written guides. #MindBottling!

I cannot even find the drivers.zip in step6. WIN7x64 and a brand new tmobile streak 7. where is this thing? I looked through all the folders and subfolders.

Drivers.zip is in the main directory of the Streak. Open up ES File Manager or a similar program and you should see it. To get it to your PC, attach the Streak via USB and let it mount as external storage (default behavior I believe).

In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Since this should be a common file for all SD7 units, can someone please email that file to me so i can get past step 6. [email protected]

cidand1 said:
In my main directory on on my streak, using ES file explorer, i cant seem to find that file. I see acct, cache, config, d, ....etc folders, i scroll down, i see default.prop, init, init_recovery.rc, ...... var files, but i dont see drivers.zip. help I need to get honeycomb so I can use skype front facing camera, cause I understand froyo 2.2 can only use the back camera w skype.
Click to expand...
Click to collapse
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
That said, I also can't guarantee this process will work for someone starting with Froyo. I do know there may be an issue with which version of CWM you can use in that case. As such, you may want to check one of the other guides to be sure.

EwanG said:
From this I gather your Streak did not ship with Honeycomb. That would explain why you didn't find the file as that is something that I gather Dell added when they changed how they shipped it later on. I am not sure what the redistribution rules are for the file, which is why I haven't posted it myself.
Click to expand...
Click to collapse
Explain please? Shouldn't drivers be present no matter how it's shipped? Mine came with Froyo with drivers, I OTA'd to HC and I still have them.

Ya I bought this from dell directly about 3 weeks ago. From what I have been reading on XDA, mine is definitely different. Its a tmobile streak 7.
Android 2.2.2
Kernel : 2.6.32.9
OEM ver: GLUNB1A133633
Build : 15420
Another thing I noticed is that even trying to load CWmod through fastboot, my computer does not recognize the DS7 in fastboot mode. The drivers in the fastboot+ADB zip file dont work on my computer as fastboot drivers (or maybe I should try another CPU). My cpu is an AMD 64; running win7 pro 64; i need some serious help.

I think I bricked!
Ok I followed the directions from here to root my tablet.
http://www.cesgeekbook.com/2011/12/root-dell-streak-7-with-honeycomb-32.html
All went well! Everything worked and I was rooted! did the Superuser7. Clockwork came up and installed. All went right! So I was pleased. I figured I would later than put on a ROM cause it was late. Well was going to do so and tried to go into clockwork via ROM manager. Didn't work! Kept rebooting! So I figured I would try the pother way "Press Power and +" then click to Install from SD Card to go into Clockwork. That didn't work either! Then Now it won't reboot at all! I can get into fastboot and I can get into the bootloader. But that's it! I tried to do a Factory Reset and nothing! it just stays on the Dell boot screen. Anyway to fix the problem? If so, please give me step by step directions on how to do it.

Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.

EwanG said:
Use of ROM Manager is generally discouraged due to unknowns about how the package will work with other ROMs. It also isn't clear to me which version of CWM you were using.
If you can get into fastboot, then you should still be able to use ADB, and I would suggest trying to reinstall CWM as indicated in the first message of this thread. That way at least you should be at a known good spot for us to try and help you get a custom ROM installed.
Click to expand...
Click to collapse
Didn't know about the Rom Manager issue. I guess it's only good to use on cell phones? Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers. But since it's not reading the tablet. I can not reinstall CWM. The version I installed was the one from the 1st page. It's a fairly simple thing to do. But just need to get the device to be read by my laptop.
I have contacted Dell and explained to them the problem. They did say that I can return it to get it fixed. but still kind of hoping I can do it from home.

Marvelous0ne said:
Anyway, I am trying again, but the problem is my laptop is now not reading the tablet when in fastboot mode. I have followed all the step again. Including reinstalling the drivers.
Click to expand...
Click to collapse
Not sure what you mean when you say the laptop is not reading the tablet in fastboot mode. When in fastboot it should NOT show up as attached storage. The best way to tell if it is "really" seeing the Streak 7 is in step 13 - which uses an id rather than a device name so that it should work even if the tablet isn't fully identified. If you try to perform step 13 while in fastboot, what message are you getting?

UMS Mode for ExternalSD Card Jelly Bean Support

here simple application that will enabled UMS mode for External sdcard
root needed.
how to use:
safe way on version 2.5 is :
enable UMS Mode when cable usb is unplug
Back to Charge mode when cable usb is unplug
safe way on version 3.0 is :
do it on condition usb plugged
note:
if you plug into player or some device player , and you found that it cannot found the USB drive
in this case just do this
settings -> connectivity -> usb connection type
and do press or repress the "Charge Only"
in version 3.0 you will notice 1 triangle on task bar, its normal , it telling you mass storage is currently unmount
2 icon on task bar is telling you the mass storage successful unmount you can take it out
those of notice are normal if we do unmount the mass storage in android api level.
all the information about how to do it i found on XDA forum.
i do some research also code this app
version 2.1
fix sometime fail to mount back to external_sd folder
version 2.5
fix sometime got to bluescreen on windows
version 3.0
fix bluescreen on windows
using different approach to unmount the external SD card
version 3.2
bring back native method to mount and unmount, its speed up abit when using native method
by check the box to enable native mode
version 3.3
support Jelly Bean
thanks are goes to XDA Members
UMS_mode.apk
UMS_MODEv2.1.apk
UMS_Modev2.5.apk
UMS_ModeV3.0.apk
UMS_ModeV3.2.apk
UMS_ModeV3.3.apk

its working good tnx mate

Thanks for app. It is amazing
Best regards,

It does not mount back SDcard to /mnt/sdcard/external_sd after disconnect, so have to reboot after use it.
MTP is working but external_sd is empty.

your welcome guys,
@m0b :
i think you forget click on "back to charge mode"

bullghost said:
your welcome guys,
@m0b :
i think you forget click on "back to charge mode"
Click to expand...
Click to collapse
No, i try it, but it does not help, only reboot.

m0b said:
No, i try it, but it does not help, only reboot.
Click to expand...
Click to collapse
try the version 2.1,
i fix it

bullghost said:
try the version 2.1,
i fix it
Click to expand...
Click to collapse
now ist fine for me, tnx!

m0b said:
It does not mount back SDcard to /mnt/sdcard/external_sd after disconnect, so have to reboot after use it.
Click to expand...
Click to collapse
With the first version I have access to the card. After disconnecting I have to reboot the phone, so I can regain access to the card.
bullghost said:
try the version 2.1, i fix it
Click to expand...
Click to collapse
Version 2.1 gives reproducible blue screens with Win7 x64 SP1 at the first link when I confirm the superuser, or in further tries, when connect the USB cable.
Only uninstalling the apk helps to solve the problem.

A little off topic:
After UMS_mode.apk does not work for me, here is another way to access both memory cards in the P880 (and any other Android-Device) from Windows OS:
Install Total Commander (Shareware): http://www.ghisler.com
Install Total Commander Plugin "Android ADB" (Freeware): http://www.totalcmd.net/plugring/android_adb.html
Android device driver has to be installed too!
Through links, both SD-Cards appear with 3 differen pathes in the P880 operating system.
The external SD-Card has its mount point in (!) the internal SD-card:
Code:
Internal SD-Card:
\\\ADB\LG-P880\data\media\
\\\ADB\LG-P880\mnt\sdcard\
\\\ADB\LG-P880\sdcard\
2. external SD-Card:
\\\ADB\LG-P880\data\media\external_sd\
\\\ADB\LG-P880\mnt\sdcard\external_sd\
\\\ADB\LG-P880\sdcard\external_sd\

Bud Cord said:
A little off topic:
After UMS_mode.apk does not work for me, here is another way to access both memory cards in the P880 (and any other Android-Device) from Windows OS:
Install Total Commander (Shareware): http://www.ghisler.com
Install Total Commander Plugin "Android ADB" (Freeware): http://www.totalcmd.net/plugring/android_adb.html
Android device driver has to be installed too!
Through links, both SD-Cards appear with 3 differen pathes in the P880 operating system.
The external SD-Card has its mount point in (!) the internal SD-card:
Code:
Internal SD-Card:
\\\ADB\LG-P880\data\media\
\\\ADB\LG-P880\mnt\sdcard\
\\\ADB\LG-P880\sdcard\
2. external SD-Card:
\\\ADB\LG-P880\data\media\external_sd\
\\\ADB\LG-P880\mnt\sdcard\external_sd\
\\\ADB\LG-P880\sdcard\external_sd\
Click to expand...
Click to collapse
thanks bro , here version 2.5 will fix the bluescreen

Thanks a lot! useful for syncing with doubleTwist. can't stand the LG PC Suite its too slow.
Sent from my LG-P880 using xda premium

version 3.0 relase fix bluescreen again,
if you suffer on always media scanning you can turn it off on
setting -> application -> find "Media Storage" -> disable

Wow!
This is the greatest thing created for this phone so far.
MTP is painfully slow, doesn't work with cars/stereos/etc, requires installing drivers everywhere I go, crashes all the time, doesn't allow access with a file path, and somehow caused my sd card to wipe itself three times in two weeks, so this was a major issue for me that was making me regret buying the phone.
Initially after installing this app (v3.0), I had to repeatedly toggle UMS/MTP mode and plug/unplug my phone from the computer several times before it finally started working, but now it's perfect.
If you have a paypal or flattr link, and I'll send something your way. Or put it on the Play Store so I can buy it and update
Thanks!

thanks
ben! said:
This is the greatest thing created for this phone so far.
MTP is painfully slow, doesn't work with cars/stereos/etc, requires installing drivers everywhere I go, crashes all the time, doesn't allow access with a file path, and somehow caused my sd card to wipe itself three times in two weeks, so this was a major issue for me that was making me regret buying the phone.
Initially after installing this app (v3.0), I had to repeatedly toggle UMS/MTP mode and plug/unplug my phone from the computer several times before it finally started working, but now it's perfect.
If you have a paypal or flattr link, and I'll send something your way. Or put it on the Play Store so I can buy it and update
Thanks!
Click to expand...
Click to collapse
thank you , as far as you like it , is enough for me

ben! said:
This is the greatest thing created for this phone so far.
Click to expand...
Click to collapse
I can not confirm unfortunately.
I wanted to give the app still a second chance and have installed 3.0.
Then I restarted the phone, without starting the APP before.
Now it hangs on startup LG boot logo.
Even without the second SD card the same problem.
Any idea without factory reset or flashing KDZ?

My phone is still stuck in boot, but I have an access via adb shell to system.
Unfortunately I have no permission to access "/data"
Could anyone tell me the aplication name of this UMS-Tool under "/data/data" ?
I only found "com.noshufou.android.su" in classes.dex, but don't know wether this is right:
Code:
[email protected]:/data $ run-as com.noshufou.android.su
run-as com.noshufou.android.su
run-as: Package 'com.noshufou.android.su' is unknown
[email protected]:/data $

Ok, I guess it's not quite working perfectly for me now that I've used it a bit more, but I still love it.
1) it's really tricky to get it working initially. I almost always have to toggle it multiple times and sometimes reconnect the usb cable.
2) like someone else mentioned, it never remounts the SD card so I have to restart the phone to get it working again after I'm done.
I have not had any problems on boot like BudCord.
I'm running stock firmware 10f.

Anyone have v3 hosted any where else? I can't download from media fire.. no captcha support..
Tried stock browser, dolphin, and chrome..

Any chance to get it working on mac os x (10.6.8) ?
For the moment it is the only default i found with this phone : the lack of "connections" with Apple's OS :/
PS : I searched on the web and I found a solution for Mac OS X users : Android File Transfer (on the official website).
Sorry I can not the url because I am new on this forum.

Unable to mount Touchpad USB to PC after installing Android 4.4.4

I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.

1sharpguy said:
I am unable to mount the USB to my PC using after installing Android 4.4.4 on my Touchpad. Was able to do so with WebOS. How can I connect my Touchpad using a usb cable to my PC? PC is a Gateway Notebook running Windows 7 Starter version.
Click to expand...
Click to collapse
Which rom and build of Android 4.4.4 are you currently using?
Try this:
Plug the tablet into the PC with the USB cable. Go to settings/storage/ click the 3 dots in the upper right/USB computer connection.
Switch from Media device to Camera, see if windows detects and installs drivers. Then set it back to media device.

Still no luck with mounting Touchpad
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay

1sharpguy said:
Hello Roland...
Thank you for your help and informative response. I am still unable to mount my device (Touchpad) to my PC (Windows 7). I have described below what I have tried to do so far.
Which rom and build of Android 4.4.4 are you currently using?
I used the downloads from [ROM GUIDE] How to Install Android 7.x.x Nougat builds on the HP TouchPad
734 posts
Thanks: 1,157
By RolandDeschain79, Recognized Contributor on 3rd December 2016, 06:30 PM
Download Android 4.4.4 Kitkat install files(Rom, Gapps, Recovery):
Rom:cm-11-20161219-NIGHTLY-MLQ-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
After switching from Media Device (MTP) to Camera (PTP), Windows was able to detect my device (TouchPad) and install the drivers. Despite the information displayed in Android Settings for USB Connections (Camera (PTP) lets you transfer photos using software, and transfer any files computers don't support MTP), I was only able to transfer photos/pictures. When I switched back to Media Device (MTP) file transfer, Windows could not detect my device. Instead, when I looked in device manager, Windows sees my device as a Samsung Android phone (which I have) and not a Touchpad.
I have attached a screen shot of the driver files in the submenu Android Composite ADB Interface. I even ran and update. All files were current with latest updates. Thus, for some reason Windows is seeing my Touchpad as a Samsung Android phone and not a Touchpad.
Any suggestions? I am unable to transfer backed up files or upgrade to Naugot 7.1 without being able to mount device.
Thanks! Jay
Click to expand...
Click to collapse
Hi have you tried rebooting both the tablet and the PC, sometimes thats necessary. You might also try running the universal novacom installer again now that the tablet is detected here. I tested plugging in the tablet with the rom you're currently using on a virgin windows 10 setup and it worked fine, unfortunately I don't have a windows 7 system to test.
If nothing works you can always transfer the backed up files over the WiFi with a free app WiFi file transfer here
That should take care of your files if you're looking to upgrade with Nougat.
Hope this helps :fingers-crossed:

Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J

1sharpguy said:
Yes...tried running Universal Novacom Installer a couple of different times without success (unable to USB mount Touchpad). Device Manager on PC allows me to uninstall Android Composite ADB Interface. Was thinking I might try that and see if I can get Windows to USB mount Touchpad and then search for compatible drivers. If that doesn't work, will try using Wifi Transfer as you suggest. Hopefully, that will get the Nougat files and backed up files transferred over to Touchpad.
Thank you for your help. Will post again when I know something more.
J
Click to expand...
Click to collapse
No problem, I've got one more thing for you to try. Found this in an older post of mine from 2012, back when I was using windows 7. Give it a try, you can always use the WiFi transfer app but it might take a while to complete. Good luck:good:
Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.
1. Go into Device manager. You will see "MTP USB Device" under portable devices.
2. Right Click it and select update driver software
3. Select Browse my computer for driver software
4. Select Let me pick from a list of device drivers on my computer
5. Select USB Mass Storage Device then click next

Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?

Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.

1sharpguy said:
Finally!! I was able to get Windows to install the MTP drivers using the method you proposed in your last reply. Took a bit of monkeying around with. Not exactly sure what I did, but it worked. Was able to transfer backed up files and Nougat files to Touchpad. Soooo...went through steps install Nougat. Everything seem to load fine. However, got an error message at boot for Evervolv and am unable to load Nougat. Error message is as follows...
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
I presume what it means by press SELECT to continue is to press the home key. When I do so, it takes me into the boot menu moboot 0.3.8
boot TWRP
boot webOS
boot Evervolv
boot webOS Recovery
reboot
shutdown
When I try to boot again in Evervolv, I get the same error message over again.
What do you think?
Click to expand...
Click to collapse
I'ts probably just a corrupt download, I've read this complaint before. Redownload the Nougat files and reinstall the recovery, rom and gapps.
1sharpguy said:
Oh yeah (full disclosure)...one more thing. In step 10 of your Rom Guide it says "-Select the System partition and swipe to wipe." I did this, but repeated it four different times because I didn't realize I had to touch the little home icon at the bottom of the page to return to the install button on the main menu. Not sure whether it would have had any effect on the install, but the error was a invalid size of uImage so wondering if by swiping to wipe the system partition so many times that I messed something up. That was the only thing I did that was different from your video and Rom Guide.
Click to expand...
Click to collapse
Wiping a blank partition won't hurt the tablet, its just a bad download. Right under swipe to wipe its says go back to main menu... I could add click the home button to return to the main menu, if you think that would help. This is why I have both a video and a written guide, I'd recommend using both resources simultaneously.
Edit: I double checked the video and I tell you to press the home button and return to the main menu here
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-go back to the main menu and select Install, locate the download folder on the left menu
-select and install the 7.1 Rom and the Gapps package then reboot.
Note: The first boot to android 7.1 can take sometime, Wait for it...

That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!

1sharpguy said:
That was it. Corrupt download. After downloading Nougat again and reinstalling, eventually Android 7.1 booted and is now loaded. Yeeees!!! The bad news is that Nougat on my device is very unstable and sloooow. I was more impressed with Android KitKat. If something doesn't change with 7.1, I will probably revert back to KitKat. After having gone through this exercise, I feel more empowered (confident) to make such changes. Although frustrating at times, succeeding in switching out WebOS for Android was a great learning experience and a big deal for me (I never do these kind of things). For someone with virtually no skills or experience in this kind of thing, it was well worth it to give it a go. I just hated the thought of seeing this TouchPad turn into a boat anchor. Couldn't have done it without you Roland. Your video and instructions (along with followup support to the forum) was invaluable. Although I am feeling nostalgic for WebOS (I really liked that operating system. Wish it had made it.), it has been fun to breath new life into these HP TouchPads with Android.
I'm sorry you seemed to misunderstand my point from my previous thread about repeatedly wiping the system files. I was not being critical of your video or instructions, but rather trying to give as much information to you and the forum to try and understand why I was unable to get Nougat to boot. You have done a great job with conveying the steps for loading Android on TouchPads. You deserve a huge :good: for your trouble. Thanks again for all your input and helping me get her sorted out. Good on ya mate!!
Click to expand...
Click to collapse
Congratulations are in order for getting this all done, i'm happy to hear the experience has empowered you with confidence and knowledge. I appreciate the feedback, my guide is aimed at users with little to no experience who just want to keep their HP TouchPad going.
No apology needed I just take my guides seriously and i'm always looking to improve them or fix mistakes. You'll see below I've added portions of this conversations to my troubleshooting section to help other users here. I'm just glad I didn't mess up that step in the video cause you can't fix those, a forum post is much easier to edit.
Nougat is still being worked on but as with any new version of android there will be bugs. Shumashs has an overclocked kernel that can boost the performance of the Evervolv nougat rom. However I highly recommend CM11 for users just looking for a stable and reliable setup. I'm happy we could save your tablet, enjoy it and check back sometime to see how Nougat is coming along.
Edits from my install guide:
Help I get this Error message after installing the Evervolv Nougat rom
Selected: 'boot Evervolv'
Loading '/boot/uImage.Evervolv'...Ok
Checking uImage...Invalid size
BOOT FAILED!
Press SELECT to continue
Solution
-You've downloaded a corrupt file, delete it and re-download the Nougat files.
-Repeat step 10 of the guide, flash the Rom and Gapps package from TWRP recovery.
Can't mount USB drive with CM11 and Windows 7
-Plug the HP TouchPad into your PC with the USB cable
-Go into Device manager. You will see "MTP USB Device" under portable devices.
-Right Click it and select update driver software
-Select Browse my computer for driver software
-Select Let me pick from a list of device drivers on my computer
-Select USB Mass Storage Device then click next to install the driver
10)Reboot into TWRP recovery 3.0.3.0, Flash the Android 7.1 Rom and Gapps
-Once in the new TWRP 3.0.3.0 go to the Wipe menu and select Advanced Wipe.
-Select the System partition and swipe to wipe.
-Click on the TWRP home button(bottom middle) to return to the main menu.
-Select Install, locate the download folder on the left menu.
-Select and install the 7.1 Rom and the Gapps package then reboot.
-After choosing to install the rom click the button to add additional zips, add the gapps package and put a check beside reboot when complete.
Note: The first boot to android 7.1 can take sometime, Wait for it...

MTP file transfer trouble in Redmi-4A

I have rooted Redmi-4A. I have supersu 2.79. My MIUI version is MIUI Global 8.2 | Stable 8.2.1.0 (MCCMIDL).
My USB debugging option is enabled.
I tried the following android applications but failed to get access to the MTP file transfer mode through my phone to PC.
1. MTP enabler Release 3.3
https://forum.xda-developers.com/android/apps-games/app-mtp-enbaler-t3263467
2. QCustomShortcut application
3. MIUI Usb settings
I can select the MTP mode easily in the phone using the default method and the 3rd party apps that I listed above but my PC does not detect my phone. The ADB drivers are installed on my PC. However, my PC detects insertion of USB device and shows a notification upon insertion and taking out of USB cable connected to the phone.
I tried using MI PC suite and it also is not detecting my phone.

Have you tried installing the USB drivers? USB driver is NOT the same as the ADB driver. Google "Redmi 4A driver" and install the USB drivers.

Fobos531 said:
Have you tried installing the USB drivers? USB driver is NOT the same as the ADB driver. Google "Redmi 4A driver" and install the USB drivers.
Click to expand...
Click to collapse
I've installed them as well. They came along with the MiFlash tool. I forgot to mention it earlier
Sent from my Redmi 4A using Tapatalk

archz2 said:
I've installed them as well. They came along with the MiFlash tool. I forgot to mention it earlier
Sent from my Redmi 4A using Tapatalk
Click to expand...
Click to collapse
Have you tried with USB debugging disabled? Also, does changing the USB mode to PTP help?

Fobos531 said:
Have you tried with USB debugging disabled? Also, does changing the USB mode to PTP help?
Click to expand...
Click to collapse
Yes, I tried with both of these options but failed.

Hmm, that leads me to think that something's wrong on the PC's side. Can you boot up a Linux distro and see if you can transfer files there?

Fobos531 said:
Hmm, that leads me to think that something's wrong on the PC's side. Can you boot up a Linux distro and see if you can transfer files there?
Click to expand...
Click to collapse
I have Windows 10 on my PC. I DON'T have Linux.

archz2 said:
I have Windows 10 on my PC. I DON'T have Linux.
Click to expand...
Click to collapse
You can easily create a bootable Ubuntu USB and test the phone in the live session (i.e. without installing it).

I am currently getting that error with my phone. Not sure but it could happen because of the computer. I have two os in my computer. Win10 and Linux mint. Win10 can detect my phone without an issue but mint not. With usb debugging on I can use adb in linux but still no file sharing.

dokuz said:
I am currently getting that error with my phone. Not sure but it could happen because of the computer. I have two os in my computer. Win10 and Linux mint. Win10 can detect my phone without an issue but mint not. With usb debugging on I can use adb in linux but still no file sharing.
Click to expand...
Click to collapse
Do you have a rooted phone?

archz2 said:
Do you have a rooted phone?
Click to expand...
Click to collapse
Yes and no I mean both. Got same issue in different times with different phones. When the time I use crunchbang I would able to fix it. (by installing things on crunchbang not on the phone). But this time, I did not try to fix actually. I am connecting my not rooted phone only for android studio. It detects it. I can install my apps and can test them. But I cant see my phone in file manager. Thats the story.

the same thing is happening to my wife's rooted 4a and her sisters unrooted one

the same for my not rooted one, I've seen my phone one day in windows 10 explorer (this day it makes 10 seconds to see and when reconnected I could see it one time over 2), but the next day nothing more, I spent hours to try fixing it and have a few computers (all with windows 10), I think it's a miui problem not letting windows acces to the storage.

I have a part of a solution, have ejected my sandisk 64GB SD card, found it was formatted in exFat, empty it in windows, put it back in redmi, after redmi search errors I clicked on the notification and saw a few remaining folders and files, so I went to storage to format the sd card, after this the sd card (and only it) was visible in Windows explorer, but only in MTP (without usb debugging), but the copy from the PC is a kind of erratic (drag and drop 1 folder full of subfolders and files is ok but selection of 10GB gb folders and files to copy stops after the first file copied...), I don't understand how one day I manage to see correctly internal storage and sd card...
edit: today I can see the sd card as empty in windows explorer despite of properties shows it is not, and impossible to copy anything...

So i use now a turnaround, I tried airdroid but device folders were shown as sd card(?), but tried another app "gestionnaire de fichiers" flashlight + clock which can activate ftp service (edit: I have seen after that file explorer from miui could, but it hangs before I found the soulution)
so I type on chrome ftp://192.168.0.45:1234 (1234 is the port number you can choose) with the phone on my box with wifi and all (device ssytem androïd too) is accessible (but to copy to the sd card I would have to use a ftp client).
EDIT: Eureka! I uncheck the fictive sd card optimisation (optimisation de la carte sd fictive in french) option in developper's options and all is ok.
---------- Post added at 05:38 PM ---------- Previous post was at 05:22 PM ----------
So for me to access both sd card and internal device memory in USB in Windows 10 for my not rooted xiaomi 4A miui global miui 9 global 8.1.11 beta android 7.1.2N2G47H
I had to:
-activate developper's mode (7 taps on Miui version)
to activate debugging usb (seems better)
-unactivate fictive sd card optimisation (windows and airdroid do not understand internal memory like a sd)
-format the sd card in the phone (in stockage menu, delete the sd card)
using the MPT mode seems the better option (in "selectionner la configuration usb" in french in developper's mode options) or with the notification when usb is connected.
For me Adb drivers were ok.
And there was a problem with file explorer that hangs when "fictive sd card optimisation" was activated, so even redmi can't access to sd card when this option is on...