I did it, sad to say. I was trying to get back to the earlier Tnt Stock so I could move up to the latest 5.0, when I got stuck on the Viewsonic screen. I had clockworkmod installed, but now nothing works. and when I try to get into recovery, it says it detects the key but then does nothing. I cannot see it when I connect it with my computer, and so I cannot install nvflash. Any suggestions?
i doubt you bricked it, as far as i know, its litteraly impossible to brick.
one of the more informed will be able to help you
if you think you can not get into apx mode, no power then inside next to the reset button are four solder spots that you can cover with a small piece of foil to recover to apx mode then run nvidia flash and you are back. you can not brick the gtab unless you physically break something.
Both of the previous posters are correct. Its practically impossible to brick it.
I use Ubuntu(Linux) so drivers aren't an issue for me. Sometimes Windows can be sketchy when it comes to APX.
Have you tried following the nvflash full restore guide? It should get you back on track.
Sent from my HTC Vision using XDA App
Reggie777 said:
I did it, sad to say. I was trying to get back to the earlier Tnt Stock so I could move up to the latest 5.0, when I got stuck on the Viewsonic screen. I had clockworkmod installed, but now nothing works. and when I try to get into recovery, it says it detects the key but then does nothing. I cannot see it when I connect it with my computer, and so I cannot install nvflash. Any suggestions?
Click to expand...
Click to collapse
Go here,
http://forum.xda-developers.com/showthread.php?t=861950
You only need to make sure you have the proper nvidia usb drivers installed so APX can work correctly with your Linux/PC OS.
It's a little tricky for Windows 7/64Bit but it does work, I brought my GTAB back from Brick using the method on that thread.
agreed, I thought I had bricked it, and when i plugged it in and although it didnt seem to be powered on at all, i ran the nvflash to stock image, it powered up the screen in nvrecovery, took the files and booted right up. So far, I've done it 3 times. It might seemed bricked, but it's probably just in APX mode until its reflashed. Linux: easy peasy, Winders: driver hell, but... once the drivers were in, it was just as easy. follow the directions, and you should have a working stock G-Tab in 3 minutes.
I'm tryin'.....
Thanks for the moral support, everyone. I'm taking a deep breath, trying not to panic, and trying the suggested thread. Actually it is my second time trying that, but before I was really panicked. I'm "calmed" down a little now.
I think I do not have the right USB drivers, since I keep getting "USB device not found" error message. The USB drivers were mentioned before, but where do I get them, and how do I install them? There is a file, "android_winusb.inf" that is among the unzipped files, but I still get the error.
When I boot to the APX mode, I do hear my computer "ding", so I gather it is trying to communicate. When I look at my Devices, It does show an APX device, but says the driver is not loaded. I've tried pointing the update driver to the folder with the "android_winusb.inf" file, but it doesn't see it, and the online search for the driver also comes up zilch. BTW I'm using Windows 7.
I'm breathing... I'm trying not to panic... At least I am progressing a little. I never knew that power on+down volume was different than power on+up volume...
for windows apx usb driver for windows
here is the link. oops cant post link just cut and paste
developer.download.nvidia.com/tegra/files/android_tegra_froyo_20101105.msi
After installing the .msi file connected the gtab by holding down the vol - and power together then go to the device manager find apx ? update the driver . It is located in the program files x86 ndivia section. C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105. It will install the driver.
hope this helps
Charles77 said:
here is the link. oops cant post link just cut and paste
developer.download.nvidia.com/tegra/files/android_tegra_froyo_20101105.msi
After installing the .msi file connected the gtab by holding down the vol - and power together then go to the device manager find apx ? update the driver . It is located in the program files x86 ndivia section. C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105. It will install the driver.
hope this helps
Click to expand...
Click to collapse
This is correct, and for 64bit systems I believe there is a folder labelled usbpcdriver in there somewhere and the "Nvidiausb.inf" driver file for the 64bit system is in there.
http://developer.download.nvidia.com/tegra/files/android_tegra_froyo_20101105.msi
sORRY, BUT....
You need better Kung-Fu to take down the tablet!
Just get the correct USB driver for your WinOS as other posted. And it's good you noticed the difference DOWN and UP volume button usage!
Whew! Success... I have Tnt back...
I have NEVER been so glad to see that little blue desktop!!! Again, this community of devotees to the gTab is Fantastic. Thanks for all the help... and once again, our gTab remains unbrickable. Even by this owner. I updated it with the OTA to the 3588 version. I think I will wait a little and calm down before trying the new TnT 5.0, which I was attempting to do and started all this "drama". But I do know that with the support of all you people here, I can continue to learn about our wonderful gTab. Kudos and Gratitude!
"Never Give Up! Never Surrender"....... Galaxy Quest
In the future you could also download a ubuntu live cd and run nvflash from that which would eliminate the need for drivers and also keep your windows os in tact.
follow up...
I did the TnT 5.0 update successfully! Yeah! All the help paid off.
Reggie777 said:
I did the TnT 5.0 update successfully! Yeah! All the help paid off.
Click to expand...
Click to collapse
Party On!!!
Only way to brick the gtablet is to pour cement on it and literally make it into a brick.
Can someone please give me step by step directions for this?
I couldn't get past the birds booting up and I downloaded the package below and I guess I ran the wrong flash file. Now my tablet won't boot at all. It is as if the power switch does nothing.
Any help is greatly appreciated.
TEK112 said:
Can someone please give me step by step directions for this?
I couldn't get past the birds booting up and I downloaded the package below and I guess I ran the wrong flash file. Now my tablet won't boot at all. It is as if the power switch does nothing.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Was this the TnT Lite 5.00 upgade? If so, check out the nflash links in my first post -- you might need to do that to get back on track.
Sadly this was me trying to downgrade clockwordmod manually and it got all sorts of outta whack.
edit: All is well. I nvflashed back to stock.
I have saved the entire folder in case anyone else needs it. Just open the folder and run the batch command and you are back to out-of-the-box stock.
Reggie,
Go to the original 5.0.0 sticky thread in the Developers Forum and go to the instructions and find the link to post 3798. In that post I list all the steps I
took and exactly the stuff I needed to NVFlash back from the same state you
are in.
The flash setup is not hard. It just took me a while to find USB drivers and I
have taken care of that now.
Good luck and keep us posted.
Rev
I had the same issue. Initially I freaked as well. Are you running a 32 or 64 bit system? That makes a difference as to which drivers you'll even be able to install. I have a 32 desktop and 64 laptop. After getting the correct drivers to install it was a breeze. Still having issues connecting in APX mode on the desktop but I'm determined to get it working.
Related
I'm a newbie, and have somehow managed to get the g tablet in a loop.
I tried to reload the gtabletrestore file by pressing PWR and the Vol+, but go into CWR. There I can't access the SD card to run update. Upon reboot, I get the message:
magic value mismatch.
I need help.....
Do you have ADB setup on your PC so you can use nvflash and/or a shell on the tablet?
Nope,... to be honest, I'm not sure what to do now...
Google "Install ADB for" whatever you have ie windows, mac, linux. If you have a 64bit windows then google 64bit. You will also need to read this thread for nvflash. ADB must be working first. If you are a user of IRC then go to freenode and enter the #tegratab channel. Someone there can usually walk you thru everything. Its very easy once you understand and when you can do this your tab is virtually unbrickable.
http://forum.xda-developers.com/showthread.php?t=861950
Okay, will do and will post my results.
thank you!
Oy Vey,
Ok so, if nothing but a blank screen comes up..
and I mean Power btn + Volume Up btn does nothing what so ever but the device is powering on with nothing but blank screen, is it possible the GTAB is bricked??
It sounds like you need to do the same process....adb and nvflash
thebadfrog said:
It sounds like you need to do the same process....adb and nvflash
Click to expand...
Click to collapse
Thank you,
I pretty much bricked my GTAB after I flashed the experimental version of CWM on the DL page of GoJimi's Site. I rebooted and got a "Black Screen" with nothing else.
So it's safe to say we shouldn't use that experimental version... AT ALL!!!
Oy Vey, my heart was in cardiac arrythmia all this time...*lol*
tekrhino said:
Thank you,
I pretty much bricked my GTAB after I flashed the experimental version of CWM on the DL page of GoJimi's Site. I rebooted and got a "Black Screen" with nothing else.
So it's safe to say we shouldn't use that experimental version... AT ALL!!!
Oy Vey, my heart was in cardiac arrythmia all this time...*lol*
Click to expand...
Click to collapse
Just the experimental version of cwm....the regular bekit 0.8 should work
Has anyone found a solution
Hello,
I am new to the forum., I am in the same situation. I think I bricked my tablet. I am able to use nvflash to revert back to the stock image, but when the tablet is turned off it does not come back on. I have to flash it again. Does anyone have any ideas?
Is it possible to perm brick your phone? My phone got stuck somewhere in the middle of an Odin flash and I had to pull the plug. Since then I have been stuck at the "Phone...!....Computer" picture.
I can get the downloading "Do not turn off Target!!!" section with the cable plugged in and no battery. I also have it recognized by Samsung PSLite, but when I'm trying to flash the stock rom back on through PSLite it disconnects as soon as it goes to 0%.
Will it make a difference that I have Win7 64bit and the VIA drivers say 32bit on them? I'm pretty sure I have every other driver that's needed.
Any help is GREATLY appreciated. I'm a sad panda without my new phone :-(
Go to the dev section of this forum.
http://forum.xda-developers.com/showpost.php?p=14147928&postcount=3
Follows these directions exactly. Will recovery your phone for you.
Good part is, you are not bricked.
Yeah, I've been following a couple of forums that all show nearly the exact same directions. Been getting stuck on the same area...
I have very little knowledge of any of this other than following instructions (obviously not that well) but something tells me it has to be a driver issue.
The VIA drivers I installed say 32bit and my machine is Win7 64. Also, when I plug the phone in it is recognized by my computer with no errors. Once I start the install and it gets to "VIA download" I get the error - then my computer tells me the device was not recognized. I have to do a full reboot to get my computer to recognize my phone again.
Thanks for the directions
Hey man, if that isnt working for you (which I dont see how.) You can always call tech support and say your phone is not booting, even after you pull the battery out. Just say it stays stuck on the samsung screen. They will send out a new phone. Just saying but it should work regardless. Also try another USB port, see if that solves your issue and make sure you are using the OEM usb cable.
I'm assuming this will work for you. It did for me. I had the same screen.
Download first file.
Odin 1.82
Open Odin then hook up your phone and put into download mode with the battery out. Crucial part here. Put the battery back in. After flash the first file I linked you to but make sure you check the PDA option and do it through PDA only.
Should fix it I do believe.
If you follow that exactly like is says. from start to finish. forgetting that you have ever tried anything before. And still follow it. You will be fine. download everything it says download, and follow the instructions exactly.
Thanks for all the feedback everyone.
I've been trying everything suggested on here except getting a newer version of Odin. When I get in tonight I'll keep trucking along with different tweeks.
The good news is I accepted defeat (Grrr!) and have a warranty replacement on the way. It kills me that I couldn't get this on my own.
I've even installed everything on my laptop with the exact same results. As soon as I get to the downloading portion where it shows 0% the phone disconnects and my computer tells me it is no longer recognized. This was in PSLite. Odin simply says FAIL when I try to flash that method.
I have a week to return the first phone. I'll use that time to get all my drivers in order and get this figured out.
After you put the phone into download mode when it was hooked up to the computer did you put the battery back in? I had the same screen as you and when I tried to use Odin it would just say it failed every time. Put the battery back into your phone after it is in download mode before you try to flash with Odin.
Also for PSLite I had to plug in the phone (in download mode) before starting PSLite (opposite of ODIN).
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
mikepic said:
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
Click to expand...
Click to collapse
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
elucid said:
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
Click to expand...
Click to collapse
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
dragonstalker said:
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
Click to expand...
Click to collapse
I agree rooting was really easy. Several people have had issues where they needed to restore using and ODIN and it complete fails (this is after using ODIN successfully to flash ROMS, recovery, kernels). See the end of this thread:
http://forum.xda-developers.com/showthread.php?t=1108115
You can blame it on user error, but I can assure you that I didn't do anything that should have caused my /data partiion to not mount. Sometimes things happen and the last thing you want is ODIN failing to flash when you have a brick on your hands.
Hope you fix your phone :] It always pains me to see one of these posts where someone has a bootloop or even a dreadful brick.
I keep trying to load the APX USB drivers and I keep getting this error...Can someone please help?
Cannot Continue with Hardware Update Wizard.
The wizard could not find a better match for your hardware than the software you currently have install.
I have tried every version of of the drivers that I can find.
Any help is greatly appreciated.
Thanks
Matt
Are you running a rom or stock, and if so which one? Have you tried this yet? That should work for you, but if you are running the ICS rom you will need to follow the instructions in the first post of the ICS thread under 'How to Install MTP Drivers'.
I am just using stock install right now and I am trying to get a rom on there. When I go to boot into APX it just sits at "Booting recovery kernel image" - it never gets past that. I am not sure why.
I actually did try your post before I posted myself. I have tried this multiple time on multiple machines with various flavors of Windows - XP, Vista, and Win7.
Thanks for the help.
Matt
Strange ... sounds like it is failing to boot into recovery, not APX mode. When you boot to APX it should show the 3 birds screen for a second, then go completely black (looks like it is turned off, but it is actually in APX). It shouldn't say anything. Are you holding Volume Down while pressing the power button? If you are, try holding Volume Up instead, I have heard that some Gtabs have the volume controls switched.
About the 'Booting Recovery Kernel Image', did you install a different recovery (CWM)? If so, which bootloader are you on and which recovery version did you try to install?
hutchinsonm said:
I am just using stock install right now and I am trying to get a rom on there. When I go to boot into APX it just sits at "Booting recovery kernel image" - it never gets past that. I am not sure why.
I actually did try your post before I posted myself. I have tried this multiple time on multiple machines with various flavors of Windows - XP, Vista, and Win7.
Thanks for the help.
Matt
Click to expand...
Click to collapse
Hey there, there are a few pre-steps that need to be done befor you can start flashing ROMs on a gtab.
A good reference is here
You will crap oout your gtab but as long as you know how to NVFlash a gatb is almost impossible to brick. KEYWORD ALMOST. The scret is ensureing you NVFLash the right BootLoader to the ROM you are trying to load. An example nvflash BL1.2 for a 1.2 ROM like CM7 there is also BL1.1 so be certain of what you are trying to load...
GLTY
hutchinsonm said:
I am just using stock install right now and I am trying to get a rom on there. When I go to boot into APX it just sits at "Booting recovery kernel image" - it never gets past that. I am not sure why.
I actually did try your post before I posted myself. I have tried this multiple time on multiple machines with various flavors of Windows - XP, Vista, and Win7.
Thanks for the help.
Matt
Click to expand...
Click to collapse
Your gTab is displaying the same behavior as mine. I went to install CWM, and it failed to install. Afterwards, my Amazon App store kept crashing every time I opened it. I tried reinstalling, and everything else (mostly games for the kids) started crashing also. I decided to go back to factory settings. It powered off, and then gave me the same message: Booting recovery kernel image with the three birds on the screen. It does not give me an option to choose a recovery. I followed instructions to recover from the external SD card, but it only sits there at the booting recovery kernel image message. Doesn't seem to make a difference whether I power on with the volume key pressed or not. It always goes to the same message.
Did you have any luck getting past that message with your gTab?
Peter
hutchinsonm said:
I keep trying to load the APX USB drivers and I keep getting this error...Can someone please help?
Cannot Continue with Hardware Update Wizard.
The wizard could not find a better match for your hardware than the software you currently have install.
I have tried every version of of the drivers that I can find.
Any help is greatly appreciated.
Thanks
Matt
Click to expand...
Click to collapse
Matt, If I'm not mistaken you're using the wizard to try and install the APX USB drivers to your computer. You have to MANUALLY point Windows to the folder containing the correct driver and it should find it. Otherwise it will give you that same message.
Hello, first time posted, long time browser...
So, I have a bricked (or almost totally bricked) LG G2X. Here is what I did:
I had flashed the Hellfire Sandwich 1.9 rom and was just fine...until my phone started turning off randomly. After reading somewhere here that I should nullify my phone and the re-flash the rom in order to fix my issue.
So, I backed up my data and downloaded the Aroma Nullifier from Volk (thanks for all you do). I booted to recovery and ran the Nullifier. Once the Nullifier had stopped, still while in Recovery, I tried to access my sdcard to re-flash my Rom...well, I couldn't access my SD card. Furthermore, I couldn't unmount the SD or mount the USB Storage.
Here comes the big mistake:
So, as I was doing some research about how to proceed, my USB cord wiggled out of the phone and my phone lost power. Now, since I had read from Volk not to let that happen, I knew I was in trouble.
At this point, I can only load into the LG Boot Screen and my computer loads drivers for "Asus Android Device" (I have the Asus Transformer Prime Tablet) and under that title "Asus Android Bootloader Interface". No APX, No USB Controller....no other communication.
Last little note, I took the phone to the Tmobile store on a hunch one of the guys who works there had some experience (which he did), and while he was trying to boot into recovery from battery power (something I have been unable to do) he got the USB communication interface...something like "S/W Do not disconnect".... Since then, I have not been able to reproduce that interface.
I am at the end of my abilities...I haven't seen anything that addresses this particular problem though I have tried a bunch of solutions without success. I have looked all through XDA forums, but if there is one I missed, please let me know.
Any thoughts would be very helpful.
Kickingcans
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Thanks much...but...
therealnexion said:
If you haven't already, I recommend looking into nvflash. I'm almost certain you'll be able to fix this. nvflash works at a very low level, requiring that you connect your phone without a battery using a special startup sequence. You will need the APX driver (for Windows) to make it recognize your phone in this recovery mode. At that point, you should be able to flash CWM using nvflash and go from there. If you can't get into recovery, I seem to recall flashing the stock ROM itself with nvflash.
This thread should help you: forum.gsmhosting.com/vbb/archive/t-1503546.html (I can't link yet)
Specifically, the link in the "I solved it" post.
Good luck, and let us know when you get it working :good:
Click to expand...
Click to collapse
Thanks for the thoughts. I will try that all again, but I have tried nvflash and tried updating APX drivers. My computer only recognizes the phone as an "Android Bootloader Interface". When I try to manually update/change the drivers for the "Android Device", there is a problem with 64-Bit operating System (Windows 7 Home Premium). I was going to try to boot the computer in Safe Mode, but I don't know if that will help.
I haven't been able to communicate with the phone, and only saw the S/W Upgrade screen once and that was in the Tmobile store without access to my computer.
I am going to try those suggested steps again. Thanks again.
Leigh
Got it going....
THANKS SO MUCH. I knew I was missing something stupid. I kept reading the nvflash instructions and pressing the Power and Volume Down button instead of Volume Up and Down.
Things are going again. Thanks so much.
Kickingcans
All I want to do is root this thing, and after spending the better part of a day updating firmware, it seems I screwed the pooch doing that first.
I tried my best to follow the outdated tutorials, first step of each sent me onto another tutorial, etc. So I had device manager up, I sent it to look for the Universal Naked Driver, it said I was up to date, plugged along. Mini ADB and fastboot went up, my shield was in dev debug mode. ADB reboot command fails, and now my tablet won't power up with the hard key, and the computer wont recognize it.
Are there any solutions to this problem?
If the tablet doesn't power up maybe u have to send it to nvidia. [emoji20]
I just followed this
http://forum.xda-developers.com/showthread.php?p=57478001
And everything worked fine.
BareGrizzly said:
All I want to do is root this thing, and after spending the better part of a day updating firmware, it seems I screwed the pooch doing that first.
I tried my best to follow the outdated tutorials, first step of each sent me onto another tutorial, etc. So I had device manager up, I sent it to look for the Universal Naked Driver, it said I was up to date, plugged along. Mini ADB and fastboot went up, my shield was in dev debug mode. ADB reboot command fails, and now my tablet won't power up with the hard key, and the computer wont recognize it.
Are there any solutions to this problem?
Click to expand...
Click to collapse
Seems quite strange that it would get bricked since you seem to have not done any operations to the tablet at all. Did you try to flash anything while in adb or fastboot? Are you holding down the power button long enough to power on? You need to hold that mushy button for what might seem like forever. There are tools like Win Droid that do what you're trying to do.
But yes, seems like you might need to send it in if the tablet is actually bricked.
Fustigador said:
If the tablet doesn't power up maybe u have to send it to nvidia. [emoji20]
I just followed this
http://forum.xda-developers.com/showthread.php?p=57478001
And everything worked fine.
Click to expand...
Click to collapse
That was the one I started with, but I had to follow the breadcrumbs through the separate tool threads.
I factory reset the device before beginning this process, I hadn't entrenched myself in the tablet since I've only had it since last Thursday. Doubt that has bearing.
I'd noticed software issues, freezing in and out of the lock screen. This was high among the reasons I decided to root it. Its possible I got a lemon, and if I didn't muck up the bootloader its still under factory warranty, correct? Should I contact Amazon who I bought it from before contacting Nvidia?
If it doesn't turn on maybe it as nothing to do with unlocking the bootloader.
Just activate the waranty.
I charged it overnight, and turned it on via recovery (down volume and power). It seems to be running fine now. Thanks for the advice, and I'll continue the process in the appropriate threads.
:good: