Related
I was using the AOSP ICS build posted by jt1134 (at rootzwiki dot com/topic/11697-rom-cdma-aosp-ics-cm9-build101-0418/) for the Galaxy Tab CDMA. The first couple of nightlies worked OK on the tablet, but the camera never worked right. Someone else insisted that the camera works correctly on new builds, so they suggested I use CWM to wipe system, and I took it to mean wipe everything so as to start from scratch, and I wiped /data too. Apparently this triggered the emmc erase bug or something, so now my internal SD is useless.
Nobody over in that thread appears to be willing to make a build that works around the issue. I've already tried partitioning my SD card and editing vold.fstab and updater.rc inside the ROM, but these are apparently useless unless init.rc in the boot image (zimage I guess) is changed. A person attempted that but seems to have gotten the filesystem type wrong in the build (ext2 instead of ext4), and is unwilling to make another attempt. I don't know anything about compiling a custom ROM myself. I've looked into decompressing/recompressing the zimage, but it's too much for me.
What I'm asking here is, can anyone help get a build of ICS to me that I can flash, that will ignore the internal SD and use the external? This site is awash with reports and fixes for Encryption Unsuccessful for other phones and tablets, so I'm hoping somene here can understand my frustration. I haven't been able to use the tablet for over a month now, I think, and I'm not getting anywhere on my own. TIA
Bump
I'm in the same boat after trying the same rom. I gave up on the old Tab, and doubt you'll get any help here. I'm still holding on to it in case Samsung releases a fix, but that might never happen.
PookiePrancer said:
I'm in the same boat after trying the same rom. I gave up on the old Tab, and doubt you'll get any help here. I'm still holding on to it in case Samsung releases a fix, but that might never happen.
Click to expand...
Click to collapse
Another fellow who had the same thing happen to him posted a guide over on rootzwiki on how to remove the offending chip. After removal you can partition an external SD and fiddle with a ROM and install it. The SD card will need 3 partitions, an ext4 /cache partition (not sure of the size of the regular one, made mine 512MB which I think is overkill), an ext4 /data partition (2GB is the default on these tablets), and the remaining space on the card can be used as the /sdcard partition (FAT). The only thing is I don't think you'll be able to go back to a stock rom ever again. There doesn't seem to be an easy way to change anything in roms that flash in heimdall or odin. CWM recovery based roms can be used, because they're just files in a zip. You have to change a few files referencing the locations of the partitions, including updater.sh and /system/etc/vold.fstab. On my tab the /cache is pointed at /dev/block/mmcblk0p1, the /data at mmcblk0p2 and the /sdcard at mmcblk0p3. I did manage to find a CWM recovery ROM that is based on CM7 GB 2.3.5 that works pretty good, but there are still some bugs with the camera (can't record video on front facing camera). I've resigned myself to sticking with this ROM, since it's otherwise completely stable for me, but I'm still trying to see if there's a way to transplant the working camera software from the verizon stock rom to replace the broken one I have now.
Thread for chip removal / rom installation:
rootzwiki dot com/topic/33743-external-sd-card-only-guide/
Thread for CM7 ROM "beta kang":
rootzwiki dot com/topic/4110-cdma-vzwtab-cm7-beta-kang-unofficial-1101/
Sorry about the broken links but I'm still too green on this forum to be trusted with posting actual links.
Hello All,
Suddenly have the “Couldn’t install on USB storage or SD card” problem. Quite a bit of information on the net on how to solve it, but it isnt doing it for this tablet.
I can not unmount the sdcard prior to installing/updating apps, theres simply no option for that in the setting->storage.
Second solution is to delete a file called "smdl2tmp1.asec" from one of two paths, but that file is not there.
I attached the tablet to the PC, but just see the "sdcard", not the internal memory.
I have CM10, from this forum.
Hope anyone can help me... Slowly my apps are being killed of by this problem, swiftkey and officesuite pro tried to update today, and can not even be opened anymore since...
Thanks,
Jeroen
Not sure what tab you have, but dies it have an external sd card? Internal is probably the same as sd card. It is on the i957.
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
I have the samsung 8.9 wifi tab. No external sdcard I can take out, just one that shows up as sdcard under /mnt/.
The tab is not dying on me, justn some apps show mthe error on updating them.Then afterwards those apps are not just updated, they're gone completely. I tried deleteing all dirs that I could find that seems associated with them, but the error still exists, I still get that same error on installing the app.
Thanks for replying, hope this clears up my poor description of the problem
OK, I did a full wipe and flashed CM10 and gapps, but the problem still exist. Installing apps gives me this problem... Anyone an idea?
Maybe the internal sdcard or memory is simply broke? But if so, why would the system install without problems?
Aww, my loved tab 8.9....
JeroenKl said:
OK, I did a full wipe and flashed CM10 and gapps, but the problem still exist. Installing apps gives me this problem... Anyone an idea?
Maybe the internal sdcard or memory is simply broke? But if so, why would the system install without problems?
Aww, my loved tab 8.9....
Click to expand...
Click to collapse
for whoever this is going to be useful, it turned out to be a kernel issue. Some developer confirmed it for me. so I fixed it in the end by installing a stock rom, the problem kept returning with non stock Roms...
Hello all,
I've got a GT-I9000, which have a ugly situation:
- on starting some apps generally break down with errormessage (Maps, Mail.web.de and others
- any change in the system are not persistent (passwords are lost, new Apps can not be installed, Apps can not deleted)
- Changes on internal SDCard are also completely not persistent (nor Deletion or copy files on the storrage, nor formatation)
- complete wipe are also not persistent, but after a new start the smartphone makes a initialisation-Setup (asking for settings Google account and so on), but other settings are still there (background pic and so on)
- Wipe did not work over settings and also not over the CWM recovery
- Flashing did not work for the system. Tryed one file versions, and three file versions with and without 512.pit and repart. But odin (1.85) told everything was fine while flashing
- Kernel and recovery-flashing works without a problem.
- used actual drivers, Kies not running in system (shutdown via taskmanager)
- Downloadmode, recovery works. Access via usb is possible in running system and over CWM, but changes are nor persistent (so it is not possible to flash via CWM, because I can not store data on the SDCard, and I ve actual no external SDCard..
So after searching a lot of forum enrys I can see, that there are some other guys which have the same prolem, but I found no working solution. I think that there are the following possebillities:
- the NAND is brocken in some areas
- the partitions/partition-tables are not working right
- maybe the MFT is brocken...
- motherboard defect
- negative energy from space or aliens lives in the phone
So I'm interested in you thougths, and your ideas. I ve no problem to use Linuxs or windows tools, and it would be absolutley great if someone can told me that there is a posebility to recover the phone (other way of check the ram, partitioning in other ways and so on)
What do you think,
Best regards
Solar Plexus
PS: sorryfor my mistakes and my english, but the used keyboard is poor, and my english is not good
SolarPlexus said:
So I'm interested in you thougths, and your ideas. I ve no problem to use Linuxs or windows tools, and it would be absolutley great if someone can told me that there is a posebility to recover the phone (other way of check the ram, partitioning in other ways and so on)
Click to expand...
Click to collapse
IF its a hardware problem, you need to use a box or JTAG solution to identify the problem, so just try exhausting Software solution, till you are sure its a hardware issue.
visit My Android Collections downgrade your phone to the earliest version, Eclair ( but your combo keys will not work) so you need to flash the fix or try froyo or try the i9000 rescue kit with heimdall or recovery tools to flash
or.
get an 8 gig EXT SD card, partition it as a 2 gig and 6 gig in rfs /vfat format, try flashing the ROM with speedmod kernel for i9000
Thanks at first for your Informations!
xsenman said:
IF its a hardware problem, you need to use a box or JTAG solution to identify the problem, so just try exhausting Software solution, till you are sure its a hardware issue.
Click to expand...
Click to collapse
So I'll retry at first the Software-way. But nevertheless I'm thinking about to buy also a JIG, because it seems that I flash more and more, and then it will be a good idea to have a emergency-tool to reach the download-screen. I've read sometimes that this stickers clean also the counter and triangle stuff, but I'm ot sure if this will also work for my new S3? (sorry, is a little of topic)...
xsenman said:
visit My Android Collections downgrade your phone to the earliest version, Eclair ( but your combo keys will not work) so you need to flash the fix or try froyo or try the i9000 rescue kit with heimdall or recovery tools to flash
Click to expand...
Click to collapse
OK, I'll try the downgrade and also the rescue-kit at weekend. We will see...
xsenman said:
get an 8 gig EXT SD card, partition it as a 2 gig and 6 gig in rfs /vfat format, try flashing the ROM with speedmod kernel for i9000
Click to expand...
Click to collapse
Here I'm a little puzzled. If I understand it right I have to format the SD-Card with two partitions, and then I flash the Rom on it?? I've never heard that this is possible. If yes, Odin recognize this automatically? Or does this only mean, that the I9000 have then a external Storrage which may improve the flash-process for CWM?
Thanks, and Best regards,
SolarPlexus
SolarPlexus said:
Here I'm a little puzzled. If I understand it right I have to format the SD-Card with two partitions, and then I flash the Rom on it?? I've never heard that this is possible. If yes, Odin recognize this automatically? Or does this only mean, that the I9000 have then a external Storrage which may improve the flash-process for CWM?
Click to expand...
Click to collapse
Nope, what I am looking at is, its possible your problems could be due to internal SD card corruption ( hence trying to isolate it using your External SD card to perform as its internal SD card) , as such by using the external SD card, with speedmod kernel, which is capable of reading that as your Internal SD card. In other words its like switching the cards and flashing the ROM. Read this
BTW this will work when Internal SD card totally corrupted and I am not sure it will work in partial corruption ( as you indicate) but worth giving it a try.
also look at this
yup, usb jig will work for S3 too, and triangle away works only for s2 and up, and S does not have a flash counter.
OK, sounds as we have maybe a way... SDCard switch is something what comes not in my mind, so now I have a little hope
So as I can do that only later in the weekend, I'll post my tests later.
Thanks
SP
Hello,
the external SD-Card could do the trick. I've startet in that way, format the ext-sd-card in two partitions (one reiserfs and one Vfat) and flash the modified firmware which was found in your link. Now I can start the Smartphone. but I have no acces to the SD-Card, but I can see, that the problem seems to be the internal SD-Card.
So now I'll try to use a custom-rom (maybe slim 4.1.2) and try to modify it in that way which was described in your link. If I will succseed, I'll maybe upload the package, or try to store it in the slimrom-area or whatever
By the way:
with speedmod kernel, which is capable of reading that as your Internal SD card
Click to expand...
Click to collapse
I did not find a option in the speedmodkernel for switching the internal and external SD-Card (K17). But I've try to find that while I have no ext-SD-Card in the phone, so maybe the option was hidden...
Thanks up to now, and best regards,
SP
There is no switch in speedmod kernels but it is designed to read both rfs and ext2/4 formats and partitions as such it will automatically read the available partitions as its internal SD card. And its best to use ICS or Jbean custom ROMs, when Internal SD card is unavailable due to any reason.
good luck on trials and do upload whatever here or on a new thread that may help others solve such issues.
My problem is almost similar to this , except the cause, and the seriousness
http://forum.xda-developers.com/showthread.php?t=2325101.
Could anyone report the rom problem to the official(i do not know how to access to them) and could the official give a solution? :crying:
If anyone could help me solve the problem, please tell the method step by step , i am not good at computer. If solving the problem need any files please post the downloading threads.Thanks.
I think the reason why I could not install the cm10.2 again maybe caused by load the internal memory too much. I saw someone said to install the cm would not format the data in the internal memory. When the memory is almost full , it won't install apps . Maybe it can not rewrite the rom. If so , how can i delete my personal data .?Now i can not boot the tablet , and even can not connect it to a PC. I am at a loss and very worried. I am out of USA , and it is almost impossible for me to return it to B&N to have it repaired. Could anyone here give some advice to repair it .
I asked verygreen , and he gave me an answer
There appears to be a bug in internal storage software used in Nook HDs that leads to internal storage dying under certain conditions, though the conditions are not exactly clear, but it also seems to do with a new feature added in Android 4.3
I disabled this feature on 8/15, though it's not yet clear if 8/15 nightly was built with that added or not.
The bug is not unique to Nooks too, Some Galaxy Note devices that use a very similar samsung-branded internal storage also have this problem.
But not gave the solution , could anyone solve this problem and give the solution step by step to me, thanks. i am just at a loss here
I'm having a similar issue except I can get the nook logo on screen and sometimes the Cyanoboot Universal Bootloader screen. Both freeze at that point though.
Sent from my M470BSA using xda app-developers app
Ogre6473 said:
I'm having a similar issue except I can get the nook logo on screen and sometimes the Cyanoboot Universal Bootloader screen. Both freeze at that point though.
Sent from my M470BSA using xda app-developers app
Click to expand...
Click to collapse
I think this fatal problem is very common . Does anyone else have the same problem? If so , reporting here to get the officials' attention . Now verygreen is working on it , but he hasn't given the solving date .
nookhdplus said:
I think this fatal problem is very common . Does anyone else have the same problem? If so , reporting here to get the officials' attention . Now verygreen is working on it , but he hasn't given the solving date .
Click to expand...
Click to collapse
looks like we have the same problem you can try requesting to verygreen here http://forum.xda-developers.com/showthread.php?t=2221289
Same problem here.
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
brickinit said:
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
Click to expand...
Click to collapse
Now I can nearly confirm there is a fatal bug in the 8/15 rom , so many are affected by it .I recommand others not to update to the cm10.2 before the problem is solved and the official should offshelve it from the website and give a solution as quickly as possible.
talha970 said:
looks like we have the same problem you can try requesting to verygreen here http://forum.xda-developers.com/showthread.php?t=2221289
Click to expand...
Click to collapse
BTW, which rom did you use when the problem occured ? Is it the 8/15 version?
brickinit said:
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
Click to expand...
Click to collapse
Booting to Nook loading screen (with no sdcard in) is different symptoms from the total emmc brick, because when emmc is bricked, so no loading scring could be possible.
In any case, the important part is, if somebody has a total bricked device and would like to donate it to me for further research on unbricking (and I will return it if succeeded), shoot me a PM.
Or if you have a brick and feel technically advanced enough to be able to run various custom kernels, CWMs, have adb working and know how to use it and are familiar with linux and willing to try to help, also PM me.
verygreen said:
Booting to Nook loading screen (with no sdcard in) is different symptoms from the total emmc brick, because when emmc is bricked, so no loading scring could be possible.
In any case, the important part is, if somebody has a total bricked device and would like to donate it to me for further research on unbricking (and I will return it if succeeded), shoot me a PM.
Or if you have a brick and feel technically advanced enough to be able to run various custom kernels, CWMs, have adb working and know how to use it and are familiar with linux and willing to try to help, also PM me.
Click to expand...
Click to collapse
I would donate my totally bricked tablet to you but there is too much personal info in it.
Riddleric said:
I would donate my totally bricked tablet to you but there is too much personal info in it.
Click to expand...
Click to collapse
The info is likely not recoverable without some significant effort anyway, but I certainly can understand this decision too.
Count me too in the list of bricked HD+s. I was on CM10.2 0815.
It started with a reboot, but the boot process got rebooted again. Now it would just hang on Cyanoboot screen. I have tried SD Recovery but it showed that sd card or EMMC cannot be mounted. Now it will not even boot to recovery from SD card. I have tried the bootloader which gives you an option to choose SD recovery or boot normally and the boot loader loads but it cannot boot to either EMMC or SD recovery.
Worse part is that it hangs on the Cyanoboot screen. Not sure even Nook will honor the warranty.
Edit: BTW I never installed fstrim or anything like that. It probably was the 0813 version that initiated it but I wonder why it failed in 0815 when trim has been removed?
excalibar001 said:
Count me too in the list of bricked HD+s. I was on CM10.2 0815.
It started with a reboot, but the boot process got rebooted again. Now it would just hang on Cyanoboot screen. I have tried SD Recovery but it showed that sd card or EMMC cannot be mounted. Now it will not even boot to recovery from SD card. I have tried the bootloader which gives you an option to choose SD recovery or boot normally and the boot loader loads but it cannot boot to either EMMC or SD recovery.
Worse part is that it hangs on the Cyanoboot screen. Not sure even Nook will honor the warranty.
Click to expand...
Click to collapse
if it boots into CM logo with no sdcard in, then your emmc is at least answering, chances are you can just flash stock zip from leapinlair's stock hints thread from my noemmc sdcard cwm (or his from his thread)
Also failing that if you are just interested in warranty service, boot from my noemmc cwm, adb shell in and execute this:
dd if=/dev/zero of=/dev/block/mmcblk1p1
dd if=/dev/zero of=/dev/block/mmcblk1p2
this will make the cyanogen logo display go away and you'll just have black screen on boot.
verygreen said:
if it boots into CM logo with no sdcard in, then your emmc is at least answering, chances are you can just flash stock zip from leapinlair's stock hints thread from my noemmc sdcard cwm (or his from his thread)
Click to expand...
Click to collapse
Thank you verygreen, you are very kind to respond to each and everyone.
I have tried a number of different sdcard recoveries including cwm-early7.1 and leapinlair's as well, but the tablet never finishes booting even the recovery. If it is just SD card recovery, it will keep showing the cyanoboot screen. I modified the recovery (from Leapinlair's provided file) that gives you an option to boot into SD card recovery or into Stock rom (which does not exist for me but just an option). I get the option screen but selecting the SD card recovery just freezes the tablet.
I was planning to
1) write the recovery to sdcard,
2) increase the size of the recovery partition using EASUS partition manager,
3) putting emmc recovery, stock or CM rom, and gapps in the expanded partition
4) booting into it and installing all of these
but I never get into booting into recovery with or without expanded sd recovery. I also tried every sdcard recovery out there. No success.
excalibar001 said:
Thank you verygreen, you are very kind to respond to each and everyone.
I have tried a number of different sdcard recoveries including cwm-early7.1 and leapinlair's as well, but the tablet never finishes booting even the recovery. If it is just SD card recovery, it will keep showing the cyanoboot screen. I modified the recovery (from Leapinlair's provided file) that gives you an option to boot into SD card recovery or into Stock rom (which does not exist for me but just an option). I get the option screen but selecting the SD card recovery just freezes the tablet.
I was planning to
1) write the recovery to sdcard,
2) increase the size of the recovery partition using EASUS partition manager,
3) putting emmc recovery, stock or CM rom, and gapps in the expanded partition
4) booting into it and installing all of these
but I never get into booting into recovery with or without expanded sd recovery. I also tried every sdcard recovery out there. No success.
Click to expand...
Click to collapse
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
verygreen said:
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
Click to expand...
Click to collapse
Hi Verygreen, what's your suggestion on contacting b&n? since it's still under warranty and I can't even turn it on so should I send it in for repair or replace?
Riddleric said:
Hi Verygreen, what's your suggestion on contacting b&n? since it's still under warranty and I can't even turn it on so should I send it in for repair or replace?
Click to expand...
Click to collapse
it does not really matter. "repair" is a codeword for "replace" these days, it's just they get your unit in and then send you one of their pile of repaired units, then see if they can fix yours and if they can, they add it to the refurbished pile to send to whoever send their stuff in next, or to sell through some side channel.
And of course I do recommend you to go the repair/replace route (unless you want to donate a broken unit to me for further research, of course ). Who knows, you might even win the emmc lottery and get emmc that is not buggy too.
verygreen said:
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
Click to expand...
Click to collapse
Thanks verygreen
I have noticed something else. When I connect the nook to pc without a sdcard, I can see a Blaze_Tablet while if i (try to boot) from sdcard, it shows a B&N Nook HD+ with a question mark. Does it tell you anything.
When it shows that a nook has been connected, I tried installing the drivers from LeapinLair page but windows says that no compatible drivers found. I think I have to get to install those drivers before I could connect using ADB.
When and if I boot to sdcard recovery, what should be I doing next to fix the tablet?
excalibar001 said:
Thanks verygreen
I have noticed something else. When I connect the nook to pc without a sdcard, I can see a Blaze_Tablet while if i (try to boot) from sdcard, it shows a B&N Nook HD+ with a question mark. Does it tell you anything.
When it shows that a nook has been connected, I tried installing the drivers from LeapinLair page but windows says that no compatible drivers found. I think I have to get to install those drivers before I could connect using ADB.
When and if I boot to sdcard recovery, what should be I doing next to fix the tablet?
Click to expand...
Click to collapse
see if you can mount /cache:
in adb shell:
mount /dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache
if that does not work, try reformatting it:
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
see if that succeeds.
then try rebooting again without sdcard and see if that helped.
Q&A for [Nook HD/HD+] EMMC CM11 install - updated 08/17
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Nook HD not charging since CM11 install
This morning I installed the latest CM11 build (M11) on my daughter's Nook HD. Prior to that I was using the stock ROM with no issues. Since installing the ROM the tablet will not charge; rather than showing an orange light the device shows a green light whenever the charger is connected.
It seems possible that my cable has failed at the same time as performing the install, though a little unlikely.
Thank you for your help.
CM11 - TI OMAP drivers going to get updated?
As seen here:
http://forum.xda-developers.com/nook-hd/general/updated-ti-omap-video-driver-sluggish-t2912381
Just curious if we'll see these get rolled in...
Thanks for all the hard work!
I updated my Nook HD+ from CM 11 snapshot 10 to 11 OTA , now there is frequent automatic-touches or ghost-touches on the screen without me touching the screen. Any help?
Newbie Questions - B&N HD+
Hi - i am going to flash my B&N HD+ for the first time. i have been reading the forums and instructions and have few questions.
i want to do this without SD card (i can go buy one but i if not needed, i prefer not to use it). is this possible? in the EMMC thread, i still see that the SD card must be used for the flashing/booting. so essentially, to flash CWM 6046, is it possible to not use SD card? and if so, can someone tell me how to do that?
Thanks
Ali
Ali Khawaja said:
Hi - i am going to flash my B&N HD+ for the first time. i have been reading the forums and instructions and have few questions.
i want to do this without SD card (i can go buy one but i if not needed, i prefer not to use it). is this possible? in the EMMC thread, i still see that the SD card must be used for the flashing/booting. so essentially, to flash CWM 6046, is it possible to not use SD card? and if so, can someone tell me how to do that?
Thanks
Ali
Click to expand...
Click to collapse
No, you must use an SD. There is no other way. And I suggest you use the dummies guide linked in my signature.
Sent from my BN NookHD+ using XDA Premium HD app
NookHDVolumeAdjuster for CM11 or CM10.2 ?
Is there a version of NookHDVolumeAdjuster that runs under CM11 or CM10.2 ? I am using version 1.0 under CM10.1.3. When I tried CM10.2, the sliders were all stuck at the far left. I need the sound higher volume, so I can't upgrade to CM10.2 or CM11. thanks.
Image Links?
Links to the intial sdcard image and recovery image in the original "[Q&A][Nook HD/HD+] EMMC CM11 install - updated 08/17" post are broken (nook.rootshell.ru appears down, from my perspective). Are these available elsewhere?
Thanks.
cmuser2 said:
Links to the intial sdcard image and recovery image in the original "[Q&A][Nook HD/HD+] EMMC CM11 install - updated 08/17" post are broken (nook.rootshell.ru appears down, from my perspective). Are these available elsewhere?
Thanks.
Click to expand...
Click to collapse
You can go to the dummies guide linked in my signature. In post 7 of that thread is everything you need for running CM11 on the HD/HD+.
Sent from my BN NookHD+ using XDA Premium HD app
Excellent ROM, thanks.
Nook HD plus and Gapps error status 6
Good morning,
I was working on flashing my nook last night with
cwm-recovery-ovation-6.zip
cm-20141224-NIGHTLY-ovation.zip
I have tried many different versions of stock, modular-full, modular-mini and gets a status code 6, I have successfully flashed gapps-kk-20140606-signed, but when I try to use it, the playstore just hangs like it is loading. Can someone advise the steps I need to take to successfully install a working version of gapps?
I have tried factory wiping several times and flashing the various versions of GAPPS.
Thanks in advance for any assistance that you provide.
Jim
jmcease said:
...
I was working on flashing my nook last night with
cwm-recovery-ovation-6.zip
cm-20141224-NIGHTLY-ovation.zip
I have tried many different versions of stock, modular-full, modular-mini and gets a status code 6, I have successfully flashed gapps-kk-20140606-signed, but when I try to use it, the playstore just hangs like it is loading. Can someone advise the steps I need to take to successfully install a working version of gapps?
I have tried factory wiping several times and flashing the various versions of GAPPS.
...
Click to expand...
Click to collapse
I'd suggest that you try resetting the Google Playstore app: go to Settings->Apps->Google Playstore, and do a "force stop" and "clear data" (after which you'll need to re-enter your Google (Gmail) account login/passwd).
CM11 M12 - Device Temperature
Hi all,
After staying around on CM10.2 for a long time due to a few issues with earlier snapshots of CM11, I've decided to upgrade to M12. Finding it runs great on everything I'm doing - definitely smoother performance. One thing I am concerned about is the temperature hike of my tablet, particularly when charged and running a game (in this instance, Terraria). Is anyone finding the back running quite hot? Can feel it on the screen and the left side of the device, but the temperature reading of 32C/90F doesn't seem that bad... it does feel worryingly hot though. Not sure if it's something on my end or a common thing with CM11, but I never had this on any other build.
As a sidenote - do the developers accept donations?
Audio stuttering in Rayman Jungle Run
I just did an SD card install of CM11 on a Nook HD+ and it's been working well (thanks!), except that I've noticed that the audio in Rayman Jungle Run and Rayman Fiesta Run tends to stutter / warble, making it unpleasant to listen to. Youtube and Great Big War Game sound are good. I'm using cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip with its initial sdcard image for ovation (sdcard-cwm-early9.img) from the first post. The micro SD card is Samsung class 6 16GB.
Any ideas on how to fix this?
Swap
Ponow said:
Any ideas on how to fix this?
Click to expand...
Click to collapse
Well, what I did, is I found the thread here that describes how to put B&N's OS v2.2.0 on a bootable microSD card. Once I had that working (it's not like B&N is ever going to update the firmware), I did a backup of the Nook's internal storage, and then installed CM11 on the internal storage.
That should solve your performance issues.
Note: You mention an HD+, but then refer to "Ovation", which is the name for the HD, not the HD+. You may want to edit your message to clarify the situation.
DeanGibson said:
...
Note: You mention an HD+, but then refer to "Ovation", which is the name for the HD, not the HD+. You may want to edit your message to clarify the situation.
Click to expand...
Click to collapse
ovation = HD+, hummingbird = HD.
Brain fart
digixmax said:
ovation = HD+, hummingbird = HD.
Click to expand...
Click to collapse
Oops, since the files I used to install CM11 clearly say ovation.
DeanGibson said:
Well, what I did, is I found the thread here that describes how to put B&N's OS v2.2.0 on a bootable microSD card. Once I had that working (it's not like B&N is ever going to update the firmware), I did a backup of the Nook's internal storage, and then installed CM11 on the internal storage.
Click to expand...
Click to collapse
Thanks for taking the time to reply. I would have done an internal install, but when I tried to backup the built-in firmware 2.2.0 using CWM 6.0.4.6 (from the OP), I got an error due to the /system partition being unmounted (I'm recalling this from memory; I hope I got it right). I tried using the mount option in CWM, but that failed too. I then said "screw it with the backup... I'll find another on the web", and then tried to do an emmc install of the latest milestone (M12) from the cyanogenmod download site (using SDCARD CWM-based 6.0.4.6 booted from SD... not internal memory), but the install failed with a "status 7" error (IIRC). I also tried using an earlier microSD image (sdcard-cwm-early7.1.img) and tried to install a backup of stock 2.2.0 firmware that I found from another thread here (thinking that maybe I had borked my own from an attempt at installing recovery CWM), but that finished too quickly (yet no errors), and on reboot it didn't appear to have overwritten my own stock firmware. After these efforts spanning a half dozen or so hours of reading, experimenting, etc., I was able to at least get the SD card install working, so I said screw it, I'll just use SD card. But I would really prefer an internal install as you suggest.
I wasn't able to get CWM to boot from internal memory, only SD card (Samsung 16gb class 6). I didn't try very hard though. Maybe this is the reason I can't do an emmc install or backup? Can you only backup internal memory after having booted from CWM recovery (on internal memory, not SD card)?
I was able to find a post somewhere that related the /system problem to rooting, but I never have rooted my Nook HD+ (manufactured Dec'12).
After reading more about the slow 4kB random write performance on most SD cards, I'm thinking of getting a Sandisk class 4 card, but I'd rather not go there if not necessary.
Thanks again.
Ponow said:
Thanks for taking the time to reply. I would have done an internal install, but when I tried to backup the built-in firmware 2.2.0 using CWM 6.0.4.6 (from the OP), I got an error due to the /system partition being unmounted (I'm recalling this from memory; I hope I got it right). I tried using the mount option in CWM, but that failed too. I then said "screw it with the backup... I'll find another on the web", and then tried to do an emmc install of the latest milestone (M12) from the cyanogenmod download site (using SDCARD CWM-based 6.0.4.6 booted from SD... not internal memory), but the install failed with a "status 7" error (IIRC). I also tried using an earlier microSD image (sdcard-cwm-early7.1.img) and tried to install a backup of stock 2.2.0 firmware that I found from another thread here (thinking that maybe I had borked my own from an attempt at installing recovery CWM), but that finished too quickly (yet no errors), and on reboot it didn't appear to have overwritten my own stock firmware. After these efforts spanning a half dozen or so hours of reading, experimenting, etc., I was able to at least get the SD card install working, so I said screw it, I'll just use SD card. But I would really prefer an internal install as you suggest.
I wasn't able to get CWM to boot from internal memory, only SD card (Samsung 16gb class 6). I didn't try very hard though. Maybe this is the reason I can't do an emmc install or backup? Can you only backup internal memory after having booted from CWM recovery (on internal memory, not SD card)?
...
Click to expand...
Click to collapse
It looks like you used the installation files meant for creating SD-based ROM image
See http://forum.xda-developers.com/showthread.php?t=2679899 or http://forum.xda-developers.com/showpost.php?p=42406126&postcount=7 for info/pointers on EMMC installation.
digixmax said:
It looks like you used the installation files meant for creating SD-based ROM image
See http://forum.xda-developers.com/showthread.php?t=2679899
Click to expand...
Click to collapse
This worked! I now have an emmc install of cm11 M12 from the cyanogenmod site. Since I'm running Ubuntu GNU/Linux, not Windows, I replaced steps 1 to 3 in your instructions in the above link with (at terminal prompt, with microSD card inserted but unmounted):
gunzip emmc-cwm-early3.1.img.gz
sudo dd if=emmc-cwm-early3.1.img of=/dev/sdb
I then mounted the microSD card and copied (as root) the zip files as in your link, all with terminal. The unmounted /system partition error did not appear, and the M12 install went fine! When wiping I had an error related to sd-ext missing, but from some more searching I concluded that it was benign.
Thank you for helping me out. I was starting to give up before the help I've received here. I'm generally really pleased with the performance of cm11 on Nook HD+ so far. I'm not yet noticing much difference between emmc and sd-card installs, performance-wise.
Unfortunately, the earlier performance problem (sound stuttering/warbling in Rayman Jungle Run) is still there using this internal / emmc install vs. the earlier SD-based install of cm11, which suggests that the problem is in cm11 itself. On stock firmware (version 2.2.0 I believe when tested), Rayman Jungle Run ran fine (no sound problems at all). The sound problem may be a slowdown problem, but it's not severe.