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.
Related
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.
hey all,
on friday I rooted my NS again to check out cm7 rc1. before i was totally stock @ 2.3.2. friday evening i wanted to show my iphone friends the nexus s with cm7. the first one took it and did take some photos. then he smiled and gave it back to me. force close: SORRY: Android.process(???) has stopped unexpectedly.
this error was looping all the thime. i pressed okay and one sec later it was there again. i tried to flash the rom again in recovery, but the error was still there. i did date and cash wipes and some factory resets and then the error was gone.
on sunday i was travelling home on train and suddenly the error was back. i tried again some wipes and then i deceided to restore my nandroid backup. so i was back on 2.3.2. during sunday afternoon and evening i got these errors:
- NS is freezing while it is in standby... if i grab the phone and want to unlock it but the display keeps black -> i have to put out the battery..
- NS is beside my keyboard and suddenly all four buttons are on. display is still black. unlock not possible--> battery again
- NS is freezing while using facebook or twitter app
today... i unrooted it again and went back to a nandroid (2.3.1) guided _here_.
after unrooted again NS wanted to update to 2.3.2 which i confirmed.
about to hours later the errors i explained came back.
am i the first one who bricked NS?
please give me some help how to get it back working correctly, because i love this phone so hard.
I did another factory reset and now the phone is hanging at the google Logo. The four buttons are powered.
This is looping, too.
Yesterday I tried some things to kill these errors. I did:
- factoy reset (in settings menu)
- fastboot erase userdata 2x
- wipe cache, wipe data, wipe devliak
Today the phone was with out a problem, but just a moment ago I wanted to unlock it by pressing the power button but the display didn't react as usal. It is still black and the only thing I can do is to take out the battery....
Last step I can do is to send it back to my girlfriends sister in US so that she can bringt it to Samsung US to get it serviced.
"bricking" the phones involves the phone not being able to turn on or do anything, period. your phone isnt a brick. after doing a "factory reset" you want to reflash whatever rom you are using. it seems like youre having problems with a bad app or some bad data.
thx simms22. i just flashed the newest cm7 nightly with rom manager (incl. wipe). i set up all my apps and 20 min later the error come.
to figure out if it is a bad app problem i do a factory reset now and won't log into google account and see if the error appears.
simms22 said:
it seems like youre having problems with a bad app or some bad data.
Click to expand...
Click to collapse
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
stiefa00 said:
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
Click to expand...
Click to collapse
are you using any of the custom kernels?
no, I'm using stock kernel and never flashed a custom kernel.
stiefa00 said:
no, I'm using stock kernel and never flashed a custom kernel.
Click to expand...
Click to collapse
im going to have you try wiping once again. wipe data/factory reset. only this time reupdate to android 2.3.3 right after the factory reset in recovery. dont boot after wiping, update after wipe, then reboot.
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
stiefa00 said:
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
Click to expand...
Click to collapse
im now thinking it might not software related. if it was software, a wipe and reupdate should have fixed it. maybe you should check into a warranty replacement. .
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
stiefa00 said:
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
the only other thing i can think of that might cause something like that after wiping is something bad on your "sd" storage. copy everything you need off your "sd" storage and try wiping that.
stiefa00 said:
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. Then nandroid restore...
Click to expand...
Click to collapse
I think I allready did this? Or do you talk about this 1gb sd. If so, how to format this one?
Could I find something usefull with logcat?
Sent from my Nexus S using XDA App
According to this thread I think you will have to get it replaced:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=44db6d8e31129d4c&hl=en
Holy sh** what an anoying link. -.-
BUT: thanks dude.. now I know waaazzz up
First off, I have done a search and read dozens of threads, none of which solved my problem...
I have a wifi xoom, which I rooted many months ago without any problems. Recently updated to 3.2 like a month ago or so. I have not made ANY changes within the last month, and the tablet has been working perfectly.
A few days ago, I left the tablet to charge. Once charging was complete, I turned it on and its stuck on the boot animation. I just keeps playing over and over again, I've let it sit for 10+ minutes, with nothing happening...
I tried removing the SD card then rebooting, and its the same result....
Please help! If need be, I can go back and look up all the exact steps I've done to root and get it to where it is today. Like I said though, it has been working perfectly, and I have not made any new changes in at least a month... I don't see why this would happen all of a sudden...
Have you tried to reinstall firmware?
Regards.
GReddySetGO said:
First off, I have done a search and read dozens of threads, none of which solved my problem...
I have a wifi xoom, which I rooted many months ago without any problems. Recently updated to 3.2 like a month ago or so. I have not made ANY changes within the last month, and the tablet has been working perfectly.
A few days ago, I left the tablet to charge. Once charging was complete, I turned it on and its stuck on the boot animation. I just keeps playing over and over again, I've let it sit for 10+ minutes, with nothing happening...
I tried removing the SD card then rebooting, and its the same result....
Please help! If need be, I can go back and look up all the exact steps I've done to root and get it to where it is today. Like I said though, it has been working perfectly, and I have not made any new changes in at least a month... I don't see why this would happen all of a sudden...
Click to expand...
Click to collapse
No need to panic.
When you rooted, did you install CWM Recovery, and if so, do you have a recent nandroid backup? Have you tried rebooting into recovery?
What steps have you followed to get out of your bootloop?
Yes, I have Clockword Mod Recovery 3.2.0.0 R4c 100611-1150
Upon attempting a restore everything appears to work properly until the end when it gets to restoring data, I get an error, regardless of which restore image I use(I tried all the ones I have). It reads as follows:
"Restoring data...
Error removing /data/data/com.noshufou.android.su/cacheError while formatting /data!"
I also attempted a clean wipe/factory reset with similar unsuccessful results. I get an error during formatting data, which reads:
"Formatting /data...
Error removing /data/data/com.noshufou.android.su/cacheFormatting /cache..."
The rest of the formatting appears to run successful for /sd-ext and /sdcard
Have you manually tried to format the system, cache and data? This can be done from the advanced menu.
Sent from my Xoom using Tapatalk
jerrycycle said:
Have you manually tried to format the system, cache and data? This can be done from the advanced menu.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Can you please provide me with more detailed instructions?
From the advanced menu I see:
Reboot Recovery
Wipe Dalvik Cache
Wipe Battery Stats
Report Error
Key Test
Partition SD Card
Fix Permissions
Sorry, we're forgot talking about Cwm. It's under mounts and storage.
Still the same result as before... I went to mounts and storage > format /data
"Formatting /data...
Error removing /data/data/com.noshufou.android.su/cacheError formatting /data!"
Try format system first then data and cache.
My suggestion would be to go back to stock and then re-root. You can find the stock download on the Moto Dev home page.
+1. Restocking link. MOTODEV > Produ / Software http:/.ly/sQtpKQ bit cts > Device. Then use universal root method reroot.
Sent from my Xoom using Tapatalk
Thanks everyone! I was hoping I would be able to fix it without going back to stock, but since I was unable to I just went that route.
Going stock worked, and I am back to where I was before, so thank you for the advice! In case anyone else may have this problem, this is what I did:
Went back to stock using this: http://forum.xda-developers.com/showthread.php?t=1049485
Then rooted using this: http://forum.xda-developers.com/showthread.php?t=1242241
Then got back to 3.2.1 using this: http://forum.xda-developers.com/showthread.php?t=1278214
I have a Sprint Nexus S4g, and have been using Bugless Beast ROM for a few weeks. About a week ago I started having Random reboots to recovery, as well as locking up at the Google splash screen when rebooting. I have also had many problems with google apps crashing as well as the phone just being locked up when I go to use it (in this case the notification lights usually are lit).
I have tried clearing cache/dalvick cache and factory reset. The last time I even wiped my SD card and am now stopping Google from installing my apps other than Goomanager.
about an hour after my last attempt, I got my first random reboot to recovery. I am not sure what to try next.
Thanks for any help!
Go back to stock and see if the problems persist
snandlal said:
Go back to stock and see if the problems persist
Click to expand...
Click to collapse
I am going to try when I get home. If that doesn't work, I guess I will send it to Samsung under warranty.
Just returned to stock, and it is still locking up.
I have the shield tablet LTE version and after connecting to WIFI it immediately installed all OTAs upto the hotfix also. So here I am sitting with lollipop in my tablet and I decide to go for rooting and CWM installation.. After rooting using adb/fastboot and installing CWM image, I decide to disable ATTall access because I read that it stops the portable hotspot from working. So, did that and then process after process started crashing. First it started with background data not being enabled (playstore wouldn't open) , NVidia hub crashing, google text to speech crashing, etc.
So, I went to cwm and did factory reset. At the initial stages itself where it asks for language setup, the google text to speexh crashes and I cannot click next or proceed forward.
I flash the Lollipop OTA once again thinking it would overwrite the system but it didn't.. and the same issue keeps happening..
Now what do I do?
Regards
Alden
An update to the mess i was in...
I tried recovery mode at the fastloader boot menu and I got the robot lying down with a red exclamation mark sign. I pressed vol + key and it opened the original recovery I think. I wiped user data from this menu and rebooted. and now it has come to the original screen setup and so far no process crashes...
What could have caused this entire mess?
I am not sure what would cause your issues but i believe your best bet is to download the full rom image for your tablet and flash it via fastboot. That should get you back up and running. (Be warned doing this will erase everything on your tablet!! SD card will be untouched)
By fullmrom u mean the one from the nvidia developer website right?
Yes that is the one! I am currently at work so I cant post a link to it but if you need it ill try to post it once im off, in about 30-ish minutes. Good luck! (p.s. last resort is RMA)
Is your shield up and running once again? Just wanted to get an update. =]
Thanks javydawg, I didnt use the one on nvidias developer website as i simply did not have enough data left in my Internet plan .. its 2.3 gb in size... after recoVery i was left with lollipop so i flashed a 750 mb file tht i gt from these forums and updated it to the latest version.. i still haven't pinpointed the reason for my earlier trouble but will shout out if it happens again... have to be careful cos not sure if RMA is possible for me in India...