Related
I recently bought a viewsonic g tablet off of ebay. The tablet is pre loaded with vegan tab ginger edition. When I recieved the tablet I turned it on it loaded a few screens then came to the vegan tab screen. It shows up then goes black then comes up vegan tab again. It continues to do that and never boots up. Any suggestions on what to do? Should I return it or can it be fixed reletively easy?
Thanks,
Dan
Hold down volume + when you power it up, that will get you into recovery. Then use the volume +or- button to navigate to factory reset (or wipe data ) then press the home button. Once that finishes go to reboot (the option at the top of the list) and press home key.
Oh, if you can't get it to power off, holding the power button in for 30 seconds will hard shutdown the device.
I tried the reformat or wipe data and it is still doing the same thing any other suggestions. THis is very frustrating because this is the first day I have had the tablet and it will not work.
Thanks
Do you try to do factory reset from recovery mode?
Yes I tried factory reset from recovery mode but I looked around and found the fix and I had to repartition the sd card to 2048 and 0 and that worked perfect. Thanks for all the help.
dhoff024 said:
Yes I tried factory reset from recovery mode but I looked around and found the fix and I had to repartition the sd card to 2048 and 0 and that worked perfect. Thanks for all the help.
Click to expand...
Click to collapse
Awesome, that is always the next step. Wish I could have gotten back to you earlier with a response but its good to see you got it figured out. Did you end up sticking with vegan Ginger or flashing something ddifferent?
Well this is the first time i have ever messed with software other than stock i had an archos 70 internet tablet and i liked it but they had an update that caused lots of issues so i sold it and bought the g tablet i like the tablet so far but there are a few things i dont like like the keyboard and i have been having an issue where the browser just shuts down and goes to the homescreen. Overall i am happy with the tablet but im not sure if ilike vegan tab if there is any you would reccomend and how to get them i would appreciate it. Also this came with vegan tab is stock any good what would you reccomend to use im new to this tablet so the help is appreciated.
If you like the feel of vegan Ginger I would recommended trying cyanogen mod 7. You can find the link stickyd at the top of the general forum. If you want super stability and speed I would recommended clemsyn+calculins combo in the development forum. It gives a closer to stock feel with all the tweeks and a built in add blocker that makes surfing the web a dream.
bonuses to right now to cm7:
you can mod one file and get it to run Netflix.
It doesn't randomly shut off the tab when its in extended sleep like other Rome.
Bonuses to Clem+calkulins combo:
Full video drivers for hardware and software support making watching downloaded movies better.
Super fast and responsive, there is not one bit of sluggish in it.
No matter what your using, I would recommended using the newest dolphin browser. It is amazing and has tweaks specifically for tablets.
Good luck
dhoff024 said:
Yes I tried factory reset from recovery mode but I looked around and found the fix and I had to repartition the sd card to 2048 and 0 and that worked perfect. Thanks for all the help.
Click to expand...
Click to collapse
I just got the G Tab... and having the same issues. Could you provide some documentation on the "Fix" you did to resolve the boot issue?
Does anyone else experience this with the new leaked 2.3.4 HKTW build? Or is it just my Atrix?
Yeah I exp. It as well but I notice my screen becomes in responsive and so do the touch keys. Only the power button and volume rocker work.
I've only experienced this while on a phone call though to be honest. Like when I'm on hold and I'm.checking Facebook or I'm looking something up on the web while on a call. But I definitely think it's a bug in hktw build 2.3.4 cause I beverage had a problem before with it.
I tried looking through the forums and haven't seen any other complaints untilled this one so maybe its just a few of us. Can any one else confirm this or is there a fix some where?
Sent from my unlocked//rooted ATRIX
mine works fine...
Happens to mine all the time. Fixes itself after turning the screen off.
d3athsd00r said:
Happens to mine all the time. Fixes itself after turning the screen off.
Click to expand...
Click to collapse
when mine freezes even locking phone with the power button and waiting a few seconds to turn it back on doesn't help it still stays un-responsive at the lock screen. I'm actually noticing it happening more and more frequent. or I'm just multi tasking more and more frequent lol idk cant wait for a USA build as apposed to this HKTW build but hey i got to say its definitely pulling me through this month of waiting for it ;P
Mine happened a few times a few days ago...then once the day after, and not since. Been like 4 days now.
i've a cyanogen 7 in my wildfire, and start happens and i dont know why, i've this rom from 3 months and never heard such a thing, hope some one can help fix this.
I've have done a hard reset and nothing
Mine did that already in 2.2 , back then the fix was to lock and unlock the screen. That would always fix the issue, at least until next time. Now in 2.3.4, it still happens, but if I wait 15-20 seconds it usually fixes itself. Looks like Motorola applied some fixes but didn't fix the issue completely.
Bell ATRIX Gobstopper 2.3.4
well guys, i solve the problem for now....
solution:
1º make sure that you have a backup prior to the problem (original stock or other thing), if not you might have to install the room from set one.
2º retrieve you sd card, make a backup of some things that you dont want to lose (like pictures, ring tones, mp3 etc) and leave a folder with a backup that you have, next format sd card in fat32 and put the things that you save (note, dont do all the backup of sd card, like the folders with .com... and android folders etc)
3º go to clockworkmod recovery, by restarting to recovery, wipe all data, like the firs time you install the custom rom, now go to backup and restore and do restore to your backup.
4º Restart and voila, that works for me...i figure that was some app that might cause the problem,(thinking on ndrive 11) im going to test now, but it works.
cheers and post something that might help some one
Gingerbread Problem
I am the same problem everything was fine with Froyo once I updated to Gingerbread I had these issues. Also the droid and nexus folks are reporting those just google up gingerbread phone freeze. I have not found a fix yet. Thanks
Reaching to the XDA family to help me troubleshoot strange issues with my 10.1 WiFi Tab. Starting a couple of months back the tablet hold not come on once i was pressing the power button and I had to hard reboot to getting back on.
I assumed that it's the power management and I turned it off, but the problem persisted. The I could see that it started to hang at the Samsung animation screen with the sound blocking like a bad CD.
I've run a hard reset cleared cache but the problem still present. It's running stock 4.0.4, was never rooted or custom ROM on it since new.
I don't really know what to do next and I'm looking for pointers.
Thanks for any help.
yulasinio said:
Reaching to the XDA family to help me troubleshoot strange issues with my 10.1 WiFi Tab. Starting a couple of months back the tablet hold not come on once i was pressing the power button and I had to hard reboot to getting back on.
I assumed that it's the power management and I turned it off, but the problem persisted. The I could see that it started to hang at the Samsung animation screen with the sound blocking like a bad CD.
I've run a hard reset cleared cache but the problem still present. It's running stock 4.0.4, was never rooted or custom ROM on it since new.
I don't really know what to do next and I'm looking for pointers.
Thanks for any help.
Click to expand...
Click to collapse
If u have cleared ur sdcard ( wiped it clean ) and are still having these issues...it could be power button related...
I would look and make sure the power button is not sticking...then after that. Make sure you don't have anything corrupted on you're sdcard.
If none of this works....I would root and flash a newer tw based ROM..
Let me know if u need help..
Thanks for your response Gil81. When I performed the factory reset or wiped the scard clean. The button it's not sticky and it function properly.
I'm thinking it might be battery related but not sure.
Any good rom's that you recommend?
Sent from my Nexus 4 using Tapatalk
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
I have to same issue that just happened and same as the screenshot.
Same issue...
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
mikeinstlouis said:
Hi guys,
I hope that this is the proper forum, if not please direct me to the correct one.
I am currently using a Sprint Samsung Galaxy S6, non-rooted.
My problem started about 48 hours ago while I was voice dictating a test message.
I was doing my regular texting with the SwiftKey keyboard microphone (problem also replicates with the Samsung Keyboard as well) and the box at the bottom of the screen would not go away. I tried to X it out, hit the back button and the home button but nothing gets rid of it other than restarting the phone.
This all seemed to start happening after the Google App update.
I rolled back to the old version and it seemed to work fine. Last night, it updated itself again and problem was back.
I have included an image of what I am talking about.
If anyone has any suggestions, I would be very appreciative!
Thanks
Mikeinstlouis
Click to expand...
Click to collapse
Latest update have little bugs
Sent from my Nexus 5 using Tapatalk
I am also having this issue on my Galaxy S4.
---------- Post added at 02:56 PM ---------- Previous post was at 02:46 PM ----------
mrneoz81 said:
This is so freaking ridiculous! A Google update that does this crap?!
I too own a S6 Edge Verizon 128GB and I noticed a couple of things.
If you bring up text to speak and then power off your phone.. Once you come back... you have locked it (Until restart)
I tried the following...
1) Reset the Dalvik Cache .. No luck.
2) tried force closing TTS and samsung text to speech.. no go.
3) Uninstalling latest update to the high quality voice. .. No Go.
4) Tried holding both buttons at the Same Time... No go..
5) For quibs and giggles.. Held down the close "X" for 5 whole minutes.
********************************************
What I think is going on is a time out error in the code.
So how i am able to get around it RARELY is..
Bring it up with the microphone button
Say what I need to say then hit the X to close it as FAST AS I CAN!!
I know that with all of our phone hackers, crackers and experts that we can ALL reach a Fix on this.
Damn Google...
Click to expand...
Click to collapse
One way I found that I can close it is by opening the menu that has active apps, then going to RAM, next turn the phone on its side (<--- yes do that), then hit clear memory a few times. And done its gone.
Thanks! That worked on my Sprint S4! (restarting phone has also worked for me, but this is easier.)
After holding down Home button to open the menu that has active apps, the options were still covered by the text to speak box. So I had to FIRST turn phone on its side to make visible the pie chart icon on bottom left, THEN then going to RAM tab and hiting clear memory a few times. When I turned it back to portait orientation, the text to speak box was gone. Thanks!
This has been happening to me all day long. so frustrating. I am also not the tech savy one in the house and hubby is not around. So thanks for the quick answer to get rid of it until he can uninstall the new update. Thanks
What is the pie chart menu option? What is the RAM tab? And will just be a little easier for Google to fix this? Lol
same problem here
Galaxy S6, same problem, started last night (September 24, 2015) . I do know that some updates were performed last night, not sure what. How do I uninstall the update? Which one is it? Help! I use voice typing constantly, and my phone is a brick when this thing locks up. It covers all my buttons. "Restart" doesn't clear it, I have to totally power off and back on. Right now, I have disable my voice key on my keyboard so that I don't accidentally touch it while waiting for solution.
Me too - just started today after some updates yesterday.
Same here....has anyone responded with a fix yet??
THANKS!
Glad it's not just me and my Note 3, but where does google get off sending out this kind of crap? It's enough to drive me to a windows phone.
Having the same issue only way I can get ride of it is to turn off my phone
same issue on moto droid mini; have to turn off phone too! poor QA google!!!!!
Me too. Galaxy S4. Have to shut the phone down and restart it to resolve the issue.
Piece of crap
Note 4 same problem started on the 24th
Same issue, Note 4
Same issue, Samsung Note 4.
Yep me too Verizon Galaxy s6
Sent from my SM-G920V using Tapatalk
BE2026
The stock oxygen OS has a text message bug that apparently isnt fixed yet, so i thought id try a different rom.
I unlocked the bootloader, worked great.
Then i flashed TWRP and it worked great.
I then proceeded to try and flash DerpFest and when the ADB sideload (ACCORDING TO THE DIRECTIONS) was done, it is suppose to reboot into the new os. but I get nothing.
So Ive tried, a bunch of stuff. I tried using orangefox and it doesnt support SD cards and the sideload option just crashes. So then i try TWRP recovery instead of billies recovery and when i select the image to install in TWRP, and then 'swipe to flash' TWRP instantly resets. and nothing happens.
So then i tried the MSMdownloader tool and it will not recognize the phone at all. all adv and fastboot commands work great.
Can someone help me?
I tried switch A or B, and flashing both,
I tried to go back to stock and i cant even get that to work.
Help meh please, i just bought this phone and now i cant even use it
I also cannot get the MSMdownloader to work. it shows my phone on the list in EDL mode. but com port is empty. device id is empty. all the fields are empty and it just says waiting on device. nothing happens.
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
arda99 said:
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
everyone comes up as it should in the device manager. sad face....
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
SomeRandomGuy said:
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
Click to expand...
Click to collapse
OH wow it did. Thank you, the documentation for that side of MSMd is vague. So after trying like 3 different "qualcomm" drivers I finally got it to work! As in the stock android 10 is loaded and the phone is no longer bricked. However, when I try the same methods again to actually put a custom rom on this phone the same thing is still happening.
No matter what OS i try to flash, no matter what mode or slot, or what recovery 'program' i use like twrp or orange FOX, nothing seems to actually boot into an OS. it just loops into Fastbook.
Can anyone help me? I dont want to use oxygenOS
I had a somewhat similar experience in loading custom ROMs, and simply took to de-bloating the stock image (emphasis on de-google-services, de-OnePlusSpyware, and de-auto-OTA). Still not really happy, compiling AOSP source now to try to swap out some of the system APKs that annoy me for customized ones. If there are only a few things that sour you to OOS, maybe I (or others) can help cure those? Debloat and replace...
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
So the main reason for me not wanting to use Oxygen OS is because when initally setting up the phone, everything works great. for about 2 or 3 days. then for what ever reason i cannot receive text messages. If I factory reset the phone, or put my simcard into another telephone all of them come rushing in.
In the event of me factory reseting my phone, ill get text messages from 3 or 4 days ago.
and it always works. as soon as my friend is texting me and i dont recieve it, i just factory reset then boom its there.
I tried everything, different SMS apps, update this, android 11 that. it always did it to me, like clockwork. like the phone installs an update and breaks text messages. I tried contacting oneplus customer support but that shhit is a joke. they told me they are aware of multiple isolated incidents about this and that the only thing to do left is to send it in. I JUST BOUGHT THIS THINg, im not about to send my device away, right after paying for it. I paid you guys $400 just to NOT have a telephone for 8-16 weeks?
SomeRandomGuy said:
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
Click to expand...
Click to collapse
See thats the thing, Ive never gotten another room, to boot. at all. no splash screen, no bootlogo nothing. it always just goes back to fastboot. it never tries to boot an OS. i follow these billie instructions and nothing happens. its the same result. I have tried all the different versions in this forum. from pixel experience to derpfest. all work great, untill the very last step where they say side load rom/flash and then reboot. your new os should be booting! and it doesnt.
Wow, that's a new one for me. I wish I knew more about the internals (slowly learning) to help troubleshoot. I would GUESS that if you can change phones (e.g. you said you can put the sim in a new phone, and get a backup of messages delivered), that it isn't so much that the phone is dropping them as it is not getting them in the first place.
With no guarantees- this is a SWAG- have you checked your APN settings? Most definitely, these come through as part of a new registration (duh), and consequently can get messed up for $diety knows why later... but at least you may be able to get a known-good set of settings (post reset, post registration) to compare to after terrorists strike and you are no longer getting messages. It should be easy to add a new APN with the "right" settings and manually select it.
If it is something like that, odds are an alternative ROM would just do the same thing; I assume there's some kind of handshake standard for initialization of the carrier network. I'm on TMo and happy to share my settings, if it helps....?
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
arda99 said:
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
Click to expand...
Click to collapse
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
agentruley said:
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
Click to expand...
Click to collapse
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
I had to go through the setup process again. First time the DF just didn't catch. I read ADB sideload can be broken as **** sometimes.
arda99 said:
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
Click to expand...
Click to collapse
Sadly this has nothing to do with my problem. Installing newer/ using older versions do not change the behavior.
The phone breaks as soon as I go back to the "Google Assisnt" -Setting up your phone for the first time- wizard and instead of selecting "Remind me tomorrow" i select next, and then the following screen says "Installing updates" and then the telephone will no longer recieve text messages. Does anyone have any help?
Oneplus customer service is terrible and they told me to buy another device.
This is the last phone i will ever purchase from them