I have yet to find an answer for this. I have a Viewsonic G Tablet Rooted running Clockwork Recovery. I was having issues installing CM7 so I thought to downgrade the recovery version as I've had some success doing the same on my Evo. After several attempts, I mistakenly selected "Flash ClockworkMod Recovery" and selected one of the 4 devices it listed, none of which was a G Tablet. Tried each of the other 3 devices with no success. Ever since I have not been able to boot into recovery at all. Just behaves like it is about to, then seems to shut off. So I'm at a loss, I can't find any way to flash another recovery or even restore to defaults. Any ideas?
Are you using ROM manager from the marketplace? You should not. You may need to install recovery using nvflash or another method. Many ways to do this are outlined on the Stickies in the General and Dev sections here.
For the gTablet there are two versions of CWM to use. One is called CWM .08 (there are some other version numbers, but people reference it as CWM .08 around here). This "old" version works just fine, and is meant for the 1.1 bootloader. The 1.1 bootloader is what most ROM's on XDA use, and what the latest stock OTA update uses (3389).
The other is CWM_3.0.2.8 which is used for the 1.2 bootloader and requires a 1.2 friendly kernel. 1.2 based roms are mostly being worked on by roebeet over on the slatedroid forums. He has a TnT based rom, an Advent Vega (stock froyo-ish), and NI Adam/Eden/Froyo rom that are being phased out. The one being continued is a HCAdam/Vegacomb port to the gtab. Nearly any rom can run on 1.2 bootloader, it just needs to be installed in the right way.
No, I sideloaded a copy of Rom Manager 4x and did use CWM .08. But where I seem to have gotten myself is my tab shuts down when I boot into recovery. I get to the first splash while I continue to hold power+up and from there the device turns off. This problem conflicts with the fast majority of options I have tried, and ones you have listed. Closest I came was using Terminal but it would grant me SuperUser but then I would get fixrecovery.sh not found.
From Rom Manager, under 'Confirm Phone Model' I have Advent Vega selected. This is the list I seem to have gotten myself into trouble from. It was only after I selected something else that I lost access to recovery. I am assuming Vega is what I want since some guides I've come across seem to be interchangeable.
Sacrifusion said:
I get to the first splash while I continue to hold power+up and from there the device turns off.
Click to expand...
Click to collapse
That sounds like you're going into APX mode (Power and Volume Down).
Try loading CWM via NVflash. My post does not delete the rom, but installs just the CWM. If you follow the instruction on the next post, you will overwrite the rom.
http://forum.xda-developers.com/showthread.php?t=1058649
K J Rad said:
That sounds like you're going into APX mode (Power and Volume Down).
Click to expand...
Click to collapse
Well, the gtab is a a little backwards for me since I am used to the volume up button being in the same direction as the power button from other devices. But I have definately been pressing vol up (and unless the buttons switch prior to boot, the button I am pressing for vol up does raise the vol in the TnT UI). For gits and shiggles I tried vol down as well but seems to behave in the same manner.
supergroverthm said:
Try loading CWM via NVflash. My post does not delete the rom, but installs just the CWM. If you follow the instruction on the next post, you will overwrite the rom.
http://forum.xda-developers.com/showthread.php?t=1058649
Click to expand...
Click to collapse
I am not a fan of the rom so long as I can get my recovery back. But I'll follow your guide and see if I can make some progress. Most have suggested against NVFlash, but it's not sounding like I have other options left.
Thanx guys
Do learn how to use NVFlash, it's saved me from many soft bricks and boot loops.
supergroverthm said:
Do learn how to use NVFlash, it's saved me from many soft bricks and boot loops.
Click to expand...
Click to collapse
Got hung up for a minute trying to get passed the ACCESS DENIED for the Tegra SDK till I realized I could just use the Vega drivers. After catching that folly, I followed your guide to a T creating the .bat file and all. Executed it, a terminal popped up for a split second and then was gone. I was hoping for a confirmation, but after waiting a moment and not seeing either device giving me any signs, I tried to boot the gtab into recovery and am back to square one. Still getting the same black screen much like the APX mode. In a sec here for gits and shiggles I'll see if my laptop recognizes as being in APX mode. But after 2 attempts to run the recovery + .bat, I am still pseudo bricked (and yes, I do consider TnT to be a bricked rom XD ).
Ok, I had a different result after I dumped the contents of the nvflash_windows folder into my NVFlash folder. Not sure if it's just me, but I read the instructions a few times and didn't quite see where it instructed to do that. But a wee bit of common sense told me the .bat file isn't going to do a whole lot if it can't see the nvflash.exe file. Think Robeet's post may have gotten caught up in hopping back and forth between the Win and Lin instructions. Currently I am looking at a black screen on my gtab with "Entering NvFlash recovery mode / Nv3p Server" and hasn't done a whole lot since. Been chilling like that for at least 8 min now. Not sure if it's just hard at work, or stopped all together. Will keep you all posted.
And we are in business// That did the trick. And I emphatically agree that NVFlash is an awesome tool. I thank you all for the assistance and hopefully my next post will be in the form of a contribution as opposed to a question.
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
Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do
My GTab will only boot up with NVFlash in APX mode. It will not power on via the power button, nor with CWM. I just bought this GTab, tried loading CWM and it didn't take (or thought so), so tried to nvflash with CWM and now it will only boot with power and volume(-) into apx. Once it boots, all my files are there. I have tried detox from gtab for dummies. I am guessing my next option is letting the battery drain all the way and go from there? Any help would be great. thanks
PS This is my second GTAB and have experience rooting, and flashing roms.
Not sure what you mean by "it only boots into APX but all my files are there." APX mode doesn't allow access to files as far as I'm aware.
Also you may want to double check the orientation of your vol + and - keys. The gtab for dummies site notes that some models have the orientation switched.
You could try one of these procedures:
1. K J Rad's procedure for unbricking gTabs. (Actually, read carefully through that entire thread.) Follow all steps exactly as mentioned.
2. Childofthehorn's method. See this video:
How to unbrick your Viewsonic G-Tablet by Railfan02.
Yes, I had seen those sources for a solution. After researching and googling, this is what I found and it worked. What I meant by only boot in APX mode is, it only would load a rom via APX and I had to NVFLASH. I couldn't get into CWM Recovery with volume + or volume -, so after searching, this was my first choice and it worked on the first try.
http://www.slatedroid.com/topic/221...n-gtab-does-not-turn-on-and-stay-in-apx-mode/
If this didn't work, I was going to try Childofthehorn's option here.
http://forum.xda-developers.com/showthread.php?t=1118087
Anyway, I am happy that I got it up and running on Flashback.
pattyboh said:
Yes, I had seen those sources for a solution. After researching and googling, this is what I found and it worked. What I meant by only boot in APX mode is, it only would load a rom via APX and I had to NVFLASH. I couldn't get into CWM Recovery with volume + or volume -, so after searching, this was my first choice and it worked on the first try.
http://www.slatedroid.com/topic/221...n-gtab-does-not-turn-on-and-stay-in-apx-mode/
Click to expand...
Click to collapse
That seems to be the procedure figured out by K J Rad some time back.
Holy Crap! This fixed my Gtablet. Awesome.
Hello
I rooted my Galaxy s2 i777 using 2.3.6 (I think that was it - what ATT pushed out earlier in the summer) and next flashed CWM using ODIN. I noticed that the menus weren't working in CWM. When I use the home or menu buttons it just toggles a logo screen, and power does nothing (volume keys do work). I noticed others had this issue with this phone but didn't encounter any solutions.
Poking around the Rom Manager application I noticed a reboot into recovery mode feature and thought I'd try it. It did as advertised. But now when I reboot by holding down power it immediately reboots into recovery mode. I'm guessing what happens is the "reboot into recovery mode" feature put itself at the head of the boot sequence and instead of removing itself from there on load, which it probably should, it waits until the user exits the program cleanly. Unfortunately, because I can't get the keys to work in the program, the only way I can exit is to hold down power. I can navigate to the "power off" or "reboot" options but I can't execute them (press "enter"). So it stays at the head of the boot sequence (just my theory) and I can't get out. Actually when I power off by holding down the power key the phone just reboots immediately, right back into cwm recovery, so there seems to be something more going on.
I have a backup of the system but I can't figure out how to get out of the sequence. I tried the download mode and recovery mode key sequences but they don't work (not even sure if they're supposed to work in this recovery screen). Any ideas? I have a backup of the system, so I'm happy to attempt scorched earth suggestions. Kies can't recognize the phone anymore. Many thanks.
Jason Farnon said:
Hello
I rooted my Galaxy s2 i777 using 2.3.6 (I think that was it - what ATT pushed out earlier in the summer) and next flashed CWM using ODIN. I noticed that the menus weren't working in CWM. When I use the home or menu buttons it just toggles a logo screen, and power does nothing (volume keys do work). I noticed others had this issue with this phone but didn't encounter any solutions.
Poking around the Rom Manager application I noticed a reboot into recovery mode feature and thought I'd try it. It did as advertised. But now when I reboot by holding down power it immediately reboots into recovery mode. I'm guessing what happens is the "reboot into recovery mode" feature put itself at the head of the boot sequence and instead of removing itself from there on load, which it probably should, it waits until the user exits the program cleanly. Unfortunately, because I can't get the keys to work in the program, the only way I can exit is to hold down power. I can navigate to the "power off" or "reboot" options but I can't execute them (press "enter"). So it stays at the head of the boot sequence (just my theory) and I can't get out. Actually when I power off by holding down the power key the phone just reboots immediately, right back into cwm recovery, so there seems to be something more going on.
I have a backup of the system but I can't figure out how to get out of the sequence. I tried the download mode and recovery mode key sequences but they don't work (not even sure if they're supposed to work in this recovery screen). Any ideas? I have a backup of the system, so I'm happy to attempt scorched earth suggestions. Kies can't recognize the phone anymore. Many thanks.
Click to expand...
Click to collapse
1. you obviously flashed a kernel WITH CWM via Odin.
2. Rom Manager should not be used.
Flash a rooted stock ROM via ODIN.
read around in the stickies of the i777 forum, and get acquainted with things.
Boot into CWM correctly, and go about flashing whatever you want knowing what you just learned by reading the correct stuff.
Welp, first things first.
1. Read, search, Google, only look at results from this forum, i.e. the ATT Galaxy S2 I777 forums on XDA. Any info from any other sites is more likely to get you nowhere or brick your phone further.
2. After having done so, you'll learn never to use Rom Manager. EVER.
3. Also after having done #1, you'll learn to never try to flash CWM separately. As Moto implies, CWM for our phones is built into custom kernels, it is not separate.
4. Follow this guide to start over and get back to stock.
5. Then follow this guide to root and flash custom ROMs and kernels.
You sound like an intelligent guy, so as long as you do more reading around here you'll figure everything out slowly. Make sure to read stuff multiple times until you fully understand everything, and feel free to ask questions about stuff you don't understand, but only after reading said guides multiple times.
EDIT: Gah Moto, why you gotta post ahead of me D:
Actually the problem is most likely the fact that he is probably using an old version of cwm where the home button selects stuff. And rom manager.
Sent from team Pirate! Using Tapatalk 2
karate104 said:
Welp, first things first.
1. Read, search, Google, only look at results from this forum, i.e. the ATT Galaxy S2 I777 forums on XDA. Any info from any other sites is more likely to get you nowhere or brick your phone further.
2. After having done so, you'll learn never to use Rom Manager. EVER.
3. Also after having done #1, you'll learn to never try to flash CWM separately. As Moto implies, CWM for our phones is built into custom kernels, it is not separate.
4. Follow this guide to start over and get back to stock.
5. Then follow this guide to root and flash custom ROMs and kernels.
You sound like an intelligent guy, so as long as you do more reading around here you'll figure everything out slowly. Make sure to read stuff multiple times until you fully understand everything, and feel free to ask questions about stuff you don't understand, but only after reading said guides multiple times.
EDIT: Gah Moto, why you gotta post ahead of me D:
Click to expand...
Click to collapse
Thanks, that did it. I'd actually read the stickies, I just didn't think I could get into download mode because the phone was stuck in that auto-reboot loop.
For anyone else stuck in that loop cwm recovery loop, the download mode entry method (press both volume keys and insert usb) needs to be timed just so, since you usually perform the sequence when the phone is powered down (in stable way) but in this situation you only have a moment before it restarts. After powering down, just as it restarts automatically you can see the capacitative buttons blink for an instant, and that's when I started the sequence. Took me about half a dozen times but I eventually caught it. Am I the only one struggling with how hard these captchas are getting over the years? there's probably a sticky for that too I guess nvm.
If I'm not mistaken you can get into download mode without having a battery plugged in, so no need for trying to time it. Just hold volume buttons and plug in USB. For future reference; glad you got it worked out. Make sure to read the second guide thoroughly so you know how to safely flash stuff, and hit my thanks button if i helped you out.
Sent from my SGH-I777