[Q] Need Assistance Please - G Tablet General

I'm like the ultimate newby. Bought new G-Tablet off E-Bay. Owner volunteered to put new OS on it, I took him up on offer. We decided on Vegan 5.1.
So I got my machine Sat, and started playing. Today I picked it up and it cycles between the Birds and the "Powered by G-Tabdevs" screen.
I know how to get to the ClorkworkMod Recovery screen.
Any ideas?
Tom

Newporttom said:
I'm like the ultimate newby. Bought new G-Tablet off E-Bay. Owner volunteered to put new OS on it, I took him up on offer. We decided on Vegan 5.1.
So I got my machine Sat, and started playing. Today I picked it up and it cycles between the Birds and the "Powered by G-Tabdevs" screen.
I know how to get to the ClorkworkMod Recovery screen.
Any ideas?
Tom
Click to expand...
Click to collapse
Boot into recovery and wipe data & cache.
If that doesn't work, you may want to read up on the install directions for vegan 5.1. It's a simple process and re-flashing might fix it.

Wiped cache - no difference
When I do factory reset I get a couple of messages that don't seem right
E:Can't mount /dev/block/mmcblk3p2
(Invalid argument)
Error mounting /data/!
Skipping format
Formatting SDEXT
No Apps2sd partition found. Skipping format of /sd.ext
Does a re-flash still seem like the way to go based on that?

http://forum.xda-developers.com/showthread.php?t=896395
Ignore the title....this is your fix

