Ok, I give (well sort of) stuck at 3 birds screen for gingerbread roms.
Need one of the better brains on this one. I'm not sure if solvable without one of the big guys having one of these troublesome woot tablets.
Story up till now.
I have a G tablet, I have had one since November 2010. (black friday sears).
On my tablet I have never had any issues installing any rom/kernel and it at least booting (ones designed for gtablet)
I impressed work with them so much that during the Woot sale a few weeks back, the university bought 11 of these tablet for other techs.
So I stepped up and decided to flash them all (since tap n tap doesn't support several things such as WPA2 enterprise).
Now on the first 2 tablets I got ahold of they would not load any gingerbread rom on this forum, not vegan experementals, not either one of the asops, nor cm7 .... etc..
But they will run TNT lite and vegan 1 5b11.....
One of the units came to me with fc issues out of the box... that one loaded and ran gingerbread just fine..... (vegan experementals + pershot kernal + gapps)
The one my step father purchased from woot runs gingerbread asop + pershot + gapps fine as well
Got to work today tried a few things on another one of these tablets and it gets stuck at the veiwsonic 3 birds screen.
So these are all the methods broken down by tablet.
Tablet 1 -
Boot to stock
Mount tablet as usb
extract CW internal to device
mount usb
Reboot recovery
Reboot CW recovery
Copy over GB Asop
Copy over gapps
Flash said above
stuck at "viewsonic" screen
Ok...
Partition memory 2048/0
mount
Copy over gb asop, gb experementals, gapps
Try all of them...
Viewsonic screen..
ok
partition
mount
Copy over vegan 5.1 5.11 and pershot kernal
flash
Bingo we have vegan tab....
Hmmm..
2nd tablet
Ok lets try this again
Boot to stock
Mount tablet as usb
extract CW internal to device
mount usb
Reboot recovery
Reboot CW recovery
Copy over GB experementals
flash
stuck at viewsonc screen
partition 2048/0
mount
copy over experementals
flash
stuck at viewsonic
copy over vegan 5.1 / 5.11
flash (no kernal this time)
bingo we have froyo .... still no gb
Tablet 3- Troubled begginings
Set time zone - Force crash here....
Copy over micro sd and extract to micro sd card
Flash CW
lets try again
Copy over asop + gapps + pershot
Bam reboot and were in---- ran perfectly.
So I go... AHHA.. Must be micro SD is the key...
Tablet 4 ---
Bring over same micro sd card with me.
Use it to install CW
Install asop +gapps+pershot
froze at "Viewsonic"
WTF....
hmmmmm
Repartiton 2048/0
stuck
repartition 4096/0
stuck
repartition 4096/32
stuck
etc...
Repartitioned 2048/0
Installed vegan 5.1 / 5.11
bingo we have a live tab....
So I really don't know what is causing this. any thoughts on any of it would be greatly appreciated.
Only thought is hardware revision.. *shrug*
Did you do the stock OTA update before flashing any roms?
Pnuts said:
Did you do the stock OTA update before flashing any roms?
Click to expand...
Click to collapse
On tablet 4 I did.
I got cm7 on my woot gtab finally.
I repartitioned to 4096/256.
NVFlash
booted in to stock > plugged in to pc > usb transferred cm .8
installed cm .8
booted back to stock > usb transferred rom + gapps
boot recovery > formated boot,system,cache,data and wipe davlik cache
mount system & data
install rom then gapps
mount system ( it unmounts after rom install, cache was still mounted)
“wipe data/factory reset”
reboot
on mine- it took 30-60 secs to go from viewsonic screen to the cm boot animation and 1-2 mins it loaded up
bill1253 said:
I got cm7 on my woot gtab finally.
I repartitioned to 4096/256.
NVFlash
booted in to stock > plugged in to pc > usb transferred cm .8
installed cm .8
booted back to stock > usb transferred rom + gapps
boot recovery > formated boot,system,cache,data and wipe davlik cache
mount system & data
install rom then gapps
mount system ( it unmounts after rom install, cache was still mounted)
“wipe data/factory reset”
reboot
on mine- it took 30-60 secs to go from viewsonic screen to the cm boot animation and 1-2 mins it loaded up
Click to expand...
Click to collapse
I'll have to give this a try.
bill1253 said:
mount system ( it unmounts after rom install, cache was still mounted)
Click to expand...
Click to collapse
Hmmm.... May have something on this line. Have to check it out.
Gentlemen -- and others reading this thread:
Please don't get people started re-partitioning the way you have just posted!!!???!!!
I can't pull the reason off the top of my head -- but the 2048 and 0 has been the
standard since last November. I do remember that it will foul things up.
If you want to experiment with it, fine. But if you keep posting and pushing it you
may start another round of problems for folks that don't need problems.
IMHO.
Rev
EDIT, HERE'S THE ANSWER: The 2048 figure has been set for a long time because other values
(particularly 4096) caused issues with the Market. Wouldn't allow downloads.
The second value is a cache and the the understanding is that Android doesn't use it, so
it's just a waste of space.
Android is not well-documented, but that is the wisdom behind 2048/0.
bc
I would agree with butchconner. I am not a developer, but I am a UNIX systems administrator.
In the "old days" when RAM was hideously expensive ($7,000 for 16MB of RAM), we used a rule of thumb that swap should be 1-2.5 times the physical RAM. Disk was cheaper than RAM, hence virtual memory.
Now, memory generally exceeds requirements. I can understand why one would want not to have your swap go to flash nvram, since nvram is slow and has limited write cycles. But, letting the system swap to nvram _and_ to less swap than you have memory for just seems counter productive.
I partitioned mine to 2048/0 and it runs great.
My Archos 70 has only 256MB RAM, and I could see a benefit from 256mb - 512mb of configured swap space, as it appears memory constrained in 256MB RAM.
Hope this helps.
butchconner said:
Gentlemen -- and others reading this thread:
Please don't get people started re-partitioning the way you have just posted!!!???!!!
I can't pull the reason off the top of my head -- but the 2048 and 0 has been the
standard since last November. I do remember that it will foul things up.
If you want to experiment with it, fine. But if you keep posting and pushing it you
may start another round of problems for folks that don't need problems.
IMHO.
Rev
EDIT, HERE'S THE ANSWER: The 2048 figure has been set for a long time because other values
(particularly 4096) caused issues with the Market. Wouldn't allow downloads.
The second value is a cache and the the understanding is that Android doesn't use it, so
it's just a waste of space.
Android is not well-documented, but that is the wisdom behind 2048/0.
bc
Click to expand...
Click to collapse
fine and good and all, but red hering all the same. still can't get gingerbread to work on a large majoity of the woot tablet i have come across.
That's the best I can offer. Sorry I can't help you.
Please remember that Gingerbread is not out for the
G-Tablet and what you are using is experimental.
It may not be perfect!
Good Luck.
Rev
butchconner said:
That's the best I can offer. Sorry I can't help you.
Please remember that Gingerbread is not out for the
G-Tablet and what you are using is experimental.
It may not be perfect!
Good Luck.
Rev
Click to expand...
Click to collapse
Yea I don't think this has to do with experimental some of the bootloaders or something are fowled up on some tabs why does it work on some and not others?
My coworker and I both bought the tabs at the same time and his flash ginger no problem and mine sticks at the birds.
My Woot tablet works great, no problem with Gingerbread. I DID let it do the OTA update before I started hacking - not sure if that made a difference.
chadness said:
My Woot tablet works great, no problem with Gingerbread. I DID let it do the OTA update before I started hacking - not sure if that made a difference.
Click to expand...
Click to collapse
Wish that it did. I tried this on both tablet 4 and tablet 5 (last night) with no effect.
I rolled tablet 3 to stock 3588 from roebeet's recovery mod
Only thing I haven't tried is skipping CW all together and do it all from update.zip s .
May give that a shot today.
It's alive!
bill1253 said:
I got cm7 on my woot gtab finally.
I repartitioned to 4096/256.
NVFlash
booted in to stock > plugged in to pc > usb transferred cm .8
installed cm .8
booted back to stock > usb transferred rom + gapps
boot recovery > formated boot,system,cache,data and wipe davlik cache
mount system & data
install rom then gapps
mount system ( it unmounts after rom install, cache was still mounted)
“wipe data/factory reset”
reboot
on mine- it took 30-60 secs to go from viewsonic screen to the cm boot animation and 1-2 mins it loaded up
Click to expand...
Click to collapse
I skipped the repartition (left it at default), but I was actually able to boot into a Gingerbread ROM! I followed your instructions to the T.
An additional note for the NVFlash, I followed roebeet's instructions to do a restore via NVFlash, although, I did not update to 3588 (it said it was already up-to-date?): http://forum.xda-developers.com/showthread.php?t=861950
Thanks!
EDIT: the Tap UI version that is installed from the NVFlash I performed is 2638. I have completed the steps above again with a different ROM (CM7) and it worked like a champ again.
Do NOT partition to anything other than 2048 and 0. You WILL have market problems otherwise. If you load a Gingerbread rom and it stops at the birds you must nvflash to stock and then you will okay. I have walked about 20 people through this in the last 2 weeks and it works everytime. Something is different in the partitioning on these newer tabs and Gingerbread dont like it. It's not the bootloader and not clockwork
Yeah, I left it at 2048/0; you actually shouldn't have to repartition it with the default settings anyway. I haven't had a problem and haven't needed to repartition it when going between Gingerbread ROMs.
thebadfrog said:
Do NOT partition to anything other than 2048 and 0. You WILL have market problems otherwise. If you load a Gingerbread rom and it stops at the birds you must nvflash to stock and then you will okay. I have walked about 20 people through this in the last 2 weeks and it works everytime. Something is different in the partitioning on these newer tabs and Gingerbread dont like it. It's not the bootloader and not clockwork
Click to expand...
Click to collapse
Any chance you could walk me through it? I'm not quite sure what I'm doing wrong otherwise.
You can join irc but the first thing that will be asked is do you have the drivers installed and can you see the tab from a pc.
Freenode channel #tegratab
Related
I currently have cwm .8 and vegan 5.1.1 running without issue and backed up.
I have tried several different gingerbread roms and all of them get stuck on the static image screen before the boot animation.
I have made sure to wipe boot, system, data, dalvik, and cache as well as running Calkulin's Format.zip all prior to rebooting. I also have tried installing the ROMs with or without the Google apps addition. All with the same results.
Internal SDcard partitioned to 2048/0
Is there anything else I can try?
Are you sure they are all hanging at the boot screen? Most of the roms first boot takes a awhile for the cache to get filled with the data it needs to perform.
After the first few boots everything usually goes smooth from then on.
Roxxas049 said:
Are you sure they are all hanging at the boot screen? Most of the roms first boot takes a awhile for the cache to get filled with the data it needs to perform.
After the first few boots everything usually goes smooth from then on.
Click to expand...
Click to collapse
I am a patient fellow. I waited 20min at minimum for each ROM and none have ever made it to the animated boot screen.
I'm having the same issue with mine.. vegantab 5.1 works fine..
none of the gingerbread based roms get passed the viewsonic logo for me.
Same problem here.
All of the GB roms freeze at the android screen.
I have tried everything, I am a serial flasher on my D1 and on the gtab with the froyo builds and consider myself very familiar with the process and it still confuses me...
These are all new gTabs right? Have any of you repartitioned the internal sdcard yet? That option is in CWM recovery. There is a thread on it somewhere too. Basically it wipes the /SDCARD space and repartitions it. The FAQ thread has information on partition sizes too: http://forum.xda-developers.com/showthread.php?t=874258
ramerco said:
These are all new gTabs right? Have any of you repartitioned the internal sdcard yet? That option is in CWM recovery. There is a thread on it somewhere too. Basically it wipes the /SDCARD space and repartitions it. The FAQ thread has information on partition sizes too: http://forum.xda-developers.com/showthread.php?t=874258
Click to expand...
Click to collapse
I have been using the highly recommended 2048/0 as I did not see any details in the threads for the GB ROMs detailing otherwise. Sorry I forgot to mention that in my OP.
-edit-
Repartitioned to 2048/0 and also tried 4096/256. Issue persists
TNT lite 4.40 works Great.
bambamishere said:
TNT lite 4.40 works Great.
Click to expand...
Click to collapse
still a 2.2 ROM
Some progress! Following these steps will erase EVERYTHING from your device including the internal SD. Backup everything before you start.
After doing another restore to stock using nvflash
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
copy vegan ginger edition over to internal sd
it installed and booted up!
-edit-
and then I tried to install gapps and it won't boot again
Ran out of battery power to fully test but finally got it to boot after gapps install. Here are the steps I had to take:
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
Restore to stock using nvflash
did not let it boot into stock
reinstall .8 cwm from external sdcard
in cwm copy vegan ginger edition.zip and gapps.zip over to internal sd
Installed ROM then gapps
reboot
(note: after returning to stock I did not wipe anything with cwm)
genei.09 said:
Ran out of battery power to fully test but finally got it to boot after gapps install. Here are the steps I had to take:
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
Restore to stock using nvflash
did not let it boot into stock
reinstall .8 cwm from external sdcard
in cwm copy vegan ginger edition.zip and gapps.zip over to internal sd
Installed ROM then gapps
reboot
(note: after returning to stock I did not wipe anything with cwm)
Click to expand...
Click to collapse
Good work, quick question, you said you reinstalled cwm from external sdcard, does that mean you used the "cwmod_microsd.zip" from the "[STICKY][GUIDE] Install ClockworkMod, a ROM, Flash Player, and the Market Fix" post?
I have always used the internal one and was wondering if that made a difference.
wadsface said:
Good work, quick question, you said you reinstalled cwm from external sdcard, does that mean you used the "cwmod_microsd.zip" from the "[STICKY][GUIDE] Install ClockworkMod, a ROM, Flash Player, and the Market Fix" post?
I have always used the internal one and was wondering if that made a difference.
Click to expand...
Click to collapse
Yes that should be the same file. Looks like it was recently renamed as I had it labeled external rather than microsd. It isn't really a different cwm I used it so I wouldn't have to let the stock OS boot up and I kept it on the external sdcard so when I repartitioned the internal card I wouldn't loose it. I reloaded to stock many, many, many times trying to get this to work.
I'm currently using the experimental VEGAN Ginger Edition. It has some nice features but the videos for Dungeon Defenders don't play, and the keyboard is a little strange.
genei.09 said:
Ran out of battery power to fully test but finally got it to boot after gapps install. Here are the steps I had to take:
wipe everything via cwm (boot, system, data, cache, dalvik)
repartition sd to 4096/256
Restore to stock using nvflash
did not let it boot into stock
reinstall .8 cwm from external sdcard
in cwm copy vegan ginger edition.zip and gapps.zip over to internal sd
Installed ROM then gapps
reboot
(note: after returning to stock I did not wipe anything with cwm)
Click to expand...
Click to collapse
This work for anyone else? These Woot batches are introducing some issues.
I've had my tablet since early Feb. and I had issues with GB roms when I started trying them too. I found that the steps that worked best for me were pretty much the same as above. Mine are assuming that the tab is coming from something other than stock...
Wipe data,cache,dalvik and Battery Stats... (not sure the battery stats wipe matters)
NV Flash back to stock
Load CWM .08
Repeat Wipe
Load GB Rom
Repeat Wipe
Load rom devs recommended gapps version
Reboot
This USUALLY results in success. I still have mixed results getting gapps installed with some GB roms...once in a while I have to change up the steps and reboot PRIOR to gapps.
I've only had to repartition a few times, but the 2/0 option is the norm for me...and I usually only have to do this after I've made a big mistake, or things start to act "off" with the tablet.....
I think I read in one of the posts over on the dev side that most of the roms are written with the stock bootloader in mind and that it's just good policy to learn NVFlash and use it if you have any issues going from one rom to another.
I've been spending A LOT of time on this site since I got my gtab, too much probably. Usually, about 6 pages into a rom post, the answers to whatever issues we have with install are answered. It seems like mostly page 1 - 4 are people excited to flash...or saying thanks... pages 4 to like 10 are full of the answers to the questions "Why can't, Why didn't, how come..."...and then 10 - 10000 are just plain fun to read. ;-)
Good luck, this Tab is a ton of fon. I was super excited when the woot sale went down. I figure if even 4 or 5 more programmer types ordered one....that could mean 4 or 5 new roms for us to play with!
pceasar said:
This work for anyone else? These Woot batches are introducing some issues.
Click to expand...
Click to collapse
Worked for me last night. Using external sd CW.... Did not work from internal....
*shrug*
so far
3 tablets - internal memory cw install --- only vegan / tnt lite
2 tablets - 1 install of asop (gingerbread) 1 install of vegan GB experementals - one with clymson kernal one with pershot....
I'm just saying...
akodoreign said:
Worked for me last night. Using external sd CW.... Did not work from internal....
*shrug*
so far
3 tablets - internal memory cw install --- only vegan / tnt lite
2 tablets - 1 install of asop (gingerbread) 1 install of vegan GB experementals - one with clymson kernal one with pershot....
I'm just saying...
Click to expand...
Click to collapse
What process did you follow is it the same as tdg2100
Edit: I follow the same process as TDG2100 and it works w00t!! I think this should be included in a sticky somewhere people are going to struggle with this if they don't know how to get out of it.
Also question. Does this mean EVERY ginger ROM I have to flash has to go back via the NVFlash ROM route or can I just upgrade? Just curious, though at this point CM7 w/TT I doubt I'll be changing soon.
tdg2100 said:
I've had my tablet since early Feb. and I had issues with GB roms when I started trying them too. I found that the steps that worked best for me were pretty much the same as above. Mine are assuming that the tab is coming from something other than stock...
Wipe data,cache,dalvik and Battery Stats... (not sure the battery stats wipe matters)
NV Flash back to stock
Load CWM .08
Repeat Wipe
Load GB Rom
Repeat Wipe
Load rom devs recommended gapps version
Reboot
This USUALLY results in success. I still have mixed results getting gapps installed with some GB roms...once in a while I have to change up the steps and reboot PRIOR to gapps.
I've only had to repartition a few times, but the 2/0 option is the norm for me...and I usually only have to do this after I've made a big mistake, or things start to act "off" with the tablet.....
I think I read in one of the posts over on the dev side that most of the roms are written with the stock bootloader in mind and that it's just good policy to learn NVFlash and use it if you have any issues going from one rom to another.
I've been spending A LOT of time on this site since I got my gtab, too much probably. Usually, about 6 pages into a rom post, the answers to whatever issues we have with install are answered. It seems like mostly page 1 - 4 are people excited to flash...or saying thanks... pages 4 to like 10 are full of the answers to the questions "Why can't, Why didn't, how come..."...and then 10 - 10000 are just plain fun to read. ;-)
Good luck, this Tab is a ton of fon. I was super excited when the woot sale went down. I figure if even 4 or 5 more programmer types ordered one....that could mean 4 or 5 new roms for us to play with!
Click to expand...
Click to collapse
Worked for me also.
Matt
I had the same issue and I fixed it by:
1) Boot to clockwork
2) Go to mounts and storage and click "format system"
3) Then wipe data/factory reset
4) After that clear the cache
5) Then go to advanced and wipe dalvik cache
6) Install cm7
7) Install gapps
8) Reboot
Now everything is working for me.
Hi XDA !
I also am stuck at the ViewSonic Birds window - I know how to install CWM etc but I cannot get this to be recognized on a PC via USB. Its almost like the USB isnt started on the GTablet. How do I reboot this thing? Holding down the Power and + button has no effect...
Hi everyone,
First time poster but have been reading and browsing for a couple month now and have been able to find fixes for all the issues on my own. I have however had this one issue from the beginning and have not found any fixes or even the issue being mentioned (been using TnTLite the entire time, going up the versions from early 3's to now 4.4).
When my Gtab goes to sleep or even sits idle for a while my WiFi just stops working. The connection is still there and Gtab thinks it's connected but I can't access the net until I turn Wifi off and on and then it works until I let it sit or the screen shuts off. This is annoying at the least and I would love to fix it, even if I have to go to a different ROM (but I do like TnTLite above others).
Does anyone find version 4.4 more laggy than 4.2.5? Gtab is just not as responsive and I seem to have a Flash issue where net videos crash after working for 1-15min.
Also I have CWM 0.8 and when I try to flash with a MicroSD I keep going back into CWM. I changed SDCARD to SDCARD2 in the common file but still my card is not being read. Basically if I want to install the stock ROM and nothing else I can't cause it only boots into CWM and not the SD card. I do have the card formated in FAT32 at 2048. Am I missing something, do I need to uninstall CMW first somehow?
If you re-read the first post in the TnT Lite 4.4 thread, you'll see that you can toggle the CWM back to stock recovery with some built in commands.
Yeah, I saw that as one of the options but I want to be able to patch via the micro SD card and CWM seems to be interfering with that. I mean if I revert to stock with CWM I will still have CWM installed. I want the true original state but more than that I want the MicroSD card recovery to work.
Switching to stock recovery removes CWM and will allow you to use the MicroSD to install. All you have to do is put a file named "command" in the recovery folder on your MicroSD card with the following contents:
--update_package=SDCARD2:/update.zip
When you reboot into recovery it will find that command and execute the update.zip on your MicroSD card.
Thank you!
It was my suspicion that CWM is interfering but I also had recovered from the SD card a couple times even with CWM installed, at least I think so, but it is good to know. I'm also still having issues with net video crashing now and again. The screen goes white and I have to reboot. Started when I installed 4.4 and now that I reverted back to 4.2.5 it is much better but still I had it happen just now and it never did before 4.4. The upgrade to 4.4 also slowed the tablet down which did improve as I went back to 4.2.5.
Try going into CWM and wipe dalvik cache and also do fix permissions, usually cures most of those problems after going from one version to another.
What exactly am I loosing when I wipe delvik cache, do you know? And thanks for the suggestion, haven't tried that yet.
Vigilantys said:
What exactly am I loosing when I wipe delvik cache, do you know? And thanks for the suggestion, haven't tried that yet.
Click to expand...
Click to collapse
Here is a post that explains it
http://forum.xda-developers.com/showpost.php?p=3844295&postcount=5
MAJOR UPDATE 2/22/12: While the process hasn't changed too much, the key files have all been replaced for greater flexibility, and they are NOT compatible with the old method using rookie1's prep-dualboot zip. See this post for an update path from the old method to the current one.
This guide details how to repartition your internal storage and install two operating systems, or ROMs, side by side. If you're looking for a SD install that leaves the Nook's main storage untouched, you're in the wrong place (see my sig).
This guide takes advantage of the multiboot functionality built-in to CM7.1 nightlies since about #140. As such, it is not compatible with CM7.0.x builds or with earlier boot menus.
What you'll get: Whatever two ROMs you install, each will have a nearly 2GB /data partition for apps and they will share a nearly 2GB /media partition for storage, and both will have access to the SD card for more storage. At startup you will see either a small green bar labeled "CyanogenMod," or the word "cyanoboot" in blue. Both boot menus work the same:
Do nothing, and your primary system will boot
Hold down both volume buttons, and your alternate system will boot
Hold down 'n' for a more detailed boot menu
Hold 'n'+power and recovery will boot (if you installed CWM internally).
All of these actions must be taken in the first couple seconds, before a "loading" message appears below the logo. Once you see a confirmation message, you can release all buttons.
DISCLAIMER: As usual, YOU are responsible for changes YOU make to YOUR device. This process is intermediate difficulty level. It probably shouldn't be the first thing you've ever done with ClockworkMod Recovery, and you probably shouldn't just follow the steps if you don't understand them. If you don't know how your NC is currently partitioned, turn back now. If you want to preserve your warranty, turn back now. Here be serpents; be so warned.
Following the guide as-is with all default options gets you a stock 1.4.1* install on secondary and a CM7 install on primary. I hope you can figure out what to substitute where for different results.
*I don't have access to a CWM-flashable 1.4.2 zip right now, but there are instructions for making one here.
The Guide
Prerequisites:
CWM on either SD or internal recovery (internal recommended)
Wi-Fi access
Materials:
repartitionDual2GBdata
BNpri2alt
reformatData
1.4.1-keep-CWM (IF you're not starting with an up-to-date stock install)
CM7.1+ OR MiRaGe's CM7.2 OR unofficial CM9 nightlies (w/ compatible gapps)
CM7 gapps(look near the bottom of the page)
Steps:
Put all materials in your SD card's root directory (DO NOT UNZIP).
Boot into CWM.
From CWM main menu, "backup and restore" and "backup."
From CWM main menu, "install zip from sdcard," and "choose zip from sdcard."
Choose the repartitionDual2GB file.
Reboot recovery. If you have internal CWM and no boot menu, you may need to use the rhythm method:
verygreen said:
hold nook N key and then press and hold power until the {first} message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the {first} message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long
Click to expand...
Click to collapse
Repeat step 4 and choose reformatData
If your backup in step 3 was stock, you can "backup and restore" then "restore" and skip to step 13.
Otherwise, repeat step 4 and choose 1.4.1-keep-CWM.
When it finishes, hold the power button to shut down, remove your CWM card (if applicable), and power back on.
Complete B&N registration process¹
Power off and boot back into CWM (may require rhythm method above).
Repeat step 4 and choose BNpri2alt.
From CWM main menu, in "mounts and storage," format system, data, and cache.
From CWM main menu, choose "Advanced" and "Wipe dalvik cache."
Repeat step 4 and choose CM7 update zip.²
Reboot into main partition and set up Wi-Fi.
Reboot into alt partition (hit both volume buttons at once on "CyanogenMod" loading screen) to make sure it's working.
optional: install gapps, keysmod, etc from CWM.
¹Any mods you want to make to stock, do it now: update to a newer version, root with Manual Nooter (if rooting 1.4.x firmware, follow the linked instructions but use MN 5.12.20), flash keysmod, overclock kernels, or anything else CWM-flashable.
²If you backed up an existing CM7/9 install in step 3, then after step 16 just install gapps, install keysmod if you want it, then from CWM's main menu, Backup & restore > Advanced Restore, and restore data only from your most recent backup. When you boot into CM7 (not tested with CM9), it will be just like you left it.³
³Steps 17 and 18 may look unnecessary, but several users experienced force closes in their CM7 installs when they didn't take these steps.
Other Resources:
CMpri2alt: Moves a CyanogenMod install from the primary partition set to the alternate partition set
BNalt2pri: Moves a stock install from the alternate partition set to the primary partition set
CMalt2pri: Moves a CyanogenMod install from the alternate partition set to the primary partition set
Revert dual boot: deletes the alternate partition set and alternate boot files. Does not restore stock partition sizes, but must be run prior to partitioning back to stock.
1.4.1 full restore: removes CWM from internal recovery, does not affect partitioning
1.4.1-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Steps to back up and/or update both partitions
Instructions to rename boot files created with j4mm3r's old multiboot
Possible fix for rooted stock boot-looping at 'n' screen on secondary
Credits:
repartitionDual2GB and reformatData provided by DeanGibson
1.4.1 zips provided by rajendra82
possible boot-loop fix provided by sryan1983
BNpri2alt, BNalt2pri, CMpri2alt and CMalt2pri are minor alterations of DeanGibson's files
revert-dualboot is a minor alteration of rookie1's remove-dualboot
Racks11479 provided key info for the above alterations
________________________________________________________
Old Resources (Do Not Use with Current Method):
prep-dualboot
froyo-to-dualboot
Remove dual boot: returns partitioning altered with prep-dualboot to stock (1GB/5GB, non-blue-dot)
1.2 full restore: removes CWM from internal recovery, does not affect partitioning
1.3-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Video documenting setup for a CM9 (Ice Cream Sandwich Alpha) dual boot with Nook Color stock 1.4.1
Old Credits:
1.2 full restore provided by nemith: thank here
prep dual boot and remove dual boot by rookie1: thank here
froyo-to-dualboot from jasoraso: thank here
1.4-to-alt from jasoraso: thank here
You can thank me with the button below, or if you feel real strongly about it, you can make a donation at my blog.
UPDATE 5/25/12: Removed the prerequisite for 1GB/5GB partitioning. A little bird named jicama confirmed that the newer partitioning script doesn't care if you start with a blue dot NC. Prep-dualboot would carve the alt partitions out of /media, which doesn't work if /media's not big enough. RepartitionDual just deletes the last three partitions (/system, /data and /media) and makes new partitions from the now-unallocated space, so as long as you have the right number of partitions, it doesn't matter how big they are.
Added to my Subscribed list !! ...Thank you
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
oppy said:
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
Click to expand...
Click to collapse
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7? Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Taosaur said:
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7?
Click to expand...
Click to collapse
Yes.
Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Click to expand...
Click to collapse
Okay, I'll do that and post results. Thanks.
EDIT: Looks like that did it. Seems to work fine, other than some app FCs, which, from what I've read, are fairly common. Thanks for the assist!
I worked that info into the OP. I've done this process twice now without taking those steps and without getting FCs, but you're not the first to report them.
I was a bit confused about the backup and restore part also. Seeing as my Nook was stock to start, I probably didn't need to do that step, and might have actually caused a problem or two by restoring data that didn't exist to start.
Still working great. The only FCs I've had so far were while trying to run Facebook.
Excellent guide! Thanks for all the work on this, it works great.
This is an awesome guide. Thanks for the help. I've been wanting to do this for a while.
Thanks man.
I appreciate you putting all the tools in one place, and I especially appreciate you posting that us blue dot people needed to repartition to 1gb data before doing this; I should've figured that, but I didn't for some reason.
Moving 1.3 to the dual boot partition as I type
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
SCrid2000 said:
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
Click to expand...
Click to collapse
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Taosaur said:
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Click to expand...
Click to collapse
Thanks man. That's what I figured.
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
This is the best thing EVER. I got sick of the nook app on my CM7 build, so this worked flawlessly.
I am running the CM7.1.0 RC1 build, and everything runs smooth as silk
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3. You would have to use j4mm3r's multiboot and the matching stock-to-secondary file found in this thread: http://forum.xda-developers.com/showthread.php?t=1156909
Nevermind, dumb question.
Updated with a link to CM7.1 stable
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
TomMelee said:
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
Click to expand...
Click to collapse
I'll just leave these here:
Taosaur said:
this guide is not compatible with CM 7.0.x sta(b)le releases, nor branch ROMs based on those builds
Click to expand...
Click to collapse
Taosaur said:
Phiremod 7+
Click to expand...
Click to collapse
Taosaur said:
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3.
Click to expand...
Click to collapse
Try installing regular CM 7.1.
rabi347 said:
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
Click to expand...
Click to collapse
Sounds like you got close. I would say start over at step 5.
UPDATE: Stock ATRIX is SLOW AS HELL.
Read my latest posts! I've since FACTORY RESET+Fully wiped!
||
||
||
V
====
Hi there, I'm running Android 2.3.4 (4.5.91) Atrix (rooted) and have extremely slow write speeds. I have seen other users with other newer phones on Android 4.1.1 that seem to steer towards TRIM not being used. They have since fixed this in Android 4.1.2 according to the post, but doesn't help me with an Atrix . I tried to fix my phone with: several apps on the market like forever gone that write and fill your drive up then erase. I tried to use mount -o remount,discard - but discard is not allowed with this phone. I've tried deleting files on my internal and moved a TON of my apps to sdcard (Still internal storage just /sdcard/* because I'm using no actual SDCard) and still the problem exists. I've tried changing my schedulers and buffer with them to no avail. I've tried using the PDSFIX someone else posted here, and that didn't work either. Tried clearing dalvik / app cache entirely, no change either.
Kind of at a stand-still here as I don't want to factory restore my phone to fix a bug. If I'm going to be factory restoring it and spending an entire day doing so, I'd rather just get a new phone and start over where a problem clearly exists over time with the old phone, and I'll end up having to re-do it over and over, and there STILL isn't a guarantee that it will fix when i factory restore! So.. I need help! If there's ANYTHING you guys can think of that I might be able to do to get my phone back to "working" I would appreciate it! Even updating apps from market or opening an app normally that will use write speed at all, will hang and mostly offer to force close/wait.
APP Storage (Assuming /data?)
1.3GB Used - 665MB Free.
Internal Storage (assuming /sdcard?)
7.5GB used - 3.2GB Free.
Using Androbench:
/data (ext3)
SEQ RD: 16.65MB/s
SEQ WR: 0.22MB/s
RND RD: 1123 IOPS
RND WR: 33 IOPS
Buffer: No
/sdcard (vfat)
SEQ RD: 20.72MB/s
SEQ WR: 2.36MB/s
RND RD: 1145 IOPS
RND WR: 65.78 IOPS
As you can see: /sdcard is getting SEQ 2.5MB/s write and RND WR of a bit lower around 0.8MB/s which is clearly higher than /data.
I've read just about every thread on slow speeds here and most deal with a physical SDCard which I do not have one installed.
http://sourceforge.net/projects/fstrim/?source=dlp
I found a source for fstrim.c but I need to compile it on my phone which costs 3$? I'm afraid it would be a wasted purchase if it didn't work. As far as I know ext3 does not support "discard" option so you need to CRON job fstrim -v / (I have seen this as a solution for others)
Does discard option work with vfat? Or it seems maybe TRIM is the issue here. If I could find a compiled version I could use ON my phone to test, that would be awesome. I tried searching everywhere for an APP to do TRIM commands on your filesystem but came up empty handed.
UPDATE: Looks like TRIM doesn't work on Android 2.3.4. Looks like I'll be getting rid of my phone instead of fixing it, as it's impossible to fix apparently. Does not support -discard or TRIM, and have no feasible way to fix. I kind of liked the Atrix but it seems I will not be buying another Motorola product. Stay away from the ATRIX, it's JUNK.
Just saw they offer 100$ if you upgrade from Atrix 1 to Atrix HD but there are far better phones on the market now to even bother. WHY? Motorola, you need to take your head out of your ass.
Have you tried ROM Manager? It has a setting for boosting SD read/write (increase value from 128 to 2048 or 4096.) Hmm.. I dunno what I'm talking aboutz.
If you are that frustrated and will buy a new phone anyways, why not factory reset your phone and get it done and over with? At least there's a small chance you can fix your problem in Atrix as a principle.. And give you a reason to give in to the nagging innards about buying a shiny new Galaxy Note2 :cyclops: Atrix is still a nice back-up phone...
doqmyk said:
Have you tried ROM Manager? It has a setting for boosting SD read/write (increase value from 128 to 2048 or 4096.) Hmm.. I dunno what I'm talking aboutz.
If you are that frustrated and will buy a new phone anyways, why not factory reset your phone and get it done and over with? At least there's a small chance you can fix your problem in Atrix as a principle.. And give you a reason to give in to the nagging innards about buying a shiny new Galaxy Note2 :cyclops: Atrix is still a nice back-up phone...
Click to expand...
Click to collapse
I installed that and didn't see the option. I have titanium backup and titanium media sync but I'm afraid a recovery would be at .5MB/s write and that could take many hours, haha.. umm I guess the reason I haven't factory restored is because this problem will reoccur without a solution. This is only logical. Simply factory restoring my phone every time I fill it up with anything or take long video,etc is not a solution to anything.
Whoops, sorry, my bad, not ROM Manager.. but ROM Toolbox Pro.
On the 1st page of ROM Toolbox Pro, swipe downwards, and presto! SD speed up option
Maybe if you reset it once, AND reinstall the ROM, (after wiping Dalvik and data with the toilet paper..) the problem might go away. Most probably a ROM corruption or app afficted error.
Doesn't hurt to try, especially after purchasing a shiny brand new Note 2..
Sent from my MB860 using xda premium
doqmyk said:
Whoops, sorry, my bad, not ROM Manager.. but ROM Toolbox Pro.
On the 1st page of ROM Toolbox Pro, swipe downwards, and presto! SD speed up option
Maybe if you reset it once, AND reinstall the ROM, (after wiping Dalvik and data with the toilet paper..) the problem might go away. Most probably a ROM corruption or app afficted error.
Doesn't hurt to try, especially after purchasing a shiny brand new Note 2..
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Tried setting the cache to all the different settings, nothing changed really. If anything, it got worse so I uninstalled, heh.. I've been uninstalling any apps I can think of but nothing is working.
I'm really trying to figure out the damn problem so I don't HAVE to upgrade my phone... I'd rather not waste my 2-yr upgrade on a 300$ upgrade now when there are new devices coming out in a few months :\
Thanks for the help though. Going to mess around with it a bit more I guess.
UPDATE: I wiped my phone COMPLETELY. Unlocked bootloader, and tested, nothing. Same speeds, SLOWER if anything!?!?!?!?
I updated to the newer version 4.5.141 and..
moto-fastboot erase system
moto-fastboot erase boot
moto-fastboot erase webtop
moto-fastboot -w (wipe data)
Used CWM to format /cache
Soo. Wat now? hah..
If you have fully wiped and reset it, it would most probably be a hardware fault, no longer a ROM or setting problem. Probably your NAND has worn out (overused?) or has factory defect that became apparent only recently. You can try using CWM (advanced) to convert ext3 to ext4 the /cache, /data, etc, and see if it helps in any little way or if any. If no effect, and If it's still usable, then just use it as a secondary or back-up phone.
(epinter's CM10.1 ROM would be nice for that..)
or you can just trade it in for a new phone.. Good luck..
doqmyk said:
If you have fully wiped and reset it, it would most probably be a hardware fault, no longer a ROM or setting problem. Probably your NAND has worn out (overused?) or has factory defect that became apparent only recently. You can try using CWM (advanced) to convert ext3 to ext4 the /cache, /data, etc, and see if it helps in any little way or if any. If no effect, and If it's still usable, then just use it as a secondary or back-up phone.
(epinter's CM10.1 ROM would be nice for that..)
or you can just trade it in for a new phone.. Good luck..
Click to expand...
Click to collapse
Interesting, my mother has the same phone and got it a bit after mine, her stats:
SEQ RD: 17MB/s
SEQ WR: 2.68MB/s
RND RD: 4MB/s 1027IOPS
RND WR: 0.16MB/s 42IOPS
So. It looks like Motorola designed these NAND chips to fail after a year or two causing the need to upgrade the phone to a new model.. I can't come up with any other solution other than they used cheap as hell hardware?
dosmac said:
Interesting, my mother has the same phone and got it a bit after mine, her stats:
SEQ RD: 17MB/s
SEQ WR: 2.68MB/s
RND RD: 4MB/s 1027IOPS
RND WR: 0.16MB/s 42IOPS
So. It looks like Motorola designed these NAND chips to fail after a year or two causing the need to upgrade the phone to a new model.. I can't come up with any other solution other than they used cheap as hell hardware?
Click to expand...
Click to collapse
I have read your posts and I'm wondering how the phone feels when you're using it? (as opposed to looking at the stats)? I must admit you got me confused with all attention to write speeds ect.
As you've rooted/unlocked the bootloader what would you think about installing a custom rom? Something like CM7.2
It shouldn't take long. You've already got Titanium backup so you can back up your apps that you downloaded (not system apps) and install them after you have installed your new rom. It really shouldn't take long.
There is also a zip file called 'ram fix' which I've put here which might help after you've installed CM7.2 (it was designed for CM9/10 but there's no harm in trying it out)
You could also install a kernel which overclocks your CPU speed, thus making your phone faster.
If you decide to go down this route you'll need to do the following:
download CM 7.2/Gapps/Ramfix/Faux 1.3 overclock kernel and install on internal sd card
back up apps using titanium back up (do not back up system apps)
go into recovery and select 'mounts and storage'
format the following: system,data,osh,cache,preinstall
go back to main recovery menu and select 'install from sd card'
select 'choose zip from internal sd card'
select the CM7.2 zip that you have put on there (it will be at the bottom)
select Gapps zip and install
restart phone and go through start up procedure'
After Gapps has installed go back into recovery and repeat steps to get to install the ramfix zip and overclocking zip
restart phone
reinstall Titanium and reinsatll your apps of choice.
and hey presto... you'll have a new shiny fast Atrix :good:
barry_ said:
I have read your posts and I'm wondering how the phone feels when you're using it? (as opposed to looking at the stats)? I must admit you got me confused with all attention to write speeds ect.
As you've rooted/unlocked the bootloader what would you think about installing a custom rom? Something like CM7.2
It shouldn't take long. You've already got Titanium backup so you can back up your apps that you downloaded (not system apps) and install them after you have installed your new rom. It really shouldn't take long.
There is also a zip file called 'ram fix' which I've put here which might help after you've installed CM7.2 (it was designed for CM9/10 but there's no harm in trying it out)
You could also install a kernel which overclocks your CPU speed, thus making your phone faster.
If you decide to go down this route you'll need to do the following:
download CM 7.2/Gapps/Ramfix/Faux 1.3 overclock kernel and install on internal sd card
back up apps using titanium back up (do not back up system apps)
go into recovery and select 'mounts and storage'
format the following: system,data,osh,cache,preinstall
go back to main recovery menu and select 'install from sd card'
select 'choose zip from internal sd card'
select the CM7.2 zip that you have put on there (it will be at the bottom)
select Gapps zip and install
restart phone and go through start up procedure'
After Gapps has installed go back into recovery and repeat steps to get to install the ramfix zip and overclocking zip
restart phone
reinstall Titanium and reinsatll your apps of choice.
and hey presto... you'll have a new shiny fast Atrix :good:
Click to expand...
Click to collapse
Considering doing this, not even sure if I can restore my Atrix back to stock and relock the bootloader. I unlocked it thinking CWM and this restore would be the fix.. heh.. nope.
The phone is basically usable as long as you're not...doing anything. Opening apps takes forever, a reboot takes 5-6minutes about. To update an app, everything on the phone comes to a GRINDING halt until the app completely updates, that is if market doesnt force close first. I have to keep hitting "wait" at least 2-3 times until a small app updates. If its a 20MB app, it's frozen for 3minutes+ just updating one app. Anything that writes/reads from my internal memory is deathly slow. I'll have to try CM7 mod maybe Neutrino?
Is it even possible to turn in this phone to Moto for the 100$ rebate and blowing my 2-yr upgrade on a ATRIX HD? It seems more effective to just go and get a Galaxy Note II with 399$ than it does to get a Atrix HD, quadcore vs dualcore? I wanted to wait until Tegra 4 came to market, but I don't know how long that will be.. I'm left with a mediocre phone that is stock (i've not re-added my apps yet with titanium backup). Not sure where to go next with this. I'm hoping I can import my apps to Jellybean from Gingerbread with Titanium Backup!! Thank you for all the help. I appreciate it!
I have the same problem. Currently running CM 10 from epinter.
Sent from my MB860 using Tapatalk 4
OP, did you ever find a solution to this problem?
I'm facing the same issue with my atrix (stock Gingerbread 2.3.4, not rooted, free app storage: 1.24Gb, free internal: 9.91Gb):
Sequential Read: 10.67 MB/s
Sequential Write: 0.28 MB/s
Random Read: 1.48 MB/s
Random Write: 0.02 MB/s
Both of you, have you tried "sd speed increase" app from play store? I recall doing this recomendation, with examples in another post. It can greatly increase reading/writing speed for sd card an internal storage as well
ndsLux was
Note that (alpha) 3.1.10 kernel always had slow sd write. Only now people starting to discuss that (see epinter's 10.1 dev thread and/or kernel 3.1 one, I didn't remember which one it was, but krystianp is aware of that).
As of cm7, I never had this issue. Copying files via usb for instance was fast and smooth. Same for epinter's 10.1 with old kernel. With kernel 3.1, it 's slow as hell. Yet to be fixed, perhaps?
I've basically spent my entire day off from work trying to root my Nook Tablet 8GB to get CM10.1 put on it, and I'm ready to yank my hair out. A while back I successfully got CM10 on an sdcard and have been running that from the sdcard while my warranty was still active (just in case). Now my warranty's run out, and CM10 had been running sluggish for a while, in spite of my cleaning off all unnecessary files regularly. So I figured I'd try an internal ROM install. After hunting around for some really good detailed instructions for noobs (because I totally am one), I found this post (http://forum.xda-developers.com/showthread.php?t=2037368) and decided that even though it looked inefficient to go from CM7 to CM10, it broke the steps down enough for me to follow along.
However, I'm now stuck with CWM not reading the sdcard once it's time to install CM7 and gapps from the zip files. I keep getting the message, "No files found." I've tried unmounting the sdcard (and mounting "sd-ext," just for kicks), and it says, "Error unmounting /sdcard." If I try choosing "format /sdcard," it says, "E:format_volume failed to unmount '/sdcard.'" I've tried popping it out and back in multiple times. I've tried formatting in SDFormatter over again (even did a full overwrite erase, which takes forever, b/c I got a message saying the device doesn't support flash erase). I've been using Minitool to ensure that the partition is always FAT32, primary, set to active. I've gone into the stock OS and used a workaround I found to ensure that it will install apps from unknown sources. I've tried doing the root again from the beginning (which is a pain in the butt because I only have 1 sdcard to use for both the root and the ROM, so I have to keep switching the files out). I have no idea what I could be doing wrong, but I fear that it's something really basic.
Does it matter that I'm leaving the partition labeled "boot" for the ROM install? Is there a better way to put the files on the sdcard besides just with a Windows drag and drop? Is there a way for me to reboot the Nook from within CWM to maybe force it to read the sdcard fresh (keeping in mind that the sdcard no longer has the CWM files on it by that point)? I've seen some info online about people having issues with this class of sdcard, but I really don't want to spend the money on a new one until I rule out the possibility of a stupid user error. I'm also loathe to give up and go back to running a ROM from the sdcard because I've already put over 8 hours into trying to make use of the full Nook memory... If anyone has suggestions, I'd greatly appreciate it. Please keep in mind that any instructions will need to be very, very basic, though.
CWM version 5.0.2.8
sdcard type: SanDisk 8GB Class 4
Files on the sdcard: cm-7-TEAM-B-BETA1-signed.zip and gapps-jb-20130301-signed.zip
MidnightFrost1701 said:
I've basically spent my entire day off from work trying to root my Nook Tablet 8GB to get CM10.1 put on it, and I'm ready to yank my hair out.
...
Click to expand...
Click to collapse
There is no point in flashing CM7 if you're aiming to immediately flash CM10 on top of it.
To flash CM10.x, I'd suggest you try the process outlined at http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1. See http://forum.xda-developers.com/showpost.php?p=42985699&postcount=117 if you'd like to use a more recent CM10.1 build.
...
Files on the sdcard: cm-7-TEAM-B-BETA1-signed.zip and gapps-jb-20130301-signed.zip
Click to expand...
Click to collapse
You'll need an older version of gapps to go with CM7, see http://goo.im/gapps.
digixmax said:
There is no point in flashing CM7 if you're aiming to immediately flash CM10 on top of it.
To flash CM10.x, I'd suggest you try the process outlined at http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1. See http://forum.xda-developers.com/showpost.php?p=42985699&postcount=117 if you'd like to use a more recent CM10.1 build.
You'll need an older version of gapps to go with CM7, see http://goo.im/gapps.
Click to expand...
Click to collapse
Thank you, I'll try that tonight after work! After having been through the steps in the original instructions so many times, I'm familiar enough with things like Minitool Partition Wizard that I can get by with slightly less noobish instructions now. So that's one silver lining... [crosses fingers]
It seems to have worked! The first time I tried to turn it on after the install, the screen went and stayed black after the initial Cyanoboot screen. So I forced a reboot, but it appears to be running just fine! Thanks for the help!