My father brought home the G Tablet yesterday after getting it at Office Depot because it was on sale and was the last one left.
I didn't want to open it because I've had my eye on the ADAM tablet and was going to wait for it to come out and compare the two. However, he convinced me to mod the G Tablet to run TNT 2.0.
It worked fine for a while today. I got it up and running, fixed the Market, and was able to download apps and games. Then, I woke it out of sleep mode and the Market started coming up with errors. I figured that I'd just need to turn it off and boot it back up again.
The problem that I'm having is that the thing doesn't want to boot back up. It goes to the ViewSonic screen, then to the G Tablet logo, pauses for a second, then goes back to the ViewSonic screen.
I attempted to do a recovery and see if I could reinstall TNT; it refused. It will see that there is a kernel, but when it goes to install it, I get an exclamation point flashed on screen and then it goes back to the ViewSonic screen (I'm getting really sick of looking at those birds).
Is there any way to fix this, or did I have the shoddy luck to have one with bad hardware?
I didn't use Clockwork to install the firmware. I realize that that might have not been the best choice now.
I haven't had that, probably I'm still stock, but there are threads about getting out of the problem. Use forum search, in this forum. Search titles only, for 'loop'.
Jim
Thanks.
I tried flashing it again with clockwork installed to no avail. I also tried to set it back to the manufacture default, but encountered the same loop.
Looks like it's going back to Office Depot!
Kaizykat said:
Thanks.
I tried flashing it again with clockwork installed to no avail. I also tried to set it back to the manufacture default, but encountered the same loop.
Looks like it's going back to Office Depot!
Click to expand...
Click to collapse
If you have clockwork installed then go to advanced and partition the sdcard. I use 2gb, and 0 for swap. Do a wipe data/factory reset, and a wipe cache partition from clockwork also. Problem will likely go away after that. Partitioning the sdcard will remove any data but that's the way it goes sometimes.
Then I would reflash from clockwork something like TnTLite 2.4, or the VegaN Beta 3 rom. You can do that from clockwork also.
Sprdtyf350 said:
If you have clockwork installed then go to advanced and partition the sdcard. I use 2gb, and 0 for swap. Do a wipe data/factory reset, and a wipe cache partition from clockwork also. Problem will likely go away after that. Partitioning the sdcard will remove any data but that's the way it goes sometimes.
Then I would reflash from clockwork something like TnTLite 2.4, or the VegaN Beta 3 rom. You can do that from clockwork also.
Click to expand...
Click to collapse
x2 on the sd re-partition, it will most likely fix the issue. Many users have reported similar issues.
Here's the problem -- this is very common and exchanging it probably won't help as you might eventually have the problem again. You already have cm on the device, so you are 90% there already.
Related
I've tried a lot of things.
Long and short of it, I was dumb. I was playing around with kernels and installed one I shouldn't have. Reason being as I wanted to go back to stock and they stock kernel on hydra-kernels.net(?) was good but it had an error for me. The error was involving phone storage.
So, I went and downloaded a stock D'inc kernel but this as it turns out was from 2.1 or so. Naturally this didn't work and broke my phone or at least really ticked me off.
I tried the downgrade but the bootloader won't see the image (formatted sd to FAT32 both in windows and OS X)
tried to hard reset: nothing
clearing cache nothing
Is there any hope?
any suggestions would be appreciated
Bump.
I need a working phone
Can you get into recovery? (Clockwork or Amon Ra)
If so, just flash a backup. If you do not have a backup (shame on you), wipe everything and flash your ROM of choice. You will of course have to start from scratch this way, but your phone will be working once again.
I was thinking of this. When i boot into recovery and select "wipe data/factory reset" it does it's thing and upon reboot I'm still stuck at the white screen
For some reason it won't install any roms either
Spoke with a Verizon tech and they're sending me a new phone
Should I be worried if they perform tests on it? The phone itself is S-Off because of root. Will they charge me for the new phone?
I have to send the one I have back to Verizon.
hey guys i picked up a gtab a couple days ago and rooted it last night. i have clockworkmod, tntlight, launcherpro, titaniumbackup, market and flash up on it by following the instructions from another part of the forum. everything was going great until a couple hours ago when i was using google in the browser and i got a force close message. i tried to restart the browser a couple times with the same message so i turned my gtab off and attempted to restart it. it got to the gtab screen on startup then kicked back to the birds. im assuming this is whats called a boot loop. is there any easy way to make this gtab usable again with the same mods i had on before or is it bricked for good?
It's not bricked. Search for boot recovery. Nvflash, restore etc...
dannny_b said:
hey guys i picked up a gtab a couple days ago and rooted it last night. i have clockworkmod, tntlight, launcherpro, titaniumbackup, market and flash up on it by following the instructions from another part of the forum. everything was going great until a couple hours ago when i was using google in the browser and i got a force close message. i tried to restart the browser a couple times with the same message so i turned my gtab off and attempted to restart it. it got to the gtab screen on startup then kicked back to the birds. im assuming this is whats called a boot loop. is there any easy way to make this gtab usable again with the same mods i had on before or is it bricked for good?
Click to expand...
Click to collapse
Not bricked. Go to clockwork, advanced, partition sdcard and choose 2048, and 0 swap. Something about these tablets seems to like to corrupt the partition. Once fixed, it should be ok.
No you're not bricked for good. Where there's a will there's way.
... looks like that will work ^
Note, a partition will erase all that you have on your "sdcard" or your gtab, that's what it partitions.
i did the partition and it boots up to the tntlite screen where i need to create a google account ... then it asks me to connect to wifi when i hit connect it says "the application Google Services Framework (processcom.google.process.gapps) has stopped unexpectedly. please try again.....if i hit force close it kicks me back to the connect to wifi screen .. any ideas on what i can do from here?
dannny_b said:
i did the partition and it boots up to the tntlite screen where i need to create a google account ... then it asks me to connect to wifi when i hit connect it says "the application Google Services Framework (processcom.google.process.gapps) has stopped unexpectedly. please try again.....if i hit force close it kicks me back to the connect to wifi screen .. any ideas on what i can do from here?
Click to expand...
Click to collapse
Without really knowing what is, or has been on your tablet I would suggest going back into clockwork and doing a "wipe data/factory reset", and a "wipe cache partition".
ok so if i do that it will be set back to stock but will i still have root access?
dannny_b said:
ok so if i do that it will be set back to stock but will i still have root access?
Click to expand...
Click to collapse
It won't go back to stock like when you bought it. It will just reset back to like when you first put whatever rom you have on it.
oh ok so i dont need to put tnt lite 2.2 back on it should be set already.. just need to do flash and market fix.. thanks for the replies
dannny_b,
And when you get to the Google login thing, just don't do it until your wifi is up and running!!!
Rev
Do a data wipe on recovery. Then when it ask to sign in, skip it and connect through wifi later. This is of course assuming you partitioned the SD card correctly.
After that you can sign in using Gmail or market and you can attempt to do the market fix, if it is not already fixed.
I've had a great experience so far with my xoom! I had it rooted and overclocked since the first day I had it!
Its starting to get sluggish and things are beginning to go a little wonky, so I'd like to reflash to either the stock honeycomb 3.1 installation, or one of the roms that I've seen floating around.
The trouble is that the minute I saw the 'encryption' feature, I used it. I did that before ever rooting or overclocking it.
I am now unable to reset to factory defaults. Here is what I've tried:
- using the menu option from inside of the settings area to reset the tablet to factory defaults: When I do this, it reboots and gets to a screen with a little android logo and a progress indicator - however within several seconds the progress indicator goes away and is replaced by that nasty little triangle with the exclamation point saying something isn't right.
- Booting into clockwork mod and formatting everything available to be formatted from CWM: This actually broke the tablet and I had to reflash things to get it working properly. However all of my user stuff and all the settings remained intact.
Does anybody know how to reset the tablet to factory default after its been encrypted? You guys know 50x more than Verizons support team will.
My only other option is to back up all of my data, "break" the tablet, then go use my warranty at the store to get another one. I'd really like to avoid that if at all possible.
What version CWM do you have? Flash the newest recovery if you flashed the recovery from ROM manager. If that doesn't work then flash stock software.
What version Xoom do you have? This is for 3g http://www.xoomforums.com/forum/motorola-xoom-hacking-guides/2788-how-return-stock-3g-4g-hr166.html
You don't have to do the last step of locking if you want to reroot. That should also remove encryption. If it doesn't do a factory reset from settings. And verify CWM works as well.
Hello there, I have a huge issue with my Motorola Xoom.
I ran the #156 TeamEOS 4.2 Nightly Rom for my European 3G Xoom when all of a sudden my tablet started acting really weird.
Apps were crashing, Google Play wasn't working, Browser as well, and so on.
I decided to do a hard reset, formatting cache, Dalvik Cache, Hard Reset...but nothing was cancelled. As soon as i rebooted my device, everything was back the way it was with the same issues. I noticed my tablet was costantly updating the same apps and even if I updated them the following reboot they were back re-updating themselves.
I have no idea what to do, I tried everything, including RSD Lite. Nothing.
Can somebody help me figuring out what to do and how to at least format my Xoom completely so that I can re-install my rom and then re-install the apps?
Thanks.
I would boot into recovery and do a full wipe the reflash the rom a gapps. you should be good to go.
No can do, sorry. What's weird is that even when I go to change the performance settings on the rom, to overclock it more or less, the changes are not recorded. I can set whatever I want but it doesn't change it. It's like the tablet is in a loop, always stuck doing the same things, charging the same rom, the same settings. I really don't know what to do, I don't want to throw it away but I don't know how to solve it.
Which xoom do you have? We can always flash the stock img with fastboot to restore it. It will be back to complete stock.
Can you get into recovery at all by powering off then press the power button wait till 3 sec's after the logo appears and press volume down. You will see android recovery at the top press vol up to select. If you can and you have a backup restore it. If you use an external sd card you can load a rom on to it and flash it in recovery.
"I decided to do a hard reset, formatting cache, Dalvik Cache, Hard Reset...but nothing was cancelled. As soon as i rebooted my device, everything was back the way it was with the same issues. I noticed my tablet was costantly updating the same apps and even if I updated them the following reboot they were back re-updating themselves."
this is the same exact problem i'm having. I cannot get my xoom to reset. It always goes back to where it was before.
danman1835 said:
"I decided to do a hard reset, formatting cache, Dalvik Cache, Hard Reset...but nothing was cancelled. As soon as i rebooted my device, everything was back the way it was with the same issues. I noticed my tablet was costantly updating the same apps and even if I updated them the following reboot they were back re-updating themselves."
this is the same exact problem i'm having. I cannot get my xoom to reset. It always goes back to where it was before.
Click to expand...
Click to collapse
Sounds like your data has gotten corrupted somehow. You can take the boot.img out of whatever Custom ROM ur using, and via terminal -
fastboot flash boot boot.img
fastboot reboot
I'm not using any custom roms. I'm using factory settings for almost everything.... also i don't know how to use terminal
Mjamocha said:
Sounds like your data has gotten corrupted somehow. You can take the boot.img out of whatever Custom ROM ur using, and via terminal -
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
I have the same problem.
The Xoom is a european with android 3.1 kernel version 2.6.36 and build H.6.3-25-9 <- this i dont understand but i think that is no correct.
I try flash the H.6.1-38-1_Retail_Europe version, all the process finish ok, but when i restart the tablet everything continues as before.
I not know what else to do, Heeeelp.
(Just wrote a detailed post and when I went to post, it said I wasn't logged in and erased it...will give a quick run down and can supply more detail where needed as I work through fixing my phone)
Stuck on the white htc splash screen is my most recent problem. Sometimes it gets by that but then boots into recovery. I think bananagranola has the solution in their sig to flash a boot.img. and think I'm comfortable with how to do that, just need to find that file (in the ROM zip?)
What led up to this.
Successfully unlocked and flashed to CM7 back in late Jan/early Feb.
Started experiencing random freezing about two weeks ago.
A week later (last weekend) flashed Jellybean (R10). Worked great for a couple hours then started having the same random freezes.
If things froze I'd have to remove the battery and reboot. After a day or two of this though it'd get to the point that even that would leave me on a frozen jellybean boot animation. So I'd go and factory/data reset in CWM Recovery, wipe cache, wipe Dalvik then reflash the ROM. and I'd be good for a little while more.
Tried flashing back to CM7 but Recovery didn't like the file (it has a good MD5 when checked) Had tried my restore point from early Feb before to no avail, so decided this morning to try other restore points from the last few weeks, right before and after switching to JellyBean. They got further, the first step is something with boot then something with system. It failed on the system part. OK...so I wiped and reflashed jellybean again, and now I am to my splash screen freezes.
I should have asked for help much earlier (lesson learned!) but here I am asking now...what's the first step.
Do I test out and see if I hang on the splash screen again. I haven't turned the phone on in about an hour. Worried of screwing it up more.
Thanks all.
TL;DR Believe I'm stuck on splash screen and know solution to that. Have had phone flashed with new ROM with no prob for months, recently freezing, regardless of ROM. Hoping for advice on getting things working again, starting with whether fixing the splash screen thing first is where to start
splash screen issue seems fixed
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
irishpanther said:
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
Click to expand...
Click to collapse
That doesn't sound like an sdcard problem. Are you full wiping?
bananagranola said:
That doesn't sound like an sdcard problem. Are you full wiping?
Click to expand...
Click to collapse
I'm wiping data/factory reset and cache as well as the dalvik cache.
The steps to flashing a ROM by sashank at link mention to format /boot and /system. I didn't specifically do those...but don't see the option for /boot in any menus I've checked.
A week or so ago I was beginning to suspect there was an issue with the memory but I never found the right search terms to find out how to do a memtest if that's what would have found any problems. Yesterday I did come across some discussion of a corrupt partition/bad chips in some HTC devices. I followed the directions there and through adb ran dmesg | grep mmc0 and the output was similar to the 'normal' one given and showed none of the messages they claimed to indicate a bad chip.
I'm not too concerned with any data from the phone...I backed all that up long ago and the rest restores from my google account. So if I getting things running would normally raise concerns of lost data, that's not an issue for me.
Thanks for taking the time to read. I try to be brief...but don't want to leave anything out.
Wanted to update here before trying to start a new thread and clogging up the board. The title of this thread is not up to date though.
I can hboot just fine and boot into recovery just fine. My phone is unlocked and rooted, ENG S-OFF from when I used AAHK quite a while ago.
When trying to navigate from menu to menu in Recovery I will get the following error messages (best I remember from last time I was in there, I've let the phone be for the last 2-3 days now)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
This doesn't show up at first though, only after I do a Wipe Data/Factory Reset. And if I understand correctly, that wipes /cache so maybe that's causing these errors?
Anyway, after wiping the dalvik cache I can flash a ROM, I've been using Jellytime, I haven't been able to rollback to CM7, not sure why not.
Jellytime will run though...at first! the first couple of boots I can get in and get through registering my google account and have it begin restoring apps if i make that selection. The time I have to work on the phone before it freezes gets shorter and shorter though. I have to remove the battery to get it to reboot. Eventually I am left with the phone hung during the boot animation. I've left it for over an hour before...it's definitely hung there.
So my reading leads me to believe corrupt partitions. I'm not finding a lot on what I should do to reformat and maybe repartition or whatever I may need to do to recover a functioning phone. I don't care about any data on the phone. I just want to get things working again. I ended up getting a new SD card during all this that arrived earlier. If I can get my phone working, I'd prefer to use that from here on out too. I can use the adb in recovery mode just fine if that's necessary to rejigger things to work.
Can anyone help reset my partitions, if that's what this issue seems to be? If not...any ideas?
Thanks.
Recovery and version?
bananagranola said:
Recovery and version?
Click to expand...
Click to collapse
ClockworkMod Recovery v5.0.2.0
Full wipe?
bananagranola said:
Full wipe?
Click to expand...
Click to collapse
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
irishpanther said:
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
Click to expand...
Click to collapse
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
OK, I'll give this a try. The issue with the freezing is why I moved from CM7 though (which had been stable for four months) so it's reproduced itself in different ROMS. I'll post back once I give this a try. Thanks.
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
I gave Android Revolution a shot. During the flash it gave a message which might also be why I wasn't able to flash back to CM7. The MD5 did verify.
Code:
assert failed:write_raw_image("/tmp/boot.img","boot")
When I went to reboot, I ended up in Jellytime. Of course I had to sign back in to google apps and those things were reset from the dalvik wipe. Shortly there after the phone froze.
On reboot I tried a logcat. Didn't get it right from the start (you can send the command during the boot animation if I read correctly) but captured the failure of things. It's back around the 09:02 portion of the log. To my eyes it looks similar to others I've collected. Especially the message
Code:
Fatal signal 7 (SIGBUS)
though I haven't been able to figure out much about that, or identify what it is before that that could give another clue as to what is screwy since that's maybe (Probably?) related to the flashing issues.