Related
editi guess sdcard is incorrect/confusing for my situation, it's the entire system up to root folders is stuck in a read-only type state.
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected]ost #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
plasticsoldier said:
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected] #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
Click to expand...
Click to collapse
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
plasticsoldier said:
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
Click to expand...
Click to collapse
I would suggest trying to restore down to WebOS 3.0. In that procedure you literally wipe EVERYTHING on the internal partitions in novaterm and start from absolute scratch. Therefore, if it a software issue you could solve the problem. However, if it is a hardware issue, you'd be kinda screwed.
Yeah, none of the methods I've ended up finding about this problem or other bricked problems are working at all.
i checked at work when i bought it, which of course the 11th was the year mark... but I do have android installed so even if i can get any chance of them honouring it so close they'll probably be like "oh you have android, that'll be $$$ for us to do anything. thanks!"
So I guess I now I have a paperweight with some features.
cdzo72 said:
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
There is a thread in the General forum about how to restore and downgrade. Have you tried that thread ? It is usually a great way to try and get that last restore before sending it back to HP.
73 de VE6AY
Sent from my HP Touchpad, running the latest CM9 nightly, from the XDA Premium App
how are you adding and deleting files when in android? which version of android do you have installed? have you tried different rom versions? have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to? it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard? are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android? have you run "fix permissions"? Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
sstar said:
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
Click to expand...
Click to collapse
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer, this would tend to suggest that the problem is software based corrupted or otherwise. I am trying to find a program that will allow me to read/format the Android partition on my windows computer and will let you know if come up with anything.
Regards
i guess i should change the title slightly.. it's not sdcard, but basically the entire touchpad contents. go to root and delete whatever i want and it doesn't matter. connect it and format with windows and it doesn't actually matter.
haxin said:
how are you adding and deleting files when in android?
Click to expand...
Click to collapse
i've added and deleted just by using mtp. i've also deleted the files on the android side with the video player (vplayer) i've installed es file explorer (which after restart is gone) and deleted with that. i've also gone into webos and installed internalz pro and deleted files that way, which it then seems to work until i of course do anything related to restarting.
some of the files i've put on, i've had it recognize briefly. so for the video file, start it, then it gets really choppy/glitchy playing it. so stop it, go back into the vplayer and it's back to the old stuff
which version of android do you have installed? have you tried different rom versions?
Click to expand...
Click to collapse
android version 4.0.3. nothing else will install. if i add files while in android, when i boot into cwm they are gone. if i mount usb in cwm and add them they stay briefly but when i try to flash them they fail.
have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to?
Click to expand...
Click to collapse
i have not tried adb yet, just not as familiar using it properly, i will give it a try though.
i am using windows 7 on my laptop currently. i do have a pc upstairs that i barely use that has vista, but i don't know how that would make a difference to the touchpad
it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard?
Click to expand...
Click to collapse
yeah as i put above i guess saying sdcard was a bit confusing/misleading (my bad, sorry!), i didn't really know what else to call it at the time or how to explain myself properly at first.
are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android?
Click to expand...
Click to collapse
i can move/delete/modify anything which has absolutely no effect to the device. i've used es file explorer and gone up to root and deleted everything and the system runs fine. says the system is empty with lots of free space (its the 32gb model) but restart or even go into recovery and everything is once again there.
have you run "fix permissions"?
Click to expand...
Click to collapse
i've run it a few times. just acts likes it's working and then says done. i've even gone into the mounts and storage in cwm and formatted sdcard/cache/data/system. does nothing at all in the end of things
Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
Click to expand...
Click to collapse
it was just something to try to get somewhere right. it never gets past 12%. always fails to reboot.
I am currently letting the battery drain and see if it dying and then being charged will do anything. probably not. but who knows. i talked to a "tech" on the chat support (i never mentioned android) who told me that having preware installed in webos causing it to become corrupt and they "don't knowledge of preware installed devices" exact words. no idea what that means haha don't have knowledge, don't acknowledge...
anyhow. i've not quite given up. i just don't really see it turning out any differently from the previous times. i do appreciate all the feedback and help very much though
ok so heres what I would try. First try flashing a new fresh rom. download one that you want to your computer like cm9 nightly or aokp or whatever you feel like. then boot into CWM recovery connect the touchpad to the computer via usb. then connect to the touchpad with adb. I'm not sure how to do this in windows because it's been so long since I've done it on a windows box, I always use linux.
adb has alot of options, you can move files to and from the device, you can uninstall or install app packages, and more. this way you can adb push the rom .zip to the touchpad's sdcard while youre in cwm recovery. this way you dont have to reboot the touchpad and risk having the file disappear, you can just go to 'install zip from sdcard' and then 'choose zip from sdcard' in cwm recovery after you adb push the rom, you should see it in the folder you pushed it to on the sdcard.
If you arent familiar with how to use adb from the command line or the terminal this might not make alot of sense and i dont know how better to explain it than that. Also yes windows 7 vs windows vista does make a difference there are issues with novacom installing properly, that's why you would have problems running acmeuninstaller or acmeinstaller2. if you look around you should find some videos or how to's that can probably explain it better. Hope this helps.
http://www.webos-internals.org/wiki/Novacom_with_Windows_7
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-5.html
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
ve6ay said:
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
Click to expand...
Click to collapse
Probably the best suggestion yet given that everything else has been tried.
Good luck.
****EDIT****
Before you attempt the step above I have just noticed a difference between between cwm and. TWRP2.2 which I have installed on my Touchpad via goo manager. If I open recovery via goo manager and then select wipe it gives me 4 options cache, davlik, factory reset AND system which i think says will remove your rom . I don't see the forth option available with the regular cwm/clockwork. Just a thought.
All the best with whatever you try next.
sstar said:
Probably the best suggestion yet given that everything else has been tried.
Good luck.
Click to expand...
Click to collapse
this would work, however you have to fix you novacom/novaterm issues on your windows machine before you'll be able to do any of this. the reason acmeuninstaller, acmeinstaller2 arent working is likely because youre on a windows7 64bit box and Palm-sdk, the novacomd.exe, noverm.exe, and javaruntime apps and drivers arent setup right. just make sure you have the proper javaupdates on your computer then you can install preware in webos, preware has some nice tools that will delete the entire android install partitions, one is called 'remove android' and the other is called 'tailor' you run them from within webos. after you do that then in webos you should do a full device reset. you'll find it in the "info" tab under settings in webos. this will delete and reformat the whole /media ,(aka sdcard) partition. so you will lose all the files you have stored on both webos and android. that format will take a long time probably like 30 min or more. after thats done. reboot the hp and run webosdoctor. now i know for sure this will work because ive done it on mine. remember to put the touchpad in developer mode in webos first to install preware. you can do that by typing webos20090606 into the webos search bar and hitting enter. I'll put links from my box.com accou t to everything you need.
https://www.box.com/s/479acdb6ef9c99fc7b92
https://www.box.com/s/1aed4722990aad251570
edit: also I'm not sure if youre on the 16gig 32gig or 64gig pad, the webosdoctor that i linked is for 32gig wifi only US version. if thats not what you have then youll need to get the doctor for for specific touchpad. or you could create a webosmetadoctor but thats a whole nother project.
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
plasticsoldier said:
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Click to expand...
Click to collapse
ok no one will be able to help you fix this issue unless you give complete details of the problems. when you say " novacom/novaterm stuff doesn't work" we cant really help specific error details is what i need. I dont mind helping you fix this but you have to be a little more specific on exactly what,where, and how youre installing and running and mounting apps and directories.
your problem IS fixable but you need to slow down and really do things exactly step by step.
Ok so back to ./adb. now when you boot in to CWM recovery on he touchpad DONT do anything in CWM just plug it into the computer. do not mount it as a usb storage and dont mount or unmount the sd partition LEAVE IT.
you can then use ./adb from the command line or terminal on the computer to move the files to the touchpad' or install apk's uninstall apk's you name it. This will require that you know some linux terminal commands. for example to move a new rom zip to the internal sd card or into any other folder you can use ./adb push command to run a root shell on the android device itself you can use ./adb shell and then change folder and file properties from readonly to rw. this can all be done while the touchpad is patiently waitng in CWM recovery. this way when youre done installing or uninstalling apps from the device and moving flash zips to it, you can disconnect the .adb connection with ./adb disconnect or just type exit from the terminal till it closes. unplug it then you will be able to pick up the touchpad and install zip from the sdcard, keep in mind you dont want to choose 'apply u[date from sdcard' you want to use the 'install zip from sdcard option' you can read up more on how adb works. it is probally the most important part of hacking android.
with that being said. novaterm is the palm webos version of .adb. this is why when you boot into webos recovery to do things like acmeinstaller and acmeuninstaller2 the novaterm novacom and novacomd apps have to be installed correctly on the computer or else you wont be going anywhere fast. some screenshot examples of how it should appear below.
https://www.box.com/s/432e63a83215f00eea6a
https://www.box.com/s/970bc29542a05f98f036
https://www.box.com/s/63c0f656e8354f7f2d6a
https://www.box.com/s/cbe3266467ae8e3ebabe
https://www.box.com/s/005e56a61a178dd17fa4 some better resolution images.
Plasticsoldier said
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Yes there is
Firstly tailor does exist, it is a beta and the facility to dl must be enabled.
Read this and scroll down to Enabling beta test feeds and follow the instructions , when you get as far as using the Linux command you CAN copy and paste thank God.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . After that reboot into Webos and launch preware. Go into managed feeds as per the instructions in the link above and install Tailor. Reboot again and the app will work. It looks very good actually.
But before attempting to actually use Tailor please read the article I have posted below it is only 7 pages long but will explain how to use Taylor properly as it is a powerful tool.
http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I have done all of this , this morning so if you have any problems pm me or ask in this thread.
I sincerely hope that this helps, it should be the answer to your problems.
@haxin: sorry, wasn't trying to be unhelpful when everyone is being helpful to me. I shall be more detailed in future responses. I think i was getting frustrated and had had a busy exhausting day so it didn't help me come across clearly/properly.
OK, so I had preware installed already, so I removed it, went into developer mode, used the linux commands, reinstalled preware, added Tailor.
(i've done this a few times, because I didn't remove the cable after doing the linux commands for preware, then i accidentally hit the wrong buttons and it connected to 'usb drive' mode and wouldn't connect on the pc side and got stuck on the "ow disconnected me properly next time" screen).
So it gives me the following options
USB (media)
Android (system)
Android (cache)
Android (data)
Unused Space
the 'usb media' starts mounted and will mount again if unmounted. If I use 'check filesystem' it'll pass. So then I try 'delete partition' which pretends to delete, then it takes me to the unused partition which is still at 16mb. so i try to use "check filesystem' again and it fails. try repair and it fails as well
I've tried mounting the android parts just to see, they just sit there processing that they are trying to mount. trying to delete or anything else fails as well.
and now after trying things, any of the 'cards' will try to open and just sit there grey. and with my usb cable not plugged in it still is giving me the option to enter usb drive mode. and with this i have to restart and go through the steps again of adding Tailor which is getting tedious.
I restarted, went through the motions to get back to Tailor. trying out resizing just to see how that goes. So far 15%. not sure what will happen when done, but we will see.
This is getting long, so i'll end this part and update on anything and also try to familiarize myself with adb a tad more
I'm new to the Nook scene, but I've read the someone/leapinlear threads on rooting/putting google apps on the device.
Now that 2.0.5 is out, that seems to break the above.
One of my confusions is the talk of OOBE ( a new acronym for me to learn. )
Is it possible for me to open the Nook HD+ on xmas morning, and play with it without registering/updating?
Does the Nook force you to connect to wifi? What if I had no wifi?
If I can play with it without registering/updating, then use the current rooting methods later in the afternoon ... will that stop 2.0.5?
Do I need to read more?
curiousmike said:
I'm new to the Nook scene, but I've read the someone/leapinlear threads on rooting/putting google apps on the device.
Now that 2.0.5 is out, that seems to break the above.
One of my confusions is the talk of OOBE ( a new acronym for me to learn. )
Is it possible for me to open the Nook HD+ on xmas morning, and play with it without registering/updating?
Does the Nook force you to connect to wifi? What if I had no wifi?
If I can play with it without registering/updating, then use the current rooting methods later in the afternoon ... will that stop 2.0.5?
Do I need to read more?
Click to expand...
Click to collapse
You said you read my thread. Yes you can do the xmas thing by skipping OOBE ( look in my thread for how to do it). Which basically means skipping registration. And you don't have to turn on wifi so that it updates itself. But you do have to turn on wifi to register and you can do nothing with it without either registering or skipping OOBE. But it may be kind of not much fun without apps, books and wifi. I also just posted a new way to have an old version and still register. But you might want to wait to see if other users do ok with it.
Sent from my HD+ rooted stock using Tapatalk
leapinlar said:
Yes you can do the xmas thing by skipping OOBE ( look in my thread for how to do it).
Click to expand...
Click to collapse
Found it and read it. Great.
leapinlar said:
But it may be kind of not much fun without apps, books and wifi
Click to expand...
Click to collapse
Agreed.
But I also don't want to do the update and risk never being able to root it and get Google App Store on it; I have a large array of apps/games for my phone that I'm hoping will work on the HD+.
You can immediately boot straight to CM10 without registering if you'd like. That's exactly what I did, and it has worked flawlessly.
OOBE, known as Out-of-Box-Experience. Basically after registering, you get the experience you should. Skipping OOBE is basically not registering the product, and entering a development/test mode. OOBE is associated with not registering the device.
The Nook HD+ requires a WiFi connection to register the product, and what if the end-user doesn't have WiFi? I guess that's tough on them, they can't register. To be honest, I can't believe it either. To use the HD+ if you do not have WiFi, is to skip OOBE (which is the same procedure as the Nook Color's).
If you skip OOBE, then there is nothing to play with on the tablet; other than familiarising yourself with the interface. That's it. Not even the browser works; actually it has no apps at all. If you later root the tablet [and install GAPPs], whilst not registering the tablet, you will eventually get a lot more features; and pretty much use it like any other Android tablet. However, a lot of features will be disabled, such as the stock Android Browser (it will not load, as it will not be installed). A lot of other apps may then cause problems, due to the default browser not being present (i.e. BBC iPlayer). With the All in One root, developed by someone0, it will disable automatic OTA updates, so you will not update any further than your current factory version. However, some users (including myself) have been forced the update, so you cannot be certain that you will remain on the factory version (those prior to 2.0.5).
However, I would recommend you reconsider your options. If you want a better experience, I would recommend that you register the device (do NOT register now, please read the rest of my post). Important, remember the credentials you register the device with. If there are any future updates for the Nook, you will need to input the same e-mail address and password (unless password changed). If you create another B&N account at this stage, your Nook will constantly output an error; I contacted B&N today, and they couldn't solve it either. I found the solution, you have to remember the exact e-mail address you used to register. So, remember the e-mail address you use to register; and absolutely the password too, or the security question. Without them, you will not be able to register your device again.
Continuing on, I stated I would recommend you to register the device. However, before you do so, please make sure you have a minimum 4GB microSD card present (I used a SanDisk 4GB class 4). When you register your device, your Nook will check for updates. It will find 2.0.5 and update to it. Just so you know, someone0 and leapinlar have worked together to bring a "Universal Root" for the Nook HD+ and that universal root even roots version 2.0.5 (thank you someone0 and leapinlar; I'm currently using it). After registering your device, you will be introduced to your Nook interface. It's empty, even the apps are pretty much useless (except for Browser, only positive); you can't even spend more than 10 minutes on it, without enjoying what your doing. So I would recommend the root + GAPPs to unlock most of the "Android" features. To use the universal root, you'll need to boot into CWM (ClockWorkMod) via SD card (minimum of 4GB, anything less won't be detected/viable). Before registering and continuing with what I say, please make sure you are able to write onto your SD card using your computer. Although we are using CWM, we are NOT going to flash any ROMs (unless you want to of course, but the following "guide" below won't detail so).
First, you'll need to insert your SD card into your computer; where you're in a position where you can write on the card. (Files links/sources/information was sourced from http://forum.xda-developers.com/showthread.php?t=2062613)
Write the CWM .img (NookHD+bootable-CWM-6023-for-emmc-stock-4GB.zip) onto the SD Card using "Win32diskimager in Windows or use the dd command in Linux or OSX".
Download NookHD+Universal-Root.zip and place it within the SD Card. Also do this for the GAPPS + EXTRAS (including ManualOTA and Unknown Sources) .zip file, which you can download here (put together by leapinlar). DO NOT extract the .zip, just place them into the SD card.
At this point, make sure you have registered your Nook HD+, updated and installed version 2.0.5. Also make sure you have launched the stock ROM at least once (i.e. turned on the device into the Nook software/modified Android OS).
Now, turn off your device (hold the power button until a message is displayed on screen, and press shut down, or similar on screen). At the bottom of the Nook, on the left of the charging port, there is a cover protecting the SD card slot. Take it out (not all the way, it's attached to the body), and place in your SD card (with the CWM and universal root, as well optionally the GAPPS; although recommend installed on the SD card).
With the SD card in, turn your Nook on. After a few seconds, you should load into CWM. Select the option "install .zip from SD card" (use volume up/down to move across the list, "n" button below screen to select, and power button to move up one menu).
Firstly, install "NookHD+Universal-Root.zip". Wait for it to fully install, then install the GAPPS + Extras.
After the last step, reboot your device and take out the SD card before reboot. You should now load into your stock OS, whilst being rooted and and GAPPs installed on version 2.0.5. Success!
After the above guide, I would personally recommend Nova Launcher Prime; it unleashes the full experience of Android for me anyway. Haha, from now it's all yours.
That should be all from me, and the best of luck. I support you either way, whether you register or not. Merry Christmas too by the way.
HiddenG said:
OOBE, known as Out-of-Box-Experience.
That should be all from me, and the best of luck. I support you either way, whether you register or not. Merry Christmas too by the way.
Click to expand...
Click to collapse
Fantastic; I happen to have a 4GB card and I'm writing out the .img as I type.
Merry Christmas to you.
Yea, I probably taking a day off from xda forum tomorrow, so enjoy guys.
leapinlar deserves most of the credits since he is doing all the scripting and testing. All I did was giving him ideas(good and bad).
Ahh.. CuriousMike, from BARF, right?
Small world. Let me reemphasize that if you immediately throw in the CM10 install, you can totally skip the registration step. You essentially boot around it, and the next time the device boots without the CM10 SD card plugged in, if you so choose, it will be like opening it up fresh out of the box, with the nook asking you to register and so on.
If you *just* want a full android tablet, the CM10 SD is by far the way to go. Odds are your Xmas wrapped nook doesn't yet have 2.0.5 installed. You should be able to jump straight into CM10 and avoid the current mess of trying to preserve root, avoiding updates, working around the B & N interface and so on. It doesn't mean you can't do that at a later date, but right now CM10 seems to be a much better option than trying to deal with the B&N interface. Best part is that you can continually boot right off that SD card and never have to worry about dodging updates.
I'd recommend it above the current alternative of trying to root and apply fixes to have a usable tablet.
KestrelYI said:
Ahh.. CuriousMike, from BARF, right?
Small world. Let me reemphasize that if you immediately throw in the CM10 install, you can totally skip the registration step. You essentially boot around it, and the next time the device boots without the CM10 SD card plugged in, if you so choose, it will be like opening it up fresh out of the box, with the nook asking you to register and so on.
If you *just* want a full android tablet, the CM10 SD is by far the way to go. Odds are your Xmas wrapped nook doesn't yet have 2.0.5 installed. You should be able to jump straight into CM10 and avoid the current mess of trying to preserve root, avoiding updates, working around the B & N interface and so on. It doesn't mean you can't do that at a later date, but right now CM10 seems to be a much better option than trying to deal with the B&N interface. Best part is that you can continually boot right off that SD card and never have to worry about dodging updates.
I'd recommend it above the current alternative of trying to root and apply fixes to have a usable tablet.
Click to expand...
Click to collapse
I guess we can disagree on that. The way I see it, doing Skip OOBE and then root it would be more stable than CM10. A lot of things still not working yet on CM10. So, I decided to stick w/ stock for my personal use. Considering there is universal root for 2.0.5 now also, it's possible to be on 2.0.5 and still get root+gapps. I guess it could just end up being what do you need it for.
my nook is up
posting this from the nook, using firefox! surprising that chrome comes up as not-compatible.
i've got a few of my play store apps already installed... looking good.
i bought nova-launcher for 0.25$ during googles last big sale, so i'm using that. the experience is androidy-enough.
word-hero is also incompatible... that will push me to "cm10" when it's compatibler-er.
My Nook HD+ came out of the box with 2.0.2 and hasn't updated to 2.0.5 after a couple hours of use. Tried a couple times to do a manual update and says no updates available. ??
Will this work, on my registered device? I have it all setup and working on205, but want gapps too.
Thanks,
Steve
piperman7 said:
Will this work, on my registered device? I have it all setup and working on205, but want gapps too.
Thanks,
Steve
Click to expand...
Click to collapse
It worked for me, just as described.
That sounds good, I just picked up a 8gb class 10 to use.
Thanks again,
Steve
HiddenG said:
OOBE, known as Out-of-Box-Experience. Basically after registering, you get the experience you should. Skipping OOBE is basically not registering the product, and entering a development/test mode. OOBE is associated with not registering the device.
The Nook HD+ requires a WiFi connection to register the product, and what if the end-user doesn't have WiFi? I guess that's tough on them, they can't register. To be honest, I can't believe it either. To use the HD+ if you do not have WiFi, is to skip OOBE (which is the same procedure as the Nook Color's).
If you skip OOBE, then there is nothing to play with on the tablet; other than familiarising yourself with the interface. That's it. Not even the browser works; actually it has no apps at all. If you later root the tablet [and install GAPPs], whilst not registering the tablet, you will eventually get a lot more features; and pretty much use it like any other Android tablet. However, a lot of features will be disabled, such as the stock Android Browser (it will not load, as it will not be installed). A lot of other apps may then cause problems, due to the default browser not being present (i.e. BBC iPlayer). With the All in One root, developed by someone0, it will disable automatic OTA updates, so you will not update any further than your current factory version. However, some users (including myself) have been forced the update, so you cannot be certain that you will remain on the factory version (those prior to 2.0.5).
However, I would recommend you reconsider your options. If you want a better experience, I would recommend that you register the device (do NOT register now, please read the rest of my post). Important, remember the credentials you register the device with. If there are any future updates for the Nook, you will need to input the same e-mail address and password (unless password changed). If you create another B&N account at this stage, your Nook will constantly output an error; I contacted B&N today, and they couldn't solve it either. I found the solution, you have to remember the exact e-mail address you used to register. So, remember the e-mail address you use to register; and absolutely the password too, or the security question. Without them, you will not be able to register your device again.
Continuing on, I stated I would recommend you to register the device. However, before you do so, please make sure you have a minimum 4GB microSD card present (I used a SanDisk 4GB class 4). When you register your device, your Nook will check for updates. It will find 2.0.5 and update to it. Just so you know, someone0 and leapinlar have worked together to bring a "Universal Root" for the Nook HD+ and that universal root even roots version 2.0.5 (thank you someone0 and leapinlar; I'm currently using it). After registering your device, you will be introduced to your Nook interface. It's empty, even the apps are pretty much useless (except for Browser, only positive); you can't even spend more than 10 minutes on it, without enjoying what your doing. So I would recommend the root + GAPPs to unlock most of the "Android" features. To use the universal root, you'll need to boot into CWM (ClockWorkMod) via SD card (minimum of 4GB, anything less won't be detected/viable). Before registering and continuing with what I say, please make sure you are able to write onto your SD card using your computer. Although we are using CWM, we are NOT going to flash any ROMs (unless you want to of course, but the following "guide" below won't detail so).
First, you'll need to insert your SD card into your computer; where you're in a position where you can write on the card. (Files links/sources/information was sourced from http://forum.xda-developers.com/showthread.php?t=2062613)
Write the CWM .img (NookHD+bootable-CWM-6023-for-emmc-stock-4GB.zip) onto the SD Card using "Win32diskimager in Windows or use the dd command in Linux or OSX".
Download NookHD+Universal-Root.zip and place it within the SD Card. Also do this for the GAPPS + EXTRAS (including ManualOTA and Unknown Sources) .zip file, which you can download here (put together by leapinlar). DO NOT extract the .zip, just place them into the SD card.
At this point, make sure you have registered your Nook HD+, updated and installed version 2.0.5. Also make sure you have launched the stock ROM at least once (i.e. turned on the device into the Nook software/modified Android OS).
Now, turn off your device (hold the power button until a message is displayed on screen, and press shut down, or similar on screen). At the bottom of the Nook, on the left of the charging port, there is a cover protecting the SD card slot. Take it out (not all the way, it's attached to the body), and place in your SD card (with the CWM and universal root, as well optionally the GAPPS; although recommend installed on the SD card).
With the SD card in, turn your Nook on. After a few seconds, you should load into CWM. Select the option "install .zip from SD card" (use volume up/down to move across the list, "n" button below screen to select, and power button to move up one menu).
Firstly, install "NookHD+Universal-Root.zip". Wait for it to fully install, then install the GAPPS + Extras.
After the last step, reboot your device and take out the SD card before reboot. You should now load into your stock OS, whilst being rooted and and GAPPs installed on version 2.0.5. Success!
After the above guide, I would personally recommend Nova Launcher Prime; it unleashes the full experience of Android for me anyway. Haha, from now it's all yours.
That should be all from me, and the best of luck. I support you either way, whether you register or not. Merry Christmas too by the way.
Click to expand...
Click to collapse
Just got my Nook HD+ for Christmas, 1st Android device. I followed the above instructions to root it, after reboot it is just sitting at the first nook screen. It's been about 15 minutes or so, should I manually reboot the device or wait longer? Is it possible it just needs to be redone? The only odd thing I can across was after selecting reboot it said "ROM may flash stock recovery on reboot", should i have selected Yes/No, Should I backup the stock ROM?
Thanks for all the Help
curiousmike said:
posting this from the nook, using firefox! surprising that chrome comes up as not-compatible.
i've got a few of my play store apps already installed... looking good.
i bought nova-launcher for 0.25$ during googles last big sale, so i'm using that. the experience is androidy-enough.
word-hero is also incompatible... that will push me to "cm10" when it's compatibler-er.
Click to expand...
Click to collapse
Glad you got your tablet working with GAPPs! Hope it's all good; of course it's much better than sticking to B&N's book reader, haha. Indeed yes, I can't believe that a few apps in Google Play are not compatible either; although as suggested, sideloading them often work fine. :laugh:
mzjc said:
My Nook HD+ came out of the box with 2.0.2 and hasn't updated to 2.0.5 after a couple hours of use. Tried a couple times to do a manual update and says no updates available. ??
Click to expand...
Click to collapse
Did you skip the OOBE? The registration process of the device? If so, this problem could occur. If not, and you're registered then no problem either. If you're truly stuck on 2.0.2, that could be seen as a benefit; as your roots would never be broken, due to no future updates. If you'd like to root and place GAPPs on your tablet, I'd recommend you follow someone0's all-in-one guide. someone0's allinone will root your Nook HD+, install GAPPs, manual OTA and installation from Unknown Sources; provided your HD+ is on version 2.0.0 to 2.0.4, where you are eligible. This rooting method provides the exact same end-result as the 2.0.5 root, and is no different in performance or usability; they're exactly the same, just different installation process.
I've not tested it, but you may use the same rooting process as I've described on the last page; since the rooting method is universal. However, I have not tested it, other than on version 2.0.5. You'll also need a microSD card for this process, so I'd just recommend the adb-allinone method by someone0.
Best of luck.
ifdwolf2008 said:
Just got my Nook HD+ for Christmas, 1st Android device. I followed the above instructions to root it, after reboot it is just sitting at the first nook screen. It's been about 15 minutes or so, should I manually reboot the device or wait longer? Is it possible it just needs to be redone? The only odd thing I can across was after selecting reboot it said "ROM may flash stock recovery on reboot", should i have selected Yes/No, Should I backup the stock ROM?
Thanks for all the Help
Click to expand...
Click to collapse
First Android device? Haha, hopefully it'll make a good impression after rooting and GAPPS. Sorry about the wait. Once you've loaded/rebooted into the Nook HD+ after CWM/rooting/GAPPS etc, press the "n" button below the screen. You should be given the option to select a launcher; temporarily select ZeamLauncher and set it as default action. After that, you should be good to go. Personally, I would recommend Nova Launcher Prime instead of ZeamLauncher. If you'd like, you can download the free version of Nova Launcher from Google Play (I would recommend it strongly over ZeamLauncher). It should provide you a better "Android-experience".
If pressing the 'n' button below the screen did nothing, then you can try the rooting process again. Also selecting yes, or no shouldn't make a difference during reboot; "ROM may flash stock recovery on reboot". You may backup your stock ROM if you feel necessary, but it's not absolutely essential (if you ever run into problems, you can force the tablet to fail booting 8 times, and the tablet will automatically restore to factory defaults). If you have further problems, please reply.
Best of luck.
Boom, thanks for the help, working like a champ now! Does the mic feature in nova require chrome? Gonna side load it now. Device is much better rooted, big thanks all to all envolved!
Sent from my BNTV600 using xda app-developers app
Hey folks. I'm having some issues with the "Root your device with a bootable microSD card" method. I followed the instructions precisely.. wrote the image to a 32 GB microSD (I don't own any 4 GB cards).. and my nook REFUSES to even see the card nor boot from it for that matter.. just goes straight to the registration screen every time. Is there something that I could perhaps be missing here...? or is it that I MUST have a 4 GB card (and no bigger)?? (the microSD is the cream of the crop Sandisk 32 GB class 10 model. I couldn't resist picking one up, as they were on sale for only $26 at the time.
My HD+ is a pretty paperweight at the moment, and I'd love to get it back up and running. I really don't want to do the "all in one" method, as it keeps you in "TEST" mode.. which bugs the crap outta me.
What am I missing?!
HiddenG said:
OOBE, known as Out-of-Box-Experience. Basically after registering, you get the experience you should. Skipping OOBE is basically not registering the product, and entering a development/test mode. OOBE is associated with not registering the device.
The Nook HD+ requires a WiFi connection to register the product, and what if the end-user doesn't have WiFi? I guess that's tough on them, they can't register. To be honest, I can't believe it either. To use the HD+ if you do not have WiFi, is to skip OOBE (which is the same procedure as the Nook Color's).
If you skip OOBE, then there is nothing to play with on the tablet; other than familiarising yourself with the interface. That's it. Not even the browser works; actually it has no apps at all. If you later root the tablet [and install GAPPs], whilst not registering the tablet, you will eventually get a lot more features; and pretty much use it like any other Android tablet. However, a lot of features will be disabled, such as the stock Android Browser (it will not load, as it will not be installed). A lot of other apps may then cause problems, due to the default browser not being present (i.e. BBC iPlayer). With the All in One root, developed by someone0, it will disable automatic OTA updates, so you will not update any further than your current factory version. However, some users (including myself) have been forced the update, so you cannot be certain that you will remain on the factory version (those prior to 2.0.5).
However, I would recommend you reconsider your options. If you want a better experience, I would recommend that you register the device (do NOT register now, please read the rest of my post). Important, remember the credentials you register the device with. If there are any future updates for the Nook, you will need to input the same e-mail address and password (unless password changed). If you create another B&N account at this stage, your Nook will constantly output an error; I contacted B&N today, and they couldn't solve it either. I found the solution, you have to remember the exact e-mail address you used to register. So, remember the e-mail address you use to register; and absolutely the password too, or the security question. Without them, you will not be able to register your device again.
Continuing on, I stated I would recommend you to register the device. However, before you do so, please make sure you have a minimum 4GB microSD card present (I used a SanDisk 4GB class 4). When you register your device, your Nook will check for updates. It will find 2.0.5 and update to it. Just so you know, someone0 and leapinlar have worked together to bring a "Universal Root" for the Nook HD+ and that universal root even roots version 2.0.5 (thank you someone0 and leapinlar; I'm currently using it). After registering your device, you will be introduced to your Nook interface. It's empty, even the apps are pretty much useless (except for Browser, only positive); you can't even spend more than 10 minutes on it, without enjoying what your doing. So I would recommend the root + GAPPs to unlock most of the "Android" features. To use the universal root, you'll need to boot into CWM (ClockWorkMod) via SD card (minimum of 4GB, anything less won't be detected/viable). Before registering and continuing with what I say, please make sure you are able to write onto your SD card using your computer. Although we are using CWM, we are NOT going to flash any ROMs (unless you want to of course, but the following "guide" below won't detail so).
First, you'll need to insert your SD card into your computer; where you're in a position where you can write on the card. (Files links/sources/information was sourced from http://forum.xda-developers.com/showthread.php?t=2062613)
Write the CWM .img (NookHD+bootable-CWM-6023-for-emmc-stock-4GB.zip) onto the SD Card using "Win32diskimager in Windows or use the dd command in Linux or OSX".
Download NookHD+Universal-Root.zip and place it within the SD Card. Also do this for the GAPPS + EXTRAS (including ManualOTA and Unknown Sources) .zip file, which you can download here (put together by leapinlar). DO NOT extract the .zip, just place them into the SD card.
At this point, make sure you have registered your Nook HD+, updated and installed version 2.0.5. Also make sure you have launched the stock ROM at least once (i.e. turned on the device into the Nook software/modified Android OS).
Now, turn off your device (hold the power button until a message is displayed on screen, and press shut down, or similar on screen). At the bottom of the Nook, on the left of the charging port, there is a cover protecting the SD card slot. Take it out (not all the way, it's attached to the body), and place in your SD card (with the CWM and universal root, as well optionally the GAPPS; although recommend installed on the SD card).
With the SD card in, turn your Nook on. After a few seconds, you should load into CWM. Select the option "install .zip from SD card" (use volume up/down to move across the list, "n" button below screen to select, and power button to move up one menu).
Firstly, install "NookHD+Universal-Root.zip". Wait for it to fully install, then install the GAPPS + Extras.
After the last step, reboot your device and take out the SD card before reboot. You should now load into your stock OS, whilst being rooted and and GAPPs installed on version 2.0.5. Success!
After the above guide, I would personally recommend Nova Launcher Prime; it unleashes the full experience of Android for me anyway. Haha, from now it's all yours.
That should be all from me, and the best of luck. I support you either way, whether you register or not. Merry Christmas too by the way.
Click to expand...
Click to collapse
Hey there. I followed your directions EXACTLY as posted. I didn't have a 4 GB microSD, but I DID have a 32 GB class 4. I used that. Long story short, the nook will NOT "see" nor boot from said microSD no matter what I do. Is there some sort of button combo I need to be doing while the nook HD+ is turning on to see the sd card? I'm totally lost on this.
Thanks in advance for your help!!
If you'd like to PM me, that way my email will notify me when a response has been received, I'd REALLY appreciate it! Thanks for all your hard work!
The one difference might be that I did the whole oobe; I registered the nook... I rebooted twice to the stock Os (somewhere I read that you had to reboot once after setting up bn account.) I don't know if that's your issue, but it's what I did and I'm running gapps.
Sent from my SPH-L710 using Tapatalk 2
Hi, I'm new to this whole android thing. I got a Kindle Fire HD 7" it's rooted with SuperSU and Google Play store on it successfully!
My main issue is it seems many tweaks like a reboot after installation, but my power button is completely missing. I can plug the device in to turn it on, and open/close the cover to put it to sleep.
Are there any tweaks around where I can like slide to power down, or force reboot how you would if you were to press the power button?
Alternately, I'd also like to remove the ad lock screens and potentially install a live wallpaper on either the lock screen or the home page. And maybe have an actual android grid set up. I know you need a secondary launcher to do this kind of thing, but all the ones I looked at screamed brick, and I got a bit worried. Could anyone point me at some basic tutorials? (I've jailbroken my Ipad rather extensively, but this seems to be a bit more in-depth to the actual operating system)
ETA: I haven't Used QMenu Just the ABD Drivers and the Root_with_Restore_by_Bin4ry_v33
If this is the 2012 model with a camera you can flash cm 11 on it and use maromi's kernel, it has double tap to wake, and cm also has double tap corner to sleep.
There are apps in the Google play store for rebooting methods that I believe allow for reboot normally as well as to fastboot and recovery, I know CM's built in power menu has those option if you enable them, but then there's the issue of getting to them with a broken power button.
Sent from my Amazon Tate using Tapatalk
It is the 2012, it has the camera with the clear slider to unlock.
I installed Nova Launcher off the G-play store, but yet again something needs to be rebooted! Hmph.
I'd love if you have any links to those store based power options, or to the CM 11 (is that a launcher also? what does "Flash" mean exactly? I've seen it around. ) The power button issue sucks, but I can't complain since it was a free gift!
I guess I can just run the battery down to reboot, but that is such a pain.
Dovetail said:
It is the 2012, it has the camera with the clear slider to unlock.
I installed Nova Launcher off the G-play store, but yet again something needs to be rebooted! Hmph.
I'd love if you have any links to those store based power options, or to the CM 11 (is that a launcher also? what does "Flash" mean exactly? I've seen it around. ) The power button issue sucks, but I can't complain since it was a free gift!
I guess I can just run the battery down to reboot, but that is such a pain.
Click to expand...
Click to collapse
hehe wow this is a first, ok cm 11 is cyanogen mod 11. its a rom you can flash instead of amazon's original os, it is way faster and more up to date and is more like pure android. Flash basically means we are overwriting the system files and such that came with the device. It can have any launcher, set wallpaper, is already rooted and has alot of cool things like themes and performance options you can set, much better than stock amazon os. You seem quite new to the concept of flashing a rom though so i advise you to read the tutorial thouroughly and as long as you don't mess up you shouldnt need a fastboot adapter even though its always advised to have one anyways. Heres a link: http://forum.xda-developers.com/showthread.php?t=2271909
Let me give you some advice so you don't end up with a red screen brick. Make sure when you follow this that when you see the red text at the top of fireflash(you will understand this when you start this part) that you check that box off thats either to the side or above the red text, this is a vital step you must follow or you will need a fastboot adapter to fix. I also recommend grabbing the cm rom and its corresponding gapps ahead of time.
Feel free to ask questions.
Also if you install a launcher on amazon os you will need root and you must copy and paste the app into the system folder and set the permission to a certain way or it will bootloop. I think titanium backup has a convert to system app button that does it for you. Wallpaper doesnt defaultly work without my fix either.
Nevermind, it finally worked
stunts513 said:
Feel free to ask questions.
Click to expand...
Click to collapse
Thank you so much for being patient with me!
I had been doing the app thing, but it seems like such a pain to do that with every app. I removed the installer, it wasn't doing much of what I was wanting anyways, the CM11 sounds much more like what I'm wanting to get to.
I'll give the tutorial a good read through and update this post with any questions I have!
Question 1: "commonly associated .... higher without first flashing the Amazon OS 7.2.3 bootloader" With flashing the cm11 do I need to (or do you recommend I) first restore or go back to the 7.2.3 or can I continue with 7.4.8? I will obviously be making backups as it seems that's the only way to recover with a standard usb cable.
Question 1A: If you are NOT on the 7.2.3 bootloader (you'll see red letters warning you), then hit the check box next to that to flash the 7.2.3 bootloader, otherwise you'll see a red screen after you reboot. If you don't see that warning, you're fine, move on. Is this the box you mentioned? It seems like this saves the hassle of going to 2.3 THEN flashing.
Question 2: "Alternatively, you can use this if the first method failed: Root_with_Restore_by_Bin4ry," I used this method in the first place. I had some issues with the ABD drivers not being recognized but got them working when I used amazon's direct ones. Furthermore, when I did get rooted (I used an app to check that it was and since nova worked I assume it was correct) superuser wasn't installed. I went and installed superSU manually. will this be an issue? (things have asked for and been granted permission and show as such in the superSU app)
Question 3: I'm using my work computer which runs through a server. when I go to back up through cmd it says the folder will be in C: and to then transfer it. The server shouldn't matter, right? I guess I can always just do a search for the file name and it'll turn up somewhere.
Question 4: Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP I did find an app called "reboot" which allows me to reboot (shocking!) without the power button. Can I still use that app at this point?
Question 4A: Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache.After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot This section calles to wipe some sections, will this also wipe my apps? it calls later on to reboot again. If the first bit wipes the apps, then I wouldn't be able to reboot at this point. (aside of waiting for the battery to die)
Answer 1: you don't actually need to downgrade the os, as long as the bootloader gets downgraded it is fine. So yes that was the checkbox I meant, believe it or not people have missed seeing it before because of the red text around it.
Answer 2: I think it will be fine, though I'm surprised you could root it with Amazon's drivers, theirs were kinda crappy.
Answer 3: I think this is OK, not sure how your setup is exactly. I don't see network issues being a problem.
Answer 4: you can still use the app. As to the wiping, yes you will lose all your apps, it is required to do the equivalent of a factory reset in twrp when coming from amazon os as the system apps leave some data left behind that causes cm to malfunction. You can install anything you had again from the play store or manually if you had apk's lying around. You can backup app data for games and such with titanium backup and restore it once you reinstall titanium backup in cm.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Answer 1: you don't actually need to downgrade the os, as long as the bootloader gets downgraded it is fine. So yes that was the checkbox I meant, believe it or not people have missed seeing it before because of the red text around it.
Answer 2: I think it will be fine, though I'm surprised you could root it with Amazon's drivers, theirs were kinda crappy.
Answer 3: I think this is OK, not sure how your setup is exactly. I don't see network issues being a problem.
Answer 4: you can still use the app. As to the wiping, yes you will lose all your apps, it is required to do the equivalent of a factory reset in twrp when coming from amazon os as the system apps leave some data left behind that causes cm to malfunction. You can install anything you had again from the play store or manually if you had apk's lying around. You can backup app data for games and such with titanium backup and restore it once you reinstall titanium backup in cm.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Thank you so much again! I'm excited! I'll let ya know how it goes.
Sweet and I thought I'd mention if you get confused on what cm 11 build to download, the unofficial builds are a little bit more dated now that the device is a officially supported cm device, I recommend the link that isn't under mirrors that goes to cyanogenmod's Tate download page. The URL has those 3 words in it so you will know it when you see it. The m6 release is the stable release I recommend download instead of a nightly, I think m7 should be out soon, the cool thing is whenever a update is available it can ota like a phone, I believe it will make you choose to install the update though. I was impressed by how it updates, just seemed cool to watch. Not positive if cm's updater notifies you when updates are available though.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
The m6 release is the stable release I recommend download instead of a nightly, I think m7 should be out soon
Click to expand...
Click to collapse
Firstly, when I go to back up through the command prompt I get this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\admnasst>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot
0block.img"
'adb' is not recognized as an internal or external command,
operable program or batch file.
Am I missing some step? I do have ABD enabled on the kindle.
Secondly, on this site: http://download.cyanogenmod.org/?device=tate
am I wanting the download second from the bottom that says "snapshot" and ends with m6-tate
I would figure so, but I wanted to double check.
Yes that the right file, as to that command not being recognized it is because it expects you to have a copy of that command handy and in the directory the command prompt is cd'd into. For instance download my wallpaper fix in my signature and extract it, then shift + right click the folder and hit open new command window here, then try the command again.
I have and by itself laying around on a thread I made here on the forum but this works just as well.
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes that the right file, as to that command not being recognized it is because it expects you to have a copy of that command handy and in the directory the command prompt is cd'd into. For instance download my wallpaper fix in my signature and extract it, then shift + right click the folder and hit open new command window here, then try the command again.
I have and by itself laying around on a thread I made here on the forum but this works just as well.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I ran the first line and it started. I'm going to do everything tomorrow when I have more time. I'll keep you updated! Thank you again for helping me, and being so welcoming.
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot this was my favorite reboot app and it works well although I see your doing the custom ROM thing now.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
ROM toolbox has a quick-reboot option that is similar to respringing iOS, and it well let you create a launcher shortcut on your home screen.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Hi all, finally I registered here at xda today because of the great new HP TPToolbox that jcsullins provides here.
This is really really great !! Many thanks !
As a newcomer to this forum I somehow can not comment on the original thread ( ) although I'm developer for decades ..
Well - so far I've been around on webosnation and other forum - but here I find that the core of development happens here.
XDA seems to be a great place to be - as a developer.
1. About the posting from jcsullins: http://forum.xda-developers.com/showpost.php?p=52765181&postcount=5
It read:
> Only Touchpad Wifi supported (not 4G) at this time
I assume this is really limited to the released HP TouchPad and does not include the never released HP TouchPad Go (7" device) - right ?
2. I read:
> Reflash A6 Firmware allows you to reflash the A6 firmware.
I very much assume I can not use this if my TP is bricked (my TP does not show anything on the screen and no light at the home button).
So - I guess - I first need to do through the TPdebrick procedure.
Sure I know these instructions: http://rootzwiki.com/topic/38786-tpdebrick-v004 Again, thanks to jcsullins for providing these too.
( Also - I wonder if there is a way to use these instructions from a Win7 system too ?)
3. In terms of using TPToolbox to get Android installed on TP:
Till today I run only webos 3.0.5 on my TouchPads and I want to keep webos around. I have 32GB (Wifi) and 64GB (Wifi) and TP GO (Wifi).
What is the recommendation before installing some Android (4.4) on a TP. Do I need to rearrange / clean up some of the existing webos volumes?
Imagine - I have no experience with Android setup. I read all of the TPToolbox thread - but found no guidance for people who want to keep webos on the same device. And I have no good understanding of what the limitations/drawbacks are when running webos and Android on the same device.
4. I read:
> It will then install moboot (which is included in TPToolbox)
I have no clear understand what moboot is doing and if needed how to remove it again. Will it allow me to boot in Android or webos ?
How many Android versions can I install in parallel and then select one at boot time ?
5. A final question for now. Is there any consideration that in future TPToolbox could allow installing openWebOS if this becomes available for existing TP devices?
anyone with some answer please ?
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
[email protected] said:
anyone with some answer please ?
No need to answer all questions at once.
I'm most interested in comments about question (3):
what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Click to expand...
Click to collapse
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.
sstar said:
OPINIONS ARE subjective as you you appear to have several tablets it is in your best interests to test out and find what works for you. I personally am using Milaq's.
Have fun trying them.
Click to expand...
Click to collapse
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)
Unable to navigate TP Toolbox UI
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??
[email protected] said:
Thanks for your comment. So far I have no idea what "Milaq" is: I assume some kind of Android version - but such version is not documented with TPToolbox - so, for sure I will not use that for now.
My question (3) is more about hard facts: what the limitations/drawbacks are when running webos and Android on the same device: 32GB (Wifi) and 64GB (Wifi) ?
Will both OS run well on a 32GB system if both are installed and they use some shared disk space (volume?). I would consider at least 5GB of shared disk space to allow (video) file exchange on the device.
What is a recommended configuration to run webos and Android on the same device. Or doesn't it make sense at all and better use 2 devices?
Will TPToolbox optimize the volume size for both OS?
Can I configure the default OS at boot time? How to do? (Can I run Android apps inside a webos window?)
Click to expand...
Click to collapse
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend. WIth respect to the TP GO, it does not appear to have ever been released, but if you have one, you'll have to answer your own questions because no one here has ever mentioned having one:
http://www.pcmag.com/article2/0,2817,2397197,00.asp
Touchpad linked to google account acting badly
J Scullins Toolbox installed with ease. Many thanks. Freed up memory and eliminated WebOS (pretty but pretty useless). Booted fine, loaded CM 11 4.4.2. Then asked if I wanted to restored my google apps from google account. I did. Began updating apps, but included all apps I've ever installed on any android device and loaded my current phone (Galaxy 3) wall paper. Repeated message -> "Unfortunately Trebuchet has stopped" Did not seem to affect downloading updates. Then died. Plugging into charger (wall socket) did not wake it up. Charged all night. Nothing. Unplugged and plugged in again, self-rebooted to boot menu, but has phone screen and shows charging at 1%. Should I reboot to restore mode and start over? Anyone having charging issues after using Toolbox? Thanks.
shumash said:
As you point out, this is the place for answers. All of your questions have been answered in other threads. Search is your friend.
Click to expand...
Click to collapse
Thanks for promising that I should be able to find answer. I did read the complete thread about TPToolbox and few others too and search before I started this new thread - but my above 5 questions remained open. If anyone has found a good pointer please paste a URL here.
If I find correct answer myself I will put such links here.
ad (4) I think I understand moboot good enough for now. In my words it is a boot manager that comes with Android or at least you can use with Android. It is not a webos app or so. Not 100% sure how to get it on the TP device - but I assume when I install Android for first time it will also install and it will somehow stay even if Android gets deinstalled. Anyhow - any link to a good wiki page would be much appreciated.
ad (1) Yes, TP GO is a rare device - but several 100 seem to be around by now. Many of these come with some Android 2.X version installed. ( Mine was patched to webos 3.0.5 ) Ok, if noone has a GO here I have to assume that TPToolbox does not support / was not tested on TP GO. So far posting from jcsullins does not mention the TP GO at all: http://forum.xda-developers.com/show...81&postcount=5
mheath said:
I'm trying to use TP Toolbox to install Android on my TP. When I reach the TouchPad Toolbox UI on the tablet, the volume keys aren't working to navigate, so I have no way to select Complete Data Reset. Any ideas??
Click to expand...
Click to collapse
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?
mheath said:
I have a TP 4G - sounds like this could be an issue? Will this Toolbox installation work on the 4G? If not, is there a good alternative to install Android?
Click to expand...
Click to collapse
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65
Toolbox not working for me
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!
Rekaro said:
Hello,
i tried Toolbox to bring life back to my Touchpad.
When i'm running this program it starts very well but i can't get the menue.
So it's not possible to run one of the menue-points.
I use Windows 7 64bit, the TP is connected with USB-sign on.
My problem:
In the WebOs-log the last line shows a flash-failure.
When i'm starting the TP, first a static HP-logo comes up, followed from a rotating HP-logo,
the a screen changes from black to white with a grey button rotating.
Any idea?
Thanks!
Click to expand...
Click to collapse
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
A) Have novacom installed
To load TPToolbox, you will need novacom to be installed on your PC.
You can download and install novacom from http://www.openwebosproject.org/open.../packages.html
Or, you can download and run a java-based "universal installer" from http://code.google.com/p/universal-n...downloads/list
B) Put the Touchpad into webOS recovery mode and connect via USB cable to PC
NOTE: Even if webOS is removed, webOS recovery will still exist as it's built into the bootloader.
If you have moboot already installed, just select "webOS recovery" there.
Or, power the Touchpad off via webOS, then with the Touchpad is off, hold VolumeUp (closest to Power) and Power until you see the USB symbol.
Or, hold Power+Home until the screen changes (about 10 secs) and then start holding the VolumeUp button until you see the big USB symbol.
Click to expand...
Click to collapse
shumash said:
Re-read the directions for TP Toolbox. You need to boot into WebOS recovery (a static usb symbol). It sounds like your TP is trying to boot into WebOS, not WebOS recovery.
Click to expand...
Click to collapse
Thanks,
no it's in recovery mode i'm shure. A big usb symbol on the screen and some other lines.
I can then open the terminal-window and connect the Touchpad.
I add here pictures what happens when i type the commands "printenv" and "token".
When i type reboot, the TP starts correct to boot, first the static HP sign, then a greyed HP sign and then a screen (see the picture) with a grey rotating Button.
That's it.
issue loading TPTToolbox
Sorry folks - i am fairly new at this - and we all had to start at some point - so if this is obvious to most, i apologize.. but need a little help.
I cant seem to get the Toolbox to load, i downloaded it from the post,{as well as the Novacom driver} i have extracted the three files - when i open the .bat file i get the message below. I have the TouchPad connected via USB, and windows has assigned it a letter drive and I have the big USB icon on the pad screen
message:
"
Setting Palm path ...
Checking novacom service ...
Loading TPToolbox ...
.
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)
.
"
Toolbox
I'm not sure you understand the instructions on how to do the install.
Here is a link with instructions that I used for my install:
http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
While the instructions are written for windows users, I used them for my Ubuntu Linux install and everything
worked perfectly.
Recovery problem when running toolbox
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
Compatible Legacy ROM files:
cm-10.1-*-tenderloin.zip or
skz_tenderloin-2.11_jb_4.2.2-*.zip
Click to expand...
Click to collapse
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
However I am having issues with the recovery. The recovery I downloaded was update-CWM-jcs-dm-tenderloin-20140317.zip
I get the error that "No supported recovery file found. Aborting."
I've seen mention that the cable could be bad however if I have no files in the ttinstall directory, I get an error that there's no ROM. I upload the ROM and rename it and the error then is about the Recovery file so that means the ROM was in fact uploaded so the cable theory is moot.
I'm thinking the recovery file needs to be named something specific however when I have tried to use the file names listed as
but that doesn't work. Is the file name supposed to be something else?
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
Try the update-TWRP-jcs-dm-tenderloin-20140512.zip instead. It worked just fine for me.
chrisjpopp said:
I've followed the instructions for running the Toolbox and have removed WebOS, setup the directory sizes and uploaded the ROM and GApps AND renamed the files as specified in the how-to.
......
(Sorry about asking this here. Tried to ask in Developer thread but I don't have enough posts)
Click to expand...
Click to collapse
How did you rename the file? I don't think you need to rename any file.
No matter how many times I reinstall novacom TPtoolbox will not get past
Checking Novacom services....
And goes no fauther.
I am running windows 8.1
HP Touchpad 4G - Issue running
[email protected] said:
The original TPtoolbox thread answers this 4G question as: http://forum.xda-developers.com/showpost.php?p=52923285&postcount=65
Click to expand...
Click to collapse
Good thing I didn't wipe webOS off! I'd have a nice frisbee. Hopefully these guru's will fix that issue and we can all be happy. Thanks JCSullins.
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)