[Q] Confused on CWM vs NVFLash - G Tablet Q&A, Help & Troubleshooting

Starting out here stock 3588. Think i flashed clockworkmod (wasn't 100% certain of success). I see NVFLASH out there too. Wondering the difference between them?
do they co-exist or is it 1 or the other??
sorry im sure the question is stupid but you know the "fool for a minute/fool for life thing" so figured i'd just ask.

Hendge said:
Starting out here stock 3588. Think i flashed clockworkmod (wasn't 100% certain of success). I see NVFLASH out there too. Wondering the difference between them?
do they co-exist or is it 1 or the other??
sorry im sure the question is stupid but you know the "fool for a minute/fool for life thing" so figured i'd just ask.
Click to expand...
Click to collapse
Google gtablet for dummies (not trying to Insult you). They are different, get off of 1.1 bootloader and go to 1.2 bootloader. The latest android update 4.0.x is out there for our tablet.

NVFlash is the PC app that loads the stock ROM and bootloader. You can also use it to load different partitions, like the recovery partition.
ClockWorkMod is a recovery/utility app. It replaces the stock recovery utility on the gTab. From CWM, you can load custom ROMs, make backups, restore backups, clear caches, format partitions, and a few other utilities.

My signature. My website.

Related

[Q] Do everything with stock recovery?

I have been reading all the threads for several days. It may be a dumb question. But I am really curious if we can do everything only with stock 1.1 recovery since CWM .8 does not update bootloader and bring potential danger to soft-brick your gTab when future 3991 based builds include the new bootloader from VS. As far as I have found, flashing a ROM or kernel does not necessarily need CWM to do it. But with CWM we can do data wiping, which stock recovery is not able to. Calkulin posted a Format_All.zip file in his thread. It can do a wipe. I guess it works with CWM just like flashing any ROM or update. But I am not sure if I can use stock recovery to flash it to do a data wipe. Or does anyone know a good way to wipe/format data with only stock recovery?
Of course, one can use stock recovery to flash safely while use CWM to wipe the data. It is just because I am lazy and want to stick with stock recovery.
This came up in the Woot! forums as well, and it's my doing (I'll take the hit for it).
This is my suggestion: Use clockworkmod for all your day-to-day stuff (like backups and restores, SD partitioning and data wipes etc.). However, when you flash a firmware, you should look at that firmware, and the dev's post if that exists, to see if a bootloader update is required. In most cases here, that is NOT the case. However, if Viewsonic sticks to their guns and releases a new firmware with a new required bootloader, then the userbase needs to tread lightly as you might get a soft-brick if you're not careful.
I'm concerned about this because their UAT (build 3991) was like this, AND because the Notion Ink Adam (a sister device) is having these issues at this exact moment - their last update had a bootloader update and clockworkmod users were soft-bricking their devices because of it.
In TNT Lite 4.3.x and gADAM 1.3.x+. I added something called a "Recovery Pack". This allows the user to toggle between standard recovery and clockworkmod, as needed. I also create a standalone package if you wanted to add it to a 1.1-based rooted mod. This way, I (and everyone else) can use clockworkmod for day-to-day, but have the ability to toggle back to standard recovery as needed. I think this is a good balance, but users just need to be aware of the issues and when to use each.
roebeet said:
This came up in the Woot! forums as well, and it's my doing (I'll take the hit for it).
This is my suggestion: Use clockworkmod for all your day-to-day stuff (like backups and restores, SD partitioning and data wipes etc.). However, when you flash a firmware, you should look at that firmware, and the dev's post if that exists, to see if a bootloader update is required. In most cases here, that is NOT the case. However, if Viewsonic sticks to their guns and releases a new firmware with a new required bootloader, then the userbase needs to tread lightly as you might get a soft-brick if you're not careful.
I'm concerned about this because their UAT (build 3991) was like this, AND because the Notion Ink Adam (a sister device) is having these issues at this exact moment - their last update had a bootloader update and clockworkmod users were soft-bricking their devices because of it.
In TNT Lite 4.3.x and gADAM 1.3.x+. I added something called a "Recovery Pack". This allows the user to toggle between standard recovery and clockworkmod, as needed. I also create a standalone package if you wanted to add it to a 1.1-based rooted mod. This way, I (and everyone else) can use clockworkmod for day-to-day, but have the ability to toggle back to standard recovery as needed. I think this is a good balance, but users just need to be aware of the issues and when to use each.
Click to expand...
Click to collapse
Thanks a lot, Roebeet! for everything you have done for this community. I have saved your "recovery pack".
Can Standard Recovery update kernels as well?
vegeetz said:
Can Standard Recovery update kernels as well?
Click to expand...
Click to collapse
I think so,TMK. Just rename the whatever kernal.zip to "update.zip" and add recovery folder with command file in it and flash .....
Seems standard recovery is my best bet if I want to mod a little and keep things as close to original as possible.
Looking to do TNT 4.3.2 with Clemsen v7 tomorrow.
vegeetz said:
Can Standard Recovery update kernels as well?
Click to expand...
Click to collapse
Check with the developer - if they say "clockworkmod only" then you should follow their instructions, imo. My guess is that they only test with cwm, but that's only a guess.
vegeetz said:
Seems standard recovery is my best bet if I want to mod a little and keep things as close to original as possible.
Looking to do TNT 4.3.2 with Clemsen v7 tomorrow.
Click to expand...
Click to collapse
I will probably go with Calkulin's 1.1 and clemsen v6. It looks Calkulin's one is the fastesd so far.
roebeet said:
I also create a standalone package if you wanted to add it to a 1.1-based rooted mod.
Click to expand...
Click to collapse
Roebeet
Did a search and found everything but link to the "standalone Recovery Pack). Please provide again.
Rumbleweed said:
Roebeet
Did a search and found everything but link to the "standalone Recovery Pack). Please provide again.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1005080

