Hey, my buddy let me borrow his rooted NC running the Honeycomb Preview on it. He wanted to see what MIUI looked like on it, and let me put it on there for him. I guess I was dumb to assume this was running Android, so it must flash files like any android phone.
He has some program to boot the NC into clockwork mod recovery. While in CW recovery, I wiped data, but after this, it froze while in CW recovery! I've never encountered this, so I just decided to reboot the thing and go from there. It rebooted and directed me to the set-up screen with the green android dude with the persons hand telling me to press him
"Welcome to LogicPD Zoom 2"
No matter what I press, nothing responds. I read up on http://nookdevs.com/Flash_back_to_clean_stock_ROM#ixzz1AAsuy5td and tried to accomplish the 8 restart thing. I don't think I can complete that because whenever I boot up, it immediately puts on a splash screen that says "Loading.."
No part of the boot cycle does it say "Welcome to the future of reading"
Is it possible flashing this thing back to stock? I tried to tap into adb, so I could put it into bootloader from there, but my adb doesn't recognize it. Even with the "adbfix.bat" file.
Any help will help.
Thanks
First, load an image of CWR v3.2.0.1 on an SD card. Then, get a CM7 ROM and the market app .zip file and put them on the card and you should be good to go. Older versions of CWR tend to freeze up when wiping the cache....
In my opinion, no one should be running Honeycomb on the Nook unless off an SD card as a secondary "toy".
Well thanks for the suggestion. I couldn't boot into any kind of recovery mode, which made things kinda confusing.
I fixed my adb issue, so luckily, I could log into adb. I cleared data and cache through adb, and than downloaded the boot.img file and system.img file. Pushed those to the nook that way. Now I'm back to out of box status ready to put some MIUI goodness on here.
Ok guys, I really didn't want to start this thread but I couldn't find any real kind of answer. So I installed CM7 with moboot on my touchpad, after the installation, the touchpad rebooted and then skipped over the "touch the android" to finish loading cm7. Immediately afterwards I get an error that reads "sd card not mounted might be damaged please click ok to format". Do you any of you guys have any idea what's going on?
I've searched these forums/google and I can't seem to find a solution. So far I'd done a full secure erase from webos, format in recovery, novaterm touchpad type fcsk.vfat.... tried to flash other versions of cm7 after a webos doctor.
I'm still trying other options, but I wanted to pick the brains of the fine people here on this forum and see what you guys think.
Thanks a million!
Spazzvogel said:
Ok guys, I really didn't want to start this thread but I couldn't find any real kind of answer. So I installed CM7 with moboot on my touchpad, after the installation, the touchpad rebooted and then skipped over the "touch the android" to finish loading cm7. Immediately afterwards I get an error that reads "sd card not mounted might be damaged please click ok to format". Do you any of you guys have any idea what's going on?
I've searched these forums/google and I can't seem to find a solution. So far I'd done a full secure erase from webos, format in recovery, novaterm touchpad type fcsk.vfat.... tried to flash other versions of cm7 after a webos doctor.
I'm still trying other options, but I wanted to pick the brains of the fine people here on this forum and see what you guys think.
Thanks a million!
Click to expand...
Click to collapse
I have same exact problem. Bought used tablet last night with cm7. I'm confused about lack of support for cm7 on touchpad. I should have researched more before I bought it.
Hi folks,
I was using Cyanogenmod 9 before the nightly releases and have installed ubuntu. Well, yesterday i tried to reset it to a factory condition to reinstall just cm9 nightly along with WebOS.
I used the WebOS Doctor 3.0.0, and after it the TouchPad won't boot anymore, just stuck on HP Logo reset loop. So i have tried again with WebOS Doctor 3.0.5 and got the same...
Also, i have tried to reinstall directly moboot and these things with ACMEInstaller, but it claims anything about lvm not found. Now, i just can't do anything to touchpad. I can enter on USB mode (Pwr + VolUP), and connect with novaterm, but i dont know what to do.
Anyone can try to help me? I'll post more details if you tell me how to catch these.
What you need to do is use the info from THIS THREAD to help you reset. It'll erase and recreate all of the partitions on the TP and allow you to flash 3.0.0 properly (then you can flash 3.0.5 and then install CM9 again).
I just did it last night (again). It's the best guide I've found, anywhere.
Hi,
I saw this and did this but i missed to flash the Recovery uImage before i created this thread, a bad mistaken.
Thanks for help.
I am coming from OaT LnTJB 12/22 and upgraded to AcmeInstaller3 before flashing that ROM (as I came from CM9, although I didn't use AcmeUninstaller first) and also have moboot 3.8 and the latest TWRP and CWM.
However, when trying to flash the new CM10 build after doing a full wipe through recovery (i.e., System, Data, Cache) I keep coming up with the same errors, such as "damaged SD card" upon boot (even though I can browse the contents through file manager) and broken wallpaper (didn't dive too much into other errors after those, as I already knew something was amiss). Also, in trying to wipe cache/dalvik, upon reboot it gave me this weird screen where it usually would say "Android is upgrading..." and instead had some symbols (one was %) with a prompt that I can paraphrase as "touch to switch apps". Odd to say the least.
Any ideas as to what could be causing these errors? Should I just dirty flash over OaT (not my preference)? Any/all help is appreciated!
rg2 said:
I am coming from OaT LnTJB 12/22 and upgraded to AcmeInstaller3 before flashing that ROM (as I came from CM9, although I didn't use AcmeUninstaller first) and also have moboot 3.8 and the latest TWRP and CWM.
However, when trying to flash the new CM10 build after doing a full wipe through recovery (i.e., System, Data, Cache) I keep coming up with the same errors, such as "damaged SD card" upon boot (even though I can browse the contents through file manager) and broken wallpaper (didn't dive too much into other errors after those, as I already knew something was amiss). Also, in trying to wipe cache/dalvik, upon reboot it gave me this weird screen where it usually would say "Android is upgrading..." and instead had some symbols (one was %) with a prompt that I can paraphrase as "touch to switch apps". Odd to say the least.
Any ideas as to what could be causing these errors? Should I just dirty flash over OaT (not my preference)? Any/all help is appreciated!
Click to expand...
Click to collapse
I would run acmeuninstaller, then go through the cminstall and acmeinstaller3 thing.
Good luck.
Edit: make a backup, just in case. Use cwm, there's been cases where twrp has caused problems.
You say you have two both TWRP and CWM which one did you use? It's also probably one to many as the maximum size for the boot folder is 32mb which you are probably quite close to.
chicle_11 said:
I would run acmeuninstaller, then go through the cminstall and acmeinstaller3 thing.
Good luck.
Edit: make a backup, just in case. Use cwm, there's been cases where twrp has caused problems.
Click to expand...
Click to collapse
Thanks for the advice. Going to have to do this I guess.
sstar said:
You say you have two both TWRP and CWM which one did you use? It's also probably one to many as the maximum size for the boot folder is 32mb which you are probably quite close to.
Click to expand...
Click to collapse
I used them both, although I generally use TWRP. I got rid of CWM and tried again to no avail. Thanks for the reply.
Running ACMEuninstall and reinstalling did nothing to fix the problem. Still have "damaged SD card" prompt upon boot, still have broken wallpaper functionality as well as crippled launcher functionality. Any ideas?
How is webOS running? If you get problems in that also then I would run acmeuninstaller and then run remove android from preware followed by webos doctor 3.00 then 3.0.5 if you want to actually use it.
sstar said:
How is webOS running? If you get problems in that also then I would run acmeuninstaller and then run remove android from preware followed by webos doctor 3.00 then 3.0.5 if you want to actually use it.
Click to expand...
Click to collapse
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
reset webos
rg2 said:
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
Click to expand...
Click to collapse
I was having trouble installing cm9 when I bought my touchpad. Got an error that said drive needed to be formatted when connected to my pc. I did a reset in webos and it fixed the problems. Try that.
rg2 said:
No issues with WebOS; trying WebOS doctor right now then going to try and reinstall android, hope it works. If not I will try your suggestion. Thanks for the info!
**EDIT** Tried WebOS doctor, but it stuck at 72% and I had to pull the plug; now my TP won't boot at all. Because of course it won't. Device may be bricked
**EDIT2** Okay just rescued my TP using jcsullins de-bricking tool via Linux. Now I am back in WebOS. If I may ask, what should be my next step? My SD storage is intact so I know my device wasn't completely wiped, which to me means that I might run into the same problems installing CM10, and I would obviously like to avoid that. I would like to do a full wipe but seeing as how WebOS doctor ended disastrously I am a little skittish about my next move. Once again, any/all help is appreciated. Thanks!
Click to expand...
Click to collapse
Did you use webOS doctor 3.00?
Sent from my cm_tenderloin using Tapatalk 2
johna2u said:
I was having trouble installing cm9 when I bought my touchpad. Got an error that said drive needed to be formatted when connected to my pc. I did a reset in webos and it fixed the problems. Try that.
Click to expand...
Click to collapse
Thanks for the tip. Will have to try this.
sstar said:
Did you use webOS doctor 3.00?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
No did 3.0.5. Gonna try 3.00. Thanks again for all the help!
**EDIT** After downgrading to 3.00 via WebOS Doctor and doing a Secure Full Wipe through WebOS, I was able to install the new JCSullins CM10 build w/o issues! Thanks again to all for the help
rg2 said:
Thanks for the tip. Will have to try this.
No did 3.0.5. Gonna try 3.00. Thanks again for all the help!
**EDIT** After downgrading to 3.00 via WebOS Doctor and doing a Secure Full Wipe through WebOS, I was able to install the new JCSullins CM10 build w/o issues! Thanks again to all for the help
Click to expand...
Click to collapse
Glad you have sorted it I'm using this Rom http://goo.im/devs/SGA/CM10/CM10_UnOfficial_Mar0813.zip with http://goo.im/gapps/gapps-jb-20121011-signed.zip and extremely happy with it.
If you are going to try it do a system,/factory wipe and then flash with your recovery.
I'm assuming you originally used acmeuninstaller 3
sstar said:
Glad you have sorted it I'm using this Rom http://goo.im/devs/SGA/CM10/CM10_UnOfficial_Mar0813.zip with http://goo.im/gapps/gapps-jb-20121011-signed.zip and extremely happy with it.
If you are going to try it do a system,/factory wipe and then flash with your recovery.
I'm assuming you originally used acmeuninstaller 3
Click to expand...
Click to collapse
Thank you for the suggestion! I will try this since I seem to be cursed using the JCSullins build :/
Hey guys!
I recently resized the partitions of my touchpad via the recommended cwm zips, in order to install latest 4.3.1.
Everything worked as expected.
After experiencing quite high battery drain I decided to reflash the A6 firmware, as I already did several times.
When I try to boot up WebOS, I'm stuck in a bootloop. The HP sign is flashing/blinking but it never boots up!
Seems the resizing deleted an important file or similar.
Is there any safe possibility to workaround this? Android is working normal, when I connect to a PC I can only see the MTP Media device, no other partitions.
Should I use WebOS doctor?
Hope somebody has a helpful idea.
Thank you in advance.
spica123 said:
Hey guys!
I recently resized the partitions of my touchpad via the recommended cwm zips, in order to install latest 4.3.1.
Everything worked as expected.
After experiencing quite high battery drain I decided to reflash the A6 firmware, as I already did several times.
When I try to boot up WebOS, I'm stuck in a bootloop. The HP sign is flashing/blinking but it never boots up!
Seems the resizing deleted an important file or similar.
Is there any safe possibility to workaround this? Android is working normal, when I connect to a PC I can only see the MTP Media device, no other partitions.
Should I use WebOS doctor?
Hope somebody has a helpful idea.
Thank you in advance.
Click to expand...
Click to collapse
EDIT: Okay. at least acmeuninstaller brought webos back to life.