Database Develop

[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?

[Q] HP Touchpad not recognized by Windows

I searched all over and found some similar threads, but after reading through all of them I'm still stuck and can't figure this out.
I have a 32GB Touchpad that I put CM9 Alpha .5 on, and it was working fine. Installed without a hitch. I went to flash Alpha 2, and it broke moboot - and now I have the android system on there, however I can't boot it, and I can't reflash it, which is the main problem.
When I go into recovery mode (vol up and power), and hook it up to my Windows 7 64 machine (or my 7 64 laptop, or my hackintosh OS X Lion - all with novacom drivers and whatnot) it shows up as Palm Novacom (bootie), but won't mount the USB drive so I can run ACMEInstaller2. I've tried reinstalling all the drivers, usb, novacom, etc, and even reset webOS with webdoctor. It still won't show up.
When I boot into webos and mount as disk drive, it shows up fine. I even took those drivers and replaced the palm bootie drivers with those, but that still didn't solve it. The few threads I found similar to this solved their problems by now, or it worked on another computer. I don't have easy access to other machines aside from those 3, and some friends Mac's that didn't work either. I rarely post when I run into a problem, always try to solve things on my own but I can't figure it out for the life of me. Just want to get CM9 back up and running!
Anyone have any other ideas? Greatly appreciated, thanks!

bone625 said:
I searched all over and found some similar threads, but after reading through all of them I'm still stuck and can't figure this out.
I have a 32GB Touchpad that I put CM9 Alpha .5 on, and it was working fine. Installed without a hitch. I went to flash Alpha 2, and it broke moboot - and now I have the android system on there, however I can't boot it, and I can't reflash it, which is the main problem.
When I go into recovery mode (vol up and power), and hook it up to my Windows 7 64 machine (or my 7 64 laptop, or my hackintosh OS X Lion - all with novacom drivers and whatnot) it shows up as Palm Novacom (bootie), but won't mount the USB drive so I can run ACMEInstaller2. I've tried reinstalling all the drivers, usb, novacom, etc, and even reset webOS with webdoctor. It still won't show up.
When I boot into webos and mount as disk drive, it shows up fine. I even took those drivers and replaced the palm bootie drivers with those, but that still didn't solve it. The few threads I found similar to this solved their problems by now, or it worked on another computer. I don't have easy access to other machines aside from those 3, and some friends Mac's that didn't work either. I rarely post when I run into a problem, always try to solve things on my own but I can't figure it out for the life of me. Just want to get CM9 back up and running!
Anyone have any other ideas? Greatly appreciated, thanks!
Click to expand...
Click to collapse
Take a look at this thread. I think it could have information that could maybe help you.
forum.xda-developers.com/showthread.php?t=1508572

Thanks, bah tried all that - the problem is mounting USB recovery, can't get into androidto test anything else. I'll have access to a few other computers this weekend so I"ll see if they can find it. Going to rewipe everything tonight as well, will update... pretty annoying.

I have an idea.
What you can try is to reboot into WebOS, mount the /media drive so you can copy files to it from Windows. On that media drive, there should still be a folder called cminstall. Copy the moboot install zip back into there, and then reboot the tablet into recovery (Power+VolUp). From there, run AcmeInstaller2 again, and you should be good to go - it'll run, and force an install of the contents of that /media/cminstall folder, which'll put Moboot back in place.
At least, that's what SHOULD happen. I'm no expert, but from what I've seen and played with, that should do what you're trying to achieve.

Thanks for trying.. Not exactly what it needed to be fixed though. I have everything ready to go in uninstall, the computer (any computer I've tried so far, and its been quite a few - that all used to read the touchpad in recovery mode) won't register it and mount it as a drive so I can run ACMEInstaller in the first place.
It must have changed something on the touchpad itself, because it used to mount fine before that happened... Now every computer installs it as palm novacom booties and never mounts the actual drive, and acmeinstaller just says no device or something like that. Bah, still can't figure it out, I miss android haha.

Did you enable MTP in the advanced menu under the Storage section?

Are you trying to get the device to show up in adb? If you are having troubles with that I found a really nice guide on another website on how to get adb to read the touchpad if nothing else is working. Not sure if I can post the link or not. Send me a pm if this is something you need.
Sent from my cm_tenderloin using xda premium

Problem is I can't boot into android cause the bootloader broke and I can't get it to boot android period, even with cyboot. I know all l I have to do is run ACME again... But I can't run it cause it won't mount haha. Stuck in webOS for now, and every computer I've tried won't boot recovery mode anymore. Drivers check out and register but can't change anything to recognize it as a drive. I think I'm going to try to manually uninstall everything android, then reinstall webOS and see if it mounts then. Blah!

AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
In recovery mode, the touchpad still wasn't mounting the USB drive in windows, it was just installing as palm device bootie and not mounting. When I tried to run ACMEInstaller it would just say device not found.
HOWEVER; I started webOS doctor. I got to the screen where it says connect your device with a usb cable and stayed there - the next button was enabled so webosdoctor saw the touchpad. It still didn't mount, but I ran ACMEInstaller for the hell of it without going any further with webosdoctor and it just ran and completed.
Back up and running Alpha 2, whew! Hopefully this can help someone else if this happens to them.

bone625 said:
AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
In recovery mode, the touchpad still wasn't mounting the USB drive in windows, it was just installing as palm device bootie and not mounting. When I tried to run ACMEInstaller it would just say device not found.
HOWEVER; I started webOS doctor. I got to the screen where it says connect your device with a usb cable and stayed there - the next button was enabled so webosdoctor saw the touchpad. It still didn't mount, but I ran ACMEInstaller for the hell of it without going any further with webosdoctor and it just ran and completed.
Back up and running Alpha 2, whew! Hopefully this can help someone else if this happens to them.
Click to expand...
Click to collapse
This trick with webOS doctor just saved my ass. I couldn't boot past the green cyanogenmod splash screen and needed to boot straight off an image from moboot on my desktop, and taking webOS doctor to that step was the only thing that would let me run the command line entry to make it where my PC would talk to my touchpad. So, thank you

Would this work for a TP that reads both ways on PC as listed by OP but is only stock?

bone625 said:
AHHH, just got it to run ACMEInstaller on my original computer. For the hell of it I tried the last thing I could think of and it worked.
Click to expand...
Click to collapse
What do mean by run ACMEInstaller? I only know using the novacom boot mem:// <ACMEInstaller method, though that's getting stuck while on the two penguin screen.

Hp touchpad 32GB converted into Android 4.4.4.KitKat with ROM CM11
Hi My name is Ramadoss.N Recently I have converted my touch pad to Android KITKAT 4.4.4. with Rom CM11 -20140625- Snap Shot- jcsulline. I used TPtoolbox V41d to install. Everything working fine. except few observation.
1. Bottom Menu Button like Home , Return to previous screen are not working in vertical position of touchpad, where as it works in Horizontal position.
2. There are 3 dots on right hand side corner to provide dropdown menu: it works in vertical position, does not work in Horizontal position.
3. search icon ( which looks like a magnifying glass) does not work in both positions.
4.Back space key working in Vertical position, does not work in horizontal position.
5. Could not load Music via computer after installing Android in the Touchpad,
I really appreciate if any one can give me solution for above.
Regards
Ramadoss.N
email : [email protected]

[Q] Cannot Flash To Repair, Boot Loops and Deleted SD card

Greetings, developers and friends!
My Touchpad is now stuck in a continuous boot, with Android backed up in Clockworkmod but I tried restoring and didn't work. A couple of days ago I deleted info on my SD card because it was too bogged down and didn't let me update anything. I did my best but I decided to do this,so I own it. Attempted to flash with Roland's video instructions and got all my files in order: Problem is, on the command prompt I get a message of "Device Not Recognized.
Here's what I see when booting:
Moboot 0. 3. 8
HP logo
boot ClockworkMod
boot Cyanogenmod
boot WebOS
boot webOS Recovery
reboot
shutdown
Then the screen goes light dark, as if the animation of CyanogenMod is going to be up and running but it doesn't. Is there a remedy to fix the SD card problem, maybe that will take care of it and my laptop can see the TouchPad? Backup works fine on ClockworkMod, restore does too but nothing happens.
Any takers? I have another HP tablet that I will not mess with, but I'd rather have both running Android.
Thanks,
chicawhyte

chicawhyte said:
Greetings, developers and friends!
My Touchpad is now stuck in a continuous boot, with Android backed up in Clockworkmod but I tried restoring and didn't work. A couple of days ago I deleted info on my SD card because it was too bogged down and didn't let me update anything. I did my best but I decided to do this,so I own it. Attempted to flash with Roland's video instructions and got all my files in order: Problem is, on the command prompt I get a message of "Device Not Recognized.
Here's what I see when booting:
Moboot 0. 3. 8
HP logo
boot ClockworkMod
boot Cyanogenmod
boot WebOS
boot webOS Recovery
reboot
shutdown
Then the screen goes light dark, as if the animation of CyanogenMod is going to be up and running but it doesn't. Is there a remedy to fix the SD card problem, maybe that will take care of it and my laptop can see the TouchPad? Backup works fine on ClockworkMod, restore does too but nothing happens.
Any takers? I have another HP tablet that I will not mess with, but I'd rather have both running Android.
Thanks,
chicawhyte
Click to expand...
Click to collapse
UPDATE: Was able to get through the Android removal, but it bothers me that one of the scrolling messages says, "no cminstall dir found, nothing to install.

chicawhyte said:
UPDATE: Was able to get through the Android removal, but it bothers me that one of the scrolling messages says, "no cminstall dir found, nothing to install.
Click to expand...
Click to collapse
TouchPad toolbox will solve it.

Moody66 said:
TouchPad toolbox will solve it.
Click to expand...
Click to collapse
Where is the Toolbox? Looked in Preware, Just Type and everywhere else and I can't find it. Thanks.

Found it on another thread, printed it out. Will take care of this after work. Thanks.
chicawhyte

chicawhyte said:
Found it on another thread, printed it out. Will take care of this after work. Thanks.
chicawhyte
Click to expand...
Click to collapse
It didn't work....aborted.... :crying:

It didn't, it aborted. I tried Roland's way and attempted to flash it but still the message is the same, no cminstall dir, power off when ready. Let me see if I can get a hold of him or JC (it'd be incredibly lucky for me) I hope my tablet can get the Android back.

Roland asked me about this, this is my reply. Feel free to help out.
chicawhyte said:
It didn't, it aborted. I tried Roland's way and attempted to flash it but still the message is the same, no cminstall dir, power off when ready. Let me see if I can get a hold of him or JC (it'd be incredibly lucky for me) I hope my tablet can get the Android back.
Click to expand...
Click to collapse
+Roland Deschain Ok Roland, what I have tried was to gain more memory on my tablet; there were several apps deleted, cached space, did all I could because I had an update via Goo.im. I tried to flash it but I was not successful; asides from that, there were automatic updates that the Touchpad did not allow due to low storage space.That is when I made the serious mistake of deleting the SD card.
I tried to uninstall according to your instructions and then load up the 5M to go back to full throttle, but for whatever reason when the scroll happened the messages were off-key, meaning that folders and files were not installed and not the usual way. That's when I realized there was trouble; I had made two Nandroid backups that are still in the Touchpad. I had only WebOS and no Android to be seen. I restored the most recent backup via ROM Manager and I thought that that would do the trick, still no Android (?).
I decided to try and reach out to my fellows at XDA-Developers because I try everything before I go to the forum; I know the rules there. That's when I was made aware of the Toolbox by JC Sullins and I downloaded it. Followed the instructions hoping to install Android that way but it didn't go past 3 seconds of Step 1. That's when I get the message(s) that there's nothing to install and cuts off.
I am aware of a way to format the SD card (if that is the problem) but for that stuff I need specific instructions, like here, to do so. I have another TouchPad 32 GB that I performed a double-boot as you instructed us to do; what I need is some specific cause(s) and what to do because the idea of wiping everything including WebOS, using WebOS Doctor to reinstall it and then Android does not appeal to me. I want to get to the bottom of it, I like to figure this stuff out and do it myself
Thanks for your work and for helping us turn a good tablet into the best tablet around!

Greetings,
Please read below my message to Roland and my problem below/wanted to add that now on both computers (my laptop where I do the flashes) and my husband's where I copied the Palm, Inc. folder to attempt Android there-the message I get is that "there is no hardware found" on the command prompt.

Please try to follow the instructions and explain things when requested
chicawhyte said:
Hello Roland, help!!!!! Please read this thread and let me know if I have to wipe everything and restart from scratch with WebOS Doctor. Here's the thread from xda-developers: http://forum.xda-developers.com/hp-...r-boot-loops-deleted-sd-t2803190/post53886856. Runs WebOS fine, but no Android to be seen; files are there but it won't let me format the whole tablet. Thanks!
Click to expand...
Click to collapse
RolandDeschain79 said:
"Hey so I took a look but that just tells me you're confused and trying to follow multiple sets of instructions. Can you list what you've tried and where you get stuck. There's no cminstall folder in this set of instructions its a ttinstall folder. Did you complete the first steps of uninstalling android and wiping the USB drive?"
Click to expand...
Click to collapse
chicawhyte said:
+Roland Deschain Ok Roland, what I have tried was to gain more memory on my tablet; there were several apps deleted, cached space, did all I could because I had an update via Goo.im. I tried to flash it but I was not successful; asides from that, there were automatic updates that the Touchpad did not allow due to low storage space.That is when I made the serious mistake of deleting the SD card.
I tried to uninstall according to your instructions and then load up the 5M to go back to full throttle, but for whatever reason when the scroll happened the messages were off-key, meaning that folders and files were not installed and not the usual way. That's when I realized there was trouble; I had made two Nandroid backups that are still in the Touchpad. I had only WebOS and no Android to be seen. I restored the most recent backup via ROM Manager and I thought that that would do the trick, still no Android (?).
I decided to try and reach out to my fellows at XDA-Developers because I try everything before I go to the forum; I know the rules there. That's when I was made aware of the Toolbox by JC Sullins and I downloaded it. Followed the instructions hoping to install Android that way but it didn't go past 3 seconds of Step 1. That's when I get the message(s) that there's nothing to install and cuts off.
I am aware of a way to format the SD card (if that is the problem) but for that stuff I need specific instructions, like here, to do so. I have another TouchPad 32 GB that I performed a double-boot as you instructed us to do; what I need is some specific cause(s) and what to do because the idea of wiping everything including WebOS, using WebOS Doctor to reinstall it and then Android does not appeal to me. I want to get to the bottom of it, I like to figure this stuff out and do it myself
Thanks for your work and for helping us turn a good tablet into the best tablet around!
Click to expand...
Click to collapse
Please try and limit your conversation to one location. People who spam my YouTube channel and the forum with the same questions tend to get permanently banned without warning. Consider this a warning.
chicawhyte said:
......That is when I made the serious mistake of deleting the SD card.
.......I am aware of a way to format the SD card (if that is the problem) but for that stuff I need specific instructions, like here, to do so. I have another TouchPad 32 GB that I performed a double-boot as you instructed us to do; what I need is some specific cause(s) and what to do because the idea of wiping everything including WebOS, using WebOS Doctor to reinstall it and then Android does not appeal to me. I want to get to the bottom of it, I like to figure this stuff out and do it myself
Click to expand...
Click to collapse
Secondly if I ask you a question try to answer it as completely as possible. Don't tell me you made a mistake by wiping the SDcard then refuse to tell me how you did this even after I asked specifically about it. Claiming that you know how to wipe the SDcard then asking for specific instructions how to do so doesn't give me confidence in your ability. If you wiped the SDcard from a windows PC then you've made your own problem and completely ignored all the available instructions.
chicawhyte said:
. Followed the instructions hoping to install Android that way but it didn't go past 3 seconds of Step 1. That's when I get the message(s) that there's nothing to install and cuts off.
Click to expand...
Click to collapse
I'm having a very hard time understanding why you say you're stuck on step 1, which is installing novacom and backing up your data, when you're talking about step 5 installing android???
Step by step instructions have been provided and I even made a long video that reads you all the info. No one can help you to follow instructions that's up to you. Saying you didn't want to follow the instructions then asking for help is just silly. If you do not wish to change the layout of your touchpad just stick to the Non data media roms.
New Super Easy Way Guide and video available
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"(DM & Non-DM)

Four Block Colored Design Freeze When Going Into USB Mode or WebOS Recovery

I did a search and did not find anything so here it goes. I am running KitKat on my HP Touchpad with no issues. However, I was going to try and load the new MM build. When I try to go into the usb mode by either rebooting and selecting webos recovery or by pressing the vol key and power button while it is rebooting, I do not get the usb symbol, but instead I get 4 designs that appear identical except for shades of color. It freezes in that state (or at least a couple of minutes). To get out of it I do the pwr and press menu 15 times to reset. I am used to using the toolbox, but can't get to it this way. Is there a way to get back to the usb from here? PS. Detailed steps are preferred if possible.

You could load TPToolbox onto the /boot partition so you don't need to use pc and webos recovery?
Peace.

chris5s said:
You could load TPToolbox onto the /boot partition so you don't need to use pc and webos recovery?
Peace.
Click to expand...
Click to collapse
Thanks, but I'm not sure which files to place where. I can still get pc access via twrp 2.8.3, but I have wiped the tp of an OS so I'm really messed up.

golfnut22 said:
Thanks, but I'm not sure which files to place where. I can still get pc access via twrp 2.8.3, but I have wiped the tp of an OS so I'm really messed up.
Click to expand...
Click to collapse
So you still have moboot and can boot in recovery?
And can you access the TP using adb?
If you can mount the sdcard thru twrp, can you not copy the files over from the pc to install an os , prob kitkat at this stage?
Otherwise use adb to push the files over, eg using these commands:
adb push /sdcard/name.of.kitkat.rom
adb push /sdcard/name.of.gapps.file
All done whilst in recovery, then use twrp to flash the rom.
Once kitkat reinstalled, use a rooted file manager, eg ES File Explorer to get TPToolbox into the boot folder.
If you manage to get kitkat up and running I'll detail the next steps.
You could circumvent all this by deleting webos from /boot and pushing TPToolbox all using adb but i dont feel confident telling you how to do that, so the 'longwinded' way may be better!
Peace

chris5s said:
So you still have moboot and can boot in recovery?
And can you access the TP using adb?
If you can mount the sdcard thru twrp, can you not copy the files over from the pc to install an os , prob kitkat at this stage?
Otherwise use adb to push the files over, eg using these commands:
adb push /sdcard/name.of.kitkat.rom
adb push /sdcard/name.of.gapps.file
All done whilst in recovery, then use twrp to flash the rom.
Once kitkat reinstalled, use a rooted file manager, eg ES File Explorer to get TPToolbox into the boot folder.
If you manage to get kitkat up and running I'll detail the next steps.
You could circumvent all this by deleting webos from /boot and pushing TPToolbox all using adb but i dont feel confident telling you how to do that, so the 'longwinded' way may be better!
Peace
Click to expand...
Click to collapse
Thanks Chris. I am able to get into moboot. I just now mounted the TP, created a folder called ttinstall (which is what the tptoolbox always used), copied my kitkat rom and gapps into that folder, unmounted the tp, then from twrp ran install for the rom first then the gapp and it all worked. I still may try your way to get to the toolbox, but at least now it is working again. I have had several of these over the years and this is the only one that gives me a weird pattern on the tp when I want to go into recovery. Thanks for the response.

golfnut22 said:
Thanks Chris. I am able to get into moboot. I just now mounted the TP, created a folder called ttinstall (which is what the tptoolbox always used), copied my kitkat rom and gapps into that folder, unmounted the tp, then from twrp ran install for the rom first then the gapp and it all worked. I still may try your way to get to the toolbox, but at least now it is working again. I have had several of these over the years and this is the only one that gives me a weird pattern on the tp when I want to go into recovery. Thanks for the response.
Click to expand...
Click to collapse
The four block weird design or pattern apparently was just substitue picture of the usb symbol as far as I can tell. I was thinking because I did not see the usb symbol, it was not going into recovery, however, the tptoolbox loaded anyways and I was able to perform the changes to ttinstall folder as ususal. I'm not sure why I get that weird pattern instead of the usb symbol, but nervertheless, it worked. I may try MM now.

golfnut22 said:
The four block weird design or pattern apparently was just substitue picture of the usb symbol as far as I can tell. I was thinking because I did not see the usb symbol, it was not going into recovery, however, the tptoolbox loaded anyways and I was able to perform the changes to ttinstall folder as ususal. I'm not sure why I get that weird pattern instead of the usb symbol, but nervertheless, it worked. I may try MM now.
Click to expand...
Click to collapse
Cool! Running flintman's MM build right now, well worth a punt!
Peace.

Cannot install novacom on Win 7

I am having trouble with this.
I have tried the universal installer which correctly identifies it as 64bit system. But it fails at download stage, I guess because the file is no longer available where the installer is expecting it.
So then I tried running "NovacomInstaller_x64.msi" by double clicking it, which installs novacomd in my add/remove programs so it seemed to work. But when I run "tptb_v42_win.bat" it says
Code:
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
unable to find device
.
Cannot connect to Touchpad.
Make sure Touchpad is connected with USB cable.
Make sure Touchpad is in webOS Recovery (bootie) mode
(where big USB symbol shows on Touchpad screen)
.
Press any key to continue . . .
The touchpad is definitely on the Web OS recovery screen and connected via USD so I assume it must be to do with drivers not installing properly. Any advice on how I can check drivers?
thanks,
James

jamesking420 said:
I am having trouble with this.
I have tried the universal installer which correctly identifies it as 64bit system. But it fails at download stage, I guess because the file is no longer available where the installer is expecting it.
So then I tried running "NovacomInstaller_x64.msi" by double clicking it, which installs novacomd in my add/remove programs so it seemed to work. But when I run "tptb_v42_win.bat" it says
Code:
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
unable to find device
.
Cannot connect to Touchpad.
Make sure Touchpad is connected with USB cable.
Make sure Touchpad is in webOS Recovery (bootie) mode
(where big USB symbol shows on Touchpad screen)
.
Press any key to continue . . .
The touchpad is definitely on the Web OS recovery screen and connected via USD so I assume it must be to do with drivers not installing properly. Any advice on how I can check drivers?
thanks,
James
Click to expand...
Click to collapse
You can following this thread ( I have you start at post 405 ) where another user called @smithylovestouchpad had the same issue with novacom not connecting to the server, and he was able to use a backup PC and it worked....
https://forum.xda-developers.com/showpost.php?p=80016590&postcount=405
But that being said, your in luck James, because a "regular user" by his own admission, @HP_TOUCHPAD will be posting very soon what he likes to call "HP_Touchpad_Novacom_Recovery_Android", and with this, any user can perform the following tasks with one click on any computer:
1) Load the ToolBox (flash the A6 Firmware)
2) Fix /boot using Create_Boot ( If the Bermuda Triangle shows up ) or the Tablet can not boot.
3) Automatic_Wipe_All_and_Create_Android_with_Swap ( Total Data Reset )
4) If the Tablet needs to be set up only for Android.
5) Change the Ramdisk, make all setting modifications and create a Custom boot file.
HP_TOUCHPAD once said,
If the user ever needs help, the tablet can be setup "completely" by another user, even remotely running Automatic_Wipe to Android, all they need is an internet connection.
The Novacom Driver and Android ADB Shell will be permanent and fully working all the time regardless of the PC being used.