[Q] Help me un-bork 1.2 recovery?

My wife installed the update on her stock g-Tablet while it was still available OTA. I tried installing roebeet's Gapps without success, so used Z4root to root her tablet and tried again. Now I can't get into recovery at all! The tablet detects the recovery keypress, but no matter how long I wait, nothing ever happens. I've tried re-installing the update from the downloaded file - no dice, since it never gets beyond notifying me that it detected the keypress. The tablet will boot and things seem to run properly. I've tried un-rooting using Z4root, but this seems to make no difference.
Any ideas what to try before I resort to nvflash?
mstevens,
This is only my philosophy, so you don't have to do it -- can make your own choice.
When I don't know what's going on with my machines, I always go with a fix that will
get me back somewhere where I know what's going on and I know the machine is
working right.
If my tablet were doing what yours is doing, I wouldn't mess with anything else --
I just take about five minutes to NVFlash back to bekit 1105/Version 2638. Then
another 10 minutes to OTA up to 3588. The set things up enough to check and
make sure it's solid and working right.
Then I'm ready to head out where I want to go.
How many times have you read in these posts where someone has a problem and
then tries to flash two or three more roms on top of a questionable situation?
To me having a "known good" is critical for moving on -- and if I don't I don't.
I apologize for the rant. You are handling the situation well so far. NVFlash if
you want to, but make sure it's working right whatever you do so you can
have some fun!!!!
Rev
You could just try to nvflash part9 with the img file from the 1.2 cwr zip file. That would give you a recovery without having to start all over. Especially since the updater isn't allowing you to upgrade past 3588 anymore.
butchconner said:
To me having a "known good" is critical for moving on
Click to expand...
Click to collapse
Agreed. In this case, my wife had already applied the OTA update. Once that had been done, I couldn't see a way to back-up her setup. When she wanted me to try to install the Market, I did that knowing I might have to nvflash.
jasco13 said:
You could just try to nvflash part9 with the img file from the 1.2 cwr zip file. That would give you a recovery without having to start all over. Especially since the updater isn't allowing you to upgrade past 3588 anymore.
Click to expand...
Click to collapse
I'll certainly try that - it makes sense before doing a full nvflash and re-build. My concern is that the problem is with the kernel since I think Z4root caused the problem, so re-flashing just the recovery may not work. I'll give it a try and report back.
jasco13 said:
You could just try to nvflash part9 with the img file from the 1.2 cwr zip file.
Click to expand...
Click to collapse
Is it boot.img or bootloader.bin that gets renamed to part9.img?
If your gonna nvflash part you may as well nvflash all and reset
thebadfrog said:
If your gonna nvflash part you may as well nvflash all and reset
Click to expand...
Click to collapse
Except that I haven't found a way to do backup and restore on 1.2 yet, so she'll lose all of her settings and data.
I may wait until there's an actual problem before doing anything further.
mstevens said:
Is it boot.img or bootloader.bin that gets renamed to part9.img?
Click to expand...
Click to collapse
Neither, it's recovery.img
It shouldn't hurt to nvflash just the recovery partition. You probably won't be any worse off than you are now and you'll still have the option of a total nvflash anyway.
mstevens said:
Is it boot.img or bootloader.bin that gets renamed to part9.img?
Click to expand...
Click to collapse
FYI
http://forum.xda-developers.com/showthread.php?t=1030042&highlight=Nvflash+recovery
Make sure you use the 1.2 version of cwr. I think roebeet posted it.
jasco13,
The NVFLash CWM was my thread and at the time I wrote it there were only 1.1 version
ROMs/upgrades.
I started to put notes in it and update it to say use Roebeets CWM for 1.2
if it still is available anywhere.
BUT -- if you are so borked up you need to get back to stock, I'm not sure
it matters.
I did the CWM via NVFlash with the intention that someone would flash it and
use it to re-partition, etc. Then they would NVFlash the stock bekit 1105 (Version
2638) per the NVFlash Procedure. And then they would OTA to 3588 (which
will overwrite the CWM) and then on to 1.2.4349.
What do you think? Should I leave it alone on that premise?
Maybe I ought to wait a day or two. I read roebeet is working on and nvflash
version of 3588 to go back to as a baseline.
Rev
butchconner said:
jasco13,
The NVFLash CWM was my thread and at the time I wrote it there were only 1.1 version
ROMs/upgrades.
I started to put notes in it and update it to say use Roebeets CWM for 1.2
if it still is available anywhere.
BUT -- if you are so borked up you need to get back to stock, I'm not sure
it matters.
I did the CWM via NVFlash with the intention that someone would flash it and
use it to re-partition, etc. Then they would NVFlash the stock bekit 1105 (Version
2638) per the NVFlash Procedure. And then they would OTA to 3588 (which
will overwrite the CWM) and then on to 1.2.4349.
What do you think? Should I leave it alone on that premise?
Maybe I ought to wait a day or two. I read roebeet is working on and nvflash
version of 3588 to go back to as a baseline.
Rev
Click to expand...
Click to collapse
i haved used it only to flash cwr to do a partition and then fresh nvflash. That being said I think it is a usefull tool to have instructions to flash any form of recovery you want. I accidentally flashed 1.1 cwr over 4349 and had to do a full nvflash when all i really wanted was the stock recovery back. This process borked my touch screen which was a bit of an ordeal to recover from. The calibration in the 1.2 recovery would have fixed it. Being that 4349 seems to be missing from the updater now I'm not sure what the best answer is. Either way the instructions would need to be uber clear because of the dangers.
Matt
edit... maybe having downloadable nvflash packets for "approved/recommended" applications instead of advising people to edit the standard nvflash which could lead to more problems.
Most (if not all) of the factory updates have a recovery image included in the zip. Those can be nvflashed individually back into an otherwise working tablet to recover from this sort of thing. I've got linux versions of the commands I use on my laptop. I'll try to put a little something together tomorrow on it and put it up for perusal.

