Related
After testing CM10 for a while (thx codeworx) I now ported my NanoBoot image to CM10.
Changes compared to original CM10 boot:
"insecure" (means: / and /system mounted read-write (easy 'adb push' into /system ...), ro.secure = 0)
support for /system/etc/init.d/ init scripts
(somewhat) easy UMS access
Changes in r10:
Use 179:24 instead of 179:25 as address for UMS (fixes UMS on Windows)
to enable UMS for external SD with this boot.img it is enough to do:
Code:
setprop sys.usb.config mass_storage,adb
to return to MTP:
Code:
setprop sys.usb.config mtp,adb
TIP:
If you use Linux you may use some function like:
Code:
ums () {
if [[ $1 == "+" ]]; then
adb root
sleep 2
adb -s c1607c00051963f shell 'setprop sys.usb.config mass_storage,adb'
else
adb root
sleep 2
adb -s c1607c00051963f shell 'setprop sys.usb.config mtp,adb'
fi
}
'ums +' will enable UMS, 'ums -' will disable UMS on your tablet (not to mention it needs to be connected (...))
replace '-s c1607c00051963f' with '-s <your adb id>' - you get the id via 'adb devices'.
If you only got one adb-enabled device, you could remove '-s c1607c00051963f' from the commands.
If there's more than one device connected adb needs to know which one should receive the commands.
I did not yet have the time to modify framework-res.apk to add UMS to the list of options...
Flash using img/pit with either Odin or Heimdall. Or use zip to flash using CWM.
Images for Odin/Heimdall
PIT:
p3100.pit http://downloads.nanolx.org/P3110/p3100.pit
p3110.pit http://downloads.nanolx.org/P3110/p3110.pit
Stock CM10 Kernel:
NanoBoot-r10-CM10.img http://downloads.nanolx.org/P3110/NanoBoot-r10-CM10.img
Johnsel's CM10OC Kernel:
-No WiFi-
Zips for CWM
Stock CM10 Kernel:
NanoBoot-r10-CM10.zip http://downloads.nanolx.org/P3110/NanoBoot-r10-CM10.zip
Johnsel's CM10OC Kernel:
-No WiFi-
Tried this on my P3113 and it broke my WiFi.
Macadamia Daze said:
Tried this on my P3113 and it broke my WiFi.
Click to expand...
Click to collapse
Here with 3110 it works... if you provide me the original 3113 boot.img, I can re-pack one, that should work.
And it only works with Cyanogen Mod 10. Not on 9 or stock rom.
Setialpha said:
Here with 3110 it works... if you provide me the original 3113 boot.img, I can re-pack one, that should work.
And it only works with Cyanogen Mod 10. Not on 9 or stock rom.
Click to expand...
Click to collapse
I am using CM10, so here's the original boot.img for CM10 on the P3113. You don't need the stock one, do you?
Macadamia Daze said:
I am using CM10, so here's the original boot.img for CM10 on the P3113. You don't need the stock one, do you?
Click to expand...
Click to collapse
try with attached CWM zip.
n00b here.....what does this do??
Sent from my GT-P3113 using Tapatalk 2
F3AR420 said:
n00b here.....what does this do??
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
Just as first post says. This is a modified boot image for cyanogen mod 10 (no other ROM supported!) for galaxy tab 2 7", which makes / and /system read-write, adds support for init-scripts and adds pretty easy way to access UMS (USB Mass Storage) for external SD-Card.
According to your signature you're using an incompatible rom anyway - so don't use this.
@Macadamia Daze: now also tested with a 3100 I got my hands on: WiFi works. Dunno why it doesn't work with 3113 (I got no clue whether 3113 has some special WiFi stuff or whatever). Either way, please tell me, whether the attached one for 3113 (two posts above) works with WiFi.
Setialpha said:
@Macadamia Daze: now also tested with a 3100 I got my hands on: WiFi works. Dunno why it doesn't work with 3113 (I got no clue whether 3113 has some special WiFi stuff or whatever). Either way, please tell me, whether the attached one for 3113 (two posts above) works with WiFi.
Click to expand...
Click to collapse
Silly me; the problem was an incompatible kernel (Johnsel's). I returned to the default CM10 kernel and reflashed this, so now WiFi works. Still, in Windows it doesn't work properly. While it does create a new removable disk in Computer, it gives the "Please insert a disk into drive" error when I try to open it. Haven't tested in Linux yet, but based on my earlier tests with your previous UMS solution, it probably works.
---------- Post added at 08:12 PM ---------- Previous post was at 07:22 PM ----------
Ooh, I have good news! I used Device Manager to examine the blank drive letter on the computer, and it was recognizing it basically like an SD card reader with no SD card. So, I decided to poke around some of the files referenced in your UMS script from before to check their values. When I tried to open /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file, I got an error. Thinking it may not be working properly, I created a file on my computer with the contents "/dev/block/vold/179:24" and ADB pushed it to overwrite the broken file. Instantly, my SD card mounted on the PC. I hope this is useful information for you!
Macadamia Daze said:
Silly me; the problem was an incompatible kernel (Johnsel's). I returned to the default CM10 kernel and reflashed this, so now WiFi works. Still, in Windows it doesn't work properly. While it does create a new removable disk in Computer, it gives the "Please insert a disk into drive" error when I try to open it. Haven't tested in Linux yet, but based on my earlier tests with your previous UMS solution, it probably works.
---------- Post added at 08:12 PM ---------- Previous post was at 07:22 PM ----------
Ooh, I have good news! I used Device Manager to examine the blank drive letter on the computer, and it was recognizing it basically like an SD card reader with no SD card. So, I decided to poke around some of the files referenced in your UMS script from before to check their values. When I tried to open /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file, I got an error. Thinking it may not be working properly, I created a file on my computer with the contents "/dev/block/vold/179:24" and ADB pushed it to overwrite the broken file. Instantly, my SD card mounted on the PC. I hope this is useful information for you!
Click to expand...
Click to collapse
I see... 179:24 is the sdcard itself, 179:25 (what I use) is the first partition on the sdcard... unixoid systems don't care about that, but windows seems too... I'm gonna test with 179:24 on Linux and if it works there (I'd say yes even without testing, I provide an update). Thanks for testing.
r10 is now online - fixes UMS issue on Windows.
I can't get WiFi to work with Johnsel's CM10OC Kernel - so I skiped uploading those image/zip...
You can find me in Freenode #cyanogenmod-dev if you care to sort out what's happening with the wifi on my kernel
Johnsel said:
You can find me in Freenode #cyanogenmod-dev if you care to sort out what's happening with the wifi on my kernel
Click to expand...
Click to collapse
It fails to load something and therefore can't be enabled, don't remember exact log-message right now.
I'll contact you, when I'm hacking around the next time.
This is pretty interesting.
Two things
1-Doesn't CM10 already support init.d scripts?
2-Would it be possible to swap the mountpoints for the "internal" sdcard space and the actual microSD card slot? My current method of re-mounting things right after boot is OK but not very elegant.
DivinityCycle said:
This is pretty interesting.
Two things
1-Doesn't CM10 already support init.d scripts?
2-Would it be possible to swap the mountpoints for the "internal" sdcard space and the actual microSD card slot? My current method of re-mounting things right after boot is OK but not very elegant.
Click to expand...
Click to collapse
1 - atleast not via boot.img - that's why I added it.
2 - I have an older tablet I used before (ARNOVA 7C G2) it worked with this one, so it should work with this one, too. But you should never enable UMS while some app is running... On that other tablet I had to use EXT2 or EXT4 on SD-Card else all that permission stuff didn't work (FAT only has very basic permission rules for files). Also I recommend using second partition of SD-Card for /data. (first gets used as external storage and is managed by vold - at least that is what I did on my other tablet).
I attached init.espresso.rc, so that you can play around with the mount points (re-send me the file after you're done and I can provide you a flashable zip).
Setialpha said:
1 - atleast not via boot.img - that's why I added it.
2 - I have an older tablet I used before (ARNOVA 7C G2) it worked with this one, so it should work with this one, too. But you should never enable UMS while some app is running... On that other tablet I had to use EXT2 or EXT4 on SD-Card else all that permission stuff didn't work (FAT only has very basic permission rules for files). Also I recommend using second partition of SD-Card for /data. (first gets used as external storage and is managed by vold - at least that is what I did on my other tablet).
I attached init.espresso.rc, so that you can play around with the mount points (re-send me the file after you're done and I can provide you a flashable zip).
Click to expand...
Click to collapse
That's the thing I have been wrestling with lately, what's "the best" way to manage this stuff?
It seems like the main thing that needs to be done for legacy purposes is linking the regular /storage/sdcard0/data directory over to /storage/sdcard1/data/.
One idea I had was to format the "internal" sdcard (/storage/sdcard0) with ext4, which would allow symlinks to exist there, then just remove the data directory and replace it with a symlink that points to /storage/sdcard1/data.
From what I've read, ext4 is supposed to be a better, higher performance solution, so I'm kinda curious to try it out.
It would make UMS pretty worthless to Windows guys like me, but I basically do everything via network anyways (SFTP mostly).
Is it possible to control the file systems used on the internal & external sdcards in the init? I didn't look too deeply at it cuz I don't know how to rebuild a boot.img (at least not yet)
Tested this with the current AOKP JB nightly, and it also breaks WiFi. I'm trying now to keep the rom and restore the CM10 NanoBoot backup. Fingers crossed it will be stable.
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
Since I've been mainly a lurker/reader I can't write in the threads involved:
http://forum.xda-developers.com/showthread.php?t=2224029
http://forum.xda-developers.com/showthread.php?t=2233138
http://forum.xda-developers.com/showthread.php?t=2224029&page=15
and finally:
http://forum.xda-developers.com/showthread.php?t=2216996&highlight=userdata+img+ext4
Btw, this is a screenshot of that eMMC test tool and sure enough, I've got the M8G2FA eMMC chip:
I can't get root to work and any app I try to use that require root stall and then make the Holo launcher in Slim-3.1.0-ariesve-20130403-1127-UNOFFICIAL rom (the only one I managed to get working, probably because it writes ALL partitions) drop to main screen an flash the menu window until I click the menu button.
I flashed, reflashed, tried all the "fixes" to no avail, flashed that 1.4GB userdata.img.ext4 file in odin, flashed the TEST KERNEL eMMC Brick Fix, tried replacing the boot.img in the slim package with the eMMC boot after repartitioning my external SD etc... Thing is, I tried them in so many different ways that I can't say exactly what the right procedure is and I'm not going to risk a reflash now that I've got it going until someone have a more permanent fix.
If a dev want me to do adb tests, scripts, get logs etc. just PM me and I'll supply you with what you want. I'm not all that proficient in adb usage but I learnt a thing or two when I bricked my Desire.
It is frustrating to not have a functioning Superuser/SuperSU/Rooted OS (tried flashing Root-i9001-Signed.zip among other things which does nothing) but I guess that's the price I have to pay for flashing a 3.x based CWM's without knowing about eMMC brick bugs and crap. Right now I'm running an OS with the eMMC fixed (used External SD instead of eMMC I believe) Linux kernel 3.0.70 since it's the only one I got working (albeit with a few random reboots here and there when I use the android debug bridge). Starting normal apps is quick and JB is blazing fast though. Can't change any system settings in Holo launcher (since they require root) so I edited the build.prop with the excellent adb-plugin for total commander (which I use almost exclusively to access my phone)
Good news is that it works as an unrooted phone.. Wifi, phone, e-mails etc. all work. So I'll be content for now since last night I thought I had a graveyard bricked phone I bought second hand for $95 5 days ago, esp. after bricking my Desire which made me buy this one.
Of course, Slim comes with a bunch of scripts in the init.d folder that may make things less stable/slower since I (think) I'm running my 8GB Class 10 MicroSDHC as the Internal and vice versa with that kernel fix.
I copied the logcat.txt and debuglog.txt and zipped them for anybody interested: http://www.megafileupload.com/en/file/411145/Logs-zip.html
Hi Scyphe,
I understand you do not remember the exact procedure you used but could you give me some help understanding how the "normal" procedure should work? I read all posts you linked, I've tried, but I still can't get what I'm doing wrong... What are the basic steps that are needed make it work with data on SD?
Hi,
I have a Nook HD+ which i run with CM13 (cm_ovation-ota-MOB30D.160422) and I've run now into a bizarre problem:
Last week, suddenly the nook started over night to get into an infinite reboot cycle where it goes throught nook start up screen, then cyanogemod universal boot loader screen followed by the pulsing cyanogemod logo. Sometimes it gets to the login screen, sometimes it reboots before but never did i manage to log in.
Trying to restore now older nandroid backups and/or flashing different ROMs and they all fail as they cannot properly update /system (restore fails as it fills up the filesystem even though i haven't resized /system and it definitely was not full at the time of backup; flashing ROM fails as it complains that after update /system did contain unexpected content.
Starting to tinkering with adb shell, i notice that any changes, e.g., adding or removing files, i do on the internal storage (be it /data or /system) seems to be reflected by ls in the same mount cycle but as soon as i umount and remount the device the state is restored to the old state! Similarly, any mkfs.* run without error on the various /dev/block/mmcblk0p* but nothing really changed if i remount the same device after that (i.e., content is not wiped and filesystem type is still what it was before). [the same happens if i try the various wipes/factory reset options in the recovery. No error but no effect].
Note this all happened regardless of recovery (CWM 6.0.4.6 / TWRP 2.8.7.5; the former via external sdcard, the latter internal to the nook). Also strangely, as i boot "normally" (and end up in the boot cycle) i can't run adb logcat as the device is listed as 'unauthorized'. Also for some operations with CWM it warns me at the end that ''root access possibly lost' and asks me whether i want to fix /system/xbin/su) [but either option i choose doesn't change the noticeable behaviour]. Lastly, the whole boot cycles and actions in recovery are very sluggish.
This almost sounds like there is a rootkit on the nook which masquerades the changes but ignores them to stay in control. However, googling i didn't immediately found any hits referring to such a rather sophisticated rootkit.
Did anybody ever see such a behaviour and/or have an idea what's happening? Any thoughts to reset the whole device?
-michael-
PS: Strike-out above part about unauthorized device for logcat: i was trying to do logcat from a device which apparently i've never used before for the nook; doing it on another one which i've previously used allowed for logcat to work but the log itself didn't really give any insights and the adb logcat died a few seconds before the nook rebooted, so i don't have any of these criticial parts of the log ...
Certain models of the HD+ have been known to develop a read only internal memory. It acts like it is being written to but it does not actually happen. When that happens it is not repairable.
Sent from my SM-T707V using XDA Premium HD app
leapinlar said:
Certain models of the HD+ have been known to develop a read only internal memory. It acts like it is being written to but it does not actually happen. When that happens it is not repairable.
Click to expand...
Click to collapse
Hi Leapinlar,
thanks for your feedback: Rather surprising (& unfortunate) behaviour but still better than a rootkit
I guess so my option are only to install/boot CM from an sdcard (or getting a new device)?
-michael-
BTW: to run CM from sdcard i guess i need a no-emmc ROM (even though my emmc still works read-only and i can boot recovery from it)? If so, the latest one i found is https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/ which is rather dated. Is there anywhere a new one or some pointers one what all has to be changed to make a emmc ROM turn into a no-emmc ROM so i could try changing a ROM myself? Thanks!