DoubleStuff said:
You can following this thread ( I have you start at post 405 ) where another user called @smithylovestouchpad had the same issue with novacom not connecting to the server, and he was able to use a backup PC and it worked....
https://forum.xda-developers.com/showpost.php?p=80016590&postcount=405
But that being said, your in luck James, because a "regular user" by his own admission, @HP_TOUCHPAD will be posting very soon what he likes to call "HP_Touchpad_Novacom_Recovery_Android", and with this, any user can perform the following tasks with one click on any computer:
1) Load the ToolBox (flash the A6 Firmware)
2) Fix /boot using Create_Boot ( If the Bermuda Triangle shows up ) or the Tablet can not boot.
3) Automatic_Wipe_All_and_Create_Android_with_Swap ( Total Data Reset )
4) If the Tablet needs to be set up only for Android.
5) Change the Ramdisk, make all setting modifications and create a Custom boot file.
HP_TOUCHPAD once said,
If the user ever needs help, the tablet can be setup "completely" by another user, even remotely running Automatic_Wipe to Android, all they need is an internet connection.
The Novacom Driver and Android ADB Shell will be permanent and fully working all the time regardless of the PC being used.
Click to expand...
Click to collapse
Thank you for your help. In the end a combination of installing and reinstalling novacom, restarting, and then plugging in the touchpad to a different USB port finally sorted it out! Then I used your tool to get a ROM etc on there.
Do you have any particular recommendation for a smooth ROM? Doesn't have to be latest version of Android, just something that runs super snooth!
I've installed Dirty Unicrorn Pi but it's a bit laggy. It'll be fine to use fit it's intended purpose, but anything that improves on this would be appreciated.
Cheers,
James

