Hey Guys,
I am sorry in advance if similar issue has been posted but I really need your help !
I just got my gtab and flashed with TnT Lite 4.4.0. I need to restore the original from factory. Now I am facing a problem, I can't go to the recovery mode because it stayed at viewsonic logo (not gtab). I can see the "recovery key detacted" at upper left corner but nothing else.
Please help me on back to restore the original or how can I go into the recovery mode to install/modify ?
I am just a new born baby and just step in this android world. any suggest is great help for me.
Thank you
Follow my link.
What happens if you hold only the power button for several seconds (10-30). Will your tab reboot? If it does what do you get then?
buchaneer.nl said:
What happens if you hold only the power button for several seconds (10-30). Will your tab reboot? If it does what do you get then?
Click to expand...
Click to collapse
Holding it for 10-30 seconds and then release will yield the same result as if you hold it for 5 seconds and then release. The gtab will turn off. To turn it on again, you need to hold the power button again.
Sorry for not stating the obvious What happens when you restart? Does it start up?
goodintentions said:
Holding it for 10-30 seconds and then release will yield the same result as if you hold it for 5 seconds and then release. The gtab will turn off. To turn it on again, you need to hold the power button again.
Click to expand...
Click to collapse
Hey Goodintentions if you want a monopoly on answering questions go right ahead. My intentions were only to help. Maybe you have more of a vested interest
Haha, I just temporarily have a lot of free time due to almost dying but now suffering from a massive infection. Right now, moving my fingers to type is about the only thing I can do comfortably.
Think of it this way. While I was 40 feet in above ground hand sawing a large branch off, it got loose, caught one of the ropes on its way down, the rope caught my arm, and dragged me down with it. Hanging on for my dear life, I used my other hand to grab the hand saw still dangling and cut the rope freeing my arm. The damn thing took a large chunk of my skin with it. I think it stretched my left arm out several inches.
Anyway, my dumbass decided it wasn't serious enough to go to the doctor. Patched up everything by myself and now I have an massive infection, a very sore arm, and lots of free time.
Edit.
Not to mention that asshole neighbor of mine who called the city to complain that I left the branch out violating city code.
How you get better...
goodintentions said:
Haha, I just temporarily have a lot of free time due to almost dying but now suffering from a massive infection. Right now, moving my fingers to type is about the only thing I can do comfortably.
Think of it this way. While I was 40 feet in above ground hand sawing a large branch off, it got loose, caught one of the ropes on its way down, the rope caught my arm, and dragged me down with it. Hanging on for my dear life, I used my other hand to grab the hand saw still dangling and cut the rope freeing my arm. The damn thing took a large chunk of my skin with it. I think it stretched my left arm out several inches.
Anyway, my dumbass decided it wasn't serious enough to go to the doctor. Patched up everything by myself and now I have an massive infection, a very sore arm, and lots of free time.
Edit.
Not to mention that asshole neighbor of mine who called the city to complain that I left the branch out violating city code.
Click to expand...
Click to collapse
Sorry to hear of your accident.
You have been very helpful to me. Thanks.
Hard-bricked?
Hello everybody,
I had VEGAn-GE-7.0.0-RC1-Harmony-signed flashed into my gtablet and I tried to flash update-smb_a1002-4349-user.
I've got a error (something similar to: bootloader not a command...) and after restart the tablet is bricked.
When I enter into recovery mode, I have the two messages
Detect a recovery key pressed
Booting recovery kernel image
and the tablet stop there. No changes in the screen and no USB recognition.
So I can't fix that with nvflash. It seems that the recovery kernel image (if there is one) is corrupted.
Do you know a solution for this case?
Thanks in advance
fogamz said:
Hello everybody,
I had VEGAn-GE-7.0.0-RC1-Harmony-signed flashed into my gtablet and I tried to flash update-smb_a1002-4349-user.
I've got a error (something similar to: bootloader not a command...) and after restart the tablet is bricked.
When I enter into recovery mode, I have the two messages
Detect a recovery key pressed
Booting recovery kernel image
and the tablet stop there. No changes in the screen and no USB recognition.
So I can't fix that with nvflash. It seems that the recovery kernel image (if there is one) is corrupted.
Do you know a solution for this case?
Thanks in advance
Click to expand...
Click to collapse
You flashed a 1.2 bootloader ROM over a 1.1 bootloader ROM using ClockworkMod. That is a sure recipe for problems. You will have to use nvflash to fix it. Go to Goodintentions "GTablet for Dummies" website. Don't be surprised if you don't see the VS Birds logo (or anything else) when you try to get into APX mode. Many people that have done this don't.
Thanks K J Rad,
Yes, I've tried cod triple red unplugging the batteries
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
http://forum.xda-developers.com/showthread.php?t=1118087
all the night and still no change.
The screen stays with the birds logo and with the two sentences (... booting recovery kernel image), no black screen as described in NVFlash procedure, and my PC doesn't recognise the USB device (not listed with lsusb in Ubuntu and no identification in windows), so I can't nvflash.
I'm going to try to drain the batteries but it seems that the kernel image is corrupted and the sw is not reseted when power off.
Hard case?
Many thanks
fogamz said:
Thanks K J Rad,
Yes, I've tried cod triple red unplugging the batteries
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
http://forum.xda-developers.com/showthread.php?t=1118087
all the night and still no change.
The screen stays with the birds logo and with the two sentences (... booting recovery kernel image), no black screen as described in NVFlash procedure, and my PC doesn't recognise the USB device (not listed with lsusb in Ubuntu and no identification in windows), so I can't nvflash.
I'm going to try to drain the batteries but it seems that the kernel image is corrupted and the sw is not reseted when power off.
Hard case?
Many thanks
Click to expand...
Click to collapse
Did you hold the Volume Down button as you were powering up?
many thanks
That's it.
I was allways pressing up. Sorry by the misundertunding and many thanks.
Regards
fogamz said:
That's it.
I was allways pressing up. Sorry by the misundertunding and many thanks.
Regards
Click to expand...
Click to collapse
Aha! You didn't follow my instructions properly. Goodness...
Added by edit.
Here is a screenshot of that portion of my instruction. Notice where the arrow is pointing at.
Are you restoring to stock to do an RMA?
goodintentions said:
Aha! You didn't follow my instructions properly. Goodness...
Added by edit.
Here is a screenshot of that portion of my instruction. Notice where the arrow is pointing at.
Click to expand...
Click to collapse
Hi, I am looking a zip file
gtab.nvflash.1.2.branch.20110617.zip
the file is 99.41 MB but I ALWAYS stock at 9.9 MB
Is it any available file I can download ??
Please help
What country are you from? I'll host it elsewhere it it makes a difference for you.
Added by edit.
Hang on. I host no such file on my website. Go to my website linked in signature and try to download that nvflash file.
goodintentions said:
What country are you from? I'll host it elsewhere it it makes a difference for you.
Added by edit.
Hang on. I host no such file on my website. Go to my website linked in signature and try to download that nvflash file.
Click to expand...
Click to collapse
I just try to download the nvflash with 1.2 branch with newer update. The nvflash1.2 zip and gtab.nvflash.1.2branch20110508.zip both stopped at 10.0 MB
Please help ! I am at Los Angeles area
Viewsonic G Tablet will not boot. Only APX mode works - 20110707
20110713- FYI. I re-posted the restore step information as a new thread and added some additional content on APX Mode and nvflash.
http://forum.xda-developers.com/showthread.php?t=1167944
Holy cow, man, that's some effort there for your wife. If it were me, I'd say "screw you, wife, here's a paperweight. Try to make it work since I screwed it up."
But seriously, I've said this before and I'm going to say it again. I'm constantly amazed at these rare cases of unrecoverable brickary that only a hand full of people get. And I have 3 gtabs to work with, not to mention thousands of visitors to my site.
Related
Hey everyone - my first post here.
Anyway, I read and read and read about my new Vibrant to see just what I could do with it without screwing it up and bricking it and I find out my device is hardware locked.
After reading [GUIDE] / [THINK TANK] - Accessing downloader & recovery w/ locked hardware access (I cannot post a link just now, apparently) from start to finish, I am more confused than not. I cannot do anything but stay in a boot loop (by holding buttons down) or boot up the phone like normal. No recovery or download mode has so far been possible.
So, can I root my phone? Should I just attempt to exchange it? Should I wait for a work-around? Or is there information I'm missing somewhere?
Thanks, all. This community is insanely helpful and cordial, without you guys I'd never have gotten my dream working properly.
Edit: I was told that my lack of drivers were the problem - I thought I didn't need them on a 32 bit system. I did. Recovery reboot solved for me!
If you cannot enter Recovery Mode with Vol Up+Vol Down+Power, your phone is defective and T-Mo will exchange it.
You're serious? It really is that simple?
So, I call them up, tell them I have a hardware locked phone and I cannot boot into recovery mode, and they'll set me up?
I'm thinking I had to go learn odin and start getting less a'scared of command lines.
FenixGryph said:
Hey everyone - my first post here.
Anyway, I read and read and read about my new Vibrant to see just what I could do with it without screwing it up and bricking it and I find out my device is hardware locked.
After reading [GUIDE] / [THINK TANK] - Accessing downloader & recovery w/ locked hardware access (I cannot post a link just now, apparently) from start to finish, I am more confused than not. I cannot do anything but stay in a boot loop (by holding buttons down) or boot up the phone like normal. No recovery or download mode has so far been possible.
So, can I root my phone? Should I just attempt to exchange it? Should I wait for a work-around? Or is there information I'm missing somewhere?
Thanks, all. This community is insanely helpful and cordial, without you guys I'd never have gotten my dream working properly.
Click to expand...
Click to collapse
Here's my advice in a step-by-step:
-Install the AndroidSDK (And make sure it is named that) Found here - http://developer.android.com/sdk/index.html
-Move the folder to Computer> Local Disk ( C: )
-Run the .exe
-Go to Settings, click on Miscellaneous, and check Force https
-Click on Available Packages and install (And then minimize)
-Click Start and search cmd (Also known as Command Prompt)
-Type cd\ (And then press enter)
-Type AndroidSDK\Tools\adb reboot download (And then press enter)
**Make sure your phone is plugged into the computer with USB Debugging turned on.
Your phone will reboot and be in Download Mode. Hope this helps.
Hardware Locked, huh? really? on the vibrant?
Can someone explain what hardware locked vibrant is. Is this some term you guys made up. I can not for the life of me, figure out, why in the world Samsung would ship some phones hardware locked and others not.
Makes no sense, someone explain, seems like this is a made up term which does not apply to Vibrant.
Either Samsung is being completely ignorant to this issue or they have the worst quality control. I am beginning to think it's both. Simply google searching brings up lots of results on this issue.
My first Vibrant (USB port eventually broke) 3 button recovery worked fine; dated July 15. The replacement after that did not work, nor did the one after that. Those were both made on Aug 16. I finally got a refund under buyer's remorse and waited another week. Got my fourth Vibrant today, made 09/01 and yes it does work with 3 button recovery.
Keep in mind none of my Vibrants were refurbished units. They were all brand new. I think Samsung has a serious flaw on their hands. I'm concerned about keeping this phone even but I added the insurance on it just in case.
By "hardware locked" they mean that you cannot access the phone's recovery or dl mode using the 3 button method.
this has apparently started with the 08/**/2010 batches. beforehand this phone was deemed "unbrickable" but it's now actually possible with the newer shipments so ppl have got to be a lot careful trying to mod their phones now.
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
sabooher said:
Either Samsung is being completely ignorant to this issue or they have the worst quality control. I am beginning to think it's both. Simply google searching brings up lots of results on this issue.
My first Vibrant (USB port eventually broke) 3 button recovery worked fine; dated July 15. The replacement after that did not work, nor did the one after that. Those were both made on Aug 16. I finally got a refund under buyer's remorse and waited another week. Got my fourth Vibrant today, made 09/01 and yes it does work with 3 button recovery.
Keep in mind none of my Vibrants were refurbished units. They were all brand new. I think Samsung has a serious flaw on their hands. I'm concerned about keeping this phone even but I added the insurance on it just in case.
Click to expand...
Click to collapse
I think that's the first phone dated after 08/** that i've heard of actually having the 3 btn modes work. My bf has a vibrant and I've been holding off purchasing one myself since hearing about the hardware locked ones. i've been literally scouring ebay for a phone that was a part of the July batch.
well, this gives me a little hope.
Oniyuri said:
By "hardware locked" they mean that you cannot access the phone's recovery or dl mode using the 3 button method.
this has apparently started with the 08/**/2010 batches. beforehand this phone was deemed "unbrickable" but it's now actually possible with the newer shipments so ppl have got to be a lot careful trying to mod their phones now.
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
Click to expand...
Click to collapse
Well just my 2 cents on the topic, entering recovery mode required following strict steps, miss 1 single step, and you won't get into recovery.
now as far as download mode goes, I have been able to get into it once. This was by accident, I was randomly doing various sequences of volume rocker and power, it went into download mode. Now since then, I have no clue what sequence I used, but I have never been able to get into download mode ever again.
Additionally, my phone is dated 7/2010, so the 8/2010 batch theory doesn't hold since I can not get into download mode either now.
To get into Recovery Mode, follow these steps.
Okay, I'm reading lots of people having trouble getting into recovery mode, thinking their phone is broken or busted. Chances are you are not holding down the power button log enough, or you are letting go of something too quick.
FOLLOW THESE DIRECTIONS STEP BY STEP.
1) START with your phone off
2) Press volume up AND volume down at same time, keep them pressed in the entire time, do NOT let go. I prefer to hold my phone in landscape, this gives me better control with my fingers.
3) WHILE holding down volume up and volume down, press and hold power button, DO NOT LET GO OF ANYTHING. You should be holding down volume up, volume down, and power, DON'T LET GO! HOLD ON... and proceed to next steps, dont let go!
4) PHONE will start, you will see the white Vibrant logo. STILL DON'T LET GO, volume down, volume up, and power all pressed.
5) White Vibrant logo disappears, still dont let go!
6) White Vibrant logo re-appears again for the second time. Right when you see the white vibrant logo pop up a second time, let go of ONLY the power button, keep holding down volume down and volume up.
7) Phone enters recovery mode, you can let go the volume rocker.
hope this helps, it worked for me, hopefully it works for you also.
now can someone post sure fire method into getting into download without needing to connect the phone to your computer and using odin?
Oniyuri said:
I think that's the first phone dated after 08/** that i've heard of actually having the 3 btn modes work. My bf has a vibrant and I've been holding off purchasing one myself since hearing about the hardware locked ones. i've been literally scouring ebay for a phone that was a part of the July batch.
well, this gives me a little hope.
Click to expand...
Click to collapse
Hate to break it to you, my phone is made in July, and it WILL NOT go into download mode, I do however get into recovery mode.
That phone date batch theory doesn't hold true, so you can stop searching for july phones.
Oniyuri said:
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.[/QUOTE]
where did you read this, please provide the link
Click to expand...
Click to collapse
Samsung Mobile USA support is worthless. I called three times and finally got someone in "premier support" who didn't know anything. He actually went as far as to tell me a simple data wipe would resolve this problem, ha! I then got a hold of someone at Samsung Telecom corporate office who said he'd look into it and never called me back. No surprise there either. I think it's kind of sad that people are having to resort to Facebook wall comments to get a company to start backing it's products.
Thanks to sabooher, I was able to get into download mode with no problems, I hope this works for you, and thank you again sabooher.
okay, start off with your phone turned off
hold down both volume down and volume up at the same time, do not touch the power button
now, get your usb cable, have one end into your computer, the other end put into your vibrant, while you are still holding down the volume up and volume down at same time. dont touch power button
your phone hopefully will now go into download mode!
SamsungVibrant said:
FOLLOW THESE DIRECTIONS STEP BY STEP.
Click to expand...
Click to collapse
Nope, no good.
jonathan3579 said:
Here's my advice in a step-by-step:
Click to expand...
Click to collapse
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
SamsungVibrant said:
Oniyuri said:
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
Click to expand...
Click to collapse
where did you read this, please provide the link
Click to expand...
Click to collapse
Sure, it's all over their facebook page. I've read tons of android sites so I can't quote the site that led me to this page but I've been following the Samsung Mobile Canada FB page over the last few days about it. Suffice it to say: the Bell customers are really not pleased with the 3 btn issue: Samsung Mobile Canada
FenixGryph said:
Nope, no good.
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
Click to expand...
Click to collapse
maybe you don't have the correct drivers installed, try the ones from this thread --> http://forum.xda-developers.com/showthread.php?t=728929
Well here's my take on things. I got my phone (July 11th build date) directly from T-Mobile corporate. Came via FEDEX on launch day. Long story, suffice to say I had Behold II and complained to the right people at the right time and got swapped a Vibrant to basically shut me up.
Entering download mode seems to be very timing specific even for this original batch phone. There is only one way I can reliably get download mode 100% of the time...
- Pull battery
- plug in to USB cable connected to PC
- hold down VOL DOWN + VOL UP (DO NOT HOLD DOWN POWER)
- Insert battery
Alternately I can get into download mode using VOL DOWN+ VOL UP + POWER, but I have to be very careful to catch the right moment after the Vibrant logo appears the 2nd time to release power to get download mode.
When I ODIN, I use the first method always now.
masterotaku said:
Entering download mode seems to be very timing specific even for this original batch phone. There is only one way I can reliably get download mode 100% of the time...
- Pull battery
- plug in to USB cable connected to PC
- hold down VOL DOWN + VOL UP (DO NOT HOLD DOWN POWER)
- Insert battery
Alternately I can get into download mode using VOL DOWN+ VOL UP + POWER, but I have to be very careful to catch the right moment after the Vibrant logo appears the 2nd time to release power to get download mode.
When I ODIN, I use the first method always now.
Click to expand...
Click to collapse
That's odd. I've never had a problem getting into download mode; in fact, I was confused the first time it happened cuz I didn't mean to! All I have to do is make sure the USB cable is plugged in and then hold all 3 buttons when I turn it on and into download mode it goes.
crazycaveman said:
That's odd. I've never had a problem getting into download mode; in fact, I was confused the first time it happened cuz I didn't mean to! All I have to do is make sure the USB cable is plugged in and then hold all 3 buttons when I turn it on and into download mode it goes.
Click to expand...
Click to collapse
I tend to have bad luck with Odin too. I've seen the "ohsh*t" icon many times...
(note: the "ohsh*t" icon is what I call the phone/caution symbol/pc icon I tend to see quite often)
When that happens the ONLY way I can get back to download mode is the battery-insert method.
FenixGryph said:
Nope, no good.
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
Click to expand...
Click to collapse
It definitely sounds like you don't have the correct drivers installed. My drivers were downloaded through the installation of Kies, however, is your computer online while you are attempting this? I can only speak for my computer which is running Windows 7, but it automatically downloads any updated/new drivers necessary when connected online.
woot!
Ha ha!! The drivers were the problem. I was under the impression I only had to install the samsung drivers if I was on a 64 bit system.
I'm looking at my recovery menu now and am very happy! Wish I had time to do the stuff I wanted to do the vibrant before work, but I gotta make a couple of bucks before I get this guy set up just how I want.
See? I knew XDA was the place to be. Many thanks Oniyuri and jonathan3579!
My touchpad has been getting crazy force closes within just starting up, I can't do anything I installed gapps, and now nothing works, not even moboot. I have tried webOS doctor to no avail. wtf am I supposed to do with my brick now?
Garrett07 said:
My touchpad has been getting crazy force closes within just starting up, I can't do anything I installed gapps, and now nothing works, not even moboot. I have tried webOS doctor to no avail. wtf am I supposed to do with my brick now?
Click to expand...
Click to collapse
can you boot into recovery at least?
Mine died also. It is like the battery is completely dead but I charged it overnight. Cannot put in usb mode or anything. Even plugging it into a pc does nothing .
I held the power and center buttton for 15 seconds and the screen came on saying I needed to plug it in.. charging it again now. But might be all right...
Sent from my YP-G70 using xda premium
duglas said:
Mine died also. It is like the battery is completely dead but I charged it overnight. Cannot put in usb mode or anything. Even plugging it into a pc does nothing ....
Think cm7 killed my touchpad also..
Sent from my YP-G70 using xda premium
Click to expand...
Click to collapse
Have you tried long pressing HOME + POWER?
have you tried WebOS Doctor to restore back to stock?
I would recommend you hard power it off by power and center buttton for 15 seconds.
Make sure you have charged it
Then Run the webOSdoctor program.
For me I rebooted the tablet and held the volume up button until the USB symbol popped on the screen...then the WEBOS Doctor found the tablet and we where on the road to recovery.
Give it a shot and let us know if you got any love. You won't be the first or the last to get this issue.
I also had the black screen. Had to do the pwr + home to get it back. It may be because it was on really low power when I left it on my Touchstone. Oddly enough it was fully charged when I got it to turn on.
hydrogenman said:
can you boot into recovery at least?
Click to expand...
Click to collapse
Yeah I got it all the way back to where moboot is off and webOS is the only thing running but if i just install cwm and cm7 i still get the force closes from gapps, I've even tried wiping data cache and dalvik from cwm but it was a no go.
Further proof not one person read the notes with release...
It's not intended for use by the general public. The fact you are having these issues shows it's not for you...
So read the docs, uninstall it, and use webOS. Learn to read the documents at least 3 times too... I had to install without pages of guides... Had zero issues despite my touchpad being a mess of partitions... You people are blessed with a guide, yet can't even manage it.
I can't switch on my HP Touchpad ! Mine don't respond to power and to reset neither (power + home + volume up).. Have you got any idea ? She's got batery and is plugged on sector !
pulser_g2 said:
Further proof not one person read the notes with release...
It's not intended for use by the general public. The fact you are having these issues shows it's not for you...
So read the docs, uninstall it, and use webOS. Learn to read the documents at least 3 times too... I had to install without pages of guides... Had zero issues despite my touchpad being a mess of partitions... You people are blessed with a guide, yet can't even manage it.
Click to expand...
Click to collapse
Dude I got it to boot. Its obviously one of the many bugs, I had it working fine until gapps installed, you're not so high and mighty that you can tell other people what the deal is so come off it.
pulser_g2 said:
Further proof not one person read the notes with release...
It's not intended for use by the general public. The fact you are having these issues shows it's not for you...
So read the docs, uninstall it, and use webOS. Learn to read the documents at least 3 times too... I had to install without pages of guides... Had zero issues despite my touchpad being a mess of partitions... You people are blessed with a guide, yet can't even manage it.
Click to expand...
Click to collapse
Good job, you got yours to work just like thousands of us did. But this is a alpha release and there is bound to be some bugs that people are going to encounter. If your really a "developer" Im sure you have messed up devices too before. Dont be such a queen douche about it.
lancelot54 said:
I can't switch on my HP Touchpad ! Mine don't respond to power and to reset neither (power + home + volume up).. Have you got any idea ? She's got batery and is plugged on sector !
Click to expand...
Click to collapse
Just hold down the power button and the middle button until the hp logo comes up, might take 15 seconds or longer, i woke up with both my touchpads off and unresponsive, after doing the above they are both on and fully charged.
friken amen
pulser_g2 said:
Further proof not one person read the notes with release...
It's not intended for use by the general public. The fact you are having these issues shows it's not for you...
So read the docs, uninstall it, and use webOS. Learn to read the documents at least 3 times too... I had to install without pages of guides... Had zero issues despite my touchpad being a mess of partitions... You people are blessed with a guide, yet can't even manage it.
Click to expand...
Click to collapse
You're so right dude, I pretty much know what I'm doing and even I got a bit freaked when I got the black screen but I read the docs and went to the issues log to find he answer just like it says. This is an alpha release, albeit an absolute triumph in itself, and improvements will come.
Check the issues log peeps before clogging up the forums, the last few threads here are all answered or logged at least.
If you don't understand the instructions you shouldn't be following them! No offence to Garret though, I'm sure his is a real issue.
Garrett07 said:
Dude I got it to boot. Its obviously one of the many bugs, I had it working fine until gapps installed, you're not so high and mighty that you can tell other people what the deal is so come off it.
Click to expand...
Click to collapse
theusername said:
Good job, you got yours to work just like thousands of us did. But this is a alpha release and there is bound to be some bugs that people are going to encounter. If your really a "developer" Im sure you have messed up devices too before. Dont be such a queen douche about it.
Click to expand...
Click to collapse
Hahahahahahaha.....this is some funny stuff. You don't even know your *****ing about. Is pulser a "developer"?! That is too rich.
Question...
if you turn it off... (hold down the power + the home button for ~ 20 seconds)... then volume up and power do you get the USB symbol on the screen? If it's still not responding at all, try pluging it into the wall with your power brick for 5-10 minutes then try again...
If you can get the usb symbol, it's not bricked...
It may not be happy, but it's not bricked.
If you feel excitable... you can google for instructions on how to recover from precentral... ('cause you'll likely need to get your hands dirty and play with lvm via novacom to fix it)
You could try calling HP, but remember you chose to void your warranty when you loaded android...
Trickman2 said:
I would recommend you hard power it off by power and center buttton for 15 seconds.
Make sure you have charged it
Then Run the webOSdoctor program.
For me I rebooted the tablet and held the volume up button until the USB symbol popped on the screen...then the WEBOS Doctor found the tablet and we where on the road to recovery.
Give it a shot and let us know if you got any love. You won't be the first or the last to get this issue.
Click to expand...
Click to collapse
Worked for me after I nerfed one crucial part of the install.
I think I'll wait till its out of beta to give it a whirl. I hate that feeling of not knowing if I messed up. I've had that feeling too many times going way to the days of my g1.
I don't think its cool to blame cyanogenmod for something you did to your device.
I leave it booted into webos overnight just to make sure and I can also charge it with the touchstone as it doesn't seem to work in android :-(
Sent from my HTC Sensation Z710e using Tapatalk
All, I've gone through many of the forums here and all I am now is confused. Issue: Had CWM and NVFLASH on and Honeycomb on gtab. Some issues, wanted to go back to stock. Followed instructions; however, now it's in a loop. I cannot get to it via PC. Holding power and volume key, see the 3 birds and "recovery key detected, goes to gtablet screen, goes to screen with a box (arrow in it pointing down) and status bar across bottom, goes to w/tap n tap screen, goes to screen with tnt; then reboots through the process again and again. I've spent the past two weeks going through the internet and reading the various methods to unbrick, none work; because I can't get to the internal SD card.
Is there a way to fix this? Is there a way to use the external micro-SD card? Or do I just need to throw this thing away? Any assistance would be appreciated. Oh, I've tried the Code Red and every other unbricking method I came across.
Thank you in advance, Michael
[email protected]
Since you are only experiencing a cycled boot loop then you are not bricked. There is still hope.
What NVflash file did you use to get back to stock?
Which bootloader do you want to run?
http://viewsonic-gtablet-for-dummie...268582d53a1&fw_sig_social=1&fb_sig_network=fw
This website helped me out allot when I was in a jam.
nobe1976 said:
Since you are only experiencing a cycled boot loop then you are not bricked. There is still hope.
What NVflash file did you use to get back to stock?
Which bootloader do you want to run?
http://viewsonic-gtablet-for-dummie...268582d53a1&fw_sig_social=1&fb_sig_network=fw
This website helped me out allot when I was in a jam.
Click to expand...
Click to collapse
I grabbed the latest one. Basically, I'm almost at the "throw it in the trash" stage. If there is a way to boot from the external SD card to load the stock 1.1 version; that's what I would like to do and give this to my niece. Thank you for replying.
Michael
There is a way to "install clockwork from external SD" - search that phrase and you should find it.
BTW- If you plan on trashing it, I'll pay for shipping to my house. I'll 'throw it away' for you
new_to-droid said:
I grabbed the latest one. Basically, I'm almost at the "throw it in the trash" stage. If there is a way to boot from the external SD card to load the stock 1.1 version; that's what I would like to do and give this to my niece. Thank you for replying.
Michael
Click to expand...
Click to collapse
Well all and all I know your fustration. The first link I beleive you are using is the Stock 1.1 from the 3588 branch. That one I used before and had nothing but issues. The best one to use is from the 4349 branch perfered with CWM pre-installed. After flashing that file shut the Tablet off during boot up. Then boot into recovery mode by holding down the volume + while pressing the power button. Do a Wipe Data Factory reset, Clear Cache, and then under advance Wipe Dalvic Cache then go back to main menu of CWM and reboot device. Make sure you don't select reboot recovery since that will not let you boot into anything but CWM. TNT TabUI will then boot up and you chould be good to go.
Thanks...but
Thanks to everyone. I still can't get this darn thing to connect to the PC or CWM to run. I would love to be able to just put it back to stock and be done with it. The more I work with Android devices, the more I'm convinced that I will stick with Windows or Apple. Android is great, but until there is a one size fits all solution; the tweaking and manipulation one has to do just to increase the functionality is what will be Android's downfall. Nothing is "simple" with Android and unless you're a programmer; there isn't much one can do with it. Partially it is the manufacturer's fault (i.e. Viewsonic) for putting out crap that doesn't even work; part of it is Google for not requiring standards for Android (yeah, no standards are great because one can explore/tweak/etc); and it is my fault (for this instance) for thinking that I could tweak and enhance my system. So, I'll put this thing up on Craigslist and see if I can make some change with it and get a newer device or just stick with a laptop and be done with it. Thanks again everyone for all your help.
$$Price?
Sent from my Droid using XDA
new_to-droid said:
Thanks to everyone. I still can't get this darn thing to connect to the PC or CWM to run. I would love to be able to just put it back to stock and be done with it. The more I work with Android devices, the more I'm convinced that I will stick with Windows or Apple. Android is great, but until there is a one size fits all solution; the tweaking and manipulation one has to do just to increase the functionality is what will be Android's downfall. Nothing is "simple" with Android and unless you're a programmer; there isn't much one can do with it. Partially it is the manufacturer's fault (i.e. Viewsonic) for putting out crap that doesn't even work; part of it is Google for not requiring standards for Android (yeah, no standards are great because one can explore/tweak/etc); and it is my fault (for this instance) for thinking that I could tweak and enhance my system. So, I'll put this thing up on Craigslist and see if I can make some change with it and get a newer device or just stick with a laptop and be done with it. Thanks again everyone for all your help.
Click to expand...
Click to collapse
Sorry to see that your experience with your newly found failure did not come with a price of knowledge. Truth be sayed I am no programmer, geek or knowledge of script writing either, but what I can pass along to all new-to-android persons is that your best path is to read and follow instructions to the T or you will end up with a expensive paper wait. The web link I posted above is pretty self explained and I give that man credit because I was a newbie too once. Then somewhere in these forums I found that website and was able to recover from just about anything that happened to my poor Gtab. Hell, I even had to drill a hole in the back of the case just because I wanted more and there was ICS from Team DRH. But truth be said that web link is your path and only path to going back to the stock UI and recovery.
Price
50 plus shipping to us only
new_to-droid said:
50 plus shipping to us only
Click to expand...
Click to collapse
I'll buy it. DIBS EVERYONE!
PM me with your info and I'll have the money sent right away.
Even if I couldn't get it to work, I could use it for parts for my current g-tab.
EDIT: Don't mind my post count. I'm very active on SD, just not here.
Just wanted to mention that I have not been PM'd or replied to. Hope this guy got his tab to work.
All,
I have to say thanks for the help in advance, well I'm in the military and I have never done anything to my G-tablet. All I used it for was to OOVOO and talk with my kids when I am in the DESERT Guys over there are always doing crazy stuff to theirs and crazy stuff always happens to them, some good some bad. :cyclops: Well here it goes my brother-in-law took my tablet without my knowledge and decided he would upgrade me to a better system :crying::crying::crying::crying: well he killed it!!!!!!! and I leave to go back to the desert in a week or so. He says something must of been wrong with it before he touched it, yeah likely story!!! it worked fine when I used it last. I have to say I have little knowledge on how to do things to this tablet IE rooting roms and all of that stuff, not saying I'm not willing to learn just very dumb when it comes to doing it. I'm one of those give it to me step by step by step
So this is what I have done so far
1. I plug it in to my Computer Windows Vista Home premium 64 bit system and it does not recognize it.
2. I opened it up and have disconnected the internal battery cord and plugged it back in still no life
3. I pressed the little white button and no reset happened
4. Held down the power button and down sound button and (3 birds ViewSonic - Detect a recovery key pressed - Booting recovery kernel image) popped up then nothing it just sits like that.
5. I have also let the battery completely drain to zero then charge it back up and still nothing.
Please help me and I'm sorry if I've been rambling on but talking to my kids when I'm deployed is the only thing I look forward to doing when I'm in the desert, Once again I would like to thank the smart guys on this forum for helping us not sooooo smart ones with our problems.
desert G-TABLET said:
All,
I have to say thanks for the help in advance, well I'm in the military and I have never done anything to my G-tablet. All I used it for was to OOVOO and talk with my kids when I am in the DESERT Guys over there are always doing crazy stuff to theirs and crazy stuff always happens to them, some good some bad. :cyclops: Well here it goes my brother-in-law took my tablet without my knowledge and decided he would upgrade me to a better system :crying::crying::crying::crying: well he killed it!!!!!!! and I leave to go back to the desert in a week or so. He says something must of been wrong with it before he touched it, yeah likely story!!! it worked fine when I used it last. I have to say I have little knowledge on how to do things to this tablet IE rooting roms and all of that stuff, not saying I'm not willing to learn just very dumb when it comes to doing it. I'm one of those give it to me step by step by step
So this is what I have done so far
1. I plug it in to my Computer Windows Vista Home premium 64 bit system and it does not recognize it.
2. I opened it up and have disconnected the internal battery cord and plugged it back in still no life
3. I pressed the little white button and no reset happened
4. Held down the power button and down sound button and (3 birds ViewSonic - Detect a recovery key pressed - Booting recovery kernel image) popped up then nothing it just sits like that.
5. I have also let the battery completely drain to zero then charge it back up and still nothing.
Please help me and I'm sorry if I've been rambling on but talking to my kids when I'm deployed is the only thing I look forward to doing when I'm in the desert, Once again I would like to thank the smart guys on this forum for helping us not sooooo smart ones with our problems.
Click to expand...
Click to collapse
1.- Try other windows version, works fine on Windows 7 x32 / x64 - tested my self
3.- wich white reset button? i never saw it !
4.- You tried POWER+VOLUME (+)? - POWER+VOLUME(-)?(this its for nvflash as far i know, im also a begginer)
Your tab is not dead, but it is not properly flashed either. If you hold power and Vol UP and it shows booting recovery but doesnt boot it, then there is a bad recovery flashed, or none at all. To fix this, you will have to NVFLASH a recovery/OS on it. There are better than stock OS's but since you need it for webchating with family I would suggest Frankentab.
Download this file:
http://teamdrh.com/DRH-Downloads/Full_Stock_NVFlash_CWM_5504_Touch.zip
Then extract it somewhere you can find it.
Using a usb Male to usb mini cable, the one that came with your tablet, plug your tab into your computer (tab turned off)
Hold down the VOL DOWN button and press power button and hold it too. The three birds should pop up, then go away, black screen.
After black screen, computer will say found new hardware. You must manually choose the drivers needed, and their location will be in a folder titled "flash usb drivers" and it is inside the folder you downloaded and extracted.
After the drivers are installed, without turning anything off, run the file nvflash_gtablet.bat which is inside the extracted folder you downloaded. This will take a while, but once it is done, you can turn off and turn back on your tablet. After a few minutes, it should completely boot back into a stock ROM.
If you are cool with this, then you are done. If you would like to run something MUCH FASTER then let me know when you get to this point and I will show you how to accomplish this. If you run into any problems report back and I or someone will help.
Just had this problem on a new (well refurbished) gTab I got during black Friday. Works great and is not hard to fix the issue once in APX. hardest part was getting the drivers installed (running win 7 x64).
I had to go to the CWM page to download the correct version of the recovery, the version listed in the guide is outdated, or not listed that it is for 1.1 only and not 1.2.
Seems like a great tablet, can't wait to get using it. Thanks!
camman85 said:
Just had this problem on a new (well refurbished) gTab I got during black Friday. Works great and is not hard to fix the issue once in APX. hardest part was getting the drivers installed (running win 7 x64).
I had to go to the CWM page to download the correct version of the recovery, the version listed in the guide is outdated, or not listed that it is for 1.1 only and not 1.2.
Seems like a great tablet, can't wait to get using it. Thanks!
Click to expand...
Click to collapse
do you remember where you downloaded the right recovery version for windows 7 ?
Before I explain my problem, let me first say that I am a novice when it comes to modifying phones. Shortly after buying my Razr, I knew that I wanted to root my phone, but I didn't know how. I found a program (that I can't recall now) rooted it, and had no problems. My problem came when I wanted to accept the OTA upgrade. I tried using Voodoo to keep my root while I accepted the OTA update, but that's where things when wrong. I don't know everything that went wrong because it seemed like nothing that I was doing was having any effect. It was having an effect, but not the effect that I wanted. After some uneducated decisions on my part, I found my Razr stuck in a bootloop. After trying to "fix" things, I gave up on it, but I decided to hold onto the phone. I replaced it with an HTC Rezound and moved on. I chose the Rezound only because it wouldn't take long to get it and it was affordable.
Last week, I decided that using the Rezound (it's definitely not all bad) has made me want to revive the Razr. I ordered BlackHat's adapter and used MattLGroff's utility (http://forum.xda-developers.com/showthread.php?t=2192467) to wipe my phone and flash JB.
This worked, with two exceptions. First, the phone still wouldn't charge. I came across a forum post that talked about successfully charging a phone in the car when it wouldn't charge inside with a computer or wall outlet. I was skeptical, but it worked. After charging the phone in the car, I can now charge it inside with a computer or wall outlet.
The second problem remains, and I am wondering if something that I did to soft-brick the phone caused a hardware problem. That seems unlikely, but I am new to this, so anything's possible as far as I'm concerned. In the attached picture, you can see that the bottom third of the screen shows up almost like static on a TV, but it's broken down into a grid. Also, the right half of the screen shifts up almost the height of the screen. Both of these problems come and go, but the "static" at the bottom of the screen comes much more often. I have to navigate through folders and menus before the shifting problem happens. Regardless, if I am at the home screen, for example, and I shift right or left (or navigate anywhere for that matter), the screen will be clean with no errors for a moment. After a second or so, the glitches usually show up.
I almost forgot about the last issue. When I wake the screen, it's quick and responsive; however, when I turn off the screen (by tapping on the power button), there is a lot of lag in the animation. Normally it would be a quick and smooth transition to the thin, horizontal line, and then it would quickly disappear. Now I can watch as it slowly blurs and stretches. It works, but it lags. This happens every time I turn off the screen.
Does anyone know what could cause this? Am I beyond repair? After typing this out, I doubt that it's a hardware problem, mainly because the static and shifting are not constant. But again, I'm totally new to this.
If anyone has any suggestions that involve utilities, then it would be ideal if I can use Linux. I have access to a Windows computer, but not at home.
Thanks in advance to anyone who can offer some insight.
Does anyone have any insight into this? Two months later and I'm still stumped. It doesn't matter how I use MattLGroff's utility...the same issues are still present. Could I maybe use a utility that will revert me to an older system? That way, I might be able to receive an OTA upgrade to JB.
I'm grateful for ANY input...
Thanks!
Just try to update through rsdlite, search for fastboot files here in development or google it and find the right one for your region.
Sent from my XT910 using xda premium
AztekSoul said:
Just try to update through rsdlite, search for fastboot files here in development or google it and find the right one for your region.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Thanks for the response, AztekSoul. I would have responded sooner, but I've been pretty busy.
I run into some trouble when I try your suggestion. I've downloaded RSDLite, and I run it through Wine. I am able to load the XML file that comes with build 6.7.2-180_DHD-16_M4-31/Blur_Version.6.16.211.XT912.Verizon.en.US (found here: http sbf DOT droid-developers DOG org/cdma_spyder/list DOT php).
My problem is that RSDLite won't show my device. I've tried clicking "Show Device" when booted into AP Fastboot and when booted regularly. I've tried plugging in the phone with Team Black Hat's factory adaptor (found here: http shop DOT teamblackhat DOT info/Factory-Adapters-motadapt DOT htm) and plugged in with just the USB cable that came with the phone.
It seems like nothing I do will get me any further. I also tried to enter Recovery mode, but I get the lying down android and the red triangle with the exclamation mark.
If you have any further ideas, I'd be grateful to see them. Thanks!
BTW, sorry about the URLs. I can't post links because I haven't submitted at least 10 posts to the forum.
neffje said:
Thanks for the response, AztekSoul. I would have responded sooner, but I've been pretty busy.
I run into some trouble when I try your suggestion. I've downloaded RSDLite, and I run it through Wine. I am able to load the XML file that comes with build 6.7.2-180_DHD-16_M4-31/Blur_Version.6.16.211.XT912.Verizon.en.US (found here: http sbf DOT droid-developers DOG org/cdma_spyder/list DOT php).
My problem is that RSDLite won't show my device. I've tried clicking "Show Device" when booted into AP Fastboot and when booted regularly. I've tried plugging in the phone with Team Black Hat's factory adaptor (found here: http shop DOT teamblackhat DOT info/Factory-Adapters-motadapt DOT htm) and plugged in with just the USB cable that came with the phone.
It seems like nothing I do will get me any further. I also tried to enter Recovery mode, but I get the lying down android and the red triangle with the exclamation mark.
If you have any further ideas, I'd be grateful to see them. Thanks!
BTW, sorry about the URLs. I can't post links because I haven't submitted at least 10 posts to the forum.
Click to expand...
Click to collapse
hi,i had the same bug with rds lite didn't show me the spec of the phone,but only --------.
try anyway and remember to have the motorola driver in the pc (i don't know if works with wine,i had try only i my other windows pc)