I hope I have this in the correct area.
I am running a stock unit with Market and Rothnic enhancement pack. I have not gotten an over the air update since just before Christmas. I finally decided to upgrade to the 4349 software that was posted here. I placed my recovery folder with the command line in it and the update.zip file on my sdcard (internal). Booted up with the vol + and power key and it started to upload correctly. When it tried to reboot on it's own, it hung on the "n" screen for over 45 minutes. I manually shut it down. Retried to start it and nothing. Now, if I let it go normally it gets hung up at the "n" screen and does not proceed after this. If I try to force it to go to the recovery mode it just sits there with the little messages saying a recovery key was detected.
What can I do to reload my software? It seems like it can't find the operating system? I do have an external memory card. Can that be used to boot the system from?
Any help would be appreciated. Please keep in mind that I am not Android gifted.
I just found a post from butchconner in another area that may help me. I will try to reboot from them memory card. I will let you know if it worked.
guitar geek said:
I hope I have this in the correct area.
Click to expand...
Click to collapse
You posted this in the wrong section. The Q/A forum section is here:
http://forum.xda-developers.com/forumdisplay.php?f=1101
To answer your question, you need to NVFLASH back to stock. Follow directions found here:
http://forum.xda-developers.com/showthread.php?t=861950
Thank you. I have just tried to reboot from the memory card with out success. I will try the NVFLASH but I am curious how this will work since it will not load from the memory card.
OK I have followed the text. One problem. When I connect the tablet to my PC I hear a ding. I go to my device manager and I see a NVIDA tegra 2 device. I do not have any APX listings and no exclaimantion points. When I run the nvflash program it says USB device not found Press enter to continue. I have attempted to update the drive on the Tegra 2 device but it says the drivers already installed are newer than the one I am trying to load and it stops. So what should I try to do now.
Moved to Q&A.
Eureka Success. The instructions were very clear. Unfortunately, I can't read. I completely skipped over the volume down button. That is why I did not have the APX mode. It is downloading 3588 now. Thanks again dzasta for pointing me in the right direction. And special thanks to roebeet for setting up the cheat sheet.
Glad everything worked out. NVFLASH is a great utility when stuff gets real messed up. Saved me a bunch of times and once you have it all setup, its so easy to use.
Related
Update: Hallelujah, we have seen the birds!
Just for future reference to those of you who may be stuck in an "APX loop", where NVFlashing and even repartioning do not work for you. I tried many things, and only one thing worked.
Didn't work:
1) NVFlashing to anything
2) Repartioning or wiping
3) Wiping out all storage on the SD card
After doing many, many rinse and repeats on the above, the only thing that did work were these instructions:
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Click to expand...
Click to collapse
Now, I don't know of too many cases like mine where APX was the only thing that was working and that no amount of CWM or NVFlashing could bring back whatever was wrong with the bootloader, but this method forced a recovery image restore and got me back to the point where I can now power down and reboot. And for that, I thank this fine community!
I think we need a better guide somewhere on... Stages of recovery. If this doesn't work, here's the next deeper level. (Example: Level 1, wipe data/cache and reflash the rom. Level 2: Repartition and fix permissions. Level 3: NVFlash for 1.1 or 1.2 back to stock. Level 4: run the steps I have listed above. Level 5: fixing the bootloader. Level 6: Remove the case cover and short the back.)
Anyways, thanks again guys. Hopefully someone else will search with the same issue I had and get fixed as I have.
try this (not a developer here) when it boots up use your computer to delete all the files on the sd card so it looks blank- not sure if it will fix your issue but if there is a file on there messing your reboot into cwm that should will get rid of it. let me know how it goes. (standard at your own risk disclaimer) i have done this before just to see what would happen and nvflash brought it back up.
Hey, thanks for the reply. The sdcard was already blanked out through my various steps, so that doesn't appear to be the problem. Same things happen.
Now, that's just the app data and such on the sdcard, so I am guessing if I was able to see/delete all the system files instead via USB and delete it that way, I'd see something else.
just to bee clear i would delete everything on there not just the system files- so when you go to the drive from your computer it shows nothing at all.
here are the steps i would take start to finish.
1 nvflash rom
2 connect to computer, mount usb, then highlight and delete all files on gtab.
3 nv flash again (preferably with a stock rom with cmw pre loaded
4 reboot and pray that this fixed it.
OP - What size is the nvflash file you are using? I have run into a similar issue before with the larger nvflash.exe (like 152kb). It should be 140KB.
Just something else to check.
So to clarify, when you nvflash the 3588 stock image, it will automatically reboot at the end of the nvflash_gtablet.bat batch file?
pugsby said:
Hey all. Little frustrated since I've tried most of the tricks and still have a soft-bricked device. Not sure how it happened originally, but one way or another, I have a bad bootloader and no access to CWM.
APX works. I can NVFlash 1.1 or 1.2-based Stock or otherwise roms, and they boot (once, and only once...) . I can get USB mount. I've tried them with and without CWM pre-installed and see no differences.
But as soon as I reboot or power off, it just returns to APX mode. It is only a black screen, however. No birds, no logo, no nothing. The only way to make it boot again is to NVFlash it again.
All the instructions say to enter CWM to re-partition or to wipe data. That's great, but I have no access to CWM. Pressing the buttons during bootup does nothing because the device never makes it that far through bootup. And the format utility doesn't wipe enough data to return this back to a truly blank device, because when I nvflash, my apps still show to be there and I want it back to a blank slate.
I've tried pressing the buttons directly after a NVFlash to enter CWM that way, but it just goes straight into the rom.
Others have suggested popping off the back of the case and grounding out things to reset that way, but I thought that was just if APX didn't work, but APX is the only thing that DOES work, so not sure if it applies. (Let me know if I'm wrong there)
More things to try?
Click to expand...
Click to collapse
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
After you repartition, wipe data, clear cache, etc. it might still loop into APX. If it does you'll need to force it to install a new bootloader. I'll dig up a link to the procedure if you need it.
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
K J Rad said:
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
Click to expand...
Click to collapse
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Acidburn find out a solution for this problem
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
K J Rad said:
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
Click to expand...
Click to collapse
This got me into CWM (Yay!). This, however, did not fix the APX looping (boo).
I repartitioned, wiped, nvflashed, wiped, repeat. Even though I have more options now with CWM, the end outcome is still the same that after the initial boot, it won't boot again.
BUT, I did find a working method. See the original post.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I was hoping you'd respond, goodintentions, as I used your NVFlash files and instructions this last time around from your very handy site.
I'm not sure exactly what happened. I do know that Rom manager was involved somehow, trying to use that integration with recovery. (I know, not recommended, but at first it acted like it would work).
Also, I think a 1.2 Rom was mistakenly flashed on top of a 1.1 bootloader somehow.
The details are fuzzy. It's been so many things since then that who knows..
goodintentions said:
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Click to expand...
Click to collapse
I am a tech. Been working with/on/in electronics and computers for roughly 35 years. I had a hard time believing the problem was real until I had one in my hands that was doing it. I've tried doing it to my own tablet but a simple nvflash always got me going again.
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
Click to expand...
Click to collapse
This is successful in some cases but not all. In some cases the bootloader has to be updated using factory stock recovery. ClockworkMod and nvflash don't update the bootloader (and I suspect some other system related partitions/information) properly. For those cases the fix is a little more complex. This process...
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
has worked on all but one of the tablets I've recovered. The odd one out required an extra reboot (though I was doing the steps from memory and on an unfamiliar computer so I could be mistaken). However... as noted above... a subsequent nvflash of even the same image resulted in another APX loop. The end result was I had to craft a custom nvflash for each of those machines to avoid the problem in the future. That may or may not be necessary for all cases but since it's relatively easy I just do it out of habit now.
Keep in mind that serious APX looping issues are very rare in the grand scheme of things. Many times folks get confused and fail to follow directions properly and think they have a bigger problem than they really do. The overwhelming majority of times a simple nvflash and repartitioning will fix these things right up.
Added: BTW, the best way I've found to avoid the APX loop issue entirely... do a data wipe before you flash a new ROM and then again immediately after and before you boot it for the first time. I know... one should be enough... but if you make it a habit to do two... then you'll probably remember to do at least one of them ;-)
Great info. I shall try not to enter another painful APX loop. I was shocked how many things I had to try and places I had to go before I found a working method. I guess I really did a number on this thing somehow. But I'm happy that it's back.
I didn't have to do the more painful one you mentioned, but honestly I was ready to try about anything short of slaying a dragon.
I've been trying to install smoke in a bottle, and when trying to revert back to the original ROM on my G tab, I had issues of it not showing up on my computer when connceted. Now, however, I've run NVFlash...And first it got stuck in an endless boot loop, the N symbol would show up then it would turn off, and restart the process.
I then went ahead and did an NVflash format, a-la http://forum.xda-developers.com/showthread.php?t=974422
Then did a standard NVflash.
Now I get a 'magic number mismatch' with some odd garbled symbols with the occasional V, and refuses to boot at all except into APX mode. I can NVflash it into oblivion, but it still gives that error and has absolutely no indication it is on unless I use NVflash when it's in APX.
Furthermore, it seems to have no recovery mode at all, leaving me wondering if I've managed to just permanently brick this thing.
Wonderful.
If I've managed to overlook something simple, I apologize.
My site.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
Start with code red.
You are now my personal e-hero. Thank you so much.
For some reason when I performed the "Code Red" it booted back to normal. Now when I restart it goes straight into APX mode. Any suggestions? Also, when I ran NVFLASH it didn't reformat. It is like I just turned it back on. It runs fine until I try and turn it off. Then it will only start in APX mode.
Don't give up!
Here is a link to the series of steps I used that brought my tablet back to properly functioning state (I too struggled for a while with only being able to boot with nvflash). I saw tonight where the steps worked for someone else as well.
http://forum.xda-developers.com/showpost.php?p=15432280&postcount=19
accidentally posted twice....this one can be deleted.
The problem is I can't boot into recovery. I can only boot in to APX mode. It seems all the fixes are for you to be able to boot into recovery. I have been reading for hours and I am lost.
If you read and follow djab67's procedure carefully you'll see that it will force the tablet to boot into recovery. I use the same technique in my procedure (linked below and has the added benefit of not requiring ADB). I highly recommend you try his procedure as I've looked it over very carefully and it should take care of your problem. If it doesn't please let us know and we'll find you another solution.
My procedure: http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
Been there. Don't fret. I've done so many terrible things to my G Tablet and it hasn't died on me yet. I'm pretty sure with the hardware and this community, this tablet is unbrickable.
If you can get into APX mode and your PC will recognize it when you run the NVFlash script, you are ok. If it doesn't see it when you run the script, there is still hope.
I have tried djab67's fix I don't know how many times now. Every time I click on the .bat file it tells me the file is gone. I have tried downloading it from multiple different posts with the same let down on each of them. Could my problem be that my rom is the current 4349 set up?
cryorayne,
I am going to go out on a limb here because it sounds like you are running windows on your pc (based on you choosing to use the ".bat" file instead of the ".sh" file), so hopefully another current windows user can validate my response.
It may be best to run the bat file from within the windows command window rather than trying to double click launch with in explorer (file manager, not the browser). Once at the command prompt you also need to navigate the old fashioned DOS way to your working folder location.
It is extremely important to set up all the files in a location the bat file expects to find them. Open up the bat file for editing and check any file/folder paths that are defined. You may need to change them to point to your nvflash working area.
Another thing to check is to make sure your user account on windows has administrator permissions (not just "standard user"). A while back, when I used windows more heavily, I seem to recall some cases where I had to give myself "system" level permissions to do some types of things. However, I highly doubt you need that level to run a batch file with nvflash.
Hope this helps. The steps worked for me and I have seen where at least one other person has used them successfully, so they should also work for you. Getting all the tools and files in place and set up for your computer is a key to success.
Finally, if your various downloads came from sources other than those I referenced in the write-up, then I suggest re-downloading and checking the hash sums.
Hope this helps.
Re-posted restore guide with a little additional information
Just wanted to let everyone know that I re-posted the restore steps as a thread (as opposed to a "reply" where it sits today). I was hesitant to do that before I knew the steps had worked for at least one other person. Should be a little easier to find now. Also, I added a little clarifying content to help with understanding APX Mode and nvflash use.
I am hoping the community can help with responding to requests for help. I try to read questions and respond, but don't have the time to be as quick as I would like and I know from experience how frustrating it can be to have "soft bricked" g tab.
As I learn additional information I will add content to the thread from time to time. However, I do not plan on changing the original steps (except maybe for format reasons) since they are the exact ones that worked for me.
Thread Link:
http://forum.xda-developers.com/showthread.php?t=1167944
I installed CM7 Alpha Final (SD card version) and was working on getting the interface back to how I had it on the previous version. I used CWM to install "transparent status bar icons.zip" from this thread...
http://forum.xda-developers.com/showthread.php?t=1471066
Upon installation I went to reboot and now I'm stuck on the CyanogenMod7 boot screen and looping endlessly.
If anyone has any idea how I can fix this, I'd really appreciate some help.
Thanks!
Retcon:
I just remembered that I did NOT have this installed on the previous version on CM7. On CM7 i had a standard theme dock, so I think I installed something that just wasn't compatible with CM7 at all. What do I do now?
Thanks.
Most likely that transparent icons xip was not built for cm7 and rather was built for stock firmware. They are not compatible. Reinstall cm7.
What method can I use to reinstall? Since I'm in a bootloop I can't get to CWM. Or is there some kind of "safe mode" I can boot into?
Sent from my T-Mobile G2 using xda premium
Turn the unit on, when you get to the n screen, hold the power button until it turns off. Repeat 8 times and you will be forced into CWM.
If you have adb installed on your pc, plug it in, turn it on and check devices. If you are listed, do an adb shell reboot recovery and that will put you into recovery instantly.
I tried the 8-boot method two different ways...
1. Pressed the power button and released. When I saw the N screen, I pressed again and held until the unit powered down.
2. Pressed and HELD the button through it powering on and not releasing until it shut back down again.
Does it matter which of the above ways I do it? I wasn't able to get it to work. Does it have to be exactly 8 times? I don't think I stopped short but I might've done it more than 8...
Regarding the ADB method, I went ahead and installed the SDK but I'm not seeing my devices in ADB DEVICES. Since this is a new computer, I think I just don't have the right drivers installed. I went to Indirect's root thread to get those drivers but his dropbox link is disabled due to high traffic. Is there somewhere else I could get the appropriate driver? And once I have the correct driver and can see my device in ADB DEVICES (I'm assuming I'll be able to see it even though I'm bootlooping the whole time?), what is the code/line to get it into recovery?
Thanks for your help thus far. I really appreciate someone taking the time the time to help me out.
Oh, and a correction to my original post - I used the internal root method, not SD.
I found a working link for the drivers.
http://www.mediafire.com/?w6y5ld1jeuh65i1
I installed them and I can access my tablet now. I can see my device and its responding to commands.
So all I need now is the command to get into CWM. I tried "adb reboot [bootloader:recovery]" which I saw in the cmd window, but it just gave me a standard reboot.
Thanks!
EDIT: I tried "adb reboot recovery" and that did it. I'm back in business! Thanks for the help, Know-Fear. Although in my n00bishness, step-by-step handholding would've been nice, your replies gave me enough for me to at least know what general direction to look in. I still couldn't get the 8-boot method to work, but maybe that's just a dexterity issue. The adb method worked perfectly once I stumbled my way to the command line.
Make sure when you reinstall you do a partition wipe.
Glad you got it working thus far. Hopefully no more problems will arise after the new install.
I already tried downloading it from the original post, but it says daily traffic limit reached. Already tried waiting two days, but the error remains. Could someone please upload it somewhere, or provide a working link? Help would be much appreciated, as Adam's method is my last hope.
Thanks in advance!
palbence said:
I already tried downloading it from the original post, but it says daily traffic limit reached. Already tried waiting two days, but the error remains. Could someone please upload it somewhere, or provide a working link? Help would be much appreciated, as Adam's method is my last hope.
Thanks in advance!
Click to expand...
Click to collapse
http://kat.ph/adam-outler-s-ubuntu-t...-t6208816.html
torrent
This is how I downloaded it a few weeks ago.
Good luck!
Thank you for your help, I managed to download and run the ubuntu recovery, but now I ended up being stuck at the "n" read forever screen. I already tried the 8 failed boots method, nothing changed. Any idea what to do now?
ouch.
It ran without a hitch for me (after I got it on card big enough to handle, sheesh). Head back to Adam's thread, I'm sure someone will be able to help you there.
After you put in the card you made, you did see ubuntu running, right?
When booting from Adams recovery sd it will take a long time before you even get to the 100 second countdown timer (about 5 MINUTES). It takes an additional 20 minutes or so to format, write zeros to all the partitions snd rewrite each with data for 1.4.0. THE SCREEN WILL TIME OUT at some point in the process and i found you can just press the N button to turn it back on to monitor progress. When it is finished, the script will tell you to take out the SD and then the tablet will reset and go into a recovery and reset the firmware. I had an issue reregistering when the B and N screen came up so i skipped registration by holding volume up and touching the left and right corners of the screen at the play video screen. A factory button appears and after pressing that, you hold volume up and touch right corner of screen and an option to skip Oobe registration appears. Skip oobe and then you are ready to root. Personally i made a CM7 root card and booted with it. I THEN INSTALLED CWM with Indirects recovery tool apk. Then you can flash Cm9 to the internal and use cyanoboot to chose between the internal cm9 or sd cm7. Good luck!
palbence said:
Thank you for your help, I managed to download and run the ubuntu recovery, but now I ended up being stuck at the "n" read forever screen. I already tried the 8 failed boots method, nothing changed. Any idea what to do now?
Click to expand...
Click to collapse
If you have a brick try my unbricking method http://forum.xda-developers.com/showthread.php?t=1562130
had to go to virtual box
my problem was not the downlaod. i got it from the OP link w/ no prob. but w/ windoze, the microhcsd did not work. aarrgghh. adam kind of responded to that conplaint by saying 'windoze has problems and linux does not'... so i am like a big zero w/ ubuntu but what the hay. i dnlded oracle's virtual box and got it going. then i dnlded ubuntu but did not like its layout and looks so i dnlded mint and that seemed better ( for me ). within mint, i made the sd using a cheapie 16GB from amazon. you do have to have patience and there is very little feedback. well, with the new sd, the un-brick process worked. just pluggin it into the pc and it ( slowly ) gets going. you think its still dead and will not work and then it comes to life and you see ubuntu graphics and its running its script. there is a progress bar of sorts. then you power on and it is at 1.40 and you have to skip over the OOBE ( out of box experience )
.
gotcha for me was that it was NOT powered off when you think it was powered off. the screen has a black / blank mode and then the 'real' black / blank mode. if you hold the tab at a really sharp obtuse angle . . . you can see that it is 'on' when you thought it was 'off'. with no cable attached, press and hold the power button for five seconds to make it off-off...
Hello all. Forgive my newness, but I was an iOS person who just recently started working with an Android tablet.
My Viewsonic gTablet was not running very fast on Android 2.2, so I decided to upgrade it to Honeycomb (or at least to Gingerbread). I downloaded CWM8 for the gTab, and followed all instructions. I powered it on, used my volume keys to select the CWM file, and left it to sit for the appropriate length of time. Unfortunately, the installation failed to go through. Soon after, I started having problems with apps crashing as soon as they were opened, and having to be forced closed. I decided to go back to factory specs, and started that process. When it restarted the tablet, it came up to the three-birds screen, and a message in the top left says Booting recovery kernel image. It then just stays there, and does nothing. It doesn't seem to matter whether I power up with the volume key pressed or not - either way I get the same message. Manipulating the volume keys doesn't seem to do anything. Once I left it like that for ten hours while I was at work, thinking maybe it was just slow, but there was no change.
Following instructions from AndroidZoom, I loaded a recovery file onto an external SD card, to see if would boot from there. No luck. Still stuck on the booting message, with no option to select anything from the external card. Now for the million dollar (or at least $200) question:
Is there a way to access the tablet's internal SD card from my PC even though the tablet won't boot? I figure if I can, I will delete the new recovery file, and load a replacement file from viewsonic which I was lucky enough to find on the web.
ptrask said:
Hello all. Forgive my newness, but I was an iOS person who just recently started working with an Android tablet.
My Viewsonic gTablet was not running very fast on Android 2.2, so I decided to upgrade it to Honeycomb (or at least to Gingerbread). I downloaded CWM8 for the gTab, and followed all instructions. I powered it on, used my volume keys to select the CWM file, and left it to sit for the appropriate length of time. Unfortunately, the installation failed to go through. Soon after, I started having problems with apps crashing as soon as they were opened, and having to be forced closed. I decided to go back to factory specs, and started that process. When it restarted the tablet, it came up to the three-birds screen, and a message in the top left says Booting recovery kernel image. It then just stays there, and does nothing. It doesn't seem to matter whether I power up with the volume key pressed or not - either way I get the same message. Manipulating the volume keys doesn't seem to do anything. Once I left it like that for ten hours while I was at work, thinking maybe it was just slow, but there was no change.
Following instructions from AndroidZoom, I loaded a recovery file onto an external SD card, to see if would boot from there. No luck. Still stuck on the booting message, with no option to select anything from the external card. Now for the million dollar (or at least $200) question:
Is there a way to access the tablet's internal SD card from my PC even though the tablet won't boot? I figure if I can, I will delete the new recovery file, and load a replacement file from viewsonic which I was lucky enough to find on the web.
Click to expand...
Click to collapse
Do a code red, you'll be fine.
http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A