Related
Ok so I was trying to install a custom recovery on my P500 and when it turned on it gave me this message
fast boot mode started
udc_start
Click to expand...
Click to collapse
I plug it in it gives me
fast boot mode started
--suspend--
--reset--
--port/change--
--reset--
--port/change--
Click to expand...
Click to collapse
I tried out this method: http://forum.xda-developers.com/showthread.php?t=1088046
After keying the fastboot commands in it says <waiting for device>. Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
I'm still on my stock ROM (untouched), phone is rooted (duh) and this is my first attempt to install a custom recovery.
Not allowed to post on that thread ofc, my first post here. All help greatly appreciated. Thanks
Here is the Simple way ..try it
this link for latest working Rom >>
http://forum.xda-developers.com/showthread.php?t=946354
how to root >>
Enable USB debugging on your phone by going to Settings –> Applications –> Development. Check the ‘USB Debugging’ option.
Make sure you have a SD card inserted and mounted in your phone (Don’t know if it’s necessary but before proceeding further I formatted my SD card after taking a backup of the data in it. Why take a risk? Smile)
Download the GingerBreak APK from XDA Developers and get it onto your phone.
Install it by browsing to the GingerBreak APK in any file manager.
Open GingerBreak from your app drawer and press the root button.
Wait for a few minutes. If there are no problems, the device will reboot itself. (The reboot will take quite some time.)
You will see a SuperUser app in your app drawer after the reboot. Open it and see if it is working.
You now have a rooted Optimus One P500 phone.
Now install custom recovery
Follow the below steps to install custom recovery on your LG Optimus One P500.
Install Android Terminal Emulator from Android Market.
Download the file "amon_ra_recovery_installer.zip" from here or here.
Check the MD5 hash value of the downloaded ‘zip’ file. You can use HashTab to do this. Right click on the downloaded file and ensure the MD5 matches 86db8a52b01f049cadb8f097a4c5bd9e.
Extract the contents of the ‘zip’ file to the root of the SD card (Don’t extract inside any folder. For example if your SD Card is mounted on J: in Microsoft Windows then the four extracted files should be right under J:/ like J:/flash_image)
Open the terminal emulator app on your phone and type ‘su’ without the quotes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions for the terminal emulator app. Click ‘Allow’ and proceed. The shell prompt will change from the previous user shell ‘$’ to root shell ‘#’ in the emulator.
Now type in the following command and press Enter. The custom recovery will be flashed on to your phone and it will reboot into Custom Recovery.
sh /sdcard/rf.sh
Shut down your phone and boot into Recovery using the Volume Down, Home and Power switch keys. You can move through the options using the volume up/down keys. Use the Menu button to select the option.
In the recovery menu, select Backup/Restore, then select Nand backup. What this will do is backup your current ROM on your SD card, if something goes wrong while flashing the new ROM you can simply boot into recovery and restore your previous ROM.
Connect the phone to your computer and inside Recovery main menu click the option ‘USB-MS toggle’ and then ‘USB-MS Toggle SDCard’. This will unmount the SD card so that you can see it in your computer. Backup everything from your SD Card. Eject from computer and toggle USB again from recovery to mount the SD card back in phone.
Though it is not a necessity for this ROM, I would suggest partitioning your SD card to create swap and ext partitions. The ext partition will come in use if you want to install apps onto your SD card later. This is different from what you see in Froyo versions of Move to SD option. Partitioning will format your SD card, so make sure you backup your SD card as mentioned in Step 3.
Go back to the recovery menu again and select ‘Partition sdcard’. Then select ‘Partition SD’. Create a swap partition of size 0 and ext partition of size 512. Once done hit Back to go again to the ‘Partition sdcard’ menu. Convert the partition you just created to ext 3 and then ext4 using the options ‘SD:ext2 to ext3’ and ‘SD:ext3 to ext4’.
Toggle USB from recovery again. Inside the SDcard create a folder AAA and copy the ROM you downloaded in Step 1 into the folder ‘AAA’ on your SDCard. Once done, eject the SD card and toggle USB again to mount the SD Card in the phone again.
Go to the Wipe option in the recovery menu and wipe userdata, /data, /sd-ext, /sdcard/.android_secure, /cache, ‘Dalvik-cache’
Then go to the Flash Zip option in the recovery menu and select the zip file you copied in Step 6.
Sit back and relax while the zip is flashed. Once recovery shows that flashing is complete, reboot phone from recovery. The first boot will take quite some time.
Enjoy Gingerbread 2.3 on your LG Optimus One P500.
@ above completely unrelated to his problem.
Sent from my LG Optimus One P500 using XDA App
Appreciate your post but it has nothing to do with query sadly.
I was doing what you've mentioned in the installing recovery section when things went wrong.
I run Win7 x64 btw.
istoner said:
Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
Click to expand...
Click to collapse
That is correct - drivers issue.
1/ Add DEVMGR_SHOW_NONPRESENT_DEVICES to your environment on Windows and set the value to 1. (In Advanced system settings, Google if you do not know how.) Log off and log back on.
2/ Run devmgmt.msc
3/ There, View - Show hidden devices
4/ Go thru it and uninstall everything Android-related (for starters, ADB Interface and stuff under it, Disk drives, Modems, Ports (COM and LPT), USB controllers - might not be complete list above)
5/ Reboot the PC.
6/ Install the latest drivers for your phone.
7/ If it worked, once you have plugged in the phone stuck in fastboot mode, in device manager you should see Fastboot interface (Google USB ID) in ADB Interface section.
Thanks, trying that out now.
doktornator,
Thanks a bunch. It was an issue with the drivers, I tried your method a few times with little success. Then I let Windows find the drivers (out of all the things), and that worked. Relieved and slightly embarrassed that Windows could what I couldn't
Good that it works now. Fingers crossed to unbrick your phone soon.
Oh it's unbricked and ready to go again lol.
Hi, I am on Windows XP with the exact same problem.
Have tried the B2CApp for driver updates with no luck. Tried windows automatic driver installation,again no luck.
Anything else that I could try on a Win XP machine?
UPDATE:
I have fixed the issue. Got the drivers mentioned in this thread:
Anyone else stuck with Windows XP not recognizing the device even after the B2CApp installation, try these drivers:
http://android.modaco.com/topic/324744-waiting-for-devicefastboot/#
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
droidao said:
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
Click to expand...
Click to collapse
is the name of the .img file recovery.img?
the command is really fastboot flash recovery (name of file).img
Yes it is...Actually I tried both ways (renaming and keeping the original name)! But I've finally figured it out!!! Here was the problem: when I installed android sdk I added the paths of the required directories (tools and platform-tools) to the system variable section so I could launch tools without writing the path all the time...However, because desperate times call for desperate (and often silly) measures, I decided to type the command cd "name-of-directory" anyway and that...made the trick.
This community is indeed great...I'm going to distribute some "thankyous" now!
I had the same problem with Win7, Updating the drivers from the device manager of w7 worked for me. Hope it helps.
Ps: will take around 15 mins updating.
Hey Streakers,
I am using DSC 1.4 on my streak. I wanted to try the OTG feature and ordered an OTG cable.
And I have to say: it works! I can use a PC-keyboard or a mouse. But I have one problem with the automount-function of a usb flash drive.
When I plug the drive+the cable to my streak for the first time, I can read the content on /mnt/usbdisk.
But when I unplug the flash drive and plug the same again, or another flash drive, nothing happens. That means the folder is emty.
After a reboot it works again. Is there a way to mount the flash drive manually with the console? Or any other trick?
Thanks for your answers and a special thanks to everyone who keeps this device alive!!! :good:
i remember hunterteins was facing similar problem and got it resolved.
Maybe PM'ing him would help?
allerd said:
But I have one problem with the automount-function of a usb flash drive.
When I plug the drive+the cable to my streak for the first time, I can read the content on /mnt/usbdisk.
But when I unplug the flash drive and plug the same again, or another flash drive, nothing happens. That means the folder is emty.
After a reboot it works again. Is there a way to mount the flash drive manually with the console? Or any other trick?
Click to expand...
Click to collapse
I newer got around, why that happend. In the end I thought it must have been a broken self-soldered cable.
Another show stopper can be an open file on the USB device. As long as some process is accessing a file in /mnt/usbdisk/ automount via vold will not work.
Lastly you may take a look into the Q5 USB Memory Manager from hxxp://android.gval.biz/
Good luck,
hunderteins
thx for the fast answers! i will try it and report the result!
ok, I tried this q5 usb memory manager. but is has no effect.
I found out, that when I restart the streak and plug the flash drive, the q5 manager detects in /sys/block/ the folder "sda". This is, according to the q5 instructions, the recomended block device. In /sys/block/sda/device/ are documents like "model" and "state". According to them runns in the sda device or folder a "16GB Trannscend" flash drive. That's the plugged drive.
I find the same documents, when I replug the flash drive only with the difference that the block device is called "sdb".
I belive the q5 manager has no impact on the mount/unmount process, because when i click "unmount file system " nothing happens.
I mean the sda/asb folder doesn't disappear.
Is there a opportunity to force the system to unmount this sda system?
Does the automount function works on your devices without problems?
I have no programming background, but if it's possible to unmount the sdcard, I gues this is at last only a codeline in the shell, why it's not possible to change the codeline for the flash drive? Only a noob idea
thanks in advance
Hey guys.
I have Samsung galaxy ace 5839i (stock for 5830i) and I am using it for a few years, but this problem came for the first time.
Always, when I try to connect my mobile to pc using cable, it just won't connect, it won't even show me the notification of connecting.
Before this problem, I connected it to fedora linux and it was succesful, but now? It won't show me that USB sign even in windows.
Any help?
Thanks in advance
@LiQuDiAk, basically s5839i and s5830 i are identical in many areas ,, few questions though,, did you root your device or you are on android 2.3.6 stock version / kernel 2.6.35.7 ?
when you are in your windows device manager ( while you are connected , do you see any exclamation / question marks in front of the corresponding driver), you can always uninstall your old driver, reboot , then try compiled driver in attachment , and reboot to take proper effect in your registry (tested on win xp/7 -32bit) . Also check your device settings>Application>Development > USB Debugging and make sure the option is checked. now lets check your debugging mode through ADB command and see if your device is being recognized. download platform zip attachment, unzip it and put the folder someplace like your desktop. Now open your command prompt (cmd) through whatever means you are comfortable and change directory (cd) to the unzip folder or simply open your folder and drag/drop adb.exe into your CMD to be in the right place very fast. Then type "adb devices" without quotation marks and report for more troubleshooting .Assuming your Samsung cable is not faulty of course.
@ehsanotaku Yes i did root my phone on pheonix fire rom. No i do not see any. And debugging is checked, that was my first guess why it was causing this. I was checking, whether my device is recognized in linux (only available OS in present) and it was NOT, but the cable is not faulty, because it was charging my phone... but i will do recognize process on windows, hope it will get better. But thanks so far!
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
LiQuDiAk said:
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
Click to expand...
Click to collapse
off topic though, gender discrimination is prejudice,, sorry if you are offended . Learning from each other despite your gender,does not undermine your knowledge EVER mate You might find it hard to believe, but I am quite novice in android stuff myself ( learning a great deal from some female members though ).
Back to topic at hand now,,,So let Perfectly Clear take away the time-consuming tasks and fix some stuff ..1. so you can not access your sdcard's content from either systems,, even if you try some live bootable Ubuntu disk/flash into your system and boot it up,, you can't access the mount drive content , right?
2. screenshot of your device manger while you are connected always help mate
3. those long streams of numbers and words is supposed to be your device name , it means your device is communicating with your pc ( /sdcard/ should not be corrupted). You can push (copy ) some vital files to your device with following command :
again same path >> put some file into your desktop (drag/drop to cmd)
i.e: "adb push C:\Users\ehsanotaku\Desktop\test.txt /sdcard/"
back to your device and check root of your files with whatever file explorer you got to approve the theory
4. forgot to ask , just to be on the safe side your device is not in boot loop process, stuck on samsung splash screen or something like that, right?
okay, thanks!
1. I cannot access it trough USB to mobile way, but from SD card adapter, yeah I can (it is just the weird feeling, when you always have to put out your sd and do it that way, i would like to sort this out)
2. http://s1.postimg.org/nkta50u3x/Untitleddas.png I suppose the unknown device is my phone.
3. Just a question, my phone is not connected, i cannot access it and this doesn't help
4. Nope, it is working, i can access everything, just this connecting problem i have. anything else is running smoothly.
Let's say any of this will work, do you think flashing a stock rom will help? I am not sure, if this is problem of rom or not, so...
And maybe i wasn't clear (my bad if not) but when i plug the cable in my device and pc, pc will make this sound of new device found, but it wont show me anything, so my phone. It will charge, but it wont connect, it is behaving like it is on a charger and not connected to the phone.
@LiQuDiAk, Hasty actions are done in a hurry, sometimes without the necessary care or thought. Now let's not leap to any conclusion about your Android custom Rom and flashing back to stock. lets focus on your first most obvious problems,which is driver related.
You didn't declare your flavor of windows: i.e: Windows x86 based-PC;professional 7
Not so sure of your OS Name/Version and System Type, search "system information" in your search box.
Your task manger depicted ACPI x64 ( 64-bit system, no wonder previous 32-bit compatible didn't work out for you ).
Symptoms observed so far:
1. USB cable only charges ( remember your USB cable data line might be the culprit. Just in case of only charging,checking with another set recommended. Your USB port might be problem, some dirt or faulty data line, checking with another USP port doesn't heart though.
2. Windows recognizes something more (like in your case, struggling to find proper corresponding driver), but cannot see it as a Samsung android device (cannot allocate the installed USB drivers to the device).
-If you got Kies (Samsung proprietary software) installed on your PC, delete it with a descent uninstaller program such as CCleaner free version .Kies might cause driver conflict , use it as only last resort , if all drivers failed to communicate with s5830i device.
-Also Uninstall your previous given driver same way, now restart , back to system and grab set of universal Samsung Drivers from attachment .
3.Can't see your "USB connected" in Android notification bar, so you cant click on it and mount your storage data part while you are connected to your PC.
-Normally, when you plug in your Android device, Windows will recognize it as an MTP (Media Transfer Protocol) device and quietly mount it.
However, if you’ve ever attempted to unlock your device such as to install a new ROM or root it, then such miss behaviors might be expected occasionally .
Before i go for more troubleshooting , please provide a full screenshot from your "About Phone" page in your settings . I am quite curious about this phoenix Rom you have mentioned though . I am quite familiar with at least dozen of discontinued/ported projects, but never heard of such ported Rom from other models into s5830i .
Couple of solutions :
Navigate to your settings,Storage and touch the upper-right corner for the “USB computer connection” options, if you have this part available.
make sure “Media device (MTP)” is selected. ( if you have USB Utilities section or whatever added section in your custom settings go there . Selecting that will do the trick. If it does not, then you likely have a driver problem.
Open your device manager, Right click on your unrecognized device in question,choose update driver software, choose Browse my computer,find it through given x64 drivers in your package ,Restart. ( After a successful installation, restart your PC, you must have something like the picture in attachment ) .
Problem was not resolved, Uncheck your debugging option,power off your phone. Now hold Volume(+) + Home + Power for a couple of seconds simultaneously to get to your Samsung Recovery or your Clockwork Recovery, choose Reboot( might be some process/service in your background, which interfere with your Auto USB connected feature of your device. See if the problem is being resolved .
Problems have been persisting, we might need to format your SD card, but before that, insert it into your card reader, in your file explorer window choose Tools>Folder options>select view tab> tick your select hidden file.folders. Now copy all of your SD card's contents into some folder, safe inside your PC.
We can format your card through your clockwork mod recovery console, or some partition tools such as free mini partition wizard,,
problem still persist? let me know
Hey
After some rest with this, my mobile got it solved (dunno why, just once tried to do it and it works.)
So, thank you very much with your answers!!!!
And about that screenshots, I will PM you
But, really, thanks a lot, mate!!!!
So, as the story goes, I accidently bricked by tablet, by rooting it.
Now all I have is.
- EFI Shell
- EFI OS
- my USB Stick
I managed to boot the stock 4.4.4 firmware downloaded from "" and it flashed it's files (system.img boot.img etc.)
However the tablet still refused to boot.
Nevermind Fixed it.
==================================================================================
=======FIXNG you tablet (Onda V919 Air Dual OS in my case ) WITHOUT Fastboot===================
Disclaimer: this WILL completly erase your Tablet and REMOVE THE WINDOWS PARTITION if you had one
It is advised to remove the Micro SD from your TABLET PRIOR USING THIS FIXING PROCESS, it MIGHT GET ERASED
All you need to fix your tablet (as long as you can still access the Bios Screen via USB Keybaord and pressing ESC during boot) is:
- USB OTG Adapter
- USB Hub (preferably self powered over USB)
- USB Keyboard
- USB Stick (formatted FAT 32)
In my case I required the Firmware "V919_Air_DualOS_4.4.4_V1.0.0_v7" (Kernel Version: 3.10.20-00004-gf8a8ae3-dirty).
#00 Fetching the Firmware
##This is the step I cannot help you with: You need to aquire the corresponding FW for your Tablet (it will be a *.rar file with at least 500MB I surmise)
1. Extract the files from the rar to the USB Stick (formatted in FAT32)
2. Connect the USB Keyboard to the Hub
3. Connect the USB Stick to the hub aswell
4. Connect the USB Hub itself to the Tablet (by USB OTG)
5. Turn the Tablet on and press "ESC" immediately & hold it until you enter BIOS (this SHOULD work, even if you tablet refuses to boot into Fastboot via VOL+,VOL- & Power hold)
6. Change the boot order inside "BOOT" to 1. EFI Shell
7. Press F4 and "Save and Exit" (leave everything connected and don't touch the Tablet)
8. The Tablet should now reboot to EFI Shell
9. From here on things should go automatically (startup.nsc should be automatically read from the stick and should autoboot the Recovery files)
[[startup.nsc should contain this line (if you open it in the Editor of your PC): efilinux-eng.efi -f droidboot.img]]
10. If DroidBoot is on...: biggest you are nearly done !
11. wait for Droid Boot to flash all files (system.img will take a REALLLLLY long time... just leave everything as is)
12. Tablet will reboot in Android Mode
I'd love if there was a subcategory called "Onda Tablets" so s.o. could pin this.
It is possible that such guide exists already, but I had spent the last day just fixing my device... so...)
Please report back to tell me if it worked for you.
If I feel lucky I might add some images to this guide sometime...
about The solution.
-Rye- said:
So, as the story goes, I accidently bricked by tablet, by rooting it.
Now all I have is.
- EFI Shell
- EFI OS
- my USB Stick
I managed to boot the stock 4.4.4 firmware downloaded from "" and it flashed it's files (system.img boot.img etc.)
However the tablet still refused to boot.
Nevermind Fixed it.
==================================================================================
=======FIXNG you tablet (Onda V919 Air Dual OS in my case ) WITHOUT Fastboot===================
Disclaimer: this WILL completly erase your Tablet and REMOVE THE WINDOWS PARTITION if you had one
It is advised to remove the Micro SD from your TABLET PRIOR USING THIS FIXING PROCESS, it MIGHT GET ERASED
All you need to fix your tablet (as long as you can still access the Bios Screen via USB Keybaord and pressing ESC during boot) is:
- USB OTG Adapter
- USB Hub (preferably self powered over USB)
- USB Keyboard
- USB Stick (formatted FAT 32)
In my case I required the Firmware "V919_Air_DualOS_4.4.4_V1.0.0_v7" (Kernel Version: 3.10.20-00004-gf8a8ae3-dirty).
#00 Fetching the Firmware
##This is the step I cannot help you with: You need to aquire the corresponding FW for your Tablet (it will be a *.rar file with at least 500MB I surmise)
1. Extract the files from the rar to the USB Stick (formatted in FAT32)
2. Connect the USB Keyboard to the Hub
3. Connect the USB Stick to the hub aswell
4. Connect the USB Hub itself to the Tablet (by USB OTG)
5. Turn the Tablet on and press "ESC" immediately & hold it until you enter BIOS (this SHOULD work, even if you tablet refuses to boot into Fastboot via VOL+,VOL- & Power hold)
6. Change the boot order inside "BOOT" to 1. EFI Shell
7. Press F4 and "Save and Exit" (leave everything connected and don't touch the Tablet)
8. The Tablet should now reboot to EFI Shell
9. From here on things should go automatically (startup.nsc should be automatically read from the stick and should autoboot the Recovery files)
[[startup.nsc should contain this line (if you open it in the Editor of your PC): efilinux-eng.efi -f droidboot.img]]
10. If DroidBoot is on...: biggest you are nearly done !
11. wait for Droid Boot to flash all files (system.img will take a REALLLLLY long time... just leave everything as is)
12. Tablet will reboot in Android Mode
I'd love if there was a subcategory called "Onda Tablets" so s.o. could pin this.
It is possible that such guide exists already, but I had spent the last day just fixing my device... so...)
Please report back to tell me if it worked for you.
If I feel lucky I might add some images to this guide sometime...
Click to expand...
Click to collapse
HI what if you did all of that but it gets to the flash bit, but it say flash failed can't format partition flash failed..... What should i do?
Hello All,
Years ago, I installed CyanogenMod 10.1. The TP works OK. Here's the info:
- Android version: 4.2.2
- Kernel version: 2.6.35-cyanogenmod [email protected] #1 Tue Dec 10 17:10:10 CST 2013
- CPU: ARMv7 Processor rev 2 (v7l)
- CyanogenMod version: 10.1-20131210-SNAPSHOT-VPN-tenderloin
- Build date: Tue Dec 10 17:05:54 CST 2013
- Build number: cm_tenderloin-userdebug 4.2.2 JDQ39E 8d5ffaac34 test-keys
From what I know, external USB can be connected to HP TP via OTG cable and external power. So in an effort to use this HP TP (which has been collecting dust) as a digital frame, I follow this link:
https://www.youtube.com/watch?v=Nc7tlPwFQpg&t=198s
The guy has links to buy OTG cable and Y adapter:
https://www.amazon.com/gp/product/B005QX7KYU/ref=oh_o02_s00_i00_details
https://www.amazon.com/gp/product/B0041CFFBM/ref=oh_o01_s00_i00_details
So I bought (2) OTG cables and (2) Y adapters from the above links.
The power adapter I use is a working 2A one (brand name: Amazon). I formatted the USB thumb drive. Then loaded a few jpeg files to the thumb drive.
When I followed the above Youtube video to plug the USB drive, the app 'ES Explorer' does recognize the USB drive but it shows 'Empty folder'. I changed out OTG and Y cables but still the same: the HP Touchpad won't recognize the jpeg files on the thumb drive.
Please tell me what I did wrong and show me how to fix it.
I'm open to two solutions:
1) Open the HP TP up and solder a SD/micro SD module (I'm a circuit technician and have no problems doing that).
2) Wipe out the HP TP and install another Android version newer and/or capable of reading external thumb drives (I hate wasting a nostalgic HP TP).
Thank you very much for your help.
quangmsc said:
1) Open the HP TP up and solder a SD/micro SD module (I'm a circuit technician and have no problems doing that).
2) Wipe out the HP TP and install another Android version newer and/or capable of reading external thumb drives (I hate wasting a nostalgic HP TP).
Thank you very much for your help.
Click to expand...
Click to collapse
This is the OTG cable that I use and another one that could not find on line:
Click HERE for 4 Port Micro USB
I had use it with a 16GB USB drive on Evervolv 7.1.2 for curiosity to see how it works and I was very impress with the speed. I was able to play movies from the USB drive and at the same time also connected an USB Ethernet ( I had to incorporate the driver into the kernel ).
It is possible to have more than one USB device connected at same time, like USB drive, Keyboard, mouse and wire Ethernet. The tablet is like a laptop with connections by wire.
If ES Explore recognize the USB drive then the OTG cables is good, but you need another software to be able to read the files. I tried it Total Commander and there was another software to mount the partition, I think it was Paragon:
https://play.google.com/store/apps/details?id=com.paragon.tcplugins_ntfs_ro&hl=en_US
Install that to mount the USB drive and then the files should be available in ES Explore if not then try Total Commander and use the plug in for it.
Thanks but unfortunately none of those work because those methods only work for at least Android 4.4. Please let me know how to 1) wipe the TP and 2) find a stable and newer Android OS / CyanogenMod to install on the TP which will only be used as a digital frame and not anything else (no internet browsing, games, etc.).
All I see is this:
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-hp-touchpad-t3923512
or
https://forum.xda-developers.com/hp-touchpad/development/rom-evervolv-7-0-0p1-wifi-t3456292
but both don't have step by step installation guides.
Thanks @HP_TOUCHPAD
quangmsc said:
Thanks but unfortunately none of those work because those methods only work for at least Android 4.4. Please let me know how to 1) wipe the TP and 2) find a stable and newer Android OS / CyanogenMod to install on the TP which will only be used as a digital frame and not anything else (no internet browsing, games, etc.).
Click to expand...
Click to collapse
If you want to easily wipe the tablet and make it a 100 % Android device and install any ROM then follow this guide.
There is a lot to read, but very simple, flash Automatic_Wipe_ALL and it does everything.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Tablet can read and write up to FOUR USB drive connected at the same time, attached are screenshots using Evervolv 7.1.2 with Total Commander and the plug in for the USB.
https://www.ghisler.com/android.htm
USB drive tested: 16G SandDisk, 16G Lexar, 8G Patriot
All three USB can be connected at the same time and be access using total commander file manager.
Also I plug in the MicroUSB Ethernet and works with the USB connected.
HP_TOUCHPAD said:
If you want to easily wipe the tablet and make it a 100 % Android device and install any ROM then follow this guide.
There is a lot to read, but very simple, flash Automatic_Wipe_ALL and it does everything.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
The Tablet can read and write up to FOUR USB drive connected at the same time, attached are screenshots using Evervolv 7.1.2 with Total Commander and the plug in for the USB.
https://www.ghisler.com/android.htm
USB drive tested: 16G SandDisk, 16G Lexar, 8G Patriot
All three USB can be connected at the same time and be access using total commander file manager.
Also I plug in the MicroUSB Ethernet and works with the USB connected.
Click to expand...
Click to collapse
Thanks. I downloaded 'TWRP Recovery Version 3.2' to my computer, unzip and copy the files to the HP TP root directory. Unplug the TP from computer. Turn off the TP completely then boot it up again. No recovery menu to choose other than WebOS Recovery and some other menu options unrelated to automatic wipe out. So I'm stuck there.
Can I use this one instead?
https://www.youtube.com/watch?v=VP-FH6fS2GI
He basically shows step by step how to uninstall everything by plugging the TP to a computer which already has Nova installed.
Part 2: Let's say everything is wiped out, which android version would you recommend given my simple use of the TP? This is Android Pie 9.0 on Youtube (same instructor): https://www.youtube.com/watch?v=hAuNSoe6euI
Thanks again.
quangmsc said:
Thanks. I downloaded 'TWRP Recovery Version 3.2' to my computer, unzip and copy the files to the HP TP root directory.
TWRP 3.2.1 needs to be flash using another recovery, if the uImage.Recovery is copy into boot then the file moboot.default needs to be edited and add uImage.Recovery to show in the moboot menu. It is best to flash it as it will create the entry for moboot menu. But now there is a copy there and the /boot maybe full and it needs to be clean.
Unplug the TP from computer. Turn off the TP completely then boot it up again. No recovery menu to choose other than WebOS Recovery and some other menu options unrelated to automatic wipe out. So I'm stuck there.
As mentioned the entry uImage.Recovery must be add to a file in the /boot partition.
Can I use this one instead?
https://www.youtube.com/watch?v=VP-FH6fS2GI
He basically shows step by step how to uninstall everything by plugging the TP to a computer which already has Nova installed.
Part 2: Let's say everything is wiped out, which android version would you recommend given my simple use of the TP? This is Android Pie 9.0 on Youtube (same instructor): https://www.youtube.com/watch?v=hAuNSoe6euI
Thanks again.
Click to expand...
Click to collapse
Follow this guide to Wipe it all, the only thing to do is one click and is done.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
boot the Linux ISO file into a PC or virtual machine, place the tablet in WebOS recovery mode connect the tablet to PC and click on Wipe ALL, then install any ROM.
I recommend Evervolv 7.1.2 as that is the one that I used for the screenshots with the USB connected.
Then go to this guide and install the ROM:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
To flash a ROM, copy the zip files to the Tablet and using TWRP select and flash.
If you have novacom install on your PC and know how to use it then follow this guide to wipe all.
https://forum.xda-developers.com/hp-touchpad/general/rom-guide-alternative-method-to-install-t3575861
All those options allows to load Wipe_All to have everything done automatically. Select the best option for you but the outcome is the same.
HP_TOUCHPAD said:
Follow this guide to Wipe it all, the only thing to do is one click and is done.
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-novacom-repair-android-t3960435
boot the Linux ISO file into a PC or virtual machine, place the tablet in WebOS recovery mode connect the tablet to PC and click on Wipe ALL, then install any ROM.
I recommend Evervolv 7.1.2 as that is the one that I used for the screenshots with the USB connected.
Then go to this guide and install the ROM:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
To flash a ROM, copy the zip files to the Tablet and using TWRP select and flash.
If you have novacom install on your PC and know how to use it then follow this guide to wipe all.
https://forum.xda-developers.com/hp-touchpad/general/rom-guide-alternative-method-to-install-t3575861
All those options allows to load Wipe_All to have everything done automatically. Select the best option for you but the outcome is the same.
Click to expand...
Click to collapse
So I created a bootable USB drive having 'HP_Touchpad_Novacom_Repair_Android'. Change my laptop boot priority to USB and used 'unetbootin-windows-677' to 'Wipe All' the Android version. After that, every time the HP TP is booted, only a moboot 0.3.8 menu appears with these options:
- boot Recovery
- boot webOS recovery
- reboot
- shutdown
Now, I have downloaded these zip files:
- ev_tenderloin-7.1.2-nightly-2017.11.03
- HpTp_MaXtreme_1674_CPU_Universal_Optimize_Swap_Evervolv_7_1_2_Nougat
- open_gapps-arm-7.1-pico-20200520
I need to copy these zip files to the tablet but I don't know how: Turn the tablet on and select 'boot webOS recovery' and the white USB logo appears. Then connect the tablet to a laptop with Windows 10 running Then a message pops up 'We're setting up Palm device'. I open Windows Explorer to copy the zip files to the tablet but there's no 'Palm' folder (before Android was wiped out, I do see 'Palm' folder in Windows Explorer). Can you tell me how to copy the zip files to the table then? Should I copy those zip files to the bootable usb thumb drive then run unetbootin-windows-677 on the laptopn and copy the zip files over to the tablet?
quangmsc said:
So I created a bootable USB drive having 'HP_Touchpad_Novacom_Repair_Android'. Change my laptop boot priority to USB and used 'unetbootin-windows-677' to 'Wipe All' the Android version. After that, every time the HP TP is booted, only a moboot 0.3.8 menu appears with these options:
Great Job! now you have a Linux OS with built in Novacom drivers that will always work no matter what.
- boot Recovery
- boot webOS recovery
- reboot
- shutdown
The tablet has been completely wipe and only the Android partitions were created.
boot Recovery is TWRP 3.2..1 by @flitman that allows to flash any Android ROM and works 100 % all the time.
Now, I have downloaded these zip files:
- ev_tenderloin-7.1.2-nightly-2017.11.03
- HpTp_MaXtreme_1674_CPU_Universal_Optimize_Swap_Evervolv_7_1_2_Nougat
- open_gapps-arm-7.1-pico-20200520
I need to copy these zip files to the tablet but I don't know how: Turn the tablet on and select 'boot webOS recovery' and the white USB logo appears. Then connect the tablet to a laptop with Windows 10 running Then a message pops up 'We're setting up Palm device'. I open Windows Explorer to copy the zip files to the tablet but there's no 'Palm' folder (before Android was wiped out, I do see 'Palm' folder in Windows Explorer). Can you tell me how to copy the zip files to the table then? Should I copy those zip files to the bootable usb thumb drive then run unetbootin-windows-677 on the laptopn and copy the zip files over to the tablet?
Click to expand...
Click to collapse
WebOS Recovery is only use to repair the Tablet ( troubleshooting )
Recovery TWRP is the App that is use to flash any ROM.
Boot into TWRP connect the Tablet to any PC, Micro SD will show ( is like a portable USB storage ) It works on any PC there is no need to have the novacom drivers install.
Copy all the zip files to the Micro SD card or USB ( it has different names )
Go to TWRP on the Tablet and select the zip files to flash, when done reboot.
It is very simple the only thing to do is select and flash that is it.
Here are some youtube videos about HP Touchpad Novacom Repair for Android, that shows how is use:
https://www.youtube.com/watch?v=4pKNPYKGp-o
https://www.youtube.com/watch?v=A9M-peqf45I
HP_TOUCHPAD said:
WebOS Recovery is only use to repair the Tablet ( troubleshooting )
Recovery TWRP is the App that is use to flash any ROM.
Boot into TWRP connect the Tablet to any PC, Micro SD will show ( is like a portable USB storage ) It works on any PC there is no need to have the novacom drivers install.
Copy all the zip files to the Micro SD card or USB ( it has different names )
Go to TWRP on the Tablet and select the zip files to flash, when done reboot.
It is very simple the only thing to do is select and flash that is it.
Here are some youtube videos about HP Touchpad Novacom Repair for Android, that shows how is use:
https://www.youtube.com/watch?v=4pKNPYKGp-o
https://www.youtube.com/watch?v=A9M-peqf45I
Click to expand...
Click to collapse
Thanks a lot. I was able to installed Nougat on TP. Try to install Paragon exfat/ntfs software but the software shows it's not compatible with HP TP Nougat 7. Installed Total Commander then install the plug-in (USB Stick, free trial btw) then the tablet restarted by itself. As it turns out, the battery drained from 50% to 0% right after installing the plug-in.
So now I'm monitoring the tablet to see if there are problems.
Also, System Storage and (Android Stock) Gallery both don't see the pictures of the usb thumb drive. The only one app can see the usb drive is Total Commander. I clicked on the pictures but there's no photo browsing app associated with Total Commander so I can't see the photo slides. If you happen to know such a photo viewing app compatible with Total Commander, please let me know.
quangmsc said:
Thanks a lot. I was able to installed Nougat on TP. Try to install Paragon exfat/ntfs software but the software shows it's not compatible with HP TP Nougat 7. Installed Total Commander then install the plug-in (USB Stick, free trial btw) then the tablet restarted by itself. As it turns out, the battery drained from 50% to 0% right after installing the plug-in.
So now I'm monitoring the tablet to see if there are problems.
Always keep the tablet charging, it will prolong the battery life.
Also, System Storage and (Android Stock) Gallery both don't see the pictures of the usb thumb drive. The only one app can see the usb drive is Total Commander. I clicked on the pictures but there's no photo browsing app associated with Total Commander so I can't see the photo slides. If you happen to know such a photo viewing app compatible with Total Commander, please let me know.
Click to expand...
Click to collapse
That is a limitation of Android but some apps would be able to read the USB, to look here:
https://forums.androidcentral.com/samsung-galaxy-tab-s-10-5/563616-possible-view-videos-photo-slide-show-usb-connected-flash-drive-card-reader.html
I know that using a USB stick is the most cost effective and easy way to set up, but also keep in mind a wireless hard drive, of you can set up a share folder from a PC and connect the Tablet and show all the photos from a network location. There are many ways the tablet can produce a slide show.
HP_TOUCHPAD said:
That is a limitation of Android but some apps would be able to read the USB, to look here:
https://forums.androidcentral.com/samsung-galaxy-tab-s-10-5/563616-possible-view-videos-photo-slide-show-usb-connected-flash-drive-card-reader.html
I know that using a USB stick is the most cost effective and easy way to set up, but also keep in mind a wireless hard drive, of you can set up a share folder from a PC and connect the Tablet and show all the photos from a network location. There are many ways the tablet can produce a slide show.
Click to expand...
Click to collapse
When I click on a photo on USB stick in Total Commander, a menu pops up 'with 2 options:
- Download+Open with
- Download+Edit
But whatever option you choose, nothing happens. It can't even view a photo. So I guess Total Commander is trying to associate a photo with an photo viewing app but it can't find such an app.
For ES Explorer, it can open a photo but no slideshow ( I heard that previous version of ES Explorer had that feature) so you have to manually click on the next photo.
Don't bother with Google Photos because it can't detect photos on the USB stick. So for now, I copy some of my pictures on the HP TP internal storage and play the slideshow by running Google Photos.
Hoping one day either ES Explorer or Total Commander can do slideshows.
Thanks for all your tremendous help.
No text.