I have 2 g-Tablets and want to flash both of them. Can I use the same MicroSD memory with the files on the second g-Tab to flash it. I am assuming that I can, but wanted to verify it. Also I've seen to process for flashing TnT Lite, but want to VEGAn-TAB. Do I understand correctly the process is the same as for TnT Lite with the exception of the image? I have searched, but cannot find an answer, look at the steps for Flashing TnT Lite, I don't see anything about rooting first. Is this accomplished through CM8? Thanks
You flash the same way with both roms. Either rom will give you root and you don't need root to flash cwm.
Related
I started discouraging its use on TNT Lite after the TNT Lite 5 fiasco, but I didn't realize that my opinions carried so much weight. So I want to set the record clear for everyone.
First off, if the developer / modder requires clockworkmod for their ROM, then that's the tool you need to use. I've had more than a few PM's on this question, but the answer is simple. Use what the developer asks you to use -- but also understand the risks. I would guess that most of the devs here mod with clockworkmod in mind.
For my own two active mods (TNT Lite 4 and gADAM) -- for the gADAM, it requires clockworkmod to install, right now. The reason why is because you HAVE to do a data wipe post-install, which standard recovery does not have. I have this written clearly in the instructions. As for TNT Lite, I discourage it for flashing, but I have instructions for clockworkmod users regardless. gADAM 1.3.0+ and TNT Lite 4.3.0+ have something called "Recovery Pack" built into them. This allows the user to toggle between clockworkmod and standard recovery.
Flashing is my concern, btw. For nandroid backups, data wipes and SD repartitions, the cwm tool is an absolute must. And if you are flashing between 1.1-based mods, clockworkmod should still be a low risk. HOWEVER, if Viewsonic releases a 1.2-based mod with a new bootloader, then cwm becomes a much higher risk. My point with discouraging clockworkmod for flashing on TNT Lite is just to get people used to the idea that cwm has caveats that might become a problem, later on.
When that new firmware is released, we will pick it apart and tell everyone the results of what we find. Hopefully my concerns are for nothing and the new firmware will be safe for clockworkmod users.
Also, for reference: I've been throwing around the term "1.1-based ROM" for about 2 weeks, now. Viewsonic's stock firmware has come in three flavors, so far: 1.0.1 and 1.1, which seem to be on the same dev branch and compatible (from a clockworkmod standpoint). Most, if not all, of the mods here are 1.1-based. 1.2 is a new dev branch that was introduced with build 3991, which was never officially released. This build has a bootloader that, if not flashed with standard recovery, will soft-brick your device. This is the dev branch that concerns me and that we should be watching out for, when that new firmware is released. As I mentioned, we will test it when the time comes.
when the time comes...
Somewhat quicker.
Thanks for detailed explanations!
absorbers said:
when the time comes...
Somewhat quicker.
Thanks for detailed explanations!
Click to expand...
Click to collapse
Quicker is not always better, imo. If users here use cwm, they should understand the risks. I would argue that anyone using a mod here should also understand how to install and use nvflash - devices like the Advent VEGA, Notion Ink Adam and even Viewsonic's own Viewpad10s have nvflash-only firmware updates. I personally find it to be a critical tool for anyone modding their device.
Thanks for the explanation. As a n00b (Wooter) to all of this, I have to say that I have used the built in bootloader to flash both Vegan 5.1.1 and TNT Lite 4.4 without any issues. I did not install CWM based on your previous warnings about it and so far I haven't had any issues. I needed to do a factory data reset after changing ROMs to fix some FC issues, but so far I haven't seen a need to repartition the SD card or any other features that CWM has.
severusx said:
Thanks for the explanation. As a n00b (Wooter) to all of this, I have to say that I have used the built in bootloader to flash both Vegan 5.1.1 and TNT Lite 4.4 without any issues. I did not install CWM based on your previous warnings about it and so far I haven't had any issues. I needed to do a factory data reset after changing ROMs to fix some FC issues, but so far I haven't seen a need to repartition the SD card or any other features that CWM has.
Click to expand...
Click to collapse
And you have cwm ready for use, with TNT Lite 4.4.0 - it's in the Recovery Pack. So, if you find the need to do an SD repartition later, it's there for you to use. I find it to be a good balance and I toggle back and forth a lot. Actually, for day-to-day I leave it on clockworkmod and then flip it to standard if I plan to flash.
There have been some discussions in the partition thread regarding the 'fix permissions' portion of CWM making the repartition suggestion obsolete. I don't have access to standard recovery to check if that option is in there too but the permissions thing may also be a feature of CWM that will be difficult to let go.
roebeet said:
And you have cwm ready for use, with TNT Lite 4.4.0 - it's in the Recovery Pack. So, if you find the need to do an SD repartition later, it's there for you to use. I find it to be a good balance and I toggle back and forth a lot. Actually, for day-to-day I leave it on clockworkmod and then flip it to standard if I plan to flash.
Click to expand...
Click to collapse
First, thanks for your work here. You guys rock! I am using TnT Lite 4.4, where do I locate the recovery toggle? Is it an app?
I wanna say Thanks for the 'Recovery Pack', I actually didn't find it until after I had
gone over the scripts in TnT Lite 4.4 and copied all the files to SDCard.
I then flashed back to Stock 3855 and gave Terminal Emulator SU, mounted system rw and copied them back in.
I ran the 'cwmrecovery.sh' and booted into ClockWorkMod and successfully did a backup (and later a restore).
I ran the 'fixrecovery.sh' and booted into Standard recovery and got the downloading animation and it proceeded to a normal startup (no exclamation!).
Is this normal?
I think there was an update.zip @ root but no command file.
Thanks again for all your work, looking forward to more modding.
Peace!
brown14you said:
First, thanks for your work here. You guys rock! I am using TnT Lite 4.4, where do I locate the recovery toggle? Is it an app?
Click to expand...
Click to collapse
It's a set of scripts - just read my first post, and the Recovery Pack reference link, at the bottom.
jazzruby said:
I wanna say Thanks for the 'Recovery Pack', I actually didn't find it until after I had
gone over the scripts in TnT Lite 4.4 and copied all the files to SDCard.
I then flashed back to Stock 3855 and gave Terminal Emulator SU, mounted system rw and copied them back in.
I ran the 'cwmrecovery.sh' and booted into ClockWorkMod and successfully did a backup (and later a restore).
I ran the 'fixrecovery.sh' and booted into Standard recovery and got the downloading animation and it proceeded to a normal startup (no exclamation!).
Is this normal?
I think there was an update.zip @ root but no command file.
Thanks again for all your work, looking forward to more modding.
Peace!
Click to expand...
Click to collapse
If memory serves, you should get the "!" and then a reboot. But it might not do anything if there's no command file (just hang there for a moment, and then reboot).
Thanks. Got it!
Thanks, I just booted again to recovery, no command or update.zip and same thing.
jazzruby said:
Thanks, I just booted again to recovery, no command or update.zip and same thing.
Click to expand...
Click to collapse
To verify 100% that it's working, you might want to run an update.zip. ie. use the Recovery Pack standalone, it will just overwrite what's already there. Always good to know before you actually need it.
I'm not so sure I'd feel 100% just flashing the 'Recovery Pack'.
I was getting ready to flash Pershoot's Kernel so I think first I'll flash 3588 with stock recovery and be sure all's good.
Then I'll flash the RP and boot into ClockWorkMod and Restore 4.4 from backup.
Thanks for the Heads Up!
jazzruby said:
I'm not so sure I'd feel 100% just flashing the 'Recovery Pack'.
I was getting ready to flash Pershoot's Kernel so I think first I'll flash 3588 with stock recovery and be sure all's good.
Then I'll flash the RP and boot into ClockWorkMod and Restore 4.4 from backup.
Thanks for the Heads Up!
Click to expand...
Click to collapse
Pershoot's kernel may not work with standard recovery, just a heads up. But you can certainly give it a go.....
Pershoot's kernel is nested in a subfolder and I need/want to wipe first.
I just flashed 3588 with Stock recovery and all's good.
I got root and flashed 'RP' and CWM restored my backup.
I ran TE 'fixrecovery.sh', rebooted into Stock recovery and I don't see the (!).
Aside from the downloading animation it seems like a normal boot.
This was with no update.zip @ root or command file in recovery subfolder.
So I guess it's safe to say that no (!) is nothing to worry about.
Just to be sure I dropped an update.zip @ root and same results.
I did the OTA update today, and attempted an install of CWM. I'm not sure if it went all the way through.
The tablet was still working fine.
When attempting to load an update of 4349 with market, the gtab gets stuck at "booting recovery kernal image".
Now the g-tab will not load at all. I attempted the NV Flash procedure but it failed at the final step during the batch where it could not find the file.
Any tips on what I should do next?
which method? Linux, windows?
windows version.
if you can, give us a list of files in your nvflash directory.
thank you, you got me in the right direction. i did not extract the gtablet file.
yea, with all these tools available, it's really hard (is it possible?) to brick g-tab . ..
210danielz,
Unless I misunderstood your first post, it sounds like you have a CWM problem.
Running CWM with 4349 will cause semi-bricks -- and several of us have tried
to post warnings to that effect all over the forum.
IMO, you probably should NVFlash back to stock and let the OTA update take
you back to 3588. Then you will be stock with a solid rom and can do what you
want.
http://forum.xda-developers.com/showthread.php?t=861950
Good Luck,
Rev
210danielz said:
I did the OTA update today, and attempted an install of CWM. I'm not sure if it went all the way through.
The tablet was still working fine.
When attempting to load an update of 4349 with market, the gtab gets stuck at "booting recovery kernal image".
Now the g-tab will not load at all. I attempted the NV Flash procedure but it failed at the final step during the batch where it could not find the file.
Any tips on what I should do next?
Click to expand...
Click to collapse
Here is more info on 4349.
http://forum.xda-developers.com/showthread.php?t=1035983
Roebeet ran a lot of tests and found that 4349 is not compatible with CWM.
210danielz,
When someone gets a bad NVFlash like that I always tell them to:
Take the procedure and go through and check everything. Make sure right
.zip files used. Check every little detail.
Re-run the NVFlash.
If previous step fails again, try nvflashing CWM only:
http://forum.xda-developers.com/showthread.php?t=1030042
If you get a good flash on CWM and get it up, the go to the
Advanced Menu and Partition (2048/0), Fix Permissions, Wipe
Dalvic Cache. Then Return to Main Menu and Wipe Cache
and Wipe/Reset Factory Data.
Having done the above, shut down and go back and NVFlash
to stock again (having cleaned out and repartitioned to
hopefully make it work right this time!)
Hopefully this will give you a working G-Tablet with Bekit 1105
or stock Version 2638 on it. If you set up wifi it will pretty
quickly offer you an OTA to 3588.
From there you can go where you want.
Hope this helps,
Rev
I am to receive my replacement phone tomorrow. I had rooted the one I am sending back so I am a little familiar with that. Have not flashed CWM yet. I see that there is now a Rom manager that will allow the flash. Have read that it is a fakeflash and will only take you to custom recovery thru Rom manager. If device is powered off and you use volue down and power it will reset or wipe data on phone. Those that flashed with nvflash do not have that problem. I have read that those that used nvflash can than flash it thru rom manager and all is good. I am not sure I know what nvflash is(I thnink it is a utility from LG)or where I can obtain it to install it. Any and all help and info is greatly appreciated.!!!!!!!!!!!!!!!!!!!!
There are very good instructions on the nvflash thread in the developer section.
There u will find links to download nvflash for windows or linux, along with all the other files you need, and the command you need to run.
If you're new to all this, I'd recommend you wait it out a bit (there are no custom roms yet anyway, so no immediate need to flash CWM recovery this minute). Things should get easier and clearer soon.
Ok, I understand the flash part using the 1.9 ROM.
But what I am not clear on is how to do the actual flashing. The last thing I did when I flashed my nook was to make an sd card bootable, copied the rom to the sd card and then rebooted the device.
Same thing here?
If you are flashing from the Stock ROM or anyway, from another ROM, I usually suggest to wait for the NVFlash version.
It really makes the flashing process really really easy...like if you're bringing back your device to Factory setup.
If you want to do it other ways...than i can't help you...i just suggest you to wait the NVflash version...
I have the stock 3.2 now.
So I assume that the NVflash version is currently not available?
You can either use the nvflash tool with a nvflash zip and install a custom recovery and rom or run the rooting tool and install cwm when prompted and then flash a custom rom from cwm. This is NOT like the nook.
All the info you need is in the development threads and is usually contained in the 1st couple of posts
acdcking12345 said:
I have the stock 3.2 now.
So I assume that the NVflash version is currently not available?
Click to expand...
Click to collapse
Just check your serial number.
B6Oxxx or less you're good
Some early B7Oxxx is still able to use NVFLash
Later B7Oxxx and newer nothing right now
so i need some help in rooting my tab 7+ p6200
so basically i dont know anything about rooting and all the other stuff about android..
so can someone explain to me some guidelines about rooting
is it safe? if ever i brick my device, will there be a way to unbrick? just some questions about rooting
and please kindly explain these terms that i dont understand
1. flashing
2. CWM
3. Firmware recovery
4. kernel
5. and so many more stuff
so if someone out there who can help me.. it will be a big help..
THANKS!
theejay0625 said:
so i need some help in rooting my tab 7+ p6200
so basically i dont know anything about rooting and all the other stuff about android..
so can someone explain to me some guidelines about rooting
is it safe? if ever i brick my device, will there be a way to unbrick? just some questions about rooting
and please kindly explain these terms that i dont understand
1. flashing
2. CWM
3. Firmware recovery
4. kernel
5. and so many more stuff
so if someone out there who can help me.. it will be a big help..
THANKS!
Click to expand...
Click to collapse
I don;t have a 6200 so i don't know how to root it, it could be the same as the 6210 but I'm not sure. Look in the development section.
I can answer a couple of these other things but you could really get the answers quickly by googling them.
CWM
Clockwork Mod Recovery, a custom recovery as opposed to the stock recovery. You have to have a custom recovery installed in order to flash custom ROMs.
ROM
The operating system (OS)
Kernel
Facilitates communication between the OS and the hardware.
Flashing
A general term for installing a custom ROM, the stock firmware, a mod or an update. There are many ways of flashing and not all devices do it the same way. Samsung uses Odin and also certain files can be flashed in the stock recovery if it is unlocked. With HTC you can flash certain files directly in hboot if the device is unlocked otherwise you need a custom recovery.
Recovery
This is a software layer that you can flash to your phone that allows you to boot the phone into a utility state where you can install roms, flash things like patches or modifications, backup your rom/kernel, etc. When people refer to a nandroid backup, they are referring to a backup made here. It's a snapshot of your phone that lets you mess with things and restore back to that point in time should you screw something up. You pretty much can't brick your phone at this level - it's all just files and filesystems. You can also mount your SD card to reader mode for connection to a computer, do a factory reset of data, and a few other fun things like root your rom here. You should only root your rom if it is a stock rom that has not been rooted yet. Rooting a rooted rom will usually unroot your root so you don't have root. (copied from tspderek in the Rezound forum)
kzoodroid said:
I don;t have a 6200 so i don't know how to root it, it could be the same as the 6210 but I'm not sure. Look in the development section.
I can answer a couple of these other things but you could really get the answers quickly by googling them.
CWM
Clockwork Mod Recovery, a custom recovery as opposed to the stock recovery. You have to have a custom recovery installed in order to flash custom ROMs.
ROM
The operating system (OS)
Kernel
Facilitates communication between the OS and the hardware.
Flashing
A general term for installing a custom ROM, the stock firmware, a mod or an update. There are many ways of flashing and not all devices do it the same way. Samsung uses Odin and also certain files can be flashed in the stock recovery if it is unlocked. With HTC you can flash certain files directly in hboot if the device is unlocked otherwise you need a custom recovery.
Recovery
This is a software layer that you can flash to your phone that allows you to boot the phone into a utility state where you can install roms, flash things like patches or modifications, backup your rom/kernel, etc. When people refer to a nandroid backup, they are referring to a backup made here. It's a snapshot of your phone that lets you mess with things and restore back to that point in time should you screw something up. You pretty much can't brick your phone at this level - it's all just files and filesystems. You can also mount your SD card to reader mode for connection to a computer, do a factory reset of data, and a few other fun things like root your rom here. You should only root your rom if it is a stock rom that has not been rooted yet. Rooting a rooted rom will usually unroot your root so you don't have root. (copied from tspderek in the Rezound forum)
Click to expand...
Click to collapse
Thank you sir for your answers! really cleared a lot..
theejay0625 said:
Thank you sir for your answers! really cleared a lot..
Click to expand...
Click to collapse
I should also add that Rooting (root) is just adding the superuser binaries to the system/bin folder and nothing else. Its pretty much the same thing as an administrator in windows, it allows you access to system folders. Rooting and installing a custom recovery are not the same thing, two different animals, though some devs will included both in their method for rooting a device. I prefer to do mine separately as I don't always want to install a custom recovery.