I am sorry. I just cannot quite understand the partitions for gtablet, explained here
http://viewsonic-gtablet-for-dummies.webs.com/repartition.htm
When you do a nvflash, do you need to re-partition? Do you need to remount these partitions manually before reformatting before a flash? Do you need to remount before flashing a rom? a kernal?
Why do the default instructions suggest making one of the partitions 0 size?
klaberte said:
I am sorry. I just cannot quite understand the partitions for gtablet, explained here
http://viewsonic-gtablet-for-dummies.webs.com/repartition.htm
When you do a nvflash, do you need to re-partition? Do you need to remount these partitions manually before reformatting before a flash? Do you need to remount before flashing a rom? a kernal?
Why do the default instructions suggest making one of the partitions 0 size?
Click to expand...
Click to collapse
No need to repartition just for NVFLASH. Repartitioning normally necessary only once (unless you get a corrupted data area like I did).
The repartitioning is done within CWM. It only repartitions the user data area. No remounting necessary. Just follow the step by step and you will be good to go.
Do you need to remount these partitions manually before reformatting before a flash? Do you need to remount before flashing a rom? a kernal?
klaberte said:
Do you need to remount these partitions manually before reformatting before a flash? Do you need to remount before flashing a rom? a kernal?
Click to expand...
Click to collapse
When you do the reparition using the option within Clockwork Mod (CWM), nothing is unmounted and there is no need to remount anything.
If you read the Dummies site by 'good intention', it says there is a incompatibility between the stock partition and the software & that repartitioning is recommended once (sooner rather than later) to prevent a problem in the future. So, assuming your gTab is new, you would first install CWM, then install the ROM you want & then Repartition (see Code Green).
As long as you do not have corruption in the user data area, that would hopefully be the ONLY time repartitioning is needed.
In my case, I had corruption (all directory/file entries were random characters & attempts to run any app resulted in app no found), so I had to reparition mine a second time.
Al
still not getting it...
Thanks for your timely response. I have read the dummies web site several times, as well as several guides from xda-forums. However, there are sometimes inconsistencies with these different sets of directions. For example, please see Part 2, step 8 of
http://forum.xda-developers.com/showthread.php?t=865245
This clearly instructs you to (re)mount these partitions before flashing a new ROM.
However,
http://viewsonic-gtablet-for-dummies.webs.com/rom.htm
makes no mention of checking or mounting these partitions.
I can certainly follow a cookbook set of instructions, but I am trying to actually understand the "why" behind these instructions.
Specifically, which partitions are changed when you do a nvflash? reflash a ROM? flash a new kernel?
klaberte said:
Thanks for your timely response. I have read the dummies web site several times, as well as several guides from xda-forums. However, there are sometimes inconsistencies with these different sets of directions. For example, please see Part 2, step 8 of
http://forum.xda-developers.com/showthread.php?t=865245
This clearly instructs you to (re)mount these partitions before flashing a new ROM.
However,
http://viewsonic-gtablet-for-dummies.webs.com/rom.htm
makes no mention of checking or mounting these partitions.
I can certainly follow a cookbook set of instructions, but I am trying to actually understand the "why" behind these instructions.
Specifically, which partitions are changed when you do a nvflash? reflash a ROM? flash a new kernel?
Click to expand...
Click to collapse
The first post was back in Dec 2010. That was back when the only bootloader was the 1.1 branch. Part 2 Step8 is flashing the ROM, not repartitioning. It looks like they are having you unmount /system & /data before flashing the rom & then remounting it after you flash the rom. Don't know why thy did it that way back then since you aren't running on those paritions (/system & /data) while in CWM. Maybe back then they thought it was safer to do it that way.
What I can tell you is that I have flashed roms/configured four gTablets (everyone in the family wanted one) using the dummies instructions & they work correctly & are up to date for both bootloader branches.
Read through these 2 posts where I've gone into some detail regarding the partition and SD card structure and contents on the gTablet:
SD card on gTablet
Android partitions on gTablet
Related
Hi all,
I am a bit confused about the process that i need to follow to gain root access and also convert my filesystem to ext4 and the order i need to do the two.
Could someone form a simple noob guide of how to do the above?
Or should i wait for the 1-click root and custom roms...
There isn't a simple way and I doubt if there will ever be a 1 click root.
The easiest way to learn, IMHO, is to start with SDE.
Download the AOS file from archos - http://www.archos.com/support/support_tech/updates.html?country=us&lang=en
Read the instructions - (boot into recovery, update firmware, plug archos into PC, copy AOS file, ect...)
Install SDE
Once you see the recovery, look into the menus and get comfortable with it, you should try Dogma's perm root and kernel. Then a next step would be to OC with ardat's kernel. Then you can try to learn Linux and $aur0n's method...
...all IMHO of course.
xnatex21 said:
There isn't a simple way and I doubt if there will ever be a 1 click root.
The easiest way to learn, IMHO, is to start with SDE.
Download the AOS file from archos - http://www.archos.com/support/support_tech/updates.html?country=us&lang=en
Read the instructions - (boot into recovery, update firmware, plug archos into PC, copy AOS file, ect...)
Install SDE
Once you see the recovery, look into the menus and get comfortable with it, you should try Dogma's perm root and kernel. Then a next step would be to OC with ardat's kernel. Then you can try to learn Linux and $aur0n's method...
...all IMHO of course.
Click to expand...
Click to collapse
I don't fully agree. There are several Steps in the Process which can be scripted. One would be a Script to partition and preload your sd card for being used in the Archos, including copying rootfs and some Help to move your Data Partition.
Probably SDE is a must for Permanent Root forever, so everyone intending to root his Device has to go through that Process, as well as flashing custom Kernels.
$auron is making good Progress on enhancing his Rom and making it more flexible and customizable. Probably someday there will be a Preferences App to change the Behaviour of the Rom.
Kashban said:
I don't fully agree. There are several Steps in the Process which can be scripted. One would be a Script to partition and preload your sd card for being used in the Archos, including copying rootfs and some Help to move your Data Partition.
Probably SDE is a must for Permanent Root forever, so everyone intending to root his Device has to go through that Process, as well as flashing custom Kernels.
$auron is making good Progress on enhancing his Rom and making it more flexible and customizable. Probably someday there will be a Preferences App to change the Behaviour of the Rom.
Click to expand...
Click to collapse
I am confused also. I've read through just about every post in this forum and the one thing that I can't get a clear answer on is, do I have to have an sdcard to load the UrukDroid stuff? Or can it be done on my internal storage? I've tried going through the instructions and I cannot get the sdcard partitioned and formatted correctly.
And what does "permanent root" mean? Does that just mean you've installed the SDE and a new kernel and removed the default Archos kernel so that it always boots the SDE kernel?
I've seen a number of requests for this functionality and recently it became necessary for one user who had a disabled Home Key to clear cache and data without the use of ClockworkMod. I have reserached two methods to address this issue. These instructions require some familiarity of android, computer and tablet terminology and usage. Feel free to ask for clarifications in comments. Here we go...
Method I - Stock Recovery Command File
Technical: Stock Recovery command file can be used to perform a few additional functions as well as to alter the path to update files. These commands will execute with all privileges available to recovery mode.
Advantages: Very easy to use. Very little technical knowledge required. No third party software is required for use.
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Prepare a text file named "command" (no file extension) with one of the following commands on a single line. The wipe data command will wipe both data and cache. Wipe cache will wipe cache only.
--wipe_data
--wipe_cache
2) Place the file in a folder named "recovery" in the root directory of your MicroSD card.
3) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
4) Allow the command to execute completely then the tablet should reboot (this may not occur automatically depending on firmware installed).
Method II - Updater Script
Technical: The attached "Updater Scripts" perform delete commands (recursively if necessary) on the named directory or file(s). The directories are mounted automatically by the system before the script executes but it could be easily revised to include that step if necessary. The partitioning, formatting and directory structure are left untouched. Only files are deleted.
Advantages: No third party software is necessary for execution. Relatively easy to modify for more surgical precision (i.e. leaving installed apps but clearing possibly corrupted system data). Included example: "Clear Battery Stats"
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Download the attached archive (ClearData.zip) to your computer.
2) Extract the files to your computer. You should then have a folder named "recovery" (which contains a file named "command") and an additional archive named "update.zip"
3) Place the recovery folder and the update.zip in the root directory of the MicroSD card.
4) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
5) Allow the script to execute completely then reboot the tablet (this may occur automatically depending on firmware installed).
This will become handy someday.
Thanks for sharing your knowledge.
You're welcome. One quick note... the new stock recovery adds a menu simiilar to ClockworkMod. These methods will still work since the recovery folder/command file are checked first but it really isn't as necessary any more.
Need Help
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Me too
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
lrgche said:
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Click to expand...
Click to collapse
That's an indication that you may have more serious problems. nvflash will be required. http://forum.xda-developers.com/showthread.php?t=861950
Once done you will likely need to install ClockworkMod and repartition your internal storage.
Loukoebel said:
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
Click to expand...
Click to collapse
If your tablet boots properly but you can't get into CWM then it probably isn't installed properly (or at all). http://forum.xda-developers.com/showthread.php?t=865245
Keep in mind that CWM is NOT compatible with all ROMs. Make sure the developer for your chosen ROM recommends it before installing it.
Does your method in opening post have to be run from external micro sdcard?
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
K J Rad said:
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
Click to expand...
Click to collapse
so your method is a simple way to replace one of the main uses of Clockword MOD?--Plus you stay stock more or less.
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
K J Rad said:
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
Click to expand...
Click to collapse
Wipe data does what--remove the apps installed?
And the partitions?
Your post is very interesting. It implies that you have a knowledge of the g-tabs partition structure. I have played with Linux off and on for the last 10+ years. When I began, I used Slackware and when you set it up you had to manually create partition tables using fdisk. You were only required to create two - the data partition and a swap partition but it was often recommended that you create several others - one to contain the home directory to prevent users from using all the disk space (in the days of small disks) for example. It appears that there are a lot of partition on the g-tab. Up to now, I have used various wiping tools like clockwork or calkulins wipe all on faith. I would really like to know what all the partitions are and what is in them. I have used terminal to get to the root folder and tried to do an fdisk to display the partitions but try as I might everything remains hidden. It would seem that a script like yours could be adapted to do many things but I would certainly want to understand the structure a little better before I did anything. I have searched and been unable to find that information. Can you point a way for the curious to learn more about the partition structure on the g-tab?
Wish I had a direction I could point you in. What I've found so far has mostly been stumbled upon while looking for something else. What I can tell you is this...
1) When using fdisk in Android you must specify the device to look at. Try something like: fdisk /dev/block/mccblk3 That should list the current partitions as defined by CWM or whatever was used originally.
2) Within one of those partitions in the list generated above are sub-partitions holding the bootloader, system, data, etc partitions. You can see how they're described in the .cfg files in the nvflash restores that are lying about.
lsu205 said:
Wipe data does what--remove the apps installed?
Click to expand...
Click to collapse
Removes user apps and their associated data as well as system related data and settings.
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
CodeNamePapa said:
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
Click to expand...
Click to collapse
I'm looking for a solution to that problem. Unfortunately these methods still require the ability to get into recovery mode which likely won't work if you're having trouble getting CWM installed.
If, however, you can get into recovery... then it is theoretically possible to create a script that would accomplish that. As soon as I have one I'll be adding it to the mix ;-)
Edit: I've found something I think will work. Will do some testing tonight. It will still require access to recovery.
I wasn't sure if you saw my other post but I am seeing no partition 0 when I NVFlash with a verifypartition.
http://forum.xda-developers.com/showpost.php?p=13059520&postcount=57
I haven't yet but I will. Let's try to keep this thread on topic. Thanks.
More thoughts:
because I went w/ cyan7 is it possible i have a "bad" kernel and that the stock bekit-1105 or the roebeet-3588 files are crashing w/ the kernel in place already?
I know custom ROMs can have a custom kernel applied separately, but I have no idea whether cyan7 loads it's own kernel...
I have yet to try the nvflash_gtablet_46 version, as I see the img files w/in are different from the original 1105 .zip
Also:
read on another thread that part 2 and part 3 aren't loading for other users when doing nvflash - I did notice that it pauses, runs some stuff, then starts loading part 4 through to the last part, then success. - do part 2 and 3 run for you?
edit: I see a 4349 downgrade.zip in another thread for those who got the OTA update but want to go back to stock 3588 prior to jumping off somewhere else - I can't expect that would help me as I can't do squat w/ recovery yet, but could that possibly "reset" any bad kernel problems? - again, I'm just thinking out loud.
This is well outside the scope of this thread but I find some of what you mention interesting so I'll address it and then end any further off topic discussions.
I did not build nor have I ever used Cyan7 so I have no basis for an opinion on the matter other than this... Each ROM comes with a kernel installed so if properly done an nvflash should overwrite any "bad" kernel.
Part2 and Part3 do indeed load, they are just displayed differently than the other Parts. Just minutes ago I flashed down from Mountain Laurel (4349 based with the new bootloader and recovery) with absolutely no trouble. I can, and have, read back those partitions after an nvflash to prove that point.
The 4349 downgrade will only work for you if recovery is working. Having never used it I don't know that it would "reset" the kernel but any subsequent flashing of a new ROM image would.
I am working on a stock recovery solution for partitioning but it isn't likely to help anyone who is stuck in an APX loop. I do have some ideas on what might help for that condition but I haven't been able to get my hands on one for testing and trying to help people here is like being a consulting mechanic for a car repair that's in someone else's shop having work done on it that you're not being told about.
I'll be happy to address any further comments or questions regarding your specific issue in an appropriate thread or via PM. Thanks.
Just wondering if anyone can do a complete backup of their device and upload it somewhere like Dropbox. My Internal SD has been formatted incorrectly and I can't get it back correctly. My touchscreen is dead and I only know people with Bell Atrix devices.
If anyone could do this huge favor it'd be greatly appreciated!! Need a complete backup and then I'd use Tenfar's modified recovery to try booting it. Thanks in advance.
Use the 'Flash SBF' guide in the Dev forum. That will get you back to stock.
http://forum.xda-developers.com/showthread.php?t=991072
link12245 said:
Use the 'Flash SBF' guide in the Dev forum. That will get you back to stock.
http://forum.xda-developers.com/showthread.php?t=991072
Click to expand...
Click to collapse
Thank you but that's not working. Hoping to get someone actual backed up recovery to see if that corrects the partitioning in the internal storage. Tried a million ways to flash and partition things.
Going to try doing some more work in an actual Linux environment after work today. I'll try seeing if I can manually format and partition it (getting random daemon errors because my PC is a bit retarded).
link12245 said:
Use the 'Flash SBF' guide in the Dev forum. That will get you back to stock.
http://forum.xda-developers.com/showthread.php?t=991072
Click to expand...
Click to collapse
bongd said:
Thank you but that's not working. Hoping to get someone actual backed up recovery to see if that corrects the partitioning in the internal storage. Tried a million ways to flash and partition things.
Going to try doing some more work in an actual Linux environment after work today. I'll try seeing if I can manually format and partition it (getting random daemon errors because my PC is a bit retarded).
Click to expand...
Click to collapse
Worst case scenario, just format any SD cards in the phone and follow the guide that link12245 posted... that should work. If you're having issues using RSDlite in windows, try using it on the linux system... you'll find it to be a lot more compliant.
mpalatsi said:
Worst case scenario, just format any SD cards in the phone and follow the guide that link12245 posted... that should work. If you're having issues using RSDlite in windows, try using it on the linux system... you'll find it to be a lot more compliant.
Click to expand...
Click to collapse
Yeah, I've tried that many times already. I'm thinking that doing this in a Linux environment will be more forgiving. Tenfar has graciously been helping me and I'm disappointed that I'm unable to follow his steps.
If I understand correctly I need to do this command in ADB: mkfs.vfat /dev/block/mmc0p18, as well as newfs_msdos -F 32 -S 512 -L MB860 -c 64 -u 16 /dev/block/mmcblk0p18 which should get it running smoothly.
At least I'm becoming a lot more comfortable with Linux commands. Actually thinking of dual booting Ubunto on our home computer once the wife isn't so pissed. Stayed up until 6am for two nights trying to fix this. If it weren't my birthday on Saturday she'd castrate me
Thanks for the help, guys.
This issue was resolved by Meghd00t's new REPART.IMG file. See this post on that thread: http://forum.xda-developers.com/showpost.php?p=26060323&postcount=151cool:
I have the 8gb model Nook Tablet and (mistakenly) tried to flash CWM & CM7a to the EMMC of my tablet. At that time, there were no warnings about how the internal flash version would brick the NT8.
Now, my tablet will not boot to ANYTHING on the internal memory. I do NOT get the stock "reset" warnings - or even a flash of light. No matter how I try to boot it (with or without cable, with or without the Nook button) or how long I hold the buttons down, it still remains with a BLACK SCREEN.
However, the SDCard will boot properly.
I followed the instructions on this thread ( http://forum.xda-developers.com/showthread.php?t=1515788) precisely to reset the BootData. I did NOT receive any errors. However, it still will not boot internally.
I then tried sigmabeta's process to flash CM9 (http://forum.xda-developers.com/showthread.php?p=25661314) to the internal emmc (which is supposed to work on NT8). The flash process (via SD/CWM) went properly and I did not receive any errors. However, I still cannot get anything to boot (except my SDCards).
If I put my CM7a (bootable) SDCard (http://forum.xda-developers.com/showthread.php?t=1481826) into the NT8, it boots and runs great! Likewise meghd00t's recovery/CWM sdcard boots and runs properly.
I can do ADB & FASTBOOT and I have even done the dd to download my partitions (for backup) and then dd copies from online onto the device's partitions. Still no joy.
However, even after dd'ing a downloaded copy of p5 to the device, ADB still reports my TRUE serial number? It seems that the dd to part5 did not take?
The only other thing that I have found, that seems significant, is the fact that when I am in CWM, I cannot mount the EMMC. I can ADB/shell into the device but that did not allow me to mount the emmc either.
Any ideas how I can get this thing to boot internally? How can I force the device to mount the emmc?
Click to expand...
Click to collapse
If you have tried all the unbrick methods out there with no luck, then throw it to the wall and see it is fixes .
~ Veronica
Final "fix"
lavero.burgos said:
If you have tried all the unbrick methods out there with no luck, then throw it to the wall and see it is fixes .
~ Veronica
Click to expand...
Click to collapse
Not sure that I have tried ALL of them, that is why I am still searching. Also, people come up with new ideas that have not previously been published.
Thanks for all YOUR help. Especially the dd to fix bootdata.
Sure wish someone would come up with a solution for this problem. There seems to be quite a few of us who are looking for answers.
Sent from my Nook Tablet using XDA
I have been reading for a while and I didn’t want to the answer because the answers are already in the Dev. area. I rather have people do some research and learn to solve their own problem rather than listen to someone else that might misled to do something even worse.
NT already has a recovery in place; factory restores (eight failed boot method). Most people do not know this and try something in an environment that they are not familiar with, Ubuntu. If you are using Windows, then you can resolve it in Windows. You do not need to repartition, format, or delete partitions. I have learned that many people like to format things apparently.
The most common problem seems to be; my NT does not turn on or my nook only boot with sdcard. It is not technically true; your NT actually turns on. The backlight just doesn’t turn on because you format/replace the x-loader/bootloader. X-loader loads the bootloader. You know the bootloader work if you see the “n” logo screen. If your NT restart after the "n" logo screen, it mean bad recovery.img/boot.img.
How did this happen? You flash the wrong MLO file to your x-loader, you used an old CWM (experimental one) and formatted your sdcard or you like to format things.
How do I resolve this? First thing is to make a proper CWM sdcard, one with proper partition table. You can compile your own CWM recovery when you compile CM7. Second, flash stock 1.4.2 rom, which contain the latest x-loader, bootloader, boot, and recovery files that works on both 8GB/16GB NT. This will restore your NT to stock android gingerbread.
If you happen to format the rom partition, you need to restore it with a backup and perform the eight failed boot method. This will restore your proper rom partition data along with the stock android. It is all in my thread in the Dev. area.
If you happen to screw up your partition table, obviously this will not help you until you fix your partition table.
Existing solutions
succulent said:
I have been reading for a while and I didn’t want to the answer because the answers are already in the Dev. area. I rather have people do some research and learn to solve their own problem rather than listen to someone else that might misled to do something even worse.
NT already has a recovery in place; factory restores (eight failed boot method). Most people do not know this and try something in an environment that they are not familiar with, Ubuntu. If you are using Windows, then you can resolve it in Windows. You do not need to repartition, format, or delete partitions. I have learned that many people like to format things apparently.
The most common problem seems to be; my NT does not turn on or my nook only boot with sdcard. It is not technically true; your NT actually turns on. The backlight just doesn’t turn on because you format/replace the x-loader/bootloader. X-loader loads the bootloader. You know the bootloader work if you see the “n” logo screen. If your NT restart after the "n" logo screen, it mean bad recovery.img/boot.img.
How did this happen? You flash the wrong MLO file to your x-loader, you used an old CWM (experimental one) and formatted your sdcard or you like to format things.
How do I resolve this? First thing is to make a proper CWM sdcard, one with proper partition table. You can compile your own CWM recovery when you compile CM7. Second, flash stock 1.4.2 rom, which contain the latest x-loader, bootloader, boot, and recovery files that works on both 8GB/16GB NT. This will restore your NT to stock android gingerbread.
If you happen to format the rom partition, you need to restore it with a backup and perform the eight failed boot method. This will restore your proper rom partition data along with the stock android. It is all in my thread in the Dev. area.
If you happen to screw up your partition table, obviously this will not help you until you fix your partition table.
Click to expand...
Click to collapse
Thanks for the info. I do appreciate it and I will be trying some of your suggestions later today when I get home.
One problem (that seems to be easing up a bit) is the fact that few posters distinguish WHICH version of the NT that they are working with. The NT16 "solutions" became the NT8 "problems." It would be great if everyone posted WHICH version they have.
The other issue is (as you stated) when you follow a guide to fix an issue, it CAN mess up your device even worse that it was. Then, you have TWO issues to deal with - rather than just one as before. I am afraid that is where I am now.
One question: You mention "compiling" CWM. Are you referring to the technical term of compiling code into an executible? Or, are you simply referring to the process of putting a working image onto an SDCard? I can do the latter without issue but I have never compiled code.
I do use Ubuntu Linux so many of the Windows driver issues are moot for me. However, I do have a dual boot with XP in on the other side - just in case I need to do some Windows-only stuff.
I really appreciate the help. I am no novice but I am not a developer either. I can usually search, read, try, and work out the problems that I (and other less technical users) experience. That is what my website is all about - translating the really "tech" jargon into everyday language for non-techies to follow. But this one has stumped me (and at least a few others) for the past couple of months.
succulent said:
I have learned that many people like to format things apparently.
Click to expand...
Click to collapse
Sent from my NookTablet using Tapatalk
I've noticed this as well. People really need to do more reading before randomly selecting/flashing things.
Thanks everyone, i bought a 16bg nook tablet (for the 1gb ram) and booted from the SD successfully. but now have a couple more questions....
1) partitioning, i get, its easy in gparted or the windows manager, but for the life of me i do not see a quick guide on how to partition *correctly*. i see 5 partitions on the sd card, and the guide says to expand 4... but it wont let me. i have not tried gparted yet, but i assume if i cant expanded it now (in windows) that i am doing something wrong and will just bork it up in gparted. so.... any links to working partition guides ?
fyi, the partition tool in cm7 in the "cm7 settings" only gave me the option of "512 megs"... so not sure.. but i think the installer made the wrong partition sizes ? dunno... im new and assuming alot based on alot of windows crap and limited linux interactions...
2) installing TOO the device itself: in the one guide above it does not mention rooting, so i assume when you boot to cm7 off a sd, and then go to "install image" that it will root, lay down the new image and all is well... am i correct in that assumption?
3) recovery, i know i will kill the install eventually. im the kind of guy to tinkers and has to re-install windows and backtrack on a regular basis. what i have not seen is how to restore to factory. is it something like my htc glacier? like this link implies ? http://nooktalk.net/nook-faq/nookco...-how-do-i-do-a-hard-reset-system-restore.html
4) if i unplug the usb cable.... i no longer boot into cm7 on the stick... is there a way to not have this happen aside from writing over the image ?
thank you all for your patience!
maxxcool7421 said:
Thanks everyone, i bought a 16bg nook tablet (for the 1gb ram) and booted from the SD successfully. but now have a couple more questions....
1) partitioning, i get, its easy in gparted or the windows manager, but for the life of me i do not see a quick guide on how to partition *correctly*. i see 5 partitions on the sd card, and the guide says to expand 4... but it wont let me. i have not tried gparted yet, but i assume if i cant expanded it now (in windows) that i am doing something wrong and will just bork it up in gparted. so.... any links to working partition guides ?
fyi, the partition tool in cm7 in the "cm7 settings" only gave me the option of "512 megs"... so not sure.. but i think the installer made the wrong partition sizes ? dunno... im new and assuming alot based on alot of windows crap and limited linux interactions...
2) installing TOO the device itself: in the one guide above it does not mention rooting, so i assume when you boot to cm7 off a sd, and then go to "install image" that it will root, lay down the new image and all is well... am i correct in that assumption?
3) recovery, i know i will kill the install eventually. im the kind of guy to tinkers and has to re-install windows and backtrack on a regular basis. what i have not seen is how to restore to factory. is it something like my htc glacier? like this link implies ? http://nooktalk.net/nook-faq/nookco...-how-do-i-do-a-hard-reset-system-restore.html
4) if i unplug the usb cable.... i no longer boot into cm7 on the stick... is there a way to not have this happen aside from writing over the image ?
thank you all for your patience!
Click to expand...
Click to collapse
3) read this post for restore to factory, it is for info only! If you break something I'm sorry. These are the facts as I have been able to prove.
http://forum.xda-developers.com/showthread.php?t=1837130
Good Luck!
sorry, try it now
tobdaryl said:
3) read this post for restore to factory, it is for info only! If you break something I'm sorry. These are the facts as I have been able to prove.
Good Luck!
Click to expand...
Click to collapse
red text is not linking anywhere ?
Regards!
post fixes with link
sorry, I have edited post to include proper link!
Good Luck!
the link is for info only!