First of all you'll need to ensure that you have Clockwork Mod .8 installed as pointed out on Roebeet's thread (http://forum.xda-developers.com/showthread.php?t=842004) under caveats and issues. I had good luck running the fix that roebeet list here as well. (http://droidpirate.com/category/ablets/viewsonic-gtablet/)
Your best bet is to continue reading up on the development forum and you will get up to speed really quick. I am very technically savy, but tablets are a whole new animal. Once you understand them it isn't that difficult.

http://forum.xda-developers.com/showthread.php?t=865245
Sometimes it helps to retrace your steps. Do what thebadfrog says and then start at the top of this link and end where it stops. Good luck.

OK, I did badfrogs trick and I'm in. Just have to set up my stuff again. I promise to check out rtreiders links.
I certainly appreciate the assistance.
Does this sound like operator error like me not unmounting when attached vis USB?
Tom

nope....it happens to everyone eventually. Somehow the partitioning gets corrupted

Related

Version 4.2.5 upgrade failed, need help recovering.

Cyanogenmod version 4.2.3 then 4.2.4 were running great on my G1 for a couple of weeks. Recently, I noticed the Cyanogenmod Updater saying the 4.2.5 stable was available. I went ahead downloaded it, did a Nandroid backup and then flashed it. However, on reboot, the Android splash screen kept freezing then trying the reboot. I could not get past this screen. I tried reflashing a couple of times with the same frozen results.
I did a factory reset. I can fully reboot, but now it appears I have regressed back to Kernel version 2.6.29. I also, don't think I have root anymore since I tried to sudo on terminal and it told me I don't have permission. What happened?
When I go to recovery mode, (pwr + home) I get a triangle with an exclamation point. I get the "E:Can't open /cache/recovery/command" I only have four options: reboot system, apply sdcard:update.zip, wipe data/factory reset, wipe cache partition.
I'm guessing that Apps to SD is not working because I might have some vanilla recovery image taking over that is not Cyanogenmod so it does not see the cache on the SDCard partition that I have.
I also noticed that I can get the "Fastboot" screen if I do the Pwr + Camera btn. I've seen posts that I should be able to get everything back that way, using but I haven't found a step-by-step on how to use if for noobs.
Can anyone suggest how I can get back everything? I still have all my data including backup files and apps on the sdcard.
Thank you.
try posting this in the 4.2.5 thread and not starting a new thread just for your problem.
Not only did you fail to flash your phone correctly but you also failed to post on the correct forum!
Currently, the CyanogenMod thread has over 5,000 replies. Could you imagine how cluttered this forum would be if everyone was as inconsiderate and selfish as you, and felt the need to open a new thread whenever an issue with CyanogenMod occurred?
jay652 said:
Currently, the CyanogenMod thread has over 5,000 replies. Could you imagine how cluttered this forum would be if everyone was as inconsiderate and selfish as you, and felt the need to open a new thread whenever an issue with CyanogenMod occurred?
Click to expand...
Click to collapse
There is also a Q&A section
Locked

CAUTION -- careful with 1.2.4349

Everyone:
My tablet is just loading the new 1.2.4349 OTA update -- and seeing the "2"
in the version number requires me to say be cautious on a couple of counts:
1. The last experience we had with something with 1.2 at the front of it was
the 1.2.3991 UAT. As long as folks went up from stock 3588 things were not
too bad. If I were giving advice (and I admit this is still a developing process)
I would tell folks to clean up your tablet as much as you can before going back
to stock. Then load either stock 3588, or load to something lower than that
and OTA update so that you have stock 3588 to update from!
EDIT: MAKE SURE YOU ARE COMPLETELY STOCK AND RUNNING 3588!!!
2. My tablet is up and running on 1.2.4349 now and it does have what I call
"blue recovery" on it. When you push power/volume+ to go into recovery,
it will give you a blue lettered screen that looks a whole like like CWM.
This tells me YOU SHOULD NOT LOAD CWM back on your machine until the gurus
check it out. Bekit .8 CWM didn't work with the 1.2.3991!
Other than the above two comments aimed at keeping anyone from getting
into difficulties -- it looks good so far. I flashed back to bekit 1105 (2638) and
then did back-to-back OTA updates to 3588 and the 1.2.4349 without any
difficulties whatsoever.
Good luck folks!!! Be careful and cautious!!!
Rev
P. S. To those of you who played with 3991, this looks just like that update and it really worked very well.
x2. I am doing some test scenarios, right now. I should know within an hour or so if this ROM has the same issues we saw with 3991.
Sure sounds like they updated the bootloader, which will mean all custom Roms will need updating, as well, if they want to install over this new stock.
Roe,
Looks like you got the major update you were expecting.
I did the OTA and now most of my apps are force closing. Even the default browser is having issues.
After downloading the update it reboots the tablet. My screen shows an exclamation mark in a triangle with and android icon to the bottom right of triangle.
The only thing none stock on my 3558 tablet was the nvidia enhancement pack. Any ideas
EDITED
I tried rebooting tablet and it reboots and comes up with message that says the update failed please try again later.
atakapa said:
Sure sounds like they updated the bootloader, which will mean all custom Roms will need updating, as well, if they want to install over this new stock.
Roe,
Looks like you got the major update you were expecting.
Click to expand...
Click to collapse
Yeah, and it's blowing up in my face.
Early tests show that it has the same issues as stock 3991 (which was the basis of TNT Lite 5). Most of the mods here may have issues with this stock update, but I am still testing.
SgtJake said:
I did the OTA and now most of my apps are force closing. Even the default browser is having issues.
Click to expand...
Click to collapse
Wiping user data/factory reset might be in your future. Boot into recovery and clear cache first to see if that helps before blowing all your apps with the reset.
Gaslight,
Yes, with enhancements your tablet is not completely stock.
If you are still running enough to get to Settings/Security/
Reset Factory Data -- you might see if that will help.
Rev
Yah, that didn't work. Looks like it on to a wipe and reset. My G Tab was completely stock too. No add-ons. What a pain in the butt...
SgtJake,
Are you on 1.2.4349 -- such as you've got!!??
Rev
EDIT: Sorry -- too little too late. Somebody else must have
had you do something!!
Yup. 1.2-4349.
Sarge Jake,
If the user wipe doesn't help, you may have re-partition the sdcard to 2048 and 0 to resolve the force closing of apps. BACK-UP your data first, it will get deleted.
Hey, what a great time to test the new recovery software and see if it can re-partition/ re-build the bct table correctly.
Let us know
atakapa said:
Sarge Jake,
If the user wipe doesn't help, you may have re-partition the sdcard to 2048 and 0 to resolve the force closing of apps. BACK-UP your data first, it will get deleted.
Hey, what a great time to test the new recovery software and see if it can re-partition/ re-build the bct table correctly.
Let us know
Click to expand...
Click to collapse
legacy cwm .8 may not work with 4349 (I have to confirm that).
roebeet said:
legacy cwm .8 may not work with 4349 (I have to confirm that).
Click to expand...
Click to collapse
I was talking about the new VS recovery and please, please don't tell me they didn't include a re-partition function. Viewsonic>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I'll have to test this out later. Battery is about to die and I don't have my charger. I sure wish this thing could be charged via USB.
atakapa said:
I was talking about the new VS recovery and please, please don't tell me they didn't include a re-partition function. Viewsonic>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Click to expand...
Click to collapse
They did not in 3991, but I haven't looked at 4349 (yet).
atakapa,
We went through this when the UAT 3991 came out back well before the Wooters
came on board. Roebeet literally had to pull TTX, which is based on 3991, because
so many people were crashing and burning in bad ways -- boot loops, etc.
No the "blue recovery" does not have all the functions of CWM.
Unless someone can tell me a better way, if someone has boot loops or major problems
with 1.2.4349 loaded, they need to:
1. NVFlash back to stock:
http://forum.xda-developers.com/showthread.php?t=861950
Do the procedure exactly and do not skip steps, substitute files,
etc. This will take you to Version 2638 -- called bekit 1105.
It is time proven reliable.
2. Then set up wifi and follow the OTA update process to Version
3588.
3. If 3588 installs and runs fine, then Update again to 1.2.4349.
We may have to refine this as things develop, but losing CWM makes
things harder.
Rev
For the Curious...
Quadrant Standard -- 4 runs all in the 1700-2000 range.
If this is typical, not as quick as I had hoped. At least
as tests go.
Will have to talk about perceived performance later.
Rev
I didn’t see a recovery option in the recovery menu. I was able to get it back by doing the factory data reset from the Settings | Security menu. Now I just have to put everything back.
Has anyone tried installing the market on this yet?
Thanks
SgtJake said:
I didn’t see a recovery option in the recovery menu. I was able to get it back by doing the factory data reset from the Settings | Security menu. Now I just have to put everything back.
Has anyone tried installing the market on this yet?
Thanks
Click to expand...
Click to collapse
I'm not a pro at this stuff, but all my attempts to install the market have failed and the enhancement pack results in a semi-brick.

Ampe A85 A31S - 0.00kbs, format and factory reset every boot

Hey guys. Forgive my noobity but I could do with some help and might have a unique problem although I dare say someone has had this or similar.
Firstly, after putting a 64GB stick in my tablet the other day, it all went badly wrong. I had done it before with my previous 64GB that had been playing up so I sent it back and got a new one. The new one seems to be where it all went pear shaped. I might add, the 64GB is for my phone really but my phone cam was playing up so I was swapping it over and stuff... anyway the card itself seems fine in my phone.
Anyways... now my ampe tablet is suffering some strange effects that have changed. initially it would not boot up unless I redone it with the official firmware.. but then wouldn't boot up again, unless I did the same thing over and over. then one time it just refused to boot up past the initial boot screen. I gave up for weeks then picked it up again two days ago.
Now I give it the firmware installed using pheonix again and it booted up. Ahh I thought... lets play. Now I plug it into the pc but the pc says I need to format the 5GB internal partition. So I did. I then looked how to fix the fact that the tab still says it has 0.00kbs internal storage in settings. Then after a while it came up saying 5GB so i copied some files onto it.. great. But I still can't install apps as I found when trying to do this tested working fix http://www.youtube.com/watch?v=sJlpek6w624
I then read about using android commander to move busybox from xbin to bin in the system folder but mine is already there.
So now I am stuck. I can't test if my tab is rooted for the youtube link fix above although this is what I said to Nayeem on youtube:
================
Hi Nayeem. I'm really struggling with this. At first my tab was staying at the 2nd initial boot up screen after I put in a 64GB SD card. Using pheonix I managed to get it to boot by reinstalling the updated official rom from szampe but every reboot back to square one. I left it alone for weeks and came back to it, reinstalled the factory rom again and now it will boot up everytime but it has factory reset every time. I cant run the apps you supply for some reason. Everytime I have rebooted the tab, and connected back to pc it says I need to format the internal 5GB partition. I don't know if I have rooted it properly as I can't check. The commands you give above, work as it changes the location proven when I 'get' it. I'm really stumped. I'm trying out a method someone said about moving busybox from sys/xbin to sys/bin but it's already there (using android commander) so I am really stumped now. When I format the partition, it allows me to copy files to it.
================
So far I am stuck with boot up being a factory reset and the partition needs formatting and although the tablet seems a little laggy, everything I have tried works including wifi and incoming email alerts after logging into google account for playstore but no apps will install or update. the best warning I get is there is no memory to install anything and Nayeems method of moving the install location to the sd card seems to work but nothing will install still saying NOT INSTALLED when I try.
Sorry for the long winded thing but I am really new to all of this.
My hat is off to you if you read all of this and can offer a solution so i can give this tablet back to the kids.
Do you have an installed recovery
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
nelsontky said:
Try installing a recovery and wipe data and cache. If it does not work u have to repartition ur tablet
Click to expand...
Click to collapse
I am gonna look into this tonight and see what I can find out. I really don't know exactly what I am doing outside of getting pheonix up and sending a standard rom back to it as previously mentioned.
How would I repartition it ? Sounds stupid asking as i can build pcs... just want to make sure I am doing the correct method.

[General Help] [ZTE Nubia Z5S Mini] Need to repartition system and data to ext4

So last night I installed TWRP and flashed a stock rom for my neighbor's phone because it had a bootloop. I made it start again and gave it back to him.
Today, he brought it back saying it had these errors popping up all the time, and that he couldn't use the phone. When I took it, I noticed that it had a constant error saying "the Launcher process has stopped", or something to that extent.
The answer everyone on the web said, was to install Nova Launcher, however, I couldn't even get to the Play Store because of the error popping up all the time, so I decided to reflash the same stock firmware that I had flashed yesterday, in order to buy enough time to get to the store and download Nova Launcher before all the errors came back.
However, this time before attemtpting to flash the phone, I did a complete wipe of user data, since I suspected it may have been what started the errors on the first place.
The thing is that after I wiped the phone, I got some errors while trying to reflash the firmware, errors such as "E: unable to mount /system", the same with /data, /cache and /storage.
Since I was already deep in the mud, I searched for some answers to my problem, and made the mistake of following a peculiar solution: go to wipe, then advanced wipe options, and change the file system from ext4, to ext2 or 3, and then BACK to ext4. People were claiming that it worked and they didn't get the "unable to mount" errors again.
In my case, it didn't seem to work, and now my system and data partitions don't appear to be in the ext4 format, therefore I can't install the stock firmware back into the phone.
Can anyone help me? I hope I explained my case correctly, and I really hope this isn't as scary as it looks.
Please help me
I thought this place was full of experts... please, someone give me a hand!
Bump...
Rockolate said:
Bump...
Click to expand...
Click to collapse
I have exactly the same problem. Did you find any solution?

Deleted Cache Partition by mistake, HELP!

Hi all,
I recently took the plunge into the Android world of things and loved it. Everything was going according to plan, until I decided to try out the DSU loader and load a GSI package. Based on everything I read it shouldn't had cause any issues, but unfortunately it did. Once I rebooted the phone I received the dreaded "Your Device is Corrupted and Cannot Be Trusted" message. Unfortunately it all went down hill for me from there. A couple of things I know now and shouldn't have done without knowing more information was performing a "Format and Download" option on the phone. Had no idea I was going to loose other partitions that is not created by the flashing of the Rom.
I was able to get the Manufacturer Rom and flash it back to the device. Everything appeared to be working fine until I noticed that I was not getting any data for the battery management option. Another thing I noticed is that now my battery is rapidly loosing it's charge. Could this be related to the Cache Partition not being present? Is there anyway to get the Cache Partition back or recreate it by rooting the device? Any suggestions would be greatly appreciated.
Thanks,
-Glitch

Categories

Resources