Related
So I successfully (I think) took my gtab back to stock rom using NVFlash. Then When i try to install clockwork mod (to eventually move to TNT lite 4.4) I killed it. I copied over the update.zip and recovery folder when attempting to do clockwork. Then I powered down. Now it won't do anything. ie. The screen doesn't even turn on. I tried disconnecting the main battery and letting it sit for up to 20 sec but that doesn't help either. Won't turn on while holding +Vol either (that's how I tried first).
Connect it to your computer via USB and see if it's in APX mode. If it is then you'll likely need to nvflash again. If you do make sure that you are using the right drivers and bekit's 1105 image. Then once you have it up and running you'll likely need to repartition it.
ok. And if that works Can I update the tablet with the new viewsonic release or do I have to keep the old version to run clockwork and then tnt 4.4? I guess 5 has been taken down?
The latest Viewsonic release (build 4349) is NOT compatible with the standard clockworkmod.
TnTLite has been retired and replaced by it's developer with Mountain Laurel which you can find over at SlateDroid. It is based on the latest stock build so you could upgrade to that with no trouble if you choose to.
Alright. Thanks for the help so far. It was indeed still in apx mode. Any Idea's on how to get it out? I can NVFlash it with no problem but every time I reboot (update or just power down) it comes back in APX and I have to re-NVFlash.
You have an APX brick. Unless KJ Rad has come up with a fix yet your stuck right nnow nvflashing everytime you boot
starfltcdrjr said:
Alright. Thanks for the help so far. It was indeed still in apx mode. Any Idea's on how to get it out? I can NVFlash it with no problem but every time I reboot (update or just power down) it comes back in APX and I have to re-NVFlash.
Click to expand...
Click to collapse
1) nvflash - bekit's 1105 image (nvflash _gtablet_2010110500.zip)
2) wipe data/cache
3) Install CWM
4) reboot into CWM
5) repartition 2048 and 0
6) nvflash bekit's 1105 image again
7) wipe data/cache
If you get any error at any step (especially during the nvflash) stop and let me know. If you're not sure how to do any of those steps I'll be happy to point you in the right direction.
I'm hoping to have something better than this in the next few days but for now this is the best we have to get you working at a good factory load.
Ok. What do I do for steps 2-5 thanks for the help.
2) Wipe Data: This can be done either through "Settings - Security - Factory Data Reset" or Method I from http://forum.xda-developers.com/showthread.php?t=1030915
3) Install ClockworkMod (CWM): The first part of this post: http://forum.xda-developers.com/showthread.php?t=865245 (Just do the CWM install)
4) Shutdown the tablet then restart it while holding down the Volume Up key until the words "Recovery Key Detected" appear in the upper left hand corner of the VS Birds Logo screen.
5) Once in CWM, Look for partitioning under Advanced menu. Select it and answer the two questions 2048 and 0. This will take a few minutes.
update: Ok I think its out of its APX loop (somehow) Now in version 1.0-2638.
Another update:
Boy am I a dumbass. When I put the thing back together I put the VOL key in backwards.... DOH! CW mod is working fine.
I'm guessing I need to update stock software to get best results now? Is that possiblcard if I can't get it to boot in anything but APX anyway???
The best I've been able to do is using the NVFlash found here: http://droidpirate.com/2011/03/10/g-tab-users/
I can see the viewsonic splash for a split second at startup when holding the Vol+ and power then back to APX
I was hoping the data wipe would clear the loop. What ROM did you have on the device before all this started?
starfltcdrjr said:
The best I've been able to do is using the NVFlash found here: http://droidpirate.com/2011/03/10/g-tab-users/
I can see the viewsonic splash for a split second at startup when holding the Vol+ and power then back to APX
Click to expand...
Click to collapse
Two things... First, I cannot help you effectively if you choose to use resources other than those I recommend. I have no idea what is in that nvflash from droidpirate nor do I have the time to research each and every one so please use the references I provide.
Second, Are you absolutely certain that you're holding down the Volume Up key to go into recovery? You'd be amazed how many folks (myself included) make a mistake here every now and then.
update: Ok I think its out of its APX loop (somehow) Now in version 1.0-2638.
Still can't boot into CW. (VOL+ + Power) DLed version 8 from here: http://forum.xda-developers.com/showthread.php?t=865017
I'm guessing I'm unbricked but just using wrong CWMod version
is this the one I need?
I guess it depends on which ROM I'd like to run correct? If you could reccommend one and help me get there that'd be great.
That one should work fine for the ROM's on here. If you're going to use the VS stock 4349 build or one of Roebeet's ROM's from slatedroid then you'll need to use the one compiled for the 1.2 development branch.
update: Ok I think its out of its APX loop (somehow) Now in version 1.0-2638.
Another update:
Boy am I a dumbass. When I put the thing back together I put the VOL key in backwards.... DOH! CW mod is working fine.
I'm guessing I need to update stock software to get best results now? Is that possible without wifi as I won't have that until the weekend?
I've re-partitioned the SD card.
I'm going to try and get TNT light 4.2.1 from droidpirate to run
looks like TNT Lite 4.2.1 went on OK. Thanks for the help and remember + is on the right
Glad you got it working. Enjoy!
K J Rad said:
2) Wipe Data: This can be done either through "Settings - Security - Factory Data Reset" or Method I from http://forum.xda-developers.com/showthread.php?t=1030915
3) Install ClockworkMod (CWM): The first part of this post: http://forum.xda-developers.com/showthread.php?t=865245 (Just do the CWM install)
4) Shutdown the tablet then restart it while holding down the Volume Up key until the words "Recovery Key Detected" appear in the upper left hand corner of the VS Birds Logo screen.
5) Once in CWM, Look for partitioning under Advanced menu. Select it and answer the two questions 2048 and 0. This will take a few minutes.
Click to expand...
Click to collapse
Hi,
I'm in the APX loop and have been unable to progress through these instructions.
My error was that I successfully flashed CWM v08 and Vegan, then tried to use ROM Manager to switch to Cyanogen. ROM Manager forced me to update the CWM to 2.xx, and then on the reboot it had the 'Magic' error.
I've done NVFlash and can get into TnT but can't get past the APX loop to install the CWM (as per step 3) - my holding down power + vol+ just results in a black screen, then when I check for APX mode, it is still in that mode.
Step 2 (clear cache) forces a reboot - is that right? I've tried the other method of clearing cache ('Method I').
Any ideas? I only got this thing a few hours ago, lol!
simmo35 said:
Any ideas? I only got this thing a few hours ago, lol!
Click to expand...
Click to collapse
Searched APX bootloop and got this:
http://forum.xda-developers.com/showthread.php?t=994046
Worked for me.
simmo35 said:
Hi,
I'm in the APX loop and have been unable to progress through these instructions.
My error was that I successfully flashed CWM v08 and Vegan, then tried to use ROM Manager to switch to Cyanogen. ROM Manager forced me to update the CWM to 2.xx, and then on the reboot it had the 'Magic' error.
I've done NVFlash and can get into TnT but can't get past the APX loop to install the CWM (as per step 3) - my holding down power + vol+ just results in a black screen, then when I check for APX mode, it is still in that mode.
Step 2 (clear cache) forces a reboot - is that right? I've tried the other method of clearing cache ('Method I').
Any ideas? I only got this thing a few hours ago, lol!
Click to expand...
Click to collapse
And stop using ROM Manager
Good Afternoon All,
I'm a complete gtab noob for starters. Anyway, I am attempting to install ClockworkMod v8 following the directions here: http://forum.xda-developers.com/showthread.php?t=865245 but cannot seem to get it to install. I have transferred the files with no problem but after powering off, then "Up Volume/Power On", the screen just remains with the "3 Birds" and -Recovery Key Detected- and -Booting recovery kernel image- messages appearing.
I let it sit for a while the first time, then powered off. I can then power on and get the stock screens with no problem and the tablet seems to work fine. Then I power off and use the "Volume Up/Power On" routine and I just end up getting stuck again.
I have searched around a bit on these terrific forums but just can't seem to find the solution that fits this exact problem.
Any help would be greatly appreciated.
Thanks in advance........
f2s
I see quite a few views but unfortunately no replies. Can I safely just delete the files from the root directory of the gtab and place them on an external sdcard and try again or will deleting the files from the root cause another problem?
Thanks to all who have read about my issue. Hopefully we can come up with a solution.
f2s
free2scour said:
I have transferred the files with no problem but after powering off, then "Up Volume/Power On", the screen just remains with the "3 Birds" and -Recovery Key Detected- and -Booting recovery kernel image- messages appearing.
Click to expand...
Click to collapse
Nearly the same here but once mine shows "recovery key detected", it reboots again and starts normally.
I can get it to boot normally by powering it down and powering it back up. I just can't get ClockworkMod to install no matter how many times I do the "Volume Up + Power Button" routine.
As a result, I am limited as to what I can do with the gtab.....
im having the same problem :/ i really wish i knew why too...i tried it so many times but it gets stuck at booting recovery kernel image
Install clockword
Same problem here it's install,but after the second reboot I can't the clockword menu it's reboot normally
You guys may have 1.2 bootloader. I do not think CWM v8 works with that bootloader. Look around for how to fix your recovery.
I just received my g tablet today (w/bootloader 1.2) and I am having the same problem as the OP. After installing CWM it will boot up normally, but when I try to hold the volume up and power keys to go into recovery it just stalls at the initial 3 birds screen.
I'm a noob and not sure what my options are to get a custom MOD on this thing. Any help appreciated.
Good god. Every thread these days have been talking about 1.1 and 1.2 compatibility. If you have 1.1 use cwm v8. If you have 1.2 use cmw 3028. In addition read second post by moi in the following thread.
http://forum.xda-developers.com/showthread.php?t=1120387
At this point you need to nvflash the appropriate cmw. Go to the following thread.
http://forum.xda-developers.com/showthread.php?t=1030042
I have exactly the same problem it sticks at the same place
Guys, you are using the wrong CWM version. Visit my website and use the right version. V8 only works with 1.1 bootloader. You have 1.2. In my website, look at option C. It shows you how to nvflash the right CWM file.
http://viewsonic-gtablet-for-dummies.webs.com/clockworkmod.htm
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. !!!
Hello all,
i have a problem with my HTC Legend.
Yesterday i installed b.0.8 custom rom and everything was working fine.
Later i tried to install Profile pro from Blackmart Alpha and i guess that corrupted it somehow. It never ended installation and this morning, when rebooting the phone, it simply hangs on the 'quietly brilliant' screen.
So, i tried to flash it using fastboot:
fastboot update [update.zip]
But i am not able. I have tried with several zips (LEGEIMG_Legend_HTC_WWE_1.23.405.1_Radio_47.26.35.04_7.05.35.26L_release_120393_signed.zip, b-0.8.zip, update-cm-7.2.0-RC1-legend-signed.zip...) and it says they are not valid or signature not valid.
I have hboot-1.00 with s-on.
I have read several posts. This one looks helpful, but i don't know how to apply:
http://forum.xda-developers.com/showthread.php?t=1519933
He says: 'I extracted the rom.zip from the RUU, signed it and then manually flashed it'
But i don't know how to extract rom.zip from 'RUU_Legend_Froyo_S_HTC_WWE_3.15.405.3_Radio_47.51.35.17_7.13.35.05_release_160328_signed.exe' and neither how to sign it.
I guess that good be a valid option for my problem.
Could somebody help here, please?
Many thanks,
Javier.
realpikolo said:
Yesterday i installed b.0.8 custom rom
Click to expand...
Click to collapse
Hello,
when you installed b.0.8 you must have clockwork recovery (as update.zip) on SD-card. Use it from the recovery-menu (enter recovery mode by turning your device on with the volume button held down and selecting 'RECOVERY', then "vol+" and "Power" to enter the blue recovery menu, then use "Apply sdcard: update.zip"). From the clockwork mode recovery wipe the legend and flash b.0.8 again.
Thanks for your reply.
But i cannot enter in recovery mode.
Phone start in HBOOT or Recovery mode with vol- and Power.
I go down to 'Recovery' with vol- and press Power, but it does not start recovery mode. Instead, a phone image with red triangle and red exclamation mark.
I think it is because i don't have the LEGEIMG.zip and .nbh in the memory card.
So, i am at the same point, phone is not starting, and i cannot flash it.
I thought on creating goldcard to flash it, but i cannot create the goldcard as all methods i find need to connect the phone in usb mode to create it. Is there a method to create an sd goldcard without the phone?
Please, assist as i don't know how to resucitate my phone.
Thanks.
realpikolo said:
I go down to 'Recovery' with vol- and press Power, but it does not start recovery mode. Instead, a phone image with red triangle and red exclamation mark.
.
Click to expand...
Click to collapse
Power/Vol+
Sometimes it needs some time. so keep pressing Power/Vol+.
Try it many times.
Many thanks for your assistance...you did it!
I was not aware of that option to enter in recovery mode.
It took too much days for such an easy thing!
Thanks again!
This happened this moring for no apparent reason, i moved a file for a game to be installed (final fantasy iv) in the android/oob folder and rebooted, and it never fully did.
Im stuck on the HTC logo forever.
At 1st i said to myself, lets go to hboot and make a factory reset, so i pressed volume - and power, and when i did, instead of restoring the device (wich was unlocked and rooted) it went back to the neverending htc logo, and it does the same for the recovery and the erase everything one, so from that point i tried installing a few firmwares from my carrier which is videotron, and it alway failed either because the signature is not compatible or simply because the device is not detected... it seems to get worst try by try...
I also tried to install from the sd card, adb or Amaze_All-In-One_Kit_V5.1 and 4.0.
Nothing works, please help me.
I just bought this phone used a month ago, and i loved it, and its unfair for it to die for no serious reason.
Are you able to access bootloader?
stuck
syedbilal093 said:
Are you able to access bootloader?
Click to expand...
Click to collapse
If it went to the HTC logo, you probably accidentally bypassed the recovery.
Turn the phone off, remove battery wait 10 seconds, install battery, wait 10 seconds, hold the volume DOWN button, while holding the volume DOWN button, press and release the power button. Keep holding the volume DOWN button until the bootloader screen appears, and then release it.
See what you can do with that.
If it doesn't help, find the RUU for your carrier--there's a list of RUU's in General section, "They're all here now" thread, and find the instructions for properly renaming it and placing it where it needs to go to have it install.