I looked and I found no posts related to this so im sorry if its already been asked/answered.
I was very excited when i found JCsullins's tp toolbox and his great work on new roms and such. I deciede that i wanted to upgrade from my 4.2.2 milaq build to JCsullins's 4.4.4 and give TP toolbox a try at the same time. I have flashed my device plenty of times so I'm familiar with the process and I jumped in (after reading the instructions on the tp toolbox ofcourse) and tried to boot it. It boots fine and looks easy to use and intuitive.........except all i can do is look After the tp toolbox booting completes, it is stuck on the "About TPToolbox" option and my vol up/down and home buttons do nothing. I can blank and unblank the screen but nothing else. I do have novacom properly installed and am running the boot script on windows as local admin. Any thoughts? Thanks.
EDIT: I tried it on a different machine and got the same result. Both have 8.1_U1 so i'll try a win7 machine next. In both cases, i used the "universal novacom installer" from google code. Maybe i should hunt down the other one? I couldn't find it before.
EDIT2: Version 41 works fine
tptoolbox frozen
einstein910 said:
I looked and I found no posts related to this so im sorry if its already been asked/answered.
I was very excited when i found JCsullins's tp toolbox and his great work on new roms and such. I deciede that i wanted to upgrade from my 4.2.2 milaq build to JCsullins's 4.4.4 and give TP toolbox a try at the same time. I have flashed my device plenty of times so I'm familiar with the process and I jumped in (after reading the instructions on the tp toolbox ofcourse) and tried to boot it. It boots fine and looks easy to use and intuitive.........except all i can do is look After the tp toolbox booting completes, it is stuck on the "About TPToolbox" option and my vol up/down and home buttons do nothing. I can blank and unblank the screen but nothing else. I do have novacom properly installed and am running the boot script on windows as local admin. Any thoughts? Thanks.
EDIT: I tried it on a different machine and got the same result. Both have 8.1_U1 so i'll try a win7 machine next. In both cases, i used the "universal novacom installer" from google code. Maybe i should hunt down the other one? I couldn't find it before.
EDIT2: Version 41 works fine
Click to expand...
Click to collapse
Hi, I'm having this same problem as well with version 40. Can you tell me how to reset my touchpad back into webos recovery so I can try again with version 41? As of right now I ran version 40 and it froze in the same manner and I can't get it to reboot or do anything except blank and unblank the screen. Thanks in advance.
Related
I've had my NC rooted for 3 weeks. No probs. I decided to update to 1.0.1 to see if wifi was better and so I entered the adb command to force system update and all seemed to be well. After that it went into a boot loop.
I forced another "update" by powering down 8x during bootup. It reinstalled and then same problem. I then tried the directions at nookdevs to fix boot loops. I couldn't ssh into the NC, but to my surprise I could use adb, but I can't do the listed commands because I get "permission denied".
I did an adb logcat and I get nonstop info going by, mostly looking for stuff that shouldn't be there anymore, i.e. apps I loaded when it was rooted. Dalvik cache??
So, long story short, I've tried a system wipe 4x now and I'm stuck in an endless boot loop BUT I do have adb access. What now?
Power, +, N button doesn't work either?
norkoastal said:
Power, +, N button doesn't work either?
Click to expand...
Click to collapse
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
GTOMEX09 said:
Haha. Good call. That did work. Bigtime brain fart. Trying all the hard stuff and not the easiest. What's the diff between the two methods?
Click to expand...
Click to collapse
Head over to Nook Devs for the breakdown of the two.. Both methods are requied for using the newest AutoNooter... Glad to hear the device is still in working order.
Stuck in Boot Loop
Noob here with a problem. I’ve had my NC rooted for 5 days and the rooting went well. I had all my favorite android apps up and running. However I was experiencing random reboots (2-3 times per day). So, I decided to unroot and let the 1.0.1 update install and then I was going to use Auto-Nooter 2.12.18 to get everything back.
I did the 8X reboot thing and after reloaded, the NC went into a boot loop. The first thing I tried to do was the n, volume+ and power button. It simply went back to the boot loop.
I immediately put the auto-nooter sdcard in the NC, plugged in the usb to the pc. As opposed to the other times I did this, I got no visual indication that the PC recognized or activated the NC. I waited the full 5 minutes and removed it. The boot animation had changed, but the NC stayed in the boot loop.
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
Before I ejected the NC I opened the command line window and I did adb devices and it came back with nothing. So now my NC is not recognized by the PC (and was before all this).
Can anyone point me in the right direction? Any help with the putty ssh screen issue? Any help will be appreciated.
Geezer Squid said:
I then searched and found this on nookdev.com (nookdevs.com/NookColor_Fix_Boot_Loops ). Following the instructions there, I installed putty.exe in the same folder as adb.exe. Putty would start and the session window would open, but I could not type or paste anything into the ssh screen. I assumed I had a bad download so I redid that and the install – no luck. I then searched and found another site from which I could download putty.exe, same results.
.
Click to expand...
Click to collapse
Out of desperation I downloaded putty.exe again and it worked this time. Using the script on the nookdev.com website, the NC booted. I then did the data wipe and the 8X reset. I'm now back to stock (mostly) and I'll see if it updates tonight. If not, I'll force it tomorrow and don the new auto-nooter.
I'm learning!!
Glad you fixed yours too. This device is nearly impossible to brick unless you deliberately try to. Definitely easy to undo hard work, but hard to brick.
I have the same problem. Minutes after rooting with autonooter, my Nook restarted and I didn't even set up ADB access. I tried reseting several times with no luck Please help!!
Mine is currently stuck in a boot loop as well. I did not update to the newer firmware it auto-updated and jacked everything up. Pretty upset right now.
I know I can reset the device but I need to get the data from it first. I have the entire storage full of data that I need. It will not boot at all and if this gets erased i'll more than likely end up returning the device and purchasing something that I won't have this problem with every update.
Unfortunately, there aren't many devices that will automatically backup all your important data to external media without you having to take some action on your own to set that up.
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
Well, I'm not an expert, but I have been through this kind of thing. I would think you have two possibilities. One would be to put the nooter sdcard back in and hook it to the computer again. If it isn't very corrupted, it may automatically reload from the nooter sdcard.
If that won't work, then I think it's time to do the 3 finger data wipe and then the 8X reboot thing. You can then redo the nooter sdcard thing.
Good luck.
Mbside said:
hey guys i'm noob here yesterday i rooted my nook color and everything was going fine until i turned it off when i tried to turn this again i couldn't so i took the sdcard off and tried again it powered but now i'm stuck in the grey 'N' screen, any idea on how can i fix this?
Click to expand...
Click to collapse
EXACT Same thing happened to me and a friend when using autonooter and 1.0.1. I think there is a problem with autonooter or 1.0.1 messing up the booting process. I wonder whats wrong So I was able to do the 8X reboot thing and get back to stock 1.0.0 and from here I'll try to attempt to use autonooter for 1.0.1. But I'm staying with 1.0.0 until Froyo next month.
thanks! the 8x thing worked good, I did the whole auto noot process again and it works at all except by this market issue
I purchased a nook color the other day and successfully rooted and used it for a few days. My youtube would not open so I reinstalled, it ran once and then failed to open again so I gave up on that issue. In reading about youtube app I found that you could get the new market app. I could not get it to install...and in trying multiple things I accidentally deleted my original market app.
I could not get it back so I whiped my nook color and reflashed autonooter. I got all my apps back but I get a connection error when trying to access the market now. I added my account via youtube which again opened once to allow me to sign in and now fails to open.
So I decided to try to reset it back to the way it was out of the box and start from scratch.
I tried the adb 8x reboot method.....it just reboots the nook as it normally would. No bootloader or install screen.
I tried the button method. It works once or twice then it goes through the entire boot. I did it for a half hour and used counts to verify I was doing the process correctly and no matter what I did I could get it to fail boot once and one the second or third it would always bypass and go through with boot even with my finger on the button.
I also am running windows 7 64bit and I cannot get my computer to see "nook" in the device manager for more than a second and it auto installs as a storage device. I've tried to "uninstall" the different devices and last night I was able to catch the "nook" in time to install usb drivers manually but when I reset the nook today my PC no longer see's it again. I was wondering if there is an easier way to install the adb device.
Thanks
UPDATE: Somehow the ADB way to reflash worked the second time I tried it. I also changed some settings in the development menu to fix the device manager issue. I'll update again if I can use youtube and the market.
I don't know what to tell you about everything else but for ADB I would highly recommend adbWireless... it works great on my NC and I never had to install any drivers.
To reset I used the button and counted slow to 15 after the screen gose off each time it worked for me. Good luck
Hi guys i been searching everywhere, all over forums and google and i cant seem to figure out this issue, the issue is that i have a demo version of a 32gb touchpad, and basically i followed all the steps to install clockworkmod and moboot and all that stuff, once all that was completed i choose to install an android rom from the development section, and no matter what i do in clockworkmod, it just keeps restarting, it begins installing a rom and then just automatically restarts. it does that when i wipe cache aswell, i redid the entire process again and i get the same issue, everytime i try to install a rom or do a gaaps update it just restarts and nothing gets installed, Please let me know how to fix this issue
Sounds like you need to completely restart fresh. It could be because of the Demo setup of the TP, it doens't wanna allow CWM to work properly.
What I would do is read THIS THREAD and follow the instructions - it'll factory reset everything, but it'll then be ready for you to install CWM, Moboot, and CM9 again. I know it works cuz I just did it last night.
thanks alot buddy, it WORKED!!!!! now my touchpad finally has android, and webos, oh man android is amazing, my kid luvs it
Hey guys,
Hope someone knows anything about the issue I'm experiencing. I downloaded all the files for the install from liliputing ([h t t p : / / liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html)
I installed the files as the website says, but I believe the wire from my laptop to the touchpad became loose very deep into the install. At which time the touchpad went black, rebooted and showed the menu for booting into webOS or android. When I let it load android the little android baby face comes up for 5-10 seconds, then restarts back to the boot menu.
This was tried with the latest update with bluetooth experimentally working 4.2.2. I also tried the older update from 12/12/2012 with audio and video working.
Does anybody know best solution? Factory reset my touchpad and try from scratch? Wasn't sure if its novacom on my desktop messing up. Should I uninstall and reinstall?
Any help is appreciated!!! Thanks!!
em11488 said:
Hey guys,
Hope someone knows anything about the issue I'm experiencing. I downloaded all the files for the install from liliputing ([h t t p : / / liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html)
I installed the files as the website says, but I believe the wire from my laptop to the touchpad became loose very deep into the install. At which time the touchpad went black, rebooted and showed the menu for booting into webOS or android. When I let it load android the little android baby face comes up for 5-10 seconds, then restarts back to the boot menu.
This was tried with the latest update with bluetooth experimentally working 4.2.2. I also tried the older update from 12/12/2012 with audio and video working.
Does anybody know best solution? Factory reset my touchpad and try from scratch? Wasn't sure if its novacom on my desktop messing up. Should I uninstall and reinstall?
Any help is appreciated!!! Thanks!!
Click to expand...
Click to collapse
First off you did it wrong! that's a guide to run cm9 not cm10 just like how you ran acmeinstaller you have to run acmeuninstaller. if you don't have that then you need to download it and place it into the palm, inc folder that you have acmeinstaller in. Then go back step by step you have to download cm9 first! load cm9 then after cm9 is installed boot back to webos open cminstall folder drag and drop Android 4.2.2 with the correct gapps Idk which android 4.2.2 your running but I'm guessing cm10? Then boot back into moboot, toggle to clockwork mod then toggle to install zip from folder then toggle to cminstall then open android 4.2.2 zip after that install gapps and then restart then voila android 4.2.2 hit the thanks button
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
josh426 said:
So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
Click to expand...
Click to collapse
I have heard no reports of what you describe.
I suggest using TPToolbox v41 from here (download link in that post):
http://forum.xda-developers.com/showpost.php?p=54986968&postcount=293
and try again.
If it does it again, I will need to see a kernel log file to help diagnose what's happening.
To get that, following the instructions on this post:
http://forum.xda-developers.com/showpost.php?p=53258228&postcount=10
but replace steps 1-3 with:
1) Load Touchpad Toolbox
2) Start holding the Volume Up button
3) Continue to hold VolUP until you see the big USB symbol (i.e. webOS recovery)
Errgghh
Downloaded but not sure what is going on. I think the problem my be with something being overwritten during one of the first attempts. With the USB logo displayed, I connect it to the PC. The minute it starts to transfer, it resets and I see the hp logo and then the boot screen. At this point it is stuck in a rebooting loop for several times. I even just tried webos doctor and it starts at 1% and as soon as it hits 2% it reboots the same way.
Also will not mount as a USB drive on the PC. Just as a palm noobie or something so I can not access anything on the device manually.
While I have not experience your issue I have had other issues that were resolved by changing to a different USB cable. Might be worth a try.
Sent from my MT2L03 using Tapatalk 2
Having the same issue. From USB to HP logo, then 1.5 seconds of text and then reboot. Tried V41 and V42 and tried multiple USB cables.