jamesking420 said:
Thank you for your help. In the end a combination of installing and reinstalling novacom, restarting, and then plugging in the touchpad to a different USB port finally sorted it out! Then I used your tool to get a ROM etc on there.
Do you have any particular recommendation for a smooth ROM? Doesn't have to be latest version of Android, just something that runs super snooth!
I've installed Dirty Unicrorn Pi but it's a bit laggy. It'll be fine to use fit it's intended purpose, but anything that improves on this would be appreciated.
Cheers,
James
Click to expand...
Click to collapse
I am curious to what install process you have used to install the Dirty Unicorn Pie? Please respond, its nice to see what install processes some users are using....like what speed of Universal swap settings did you install?, did you use ROM reducer?
In the meantime since you have Novacom and TPTB installed try this process to install maybe Nougat, Oreo or Pie ( with /swap ) or KitKat or Lollipop. Once you read the OP it will direct you to the key Android versions to install on HP_TOUCHPAD's page.
I currently use KitKat and I am fine with that.
https://forum.xda-developers.com/hp...-guide-alternative-method-to-install-t3575861

Hi,
Thanks again for the advice.
I booted in to TPToolbox
Ran Complete Data Reset
Then rebooted to WebOS recovery.
Ran the ."TPTB_WipeAll_TWRP_v02_win.bat" which ended up with me in TWRP.
Then I installed ROM, reducer, gapps, optimiser, recovery, and super user via TWRP and it all raun when rebooted.
Now - another question - my second touchpad - It is currently sitting in the Touchpad toolbox screen. My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
I've already ran "Complete Data Reset" but wasn't able to run the "TPTB_WipeAll_TWRP_v02_win.bat" before my windows PC got Blue Screen of Death!
So now I can copy zips to my touchpad and potentially install android, gapps, recovery using the tool. Then I figured I'd go in to recovery and flash "Automatic_Wipe_All_and_Create_Android_with_Swap_Partition" and start again.
The problem I have is I cannot flash android/recovery/gapps with TP Toolbox as I need a set of three compatible files.. Can anyone point me to a set of such files? Or another way of doing this from TP Toolbox - remember - I can't currently run anything on a PC!
This wouldn't be desperately urgent if it weren't for the fact that my mum wants to use these devices as digital photoframes on Thursday (my grandads funeral!).
Any help would be appreciated.
Currently I have
du_tenderloin-v13.0-20190328-1316-RC.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip
I downloaded a zip from Open Gapps but TP Toolbox says its not compatible and will not flash.

