Related
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
i'm stuck in bootloop too.
I'm no expert, but just out of curiosity, have you tried to get back into CW and format your SD to 2048/256? Maybe the partition is hosed?
1st, try to FORMAT with this tools: http://forum.xda-developers.com/showthread.php?t=974422
you can change the image #9 with CW, once format done, when it reboot, you will have a message error in RED just power it off and on again, you will be in recovery mode, now follow the NVFLASH here:
http://forum.xda-developers.com/showthread.php?t=861950
also you can change image#9 to CW this will get you back to the base of stock VS rom
good luck
Wysdym said:
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
Click to expand...
Click to collapse
Can you get back to a state where you can at least get into CWM, even if it is still bootlooping? If so, go into the advanced settings and perform a fix partition (use the settings 2048 / 0). Please note, this will wipe any data you have on your /SDCARD folder (which is the flash card disk installed on your gtab, not the microSD card you may be using)
I agree with butch1326.
You can't move on to other roms until you know the G-Tablet is working right.
I would try to either nvflash or load the regular way CWM and just get CWM working right.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
Once that is done, then I would nvflash the bekit image as is described in a bunch of threads. That will get you all the way back to one of the old, stock setups.
If you get that far successfully, the get on wifi and the OTA should update you to
3588.
Once there, you can take a deep breath, do a bunch of studying on what has been working and what has not, and then move ahead.
Rev
P. S. --- Changing too much too fast is poison in the IT world.
butchconner said:
I agree with butch1326.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
QUOTE]
I was under the impression that 2048/256 was the default for the Gtab and that 2048/0 was used primarily for TnT Lite builds. Was I mistaken on this? I'd hate to be giving out the wrong suggestions.
Click to expand...
Click to collapse
From what I gather android in general is 2048 0. I believe stock gtab may have come with something else but never saw a reason why.
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
butchconner said:
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
Click to expand...
Click to collapse
Damn....I must be getting old. 2048/0 it is. My apologies.
Ronin916,
No need for an apology. It was what it was and someone improved it and it is what it is.
Enjoy.
Rev
SOLVED
For the replies and more, No.. cwm was wiped out and did not exist any longer so that was not an option.
This took a LOT of doing. I'm talking about over 4 hours of nvflash, replacing parts of nvflash with other parts of cwm .8 and more. I was walked step by step through by a few devs. Because they tell me that mine had "other" issues, it would be specific to my machine alone and probably not help anyone else to post all of it. (However, I did find an IRC for the dev chat and that made all of the difference) Thank you to all of you Roebeet, EJ, Bad, and all the rest!
I was told that you haven't bricked it until you pitch it in the water, so keep your heads up.
Thank you to EVERYONE who replied to me.
You are a great community of helpful gents.
i have the same problem as you! I need help=(
Come on man you gotta close a thread like this out! It leaves everyone else stranded by not doing so. Glad you got this fixed though.
I'm STUCK in the same spot.. are you ablet to post your fix? PLLLLEEEAAASEEE
HELP!! HELP!! Stuck in bootloop for days!!
Hello all,
I have been stuck in boot loop for two days now!! I have nvflashed about 50 times (even used the format utility too in the mix) no luck!! I want to flash back to stock, then update to 3588 and use either Illuminate or Roebeets Honeycomb rom.
If some one has had this problem, can you help with some steps to fix??
Please please help!! I am ready to throw the G-tab out the window!!
THANKS!!
Anthony
Have you tried repartitioning?
Try installing clockworkmod and fixing permissions?
Sent from my Droid using XDA Premium App
I would love to be able to re-partition or install CWM, but I can't get by the boot screen.
Is there another method other than NVflash??
Thanks for responding!!
You need to nvflash...
1) Use bekit's 1105 nvflash image
2) replace part9.img with the recovery.img from clockworkmod install zip
3) type in the command to nvflash but hold down the volume up key on the tablet while you press the return key to start it. Continue holding the volume up while the nvflash starts.
4) When the flash ends you should enter CWM recovery mode. Repartition and wipe everything
5) swap part9.img back into the nvflash image and nvflash one more time.
If you are still looping after that you'll need to force the tablet to load a stock update. It will require a little more tinkering with nvflash. Let me know if you need the additional steps.
I tried to install a custom boot animation and wound up having to use CWM recovery to get out of weird looping behavior. I'm not sure exactly what the restore function wipes (for instance, my Vegan ROM was still installed).
Since that episode I've been seeing more Forced Closures than before. I wonder if I need to repartition again. What values should I see if am or am not partitioned 2048/0 and where would I look for those? Thanks.
Surely someone can tell me what to look for as an indicator.
I promise to stop calling you "Shirley."
Rick,
I don't think it's personal -- there just is not a place you can look and see your
partitioning.
If you were boot looping, used CWM to stop it, repartitioned 2048/0 and are running
smoothly now I wouldn't worry about it.
Rev
EDIT: On further thought, I think if I were having glitches (like the FCs), I would
reflash back to stock, install CWM and clean up and reset as needed, and make
darn sure everything was working and exactly right -- and then go my way from
there. But that's just the way I work.
Thanks, Rev.
Thing is, I did not repartition (or, rather, re-repartition) after recovery. Have I necessarily reverted, due to CWM recovery, to the unreliable stock partition (bearing in mind that the device wasn't totally wiped; the Vegan ROM was still in place)?
EDIT: I understand that reflashing to stock and starting over will address any issue. I'm just trying to learn.
Rick,
If you boot into recovery using power/volume + and you get CWM you are still in
ClockWorkMod and have not reverted to stock recovery.
I understand you are trying to learn. I just don't like "flaky" anything so I "make sure"!
Rev
This is my first experience trying to mod a device but everything I read said it was easy so I bought the Gtab and spent 4 hours yesterday trying to flash VEGAn-TAB GingerEdition STABLE RC1 but it won't boot.
The first thing I did was root the device following instructions from driod pirate (before I found XDA). I now know I didn't need to do that step.
After rooting it, I found this post with great step by step instructions for installing clockworkmod and flashing a rom. I followed the instructions to install ClockwordMod and the VEGAn-TAB GingerEdition rom. After trying to boot, it stuck on the ViewSonic splash screen.
I did some more research and thought I might need to downgrade the bootloader/tnt version so I followed these instructions and was able to successfully load the stock rom. I then followed the same steps above to install clockworkmod and flash the vegan rom. Again, when trying to boot, it just sticks on the ViewSonic splash screen.
Any ideas what I might be doing wrong?
Do I need to do a nvflash and try the process from the beginning again?
dw21 said:
This is my first experience trying to mod a device but everything I read said it was easy so I bought the Gtab and spent 4 hours yesterday trying to flash VEGAn-TAB GingerEdition STABLE RC1 but it won't boot.
The first thing I did was root the device following instructions from driod pirate (before I found XDA). I now know I didn't need to do that step.
After rooting it, I found this post with great step by step instructions for installing clockworkmod and flashing a rom. I followed the instructions to install ClockwordMod and the VEGAn-TAB GingerEdition rom. After trying to boot, it stuck on the ViewSonic splash screen.
I did some more research and thought I might need to downgrade the bootloader/tnt version so I followed these instructions and was able to successfully load the stock rom. I then followed the same steps above to install clockworkmod and flash the vegan rom. Again, when trying to boot, it just sticks on the ViewSonic splash screen.
Any ideas what I might be doing wrong?
Do I need to do a nvflash and try the process from the beginning again?
Click to expand...
Click to collapse
You need to follow the nvflash instructions on the developer page. Your partitions need to be fixed before gb roms will work
I suggest the first thing you do is setup nvFlash. I can assure you that you will need to use this utility at some point. It is very usefull and powerfully utility and is very easy to setup and use. http://forum.xda-developers.com/showthread.php?t=861950
once you set that up..i suggest you start from scratch.
So this is what I would do if i was in your shoes.
1. Install nvFlash and go back to stock.
2. Update to 3588 using OTA
3. Install cwm .8 on your tablet
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
6. Mount your tablet using cwm .8 and upload the rom you want to install
7. Install the rom you want and you should be good to go
(dont forget to reboot your device after that first boot.)
What is the risk involved with NVFlash? I've read a few complaints that their devices were bricked after nvflash. How do I make sure I avoid that happening?
dw21 said:
What is the risk involved with NVFlash? I've read a few complaints that their devices were bricked after nvflash. How do I make sure I avoid that happening?
Click to expand...
Click to collapse
Anytime you brick it, you can use nvFlash to un-brick it. Its just a matter of knowing what you are doing and reflashing it with the correct files. From what I have experienced, its pretty much impossible to brick these tablets once you have nvFlash setup. No matter how bad that situation is, I have always been able to recover using nvFlash(and I have been in very terrible situtations where I got a blank screen when i booted...turns out I was stuck in apx mode when i booted)
rbansal2 said:
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
Click to expand...
Click to collapse
Can you go into more details on these two steps? I know it's done with cwm but I want to make sure I do it exactly right.
worked for me
Thanks guys this worked great! For some reason I couldn't upgrade to 3588 it would FC at 50% but it works now!
clayvikings said:
Thanks guys this worked great! For some reason I couldn't upgrade to 3588 it would FC at 50% but it works now!
Click to expand...
Click to collapse
Awesome, that's great news! Welcome to the club!
rbansal2 said:
I suggest the first thing you do is setup nvFlash. I can assure you that you will need to use this utility at some point. It is very usefull and powerfully utility and is very easy to setup and use. http://forum.xda-developers.com/showthread.php?t=861950
once you set that up..i suggest you start from scratch.
So this is what I would do if i was in your shoes.
1. Install nvFlash and go back to stock.
2. Update to 3588 using OTA
3. Install cwm .8 on your tablet
4. Repartition to 2mb/0 using cwm .8
5. Wipe data, clear cache, clear dalvik using cwm .8
6. Mount your tablet using cwm .8 and upload the rom you want to install
7. Install the rom you want and you should be good to go
(dont forget to reboot your device after that first boot.)
Click to expand...
Click to collapse
I did exactly this (minus step 1. as it was already a stock device) and I had exactly the same problem - gtab stuck at viewsonic splash screen. My unit was fresh outta the box and fully charged, and this was the firstht hing I tried to do with it. CWM installed without a hitch (yes, 0.8) and I repartitioned without fear (I had no data on it anyway). Did the wipes, mounted the tab and copied over the rom... all instructions I found on XDA for doing it. It still sticks at the splash screen.
So, to get a working tablet again, I used nvflash to go back to stock (though I have a superuser app now, which is odd for 'stock'), did the ota update to 3588, loaded Spark+ on it for a launcher and add the amazon marketplace app (looking for more free apps).
I still want to get VEGAn installed though, just wish I new why it was freezing up/not booting/not correctly installing or whatever the problem is.
If you have run nvflash you can now install Gingerbread roms as it fixed your partitioning. When you got stuck on the vs birds it meant your partitioning was wrong and you needed to nflash. If you did then your fine now.
The nvflash provided does not bring you to complete stock. If you want complete stock just flash the 3588 update.
I did the exact same thing you did, with the same result. Then I nvflashed and walked through the rest of the steps and I was quickly able to flash VEGAn-TAB.
dw21 said:
I did the exact same thing you did, with the same result. Then I nvflashed and walked through the rest of the steps and I was quickly able to flash VEGAn-TAB.
Click to expand...
Click to collapse
I've been watching the VEGAn-TAB logo flash and pulse at me for the past hour. Think I'm going to try to flash the ROM again...
EDIT:
Scratch that. restarted into cwm, cleared user data again, booted right into V. Going through setup screens now. Question though... If this was writtne for the G-Tab, then why does it still have the phone stuff in it?
was working but now it isn't?
++++i had to use nvflash for my gtab and it worked. I loaded vegan-tab 7.0 GE and it took "literally HOURS" to boot to the tablet setup page, after that it was working great until I rebooted it after 1 day of use and now i can't get past the "powered by g-tabdevs" boot page?????? any thoughts?++++
UPDATE: I repartitioned the sd card 2048/0 and that didn't work, then i cleared the dalvik (?) cache and the other cache and it booted up successfully (warning to newbs like me, this did clear all my data so back up everything)
SIDE NOTE: I love this website!!!
Two things I always do before I decide to try a new ROM, backup anything I don't want to lose, then go do a factory reset. When you install a new ROM, it doesn't automatically wipes all the partitions, especially the user data and settings. By leaving that there, you are allowing the ROM have access to that information which in turn, can cause problems because not every ROM setups the same. I have seen many people run into problems because they don't do a data wipe. If you do this, you will see a lot less problems in the future and if you do get a new install running but seeing FCs with a lot of apps, do a factory reset.
VEGAn-TAB GingerEdition STABLE RC1 Still In Boot Loop
Hi, I've tried doing as per what the instructions said about clearing the cashes and partition SD card sizing. I've load VEGAn-Tab 6 times already and everytime I still end up with a boot loop error. I just decided to use tntlite instead, but I really want to get this working. I noticed one thing as I was loading tntlite and the stock rom that when I go back to ClockworkMod v08 to mount “/system” and “/data”.
I see the following:
“unmount/system”
and,
“unmount/data”
which is right, but when after I load VEGAn-Tab
I see the following:
“mount/system”
and,
“unmount/data”
From what I've been reading this should not be the case. I'm not sure it this is related to my problem with the boot loop or not.
Please help!
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.
I bought a used, already rooted g tab about a month ago. While watching tv (or something) I was reformatting the internal memory in CW recovery and my computer froze completely while reformatting. Anyways, it messed up some of the other partitions I think because it wouldn't boot into 1.1 based flashback, and I couldn't get 1.1 gtabcomb to boot up either.
There are so many dated tutorials around here that I'm not sure which one to follow. How can I repair the partitions and make sure everything is good, while also upgrading my gtab to the 1.2 bootloader so I can install the new flashback. Any help please? Sorry for such a newb questions but I just want up to date info!
parkgrrr said:
I bought a used, already rooted g tab about a month ago. While watching tv (or something) I was reformatting the internal memory in CW recovery and my computer froze completely while reformatting. Anyways, it messed up some of the other partitions I think because it wouldn't boot into 1.1 based flashback, and I couldn't get 1.1 gtabcomb to boot up either.
There are so many dated tutorials around here that I'm not sure which one to follow. How can I repair the partitions and make sure everything is good, while also upgrading my gtab to the 1.2 bootloader so I can install the new flashback. Any help please? Sorry for such a newb questions but I just want up to date info!
Click to expand...
Click to collapse
You must first research on how to do this before hand. I tryed the same thing that you did and almost HARD BRICKING my device. Know your bootload.
http://forum.xda-developers.com/showthread.php?t=1035983
To my understanding is that Flashback is only offered in the 1.2 bootload so NVFlash is your friend in this case.
yep I'm on the 1.1 bootloader. When flashback 8.1 was released, it was actually released with a 1.1 version, but was pulled shortly because of some problems. It worked fine for me so I just lived with it. Alright I'll see if I can get to stock 1.2 and then flash to the new flashback rom.
EDIT: Ok so if I follow the instructions here, and I'm currently on the 1.1 bootloader, can I just use nvflash to flash over the the 1.2 version of tnt?
(it wont let me post the link, but its on the gtab for dummies nvflash instructions)
Yes you should be able to just be able to flash the Stock 1.2 rom. There are nvflash setups with the stock 1.1 and 1.2 roms that come with the CWM recovery kernal already on them. Being a noob they won't let me attach links from the Dev. portion just yet, but that's how I got mine.
I believe it's nvflash for dummies. The Dev. created a link to the site to be able to download both if needed. Make sure that you have ADB setup first before flashing. Read up on all that from the dev forum.
OK so I managed to fix the partitions through CWM, but I can't get NVFLASH to flash it over to the 1.2 BL. I was able to install the 1.1 gtabcomb but I want to switch boot loaders.
When I click on the .bat file it just says "unknown device detected" I installed the proper drivers ect. This is while I have my tab in CWM. Also I don't know if this is important or not, but when I boot up it says NVIDIA TEGRA Development unit, and in the top right corner there is an android peeing on the apple logo. Maybe I have a weird cwm recovery or something? Am I even in APX mode when im in cwm?