Related
This update.zip will flash clockwork recovery, overwriting the need/ability to use the stock recovery folder with command in it.
For advanced users only.
v.8 Download: http://www.mediafire.com/?dvleg4oatkfxm7w
The credit for this all goes to Bekit for the biggest step forward on the Gtablet, and obviously Koush for the custom recovery to begin with. Roebeet packaged this update.zip.
Instructions:
1) Unpack download to root of sdcard. (Internals /sdcard, NOT /sdcard2)
2) Start tablet while holding volume + and power. (Let go when you see text come up saying entering recovery)
3) You will see a short installation and it will reboot.
4) Check the install by powering off, the powering on with volume+ and power
5) You should be greeted by a menu with Clockworkmod at the top
i have been using clockwork on my gtablet for several days now. it backs up and restores just like i would expect it too.
well done as usual.. props for all involved.
Works great no problems at all !!!
wishlist:
1. add SDCARD2 to the mount and storage section.
2. ... wait that is it.!
Should I be able to take this file and rename to update.zip, put it in the root of "sdcard" internal space, put the recovery folder in root directory too and then boot up with power + volume up to install this?
rushless said:
Should I be able to take this file and rename to update.zip, put it in the root of "sdcard" internal space, put the recovery folder in root directory too and then boot up with power + volume up to install this?
Click to expand...
Click to collapse
thats how i did it
rushless said:
Should I be able to take this file and rename to update.zip, put it in the root of "sdcard" internal space, put the recovery folder in root directory too and then boot up with power + volume up to install this?
Click to expand...
Click to collapse
Or just extract the zip file supplied in the first post onto the sd card. Everything will go into its place. Then boot from recovery using power and volume+.
So, if I place the cwm update.zip and recovery folder in the root of sdcard (internal), then when I boot into recovery, CWM will show up instead? Just want to know if it really is that simple. Also, if I want to flash a new ROM (Like the zpad one), do I simply place the update.zip from that rom anywhere other than the root of "sdcard", and flash using CWM?
One last question, if I delete the CWM update.zip, is it like CWM was never placed on my g tab?
Am I the only one having trouble getting cwrecovery on the root of sd card? cant get this to run. i am a visual learner and reading how to do all this is helping me very little. if anyone would be willing to do a video or reference me to a link so i can learn to do all this, i would appreciate greatly. this is very frustrating tab stock!
hey this might help you get it installed..
plug your gtablet into your computer, then on the gtablet, click the "enable usb storage connection" button
then on your pc, open windows explorer, and open removeable drive F, the letter may be different for you.. it should show 13gb free on it, and there should be an android folder and a dcim folder.. that's the root of the storage inside the tablet.. it's the same as sdcard.. unzip the clockworkblahblah.zip to the root/top level directory of that removeable drive. then turn the tablet off. and then hold down the volume + button while powering it back on, it should install the clockworkmod recovery manager.. that's about it
jw52637 don't feel bad... I'm a visual learner as well.
uncola,
I followed your instructions and I saw the update install on boot up. Now I'm lost. I expected to see and application named ClockworkMod Recovery or something like that... but I did not. How do I know it is installed and how do I use it to back up my stock ROM? Also, do I remove the "update.zip" from the root directory or just leave it there?
Sorry for the questions but I want to learn how to do this so I can stop bothering you guys.
mmracing said:
jw52637 don't feel bad... I'm a visual learner as well.
uncola,
I followed your instructions and I saw the update install on boot up. Now I'm lost. I expected to see and application named ClockworkMod Recovery or something like that... but I did not. How do I know it is installed and how do I use it to back up my stock ROM? Also, do I remove the "update.zip" from the root directory or just leave it there?
Sorry for the questions but I want to learn how to do this so I can stop bothering you guys.
Click to expand...
Click to collapse
ClockWorkMod Recovery is the recovery system...so you have to boot your tab into recovery (hold volume + and power the tab up). If installed, you'll get the ClockWorkMod Recovery instead of the stock recovery system. You can make backups, do restores, install .zips, etc... from there.....then "reboot" the system to boot back to your normal system.
Thanks tcrews. I moved the update.zip from the root directory to a saved directory then rebooted holding the volume + key and it booted into ClockWorkMod Recovery. I chose back up and everything seemed to backup fine.
So if/when I install another ROM and I do a restore to the ROM I just backed up I should be right back to where I was at that time. I have used Titanium Backup to back up all my applications and settings and know I would have to restore them also.
I'm just wanting to understand how I can get back to "stock" so that I can get the automatic updates from Viewsonic.
Well i just tried it all again, and all worked very well. Thank you very much
Ok, I'm totaly new to this so please bare with me, having some troubles with my G tablet NOT booting so I cant access it through Windows to install CW to fix my tablet. How can I get the Files on the tablet? I can get it to attempt recovery but no luck. PLEASE help. I'm pulling my hair out here.
Anyone know how or am I sol and should try and sent it back?
maccaw1 said:
Anyone know how or am I sol and should try and sent it back?
Click to expand...
Click to collapse
There is a physical reset button inside the device, or you can try ADB.
I cant get the recovery image to find update.zip
I have clockwork recovery gtab-cwm-v08 installed and renamed to update.zip in the root of the internal sd but when i boot into recovery it goes to the android screen then shows a triangle with a exclamation point, then reboots normally!
I rooted with z4root 1.2.1
I have superuser permission so am rooted!
Unrooted then rooted again figuring this might help!
Tried a few different clockwork recoveries
have no idea what the problem is! if anyone has any clue it would be appreciated!
drumdumb said:
I cant get the recovery image to find update.zip
I have clockwork recovery gtab-cwm-v08 installed and renamed to update.zip in the root of the internal sd but when i boot into recovery it goes to the android screen then shows a triangle with a exclamation point, then reboots normally!
I rooted with z4root 1.2.1
I have superuser permission so am rooted!
Unrooted then rooted again figuring this might help!
Tried a few different clockwork recoveries
have no idea what the problem is! if anyone has any clue it would be appreciated!
Click to expand...
Click to collapse
Had that happen to me. What I did was run the CWM again into the gtab. Next reboot I had CWM insgtalled and working.
Hope that helps
CWM 0.8 is the one that I used and is working for me. I have the gTab w/the "original" partition scheme, and installed it by the original gTab update process.
If you're using newer CWMs I've read posts in the CM6b4 thread that newer CWM version seem to be causing problems for some people.
Also if you have a "newer" "batch" gTab w/a different partition map scheme you might want to check what the latest info is on the IRC channel, #tegratab on freenode IIRC. Might be quickest to ask for help there anyways, as it sounds like this probably isn't your problem.
OK, so I just got my Nexus S4G two days ago, and I'm ready to root. My phone out of the box has 2.3.4 on it.
I follow this tutorial: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ the link to which was provided by a good XDA'er. I get the bootloader unlocked and install CWR (recovery-clockwork-3.0.2.4-crespo.img) and that goes fine.
That's when things stop going fine.
First, I try to create a Nandroid backup, and that process seemingly completes fine until i note that the process says it couldn't mount /data. I don't worry about it.
So, I go to Mounts and Storage to prepare to push SuperUser.zip and I tell CWR to "Mount USB Storage" and I wait as directed, but the USB storage never mounts. I try mounting USB Storage and mounting /sdcard, neither of which work, so I can't push SuperUser.zip.
Figuring I did something wrong, I decide to restore from Nandroid, only to have CWR tell me that the MD5 checksum is incorrect and now I have no clean, base Nandroid to restore to.
Then I do some digging, and discover that there's a new CWR for the NS4G at Koush's site and I download the file (recovery-clockwork-3.1.0.0-crespo4g.img) from there, push it to my phone using fastboot's recovery command and start it up.
It doesn't work.
Clicking any of the options (like mounting partitions, or restarting/powering down the phone) causes the screen to go blank and just display the CWR logo in the middle of the screen. The only solution to get out of those loops is to pull battery and restart.
So, now, I'm wondering what to do.
I go back into fastboot, relock the bootloader and I now wait for a reliable root method to root a 2.3.4 NS4G on a Mac.
My questions are:
Where can I get a stock ROM to completely start over from scratch and even remove the recovery I've installed <-- found a base ROM here: http://forum.xda-developers.com/showthread.php?t=1078213
Is there a fully reliable way to root the NS4G on a Mac, and if so how? (I've looked at this thread: http://forum.xda-developers.com/showthread.php?t=878446 and it looks problematic as well).
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
herbthehammer said:
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
Click to expand...
Click to collapse
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
My first nandroid choked. After root and final recovery install, I cleared all the caches it was *****ing about the first time, went in normally to make sure everything was okay, then went back and nandroid and no errors the second time. I probably will just stay with rooted stock but I would not flash other stuff until the dust settles and many of the bugs are worked out of the roms and kernels before jumping in.
TonyArmstrong said:
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
Click to expand...
Click to collapse
If cwm mount won't work then boot into the phone normally and copy over the file like usual is the only other quick and easy way to do it that I could think of at the moment the snafu happened. Yeah the way I did it might not have been the most efficient way but it got me past the hurdle that cwm made quickly. In the end, the result is the same so no big deal.
I don't know if cwm backs up wimax keys so I did it manually. There's a post on how to do it, I don't know if it's in this section. It might be dev?
After installing cwmod zip, I went to install the busybox zip in cw and accidentally chose to automatically install update.zip. I think that's what messed it all up for me. I can get into CW Mod, but if I try to restart the tablet, it stays stuck on the galaxy tab 10.1 screen that has the unlocked icon at the bottom.
Can someone just point me in the right direction on what I need to do to get this thing up and running again?
I've tried to install the OTA which didn't work. ODIN doesn't work on my tablet for some reason, either. I feel like an idiot.. lol
The fix might be easier than I thought.. I found someone's cw backup over at droidbasement.com.
NM it wont allow me to flash it.
Looks like I jumped the gun on creating this thread. I managed to copy over that CW backup's boot, system, and recovery images using adb push. It let me flash them and booted up.
At least it's always "semi" fun trying to fix your mess ups.
Mods can delete this
I think I soft bricked my a500. I made a backup using thor's recovery 1.6 and when i tried to restore, it complained of md5 error. So what I did was to make a new nandroid.md5 by deleting the old one and doind md5sum. It was able to do the recovery but it will not boot past the acer logo.
I can still see the stuff when I adb in recovery, especially /data/media but not booting past the acer logo. What can I do? Is there a boot log or something I can look at?
************* udpate there seems to be boot log file that I can find. I have installed 3.2 rooted stock via the recovery after wiping everything. It did not work. Changing another sdcard worked. So it seems that it was a bad sdcard that was causing the problem.
If mods see this, might want to delete this thread Cheers
I have read all I can regarding rooting, recovery, roms, and just wanted to do a quick terminology check before diving in.
Root = allow myself and certain apps to access settings/files not normally allowed by the OS?
Rom = akin to a non-stock OS that may have features and software added/removed and/or add functionality?
Recovery = some method to go back to a previous state?
Assuming I understand the above, what I believe I want to do, is Root (so that some apps that require 'root only' can work on my device), I should be able to do this by following one of the many guides in these forums. If I do not wish at this time to experiment with roms, I can stick with what came with the phone? And if, in the event of disaster, rather than restore from a backup or recovery, I should be able to Reset to Factory, re-root? and re-install everything (or possibly partially restore from Titanium backup), I do not need to concern myself with Recovery, correct?
Do I seem to have a good enough understanding or should I read some more? Does it sound like all I need to do is Root, and basically I don't need any Roms or Recovery?
Thanks in advance.
Klotar said:
I have read all I can regarding rooting, recovery, roms, and just wanted to do a quick terminology check before diving in.
Root = allow myself and certain apps to access settings/files not normally allowed by the OS?
Rom = akin to a non-stock OS that may have features and software added/removed and/or add functionality?
Recovery = some method to go back to a previous state?
Assuming I understand the above, what I believe I want to do, is Root (so that some apps that require 'root only' can work on my device), I should be able to do this by following one of the many guides in these forums. If I do not wish at this time to experiment with roms, I can stick with what came with the phone? And if, in the event of disaster, rather than restore from a backup or recovery, I should be able to Reset to Factory, re-root? and re-install everything (or possibly partially restore from Titanium backup), I do not need to concern myself with Recovery, correct?
Do I seem to have a good enough understanding or should I read some more? Does it sound like all I need to do is Root, and basically I don't need any Roms or Recovery?
Thanks in advance.
Click to expand...
Click to collapse
You pretty much got it. Only concern is your statement "I should be able to reset to factory". In case of catastrophic error you can't go into settings and factory reset. This is where the recovery comes in. You can use stock recovery to wipe data/factory reset but if you made changes with root apps, this option won't work. Only a nandroid restore or ROM flash or some third party recovery tool to reflash stock images using fastboot most likely.
You have a recovery partition with a recovery program installed. This can be booted into manually from a powered off state. In recovery you have options to backup, wipe, install .zip and much more. Installing a recovery and making a backup is first thing I do. You can use flashify (app on market) to flash the downloaded recovery .img for your device. Its very easy and you don't lose any data.
Excellent, thank you! I see Flashify is a root app, so basically, I should root, install Flashify, pull the recovery image off and I should more or less be set? That is, at least until I get comfortable with where I've gotten to so far (and done more reading). Thanks again.
Klotar said:
Excellent, thank you! I see Flashify is a root app, so basically, I should root, install Flashify, pull the recovery image off and I should more or less be set? That is, at least until I get comfortable with where I've gotten to so far (and done more reading). Thanks again.
Click to expand...
Click to collapse
That's it. Flashify should also have an option to boot into recovery. Do that (after recovery flash) and make a backup. Then reboot and have fun. That initial backup is important. Its your way back while you get comfy. Move that backup to computer also in case your /sdcard gets wiped.
What do you mean, pull recovery image off? You download the image for your specific device from XDA, then open flashify and follow instructions.
Mandelbrot.Benoit said:
That's it. Flashify should also have an option to boot into recovery. Do that (after recovery flash) and make a backup. Then reboot and have fun. That initial backup is important. Its your way back while you get comfy. Move that backup to computer also in case your /sdcard gets wiped.
What do you mean, pull recovery image off? You download the image for your specific device from XDA, then open flashify and follow instructions.
Click to expand...
Click to collapse
I read too quickly what [kind of app] Flashify was, and where to get the image from. I thought it copied the image off of somewhere on the device to somewhere else, but I see now from your explanation what it is. And to save the image on PC, and to save the first backup off device (also onto PC). Thanks again, will work up the courage to do these in the next few days.
Klotar said:
I read too quickly what [kind of app] Flashify was, and where to get the image from. I thought it copied the image off of somewhere on the device to somewhere else, but I see now from your explanation what it is. And to save the image on PC, and to save the first backup off device (also onto PC). Thanks again, will work up the courage to do these in the next few days.
Click to expand...
Click to collapse
The recovery image isn't too important to save. Once its flashed its kinda hard to loose it, but for sure it can't hurt I guess. Good luck!
Just so you know that after installing custom recovery, you will not be able to update through OTA. If you update it, you'll get in trouble. So if want an official update, go to stock again and update.
marshygeek said:
Just so you know that after installing custom recovery, you will not be able to update through OTA. If you update it, you'll get in trouble. So if want an official update, go to stock again and update.
Click to expand...
Click to collapse
I've waited for stock to push to my Xoom, Galaxy Nexus and Nexus 7 soooo many times but never make it. A rooted flashable zip made from the stock ota always lands and I get all flashy.
But yes as soon as you modify your recovery there is a chance you can soft brick your device if you accept the OTA.