Here is what I did, on a new Nook Color (I guess mine is Nook Tablet) 16GB, I used MicroSD image with cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img to boot into CWM
Did factory wipe and Dalvik wipe.
Installed cm-10.1.3-acclaim.zip
Did another quick factory wipe
Installed gapps-jb-20130812-signed.zip
Everything was perfect, booted just fine, went through set up process but at setting up google account, I went to get my password from my PC, when I got back screen was not responding. Auto rotation, volume rocker, buttons all work very fast and smoothly, but I cannot touch/tab on anything.
hydeah said:
Here is what I did, on a new Nook Color 16GB, I used MicroSD image with cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img to boot into CWM
...
Auto rotation, volume rocker, buttons all work very fast and smoothly, but I cannot touch/tab on anything.
Click to expand...
Click to collapse
The ROM build cm-10-20121231-NOOKTABLET-acclaim-HD-SDC which you use is for the Nook Tablet, not for the Nook Color.
digixmax said:
The ROM build cm-10-20121231-NOOKTABLET-acclaim-HD-SDC which you use is for the Nook Tablet, not for the Nook Color.
Click to expand...
Click to collapse
I did not do anything with the ROM on it, I simply used it to boot into CWM without having to go through partitioning the SD, etc.
PS: When I was testing above "live SD card" CM10 loaded fine and was working, a little slow but I blame the slow SD card for that..
(I booted to cwm, removed the SD card with HD-SDC and then inserted another SD with cm-10.1.3-acclaim used the CWM to install)
Everything looked like they worked just fine until suddenly touch screen stopped working. I have BNTV250. Did I just totally mess this up!
I fixed the title on 1st post, maybe I posted this in wrong section?
Have you tried rebooting with no sd-card inserted?
Press and hold power so the device shuts off completly and then restart.
Thanks Moscow for moving the thread for me.
asawi said:
Have you tried rebooting with no sd-card inserted?
Press and hold power so the device shuts off completly and then restart.
Click to expand...
Click to collapse
Asawi, no, that doesn't help. I already removed the SD card (since I flashed to 10.1, it boots into 10.1)
When I press and hold power and I keep holding with n button, it then asks me if I want to format to factory settings (I guess this is nook's own formatting tool)
Also, when I try to go into internal recovery (with no SD card) it crashes.
Is there anything I can do to just try again? Can I simply flash another copy of 10.1, maybe an earlier version or even a newer version like 10.2 over this?
I was so disappointed last night, I thought about this all night, couldn't go to sleep!
You can certainly flash the ROM and gApps again an see if that helps.
asawi said:
You can certainly flash the ROM and gApps again an see if that helps.
Click to expand...
Click to collapse
Thanks.
The ROM and gApps I listed above match each other, right?
cm-10.1.3-acclaim.zip (http://get.cm/?device=acclaim)
gapps-jb-20130812-signed.zip (http://goo.im/gapps/gapps-jb-20130812-signed.zip via http://wiki.cyanogenmod.org/w/Gapps)
btw, thanks for replying, in fact I followed your instructions to install 10.1, and here you are. :good:
Before installing cm and gapps, my nook was completely stock, I guess I really did not need to do anything before installing CM, right? Did I need to root it with a custom update.zip or something like that, or is that not necessary at all? Just boot into cwm and install rom+gapps, that's it?
Edit: Re-installed CM10.1 and Gapps, still have the unresponsive touchscreen..
I have to admit I don't know what ROMs and gApps match now. I've stayed om Succulent's CM10 on my devices becasue I've been so happy with it feel no need to upgrade. You have to check the info surronding your ROM what gApps goes with it.
Edit: It looks like you have matching ROM and gApps.
asawi said:
I have to admit I don't know what ROMs and gApps match now. I've stayed om Succulent's CM10 on my devices becasue I've been so happy with it feel no need to upgrade. You have to check the onfo surronding your ROM what gApps goes with it.
Edit: It looks like you have matching ROM and gApps.
Click to expand...
Click to collapse
Thanks for checking, I just re-installed them, still touchscreen won't respond to taps.
I can just go with what you have if it works fine. Tell me how to get them on my Nook and I will, I don't care about version of Android, just need a stable android on this device so I can buy some sesame street, disney, etc stuff for the kids since Nook OS was laggy and limited. Can I just wipe all this stuff off the nook and start over?
Is there anyway to check if touchscreen problem is physical or software issue?
What's happening to you is really odd, and it could be hardware related. Unless somehow the touchscreen drivers got corrupted during install (and that really shouldn't have happened...)
I doubt going with another ROM will help, but this is what I run:
http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
There is a link to the matching gApps on that page.
asawi said:
What's happening to you is really odd, and it could be hardware related. Unless somehow the touchscreen drivers got corrupted during install (and that really shouldn't have happened...)
I doubt going with another ROM will help, but this is what I run:
http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
There is a link to the matching gApps on that page.
Click to expand...
Click to collapse
Thanks, do I need to wipe anything to get rid of 10.1 before I install this?
I will follow this:
Download the updated CM10 12/25 ROM (cm-10-20121225-acclaim-HD-SDC.zip (GCC 4.6) (http://tinyurl.com/au32v2l) and also download the GApps file (http://goo.im/gapps/gapps-jb-20121011-signed.zip)
Do the usual wipes. Factory reset, cache, Dalvik
No go, I went down to CM10 ROM above, no luck, touchscreen is still not functioning.
I am going to use recovery by following these instructions to return this to stock OS and then take it back, this is ridiculous.
I can just use this, right: http://forum.xda-developers.com/showthread.php?t=1663836
Yes, that repart.img should work. I have used it on numeroud Tablets and it has never failed me.
Nook is going back, recovered using repart, worked very well, I don't see a trace of cwm.
Touchscreen has some issues, that's for sure, thanks for all your help.
hydeah said:
...
When I press and hold power and I keep holding with n button, it then asks me if I want to format to factory settings (I guess this is nook's own formatting tool)
Also, when I try to go into internal recovery (with no SD card) it crashes.
...
Click to expand...
Click to collapse
Sounds like you still have stock recovery.
Related
I can't post in the VEGAn-TAB GingerEdition STABLE RC1 thread, so I have to post here, sorry.
I am trying to install VEGAn on my new G Tablet, and I keep getting into endless cycles.
First I rooted, then loaded CWM fine. Cleared data, cache, and dalvic. When I installed the ROM, it would hang on the Viewsonic boot screen. Tried several times, even tried fixing permissions, nothing.
So now I have tried the nvflash full restore, which made me lose CWM. Now I am not able to install CWM (.8) it just gives a loading bar and then reboots. Then when I use push power+volume up and release, which should boot into CWM, it just does the same thing (tries to install update.zip) then reboots.
I also can't boot into APX mode: when I hold down Power+Volume up, the screen is supposed to go black, but it never does. Just tries to load an 'update.zip' file that isn't there, and then reboots. This means that I can't use the nvflash method to install CWM.
Here is the current info from my about tablet:
Model UPC300-2.2
Tap UI version: 1.1-3389
Kernel version: 2.6.32.9.00000.10.8.2-dirty
Build Number FRF91
Any help would be extremely and much appreciated. Thanks!!
G
To go into APX mode, you have to hold Power plus Volume down. Get NVFlash, restore to stock rom, and then install CWM again and the flash your Rom. And don't forget to partition with NVFlash.
http://forum.xda-developers.com/showthread.php?t=861950
EDIT: I had the same issue. Installed CWM, then flashed CM7 and I wanted to change roms but I couldn't until I set up NVFlash and restored to stock and flashed VEGAn-TAB.
fp99 said:
To go into APX mode, you have to hold Power plus Volume down. Get NVFlash, restore to stock rom, and then install CWM again and the flash your Rom. And don't forget to partition with NVFlash.
http://forum.xda-developers.com/showthread.php?t=861950
EDIT: I had the same issue. Installed CWM, then flashed CM7 and I wanted to change roms but I couldn't until I set up NVFlash and restored to stock and flashed VEGAn-TAB.
Click to expand...
Click to collapse
Thanks! If I follow the steps here for nvflash http://forum.xda-developers.com/showthread.php?t=861950, won't that automatically repartition, or do I need to do something else beyond that?
generosity21 said:
Thanks! If I follow the steps here for nvflash http://forum.xda-developers.com/showthread.php?t=861950, won't that automatically repartition, or do I need to do something else beyond that?
Click to expand...
Click to collapse
You actually have to do that in CWM. Under the advance option -> partition SD card.
Check out step 7. http://forum.xda-developers.com/showthread.php?t=865245
EDIT: This will erase everything on the tablet. Rom files and all. After the partition. Mount the USB and copy the rom file onto the tablet via the usb cable.
Thanks for the help, one last question.
I applied the fix to Market, but now I'm not sure if it needed it, and I am not able to download any apps from the market. I can browse fine, just not download. Did applying the fix mess things up, and is there an easy way to fix? I tried rebooting, but maybe fix permissions is necessary?
Thanks
g
generosity21 said:
I can browse fine, just not download. Did applying the fix mess things up
Click to expand...
Click to collapse
No, you didn't mess things up. Do the fix again: delete the cache for the Market app, delete the data for the Google services app, reboot, and you should be able to download. Worked for me.
By reboot, I mean powering completely off, then manually turning it back on.
Working great now! I think it may have been the Wifi network I was using. I have read several posts where switching to a different wifi fixed the download issue.
Thanks for the help
-BoneZ- said:
No, you didn't mess things up. Do the fix again: delete the cache for the Market app, delete the data for the Google services app, reboot, and you should be able to download. Worked for me.
By reboot, I mean powering completely off, then manually turning it back on.
Click to expand...
Click to collapse
You guys hit it out the park with this rom. I have a question what browser is this? Also I like to save articles as I cruise the web and the stock browser let me create custom folders. What would be a good way to do it with this rom and browser?
First of all, I want to thank everyone working on the CM7, CM9, CM10, SGT7, TWRP, CWM projects for the Nook Tablet. I've really been enjoying trying different ROMs on my Nook Tablet.
I started with CM7, and it ran pretty well. I also tried the CM9 (NX-Fire?) port, and I liked it as well.
I have been using the SGT7+CM10+Cherry Picks and it has been fine up to the 27/9 release. I cannot run anything higher than this on my NT.
I have tried CWM (up to 6.0.1.2) and TWRP (up to 2.2.2.0) to flash the newer ROMS, but the ROMS will not boot. The screen blanks, and after a time, it goes back to the boot screen.
I also can't seem to use the CWM 6.0.1.5 or TWRP 2.3.1.1 from the SGT7+CM10 thread.
I know I have the 16GB Nook Tablet. I have repartitioned the userspace, as mentioned in other threads. I can't help but feel like I'm missing a step somewhere.
Presently, my NT is running TWRP 2.2.20 and SGT7+CM10+Cherry Picks 27/9. Any one have any hints? A thread on the boards I have missed? Any help would be appreciated.
Again, thanks for all the hard work!!
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Moved. Questions belong in the Q&A section.
Thanks
AvRS
demetris_I said:
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Click to expand...
Click to collapse
Thanks! I'll try that this weekend. I knew I was missing something.
demetris_I said:
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Click to expand...
Click to collapse
Sorry, but how does one manually update a recovery? I've tried flashing the newer TWRP from CWM as well (from an older version of CWM), and while the flash doesn't fail, it won't let me boot into TWRP, and the new CWM crashes before I can do anything. I've also tried flashing the recovery from fastboot, but I get a "bad boot magic" error when I try to boot.
Just flashed couple of days ago: pretty nice ROM
Besides annoying "SD card unmounting" problem I found that B&N Nook app does not work, it just keeps restarting, some error message shows up but goes away so quickly I can't read it. I wiped before I installed the ROM and reinstalling the app didn't help.
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
jnorrisman said:
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
There is a search function on here...
Sent from my NOOK Tablet running CM10
jnorrisman said:
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
The OP in the developers section has links to both CWM and TWRP for your use. Remember, SEARCH is your FRIEND!
play store/goomanager closing
First let me say this rom is awesome! I had no idea my nook could run this smoothly. The only problem I seem to have is that on the newest build(10/25) both playstore and goo manager will open then close. I have tried clearing the app cache, re flashing rom and gapps, full wipes then reflash. I also tried reflashing the newest gapps without success. The 10/12 build works with both play store and goo manager. I am using the 10/12 build now so no worries if it can't be fixed. Again thanks for the time and effort on an awesome rom:good:
edit: I am using the latest twrp for my recovery (also awesome). the tablet is the 16gb version
Same problem as OP, latest SGT7 not loading
I am having the exact same problem as Byron and Spurious. I've really enjoyed this series of ROMs up until the last couple, which give the same symptoms as described in the OP - the ROMs will appear to load up to a certain point, then the device reboots. For me, the the device will load up to a seemingly random point -- sometimes it will reboot itself during the boot animation, and once it got all the way to the point where it starts updating the applications. But it never actually finishes booting up before it reboots itself.
In addition, the latest CWM and TWRP do not work for me. TWRP does not come up at all, and sometimes CWM will come up and I can move around the menus for a few seconds, then it hangs. It happens whether they were flashed via fastboot or SD, I've tried every combination. I can fastboot back to TWRP 2221 or CWM 6013 and they work fine.
I've been keeping my NT (16G) updated with the latest builds since early ICS and everything has worked as described up until now. I follow all instructions to the letter as regards to wiping, etc. so I don't think I'm doing anything wrong.
Is anybody else having the same issue with these latest ROMs? Byron, Spurious - did you get yours sorted? Could it be a hardware issue?
jarvz said:
I am having the exact same problem as Byron and Spurious. I've really enjoyed this series of ROMs up until the last couple, which give the same symptoms as described in the OP - the ROMs will appear to load up to a certain point, then the device reboots. For me, the the device will load up to a seemingly random point -- sometimes it will reboot itself during the boot animation, and once it got all the way to the point where it starts updating the applications. But it never actually finishes booting up before it reboots itself.
In addition, the latest CWM and TWRP do not work for me. TWRP does not come up at all, and sometimes CWM will come up and I can move around the menus for a few seconds, then it hangs. It happens whether they were flashed via fastboot or SD, I've tried every combination. I can fastboot back to TWRP 2221 or CWM 6013 and they work fine.
I've been keeping my NT (16G) updated with the latest builds since early ICS and everything has worked as described up until now. I follow all instructions to the letter as regards to wiping, etc. so I don't think I'm doing anything wrong.
Is anybody else having the same issue with these latest ROMs? Byron, Spurious - did you get yours sorted? Could it be a hardware issue?
Click to expand...
Click to collapse
Sort of. I figured out what I was doing wrong flashing the recovery from fastboot (you apparently have to extract the .img file from the zip) but was still having the exact same issues with CWM and TWRP as you. I've managed to get a newer version of CWM installed without it hanging by using the 5 touch enabled one from here. Using this I still have the same issues with the meghd00t rom going into a bootloop though.
I noticed OP said he has repartitioned his Nook, and I have as well. I wonder if this could be causing problems, have you done this as well, jarvz? Does anyone else have any input about if repartitioning could effect this?
spurious_access said:
Sort of. I figured out what I was doing wrong flashing the recovery from fastboot (you apparently have to extract the .img file from the zip) but was still having the exact same issues with CWM and TWRP as you. I've managed to get a newer version of CWM installed without it hanging by using the 5 touch enabled one from here. Using this I still have the same issues with the meghd00t rom going into a bootloop though.
I noticed OP said he has repartitioned his Nook, and I have as well. I wonder if this could be causing problems, have you done this as well, jarvz? Does anyone else have any input about if repartitioning could effect this?
Click to expand...
Click to collapse
Yes I have repartitioned mine as well, so that must be it. I was hesitant to go to the 5-touch because it was indicated in the thread that there was no way back after you do the firmware update, and so far there is only one rom that worked with the new firmware, so I didn't want to take a chance.
At least I'm pretty sure I'm not doing anything wrong, lol.
jarvz said:
I was hesitant to go to the 5-touch because it was indicated in the thread that there was no way back after you do the firmware update, and so far there is only one rom that worked with the new firmware, so I didn't want to take a chance.
At least I'm pretty sure I'm not doing anything wrong, lol.
Click to expand...
Click to collapse
Yeah, I don't have the new touch firmware installed either. CWM worked fine, though TWRP didn't seem to work properly (maybe it needs the new touch firmware?).
Do you know if there is any mention of re-partitioning causing an issue? I looked in the rom dev thread but didn't notice anything. I guess one of us who are seeing this issue could post there to see if anyone knows what could be causing this.
I finally got it to work. My PC is running Ubuntu, so YMMV.
Here is what I did:
1. Used "gparted" to create 2GB FAT32 partition that is bootable.
2. Used the instructions in the this thread thread to create a bootable SD disk that boots into CWM 6.0.1.2.
3. CWM 6.0.1.5 just doesn't seem to work on my Nook Tablet. So, I downloaded CWM 6.0.1.3 from here
4. I downloaded the latest ROM here
5. Downloaded the latest gapps: here
6. Copied the CWM, ROM, and gapps to the SD disk.
7. Inserted the SD and booted the Nook Tablet.
8. On first boot, it boots to CWM 6.0.1.2, so I flashed the CWM 6.0.1.3, and rebooted.
9. This time it boots to Cyanoboot, so I entered the boot menu and selected EMMC Recovery.
10. From CWM 6.0.1.3, I formatted /storage, and did a factory wipe. (I didn't format /storage the first time, and the wireless would not come up.)
11. Installed ROM from SD card.
12. Installed gapps from SD card.
13. Rebooted, this time letting cyanoboot boot from EMMC.
14. Profit!
I haven't tried 6.0.1.4 to see if that would work.
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2
I am in charge of several nook tablet (16gb) devices, these devices all run on the cyanogenmod nightlies. I fixed a problem with one of them recently, After fixing the problem I noticed it needed an update. After performing the update the tablet refused to boot (either shutting down before or sometimes during the bootloader).
Rather than flash back to the previous update my genius mind decided to try flashing the acclam_update zip and then flashing back to cm. The first half of this worked out well enough and I got the tablet on stock B&N software. However when I loaded the device I realised my error. some time ago I had flashed the updated touchscreen firmware that was included with the rom. Before flashing acclaim I should have flashed stock touchscreen firmware but did not, rendering the nook's touchscreen useless on the current software. Additionally (though I was aware this would happen) I now have the stock recovery mode instead of CWM.
I have struggles with adb as it is (I originally used a bootable CWM sd card for these devices but have since cleared that sd card) and I'm fairly certain I need access to the screen to use it on this device (I believe I need to activate something in the developer settings.)
So that's my problem. If anyone knows what I should do please help me out. If you need more info tell me what you need and I'll do my best to put it up here.
Run CM10 from sd card and flash the original firmware whle running it. Ready-made image tthat you can just download and burn http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Thank you
asawi said:
Run CM10 from sd card and flash the original firmware whle running it. Ready-made image tthat you can just download and burn http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Click to expand...
Click to collapse
That should work excellently, thank you very much.
Nookuser19 said:
I am in charge of several nook tablet (16gb) devices, these devices all run on the cyanogenmod nightlies. I fixed a problem with one of them recently, After fixing the problem I noticed it needed an update. After performing the update the tablet refused to boot (either shutting down before or sometimes during the bootloader).
Rather than flash back to the previous update my genius mind decided to try flashing the acclam_update zip and then flashing back to cm. The first half of this worked out well enough and I got the tablet on stock B&N software. However when I loaded the device I realised my error. some time ago I had flashed the updated touchscreen firmware that was included with the rom. Before flashing acclaim I should have flashed stock touchscreen firmware but did not, rendering the nook's touchscreen useless on the current software. Additionally (though I was aware this would happen) I now have the stock recovery mode instead of CWM.
I have struggles with adb as it is (I originally used a bootable CWM sd card for these devices but have since cleared that sd card) and I'm fairly certain I need access to the screen to use it on this device (I believe I need to activate something in the developer settings.)
So that's my problem. If anyone knows what I should do please help me out. If you need more info tell me what you need and I'll do my best to put it up here.
Click to expand...
Click to collapse
Just now experienced the same problem. I've been trying to get my nook to boot from SD for the last couple hours and nothing. Tried booting tethered to my laptop, the factory wall charger, etc. It's a stock Nook Table with the 10point touch driver...meaning completely unusable. Could you post what tools you used if you get it working?
topdawg7793 said:
Just now experienced the same problem. I've been trying to get my nook to boot from SD for the last couple hours and nothing. Tried booting tethered to my laptop, the factory wall charger, etc. It's a stock Nook Table with the 10point touch driver...meaning completely unusable. Could you post what tools you used if you get it working?
Click to expand...
Click to collapse
What sd card are you using? Do you have another one to try? Are you using the image I linked to or something else?
Sent from my BNTV400 using Tapatalk 2
asawi said:
What sd card are you using? Do you have another one to try? Are you using the image I linked to or something else?
Sent from my BNTV400 using Tapatalk 2
Click to expand...
Click to collapse
Just used a 4gb class4 through a memory stick reader. It's working beautifully now, except I need to repartition it.
Interesting bug though, the home button won't take it out of sleep any more. Only the power button..?
Hey, guys, I made a mess.
A long time ago I decided to try out CyanogenMod for my S3 and then everything went well. I got it up and running and it was a cool ROM but I decided to stick to stock at that time. So I looked for a tutorial online and managed to get it back to stock 4.1 Android running well and as usual.
The issue I had then was that I couldn't update my phone from Google's servers anymore. Every time the phone tried to update the firmware I'd get an error, no matter if I tried it through Kies, the phone or whatever. So I decided I'd just install a ROM for a more recent version.
I found a post on a tech blog here in Brazil saying that OmniROM promised they finally had a somewhat stable version of KitKat 4.4
I went on to install it to then find a beautiful, but still very glitchy ROM. My phone froze all the time and it was starting to bother me. My initial plan was to stick to it until it got better, get the daily updates and stuff, but my phone was way too unstable for that too. So I said to myself: "Okay, no problem, so let's get a stable ROM on this little guy."
I downloaded PA 4.3 and proceeded to get it on my phone. That's when the issues started happening. I couldn't find the .zip from CWM no matter where I put it, and my sdcard1 was full because of the previous backup I created (there was a problem with that too, MD5 mismatch, but I didn't lose anything important so that's okay).
Then I did something even more stupid. I figured, why not clean up the backup and get the .zip there, so maybe it'll show up? At that point the sdcard0 (internal storage) was all different and I couldn't find the .zip for the OmniROM, but when I was on CWM it showed up instead of PA's. The problem with that is that I somehow wiped out CWM and now I can't get to recovery. If I boot up my cellphone through OmniROM, it loads up fine but I can't download the ROM Manager or the superuser from the Play Store. I'm trapped with OmniROM and it's working even less well than at first.
What should I do? Is there a way back from this? I'd really like to have my phone running again soon, I need it to keep in touch with my parents since my grandma died recently.
Thank you in advance.
EDIT: Okay, some progress. I remembered that I got CWM on the phone through Odin and went through that again. I have CWM back but still, my internal storage fails to recognize the new .zip files and only shows OmniROM's. The folder is completely different when I connect the phone to my computer. I got to see the .zip files at the sdcard1 but CWM says they're bad files. I'll trust it and redownload/transfer again. We'll see what happens.
EDIT 2: Trapped again. Can't find anything on Google. It sure sucks to be me. I can't even figure out how to get everything back to stock so I can try again. Tried turning USB debugging off but it didn't make a difference. The CWM shows me the two OmniROM .zip files and my computer shows me the PA .zip files. I'm just...
first- try to flash newer cwm based recovey. I suggest philz (is has both Odin / cwm based install):
http://forum.xda-developers.com/showthread.php?t=2002953
after flashing is complete- try to download this rom:
http://forum.xda-developers.com/showthread.php?t=2060403
and check if you can see it.
(you can put it in your internal or external sd, philz can access them both)
Before installing the new rom, I strongly recommend doing a 'wipe to istall new rom', cache wipe and delvik.
good luck
Sent from my GT-I9300 using Tapatalk
Yay, thank you! I'm not trapped anymore. The PA rom I downloaded is still "bad", but that's probably its own fault. I'll wait until NeatROM's download is complete and try with that. I'll edit this if things turn out well.
Thanks again!
EDIT: So, I tried with NeatROM and it also says it's bad. But I only tried on the external storage, so maybe that could be it. My sdcard has been returning some really funky errors when I get it on my computer so I'm worried it might be a bit compromised (and I actually found it at a bus terminal, so it never really worked properly even after formatting).
Thing is when I did the wipe I picked the option that wipes it for a new ROM, so OmniROM is gone. Is there a way to get USB connection through CWM so that I can transfer NeatROM to the internal storage? I only have this one sdcard.
EDIT 2: Finally got it! Thanks so much, amirTor, my S3 is back on track! The sdcard was the bad one, not the file. But the PA ROM didn't work anyway. I might stick to NeatROM or maybe look later. I'm gonna take a week off of all this after so much trouble.
Glad I could help (even though it seems that you pretty much helped yourself...)
1)If you got Sandisk SD card, make sure to follow my post on thread: http://forum.xda-developers.com/showthread.php?t=2614170
2)You can mount your phone to be shown in your pc even when in recovery mode: Mounts and storage-> moun usb mass storage
3)You should definitely stick with neat- the best stock (and aosp) rom there is :good::good::good:
ps- hitting the 'thanks' button will be appreciated :angel:
Done and done!