jamesking420 said:
Hi,
Thanks again for the advice.
I booted in to TPToolbox
Ran Complete Data Reset
You don't have to do a Complete Data Reset anymore with the TPToolbox if your going to run TPTB_WireAll_TWRP_02_win.bat or flash Automatic_Wipe_All_and_Create_Android_with_Swap_Partition, it almost seems like your combining three different methods of installs, because TPTB_WipeAll_TWRP_v02_win.bat actually flashes Automatic_Wipe_All_and_Create_Android_with_Swap_Partition in the background and that actually does a complete data reset and creates a 500 Mb swap partition, and re-creates the system, cache, media and data partitions with sizes of 2200 Mb, 200 Mb, 500 Mb, and "rest of memory" respectively, also automatically installs version 3.2.1-0 of TWRP which is required for the other ZIPs.
Only use TPToolbox to flash A6 firmware, or look at partition sizes.
Then rebooted to WebOS recovery.
Ran the ."TPTB_WipeAll_TWRP_v02_win.bat" which ended up with me in TWRP.
Then I installed ROM, reducer, gapps, optimiser, recovery, and super user via TWRP and it all raun when rebooted.
Now - another question - my second touchpad - It is currently sitting in the Touchpad toolbox screen. My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
I've already ran "Complete Data Reset" but wasn't able to run the "TPTB_WipeAll_TWRP_v02_win.bat" before my windows PC got Blue Screen of Death!
So now I can copy zips to my touchpad and potentially install android, gapps, recovery using the tool. Then I figured I'd go in to recovery and flash "Automatic_Wipe_All_and_Create_Android_with_Swap_Partition" and start again.
How are you copying zips to your touchpad if your PC does not work? Once you
flashed Automatic_Wipe_All_and_Create_Android_with_Swap_Partition it should get you to a
TWRP Recovery install screen, and you can then flash your zips, no need to use TPToolbox as I said before. Essentially TPToolbox is an "old school" method now. And flashing from TWRP Recovery you don't need compatible zips, that is a bug of TP Toolbox that has not been fixed.
The problem I have is I cannot flash android/recovery/gapps with TP Toolbox as I need a set of three compatible files.. Can anyone point me to a set of such files? Or another way of doing this from TP Toolbox - remember - I can't currently run anything on a PC!
I am curious, even if we point you to a set of such files, how are you going to copy them from a broken PC?, and see above for another way of doing this than from TPToolbox, if you can get into TWRP recovery and have zips on your Touchpad your all set.
This wouldn't be desperately urgent if it weren't for the fact that my mum wants to use these devices as digital photoframes on Thursday (my grandads funeral!).
Any help would be appreciated.
Currently I have
du_tenderloin-v13.0-20190328-1316-RC.zip
FLINTMAN-TWRP-touch-data_media-SELINUX-2.8.3.0-12-23-14.zip
I downloaded a zip from Open Gapps but TP Toolbox says its not compatible and will not flash.
Your PIE version above is the latest version, good. But the TWRP 2.8.3 version above is "old school" we are currently at this version FLINTMAN-TWRP-3.2.1-0-03-15-2018, and like I said above the "Wipe All" methods automatically install this latest TWRP version, so no need to flash an "old school" TWRP's afterwords.
Click to expand...
Click to collapse
I made comments above in blue. Here is my summary.
Because your PC broke, like you said "blue screen of death, RAM corruption". This is the very reason that @HP_TOUCHPAD is thinking "outside the box" trying to create an environment that users will not be dependent on a PC anymore. He is in the process of creating this environment, but lets give him time. For by his own admission he is just a regular user, he is learning, experimenting, creating and testing. He is also documenting his findings for all of us to read, learn and apply. So let us do our due diligence and do the best we can.