[Q] Brand new GT, NVFlashed to 1.0-2638, what next?

This has been the most frustrating experience I have ever had with an Android device...
I was one of the lucky few who got one for $280 on Amazon and apparently it had the newest build on it that has the boot loader locked down.
I went through all the stickied guides, warnings about the locked bootloader and NVFlash. Needless to say, I have done my homework.
I tried in vain to install any ROM, but the only one that would install is TnT, which to the dev's credit it was a huge step above the stock ROM, but *shudder* that interface...
Long story, short; I managed to install CWM, fail at any install of a ROM (3 bird screen) and and ended up flashing with NVFlash to 1.0-2638, tried to flash ROM's again and again only to reflash 2638. It has been a LOOOOONG day with this thing.
I am at my wit's end.
Here is what I have 1.0-2638, no CWM and a bottle of Patron Silver...
How do I get a ROM on here...
Hey
Compusearch said:
This has been the most frustrating experience I have ever had with an Android device...
I was one of the lucky few who got one for $280 on Amazon and apparently it had the newest build on it that has the boot loader locked down.
I went through all the stickied guides, warnings about the locked bootloader and NVFlash. Needless to say, I have done my homework.
I tried in vain to install any ROM, but the only one that would install is TnT, which to the dev's credit it was a huge step above the stock ROM, but *shudder* that interface...
Long story, short; I managed to install CWM, fail at any install of a ROM (3 bird screen) and and ended up flashing with NVFlash to 1.0-2638, tried to flash ROM's again and again only to reflash 2638. It has been a LOOOOONG day with this thing.
I am at my wit's end.
Here is what I have 1.0-2638, no CWM and a bottle of Patron Silver...
How do I get a ROM on here...
Click to expand...
Click to collapse
Thats sucks, and i feel for you. I am also someone that just purchased the gtablet from amazon, and have been reading the forums throughly and it clearly says to downgrade before attempting to load cwm and flashing a given rom. So i guess my question is, did you downgrade before flashing?
@Compusearch... welcome to the G-Tablet world...
before you go ahead... look though the forum and FAQ posts...
do you have a particular ROM in mind??
keep these in mind...
if you install the latest 1.2-4329 ROM, you cannot install a custom kernel... so most custom ROMs like CM will not work... there are three 1.2 based custom ROM available (can't post the links so google Century Eyes or Mountain Laurel)
if you install a Gingerbread ROM like CM7, hardware video decoding will not work...
a start up from where you are... get the 1.1-3588 ROM from http://forum.xda-developers.com/showthread.php?t=842000 and flash it with the stock recovery... it's the best base ROM... then you can flash CWM 0.8 bekit if you want to install a 1.1-based ROM (most ROMs available here) or move to 1.2-4329 and install a 1.2 based custom ROM...
you can easily nvFlash back to the 1.1 based ROM even after you move to a 1.2 based ROM...
craigacgomez said:
@Compusearch... welcome to the G-Tablet world...
before you go ahead... look though the forum and FAQ posts...
do you have a particular ROM in mind??
keep these in mind...
if you install the latest 1.2-4329 ROM, you cannot install a custom kernel... so most custom ROMs like CM will not work... there are three 1.2 based custom ROM available (can't post the links so google Century Eyes or Mountain Laurel)
if you install a Gingerbread ROM like CM7, hardware video decoding will not work...
a start up from where you are... get the 1.1-3588 ROM from http://forum.xda-developers.com/showthread.php?t=842000 and flash it with the stock recovery... it's the best base ROM... then you can flash CWM 0.8 bekit if you want to install a 1.1-based ROM (most ROMs available here) or move to 1.2-4329 and install a 1.2 based custom ROM...
you can easily nvFlash back to the 1.1 based ROM even after you move to a 1.2 based ROM...
Click to expand...
Click to collapse
Trust me, I went through all the FAQ's and Guides here. I even found a bunch of youtube video's showing how to do the installs of CWM and ROM's. I can follow along, but the end result is always the 3-bird boot screen.
I am seasoned veteran of installing ROM's: Droid, DroidX, Nook (too easy), Galaxy Tab, Captivate, HD2 (winmo7, android), MyTouch3G, and HTC Inspire. I know the procedures and concepts very well.
I think the variable that is screwing me over, is what was initially installed on my gTablet when I got it this week.
I assumed that I had 4349 as there was no available update when I checked for it over wifi. With that in mind, I did downgrade it to 3588 per:
http://forum.xda-developers.com/showthread.php?t=1036956
Even with that, I could not install any ROM's other than TnT Lite.
I am wondering of the latest batches of gTablets are locked down beyond what the newest update 4349+ already does.
Technically as it stands, I have 1.0-2638 installed and that should have the unlocked bootloader and I should be able to follow this guide:
http://forum.xda-developers.com/showthread.php?t=865245
I would assume that logically, if I have an earlier version of the original TnT, that I can install CWM and then any gTablet ROM.
Am I wrong to assume this?
[edit] I want to be able to use the Vegan Beta 5.1.1 ROM
Stupid question but have you actually tried to install a rom after nflashing. The problem you were having before was the partition structure was wrong and nvflash should have fixed that. You can also extract "recovery.img" from bekit 0.8 zip file......
Copy recovery.img to your nvflash directory
Rename part9.img to part9.bak
Rename recovery.img to part9.img
Run nvflash again
This will flash cwm for you. Then try clearing data and flashing anather rom
Compusearch said:
Trust me, I went through all the FAQ's and Guides here. I even found a bunch of youtube video's showing how to do the installs of CWM and ROM's. I can follow along, but the end result is always the 3-bird boot screen.
I am seasoned veteran of installing ROM's: Droid, DroidX, Nook (too easy), Galaxy Tab, Captivate, HD2 (winmo7, android), MyTouch3G, and HTC Inspire. I know the procedures and concepts very well.
I think the variable that is screwing me over, is what was initially installed on my gTablet when I got it this week.
I assumed that I had 4349 as there was no available update when I checked for it over wifi. With that in mind, I did downgrade it to 3588 per:
http://forum.xda-developers.com/showthread.php?t=1036956
Even with that, I could not install any ROM's other than TnT Lite.
I am wondering of the latest batches of gTablets are locked down beyond what the newest update 4349+ already does.
Technically as it stands, I have 1.0-2638 installed and that should have the unlocked bootloader and I should be able to follow this guide:
http://forum.xda-developers.com/showthread.php?t=865245
I would assume that logically, if I have an earlier version of the original TnT, that I can install CWM and then any gTablet ROM.
Am I wrong to assume this?
[edit] I want to be able to use the Vegan Beta 5.1.1 ROM
Click to expand...
Click to collapse
nvFlashing back to the 1.0 release will definitely downgrade your bootloader... and then I recommend upgrading to the 1.1 branch (3588)... install CWM using the stock recovery or using nvFlash (as @thebadfrog said)...
Format all partitions using CWM... and even try re-partitioning the internal SD card using CWM to 2048MB ext, 0MB swap... and then install a custom ROM
craigacgomez said:
nvFlashing back to the 1.0 release will definitely downgrade your bootloader... and then I recommend upgrading to the 1.1 branch (3588)... install CWM using the stock recovery or using nvFlash (as @thebadfrog said)...
Format all partitions using CWM... and even try re-partitioning the internal SD card using CWM to 2048MB ext, 0MB swap... and then install a custom ROM
Click to expand...
Click to collapse
Trying that now:
1. upgrade to 3588 -Done!
2. install CWM -Done!
3. re-partition SD 2048/0M -Done!
Wipe Dalvik Cache -Done, but with error "Can't Mount /dev/block/mmcblk0p2"
Wipe data/factory reset -Done!
Wipe cache partition -Done!
Format SYSTEM -Done!
Format DATA -Done!
Format CACHE -Done!
Format SDCARD -Done!
4. Custom ROM - VEGAn-TAB GingerEdition STABLE RC1 - INSTALLED!!!
Thanks, Craig and Frog for the tips. This really should be added to the current FAQ.
Sadly, now that I can actually use the tablet, I am HATING the view angles on it.
For a company that prodomiately makes nice monitors and LCD's this is some BS right here.
I know that ViewSonic slapped their name on it, but seriously, who over at VS said that the screen was great and ready for production?
Yeah, the viewing angles aren't great... but it's perfect for a traveller like me... I can sit on the plane and use my tablet without anyone seeing what I'm doing!!
And ignore the dalvik wipe error!!
I wish more people would look at repartitioning as a "step" during the flashing process as apposed to a maybe. All the roms and recovery images are built off of one specific partition set and it is in my book a necessary step to make sure we are all on the same page.
Glad you got it sorted
Mantara said:
I wish more people would look at repartitioning as a "step" during the flashing process as apposed to a maybe. All the roms and recovery images are built off of one specific partition set and it is in my book a necessary step to make sure we are all on the same page.
Glad you got it sorted
Click to expand...
Click to collapse
We have debated that for several months since discovering the different partitioning. The only real way to "brick" for real is through a bad nvflash therefore it makes since to skip that step until necessary.
I think all roms should be nvflashed anyway so you have to understand and be able to use the recovery tools to even modify your tab. But thats my own opinion

[Q] Cannot boot into Recovery

Hey all. I just got a new G Tablet and am trying to install CM7 I was following the instructions to the letter from (Since I an't post links, just google this) Cyanogenmod G Tablet Wiki Full
I got through the 'Installing ClockworkMod Recovery' part and everything appeared to finish successfully.
After rebooting the device, I tried to boot into Recovery to install CM7 and the device just freezes on the ViewSonic splash screen. The screen says 'Recovery key detected Booting recovery kernel image', but it just sits there.
I am able to boot the device into the stock OS, but I can no longer get into recovery.
What can I do?
Tap UI Version: 1,2-4349
Kernel Version: 2,6,32,9-00001-g0e0c333-dirty
Build number: FRF91
Thank you in advanced for your help. Please let me know if there is any other information you need about my device.
Andrew
The key to your post is
Tap UI Version: 1,2-4349
Click to expand...
Click to collapse
You're on the 1.2 bootloader, and CWM .8 will not work on it. There is a versio nthat WILL work, but I, unfortunately don't know the exact link to provide for you. I'll attempt to look it up and get back to you, though.
basically, your G-Tablet, was at some point, updated with the most recent OTA update provided by viewsonic. The update was pulled 24 hours after it was released. You're not lost with 1.2...you have many options. You can either stay on 1.2 and flash any of the many 1.2 roms...some are listed in the development section, others can be found on "another" forum.
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Download
clockworkmod v3.0.2.8 (1.2 branch / NIA rev5) Link: http://www.mediafire...2flqn8b10ebcq44
md5sum: ac4d728d74a6b608cce588d2649e79f3
(updated on 5/15/2011)
clockworkmod v3.0.2.8 (1.2 branch rev2) Link: http://www.mediafire...x61q8jlu2dx8i9u
md5sum: 48c0c40175ab38cebc1199f9d3be8a7d
(updated on 5/05/2011)
THIS REV2 VERSION HAS BEEN TESTED MORE, but nandroid restores are not working properly. Rev5 corrects that, but I need more testers to confirm stability, please!
Many thanks to bekit and rothnic, for their work with clockworkmod!! Their documentation is what assisted me to get this functioning.
NOTE ON CWM: Do not use the Android GUI tool to wipe user data, or else cwm will get stuck in a reboot loop! If this occurs, there are two ways to fix this:
1- ADB required
In clockworkmod, go to mounts and storage and mount /system. Then, run this on your local PC:
adb shell
cd /system/bin
./fixrecovery.sh
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
2- nvflash required
Using the 4349 nvflash image, run this:
nvflash --bl bootloader.bin --download 9 part9.img
Then reboot. What should occur is that standard recovery should pop up and complete the data wipe. On the next reboot, you should be able to get back into the GUI.
Click to expand...
Click to collapse
TJEvans (is it ok if I call you TJ for short?) thank you very much for your help, I appreciate it very much. I'm sorry if confuse some terms here as I try to address your posts inline below, but I would definitely still consider myself a novice at this process of installing custom roms.
TJEvans said:
EDIT:
I also find it interesting, it appears that pershoot's kernel has been installed already? Was this a brand new out of the box G-Tablet, or a used one? I am actually hoping that it's used. If it's NEW, then VS needs to explain how it came with a redacted update AND a custom kernel...
Click to expand...
Click to collapse
This is a brand new G Tablet. I litteraly got in the mail today from Tiger Direct. I'm wondering if the Clockworkmod I tried to install is responsible for the custom kernel.
TJEvans said:
If you need CM7, then I suggest that you follow the "foolproof flash to stock 4349" thread, (http://forum.xda-developers.com/showthread.php?t=1039000) but STOP once you've successfully flashed STOCK 3588.
3588 is on the 1.1 bootloader required for CM7.
Click to expand...
Click to collapse
I don't necessarly need CM7, but that is what I have on my Nook Color, and I really like it.
The main question I have is that right now, I cannot get into clockwork or stock Recovery at all. I do have adb working, so I would think my next steps will require me to use adb.
At the moment since I can't get to recovery I seem to be stuck. Is there a process somewhere I can get recovery working again using adb?
OK...let's try something. It looks like you may actually be in stock recovery, but there's nothing for it to recover.
do you know of a way to get a file and a folder onto your internal SD?
if so, let's edit the instructions to be able to flash to 3588 stock...
What you need:
1. A stock 3588 image renamed to 'update.zip' (http://tapntap.http.internapcdn.net/...-3588-user.zip)
2. 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
Click to expand...
Click to collapse
if yo ucan get those on the SD, then when you reboot, the stock recovery will run and install stock 3588 1.1 based rom and recovery, then you can install your CWM .8.
I have never used NVFlash or ADB, or APX...I have no experience with them. I'm just here helping people that have compatibility issues between 1.1 and 1.2 bootloaders.
After all, the key to fixing problems, is to first find out what the problem is...
I wish I could help more, but I've seen more and more people softbrick their g-tabs by using NVFlash than anything else. I'm not ready to go messing around with my own root files, yet.
If you can get that file, and that folder onto your SD, then stock recovery will automatically recognize it and run it...
I may have just really screwed things up. I ran 'adb reboot recovery' and I gets to the Splash screen with 'Booting recovery kernel image' and gets stuck. Now, I can't get into the device at all.
Also, none of the links in your posts seem to work for me.
try them from the original post, then:
http://forum.xda-developers.com/show....php?t=1039000
sorry, like I said, I'm not a techy...just a guy that doesn't like to see people suffer...
TJEvans said:
THANK ROEBEET FOR THIS:
Since I can't link to another forum, I decided to copy and paste. If people are going ot come ot XDA with issues involving the now taboo 1.2 bootloader, then they'll need to admit that the only way to help them is to link to a forum that everyone is migrating to.
Click to expand...
Click to collapse
It's far from being taboo since it's the honeycomb bootloader... their recovery was blue for a reason...
maybe they pulled those OTA update because they had not licensed honeycomb anyhow, 1.2 is perfectly good to install as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Ok, I was able to get the device working again using NVFlash. (http forum,xda-developers,com/showthread,php?t=861950 replace commas with periods).
Now, I have the following:
Tap UI:1,1-3588
Kernel is still: 2,6,32,9-00001-g0e0c333-dirty
I don't know anything about this kernel, or how I got it, other than maybe it came with my first errant clockwork install.
Can you give me some pointers on how I should proceed? (I would still like to get to CM7 at some point, but I don't know if I should get a different kernel or go back to the stock kernel as well)
GREAT NEWS....glad you god it running so far.
OK, that may be the stock kernel...the numbers looked familiar to me, and I've never seen the stock kernel on that report...so, I may be mistaken.
in any case, you are now back on stock 3588 1.1 bootloader...
Now, you should be able to install the CWM .8 that you tried before, and flash CM7 from there...basically, follow the guide you followed before. but this time, it should work fine, since you are on the right bootloader.
Just remember, research ANY new roms you want to try to make sure what bootloader they are on.
to P00r:
as long as you use a 1.2 compatible kernel you can even use non 1.2 rom!
Click to expand...
Click to collapse
see, I didn't even know that...
The thing I'm seeing, is that Clemysn posted the BOS infromation here, and tried to emphasize that it's a 1.2 Rom...The 1.1 rom's though, do not indicate that they are 1.1 Roms. when 1.1 was all that existed, it made no difference, but now that there is another option, they should at least make sure to add "PLEASE BE SURE YOU ARE USING A 1.1 BASED BOOTLOADER BEFORE FLASHING THIS ROM!!!"
As you can see from Imarikinrat's post, he bought a supposedly factory G-Tablet with 4349 prepackaged on it...now, granted, you and I both know that it's more than likely a refurbished one, as I can't see Viewsonic intentionally releasing product with a bootloader and firmware that was pulled from their updater...
in any case. Roebeet kinda predicted that this would happen a bit. Since most moderators on XDA downplayed the impact of 1.2, it's gone fairly ignored. Think about Imaricanrat's post for a second. Had he not posted his system information there is no way that we would have known that it was a bootloader conflict. It would have been assumed that he was on 1.1 bootlaoder with a "brand new" g-tablet (seriously, man, I'd check that thing with a magnifying glass to make sure that there are no scratches or anything that would indicate that it was anythign other than BRAND NEW)
anyway...had he not posted that he was on 1.2, then who knows what advice he would have been given.
Well, now I'm back to my original problem. I cannot get into Recovery. When I start holding Power and Vol+, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
I have tried putting the recovery folder and update.zip in the internal memory, and on an sd card to no avail. Any other suggestions?
that most certainly sounds like stock recovery to me...
I'm at a loss...it worked fine for me when I flashed to 4349 from stock 3588...just ran and installed, then I ended up on 4349 stock...
you're following the CM7 install guide? Or are you trying to install CWM at this point? I never installed CWM myself, as mine came with it on it.
I'm trying to install clockworkmod so that I can install CM7. Is that the right way to do it? I know there was a stock recovery gui that I cannot get into now.
as long as the recovery folder is on the SDcard, it will automatically attempt to run it...
picture it this way...remember back in the day of windows 3.1 In some cases, if you inserted a floppy disk with a boot file on it, it would check there first, then boot from internal memory...
So, the recovery folder is telling it to run the file in it, which unpacks and installs the update.zip.
once again, though, I never installed CWM myself, but from what you're saying, it should be working.
what happens if you remove the folder and file (after running it), and attempt to go into recovery again?
When I remove the file, folder, and SD card and try to get into recovery, I see 'Recovery key detected Booting recovery kernel image' it then goes to the 'gtablet' splash screen then quickly into a screen with a box with an arrow and a progress bar (the progress bar has the candy cane animation and nothing happens for all of 3 seconds) then the device reboots.
hmm...the box with the arrow and progress bar indicates that it's trying ot run something from recovery...weird..
ANYONE ELSE???
I'm not experienced enough to help...anyone else know enough about flashing CWM from stock, or flashing CM7, that can help out, please chime in.
thanks.
and sorry Imarican...I tried, but once again, no techie here.
No worries man, thanks for your help. Have a good night.
Update: Ok, I think somehow this whole process messed up the 'Recovery Partition' on my G Tablet for whatever reason. When I performed the NVFlash back to stock, it managed to 'fix' the majority of the device, allowing me to boot normally into Tap UI:1,1-3588. However that flash did not fix my Recovery Partition.
With all of that in mind, I found instructions on XDA to install 'clockworkmod via nvflash' (Since I still cannot post links, just google that and it should be the first link, also it's XDA thread 1058649).
After following those steps, I am now able to boot into Recovery which is now Clockwork Mod Recovery, and hopefully *crosses fingers* be able to flash CM7.
Given that I will probably never go back to stock anything on this device, does anyone know where I can download the 'Stock Recovery' for the G Tablet?
so is the point of this article Tiger direct sell used products as new?
so is the point of this article Tiger direct sell used products as new?
Click to expand...
Click to collapse
unconfirmed...what we know is that he had 1.2 4349 out of the box, stock firmware. There are a few possibilities. This could be a Tiger Direct return that was repackaged and sold as new. It could also be a direct from VS return that was repackaged as new, OR, VS actually sent a stock of G-Tablets to Tiger Direct that were packaged with the 4349 firmware on it.
Either way, people need to be careful when flashing roms and such. XDA has not, so far, made it clear which roms, kernels, and CWM versions are good on which bootloader. Some have been asking that devs start exiting posts to indicate which bootloader is needed for each mod, to attempt to avoid confusion.
We must also realize that new G-Tablets are being bought every day, and not every owner is knowledgable of the issues of the recent past, with VS, NVidea, 1.1, 1.2, etc. Most people probably, reasonably, assume that they can open it, root it, and start flashing whatever they want, not even aware that there is a difference.

[Question] Sorry, Complete Eris Noob...

I'm not an android noob...
But just curiously browsing this forum because my sister is getting an Eris as a semi-permanent replacement for her crapberry that she lost.
I can't stand to see her stuck on cupcake...and she's given me the go-ahead to get her up to speed.
I plan on putting CM7 on there for her...
But I have a few questions.
Rooting:
Should I just use this application?
https://market.android.com/details?...1bGwsMSwyLDEsIm5ldC5hbmRpcmMuZXJpc3Jvb3RlciJd
And then to get CWM...
Rom Manager?
I see that CWM is bricking phones...why is that and how common is it?
Are there alternatives I should use instead (RZrecovery or similar?)
And as far as returning to stock...
We use SBF's with Motorola.
What is the alternative here?
Do I have to rely on Nandroids?
Can I restore a stock nandroid from CM7?
Jubakuba said:
I'm not an android noob...
But just curiously browsing this forum because my sister is getting an Eris as a semi-permanent replacement for her crapberry that she lost.
I can't stand to see her stuck on cupcake...and she's given me the go-ahead to get her up to speed.
I plan on putting CM7 on there for her...
But I have a few questions.
Rooting:
Should I just use this application?
https://market.android.com/details?...1bGwsMSwyLDEsIm5ldC5hbmRpcmMuZXJpc3Jvb3RlciJd
Click to expand...
Click to collapse
Yes. Install the app. Run the app. It will tell you to restart the phone - so, that means shut down the phone. Start it back up again. That will have installed Amon_RA recovery, which will allow you to Nandroid backup, install a custom ROM, etc.
(So, after that restart, you can shut the phone down, hold VolUp while powering on to get to Amon_RA recovery. You sound experienced enough to know what to do from there.)
By the way, the Eris by now should have Eclair (2.1), not cupcake (1.5). There should have been three OTAs that brought cupcake up to 2.1.
And then to get CWM...
Rom Manager?
I see that CWM is bricking phones...why is that and how common is it?
Are there alternatives I should use instead (RZrecovery or similar?)
Click to expand...
Click to collapse
As you have seen, many people running Clockwork Recovery as the default recovery have bricked their Erises. ROM Manager comes with almost all of the CM7 ROMs, but you can install it. From within ROM Manager you can have it flash Clockwork, which puts an update.zip file on the SD Card. Go into Amon_RA Recovery, Flash a zip from SD card, choose update.zip, and it will start Clockwork, if you prefer using that. (I actually always do this, as I prefer the Nandroid backup and wipe functions in Clockwork over Amon_RA.) Running Clockwork in this way is safe, as Amon_RA remains as the default recovery.
And as far as returning to stock...
We use SBF's with Motorola.
What is the alternative here?
Do I have to rely on Nandroids?
Can I restore a stock nandroid from CM7?
Click to expand...
Click to collapse
No SBF files for the Eris; however, user bftb0 created a ROM that you can flash that reinstalls stock Recovery and the stock 2.1 ROM. It's called Flashback_21v2, located here: http://forum.xda-developers.com/showthread.php?t=792026
The no radio version should be fine for this purpose.
Perfect.
And I even meant to ask if there was a way to boot into the custom recovery from a power-off state...which you already covered!
That's all I needed.
I appreciate the time you put into answering every question...most people tend to pick one and then the thread dies.
Thanks!
Edit:
Oh, and ya her phone hasn't arrived yet...
The HTC official website said Cupcake...wow that would have been out-of-date!

Categories

Resources