I am having a repeated issue I was hoping someone has seen or could help me with.
I'm on the default rom w/ the TnT Enhancement pack and overall I LOVE the device. One thing that is literally killing me is trying to get data to/from my device.
I have tried USB linking to my Win7 64bit system as well as copying data to/from with Astro and the microSD card and more times than not either during or after any file copy/move activity the device locks up, needs to be hard booted and then I'll get the 'scanning SD card' message in the notifications and the tablet locks up hard, and becomes unuseable until I reboot about 10xs and finally it starts to return to normal.
I've tried formatting EVERYTHING and re partitioning to 2048 & 0 w/ clockwork and doing a fresh NVflash and reupdating/TnT Enhancement, etc...with similar results, so I'm not sure at this point if it's my microSD the internal card, some sort of hardware or overall software issue.
I love this device, but I'm borderline frustrated enough to return it, only problem is ALL the other tabs are WAY too expensive for what you get! ($400 is reasonable $600+ is stupid - I can get a laptop for that much - which I already have, and the tablet isn't nearly as capable/more just convenient)...
tullywork said:
I am having a repeated issue I was hoping someone has seen or could help me with.
I'm on the default rom w/ the TnT Enhancement pack and overall I LOVE the device. One thing that is literally killing me is trying to get data to/from my device.
I have tried USB linking to my Win7 64bit system as well as copying data to/from with Astro and the microSD card and more times than not either during or after any file copy/move activity the device locks up, needs to be hard booted and then I'll get the 'scanning SD card' message in the notifications and the tablet locks up hard, and becomes unuseable until I reboot about 10xs and finally it starts to return to normal.
I've tried formatting EVERYTHING and re partitioning to 2048 & 0 w/ clockwork and doing a fresh NVflash and reupdating/TnT Enhancement, etc...with similar results, so I'm not sure at this point if it's my microSD the internal card, some sort of hardware or overall software issue.
I love this device, but I'm borderline frustrated enough to return it, only problem is ALL the other tabs are WAY too expensive for what you get! ($400 is reasonable $600+ is stupid - I can get a laptop for that much - which I already have, and the tablet isn't nearly as capable/more just convenient)...
Click to expand...
Click to collapse
I'm kind if unclear about your problem. Is it hanging only when you're copying stuff between /sdcard and /sdcard2?
I'm asking because you mentioned USB, but I didn't think you could xfer directly to/from /sdcard2 over USB.
If that is the case, have you tried a different microSD card?
Jim
I've tried USB xfer from computer to /sdcard as well as using multiple microsd cards to transfer data to the internal gtab memory, all seem to have the same results, when moveing external data to the gtab, it suddenly seems to cause some sort of file system corruption (as best I could guess). last round forced me to go as far as re-doing the entire device to bring it back to a stable state!
Since you mentioned returning it I would suggest exchange as this sounds like a problem with your device. Could have a bad card reader or the card is just not seating correctly
Hi,
A couple of comments:
- does the enhancement pack you have have that dataloop thing? I've seen some posts mentioning corruption w dataloop. Maybe try w/o the enhancements?
- for the scanning /sdcard2 thing, maybe try adding a file named .nomedia (period followed by nomedia) in /sdcard2. That's suppose to prevent the mediascanner from scanning the dir plus subdirs.
Jim
I'm about done with this thing. I've tried everything I can think of and I can't get away from the thing locking up (from full stock OTA gtab to the TnT custom ROMs).
1)The first Gtab I had the screen wasn't responsive to touch (had to hit it two or three times to get it to recognize you wanted to open an App. returned to SEARS
2)The second Gtab I got, when I powered it on for the first time it had a line across the entire screen in the LCD of bad pixels (dead pixels/whatever - something was wrong with the screen) - took it back AGAIN
3)This Gtab locks up whenever I use the microSD or USB transfering files to the thing. WILL BE RETURNED
I'm convinced that these things are the biggest pieces of sh!t on the planet. I've spent (and I'm not even stretching the truth) probably 40 to 60 hours trying to get this thing to work LIKE A NORMAL DEVICE - all I want is something to: browse the web, view videos and read epubs on - I'M NOT ASKING FOR MUCH, a simple device that can't accomplish THOSE SIMPLE TASKS - SUCKS.
I'm happy to think that the money viewsonic (or whomever) spend to build these three BAD devices is out whatever it cost them, given my trouble. TiD!
how to fix
Go to settings, applications, system applications, media storage and clear data. It worked for me.
tullywork said:
I'm about done with this thing. I've tried everything I can think of and I can't get away from the thing locking up (from full stock OTA gtab to the TnT custom ROMs).
1)The first Gtab I had the screen wasn't responsive to touch (had to hit it two or three times to get it to recognize you wanted to open an App. returned to SEARS
2)The second Gtab I got, when I powered it on for the first time it had a line across the entire screen in the LCD of bad pixels (dead pixels/whatever - something was wrong with the screen) - took it back AGAIN
3)This Gtab locks up whenever I use the microSD or USB transfering files to the thing. WILL BE RETURNED
I'm convinced that these things are the biggest pieces of sh!t on the planet. I've spent (and I'm not even stretching the truth) probably 40 to 60 hours trying to get this thing to work LIKE A NORMAL DEVICE - all I want is something to: browse the web, view videos and read epubs on - I'M NOT ASKING FOR MUCH, a simple device that can't accomplish THOSE SIMPLE TASKS - SUCKS.
I'm happy to think that the money viewsonic (or whomever) spend to build these three BAD devices is out whatever it cost them, given my trouble. TiD!
Click to expand...
Click to collapse
Dude, I've been telling people on here for days. Go buy an ipad and leave us gtab fans alone. My benchmark is at 3000's while having half a dozen apps running and I'm happy with it. My screen is too sensitive to say the least.
Related
I've been running the leaked 3.16.651.0 ROM on my Sprint Mogul for a little less than month now. A problem I've seen (only twice) is that the microSD card just 'disappears'. Both native file explorer and Resco file explorer say it isn't there when I try to navigate to it. Problem is resolved with a soft reset.
I don't run programs from the card so I wouldn't notice it is missing unless I'm specifically working with files on it, which isn't too often. The fact that I've seen this twice (out of maybe 20 times working with the card) just had me wondering if anyone else has seen this. I'm using the 8GB Sandisk SDHC card. Since I just got the phone, and updated to the ROM about the same time I got the card, I have no experience with the card running on stock ROM
I've never had that problem (leaked or official ROM), but I seem to remember my old 6700 had issues like that when I installed voicecommand.
you should do a search cause alot of people with dcd rom based on the new rom had the same issue i think you have to not use encryption or something
Try installing this:
http://www.mediafire.com/?7mucmyyntlx
It's supposed to help your phone function with the larger Micro SD HC cards.
eXplicit815 said:
Try installing this:
http://www.mediafire.com/?7mucmyyntlx
It's supposed to help your phone function with the larger Micro SD HC cards.
Click to expand...
Click to collapse
correct me if im rong, i thought the mogul supported up to 8gb so why would you need the patch
Originally, it wasn't supposed to. It would only support up to 2GB. Coincidentally, it works, but will have it's days that it won't. This is to ensure that it works constantly.
I am running M$ Voice Command (1.60.4622.0) and did see this on rare occasion on my old 6700 too, but didn't investigate back then. I have not turned on encryption. There hasn't been a problem recognizing the 8GB capacity, just with it completely disappearing. It isn't a large problem, but even one disappearance seems odd.
I'll try collecting some baseline stats on how often it is disappearing by going to it regularly, and then try suggestions to see if things change for the better.
Any suggestions on places I should look beyond using file browsers (stock, Resco) and start>settings>device information>memory>storage card to see if the card is being recognized? I'll also try card re-insert vs. soft boot when it is gone to see if that brings it back. Thanks for the suggestions
eXplicit815 said:
Originally, it wasn't supposed to. It would only support up to 2GB. Coincidentally, it works, but will have it's days that it won't. This is to ensure that it works constantly.
Click to expand...
Click to collapse
i seen ppl say it works fine with 4 gb idk about 8 gb
Ran fine yesterday, saw problem today (last soft reset 1d2h ago). Additional details on symptoms on this particular failure: File browser: sees top level folders on storage card. In some of these lower level folders and files appear, in some not. Nothing consistent with respect to levels down where things start disappearing but I couldn't get to any folders or files more than two levels down. start>settings>system>memory>storage card shows capacity of card as 7782.5MB (correct), same amount as in use (incorrect), and 0 free. Popping the card out and in resolved the problem. Next time it fails I'll see what Pocket Mechanic can see with respect to the card when it goes out.
I did a search on 'storage card disappears'. Seems this is a problem folks experience across phones and WM5/WM6 PPCs. May even be the card. Didn't come across any explanations of the problem or fixes (some registry hacks related to thinking it is a new or old card, that were later discounted in the thread, but even if true, the new/old card isn't the problem as I'd still expect to see files if it were a new card). e.g., http://forum.xda-developers.com/showthread.php?p=1138270. From what I found searching, its something I live with for now. I'm pretty sure it isn't anything specific to 3.16.651.0 ...
Broke my NT screen & replaced but now touchscreen capability doesn't work. I have been trying to return to stock & go from there but am unable to get that done w/o touch.
I am assuming I didn't get a defective screen but cannot be sure.
Anybody have any suggestions for me?
Thank you!
MIGHT<--------- work
sd1 boot--->clock works mod recovery---------------
http://forum.xda-developers.com/showthread.php?t=1446987&highlight=cwm
boot into it(remove) and then insert
sd2 which, contains stock zip,or any other rom
flash that sucker
and hope it works
METHOD 2 (might be easier, but results in root and other apps)
http://forum.xda-developers.com/showthread.php?t=1488035&highlight=cwm
(methods above uses no screen, only side buttons and the n)
please reply because i am interested to see if this works
I can't boot to an sd card. Tried Method 2 & was not able to boot to the card. Flashed the image to the card, put it in the Nook, powered down 8xs & get the blue menu but then can't get the zip image to work.
Sorry, I am a noob in may respects & I'm really foundering here. In method 1 I don't even know how to make a new MSDOS partition table and add a 50 MB FAT32 partition as the first primary partition.
I fear I am up the proverbial creek!
interesting...
method one 50 mb http://forum.xda-developers.com/wiki/SD_card_partitioning
why can you not boot from SD
and
by blue menu do you mean the clock works mod
and what do you mean by 'can't get the zip image to work.' what is happeneing
concern:
well you said that it was a hardware screen damage
so TECHNICALLY the software should work as created since that was 'untouched'
thinking...
Sorry I haven’t gotten back to you; I’ve had company & no time to address this again.
I will try & explain the steps I have taken, although, as I have explained my tech speak is limited at best.
I am using a 2gb sd card (believe it or not I snapped my 32gb card in half while replacing the screen)
I just now tried to use method 1. I thought I followed the instructions exactly found at: http://forum.xda-developers.com/wiki/SD_card_partitioning
but now my computer doesn't detect the sd card at all, nothing when I plug & unplug the card.
Previously when I said 'get the blue menu' yes, I mean clock works mod.
I think somehow during the use of Partition Wizard 7 the card reader on my comp was fried. I bought a brand new 16gb card; when inserted in the adapter, then into the onboard reader, PW7 shows both cards as 'bad disk'
woah woah woah...well first i was 'gone' for a couple of days due to freshman finals. (dont be like...well this young foo aint going to help...cuz i try to)
second--> the chip could not have gotten fried...check if it works with the native software (windows explorer) and with other SD cards
and how is it one snaps the 32gb sd. like you forgot it inside the device...or while taking it out it 'broke'
back to my third post---> and what do you mean by 'can't get the zip image to work.' what is happening
like is it an md5 sum error or...
obviously this is a very technically problematic because by now...other devs would be helping...
Finally figured out sd card reader on my comp quit working - card's okay in different comp. Snapped the 32gb card when removing the back of the NT. (My bad-forgot it was in the tablet & removing back with card in snaps the card in 2)
Finally got the NT returned to stock (Kudos to Ray Waldo.com)
Now I have working stock NT but still no touch capabilities. My best guess is that the touch digitizer of the screen is bad & since warranty was for 30 days seller won't exchange. (It has been 40 days) Seller is not appreciative of the fact that I have been trying to get this thing working & I too was on vacation.
So unless someone has another idea of what might be wrong, I'm up a creep.
I really appreciate your efforts & the help I have received.
From my reading the touch part is not sold with the LCD display. I assume you purchase the digitizing touch part too.
"7" Nook TABLET IPS LCD Screen Display Repair Replacement. This item is the exactly inner IPS LCD screen dispaly (without Touch screen digitizer glass) for Nook TABLET , easy to change, plug into the board, ....."
Most manufactures have internal diagnostics, can you somehow run these? Who ever your vendor was they should be able to get you the manufactures information. If nothing else you may be able to send it to them for testing.
I did take two laptops apart to combine them into one working one, lots of thin flat cables that went directly into connectors. I did observe that some held well, some did not insert fully and some did not stay in very well. Could you problem be a loose cable?
goworley said:
I think somehow during the use of Partition Wizard 7 the card reader on my comp was fried. I bought a brand new 16gb card; when inserted in the adapter, then into the onboard reader, PW7 shows both cards as 'bad disk'
Click to expand...
Click to collapse
Did you ever get this thing fixed?
First, sorry for my bad English. Hope I make myself clear enough for you to understand me.
Second, to the moderators: feel free to move this topic if I posted it on the wrong session. But as you will see reading the following, I believe that the issue I will describe is directly related with the Neatrom - correct me if I'm wrong, but I have reasons to believe that.
So, here it goes:
I have a Samsung Galaxy S2 (i9100), running XXLSJ Neatrom Lite v4.0, and this kernell: 3.0.31-Siyah-s2-v6.0b4+
In december 2012, I bought a MicroSD card (model Sandisk Ultra 32Gb class 10) to install in my i9100, and it rocks.
But 4 weeks ago, when I was playing some games on the phone, I ignored the first battery low warning messages, and kept playing to a point that the phone simply turned off. Completely. I recharged the battery and, after powering the phone on again, it showed a message saying something like "blank sdcard" or something. I had many pictures and important movies on that card, so I decided to not format it; instead, I searched for a way to fix it.
I tried to access the files from my computer - on Windows, no success; on Ubuntu, no success; on Mint, no success. Windows and Linux showed the icon representing the sdcard, but when I tried to open it under Windows, it showed a message saying "this disk is not formated. Do you want to format it?". Linux didn't show any message, and didn't opne a single window to show its content. Nothing. Nada.
Then, my cousin (a geek genius) took my card to test it on his own notebook. He made some long research on the net, and installed a software called TestDisk (http://www.cgsecurity.org/wiki/TestDisk - linux version) to try to recover the partition (or the MBR, I don't know exactly the tech name of this stuff...). He even entered on the software the number of cylinders, sectors and all that stuff to try to achieve sometuing... But after almost two hours reading tutorials, and trying hard to bring that card back to life with no success, he finally gave up, telling me to RMA the sdcard.
Then, I took the card from his hands, and put it aside, giving up too. Half an hour later, accepting the fact that my files was gone forever, I decided to try to format the card on my phone, to see if it would work after being formated. So, I put the card on the phone again, and powered the phone on... And, for my surprise, the card was back to life! For no reason, it decided to work again! With all the movies, all the pictures, all the games, everything was there, untouched!!!!
So, it worked great in the last 4 weeks, fast and nice - recording long HD movies, taking hundreds of pictures, installing huge data games, etc. It worked fine - until two days ago.
Because, two days ago, I was playing again, and again I ignored the low battery warnings, and it happened again! In the middle of the game, the battery ran out, and the phone turned off. Guess what? Yeah, after recharging it and turning it on again, there came that same message, telling me that my sdcard was blank! Again, no success trying to access it from Windows or Linux. And no geek cousin nearby...
(Of course, I had a backup of my files, created just after that first "death").
so, I sent an e-mail to my cousin, asking him about the software he used, and how it used it. He told me about that testdisk software. I downloaded the Windows version of the software, and give a try - no success. The program didn't recognize the drive letter of my "blank" sdcard, because the filesystem was simply not listed by the program. So, I went to the site, and I read that, under Linux, it was possible to force Testdisk to try to repair filesystems that was not shown in the list, by using a command line telling the software to look for the device through this mounting point (a folder inside /dev/). Linux stuff, I wont go any deep on this here.
So, I decided to restart my notebook, to boot on Linux to try that method. Guess what again? Suddenly, Windows recognized the sdcard again! I just ran the TestDisk utility, with no success - no command was used, I just ran the program, and since it didn't recognize the card, I closed the program. Nothing was done.
But, given the fact that the card was dead twice in the exact circumstantes (battery wearing completely off), and given the fact that the card came back to life after a simple run of the software TestDisk, I refuse to believe that it was a simple coincidence; I am not a geek, not a linux or android expert, nor a hardware wizzard, but my little experience tells me that it is possible that the android system locked the SDcard filesystem in a way that, after a sudden energy cut, it needed some sort of "logical shock" (made by TestDisk, even without any changes or command being called by the user, thats me).
I believe that this issue is part NeatRom's (or maybe kernell's) fault, because in stock roms, the system would close the app and close all sdcard access before turning the phone off to prevent issues like this one.
Again, I must repeat: I am not a technician, not an expert, so chances are I am wrong - very wrong. But I believe that my suspicions makes some sense, and woths to be investigated - or cleared out. And, of course, chances are that the card is deffective - and I already called RMA service from Sandisk. And I made another backup right now. But, I insist: everything is working: no movie corrupted, not a single file is corrupted... So, I still have a doubt here: was this issue cause by a deffective card, or was it cause by the sudden turn-offs?
Before you ask: no, I didn't test playing to the end of battery using another sdcard. By the way, I will never play to this point anymore. And yes, the card is still working!
Sorry for the VERY LONG POST. But I think that this testimonial may be of some value to the rom and kernell developpers.
I can honestly say i have never heard of a Rom or Kernel damaging a memory card, could be yours just developed a fault??
Galaxy s2 said:
I can honestly say i have never heard of a Rom or Kernel damaging a memory card, could be yours just developed a fault??
Click to expand...
Click to collapse
Not the rom itself, but possibly some "features" of this or any other rom related to how it handles battery. I will try to make myself as clear as possible...
I know that in stock roms it is not possible to shoot photographs using flash when battery level is under 15% - this is to prevent sudden turn-off of the phone. And I know that some roms uses some tweaks that allows the user to take pictures using flash under this 15%. This is a thing that most users can think is an improvement - but we know that it is dangerous to use battery in a not-so-controled way. The history I told on the first post is a prove of it!
So, my suspictions is that, in some way, some rom configurations (or kernell configurations) may be allowing the user to play a high-power-demanding game or app to the end of battery charge - when, instead, it should close all the apps after the first warning, and before shutting down the phone. In other words, some roms let the decision up to the user - and if the user is (like me) distracted with some game, and forgot or bypass the first warning, he becomes a victim of this own distraction, wearing all the juice without thinking about closing the apk and shuting down the phone in the correct manner.
So, the question is: are there some rom tweaks that could POSSIBLY be the reason for this kind of issue?
Hope I made myself clear now, despite my horrible "engrich"...
So, I originally had this posted under the Nook Color section, but apparently I was wrong in thinking what I had was a Nook Color (despite the box it was purchased in saying Tablet (color) and google telling me the same thing). Regardless, here is my problem.
I recently received a used Nook from a family member. They had bought a new tablet, and didn't need the Nook any longer. The problem with the Nook, however, is it would no longer turn on or even charge. After opening the back (and thus voiding the warranty), I discovered the wires connected to the power button had come loose. I reattached them, put the Nook back together, plugged in the charger and turned it on. Everything seemed fine, until I tried to erase it.
I've tried several different attempts, from simply tapping 'erase and deregister' to holding the power and home buttons, and pretty much every other way B&N's tech support told me. Each time, I get the same error message telling me to try again or contact customer support.
Likewise, any changes I make to the Nook (wallpaper, deleting some of the previous owner's books, etc) revert back to the way they were before each failed attempt as well as after simply turning the Nook off and back on.
I even tried connecting the Nook to my computer via usb cable to delete the old books, however once I eject and disconnect the nook, all the books that were deleted remain, and the books I attempted to add weren't there.
Finally, a problem with the SD card. If I have any .epub books on it, after a few minutes the Nook blackscreens and remains unresponsive until I hold the power button for 20 seconds, release, then press again to turn it back on.
The model number is BNTV250-A. And I have tried every option I can find through google search to repair this thing myself, and am at an utter loss. Though, most of those attempts were from when I thought this was a Nook Color, so perhaps I've just been trying the wrong methods, but I've attempted the 8 failed reboots, as well as attempting to boot from the SD card. Neither of which worked.
Now, B&N tells me the Nook is pretty much trashed and that I need to upgrade to a new one. I refuse to believe this until I've tried every option I can find. So, if someone can give me any help on trying to get this thing fixed, I'd be greatly appreciated, or if I'd just be better off buying a new tablet altogether.
I will continue to google possible solutions while waiting for someone to come up with something here.
sounds like you'd be better off buying a different unit. the model you stated (BNTV250-A) is indeed a Nook Tablet, probably a 16GB model (i have the same one) but yeah it sounds as though it's pretty much FUBAR at this point. sorry.
I was afraid of that. I mean, it's still good for playing movies and reading pdf files and such. But loading epub files onto the sd card causes it to go all crazy and such.
The thing that gets me is the rooting issue. I just tried rooting again, and absolutely nothing changes. It just keeps going right back to the way it was when my mother gave it to me. I even attempted to use the recovery mod to completely wipe all user data from the NT, with the same result.
I am at a complete loss and am willing to go with your pretty accurate description. This thing is FUBAR.
It's a known issue. Your only option is to boot from sdcard. Here you can find recent images
Hi guys, having serious issues here and hoping someone can point me in the right direction to resolve them.
In all 'Smart Phones' I've had including the S3, S5, S7 etc I've been able to copy the entire contents of the internal storage to the external SD card or my Desktop PC with no issues at all, but on this S9+ It gets about half way through copying then stops, the 'copying' dialogue just disappears. I've tried in normal powered on mode, booting into TWRP and all result in the same problem, it's most annoying, I want to backup the entire contents, reset/reflash the ROM and then copying the internal storage stuff back but it just won't let me, unless I go through the tedious route of copying folder-by-folder...
I thought it might be an issue with my PC but just tried it on my laptop with the same result....
Anyone else having this problem? found a resolution?
Thanks
Are you copying the content via cable or wireless connection? Try switching this, also notice when the process breaks, copying which folder or file, try excluding that as well.
Thanks for the reply, ethernet cable mostly, on a gigabit network, I have tried wifi and that failed too, basically I have about 105 files, mostly folders but a few about 20-ish standalone files (documents etc) obviously the actual file count runs into the thousands, copying always gets to about 55 or 56 out of that 105 then breaks, every single time, I have the same issue going back too, from the PC or SD card to the internal storage, I didn't have this problem on my S7 Edge a couple of weeks ago. I thought it might have been caused by me flashing a debranding firmware (xeu from H3G and back again) but I always flash then factory reset when I do anything like that ( that comes from my old HTC HD2 custom ROM days ) but I've had this issue from day one on the S9+ as there was no root when I got mine I just copied my files over to go unrooted for a while until the Devs plied thier magic, well tried too, as that's when this failure malarky started. This is currently my 2nd S9+ with a 3rd on it's way and will be here on Monday. I've convinced myself that there are some serious hardware flaws on the S9+ and I'm realy hoping someone could say do this, do that and it works....
I guess it could also be Oreo, I have heard rumours that it's not the best Android version to have been released - I'm hoping that one or two of the many very knowledable people on here could help me, if not that I hope the replacement has come from a different batch and is okay, fingers crossed eh?
The Issues I'm having with this device is seriously giving my loyalty-to-Samsung mojo a severe knocking...