I have a raspberry pi computer I can use that I can copy files to/from with but I cannot install novacom drivers on it as they are not compatible, as far as I'm aware.
I think I might have found a suitable grouping of ROM/gapps/recovery I can flash with tptoolbox - literally trying again now

jamesking420 said:
I have a raspberry pi computer I can use that I can copy files to/from with but I cannot install novacom drivers on it as they are not compatible, as far as I'm aware.
I think I might have found a suitable grouping of ROM/gapps/recovery I can flash with tptoolbox - literally trying again now
Click to expand...
Click to collapse
This appears to be working to install a KK ROM so I will see if it comes up and I can then run the various flashes.
PS - yes - I did think that running Complete Data Reset and the "TPTB_WipeAll_TWRP_v02_win" was probably unecessary but I'd already run Complete Data Reset before I realised that it probably was overkill. Since this process worked I decided to do it again on the second touchpad, but the Windows PC died before I got the chance. But I had already run the process to load TPToolbox on to the tablet. So I'm now flashing TWRP v2.8.3.0 (data media), a KK ROM, and some KK compatible GApps using TPToolbox.
I hope that after that I can use the recovery I have loaded to install a new ROM, Rom Reducer, SU, Optimiser, GApps, and a more recent Recovery.

jamesking420 said:
snip...
My PC has just broken (RAM corruption), I only have a Raspberry Pi which is not compatible with novacom drivers.
...snip
Click to expand...
Click to collapse
I learn something new everyday, I just googled Raspberry Pi and its some sort of tiny, dual-display, desktop computer. At first I thought it was some sort of "Rogue ROM", I guess we can always learn something new everyday, like last month I learned to play Run Race 3d and I am not even a gamer.
And yesterday I wrote a program in a UNIX language called "AWK"

Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!

