I'll put the link the the vid I followed (but only get halfway through whole process) and think I've missed something but not sure what. The guy appears to have good luck with his method, but I didn't. I cannot get the screen with the "box"
Here are the two messages I get after last step and reboot:
1. Nook encountered a problem that requires a system restart (I click "ok")
2. Then after I click "ok" I get this message:
Your Nook could not restart. Please Try again later. Or contact Customer Support.
The only part of the video I've found that I did on my own is that he doesn't tell you to plug the power cord into an outlet but it seems logical. Unless for some weird reason I'm supposed to plug it back into the usb on my laptop.
Any help very, much appreciated, denise
denise1952 said:
I'll put the link the the vid I followed (but only get halfway through whole process) and think I've missed something but not sure what. The guy appears to have good luck with his method, but I didn't. I cannot get the screen with the "box"
Here are the two messages I get after last step and reboot:
1. Nook encountered a problem that requires a system restart (I click "ok")
2. Then after I click "ok" I get this message:
Your Nook could not restart. Please Try again later. Or contact Customer Support.
The only part of the video I've found that I did on my own is that he doesn't tell you to plug the power cord into an outlet but it seems logical. Unless for some weird reason I'm supposed to plug it back into the usb on my laptop.
Any help very, much appreciated, denise
Click to expand...
Click to collapse
Mmm... Video is not playing?
nmyshkin said:
Mmm... Video is not playing?
Click to expand...
Click to collapse
I'll just post the youtube URL and see if that works, sorry about that, denise PS I used the youtube icon last time. Let's see if just the "link" icon will work
https://www.youtube.com/watch?v=QBvGLHUFOgg
Ok, looks like that works, new to this site, or at least posting to it If you know anything about the rooting I could sure use some help. I have it all finished but, for example, I'm having issues with many of the apps on playstore not being available to me. I get the "this app is not compatible with version". Something like that. I have been reading about possible fixes but one is something called Cyanogenmod, and I can't get the app in the store. It's supposed to do some sort of fix. Then I tried a took called BuildProp Editor but when I go into my build.prop file it doesn't list one of the strings I'm supposed to change (product Model).
With the buildprop editor, you change the "model" to something the app would be compatible with. Samsung to Nexus etc. Anyway, I hope you can see the video if you either need to root something, or, you want to comment/give me some feedback
PS I just read your "signature" and you obviously know a lot about this Hope you drop back in, Denise
denise1952 said:
I'll just post the youtube URL and see if that works, sorry about that, denise PS I used the youtube icon last time. Let's see if just the "link" icon will work
https://www.youtube.com/watch?v=QBvGLHUFOgg
Ok, looks like that works, new to this site, or at least posting to it If you know anything about the rooting I could sure use some help. I have it all finished but, for example, I'm having issues with many of the apps on playstore not being available to me. I get the "this app is not compatible with version". Something like that. I have been reading about possible fixes but one is something called Cyanogenmod, and I can't get the app in the store. It's supposed to do some sort of fix. Then I tried a took called BuildProp Editor but when I go into my build.prop file it doesn't list one of the strings I'm supposed to change (product Model).
With the buildprop editor, you change the "model" to something the app would be compatible with. Samsung to Nexus etc. Anyway, I hope you can see the video if you either need to root something, or, you want to comment/give me some feedback
PS I just read your "signature" and you obviously know a lot about this Hope you drop back in, Denise
Click to expand...
Click to collapse
OK, so from what I can see in the video you end up with a rooted Nook Tablet, an old version of the Market, and a new launcher (maybe a few other things I didn't notice). The problem is that you now have a rooted android tablet that is running Android 2.3(?). And so what was the point? Eventually the old version of the Market won't even let you in and even if it did, your selection for apps is limited with the current Android version now being 7.0
So....you did this much and that means you can do the little more needed to not only root your tablet but also to install a new ROM that can update it to a more recent Android system. I'm no expert, but I have been around the block a few times with this device. You can "easily" flash either Cyanogenmod 10, 11 or 12 (Android Jellybean, KitKat, or Lollipop). I started with 10 and was happy with that for a long time until I got curious about a more up-to-date system. I skipped over 11 and went straight to 12.1. I'm more or less satisfied but I think 12 is pushing the limits of the hardware. It's a little wobbly sometimes.
If I were you, I'd pick the last stable version of CM 11. The absolute best guides on XDA for flashing these ROMs on the Nook Tablet were written by digixmax. The one for CM 10 is here. The one for CM 11 (and sort of 12) is here.
Read carefully and take your time. The result is well worth the effort, IMHO. A rooted tablet with the hardware capabilities of the NT running Android 2.3 is not.
nmyshkin said:
OK, so from what I can see in the video you end up with a rooted Nook Tablet, an old version of the Market, and a new launcher (maybe a few other things I didn't notice). The problem is that you now have a rooted android tablet that is running Android 2.3(?). And so what was the point? Eventually the old version of the Market won't even let you in and even if it did, your selection for apps is limited with the current Android version now being 7.0
So....you did this much and that means you can do the little more needed to not only root your tablet but also to install a new ROM that can update it to a more recent Android system. I'm no expert, but I have been around the block a few times with this device. You can "easily" flash either Cyanogenmod 10, 11 or 12 (Android Jellybean, KitKat, or Lollipop). I started with 10 and was happy with that for a long time until I got curious about a more up-to-date system. I skipped over 11 and went straight to 12.1. I'm more or less satisfied but I think 12 is pushing the limits of the hardware. It's a little wobbly sometimes.
If I were you, I'd pick the last stable version of CM 11. The absolute best guides on XDA for flashing these ROMs on the Nook Tablet were written by digixmax. The one for CM 10 is here. The one for CM 11 (and sort of 12) is here.
Read carefully and take your time. The result is well worth the effort, IMHO. A rooted tablet with the hardware capabilities of the NT running Android 2.3 is not.
Click to expand...
Click to collapse
Yes, 2.3 Gingerbread. I get things done but I don't understand half of what I do. Thanks so much for the explanation. The more I searched for info, the more I kept see Cyanogenmod so figured that was going to help in some way.
Ok, do I reset the NT again, or just go from where I am at this point?
I don't know if I'm even supposed to be on this forum since I read that it is for "developers". I wouldn't have gotten the info you just gave me anywhere else that I know of though. Hope it's ok for me to stay and learn.
I'll go with the 11 because I understand that the NT is older (bought it in 2011) so no, I don't want to push my luck with it either. I have a new Fire Tablet 7, yuck, but I did get the Playstore on it at least. It works fine, I just like the whole feel of my Nook (payed a lot more for it of course).
Thanks again, and I'll post here on my progress, or lack thereof denise
denise1952 said:
I get things done but I don't understand half of what I do.
Click to expand...
Click to collapse
Yep, that's me.
Ok, do I reset the NT again, or just go from where I am at this point?
Click to expand...
Click to collapse
Reset.
I don't know if I'm even supposed to be on this forum since I read that it is for "developers". I wouldn't have gotten the info you just gave me anywhere else that I know of though. Hope it's ok for me to stay and learn.
Click to expand...
Click to collapse
There are the developers, and then there are the people like me who grovel at their feet. I have learned soooooo much here.
Good luck. It sounds like you can do this "easily" At any rate, you can always ask questions.
nmyshkin said:
Yep, that's me.
Reset.
There are the developers, and then there are the people like me who grovel at their feet. I have learned soooooo much here.
Good luck. It sounds like you can do this "easily" At any rate, you can always ask questions.
Click to expand...
Click to collapse
Ok, will do I am bummed as I have to do some errands, but can't wait to get back and go for this. Already downloaded the Mini Partition Tool, totally new to me, partitions but I do love to learn, ttyl, and thank you so much, again!
Just a bit of an update for anyone interested I got through this part of the instructions from digixmax:
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on SD card a Primary FAT32 partition, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows
Click to expand...
Click to collapse
But at the end, I went in to look for the Drive and it said "Boot E" because that's where I had my SD Card. I couldn't find anywhere it said read/write accessible though? I figure I was looking in the wrong place as the directions says "under Windows" so I even looked to see if something was listed under my Windows file in File Manager.
Anyway, kind of toast right now, I'm tired and going to try again in the a.m. The making of the Partition in the Minitool didn't seem hard at all, if I did that right.
Thanks again for the help, I'll check back tonight for any replies, and then again in the a.m. denise
denise1952 said:
Just a bit of an update for anyone interested I got through this part of the instructions from digixmax:
But at the end, I went in to look for the Drive and it said "Boot E" because that's where I had my SD Card. I couldn't find anywhere it said read/write accessible though? I figure I was looking in the wrong place as the directions says "under Windows" so I even looked to see if something was listed under my Windows file in File Manager.
Anyway, kind of toast right now, I'm tired and going to try again in the a.m. The making of the Partition in the Minitool didn't seem hard at all, if I did that right.
Thanks again for the help, I'll check back tonight for any replies, and then again in the a.m. denise
Click to expand...
Click to collapse
On my Win 10 machine the "properties" option from the context menu doesn't say anything about r/w for the SD card, but it does show the space used and the space available. I think you're good to go if that's what you are seeing. You can't have done all the manipulations in Mini Partition Wizard and not had write access to the card, so it's not like it's locked or something odd.
Onward!
nmyshkin said:
On my Win 10 machine the "properties" option from the context menu doesn't say anything about r/w for the SD card, but it does show the space used and the space available. I think you're good to go if that's what you are seeing. You can't have done all the manipulations in Mini Partition Wizard and not had write access to the card, so it's not like it's locked or something odd.
Onward!
Click to expand...
Click to collapse
Ok, gotcha! Onward it is:highfive: lol
Ok, spent all morning trying to figure this out myself, and gave up and decided to come back here and ask what to do.
For some reason, I cannot find my unallocated space, it's not showing like the first time I ran through #1 step to "create on SD Card a FAT32 partition, etc. I did reformat the SD Card so that it was a fresh start. I did something wrong, but I can't figure out.
I read that on the MiniTool Wizard "create" is not enabled unless I have unallocated space, so that's my issue. I cannot get that "create" option enabled. I'll attach a snip of what I see at this point. Maybe that will help. I do select the Disk 2 and look down under the "partition" menu and "create" is greyed out. Then I also tried right clicking on the Disk 2 to see if it would show there but it still is disabled (please see attached please) Any help so appreciated, denise:
denise1952 said:
Ok, spent all morning trying to figure this out myself, and gave up and decided to come back here and ask what to do.
For some reason, I cannot find my unallocated space, it's not showing like the first time I ran through #1 step to "create on SD Card a FAT32 partition, etc. I did reformat the SD Card so that it was a fresh start. I did something wrong, but I can't figure out.
I read that on the MiniTool Wizard "create" is not enabled unless I have unallocated space, so that's my issue. I cannot get that "create" option enabled. I'll attach a snip of what I see at this point. Maybe that will help. I do select the Disk 2 and look down under the "partition" menu and "create" is greyed out. Then I also tried right clicking on the Disk 2 to see if it would show there but it still is disabled (please see attached please) Any help so appreciated, denise:
Click to expand...
Click to collapse
Been awhile since I did this, but if you reformat an SD card that has separate partitions (as yours appears to), you will not get back all your space. What I'm saying is that there should not be two separate memory entities on that SD card at this point. The section marked by the "*" needs to be merged with the section called "Boot". That large chunk is needed to hold all the files you will use to flash the new ROM.
If you right-click on either partition near the top of the display where it shows the two sections, the context menu contains a "merge" option. Bottom line is, you need one partition on the SD card and right now the bulk of the storage space is locked up.
nmyshkin said:
Been awhile since I did this, but if you reformat an SD card that has separate partitions (as yours appears to), you will not get back all your space. What I'm saying is that there should not be two separate memory entities on that SD card at this point. The section marked by the "*" needs to be merged with the section called "Boot". That large chunk is needed to hold all the files you will use to flash the new ROM.
If you right-click on either partition near the top of the display where it shows the two sections, the context menu contains a "merge" option. Bottom line is, you need one partition on the SD card and right now the bulk of the storage space is locked up.
Click to expand...
Click to collapse
Ok, I'll do that, saw the merge option. So hopefully, this will bring back unallocated space then. I should have asked how much I need. The SD card is 8 GB, probably don't need more than a couple at the most I'm thinking. I'll go give your direction a shot, thanks much for hanging in there with me, denise
OK, you need to take a breath and stop. I've just come away from another thread in which the poster decried the disappearance of all the Cyanogenmod stuff. I knew they had died but I didn't realize everything would disappear so fast...
That means you need to source the most critical component from somewhere. One option is a new post on this board for the critical files. There is also a fellow who was developing his own related ROMs, both internal and SD card versions. I'll search for that and add it to this post in a bit.
Edit: here you go https://iamafanof.wordpress.com/category/nook-tablet-2/
nmyshkin said:
OK, you need to take a breath and stop. I've just come away from another thread in which the poster decried the disappearance of all the Cyanogenmod stuff. I knew they had died but I didn't realize everything would disappear so fast...
That means you need to source the most critical component from somewhere. One option is a new post on this board for the critical files. There is also a fellow who was developing his own related ROMs, both internal and SD card versions. I'll search for that and add it to this post in a bit.
Click to expand...
Click to collapse
Well all is good because I decided the same thing when I left here last time. I did try to do the partition thing and ran into another "block" so just put it away, and got into something else
I appreciate your letting me know, nmyshikin I'll be subscribed to the thread, and keep watching for any new additions. I'm not in a hurry since I have my Fire Tablet, and working on the Nook is just going to be a fun project, I hope, at some point And I did learn some things about partitions, and especially about SD Cards Denise
G0ldengirl68 said:
I'll just post the youtube URL and see if that works, sorry about that, denise PS I used the youtube icon last time. Let's see if just the "link" icon will work
Ok, looks like that works, new to this site, or at least posting to it If you know anything about the rooting I could sure use some help. I have it all finished but, for example, I'm having issues with many of the apps on playstore not being available to me. I get the "this app is not compatible with version". Something like that. I have been reading about possible fixes but one is something called Cyanogenmod, and I can't get the app in the store. It's supposed to do some sort of fix. Then I tried a took called BuildProp Editor but when I go into my build.prop file it doesn't list one of the strings I'm supposed to change (product Model).
With the buildprop editor, you change the "model" to something the app would be compatible with. Samsung to Nexus etc. Anyway, I hope you can see the video if you either need to root something, or, you want to comment/give me some feedback
PS I just read your "signature" and you obviously know a lot about this Hope you drop back in, Denise
Click to expand...
Click to collapse
Good video, now if i could only find the files. Nothing but dead links everywhere.
Related
Hi,
I received my GTab in the mail yesterday and was very excited to start messing around with it. When I first turned it on I noticed the touch screen was not very responsive, but assumed it was just what everyone was talking about with the stock rom. After a little bit of messing around I was able to get the update which I figured would solve the problem.
Gradually it is becoming less and less responsive, to the point where I can only really click the very bottom of the screen, nothing else responds to me clicking it, I can occasionally get to the file manager after trying for awhile but can't click any folders in there. It is even difficult to reboot because I can't click "Power down" after I've hit the power button. The buttons on the side work fine and can easily get back to the home screen. I am wondering if this is an issue with the stock rom or if I am going to need to return it. It is basically unusable.
Any suggestions would be appreciated.
-Myles
place an empty file on the root of the sdcard called "calibration.ini". Reboot tab. Dont touch screen until the tab is completely booted. Delete calibration.ini
I appreciate the help. I have an sd card in the slot and I am hooked up to my PC with the USB.
This probably sounds dumb, but how do I get this file onto the sd card (I've never done this)
Ok, here is what I have done which did not seem to work:
-Used a blank text document and named it "calibration.ini"
-connected to my G Tab and put the file in removable disk/update/sd card
-rebooted and allowed to load
-deleted file
This did not seem to work but I am sure that is not the process, any clarification would be greatly appreciated!!
Thanks again!
MylesG said:
Ok, here is what I have done which did not seem to work:
-Used a blank text document and named it "calibration.ini"
-connected to my G Tab and put the file in removable disk/update/sd card
-rebooted and allowed to load
-deleted file
This did not seem to work but I am sure that is not the process, any clarification would be greatly appreciated!!
Thanks again!
Click to expand...
Click to collapse
the calibration.ini has to be in the tablet's internal memory
The file has to be on the root of the internal or external. Make the file is not named calibration.ini.txt
thebadfrog said:
The file has to be on the root of the internal or external. Make the file is not named calibration.ini.txt
Click to expand...
Click to collapse
Thanks again for helping.
Checked file, it's not named calibration.ini.txt. I think my issue might be where I am putting it? What do you guys mean when you say the "root" of the internal or external?
The file needs to be in the root meaning outside of every folder.
When your tab is connected to your pc. You click on removable disk. Paste the field right there don't go into any folders
the base....the beginning....the start....on windows c:/......on your tab sdcard/
Thanks to everyone for their help.
I actually think I have been doing it correctly and parts of my screen are simply dead. It is really bad, even worse than a Youtube video where people commented in forums they were "glad theirs wasn't that bad".
The parts of the screen that do work actually seem to be more responsive while the non-working parts are still unresponsive, which lead me to believe it is defective and I will have to return it.
I followed all of the steps and even downloaded an app from this forum located here:
http://forum.xda-developers.com/showthread.php?t=934500
ran the app and still nothing.. so thanks again and hopefully my replacement will work much better
I had deadspots on my screen. I just sent it back today.
Hi, I'm running the latest rootfs and Ril on Rhod400, even though this issue is almost definitely not related. I think that the battery died in middle of the night (I forgot to plug it in), and when I turned it on after charging it, a lot of apps started to Force-Close. This happens even after a reboot.
Thanks for all the help.
yelped said:
Hi, I'm running the latest rootfs and Ril on Rhod400, even though this issue is almost definitely not related. I think that the battery died in middle of the night (I forgot to plug it in), and when I turned it on after charging it, a lot of apps started to Force-Close. This happens even after a reboot.
Thanks for all the help.
Click to expand...
Click to collapse
Delete the data.img, let the system create a new one. Problem solved.
So it got corrupted? I feared so. At the rate I'm re-creating Data Images, I should buy the Pro version of Titanium Backup for Batch Restore.
yelped said:
So it got corrupted? I feared so. At the rate I'm re-creating Data Images, I should buy the Pro version of Titanium Backup for Batch Restore.
Click to expand...
Click to collapse
That's what I did! I found myself using the app so frequently, I decided to pay for it.
Advanced users willing to do a little research will also find that sometimes the fix_permissions script will fix your data.img in these situations, it fixed mine a few days ago.
rpierce99 said:
Advanced users willing to do a little research will also find that sometimes the fix_permissions script will fix your data.img in these situations, it fixed mine a few days ago.
Click to expand...
Click to collapse
Yea, I always forget that. I haven't had to blast out a data.img in a while tho... Hrm.
yelped said:
Hi, I'm running the latest rootfs and Ril on Rhod400, even though this issue is almost definitely not related. I think that the battery died in middle of the night (I forgot to plug it in), and when I turned it on after charging it, a lot of apps started to Force-Close. This happens even after a reboot.
Thanks for all the help.
Click to expand...
Click to collapse
Happened to me also after it paniced and rebooted one day. I had to install all of the apps that force closed over again after uninstalling them. Seems like info got corrupted. I didn't want to start from scratch, especially since I just successfully got my work VPN working, so I just spent the time to uninstall and reinstall the stuff as I go. Have no clue what causes this other than something got corrupted.
slickdaddy96 said:
Happened to me also after it paniced and rebooted one day. I had to install all of the apps that force closed over again after uninstalling them. Seems like info got corrupted. I didn't want to start from scratch, especially since I just successfully got my work VPN working, so I just spent the time to uninstall and reinstall the stuff as I go. Have no clue what causes this other than something got corrupted.
Click to expand...
Click to collapse
I ran into a similar issue. My phone hard locked after running Android for the better part of a day. When I rebooted it ran extensive disk checks on the system. It still does every time I boot and I am get force close messages constantly. Windows also found and fixed errors with the FAT32 partition on the card. It's possible my card is dying but I also didn't notice any of that until the forced reboot. It didn't say what file was damaged but I can take a guess.
I believe that the FAT32 file system on the card was corrupted because files were open when I was forced to reboot. Because the linux file system is hosted as a file on the fat32 partition, it is subject to damage if the host file system gets messed up. It's sort of like when MS offered the option in DOS to compress your hard drive. It was all stored as a giant compressed file on your disk. If something happened to the integrity of that file it caused all sorts of problems.
This is why I use a partitioned build...
might be a stupid question but what is that ^
manny05 said:
might be a stupid question but what is that ^
Click to expand...
Click to collapse
Instead of using looped files (system.ext2 file is really an entire file system that is 'loop mounted' within Linux/Android) you use native partitions.
So a separate partition for data, separate partition for system, etc. It's a little more difficult to setup, but in theory it causes less corruption. Not sure if it's true or not, hyc is pretty convinced it does .
arrrghhh said:
Instead of using looped files (system.ext2 file is really an entire file system that is 'loop mounted' within Linux/Android) you use native partitions.
So a separate partition for data, separate partition for system, etc. It's a little more difficult to setup, but in theory it causes less corruption. Not sure if it's true or not, hyc is pretty convinced it does .
Click to expand...
Click to collapse
I've been running with the same data partition since the middle of January, haven't needed to recreate it even once. It boggles my mind how often you tell people to blow away their data.img and start over whenever they run into problems. That just ain't right, and an approach that encourages that style of problem-solving is inherently flawed, IMO. And a build layout that leads to that type of solution is also inherently flawed.
Plus the simple existence proof - my /data partition is fine, despite having reinstalled /system several times, switching between original FRX05 and FRX06, rewritten rootfs scripts, plus all of the built-from-scratch system images I've tested, replacing framework.jar, etc. etc... My SDcard has seen a lot of churn, but all of my downloaded apps, settings, and data have come thru unscathed.
A couple times I've needed to run fix_permissions. But now with my current framework and rootfs that does a clean shutdown and unmount of /data, I haven't needed that in a while either.
Oh, and also, with a partitioned build, you get full use of USB mass storage. Everything just works.
highlandsun said:
I've been running with the same data partition since the middle of January, haven't needed to recreate it even once. It boggles my mind how often you tell people to blow away their data.img and start over whenever they run into problems. That just ain't right, and an approach that encourages that style of problem-solving is inherently flawed, IMO. And a build layout that leads to that type of solution is also inherently flawed.
Click to expand...
Click to collapse
I agree, it's horrible troubleshooting - but it works, and until we get a solid fix then there's really not much to do...
I know you love your partitions, but that's not going to be for everyone. Anyone can do it, and how many do?
highlandsun said:
Everything just works.
Click to expand...
Click to collapse
LOL at this statement. I won't poke holes in it, c'mon guy, that's just silly.
arrrghhh said:
LOL at this statement. I won't poke holes in it, c'mon guy, that's just silly.
Click to expand...
Click to collapse
Ok fine. 500 patches later, and everything works...
Sent from my TP2 using Tapatalk
highlandsun said:
Ok fine. 500 patches later, and everything works...
Click to expand...
Click to collapse
Heh, much more accurate statement .
Also good to note - everything works, related to USB mass storage, etc. This isn't some magic voodoo fix for BT, so don't take this out of context people!
rpierce99 said:
Advanced users willing to do a little research will also find that sometimes the fix_permissions script will fix your data.img in these situations, it fixed mine a few days ago.
Click to expand...
Click to collapse
Nearly all other post-crash forceclose issues seem to be database corruption.
Android seems to like to store a LOT of stuff other than contacts (including call logs) in the contacts database. As a result it tends to be more prone to corruption.
Piece of advice - when complaining about an issue like this where obtaining a logcat is possible, please do so. (A logcat would be able to narrow down exactly where your problems likely were.)
DB corruption can still happen even on partitioned builds. I forget where the best HOWTO for this is, but it involves partitioning your SD card such that:
Partition 1 is FAT (main sdcard stuff)
Partition 3 is ext2 (system partition)
Partition 4 is ext2 (data partition)
I can provide a reasonably good HOWTO for doing this on a Linux box when I return from business travel, can't help the Windows-only users.
fix permission script? where can i find more about this?
just noticed today a file, .tcookieid (33 bytes in length, dated yesterday, opened file, about 30 characters of Hex), has appeared on my M8 in every folder on my SD card, and is also on the root dir. anyone know what it is?
Have you recently installed ifonts app?
I saw that I also had this file throughout my sdcard.
The only thing I can think of is that it has something to do with how ifonts deals with replacing and/or backing up your current Fonts.
I found your post after a google search about it. But there is not much info about it (that I can find)
It may be that everyone knows what these .tcookied files are and me and you are a pair of idiots lol.
But I figured I'd post just so you wouldn't feel on your own!
I'm gonna keep searching for answers and if I find anything I'll let you know.
All the best rich
whoamigriffiths said:
Have you recently installed ifonts app?
I saw that I also had this file throughout my sdcard.
The only thing I can think of is that it has something to do with how ifonts deals with replacing and/or backing up your current Fonts.
I found your post after a google search about it. But there is not much info about it (that I can find)
It may be that everyone knows what these .tcookied files are and me and you are a pair of idiots lol.
But I figured I'd post just so you wouldn't feel on your own!
I'm gonna keep searching for answers and if I find anything I'll let you know.
All the best rich
Click to expand...
Click to collapse
there could have been an update to ifonts recently, in the past few days, cant really remember as i have so much stuff getting updated daily. but ifonts makes sense as to what is making this small file. its harmless anyway, just wondered why it was appearing. surprised no one else has picked up on it here on XDA (apart from ourselves)...
Hello there,
Even i stumbled upon this post from the Google keyword query, my SD card was displaying as being damaged, so i was closely examining the contents of my SD card and i found this newly created file.
It was only in the root path of the SD card, nowhere else.
Even i think that this file might have belonged to iFonts, i have uninstalled the app and removed the file after iFont messed up my factory font restoration pretty badly.
same here
On every folder on my sdcard appeared a file called .tcookieid with a strange code inside
I just installed some new application this afternoon, i am 100% sure that i hadnt it some hours ago.
If someone know what is the cause or what is this please let me know.
I cant find nothing on google
Just found it myself..delete some of it..i hope it doesnt affect my files.....curious?????
Sent from my LG-D802
Well iFont has never even been near my device, I hadn't even heard of it until this thread. So either something else creates it too or it's nothing to do with iFont.
These little buggers are all over my SD card and internal storage.
I have the same issue on my LG G3.
I've never heard of iFonts, So why there are so many .tcookieid files all over my Internal AND External SD cards?!
krashd said:
Well iFont has never even been near my device, I hadn't even heard of it until this thread. So either something else creates it too or it's nothing to do with iFont.
These little buggers are all over my SD card and internal storage.
Click to expand...
Click to collapse
+1
Totally same
i have it all over my sd card
+1, Z2, no IFonts ... weird ...
find . -type f -name ".tcookieid" -exec rm -f {} \;
Not sure what it is. I found one website which gave information stating that it's recognized as a form of a Trojan virus that collects info and sends it somewhere. Can't verify that, however, if you want to remove them all then open up terminal, change directory to root of internal sdcard and copy paste the command above. Do the same for external sdcard as well.
I haven't seen them come back yet, but if it does, then best believe I have every intention of wiping my device out and restoring with a pure stock Rom.
EDIT: I noticed that it's not just the internal and external storage. Its everywhere on the device. However, I still have not seen it come back on my device since I have removed them.
same issue, not that alarming
I believe they are a direct link to a cookie on websites to keep track of your browser traffic, lots of websites use them, some more aggressively than others, I just delete them through 7zipper 2.0. If you stay on top of it, check once a week, it doesn't get too out of hand.
Read this article; type in your browser "what is a cookie?' And click the link, ".... All about cookies" I can't post links yet, sorry.
Correct me or add to if you find anything else
simes6600
simes6600 said:
just noticed today a file, .tcookieid (33 bytes in length, dated yesterday, opened file, about 30 characters of Hex), has appeared on my M8 in every folder on my SD card, and is also on the root dir. anyone know what it is?
Click to expand...
Click to collapse
It's more of a headache than a threat, its a file that allows websites to keep up with browsing history on websites to give suggestive sites on your mobile browser through their cookies. Read this article and put 2&2 together. Type in "All about cookies" in your browser, I can't post links yet, sorry. I just monitor my files closely and it doesn't get out of hand checking once a week, but that would depend on how much you surf and what sites you go to. Hope this helps!
Fill me in on any extra details
krashd said:
Well iFont has never even been near my device, I hadn't even heard of it until this thread. So either something else creates it too or it's nothing to do with iFont.
These little buggers are all over my SD card and internal storage.
Click to expand...
Click to collapse
Me too never had that app but many others have come and gone. I have this file and many others stored in "miscellaneousfolder" or whatever on my Samsung Galaxy s5. I'm going on a deleting spree and still the numbers don't add up and oddly enough the bar reflecting the slices of memory shows a larger, I believe more accurate, slice of free space than my phone is telling me. Ugh I'm just gonna get a bigger SD card it'll probably solve everything.
How do I remove .tcookieid files?
I also have this problem. The files are all over my internal SD card and I need to get rid of them. Are they dangerous files?
I'm pretty sure it is caused by games that offer all sorts of in-app free stuff if you watch videos and such. As the name suggests it's a tracking cookie.
Sent from my LG G3-D855
.tcookieid
I too have found this file, it came from xmodegame which i had install for clash of clan. I think the file contain some kind of ID, for further exchange of data, this app get root permision and voilate privacy by tranmiting other data too. I have install in rooted device, my suggetion to refresh the ROM. Rest phone works only with non rooted device with root and also granted root, my guggetion is that refersh your ROM asap. 5his is leach (worm).
It is a kind of permanent marking. For each directory, the file has the same contents. After installation Xposed with xprivacy and refusal to provide android id, my device has been so marked. It is best to install the new clean rom.
Is it anyhow lethal to my data or my sd card .? should i worry about it .? help will be appreciated
Hi everyone.
So I have an Android car receiver (DV638A, otherwise known as AN6B01). It runs 2.2 Froyo. I've modded it to improve the Android experience, and it's pretty good I must say. I have root permissions, I froze most of the annoying stock apps, installed a custom launcher and some ICS style visuals, etc.
But there's just ONE thing I haven't been able to do that I really want to. I've been researching and experimenting with it for days!
I use Google Play Music (version 5.2 which is the latest supported version for Froyo) and it stores downloaded music to the internal SD card. On this device, the internal SD card is only 2 GB which is not huge. However, it also has a full-size SD card slot, where I can pop in a 128 GB card, as well as a micro SD card slot where I can plug in yet another.
But while the hardware is there, I CANNOT FIGURE OUT HOW TO GET THE MUSIC TO BE STORED ON THE EXTERNAL STORAGE! I've read all kinds of articles and threads that propose how to do it, but none of the methods have worked.
I tried:
A.
Navigating to the current location of the stored music (on this device it's /sdcard/Android/data/com.google.android.music/cache/music), deleting the 'music' folder and its contents, then making a new 'music' folder on the external SD and creating a symlink to it in the original location. This does not work. My file manager (rootbrowser) tells me that symbolic links are not supported by all filesystems (apparently including this one).
B.
Using the Cache Apps To SD app. The app works, but it does not move the correct files. It takes the cache located at /data/data/com.google.android.music/cache and moves it to the external SD. But that's not where Google Music stores the music, that's only where it stores... other things. The music files at /sdcard/Android/data/com.google.android.music/cache/music remain untouched, so this is useless.
C.
Moving the Google Play Music app itself to the external storage. To do this I tried both Apps2SD and Link2SD. Both do the same. What happens is the .apk file is moved to the external storage, but it doesn't take any of its files with it.
What do I do to make this work? I feel like doing this on 2.2 should be easy considering its friendliness with external storage, but no matter what I try I can't figure it out. I'd really appreciate someone's help with this one.
P.S. please don't make the obvious suggestion to upgrade to a newer version of Android. I would if that were possible, but it isn't.
Anyone? There's got to be someone who knows what to do with this. I know Android 2.2 is fading into the distant past by now, so I don't expect NEW enthusiasts to know how to use it, but aren't there any veterans on here that remember what they were doing in 2010? As far as I can tell this was a problem many people grappled with on their Galaxy S, Droid X, etc. phones.
Raven-6 said:
Anyone? There's got to be someone who knows what to do with this. I know Android 2.2 is fading into the distant past by now, so I don't expect NEW enthusiasts to know how to use it, but aren't there any veterans on here that remember what they were doing in 2010? As far as I can tell this was a problem many people grappled with on their Galaxy S, Droid X, etc. phones.
Click to expand...
Click to collapse
Don't you worry about 2.2 fading to nonexistence - I develop on a device that still only supports 2.1!
I'll do some research on this topic, but I don't know if it's possible. It probably is, though, so don't get your feathers ruffled.
thenookieforlife3 said:
Don't you worry about 2.2 fading to nonexistence - I develop on a device that still only supports 2.1!
I'll do some research on this topic, but I don't know if it's possible. It probably is, though, so don't get your feathers ruffled.
Click to expand...
Click to collapse
I appreciate your help on the matter. Have you found anything yet? What do you think about editing the vold.fstab file and switching the mounting points of the internal and external cards?
Raven-6 said:
I appreciate your help on the matter. Have you found anything yet? What do you think about editing the vold.fstab file and switching the mounting points of the internal and external cards?
Click to expand...
Click to collapse
Actually, haven't done much research yet - been busy with school stuff. Sorry.
Switching the mount points on the sdcards shouldn't be too much of an issue, but we'd need to actually edit init.rc inside uRamdisk to get it to mount properly on boot.
thenookieforlife3 said:
Actually, haven't done much research yet - been busy with school stuff. Sorry.
Switching the mount points on the sdcards shouldn't be too much of an issue, but we'd need to actually edit init.rc inside uRamdisk to get it to mount properly on boot.
Click to expand...
Click to collapse
Is that.... less easy? Your words do not inspire confidence.
Take your time though, midterms are going on after all. Let me know when you can help me out.
Raven-6 said:
Is that.... less easy? Your words do not inspire confidence.
Take your time though, midterms are going on after all. Let me know when you can help me out.
Click to expand...
Click to collapse
Sorry about my uninspiring speech.
It's not that hard, but it'll take some work.
I'll talk to you later. Have a good day.
Oh, I didn't mean any offense by that, I only meant that what you suggest seems difficult. Speak with you soon!
thenookieforlife3 said:
Sorry about my uninspiring speech.
It's not that hard, but it'll take some work.
I'll talk to you later. Have a good day.
Click to expand...
Click to collapse
I guess the guy who was going to help me went and got his account disabled?
Hello all i have the tab s6 that i got primarily for photo editing using lightroom. Unfortunately it seems i cant access any form of external storage through lightroom in order to view pictures and then import them into lightroom to edit them. It seems that I first have to transfer the pictures into the internal storage of the tab, in my case 256gb, and only then i can see the pictures in lightroom prior to importing them. By doing this i would essentially end up with duplicate photos and then reducing the storage even further.
The only way i can access the external storage is via the files manager app installed. Is there any work around this? In ios i can see the pictures from the external storage through lightroom prior to import.
What Android version? Scoped storage is fully active in Android 11/12 and it's a mess.
Unless the app has special permissions like that file app, scoped storage will puke on them and limit their access. You may be able to do a adb edit work around, not sure as I refuse to deal with these OS versions.
Maybe try using a OTG flashstick as a work around.
Running Android 11 and no new update available. And lightroom app permission under files and media it says “allow access to media only” dont see other options
Any app that allows full access to external drives where i can see the full size picture thats stored?
adinis78 said:
Any app that allows full access to external drives where i can see the full size picture thats stored?
Click to expand...
Click to collapse
Lightroom developers need to modify it for it to work most likely. Not a trivial task.
Do some searches to see if you can modify this behavior with adb edits. Yeah, now even bloody iPhones are easier to use than Androids, thanks for nothing Gookill...
I would just download the whole file copy onto the PC. You need to back it up anyway...
Last thing i want is too root the tab and gave things go wrong. Havent rooted an Android device in years and always more of a hassle than what improvements where promised
adinis78 said:
Last thing i want is too root the tab and gave things go wrong. Havent rooted an Android device in years and always more of a hassle than what improvements where promised
Click to expand...
Click to collapse
I prefer using stock. Adb editing is just modifying the user partition, a factory reset will undo the changes if you goof up.
If it came loaded with 11 you can't flash it back to 10 because of the boot loader version.
Try some Google searches ie something like "scoped storage workaround adb". Add xda to it to find threads about it here. Maybe Package Disabler could help but I doubt it as scoped store is a core feature.
There's a lot of pissed off Android users right about now... you're not alone.
Share your wuv and give Google some feedback.
I have to N10+'s, one is running on Pie, the newest on Q. Both behave almost identically, however Samsung added dozens of small system apks to do that... Samsung went to a lot of trouble to do that.
You confirmed my fear Samsung couldn't or wouldn't be able to do the same with the models running on R and above.
The culprit is Google not Samsung.
It's the game that moves as you play it.
Something so simple that they are alienating photographers and are forcing them into ios, maybe I should have gotten an ipad pro
adinis78 said:
Something so simple that they are alienating photographers and are forcing them into ios, maybe I should have gotten an ipad pro
Click to expand...
Click to collapse
There are work arounds but you shouldn't need to do this. At this point Android is more iPhone than Android... a tard wannabe iPhone that is.
Return if you still can.
If you get a Samsung running on P or Q it will function normally and still have sufficient security.
Be wary of buying devices as they may list P or Q as the loaded OS when in fact they've been updated or factory loaded (depending on manufacturered date) with R.
Tried to look into the scoped storage but seems to be too much of a hassle and not really working possibly depending on what you need. There doesnt seem to be a definitive answer to my particular issue in regards to having lightroom (adobe) have access to external storage. I might just have to bite the bullet and get a 1tb microsd card although thats a huge expense.
On another note, Adobe should make it a requirement to have access to external storage, its possible in IOS and windows and tell google to allow it.
Test a small sd card first to make sure it works as you want with scoped storage.
Get a V30 rated card, Sandisk Extreme works well.
Take a look at this thread.
blackhawk said:
Take a look at this thread.
Click to expand...
Click to collapse
Thanks but not really what i am looking for. Will test out and old microsd card i have from an old android phone and see how that goes
So some positive news to report. Tried an old microsd card. As expected it automatically displays the photos in the photo app just like the built in storage. So tried to copy a picture that i had backed up in the external ssd, did this via the file manager app. Then the moment of truth, opened up Lightroom and i have access to the additional microsd card, the picture that i copied from the ssd along with all the other old photos showed up in lightroom. So, as much of an inconvenience this is, it seems that for my needs and workflow, i would need the extra microsd card.
So here would be my work flow after taking pictures
1-Backup all the pictures taken on a certain date into the Samsung T5 SSD.
2-Also copy all of the pictures into the extra microsd card (1tb)
3-Go through all the pictures on the microsd card using lightroom to decide which ones to edit and then import them into lightroom.
4-Do all my edits then save those edits into the built in storage, upload to Facebook, instagram, etc. then save those final edits into the Samsung T5 SSD.
5-Format the 1tb microsd and repeat the whole process when needed.
Extra steps but it seems this is the only way. Thanks Google
EDIT: after thinking about it I think a 512gb would be more than enough for my expected workdlow and would be a significant savings vs the 1tb
Yay This will be a better setup than you had.
I always build dual drive PCs; the OS, apps, DCIM folder and the temporary download folder go on internal memory.
All critical data goes on the data drive. This is then backed up redundantly to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Do Not use DCIM in the name of photo folder on the SD card; there can only be one folder with that name.
I'm having the same problem with this scoop storage issue that Google has handed us My 1tb card is full of music that I can't access it worked fine on my Note 8 but it doesn't work hardly at all on my new Note 10 I can't even get a playlist to function right people have talked about editing Android manifest in Android studio Man that's so far above my ability but I wouldn't just format my card I know I bought the best one I could buy and I still have the problem and I've had my card for some time I hope someone comes up with a solution
alpastor said:
I'm having the same problem with this scoop storage issue that Google has handed us My 1tb card is full of music that I can't access it worked fine on my Note 8 but it doesn't work hardly at all on my new Note 10 I can't even get a playlist to function right people have talked about editing Android manifest in Android studio Man that's so far above my ability but I wouldn't just format my card I know I bought the best one I could buy and I still have the problem and I've had my card for some time I hope someone comes up with a solution
Click to expand...
Click to collapse
Scoped storage is a mess. Back up the 1tb card's data at least twice on 2 different hdds, more backup is always better.
Or use a different SD card in the device.
With the test SD card format the card with the device (all data will be lost, etc, etc), then doing the data transfer through the phone load the data. See if that works.
Regardless it's best practice to leave the SD card in one device and not "share" it with other devices. Having other devices write to it can lead to card corruption.
Don't know if this will help or not. I'm still running on Android 9 and 10. Gookill sucks elephant balls bad now... no way I'll upgrade my N10+'s to 11 or 12, they're running too good as is.
Thank you for getting back with me I have a real hard time keep you track of stuff nowadays but I don't need the aggravation of this scoop storage stuff as it is I have to pay someone to root my phones anymore because I just can't do it.
I used to be fairly good at it but not anymore so dr.ketan is promising updates in April and unless the issue is addressed by him I'm going to go ahead and downgrade my Note 10 Plus to Android 9 or 10 wherever that point is I can avoid all this crap
I think I read on one of the posts that they didn't really see any speed difference between 9 and 12
I think 9 was what was on my phone when I bought it in December.
And it was my phone guy that brought it up to 12 and put on dr.ketan's ROM. But I am so used to backing up stuff to SD card that it's driving me nuts. And isn't that the idea of TWRP anyway to be able to back up to your SD card and restore if you screw things up? Anyway thank you again for getting back with me and if you hear of any news about a fix or patch that someone like me could put on to fix it other than having to have the skills of a developer let me know I appreciate it I'd even be willing to be a beta tester.
Take care Rick