Database Info

[Q] Stuck during bootup TNT 2.0

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.

[Q] I need some help with my sidekick

Ok so I'm not a noob around here. I'm pretty good with the android stuff, but this one has got me stumped. I have a perfectly working sidekick 4g with B2b 2.5 on here. All of a sudden it forces itself into a repeated reboot. It shows me the white sidekick/samsung screen, and about 3 seconds later reboot into the same thing. And it does this over, and over, and over again. At some point it stops and functions normally, but only for a few minutes, then repeats the process. I've already changed roms, back to glorious overdose. It will even reboot in CWM. The only time it stays stable is when it's in download mode. Another problem there. ODIN doesn't recognize when the sidekick is plugged in through USB. So even if I wanted to ODIN, I can't. I tried booting without my sd card, and my sim card. No avail. and i disabled lagfix, still reboots. I take the battery out, and when I put it back in, it turns itself on just so it can continue restarting. There's nothing stopping this phone. Please help if you can. Thanks for taking the time to read this!

first, enable voodoo. i tried disabling voodoo once and it just kept rebooting. i pulled the battery, put it back in, enabled voodoo, and it booted normally. however, in your case, i would run fix permissions before trying to reboot. to run fix permissions, while in recovery mode go to advanced. select fix permissions, wait for it to say done, hit the back button, and reboot. see if that helps. if not, you may want to ask someone more experienced.

Thanks for your reply. I found out that my windows(8) didn't correctly install my sidekick drivers. tried it on my xp machine and bam, ODIN worked like a charm. Unfortunantly, the problem persisted. So i know it's not a software problem. I contacted samsung yesterday and sent in my phone today. I ODINed back to stock then updated to kj1 through kies. I read up on it a little more and people said it was maybe a loose connection on the phone. I'm still in warranty, so I'll let samsung deal with that.

[Q] Can't install roms, booting recovery kernel error

I've been working on this for nearly three days. My pad has been having issues for a while. Really laggy and slow. Finally couldn't take it anymore. I've restored to factory a number of times and while it helped briefly the lag always returned within a few days. Since I rooted (with Motochopper) and unlocked my pad the improvement is very, very noticeable. Faster than it was out of the box. I've been trying to install Cyanogen, but from the start I've been getting stuck at "booting recovery kernel image" whenever I try and boot into recovery. CWM can't get into it either. I tried TWRP instead but apparently their website is down because I can't access it via CWM or a web browser. I rolled the rom back to the last 4.1 and thought I'd bricked it. Kept getting stuck at spinning wheel on every restart. Wiped data and it restarted fine.
I'm convinced that it's the kernel issue, but after extensive searches I can't find a way to overwrite it without having access to "recovery". Yes, I'm noobish. I haven't cracked anything since my original Razr many a moon ago.
Any help would be greatly appreciated cuz im about to lose my marbles
Thanks!

[Q] I've tried everything and looked everywhere

Hey everyone, I'm using a GT-P5100 (3G + Wifi) O2 UK rooted tablet and for the last month it has been broken. It started rebooting itself randomly every now and then, and then suddenly it wouldn't even boot up for 15 seconds before it would restart itself again.
I am able to get into safe mode and I can get into the boot options, but when I factory reset it does nothing, I've tried from the boot menu, from safe-mode options and even from the dial up code.
I tried to connect my tablet to my PC as a media device and format it but that didn't work either; I can't connect it as a disk then format it that way because they took out 'mass storage mode' on this firmware.
I then tried to flash a stock ROM in Odin but every time I tried it would fail until I used Odin.v1.3, but guess what, it rebooted itself and my entire tablet is still exactly the same.
(the option was on AP ram in v1.3 not AP nand I don't know if that makes a difference.)
If anyone can point me in the right direction I would appreciate it so much. I have been trying for weeks to fix this and I just don't know what to do anymore, I tried on another forum but nobody answered me.

Everyone else gets replies and I get zilch; amazing. I don't know what it is that is preventing my tablet from wiping itself but it refuses to clear the current data no matter what way I try (ROM, factory reset, computer format). If someone could just tell me what that is and what I have to do about it that would be grand.

You mention "rooted " but you don't mention what current rom or past roms that you may have flashed, you could have some sort of rom cluster [email protected]$k going on in your tab but NO one else will ever be able to help because of lack of INFO or history.
Pp.

I standard rooted it from Odin. This is my first ROM I am trying to flash. I just need to know what would prevent a tablet from rebooting itself properly. Factory reset, format and flash is not working so I must assume that rebooting is the issue here.

If you are running stock rooted rom and having issues like this the only way out is reflashing the stock firmware complete (not just a rom) and see if that fixes it before you try any other roms.
If you can get into download mode thats the fix.
Pp.

To flash it completely do I need more than an MD5 file? (I also have the partition file for my model). Another question, if the tablet is having issues with the reboot after a flash, will updating from a microSD with a zip help? Thanks for the advice.

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5

Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster

napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.

Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-

So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.