jamesking420 said:
Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!
Click to expand...
Click to collapse
As per your comment recovery ( again?! ), only flash recovery if you want a different version than what the Wipe all zip flashes ( currently flashes TWRP 3.2.1 ), lets say in the future nobody is updating the Wipe all zip, and it still flashes TWRP 3.2.1, but you see a newer version of TWRP 4.1 compatible with the touchpad, then you can flash that at the tail end, or if your fond of an older version like TWPR 2.8, same thing.

Thanks - yes - I want sure if Wipe all Zip was flashing or just into TWRP so I flashed it again just to be on the safe side. Because it was called wioe ask I thought maybe it wasn't actually flashing anything new, just wiping and booting.
Anyway, thanks for your help it was very useful.

jamesking420 said:
Yep it worked - so I then was in recovery on the device and I ran the Wipe all zip and then I flashed ROM, Optimiser, Reducer, Gapps, SU, recovery (again?!) and now it looks like it is loading in to Dirty Unicorn Pi.
I will have a play with it on the the max MHz optimiser kernel and then see if I want to stick with this or move on to an older/less system intensive ROM.
Thank you for your help!
Click to expand...
Click to collapse
The HP Touchpad Novacom Repair Android guide:
Click HERE for the Guide and File
A live Linux CD, just boot it from any PC, no installation is need it and have full control of the Tablet for ever !

Thanks for posting this, I'm sure it will be useful for many people.
Unfortunately on the way home from the funeral I left the two touchpads on top of the car as I was putting my kids in their car seats. They feel off at a roundabout which I imagine caused some damage. We turned around and went back for then and someone has nicked them! Ah well!
At 8 years old and costing less than £100 each they'd had a good innings.
Sent from my ONEPLUS A5000 using Tapatalk

jamesking420 said:
Thanks for posting this, I'm sure it will be useful for many people.
Unfortunately on the way home from the funeral I left the two touchpads on top of the car as I was putting my kids in their car seats. They feel off at a roundabout which I imagine caused some damage. We turned around and went back for then and someone has nicked them! Ah well!
At 8 years old and costing less than £100 each they'd had a good innings.
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
That is very unfortunate, but there is nothing to worry. The Tablets can be found for $10 anywhere and you maybe surprise to find in a dumpster somewhere.
But it can be revive to its full working conditions and all the files are posted on here, it only takes a click and is done!