Ok, I know this has been posted before, but I can't find my specific problem and I've tried just about everything here and other web sites with no luck.
facts;
1. cannot load CWM any more (stuck at "booting recovery kernel image")
2. cannot load anything into internal memory. I can see a drive show up on my computer but it tells me to insert a disk.
3. APX usb driver works, ran nvflash (different versions) successfully but tablet does not reboot by it self afterwards. it hangs where it reads "Entering NvFlash recovery mode / Nv3p Server"
4. tried recovery through external sd card with no luck.
PLEASE HELP!!!! REALLY LIKE ANDROID AND DON'T WANT TO TRY IPAD.
Look in my signature. Code red.
thx goodintentions, but i just tried code red, double red, tripple red and detox. Everything seems to execute fine during nvflash. My computer starts running the bat file and my tablet displays "Entering NvFlash recovery mode / Nv3p Server"
computer finishes bat and reads to press enter, i press enter and window closes, but my tablet never leaves the black screen with the same message "Entering NvFlash recovery mode / Nv3p Server".
Even when i do DETOX my screen displays the red "magic value mismatch" message like it says in your steps, then i nvflash again and i'm back to square one. with 3 birds and no CWM. Any other suggestions?
Format MISC partition
unomasaudio said:
thx goodintentions, but i just tried code red, double red, tripple red and detox. Everything seems to execute fine during nvflash. My computer starts running the bat file and my tablet displays "Entering NvFlash recovery mode / Nv3p Server"
computer finishes bat and reads to press enter, i press enter and window closes, but my tablet never leaves the black screen with the same message "Entering NvFlash recovery mode / Nv3p Server".
Even when i do DETOX my screen displays the red "magic value mismatch" message like it says in your steps, then i nvflash again and i'm back to square one. with 3 birds and no CWM. Any other suggestions?
Click to expand...
Click to collapse
According to rajeevvp, sometimes formating the MISC partition can fix the tablet not booting into recovery/CWM. I have had other users try this and it has worked for them. Save the attachment with a .bat extension, drop in your nvflash folder & execute it. Power down the gtab after running it and then try restarting in recovery mode.
View attachment format_partition7.txt
unomasaudio said:
thx goodintentions, but i just tried code red, double red, tripple red and detox. Everything seems to execute fine during nvflash. My computer starts running the bat file and my tablet displays "Entering NvFlash recovery mode / Nv3p Server"
computer finishes bat and reads to press enter, i press enter and window closes, but my tablet never leaves the black screen with the same message "Entering NvFlash recovery mode / Nv3p Server".
Even when i do DETOX my screen displays the red "magic value mismatch" message like it says in your steps, then i nvflash again and i'm back to square one. with 3 birds and no CWM. Any other suggestions?
Click to expand...
Click to collapse
Did you make sure to wipe data right after nvflash? Did you use the right nvflash file (the one with cwm pre-installed)?
aabbondanza said:
According to rajeevvp, sometimes formating the MISC partition can fix the tablet not booting into recovery/CWM.
Click to expand...
Click to collapse
Formatting the "misc" partition is useful only for some specific cases, and this doesn't seem to be one of those. Here, the problem seems to be that he's not able to boot into recovery mode which suggests a CWM problem, possibly due to a bootloader/kernel mismatch.
You should wipe the misc partition if:
1. Every reboot goes into recovery mode.
2. You get a message everytime from the bootloader saying:
Detect a recovery command
Erasing MSC
Click to expand...
Click to collapse
If your stock recovery to CWM recovery process was botched or aborted, then you should wipe the cache partition also.
---------- Post added at 10:46 PM ---------- Previous post was at 10:36 PM ----------
unomasaudio said:
1. cannot load CWM any more (stuck at "booting recovery kernel image")
Click to expand...
Click to collapse
Did you use the correct version of CWM for your bootloader? Try loading the latest CWM-4.0.1.5. Use the nvflash command as indicated in the thread with a "--go" tacked on at the end.
2. cannot load anything into internal memory. I can see a drive show up on my computer but it tells me to insert a disk.
Click to expand...
Click to collapse
Did you go to "mounts and storage", then select "mount USB storage"? If you did, and the drive still appears unformatted, then you'll have to repartition the internal SD card. (There are other ways of fixing this problem without losing (too much) data, but it's fairly advanced involving some command line work in CWM.)
3. APX usb driver works, ran nvflash (different versions) successfully but tablet does not reboot by it self afterwards. it hangs where it reads "Entering NvFlash recovery mode / Nv3p Server"
Click to expand...
Click to collapse
For nvflash to reboot the gtablet, the command line you use has to have a "--go" at the end. If you don't, then the bootloader will wait for additional commands. This is the normal behaviour. Did your command (actually, the final one if there were a sequence of nvflash command lines) have a "--go" at the end?
thanks everybody for your input.
rajeevvp , i downloaded CWM-4.0.1.5 but don't quite understand the instructions for execution. (sorry still a newbee).
also, if "mounts and storage" is in a menu of the actual tablet then i can't access it.
NOW THE NEW. in desperation I took it appart and unplugged the battery and tried discharging the caps. still nothing. THEN in even further desperation i shorted a couple of the battery wires wile tablet was ON trying to load the kernel and my tablet went into CWM... this was reproduceable and it loaded CWM every time BUT even thou i could get into CWM I could not actually execute anything from it because it would not detect me touching the HOME button to execute. sooo still stuck.
unomasaudio said:
rajeevvp , i downloaded CWM-4.0.1.5 but don't quite understand the instructions for execution. (sorry still a newbee).
Click to expand...
Click to collapse
This makes me wonder now if you followed goodintentions's code red/.../detox steps correctly: If you've correctly completed any of the code ... procedures listed on the viewsonic g-tablet for dummies site before, then you should not have any trouble with the nvflash instructions for installing CWM-4.0.1.5. Put the tablet into APX mode (Power and Vol [-] key) and then just run the command as listed on your desktop PC.
also, if "mounts and storage" is in a menu of the actual tablet then i can't access it.
Click to expand...
Click to collapse
It is a CWM (Power and Vol [+] key) menu item.
NOW THE NEW. in desperation I took it appart and unplugged the battery and tried discharging the caps. still nothing. THEN in even further desperation i shorted a couple of the battery wires wile tablet was ON trying to load the kernel and my tablet went into CWM... this was reproduceable and it loaded CWM every time BUT even thou i could get into CWM I could not actually execute anything from it because it would not detect me touching the HOME button to execute. sooo still stuck.
Click to expand...
Click to collapse
From the frying pan into the fire now, I would say.
What was previously a fixable problem may now have become unfixable. The first order of business is to get the soft-keys working again. Check for loose and unattached cables. When the keys start working again, try installing just CWM after putting the gTab into APX mode. If you have a 1.1 bootloader:
Code:
C:\> [B].\nvflash --bl bootloader.bin --download 9 recovery-clockwork-4.0.1.5-smb_a1002_bl1.1.img --go[/B]
Get the bootloader.bin file from one of the zip files on goodintentions's web site. You can use any version of the bootloader.bin file as long as it is for the gTablet, but, for the "--go" parameter to reboot the tablet, the bootloader and the kernel installed should match (ie. 1.1 bootloader should have a 1.1 kernel). The bootloader.bin is just executed and not written permanently anywhere.
If CWM doesn't stick, then see this post.
thanks, i"ll be dedicating a couple of hours to this, wish me luck.
Related
Hey guys. I've had my G Tab for about 2 weeks with TNT Lite 4.4 installed, and it has been running beautifully. The day before yesterday, I quickly tapped the power button to turn the screen off, and it shut the whole thing down (without going through the normal shutdown process where it asks you to confirm, etc). Every time I have turned it on since then, once it boots up I get force close message after force close message for several apps, and am unable to do anything.
Some examples of the apps that are repeatedly force closing are:
Google Services Framework
Launcher Pro
Titanium Backup
Pandora
Tapatalk
Dropbox
Once I manage to get all the force close messages closed for a moment, there is usually enough time for me to hold the power button and bring up the shutdown menu. Then I get a bunch more force closes and I can usually get them to close long enough to power it off eventually, but it is a struggle.
I am able to boot into CWM fine, but whenever I select any of the options on the top level menu in CWM, it switches to a black screen and I am unable to do anything until I hold the power button and turn it off.
Any ideas? Thanks!
Bumping this thread to see if anybody has any ideas. I tried NVFlashing the tablet, but that didn't fix the problem. I think it might be connected to this thread:
http://forum.xda-developers.com/showthread.php?t=962545&highlight=process+android.acore
But now when I try to turn the tablet back on, nothing happens. I am at a total loss.
You probably only needed a data wipe. But since we're beyond that now...
You say it does nothing. How much nothing does it do? Backlight come on? Splash screen? gTablet Screen? Fade to black? Have you tried pluggin it back into your computer to see if it's booting into APX Mode (likely)?
Most likely the nvflash failed in some way. Make sure you have bekit's 1105 image, the correct version of nvflash and the appropriate drivers for your version of windows (if that's what you are using). Then try again. If it doesn't work. Let us know.
Yes, it looks like my tablet is now stuck in an APX loop as described here:
http://forum.xda-developers.com/showthread.php?t=1038689&page=1
Reading through this thread and several others it links to to see if I can find a solution.
Follow these instructions exactly.
http://forum.xda-developers.com/showthread.php?t=861950
Use bekit's 1105 image (nvflash_gtablet_2010110500.zip)
Following those instructions exactly is what got me into this situation in the first place
I was just about to send you a PM because in the thread I quoted in my last post, you asked whether anybody experiencing the APX loop problem happened to live near the FL panhandle. I am Tallahassee. If you are still interested in getting your hands on a tablet with this problem, let me know and I am sure we can work something out.
Ok... in the thread you referenced we got one fixed by doing this:
1) Go into APX mode and connect to the computer.
2) enter the following command from the appropriate directory on your computer.
nvflash --bl bootloader.bin --format_partition 12
3) reboot
4) if the tablet does not boot properly repeat the nvflash with bekit's stock 1105 image.
If that doesn't fix it then I really would like to see that tablet. I'll PM you an email contact address.
Thanks! I am kind of new to all this, so... How do I enter that command?
Edit: I tried copying and pasting that line into NotePad and saving it as a .bat file in my NVFlash directory. It opened a command prompt which said something like "NVFlash started" but it closed VERY quickly after that, and didn't appear to do anything else. I tried reflashing stock 1105 after that, and it is still in APX loop.
From command line or copy and paste the following two lines into a text editor and save it as a .bat in your nvflash directory.
"nvflash.exe" —bl bootloader.bin —format_partition 12
@set /p batuserinput=Press enter to continue:
I am basically the world's biggest idiot. I thought I was so careful about following the NVFlash directions exactly, but the whole time I was using the nvflash_gtablet_46_whatevernumbers download instead of the correct one. I downloaded the right one, followed your instructions, and now I can boot correctly! Thanks so so so so so much for your help!
Okay, so I followed the instructions in your other thread to use a micro SD card to wipe my cache and data. I then downloaded the OTA update. However, my original problem of lots of various things force closing still seems to be happening. I rebooted the tablet so I could get an accurate list of which apps/processes were crashing on boot, and I got stuck in a boot loop (birds -> g tab logo -> birds -> g tab logo -> etc).
I NVFlashed it again a couple more times, and it is still stuck in a boot loop.
Figured this was better for a new thread (since a few people in the [Solution] How to recover from a 'bricked' gtab! thread have the same issue, and obviously there isn't a solution yet)
So I screwed up and formatted the SD Card, not realizing that on the G-Tablet the SD Card is actually the internal storage. Needless to say it caused some major issues.
Originally I was stuck in an APX Bootloop. Then I NVflashed, and on initial boot it would show the G-Tab screen, TapNTap screen, then the N screen and then proceed to reboot. It would go through this for 5-10 minutes then just go to a black screen.
With all that said, here are the most recent steps that I've used, and been able to boot up normally ONCE (upon restart it boots into APX):
NVflash 3588 w/ CWM
Boot into CWM (holding the Volume + before beginning NVflash)
Format Boot
Format System
Format Data
Format Cache
Format SD Card
Format SDext
Partion SD Card (2048/0)
Fix Permissions
Wipe Data/Factory Reset
Wipe Cache
Wipe Davlik Cache
Reboot
Reboots into APX
NVflash 3588 w/o CWM
Reboots
G-Tablet Screen, then TapNTap screen, then N screen
Boots up the first time fine (into Android OS), but after a restart it only goes into APX.
Click to expand...
Click to collapse
Is this thing on? Bueller, Bueller?
From reading through some of the other (somewhat unrelated) threads, it seemed like there were a number of people with this same issue. Something is stopping it from re-booting normally. I know there are alot of great minds in the dev section, hoping they can provide some insight on this issue.
Can you get into cwm to repartition the internal SD to 2048 and 0 swap? I think Your SD was formated but not to correct structure for correct boot partitioning.
I ran into a similar issue and from my experience it seems as if each tablet are quite different. If you search through the forums you will see a number of techniques that work for some yet fail for others.
My situation was never fixed and it ended up with me returning my device.
There is some decent information in this thread http://forum.xda-developers.com/showthread.php?t=1038689 however it is spread out through the pages
FIXED IT!!!!!!
Followed the instructions in this post: http://forum.xda-developers.com/showpost.php?p=12220001&postcount=1
Here is what I did step by step
1. Download the 2 attached files below and the top file here: http://forum.xda-developers.com/showpost.php?p=9837354&postcount=3 (rename that file to update.zip)
2. Copy recovery-stock.img into folder that you are running NVflash from.
3. Run NVflash to start the tab, since that is the only way to boot it with the APX issue.
4. Once booted up, Mount it via USB, and copy the attached update.zip into the tablet internal sdcard.
5. Unzip the attached cwmod-internal.zip and copy the recovery folder (including the command file) to the sdcard.
6. Power off the tab.
7. Power on to make sure you enter APX mode (you will see the black screen, but hear a bing sound)
8. Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go (READ BELOW BEFORE YOU HIT ENTER)
9. Press and hold the Volume + on the Gtablet and press enter on the PC to execute the above line. You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashing ! Dont worry.
10. Repeat step 7 and 8, and press enter (do NOT hold volume +!)
11. The tab will start to the TnT like the original one you had, and Magic now: you can turn off and turn on the tab NORMALLY!!
In step 8 I don't know where to type the code in, which Dos command, the dos command window which nvflash step opened( and I didn't press enter to close that window), or I have to open a new one( or make a new .bat file with the code).
I do it and cann't see it install the original rom( "You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashingtes" as you wrote in step 9)
So I still cann't fix my problem.
Please help me!
Thank you so much, you are a life saver.
yesterday, i can not do the step 8 because i can't run cwm to wipe all before, so nothing happen after i press enter.
but now, everything is ok.
Thank again!
naythiten said:
Thank you so much, you are a life saver.
yesterday, i can not do the step 8 because i can't run cwm to wipe all before, so nothing happen after i press enter.
but now, everything is ok.
Thank again!
Click to expand...
Click to collapse
hey can u help me pls,i can,t even get to my internal memory i can,go pass the three bird screen,i don,t know how to do stop four if i can,t see it on my pc
How do you change the zip to an img file? I tried renaming it and it shows as img.zip
Hello all. I'm a brand-noob (my phrase, thank you) here.
I have received a Verizon HTC Eris phone that boots to the red triangle with exclamation point (three droids on skateboards prior to the triangle screen). I have no information on what was done on this phone prior to my receiving it. I have read here that the three droids means that it has been rooted, and that the red triangle means a stock recovery is on it.
I can only "Up Volume + Power" to get this - "E:Can't open /cache/recovery/command". Other than that, I can't seem to get to anything else on the phone.
Now, upon connecting via usb to my computer (Windows 7), I can get Windows to recognize the "Android Phone", but not specifically an HTC Eris. I do not have HTC Sync installed. I have used ADB to root another phone (MyTouch), but this phone does not show up when I check for devices via "adb devices".
I am hoping someone can offer some simple steps that I can do to work towards fixing the phone. Thanks everyone for your time. !
This may help you:
http://forum.xda-developers.com/showthread.php?t=992916
Good luck.
Thanks for the reply phone_cell. I had already read/seen that post.
I cannot see any boot information at all, it shows the skateboarders, then the red triangle. The phone shows up on my computer, but only as an "android storage device". I'm not sure how I can check anything via my computer. I have installed PDAnet prior, and read that it should have installed the phone drivers. ? I installed HTCSync on a different computer and it doesn't see the phone.
If there is no way to fix this phone, then I understand. I would like to think that there are ways (standard methods ?) to check and/or re-install a phone (any phone) back from something like this. ? ...Thanks again for your time and expertise!
I was happy to try to help you. I recommend you send a PM to bftb0. If your Eris can be brought back to life, bftb0 will know what to do.
Bummer. bftb0 does not receive private messages, or at least not from me. Maybe someone could relay the forum post.
I am still digging and digging to try and figure something out. If I could get my computer to communicate properly with the phone, I'm sure I could re-install/fix the boot problem.
Anyone have ideas on how to install a usb device that's stuck in recovery?
As always, thanks thanks thanks. And thanks.
I made a post asking bftb0 to lend you a hand.
http://forum.xda-developers.com/showpost.php?p=15386610&postcount=33
Are you able to get it into fastboot mode? To do so, the phone needs to be completely off first...pulling the battery if needed. From there, first hold down the green send/call button then press and hold the red power/end button at the same time. Holding both should bring you to the fastboot screen which has three small skateboard andy's at the bottom and the word FASTBOOT highlighted in red. If you get there, post what the top two green lines say. Post #4 in the thread phone_cell gave shows an example of what you'll see. I would also try and follow bftb0's directions in post #5 about using the "Official" RUU utility to install usb drivers but make sure to stop before actually flashing anything to the phone. After that, download the fastboot tool and then with the phone connected through usb, see if the command "fastboot devices" lists your device ID.
Getting that far is promising and you can proceed with bftb0's directions in that thread to flash with HBOOT, load a recovery, hopefully eventually get a custom ROM flashed.
Hey MongooseHelix (great nick). Thanks for your reply.
No, the phone does not boot into fastboot, or anything else. There's plenty of resources here for all the different methods for booting and such. I've read hundreds of threads and pages. I've tried them all (and to success on other phones). It only gives me the recovery-stuck-ness.
The more I think about it, the more I think it has something to do with me not having this certain phone installed on my computer prior to receiving it. ? What would other people do to remedy something like that..? Find a working model to get the drivers working? Hmmm. Thanks and thanks again folks.
If you haven't already, how about installing the android-sdk(try the exe if on windows):
http://developer.android.com/sdk/index.html
Then run the SDK Manager.exe from the SDK directory. I'd download the latest SDK tools, SDK platform-tools, and the USB driver for Windows. Make sure to add the tools and platform-tools directories to your path...instructions at the end of Step 5:
http://developer.android.com/sdk/installing.html#sdkContents
With the phone on and connected through usb, see if running "adb devices" from the command prompt recognizes the Eris.
Yes, I had the android-sdk installed prior to receiving this phone. I did run it and update everything within it (per everything I researched online). But, the phone still doesn't show up via "adb devices". I feel like because the phone is stuck in recovery, it's not letting the computer do anything hardware-wise with it. ? Not sure.
Not sure what else to suggest. Without access to recovery, fastboot, or hboot along with not being able to connect through a comp, it unfortunately sounds like it might be hard-bricked. I'm certainly no expert at reviving an Eris so someone may know a way to to fix things...maybe bftb0 will come work his magic. Good luck and if I find or think of anything else I'll let you know.
The red triangle screen is indeed a splash screen for the stock recovery.
The next question is whether you are able to proceed beyond the "splash screen" and attempt to perform a "factory reset" procedure using the stock recovery menus.
There are two ways you get past the stock recovery splash screen, and it depends on which version of the stock recovery is installed on your phone have.
(1) press & hold Vol-Up+End simultaneously (with the "red triangle" splash screen showing)
or
(2) press the Home(soft-key)+End simultaneously (with the "red triangle" splash screen showing)
Do either of those cause the <2e> recovery menu to appear on the screen? If so, perform a "factory reset" using that menu, and THEN see if you can get alternate startup modes to occur (after powering off the phone before each trial):
End (only) => Does anything boot now?
VolDown+End => HBOOT
Send+End => FASTBOOT
VolUp+End => Recovery boot (red triangle screen again) **only works if HBOOT > 1.49.xxxx
Please do not say "I tried everything" in your reply. It is extremely non-specific, and conveys no information about what you actually attempted.
bftb0
Many thanks for the reply. !
With the recovery splash screen showing, upon holding "Volume Up + End (power)" I get = E:Can't open /cache/recovery/command Now, I am able to clear that message by pressing "Volume Up + End" again, however it just goes back to the recovery splash screen.
I held down Home (on the glass) + End (power) and nothing happened.
?? Any suggestions ?
Also... my reference to "tried them all" in my earlier post meant that I have tried just about every combination of simultaneous key pressing upon powering up (booting from no power) the phone. I am also familiar with the recovery menus on other phones - I have not seen it show up on this one (per my most recent post as well).
cjslugbug said:
I get = E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
That message is quite normal. However, what usually happens is that the (stock) recovery <2e> menus appear immediately after that message.
I guess this suggests that there is something wrong with the phone (hardware) or the recovery.
I'll give it some thought (check this thread every so often), but I don't see an immediate way out of your situation.
bftb0
Well, I certainly appreciate the replies. Thanks!
Does
VolDown+Send+End
do anything interesting - either from a phone off condition, or when the "can't open /cache/recovery/command" message is on the screen?
Was there a (properly formatted) SD card in the phone when you performed all the prior button-pressing experiments?
Booted with "Volume Down + Send + End" = same, straight to recovery splash screen.
I then "Volume Up + End" to get "e:can't open /cache...." and tried "Volume Down + Send + End" = no changes.
I have an sd card in it that I used to root a MyTouchSlide recently. It has ClockworkMod recovery on it (update.zip). I have done every procedure I've mentioned in this thread with and without the sd card in the phone.
I just reread the whole thread.
I understand that you tried all the standard button-press-startup methods, and the only thing you can get to work (partially) is the first part of the standard recovery boot. What you didn't say explicitly is, what exactly happens when the standard button-press operations fail:
- nothing at all (screen stays black, not a single LED blips, etc)? or,
- every start sequence results in the recovery splash screen? or,
- the three skating droids appear but the screen freezes that way? or,
- other?
Here is what you are up against:
The standard recovery does not start up an "adbd" daemon, so worrying about drivers is not likely to get you anywhere: under normal circumstances, "adb" simply doesn't work with a standard recovery.
There are two exceptions to this:
(1) The (leaked) HTC "Root ROM" does start an adbd daemon (but "adb shell" won't work)
(2) The Leak-V2 recovery had a race condition that allowed less than 20% of the folks who tried it to get an adbd daemon to persist. (Search for "tereg" root). It's a huge long shot.
Whether either of these apply to you is indeterminate, as we know neither the bootloader version that is on your phone, nor the version ofthe (damaged?) recovery on the phone.
One more question, and then some straws to grasp at:
- when you plug the phone into the charger, do you see the amber/green LED light up?
- repeat every one of the "standard-button-press" sequences, but make sure that before each start sequence, you pull the battery, press all buttons, wait 10 secs, and then reinsert the battery. Long shot, but what have you got to lose?
bftb0
- what exactly happens when the standard button-press operations fail:
The three skating droids appear (for a few seconds, as per a normal-type boot is beginning) but then the screen freezes to the recovery splash screen.
- when you plug the phone into the charger, do you see the amber/green LED light up?
Yes, I see the amber/green light. The light seems to operate as if it is charging normally.
I will try your 10 + second-battery-pull-button-combinations method here in a while.
Really appreciate the thoughts/help on the matter. !!!
I'm not able to get to CWM.
I was switching ROMs and now I seem to be stuck in APX mode.
I'm able to use NVFLASH as outlined here viewsonic-gtablet-for-dummies.webs.com/nvflash, using the 1.2 branch with CWM preinstalled. After the process is finished, I get the stock rom and everything appears to be working but if I power off and try to turn it back on using power and volume + (I'm sure it is '+') I just get a black screen. If I plug the gtablet into my pc I hear the familiar usb connected sound and can run nvflash again, but if I power off it won't reboot.
I searched around this forum for possible solutions, but everything I've tried is not working for me.
Am I missing something?
I've been successfully switching between ROMs in the past.
LouieM said:
I'm not able to get to CWM.
I was switching ROMs and now I seem to be stuck in APX mode.
I'm able to use NVFLASH as outlined here viewsonic-gtablet-for-dummies.webs.com/nvflash, using the 1.2 branch with CWM preinstalled. After the process is finished, I get the stock rom and everything appears to be working but if I power off and try to turn it back on using power and volume + (I'm sure it is '+') I just get a black screen. If I plug the gtablet into my pc I hear the familiar usb connected sound and can run nvflash again, but if I power off it won't reboot.
I searched around this forum for possible solutions, but everything I've tried is not working for me.
Am I missing something?
I've been successfully switching between ROMs in the past.
Click to expand...
Click to collapse
So it's going into APX when you do Power & Vol +. What happens when you do Power & Vol -?
I am seeing the exact same issue after trying to revert to stock mod w/ CWM... any ideas?
---------- Post added at 03:56 PM ---------- Previous post was at 03:40 PM ----------
aabbondanza said:
So it's going into APX when you do Power & Vol +. What happens when you do Power & Vol -?
Click to expand...
Click to collapse
For me, both [power & vol-] and [power & vol+] puts it in APX mode.
DarthSudo said:
I am seeing the exact same issue after trying to revert to stock mod w/ CWM... any ideas?
For me, both [power & vol-] and [power & vol+] puts it in APX mode.
Click to expand...
Click to collapse
Would you like to check out this fix ?
Dave
Thanks Dave, I was able to get further with your link (which is promising), but it didn't quite fix my issue. Everything goes great through 2.7, then on 2.8 when flashing with part6 (the 1st time), it stops at the "Android system recovery <3e>" screen, with the following at the bottom:
E:Can't mount /dev/block/mmcblk2
(No such file or directory)
E:Can't mount SDCARD2:recovery/command
Finding update package...
Opening update package...
Installing update...
Installing Tap 'n Tap build 4349
bootloader_file[0]="/tmp/bootloader.bin", partition_name[0]="EBT"At this point if I reboot, it gets stuck at the screen with the screwdriver and wrench crossed in the middle. The only resolution is to hold the power button... then back to APX mode. *sigh*
From the posts that I could find, the first mounting errors seem benign, but I looked at the recovery.log, and here is what I see at the bottom:
Installing Tap 'n Tap build 4349
wrote recovery partition from /tmp/recovery.img
wrote boot partition from /tmp/boot.img
mtd: not erasing bad block at 0x0b940000
mtd: not erasing bad block at 0x0b980000
mtd: not erasing bad block at 0x0d620000
mtd: not erasing bad block at 0x0d880000
Start mtd_fs_write_partition --------
mtddevname = /dev/mtd/mtd3 ----------
mtd_fs_write_partition : Return happy ----------
mount: no mtd partition named "data"minzip: Extracted file "/data/app/AngryBirds.apk"
minzip: Extracted file "/data/data/com.rovio.angrybirds/lib/libangrybirds.so"
script result was [0.100000]
bootloader_file[0]="/tmp/bootloader.bin", partition_name[0]="EBT"
It would appear that I have some bad blocks
I'm not quite sure what to make of the message about no /data partition (while trying to install angry birds, of all things)
Any suggestions for the next course of action?
Any thoughts on where I go from here? I'm thinking it might be time to flash with the stock ROM, no CWM, and send it back to Viewsonic. From the log, it looks like I've got some bad memory blocks.
Any other ideas before I ship it back and hope they fix it under warranty?
Yes, I know this is a common issue. But My Gtab is really stuck. I tried days of following the stock Bekit install. Everything installs just fine and after the nvflash it goes right into the opening screen and starts up normally. Never see birds.
The issue is if I power off, it cannot reboot, always goes to APX mode. I tried several times.
If I run a command such as nvflash --bl bootloader.bin --sync --go I can get back into the startup screen and the tablet runs normally.
There must be a file missing that is part of the normal booting sequence. Is there something missing that the stock install doesn't do?
Yes I have installed CWM and repartitioned and cleared the data. Many times.
Can run the tablet fine if I start it from APX mode, just can't start it from the power button.
I also tried to update to 3588 with same results. Nothing allows a boot from the power button.
I also tried all the files on the "dummies" site. 1.1 and 1.2 install and run just fine, It's just if I power down the tablet. I only get APX mode when powering up.
I also let the tablet update over the internet to version 1.2.5699. It downloaded, then did a restart and went into APX mode. When I forced a boot in APX mode it came up with an android and a red triangle. Another APX boot got me back into version 1.2.4349
Even if I do a reboot from CWM it shuts off tablet and then the power button goes into APX mode
Any help is greatly appreiated.
Try this. My old Gtablet got stuck in APX mode....was like that for about 8 or 9 months until I followed the link in this thread here...
http://forum.xda-developers.com/showpost.php?p=19175683&postcount=106
Possible vol rocker internally stuck
dcol said:
Yes, I know this is a common issue. But My Gtab is really stuck. I tried days of following the stock Bekit install. Everything installs just fine and after the nvflash it goes right into the opening screen and starts up normally. Never see birds.
The issue is if I power off, it cannot reboot, always goes to APX mode. I tried several times.
If I run a command such as nvflash --bl bootloader.bin --sync --go I can get back into the startup screen and the tablet runs normally.
There must be a file missing that is part of the normal booting sequence. Is there something missing that the stock install doesn't do?
Yes I have installed CWM and repartitioned and cleared the data. Many times.
Can run the tablet fine if I start it from APX mode, just can't start it from the power button.
I also tried to update to 3588 with same results. Nothing allows a boot from the power button.
I also tried all the files on the "dummies" site. 1.1 and 1.2 install and run just fine, It's just if I power down the tablet. I only get APX mode when powering up.
I also let the tablet update over the internet to version 1.2.5699. It downloaded, then did a restart and went into APX mode. When I forced a boot in APX mode it came up with an android and a red triangle. Another APX boot got me back into version 1.2.4349
Any help is greatly appreiated.
Click to expand...
Click to collapse
Could be the contact portion of the volume rocker is stuck (I've heard of one user with this issue). Remove the back cover & disconnect the volume switch connector at the motherboard (see attachment) and then try booting.
Al
Tried tcrews suggestion. Same result. APX only on power on. Only thing different was the partitioining 3 times. Didn't work.
Volume button works perfectly. When I am in the tablet, it adjusts volume up and down correctly.
Give K J Rad's technique a whirl.
Tried that one already. Think I am going to just toss it and give up on this and just assume there is some sort of hardware problem with this Gtablet.
I must have reflashed it at least 25 times and spent days on it. I give up. Shame it works fine if you boot it from the APX mode, just not from the power button.
dcol said:
Tried tcrews suggestion. Same result. APX only on power on. Only thing different was the partitioining 3 times. Didn't work.
Volume button works perfectly. When I am in the tablet, it adjusts volume up and down correctly.
Click to expand...
Click to collapse
Did you do all the partitionings ?
Like I said, mine was stuck for near 9 months (just kept it charged and running...if it shutdown would APX boot it).
I tried every nvflash fix that was posted but when I followed the one I linked exactly, it worked. Shocked me since I had tried so many other sure fire methods didn't.
dcol said:
Think I am going to just toss it and give up on this and just assume there is some sort of hardware problem with this Gtablet.
Click to expand...
Click to collapse
Before you give up, do this for me.
Get bekit's standard 2010110500 zip file. Edit the batch file (or shell script) in it and remove the ``--go'' parameter if there is one. Flash the images. The tablet should remain in APX mode. Now run this command:
Code:
C:\SOME\PATH> [B].\nvflash -r --read 2 a2.img --read 3 a3.img --read 4 a4.img --read 5 a5.img[/B]
After the command completes power the tablet off and immediately boot it back into APX mode. Run this command:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --read 2 b2.img --read 3 b3.img --read 4 b4.img --read 5 b5.img --go[/B]
Let the tablet boot into the Tap 'N Tap desktop, then power off. Put the tablet into APX mode and run the previous command again (change the file names to cn.img). Now you will have 3 sets of img files. Upload all of them somewhere so I can compare them with each other and with my bekit img files.
If everything checks out ok, I'll give you another nvflash command to run and if that fails, you can give up.
I've tried all techniques posted and I can't boot anymore and don't see birds either.
I can nvflash all day long but once it shuts down, I need to use nvflash to boot it up again.
Go it.
I used nvflash to stock 1.2-4349 as I had been doing according to these instructions:
slatedroid com/topic/22124-how-to-recovery-when-gtab-does-not-turn-on-and-stay-in-apx-mode/
Then, after booting to the main screen, I let it download 1.2-5699 and shutdown.
I'm still in APX mode at this point.
Then, I referred back to those instructions and and held Vol+ along with power but I never let Vol+ go. It brought me to the blue Android recovery. I ran 'update.zip' right from that menu and it brought up something different I had never seen at the bottom in yellow text (unfortunately I was so suprised that when I grabbed the tab, I hit the home button to reboot) but it said something like /tmp/bootloader.bin=[0]....
I pressed power by itself and I finally saw birds. 4 days of this **** I'm leaving it alone for a while. :-D