First let me introduce myself, my name is Sean Cullinan and I posted a very detailed set of instructions on my blog blendblog.net on how to take a stock GTablet and get it going with a custom ROM. I used Vegan for my instructions.
After the woot deal blew up a ton of traffic came to my site and there was some concern over using my instructions versus the ones here and also with the sources of the binaries I posted. I posted the binaries because I wanted to rename them with "number coding" to make them easier so that new users wouldn't install them in the wrong order.
Anyway, after talking with Roebeet and a few others I thought it would be good to post the instructions here as well. I wasn't trying to steal any of XDA Devs thunder, everything I learned I did through this site.
So here is the original blog post in it's entirety.. Note that I still pointed the links back to my server, you can find the same files linked from the devs at XDA if you don't "trust" me. Also, if you want to use TNT Lite 4.40 I posted a second tutorial to my blog, I kept it separate to keep things simple.
Please feel free to checkout my site as well if you find this useful,...and if enough people find this useful maybe this is "Sticky worthy?"
Verifying Installed ROM Version
The first thing you have to do is verify that you're GTablet is on ROM 3358 or lower before doing this procedure. If you have a newer ROM version on your device you cannot do this procedure at this time!
1) On the GTablet go to Settings->About Device
2) If the version is anything higher than 3588 STOP NOW! According to this thread it is easy to "softbrick" your device if you proceed. So again, STOP NOW! I hope to have instructions on how to get around this posted in the future.
Introduction
We bought a GTablet for work and our software partners also bought one to test the development we were doing on it. As such I had to write up instructions on how to flash the GTablet with the VEGAn ROM and a custom Kernel. I was told the instructions were very good so i decided to post them here. Disclaimer: First, flashing your tablet means you will lose any applications that you have installed previously or that came with the stock ROM. You will have to reinstall them. If you search around on XDA you will find other separate instructions on how to take backups if this is important. Second, please note that the developers at XDA Developers are not responsible for these instructions!! I put them together myself to help a vendor partner of ours whom I am developing software with. Many people have informed me that these instructions work great but as always with these things, you are doing something that is highly technical and something can go wrong...at which point you will have to figure out how to recover!
Installing Clockwork Mod Recovery
The first thing you have to do is install Clockwork Mod Recovery. The GTablet goes into “recovery” mode whenever you power up by holding the volume up key along with the power key. Clockwork Mod Recovery gives us a low level UI with which to work which the default “Recovery” mode does not do. To install Clockwork Mod Recovery do the following:
1) Attach the GTablet to your PC so you see it as a drive
2) Download and unzip the 1-cwmod_internal.zip file from the website on your PC.
3) Place the recovery folder and the update.zip file on the root of the disk drive that represents the GTablet on your PC from step 1. If there was already a recovery folder and update.zip you can delete them and replace them with this one.
4) Safely remove the GTablet
5) Power down the GTablet (hold power button and use the Power off option).
6) Hold the volume + key down while holding the power button. Release when you see “Detecting recovery key pressed” on the screen.
7) It will now install clockworkmod and the device will boot again.
Repartitioning GTablet storage
For some reason Viewsonic used an odd partition set when they shipped the GTablet. While repartitioning the storage wasn’t totally necessary it has been recommended on the forums so I did it. Here’s how:
1) Power down the GTablet
2) Boot into Clockwork Mod recovery by holding the Volume + key down while holding the power button. Release when you see “Detecting recovery key pressed” on the screen.
3) You will be presented with a menu, this is Clockwork Mod Recovery. To navigate the menu use the volume up and down keys. To select a menu option use the home key. To go back press the back key.
4) Navigate to Advanced->Partition SD Card (FYI, SD Card refers to internal storage, not the MicroSD card).
5) Choose 2048M for EXT size on the first screen
6) Choose 0M on the second screen.
7) You have now repartitioned the GTablet
Copying the ROM and Kernel files to the GTablet
Now that everything is formatted we have to copy the ROM files to the GTablet that we are going to use.
1) Navigate back to the root menu of Clockwork Mod by using the back key or by powering off and powering on with the Volume + key held down as above
2) Plug the GTablet into your PC
3) Choose mounts and storage->Mount USB storage. The Gtablet should now show up as a drive on your PC.
4) Create a directory on the drive called ROM’s.
5) Download and copy 2-gtab.VEGAn.1.00.beta5.1.user.final.zip from the website to the ROM’s directory. Note that this file is 88mb (rather large). DO NOT UNZIP, just copy
6) Download and copy 3-gtab.VEGAn.1.00.beta5.11.suppl.zip from the website to the ROM’s directory. DO NOT UNZIP, just copy
7) Download and copy 4-boot-cm_2632.32-xtra-vfpv3_fp-030711.zip from the website to the ROM’s directory. DO NOT UNZIP, just copy
8) You can now “safely remove hardware” from windows and select “Unmount” in Clockwork Mod. You can unplug the GTablet from your PC.
Installing the Vegan 5.1 ROM
Now we are ready to actually start installing stuff!
1) Navigate back to the root menu of Clockwork Mod by using the back key or by powering off and powering on with the Volume + key held down as above
2) Choose install zip from SD Card->choose zip file from sdcard
3) Navigate into the ROM’s directory and select 2-gtab.VEGAn.1.00.beta5.1.user.final.zip
4) When prompted choose “Yes- Install 2-gtab.VEGAn.1.00.beta5.1.user.final.zip”
5) Let the installer do its thing.
6) When installer completes go back to the root menu in clockwork mod.
7) Choose “wipe data/factory reset.” When prompted confirm that you want to wipe.
8) Choose “wipe cache partition”
9) Navigate to Advanced and choose “wipe davlik cache”
10) Navigate back to the root menu and choose reboot system now. The device should boot into Vegan 5.1. Let this happen.
Installing the Vegan 5.1 ROM supplement
There was a small update to Vegan 5.1 that was posted as a supplement that is installed exactly the same way that Vegan 5.1 was installed:
1) Power down the GTablet
2) Boot into Clockwork Mod recovery by holding the Volume + key down while holding the power button. Release when you see “Detecting recovery key pressed” on the screen.
3) Choose install zip from SD Card->choose zip file from sdcard
4) Navigate into the ROM’s directory and select 3-gtab.VEGAn.1.00.beta5.11.suppl.zip
5) When prompted choose “Yes- Install 3-gtab.VEGAn.1.00.beta5.11.suppl.zip”
6) Let the installer do its thing.
7) When installer completes go back to the root menu in clockwork mod.
8) Choose “wipe data/factory reset.” When prompted confirm that you want to wipe.
9) Choose “wipe cache partition”
10) Navigate to Advanced and choose “wipe davlik cache”
11) Navigate back to the root menu and choose reboot system now. The device should boot into Vegan 5.1 with the supplement. Let this happen.
Installing Pershoot’s kernel
Pershoot is a fantastic Android dev who has written superior Kernel's for several devices including the GTablet. You can check his site for the latest builds. This kernel fixes several more bugs in the default Kernal that comes with Vegan 5.1. It is installed the same way that you install the Vegan ROM/Supplement:
1) Power down the GTablet
2) Boot into Clockwork Mod recovery by holding the Volume + key down while holding the power button. Release when you see “Detecting recovery key pressed” on the screen.
3) Choose install zip from SD Card->choose zip file from sdcard
4) Navigate into the ROM’s directory and select 4-boot-cm_2632.32-xtra-vfpv3_fp-030711.zip
5) When prompted choose “Yes- Install 4-boot-cm_2632.32-xtra-vfpv3_fp-030711.zip”
6) Let the installer do its thing.
7) When installer completes go back to the root menu in clockwork mod.
8) Choose “wipe data/factory reset.” When prompted confirm that you want to wipe.
9) Choose “wipe cache partition”
10) Navigate to Advanced and choose “wipe davlik cache”
11) Navigate back to the root menu and choose reboot system now. The device should boot into Vegan 5.1 with the supplement and this kernel. Let this happen.
Last Steps
You now have Vegan 5.1 installed on your GTablet! What is left to do? The launcher that comes with Vegan is kind of weak, it doesn’t rotate to portrait so I chose to install Launcher Pro which is much nicer. You can get this in the Android Market which is built into this ROM. Launch the Android Market and you can either use an existing or create a new Google ID. Do a search for Launcher Pro. If you don’t see it you may need to “fix” the Android Market which is common when doing a ROM upgrade. Here is the procedure to fix it.
1) Navigate to the Android settings->Applications->Manage Applications
2) Choose the all tab
3) Select “Market” from the list
4) Press “Clear Cache”
5) Press “Force Stop”
6) Press the back button to navigate back to the list of applications
7) Select “Google Services Framework”
8) Press “Clear Data”
9) Press “Force Stop”
10) Exit the settings. Try to launch the market
11) You should receive an error, this is expected.
12) Power down the GTablet (I’ve been told not to use the reboot option instead powering down and using the power button to bring it back up).
13) Power on the GTablet
14) Once everything is loaded go back to the Market. If you get an error wait a minute.
15) Search for Launcher Pro and hopefully it is found. If not repeat this fix process again (I’ve had to do it twice sometimes).
Once you have Launcher Pro installed you can make it the default using the “Home Switcher” application. You can customize Launcher Pro quite a bit, it’s a nice launcher app.
Note You can safely delete the ROM’s directory after doing this if you desire to do so, although its sometimes handy to have it on there if you want to re-flash for some reason.
You should now have a pretty rock solid GTablet that gives you a very good, stock like Android experience.
Awsome Tutorial!,, Truly Awesome! Thank you for taking the time to write this. My Tab is currently OUT FOR DELIVERY. I can't wait to get it and try this! Thanks again.
I noticed on your website that you felt that the Archos 101 is a better device than the gTab. With the recent updates in ROMS and kernels do you still think the Archos device is superior?
What did you use for rooting? That is the one thing I see missing in your post.
Thanks for the comments and compliments!
I didn't use the term "rooting" but this is what you are doing when you install CWM and then flash your own ROM. So following my instructions "roots" the devices.
Here's a link to my article pr0cs is referring too. I wouldn't necessarily say that I thought the Archos was better, just different. My comparison was made with Vegan 5.1 so the review is still relevant. Now when/if Honeycomb gets running on the GTablet (which is far more likely than the Archos) it may change the equation a bit!
Sean
I've read other articles that specify rooting the device first then installing CWM, and I've seen articles like yours that don't mention getting root access, so thanks for that clarification.
And wonderful step-by-step guide.
Nice write up. I'll have to search the forum for information about this ROM.
Sent from Captivate, Cognition 4.1.1
Thanks for the step-by-step!
Just got my gtab last night.
Followed your instructions to the letter. Everything worked perfectly, thanks for your easy to use guide.
And thanks to all the Devs that made it possible. This tablet screams with a different ROM on it! My iPad toting friends are already jelly...
I just followed these instructions today from Sean's site, in order to upgrade my VEGAn 5.1.1 kernel to Clemsyn's v7 kernel.
It took me a bit to find Sean's blog location, so I am glad to see this here. I would encourage anyone who wants to mod their ROM and kernel revs to use this as a baseline.
I nominate this thread for a sticky.
Thanks OP! I just got my gtab today... someone mentioned in another forum that you should get nvflash in case you mess something up... is clockworkmod acting as a replacement for nvlflash here?
I know this is a stupid question but is it required to root the device before following any if these steps
Sent from my X10i using XDA Premium App
MFister said:
Thanks OP! I just got my gtab today... someone mentioned in another forum that you should get nvflash in case you mess something up... is clockworkmod acting as a replacement for nvlflash here?
Click to expand...
Click to collapse
ClockworkMod is another tool but not a replacement for nvflash. It would be wise to be comfortable with both.
sweetfish said:
I know this is a stupid question but is it required to root the device before following any if these steps
Sent from my X10i using XDA Premium App
Click to expand...
Click to collapse
Rooting isn't necessary at all whether you're modding or not. Most of the custom ROMs are pre-rooted for your convenience.
Great instructions. Been looking for an organized and easy-to-use guide for Vegan 5.1.x
Just got my G-Tab and waiting for it to finish charging.
Worked slick as a whistle. No problems whatsoever. I now have a REAL Android tablet. Thank you for putting together a very clear and thorough tutorial.
With a handle like "stiphy" and a post count of 69, you need to stop right there and enjoy life for a while!
nunjabusiness said:
With a handle like "stiphy" and a post count of 69, you need to stop right there and enjoy life for a while!
Click to expand...
Click to collapse
LOL...awesome post, oops, just screwed it up!
Glad the instructions are helpful!
Sean
Followed instructions and now my tablet is flying like a butterfly, thanks very much!
But I got a quick question,
Is it normal for my device to say:
Baseband version: Unknown
Also, every time I try to open 'status' in 'about device', I get a:
Sorry! The application Settings (process com.android.settings) has stopped unexpectedly. Please try again.
Is this normal as well?
You made this noobs day!!!
bro i have read and watched countless hours on how to do this...and it wasn't until i found this thread with my 100th google search during the past 2 wks that i felt confident enough to do this.
because of this thread, it was MAD easy!! again, mucho gracias.
on a side note...cant find launcher pro (or adw.launcher) in google markets. any idea why? suggestions?
studjethro said:
bro i have read and watched countless hours on how to do this...and it wasn't until i found this thread with my 100th google search during the past 2 wks that i felt confident enough to do this.
because of this thread, it was MAD easy!! again, mucho gracias.
on a side note...cant find launcher pro (or adw.launcher) in google markets. any idea why? suggestions?
Click to expand...
Click to collapse
Studjethro, try the market fix
+1 OP, great guide!
First of all, thank you so much for the concise and clear guide! I followed this exactly. The market fix needed titanium backup though.
Couple of issues:
1. The status check gives out error, does not work, and baseband is unknown - same as post #17
2. Calling using phone gives core dump :-( - I am assuming it should use google voice, but does not seem to work
Any ideas about these ? I have just started exploring. Will post if I find more issues.
Thanks again!
Related
This guide was written by Darkonion. I have just updated it to work for the newest release. Please give all credit to him.
NOTE: Updated September 12th, 2010. Added additional steps to the process. Reread to reapply the Epic Unleashed 2.0!
Please READ each direction CAREFULLY and BEFORE executing each step. I can not stress how many mistakes are made because someone did not READ the directions carefully. So... yeah, once again, READ THE DIRECTIONS CAREFULLY!
How to Apply EpicUnleashed 2.0
Credits: The ROM was created by Matt4542. Tutorial was written by me with some simple directions from Matt. You'll need to be rooted in order to run the Droid 2 Bootstrapper.
The fine print: Matt4542 and/or I (DarkOnion) can not be held responsible if you mess up. If you mess up, you mess up. That's why I wrote the .sbf recovery tutorial. Matt has also written one. More simple, but requires Linux.
Here we go.
1. Download Koush Bootstrap here.
http://koush.tandtgaming.com//motoro...2Bootstrap.apk
2. Download Unleashed 2.0!
http://matt.kimete.com/screenies/Unleashed2.0-D2.zip
3. Move both files to the base of the SD Card. Best way to do this is to plug your phone into your computer and move it like that. Make sure you phone is in USB mass storage mode. To change it, pull down the notification blind, choose USB connection, and choose USB Mass storage. Now copy and paste the two files to the new removable drive that showed up in your My Computer. The Epic-Unleashed11Deodexed.zip needs to be at the base of the SD card, and not in any folders. After moving all the files over to the phone, change the connection type back to Charge Only. Notfication blind -> USB Connection -> Charge only.
4. Install Koush Droid 2 Bootstrapper. Using an app installer, Astro File Manager, or equivalent, navigate to your SD card. The folder in Astro File Manager will be called sdcard. Choose Droid2Bootstrap.apk and install it. Follow the directions.
5. Now that it is installed, open Droid 2 Bootstrapper located in your applications section menu. It'll probably ask you for Super User access, say yes.
6. Press Bootstrap Recovery. It'll probably ask you for Super User access, say yes.
7. Next, we want to back your system file up by making a system image. In the Droid2 Bootstrapper, which you are already in, choose Reboot Recovery. Your phone should restart and load up into the custom recovery.You should see some green text with various options, and a little lower than the middle of the screen, it says ClockworkMod Recovery.
Notes for navigating through the system. You need to use the keyboard to navigate. "Enter" will select. "Del" will cancel/go back. and the arrows are movement.
8. Using your slide out keyboard, scroll down to backup and restore and press the enter key. It should take you to another window. Choose Backup. Let it runs it's course. After it is all said and done. If it does not bring you back to the main menu after this backup press the power button.
10. Using your keyboard buttons, choose mount and storage. And then choose mount /system. After that, press del to go back to the main menu.
11. Using your keyboard buttons, choose install zip from sdcard.
12. You need to make sure signature verification is off. Choose toggle signature verification and make sure it is off. At the bottom, under ClockworkMod Recovery, it'll say whether or not signature verification is enabled or disabled. You want it to say that it is disabled.
13. Then choose install zip from sdcard. Choose Unleashed2.0-D2.zip. It'll ask to confirm. Scroll down to Yes, and press enter. You'll see some commands going and eventually say it is complete.
14. Now navigate back to the main menu by pressing "Del" on the keyboard. And restart your phone by choosing reboot system now. It'll reboot and that's it! You've installed Unleashed 2.0!
Note: Your first boot will take a little while, up to 10 minutes. PLEASE BE PATIENT.
If you need to undo this thing, boot back up into bootloader using Droid 2 Bootstrapper -> Reboot Recovery -> Back Up and Restore (after the reboot) -> Restore.
If you like this tutorial or any other tutorial, please feel free to show your gratitude by sending me a few bucks my way. I am a poor college student always trying to make ends meet. It's just more than writing a tutorial. Troubleshooting, helping others when they get lost, constant updating and rewording to make the process more simple. All donations are greatly appreciated, no matter the amount. $1 USD is good for two taco's at Jack in the Box! Paypal: [email protected]
And please don't forget about Matt. Send some love his way, too. It takes time create this stuff, not to mention troubleshoot, fix, and update. Make sure you send some love his direction. He needs money for a domain name. Paypal him at: [email protected]
If anyone comes across and problems with instructions, please let me know. I am going to try to keep this thread updated and easy to use.
= = =
How to Root Droid 2
http://forum.xda-developers.com/show...&postcount=164
How to SBF Recovery Droid 2
http://forum.xda-developers.com/showthread.php?t=770224
thanks for this
the link to koush bootstrap is messed up btw
And there's no step 9
Here you go!
http://koush.tandtgaming.com//motorola/droid2/Droid2Bootstrap.apk
Uh... It said it installed and stuff so I rebooted, but it been on the Moto logo for more than 20 minutes now. Is something wrong or should I keep waiting?
kjik said:
Uh... It said it installed and stuff so I rebooted, but it been on the Moto logo for more than 20 minutes now. Is something wrong or should I keep waiting?
Click to expand...
Click to collapse
Pull battery and reboot. Rebootstrap and boot to recovery. You most likely forgot to mount system before flashing.
If for any reason I needed to go back to stock do I just do a recovery?
Yeah. Just boot back up in recovery, choose back up and restore, then backup, and choose a back up. In order to restore to a back up, you would have previously had made a back up.
darkonion said:
Yeah. Just boot back up in recovery, choose back up and restore, then backup, and choose a back up. In order to restore to a back up, you would have previously had made a back up.
Click to expand...
Click to collapse
Thanks! Just wanted to make sure, im all backed up and ready to go. But now I can't decide Epic or Tranquility? Mmmm
Just wondering why wiping isnt suggested...yet/
Coderedpl said:
Just wondering why wiping isnt suggested...yet/
Click to expand...
Click to collapse
No need to
Can someone post a mirror to this rom release, I've been trying to flash 2.5 and its not workin at all... wanna try to flash 2.0 then upgrade.. thnx in advance
Sent from my DROID2 using Tapatalk
Vanilla FroYo FRF91
For your Droid2, DroidX & Droid2 WE
Brought to You by Team DeFuse - AngDroid, Matt4542 & Drod2169
Splitting Blur from your Moto Droid.
Twitter:
@AngDroid
@Matt4542
@Drod2169
Web:
www.teamdefuse.com
IRC:
http://webchat.freenode.net/
Channel #fissionrom
Thanks:
Thanks to all the developers before me who shared their knowledge for me to get where I am now.
Thanks to Koush for Bootstrap recovery.
Thanks to cvpcs for the 8mp AOSP Cam package in DX build.
Thanks to FreeWell for the overlcoking kernel and WalCS for all the overclock testing on D2.
Thank you to all in the IRC chat ROM for all the help.
Whois Team DeFuse:
AngDroid - Project Manager & Developer
Matt4542 - Developer
Drod2169 - Developer
Redflea - Forum & IRC Tech Support
WalCS - In house overclock nut
Darkonion - Guide Creator
Breif History:
This ROM came to be by being bored and not sure what else can be modified with the software Moto so lovely gave us on our devices. I stumbled on the Droid2 SDK and gave it a look to see what was inside. To my surpise it was a clean ROM. No signs of Blur. I thought to see if it would boot on device and it did. The resolution was horrible and the device was so slow. I told Matt and we began to get the system up and running. In no time we had a more stable system. AOSP packages were created for our app folder and here we are now. Along the way Drod2169 asked if I needed some help porting it over to the DX so he joined up to help us create the DroidX version.
About ROM:
First Vanilla ROM for Droid2, DroidX & Droid2 WE!
First ROM for Droid2, DroidX % Droid2 WE that can be overlocked!
This is not an AOSP ROM but all stock packages are built from source. It is a complete set of vanilla Android applications. All Blur has been removed so it is the closest you will get to a true AOSP clean ROM for the Droid2/X/WE/Pro right now. This is not a themed ROM to make it look like AOSP ROM.
The purpose of this ROM was to remove all Blur and have a real Android experience. Please do not ask to add anything to ROM. Everything that is missing can be found in the Add On folder that was created when you installed ROM or can be downloaded from market.
The installed applications are all of your basic Android apps. Gmail, Voice Search, Car Home, YouTube and some other apps are missing since there are more updated versions on the market.
ROM has root, deodexed and zip alligned.
All downloads and support will be provided HERE.
It is hard to support so many different forums so that will be our new home base for now.
Thanks!
hold hold hold
Instructions to Apply Fission 1.1 Final
Please READ each direction CAREFULLY and BEFORE executing each step. I can not stress how many mistakes are made because someone did not READ the directions carefully. So... yeah, once again, READ THE DIRECTIONS CAREFULLY!
How to apply Fission!!
Credits: The ROM was created by AngDroid and Matt4542 and some other peeps. Tutorial was written by me. You'll need to be rooted in order to run the Droid 2 Bootstrapper.
Information on how to root the Droid X and Droid 2 can be found here:
http://forum.xda-developers.com/showthread.php?t=782556
The fine print: Matt4542, AngDroid and/or I (DarkOnion) can not be held responsible if you mess up. If you mess up, you mess up. That's why I wrote the .sbf recovery tutorial. Matt has also written one. More simple, but requires Linux.
Here we go.
1. Download Koush Bootstrap here (for Droid 2).
http://koush.tandtgaming.com//motorola/droid2/Droid2Bootstrap.apk
Link for Droid X coming soon!
2. Download Fission!
Link in previous post!
3. Move both files to the base of the SD Card. Best way to do this is to plug your phone into your computer and move it like that. Make sure you phone is in USB mass storage mode. To change it, pull down the notification blind, choose USB connection, and choose USB Mass storage. Now copy and paste the two files to the new removable drive that showed up in your My Computer. The Epic-Unleashed11Deodexed.zip needs to be at the base of the SD card, and not in any folders. After moving all the files over to the phone, change the connection type back to Charge Only. Notfication blind -> USB Connection -> Charge only.
4. Install Koush Droid 2 Bootstrapper. Using an app installer, Astro File Manager, or equivalent, navigate to your SD card. The folder in Astro File Manager will be called sdcard. Choose Droid2Bootstrap.apk and install it. Follow the directions.
5. Now that it is installed, open Droid 2 Bootstrapper located in your applications section menu. It'll probably ask you for Super User access, say yes.
6. Press Bootstrap Recovery. It'll probably ask you for Super User access, say yes.
7. Next, we want to back your system file up by making a system image. In the Droid2 Bootstrapper, which you are already in, choose Reboot Recovery. Your phone should restart and load up into the custom recovery. You should see some green text with various options, and a little lower than the middle of the screen, it says ClockworkMod Recovery. We are going to call this the main menu.
Notes for navigating through the system. You need to use the keyboard to navigate. "Enter" will select. "Del" will cancel/go back. and the arrows are movement. You can also use the Volume Up/Down to navigate, the power button to cancel or go back a menu, and the photo trigger as okay.
8. Using your slide out keyboard or the volume control buttons, scroll down and choose backup and restore. It should take you to another menu. Choose Backup. Let it runs it's course. After it is all said and done, you will now have a back-up. If it does not bring you back to the main menu after this backup press the power button.
10. On the main menu choose mount and storage. And then choose mount /system. The option will become unmount /system after choosing it. After that, go back to the main menu.
11. Next, at the main menu, you'll need to wipe cache and then wipe data. First, scroll down to wipe cache partition and choose it. It'll take you to another menu confirming. Choose the yes option. It'll wipe. Go back to the main menu again, and do the same with wipe data/factory reset. Confirm by choosing yes.
12. Now you need to mount data. Go to mount and storage and choose the second option which is mount /data. The option will become unmount /data. Make sure that both /system and /data are mounted.
13. Next, go back to the main menu and choose install zip from sdcard.
13. Then choose install zip from sdcard. Choose (TheVersionOfFissionYouWant).zip. It'll ask to confirm. Scroll down to Yes, and press enter. You'll see some commands going and eventually say it is complete.
15. Next, at the main menu, you'll need to wipe cache and then wipe data AGAIN. Scroll down to wipe cache partition and choose it. It'll take you to another menu confirming. Choose the yes option. It'll wipe. Go back to the main menu again, and do the same with wipe data/factory reset. Confirm by choosing yes.
14. Now navigate back to the main menu. And restart your phone by choosing reboot system now. It'll reboot.
Note: Your first boot will take a little while, up to 10 minutes. PLEASE BE PATIENT.
15. After the reboot is complete, you need to do a factory reset inside of Android. Press the menu button in the bottom left of your phone (image of the 4 squares), choose settings, then privacy, then choose factory data reset. It'll give you a warning and ask you to confirm. Go ahead and confirm. The phone should factory reset itself and then reboot.
16. After reboot, you need to enter your Android information again. Just follow the onscreen user interface until completion like when you did when you first got your phone.
If you need to undo this thing, boot back up into bootloader using Droid 2 Bootstrapper -> Reboot Recovery -> Back Up and Restore (after the reboot) -> Restore, and choose the restore file you want to restore to. The files are named by the date you
If you like this tutorial or any other tutorial, please feel free to show your gratitude by sending me a few bucks my way. I am a poor college student always trying to make ends meet. It's just more than writing a tutorial. Troubleshooting, helping others when they get lost, constant updating and rewording to make the process more simple. All donations are greatly appreciated, no matter the amount. $1 USD is good for two taco's at Jack in the Box! Paypal: [email protected]
If anyone comes across and problems with instructions, please let me know. I am going to try to keep this thread updated and easy to use.
Thanks for all your hard work on this rom, guys.
It's a billion times better than stock!
Donation coming your way the second I get paid next week.
After following the instructions exactly, I don't have root.
Any ideas why?
EDIT: I took the question to the forum linked above ("All downloads and support will be provided HERE.")
eleventy said:
After following the instructions exactly, I don't have root.
Any ideas why?
Click to expand...
Click to collapse
This doesn't appear to have root (even though the readme says it does). I rooted again, and everything seems to work ok.
It does you just need to download superuser from the market and wallah~. This rom is impressive. Appreciate it and looking forward to updates
i lost root =[
installed superuser.apk from sd card, but when opening apps that require root it says its not able to obtain root access. Normally superuser would pop up a message and i would allow it. In this case it wasn't happening. I had to re-reoot, then was able to use bootstrap to reeboot in recovery. Flashing back to my old rom and wait til further notice. Besides that its a GREAT rom and love it.
new ROMs have been uploaded that include superuser app in system/app so it comes with rom.
When/if an updated superuser app and you isntall it please dont come here asking for help cause you have to superuser apps in the draw if that does happen. It was left out for a reason. I never lost root during the building stages of ROM and not sure what is going on so I just threw superuser back into the sytem/app folder.
I followed every step exactly and I did not lose root. Thank you guys for all your hard work. The new bootup screen is a nice added touch also!
Swyped from my Droid 2 using the XDA app
I've been reading that any rom for droid 2 will brick my r2d2...does this include fission?
Sent from my DROID2 using XDA App
Yes
Sent from my DROID2 using XDA App
Works beautifully, but there's definitely something up with this root business. Had to reroot and was fine.
Sent from my DROID2 using XDA App
No problems here. Great ROM. Maintained root.
Boot Animations
Anyone else having trouble installing the D2 Boot Animation? Is there a trick to it?
Anyone have trouble installing the d2 gallery?
Sent from my DROID2 using Tapatalk
Any luck w/ the contact ringtones yet? As of Test5 they still refuse to work on my phone
I am having The same issues. Everything else works great but gallery was missing, so I installed d2 gallery, then after install it was missing as well.. tried to install the dx, same issue. Then tried to install the android stock one and same issue no gallery.
Everything else works freaking great! Hats off to the devs..
This being a blur-less ROM and all, what kind of dependancies would I have to add back in to get some of the blur back in here?
I really dig the messaging, gallery, camera, and keyboard.
PART2: Now since this is a blur-less ROM would it be safe to use metamorphs as system files should be the same as most stock devices?
Gallery Issue
Guys, Freaking Great Job!! Hands down best rom I have had on D2.
Only issue I ran across is the Gallery is missing and I installed d2 gallery and its still no where to be found. Even tried to install the dx and stock with no luck.
Any Idears?
-Mike
Hey all, just wanted to give a quick rundown. I shared this on Slickdeals earlier and someone recommended I throw it over here so that it might help anyone. My Coworker got his gTablet yesterday (from the Woot deal in March) and I had the chance to play with it/flash a custom ROM.
First about the stock ROM. His had angry birds and flash preinstalled, there were some funny directories setup on the internal storage which included a few apps (angry birds and flash amoungst them). I suspect they did some funny business at the factory with our units, but it did not in ~ANY~ way appear to be used/returned etc. The directories I remember were "Master", which I believe had apps and ... Oh hell it's too long now, something else. Anyways it didn't appear to be anything other than new is my point.
Next, the screen. It was definitely a TN panel and did have some odd viewing angles, and while not ideal it was certainly not anything that was preventing one person from enjoying it, vertical or horizontal. It was difficult for others to gather around and see videos well, so if that is a large concern for you then be concerned I suppose.
The stock ROM. It came with 1.1-3381 (or whatever the 33 was). It really does suck. They disable the menu button in most locations with the stock ROM, and it was slow/sluggish just like everyone has been saying.
Now I hope this crash course is of some help to anyone with their new toy. First to check your ROM version, you can go tab the Gears icon at the side of the screen, then choose About in the left menu. In here you'll find the rom version (should be something like 1.1-3389, 1.1-3588 or 1.2-something). Here's what I did to get his updated. Get familiar with XDA, it'll be a great friend and resource.
1.) I loaded the 1.1-3588 stock recovery, an upgrade from the 1.1-3389 recovery. It was possible to do this by going to this page (don't forget to thank Roebeet for putting all of this together), downloading the "3588 Recovery Pack v1.0".
2.) Unzip the 3588 Recovery Pack v1.0 then connect your tablet to your PC and enable USB mode (when you plug it in, you'll need to click the Yellow/Orange circle in the upper-right, then choose to enable USB tethering). Copy the "recovery" folder, and the update.zip to the root (what opens when you double-click the tablet drive) of the tablet internal memory (Probably D: or F: ).
3.) After the files copy to the tablet, turn off USB tethering, then turn off the tablet. You'll be restarting it in Recovery, which will automatically load the new recovery.
4.) To start the tablet in recovery, have the tablet turned off, then press and hold the power button and volume + button. You'll see a small message in the upper-left to indicate that it is starting in recovery. You can release the buttons now.
5.) After the update finishes installing the tablet will automatically reboot to Android once again, with the ugly Tap And Tap interface. This is OK, you're two steps from fixing it.
6.) Turn on USB tethering again, then open the tablet folder and delete the recovery folder and update.zip.
7.) Go back to this page, and once again thank Roebeet, and download "clockworkmod .8 bekit". Once downloaded, unzip it, then copy the recovery and update.zip to the root of the internal memory again. Turn off the tablet.
8.) Start the tablet in Recovery again by holding power button and Volume + at the same time. Once again you'll see a message in the upper-left and you can release. It'll do its thing and reboot to Android when it completes.
9.) After you get into Android again, start USB Tethering then delete the recovery folder and update.zip.
10.) At this point you can load what ROM you want (within limits, BE SURE TO READ THE ROM THREADS FIRST). I installed Vanilla AOSP Gingerbread ROM. Go download the file from that thread, then place it into the root of your tablet internal memory. Be sure to thank kornyone for their work. Also be sure to download the "gapps" available on this page as well, for you will have to install it to have the Android Market, GMail, etc.
11.) To install it, turn off the tablet, reboot into Recovery (Power button & Volume + at the same time..). You'll now be in Clockworkmod, a custom recovery. You can navigate the custom recovery by using the volume rocker to go up and down, the power button to go back a menu, and the Home soft key to press enter.
To properly install a ROM you should always first clear the data/system/cache. It's been a while since I've used clockworkmod, but I believe the option you are looking for is Factory Data Reset, choose Yes on the next screen. Then delete cache just to be sure.
Now you can go to "Install ZIP from sdcard", then "Choose zip" or something akin to it. Navigate to the file you copied, and tell it to install. Wait a short while and you should see that it successfully installed. Now just press the power key a few times to get back to the main menu and then choose to Reboot (whatever the top option is).
Enjoy your Gingerbread Android.
A few app recommendations: I use LauncherPro. It's available in the Android market and it's a "Home" replacement. Try it out, it's smooth and it has a bunch of extra widget if you purchase the program (1.99). Also check out Dolphin Browser HD. The last word of advice I can give is to get familiar with Long Press, it's basically right-click in Android. To do a long press just hold down on an icon or a blank area and see what happens.
A round of thanks go out to Roebeet and kornyone for putting the files used together, and a special thanks for the excellent documentation Roebeet. If I've left anyone out or placed this post in the wrong section please let me know and I'll get it fixed.
newbie question
I load the clockworkmod recovery and nothing changes. How do I get the clockwork mod to work? I already have my gTablet rooted. Now just trying to get to where I can load a custom ROM.
Thanks
apboswell said:
I load the clockworkmod recovery and nothing changes. How do I get the clockwork mod to work? I already have my gTablet rooted. Now just trying to get to where I can load a custom ROM.
Thanks
Click to expand...
Click to collapse
If you have flashed clockwork properly then to power on your device hold the volume up key as press the power button. This will load the recovery kernel and the clockworkmod, from which you can backup your device and install custom roms.
Just wanted to posted a quick update -- Two of the tablets that people at my workplace ordered suffered an odd corruption of the internal memory. The symptoms were random app's force closing, then upon trying to reboot the device it simply boot loops (the OS screen displays, then flips back to Viewsonic -> Load screen, repeat endlessly). Got them booted into recovery and tried to load data to which it reported the data partition could not be loaded due to the block being inaccessible. After a quick search the solution to this problem if you encounter it is:
1.) Boot into clockworkmod .08 by holding the power button and volume + button until you see the Recovery key press detected in upper-left.
2.) Go to advanced using the volume buttons, then press the home key to enter the advanced menu.
3.) In here go to Partition SD Card and select 2048, then 0. Wait a few minutes and the data partition will be ready to go again.
At this point I went ahead and did formatted the following partition through the mount menu: boot, system, data, cache. Afterwards I loaded the ROM again and everything appears to be working well.
Hope this helps anyone else who gets this random error.
Good post! Thanks!
The SD repartitioning is a very common fix here, in XDA. Usually it's what we try if you have weird FC's or file corruption and a re-flash or data wipe doesn't fix things. I've had to do that at least twice on my own device, over the last 3 months or so.
Also, keep in mind that the 3588 Recovery Pack is designed with a rooted ROM in mind (it lets you flip back and forth between clockworkmod and standard recovery via a script that can run off the GTablet or via adb)
Fool proof way to install 4349:
The reason there are so many steps is that they are broken down so that each step is basically one menu action. Follow EVERY step. Yes there are easier ways, this way ensures that your tablet is absolutly stock and wiped of all traces of other roms.
What you need:
1. A g Tablet with CWM 0.8 recovery (doesn't matter what ROM)
2. A stock 3588 image renamed to 'stock3588update.zip' (http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip)
3. A stock 4349 image renamed to 'update.zip' (http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-4349-user.zip)
4. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
4. Calkulin's Format_all.zip (attached here: http://forum.xda-developers.com/showpost.php?p=11946224&postcount=1)
Step 1: Ensure there is nothing on your g tablet you want. NOTHING!
Step 2: Boot to CWM recovery with Pwr and Vol+
Step 3: Go to the "mounts and storage" menu
Step 4: Choose "mount USB storage"
Step 5: Confirm there is nothing you want to save on your SD card. If there is anything you want, save it now.
Step 6: "Unmount" and go back to the main CWM Recover Menu
Step 7: Choose "advanced"
Step 8: Choose "Partition SD Card"
Step 9: Choose 2048M for Ext size
Step 10: Choose 0M for swap size
Step 11: Watch it Partioning SD Card, then when complete once again mount USB storage as in steps 3/4
Step 12: Load onto the SD Card: Calkulin's_FORMAT_ALL.zip, stock3588update.zip, update.zip (this is the 4349 file), the recovery folder with the command file inside it. Your Sdcard should look like the attached screen grab.
Step 13: Unmount and return to main menu of CWM.
Step 14: Choose "install zip from sdcard" then "choose zip from sdcard" and select "Calkulin's_FORMAT_ALL.zip"
Step 15: Proceed with the install, once finish select "choose zip from sdcard" and select "stock3588update.zip"
Step 16: Once it completes, go to the CWM recovery main menu then power off with the power button.
Step 17: Boot up into recovery with PWR and Vol+. This will initiate the 4349 install using the stock recovery.
Step 18: Watch your tablet boot into a bone stock 4349 rom.
An optional starting point for this is to use nvflash (back to stock recovery or CWM recovery) to repartition everything first to make fully sure all partitions are as they should be.
Nice! Well laid out with clear steps. I 100% agree that the cleaner your device is, the more likely that the 4349 upgrade will succeed. On clean 3588 stock, I've had about a 90% success rate, at least (but I have had a few soft-bricks too).
Going to work on 3588 nvflash today - need to test it out as I think we all really need it, at this point.
Just one question for clairifacation.. on the command line of text. Should it have the have the apostrophy and the beginning and end or not?
LisaBham said:
Just one question for clairifacation.. on the command line of text. Should it have the have the apostrophy and the beginning and end or not?
Click to expand...
Click to collapse
No, corrected. Thanks.
Just to post a bit of an update:
It is pretty easy to get rooted with z4root. The permanent option works. Also, installing the amazon marketplace was no problem. I actually like this setup better than google market because it stores all the free apps you download as well as the paid ones.
Additionally, the google apps (download from here: http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps get the ones for tegra on CM6) from CM6 were easy to install with the standard recovery. Looks like this latest stock version is pretty decent overall.
ramerco said:
installing the amazon marketplace was no problem. I actually like this setup better than google market because it stores all the free apps you download as well as the paid ones.
Click to expand...
Click to collapse
The biggest problem with the Amazon Appstore for Android is that it has far, far fewer apps than the Google Android Market. A large majority of the applications that I require (indeed, what I bought the tablet to run in the first place) are only available through the Google Android Market.
Followed step by step and everything seemed to go well until I tried to restart after the upgrade....nothing but a black back-lit screen. Tried resetting/factory reset, tried clearing cache, nothing. Had to NVFlash back to 3588 and tried to see if there was an OTA update but it says I am up to date with 3588. Then tried to manually install the 4349 update.zip which appeared to go through but again, same black screen afterwards. Very frustrating.
tsg2513 said:
Followed step by step and everything seemed to go well until I tried to restart after the upgrade....nothing but a black back-lit screen. Tried resetting/factory reset, tried clearing cache, nothing. Had to NVFlash back to 3588 and tried to see if there was an OTA update but it says I am up to date with 3588. Then tried to manually install the 4349 update.zip which appeared to go through but again, same black screen afterwards. Very frustrating.
Click to expand...
Click to collapse
Sounds like you were stuck in apx mode. Lucky you were able to boot at all!
jason1332 said:
Sounds like you were stuck in apx mode. Lucky you were able to boot at all!
Click to expand...
Click to collapse
Could be, but I don't think so. I got through the 3 birds screen then the g-tablet screen before it went black so I don't think I was in apx. I guess I will just wait until VS pushes the OTA Update again.
Is there any way to change the boot animation in 4349?
ideaman said:
Is there any way to change the boot animation in 4349?
Click to expand...
Click to collapse
Boot animation is still stored in the same place (system/media) so existing methods for changing it should work fine.
Hi Gents,
Questions,
- Is this flash will void my warranty?
- If I'm running from stock 3855 Rom form VS, from what step I should begin with?
Thanks,
Charles
I'd like to make a formal request that this guide be stickied?
Many people have been wanting to flash the HC rom, and this is the best guide I've found (used it myself) to safely, and efficiently get to the 1.2 bootloader and stock recovery in update 4349.
It does not instruct anyone, or link to Roms on other forums, just provides them with the information to reach a foundation to where they can use 1.2 based bootloader roms. We can't ignore that it's an important catagory of users.
TJEvans said:
I'd like to make a formal request that this guide be stickied?
Many people have been wanting to flash the HC rom, and this is the best guide I've found (used it myself) to safely, and efficiently get to the 1.2 bootloader and stock recovery in update 4349
Click to expand...
Click to collapse
At that time this was a good way to do it. Now, you can NVFLASH 4349 in a few minutes. Then when you reboot wipe data/cache.
jcflman said:
At that time this was a good way to do it. Now, you can NVFLASH 4349 in a few minutes. Then when you reboot wipe data/cache.
Click to expand...
Click to collapse
regardless, there isn't a stickied guide on safely getting to 1.2 from out of the box setup...this is the most comprehensive one I've found for a brand new user that doesn't have any experience with nvflash (I still don't) or even flashing a rom. I've answered 2 questions today from people that basically just opened the box and were wondering how to get to 1.2 from stock. or wanted a link to a stock rom/recovery image. I haven't found any other posts that have a stock 3588 or stock 4349 files link in it. This post does, without even going into the roms available for the 1.2 bootloader.
Thanks ramerco. This is exactly what I've been looking for. I am still relatively new to the G-Tab and ROMS and need more details, which you have provided. I've been looking for "detailed" steps to get to 4349 along with 1.2 boot loader since I want to try roebeet's HC.
jcflman said:
At that time this was a good way to do it. Now, you can NVFLASH 4349 in a few minutes. Then when you reboot wipe data/cache.
Click to expand...
Click to collapse
I'd like ot bump this, and request again, that this post be stickied. More and more people are having issues when flashign from 1.1 to 1.2 roms, and THIS GUIDE is the SAFEST and MOST COMPREHENSIVE guide on how to go from 1.1 to 1.2.
Yes, it may be quicker to NVFlash as much as you possibly want, but I'll bet that if you found every post about a softbricked G-Tablet, the user was trying to NVFlash something...
It seems to me at this point, that developers are NVFlashing everything nowadays..that's fine, becuase most of them know how ot recover from it. Typical USERS, though, do not, and end up making their situation worse. WE NEED TO PREVENT PROBLEMS, so using standard recoveries, or CWM over NVFlash is the safest way to do it. I have no problem learning NVFlash to recover from a softbrick, but I'll be damned if learning it and using it CAUSES a softbrick becuase I have no idea what I'm doing.
PLEASE Sticky this thread, and clean up some other stickies that are no longer needed. For instance, Jerdog's "One and only Honeycomb" thread...not necessary anymore, since the reality he predicted wouldn't happen, has.
Wi-Fi
Who knows how to set up Wi-Fi on Linux.
Shall describe the step by step please.
how do you create file
I am really new at this. So how to you do this step?
4. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
What is the step-by-step process for this? I know how to create a folder, but I dont know how to create the file with the code. Can someone help me with this. Thanks I have Windows 7 if that matters.
novicexda said:
I am really new at this. So how to you do this step?
4. A folder called recovery with a file in it called COMMAND inside it with the following line of text:
Code:
--update_package=SDCARD:/update.zip
What is the step-by-step process for this? I know how to create a folder, but I dont know how to create the file with the code. Can someone help me with this. Thanks I have Windows 7 if that matters.
Click to expand...
Click to collapse
You might have a copy of the recovery folder with command file on your pc where you unzipped the cwmod_internal.zip unless you moved it to your G Tablet instead of copying. You could always unzip the cwmod_internal.zip file again to pull the recovery folder from it. Anyway, to answer your question...
To create a file just open the recovery folder you just created then right-click > new > text document. Put the code "--update_package=SDCARD:/update.zip" without the quotes & save the document as command. It shouldn't have a file extension like command.txt just command only.
**** USE AT YOUR OWN RISK ****
The following is posted so that I may share what I've done. It was done by me and for me. If you use it for you, then you take responsibility for whatever happens. This could, potentially, cause problems. It certainly will void your warranty (though it's pretty easy to undo this with no obvious signs.)
Install ClockworkMod Recovery and roots your P6210 tablet.
DO NOT ATTEMPT TO RESTORE ANY CWM BACKUP MADE WITH ANY OTHER VERSION/REVISION. IT WILL BREAK THINGS. THIS VERSION IS NOT BACKWARDS COMPATIBLE. JUST START WITH FRESH BACKUPS AND BE HAPPY.
WHAT THIS DOES:
Installed from recovery, this .zip will first ensure that it's running on the Samsung GT-P6210. If you have a different model, don't waste your time downloading it. It won't work. I have a P6210 to test with. I don't have any other 7 plus tab, so I can't test any other 7 plus tab, and therefore won't even act like it might work. If you want to try it anyway, you should have the knowledge to repair whatever you break - in which case you'll also have the knowledge to unpack this zip file and do things the manual way.
(starting with 20111210, a backup of the recovery is no longer made. I feel this is no longer needed as there is a confirmed working ODIN package people can use to restore their tablets with.)
Next, a new version of the clockwork mod recovery is installed.
(starting with 20111210, old backups are no longer purged. If you are upgrading from my original CWM recovery (previous to Dec 9th), please manually delete old clockwork recovery backups, as they are NOT VALID and will destroy your normal boot operation if you attempt to restore with a proper/current version of this recovery.)
Finally, the tab will be rooted. This only involves copying a tiny file (called 'su') to the system. In order for most android apps to make use of that, however, another application must be first installed. (See "Finishing SuperUser installation" below.) I considered putting that "SuperUser" application as part of this package, but it's really very easy to get it from the market.
INSTRUCTIONS:
Put the installation zip file on your tablet's external SD card. If you don't have an external SD card, you won't be able to install this. MicroSD cards are cheap. If you have a tablet that costs 399 USD, you can afford to spend a few extra dollars/euros/pesos/whatever on a microSD card. Just get one. Not only is it required for installing this from the factory recovery, but it makes a great place to back things up to. A nice 16GB card is suggested. 32GB is better. You'll need AT LEAST 1GB for this recovery. If you have a previous version of CWM already in-place, you won't need the storage card.
You can download the .zip file directly to your tablet and then possibly use the built in "My files" applet to move it to extStorages/SdCard, or you could download it to your computer and use "adb" to push the file to /mnt/sdcard/extStorages/SdCard, or you should be able to get it there with "Kies." If you have the proper adapter, you could also attach the microSD card directly to your computer and just copy it there. It doesn't matter HOW you get it on the card, as long as it's on the card.
After the zip file is on your microSD card, and the microSD card is inside (and recognized by) your tablet, then you need to...
Boot into recovery mode.
If the recovery version banner is "CWM-based Recovery v5.x.x.x", then you already have a version of CWM installed and should skip ahead to the proper section. If the banner is "Android system recovery (3e)", then you have the factory recovery and should continue with...
Installing from factory (3e) recovery:
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "apply update from external storage"
2. Select the file you placed on your storage card (starts with "p6210_CWMR".)
3. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
4. Select "reboot system now."
You now have a CWM-based recovery installed, and your tablet is rooted.
Please skip ahead to "Finishing SuperUser installation"
---------------------------------------------
Installing from CWM-based Recovery
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "Install zip from sdcard"
2. Select "choose zip from internal sdcard" (which will actually point to the external card.) (If you are upgrading and chose not to put the .zip on the external microSD card, you might need to select "choose zip from sdcard" instead.)
3. Select the file you placed on your storage card (starts with "p6210_CWMR".)
4. Select "Yes - Install (whatever filename you selected)"
5. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
6. Select "+++++ Go Back +++++"
7. Select "reboot system now."
---------------------------------------------
Finishing SuperUser installation
Install the SuperUser application directly from the android market:
https://market.android.com/details?id=com.noshufou.android.su
....
Post-installation Notes and Issues
It's a known issue with the version of CWM used in this recovery that the "internal sdcard" actually references the built in storage on the tablet. So, if you want to back up to your microSD card, choose "backup to internal sdcard". I'm retaining this issue to stay "compatible" with other CWM recoveries of the same version number. (won't fix)
The .zip package displays an incorrect version identifier/date when version 20111209 is being installed. (It's shows a banner with the date of 06-Dec) (cosmetic)
This recovery is NOT compatible with firmware updates via Kies (and perhaps not via other samsung official methods.) In order to perform a firmware update, I suggest the following procedure: First, perform a CWM Recovery backup, then use the ODIN package found elsewhere to restore this tablet to a factory state. Let Kies upgrade the tablet to whatever version it wants (give it a few tries in case multiple upgrades are needed.) Then re-install this recovery, and perform an "advanced restore" (or "advanced restore from internal sdcard if you made the backup using the similar option.) From there, restore "data." That will leave the entire firmware update in place. (boot is the normal boot kernel; system is what people like to call a ROM here, but is the samsung pre-installed apps; and data contains the applications you install and all your data.) Then "go back", wipe the cache partition, advanced, and wipe the dalvik partition. HOWEVER, please note that I have no way to know if any given samsung firmware update is "compatible" with this restore unless I've tried it myself. It's compatible with everything released up to the date of this note (10-Dec-2011), but I can't predict the future.
Donation?
I don't take donations. If you have spare money (I don't), please donate it to the Salvation Army, Red Cross, or just find a homeless person on the street and give them something. My favorite charity is the Shriner's Hospital for Children. (yes, I am.) If you'd like to thank me, there's a button at the bottom of this post dedicated to that. If you don't want to thank me, that's okay too.
Changes for 20120107:
Brought the recovery kernel up to date with the normal boot kernel. The only impact should be that if you keep crashing any time you boot normally (and before you are able to perform any action), you can now boot into recovery to _hopefully_ be able to retrieve the /proc/last_kmsg as a diagnostic tool.
Reduced the size of the .zip quite a bit.
Changes for 20111210:
* A backup of the existing recovery image is no longer being made. I feel this is no longer needed, as an ODIN package is now confirmed to be working that people can use to restore their tablets to a factory state.
* Old clockworkmod recovery backups are no longer being deleted when installing this. If you are installing this or newer from my CWM recovery previous to Dec 9th, 2011, please manually delete all those old backups. If you attempt to restore them, please be prepared to download ODIN and a factory ODIN image, as you'll need it in order to get your tablet working again. You've been warned...
* The issue that was causing backups to the tablet's built-in storage to fail has been corrected.
Changes for 20111209:
* Issues with getting into recovery are resolved.
* a backup of the recovery is only made if there is no sign of a previous version of this same recovery in place
Credits
Most obviously, Koush for his wonderful clockworkmod recovery. It's the basis of this entire project. Entropy512 for pointing me in the proper direction on a couple of things, pershoot mods to CWM for the Galaxy Tab 10.1 that I ported over to this one (due to the different partition structure of honeycomb devices.)
Links are below...
Take care
Gary
thanks gary, how might we be able to tell if this will be kosher with 3g version? do we need to --dump all pit via heimdall to ensure all partitions match up,etc? Thank you for your speedy work.
chrisrotolo said:
thanks gary, how might we be able to tell if this will be kosher with 3g version? do we need to --dump all pit via heimdall to ensure all partitions match up,etc? Thank you for your speedy work.
Click to expand...
Click to collapse
It's not kosher at all. I didn't wash my hands before compiling it, and had bacon bits on my salad for lunch. Sorry.
Thanks Gary. I have been watching your progress for about a week and you are like a put-bull. Amazing. u da man!!!
Pit bulls would be shamed as wussies. Many great devs possibly have a touch of Asperger's syndrome (with MUCH better socialization skills!) which, with tasks like this, is a benefit! At the very least just plain tenacious! lol
Thanks Gary. I've learned a lot just following along reading the discourse between you and others like Entropy. Appreciate it.
garyd9 said:
It's not kosher at all. I didn't wash my hands before compiling it, and had bacon bits on my salad for lunch. Sorry.
Click to expand...
Click to collapse
ahhh , close enough. anyways what could we do to find out without actually flashing this to possible incorrect partition??
chrisrotolo said:
ahhh , close enough. anyways what could we do to find out without actually flashing this to possible incorrect partition??
Click to expand...
Click to collapse
Which "3g" model do you have? The tmobile one or the international one?
I'm trying to narrow down which is the GT-P6200 and which is the SGH-T869!
I'm working with someone via PM and email to get the information needed for the SGH-T869, and I think it'll be pretty easy to get a recovery together for it, but other people will have to test and validate. I think this is the tmobile version...
international p6200
Soft Brick(kinda Sorta - well not really). Using defult 3e recovery. Tab would boot up, but would not go into recovery at all. Nada Nada. Thought it might have been some leftovers from other stuff I have been trying, so I odin3'd the factory image, did a wipe all and tried it again. Same difference. The only thing I could really think of was maybe I had a corrupted download.
funny thing is that it would boot up into the OS. Just not into recovery. will keep trying as I really want a way to make nandroid backups.
otamctech said:
Tab would boot up, but would not go into recovery at all.
Click to expand...
Click to collapse
No need to ODIN... that's why the package creates that backup recovery image. However, you said it's booting normally, correct? If so, it's not broken or bricked (and I experience the exact same thing.)
For some odd reason (that I haven't been able to figure out), after I flash a non-stock recovery, its very difficult to get the tab into recovery mode. Some times I get it instantly, and some times I have to try several times in a row. Are you using adb? If so, it might be easier. Power off the tab, plug it into your computer, and eventually the tab goes into a "low power mode" where you see the battery gauge but nothing else. From there (again, assuming you have adb installed/working), you can just run "adb reboot recovery" That usually gets me into recovery. 90% of the time.
If not, just try again. If you see the samsung animation starting, press/hold the power button to turn it off again, then press/hold volume up again... etc. It's a PITA, and a major annoyance of mine.
Two things about it make it REALLY annoying for me. First, I'm using samsung's own kernel for this... but I'm just repacking the initramfs portion of it. Second, if you put the factory recovery back, it's easy to get into recovery again.
chrisrotolo said:
international p6200
Click to expand...
Click to collapse
I'll get to that one eventually. I'm commited to do the tmobile one next, and I REALLY need to concentrate on my full-time job (the one that pays me a salary) which only leaves me a couple hours each day.
take care
Gary
absoultely, take your time. Is there a certain battery percentage requirement to get into either stock or CWM recovery say 50% or 60% minimum? we had this issue on dell streak 7. Let me know if I can help with partition layout or anything for p6200. thanks.
chrisrotolo said:
absoultely, take your time. Is there a certain battery percentage requirement to get into either stock or CWM recovery say 50% or 60% minimum? we had this issue on dell streak 7. Let me know if I can help with partition layout or anything for p6200. thanks.
Click to expand...
Click to collapse
No hard requirement I'm sure - but flashing at below 50% is just a stupid reckless risk, plain and simple as that.
If you are having issues getting into recovery after flashing this...
Here's a procedure I've come up with that has allowed me to get into this recovery 9 out of 10 attempts (and it doesn't require any special connections to a computer.) Please read all the steps before starting so you're prepared for what comes next. It'd really be annoying to have recovery finally pop up, but you weren't paying attention so the tablet turned off.
power off the tablet
Throughout this entire process the volume UP switch should be held and not released. This is the side of the volume switch closest to the power button. Once you see your recovery screen, you can release the volume switch (and any other button you might be holding at that time.)
Press/hold Volume Up (constant)
Press the power button, hold it down for 2-3 seconds, and release it.
You'll see the Samsung logo screen for a few seconds...
Instead of the expected recovery screen, you might see the samsung boot animation with music. If so, immediately (without releasing volume up), press and hold (and keep holding) the power button. Don't let it go this time.
The tablet will appear to power off after holding the power button for a few seconds, and then will power back on a second or two later.
(you're still holding that power button, right? how about volume up? Good.) Again, you'll see the samsung logo screen for a few seconds...
Instead of the boot animation, recovery should pop up this time. Release the power button as soon as it does or you'll just turn the tab back off again. You should also release the volume UP at this point.
(If you've flashed my recovery, please try this. If it doesn't work, please take the effort to reply to this post so I can know what people other than myself are experiencing.)
Take care
Gary
updated OP with:
Post-installation Notes and Issues
I'm aware that after flashing this, it is difficult to get back into recovery. I'm not sure WHY, but it's fairly consistantly a pain in the rear. However, I have found that following the steps in the following post seems to work (at least for me) 9 out of 10 times. (I was distracted on the 10th try, so not sure if it worked or not): http://forum.xda-developers.com/show...6&postcount=14
Remember above I mentioned that when this package installs, it creates a backup of the old recovery? Well, it does that no matter what recovery was in place. So, if you install this package with a factory recovery, that backup will be of the factory recovery (which is probably what you want.) If you install this package a second time when you already have the CWM Recovery installed, you'll overwrite that factory recovery backup with a backup of the CWM recovery (which makes no sense.) I'd strongly suggest that after you FIRST install this package, you make a copy of that backup recovery image file (and full filename is displayed when it's created), and stick that copy someplace safe. Perhaps just rename it and copy it to your SDcard or computer. A good name might be "p6210_factory_recovery.img"
The Tab 10.1 could be difficult to get into recovery too.
Usually, the following works for me:
Press and hold VolUp
Press and hold Power until the screen turns on (this is slightly different from your instructions)
Release Power but keep holding VolUp until Recovery shows
__________________
somebody9 said:
I was wondering if anyone knows what needs to be deleted in order to get rid of that pesky pop up menu you get by pressing on the Chevron/Arrow in the middle of the bar.
Click to expand...
Click to collapse
Please start a new thread for a new topic. Try to keep this one isolated to the CWM recovery.
garyd9 said:
Please start a new thread for a new topic. Try to keep this one isolated to the CWM recovery.
Click to expand...
Click to collapse
Sorry about that. Post removed.
Garys method of booting into recovery works fine. I'm just going to post it in linear format.
1. Press the power button and select Power Off
2. Press the volume up button (closest to power button) and do not release until the recovery screen is displayed
3. Press (do not hold) the power button
4. The static Galaxy 7.0 Tab Plus screen will display (possibly twice)
5. When the animated Samsung screen displays, press and hold the power button
6. The static Galaxy 7.0 Tab Plus screen will display
7. Release all buttons when the recovery screen displays.
This works every time for me