Database Info

[Q] task rpcrouter:15 blocked

I have a HTC Fuze (AT&T GSM). I followed the instruction on (http://forum.xda-developers.com/showthread.php?t=951981) for FRX06 but it keeps getting stuck at "task rpcrouter:15 blocked for more than 120 sec". It never gets to the calibration screen... I even tried downloading and using a pre-made ts-calib file but the results were the same.
I also tried numerous other posts ROMS (FRX03, FRX04, XDAndroid 2.2 (rel 1.6).cab, even tried XDAndroid 2.1 (rel 2.5a).cab) but I still get stuck at the "task rpcrouter:15 blocked for more than 120 sec" error.
I read in another post back in Feb 11 that it was an issue and someone acknowledging it is an issue but no solution stated in the 19 pages of forums. Another user states this is a "bootloop" but did not offer any solution.
In any case, I never got to any graphical screens - never got past the text screens (white text on black background).
Help!

Actually the fix was to delete the data.img but that would be the "quick fix". This WAS mentioned under the troubleshooting section of THIS post. If you really want to see the calibration screen, download an older kernel package as stated HERE.
BE SURE TO SAVE THE FILE CALLED ts-calibration THAT YOU JUST CREATED!​Additionally, I want you to format your microSD and start over from scratch. Just to flush out any other issues that you and may not encounter; such as the "waiting on SD card" issue some complain about. When I say format, I mean use something other than windows to format your microSD. I use the free version of partition wizard and it seems to do the trick. IF you want something a little less program intensive, I would suggest using SD Formatter. Again, not required but it might help solve other issues you may encounter on down the line.
All of that being said, I have a RAPH110 aka at&t Fuze, so I know this process works. If it doesn't work for you, YOU are doing something wrong!
Also, if you insist that you would rather skip the calibration screen, you may use my ts-calibration file. Make sure you place it where the file called haret.exe is.
CLICK HERE for your viewing pleasure!

Same problem with FRX06 even after FORMAT with OVERWRITE of the microSD. I included the ts-calib file. Got past "Creating a new Data Store" then got stuck at "mdp irq is already 4 4 and above mdp_dma: busy" where it would retry after getting stuck for 120 sec.
I then reformatted again and this time tried "XDAndroid 2.2 (rel 1.6).cab". Got to "Creating a new Data Store" and it is stuck there for over an hour - so I gave up.
I then tried deleting the files for "XDAndroid 2.2 (rel 1.6).cab" and this time tried "XDAndroid 2.1 (rel 2.5a).cab". Same issue.
Next, I tried loading Android on the Device instead of Storage Card. Stuck at the same point... I waited 5 min then quit.
I read elsewhere possibility of problems using micro SDHC cards... do you have a microSD card in your Fuze? My card is a Patriot microSDHC 8GB.

As always, there may be a bad batch but have had no such luck with buying PNY nor SanDisk. You did download 1231 as mentioned earlier, correct? So, if you want to try that first, you'll need to delete the existing modules-xxx and zImage file and extract the contents of the downloaded file till you see the modules-xxx and zImage_xxx. Rename the one called zImage_xxx to just zImage and be sure to place them with the file called haret.exe and launch haret once more. Keep in mind, downloading the kernel packages may not be required but in order to test things out and to see what works best, it is. Good luck my friend!

So I tried again and let the install run overnight (>4 hr). In the morning, it was still looping so I stopped it. Today, when I looked at the microSD, I see 171 FSCH0xxx files... most are 32K. 170 was 192K and 171 was 1.81M total of these files were about 158MB. Does this indicate anything?
Anyway, I reformatted my microSD card twice using the SDFormatter (Overwrite, Size Adjustment on), loaded FRX06, replaced the set with the 2 files you sent and renamed the zImage file. Booting up, goes into text screen, still get the timeout error. This time I noticed that there was a line that says "INFO: task dd:91 blocked for more than 120 seconds." My guess is that it's creating those FSCK files again... meaning SD card errors?

Have you another microSD to confirm whether it is a bad card? I just started from scratch (for the 50th time today) and I am NOT seeing what you are seeing(I don't see any FSCHxxx files)... I don't suggest trying anything older than FRX06. If anything, I'd suggest you see if you can find another microSD and probably only use that card for temporary storage.

OK, I'll have to go get another card this weekend then. I do think it seems like the card has some kind of compatibility problem... what brand are you using?
For tonight, I've formatted the card twice and then am trying the "XDAndroid 2.2 (rel 1.6).cab" now... It is stuck in the "Creating a New Data store" line for >20 minutes now... (FXR06 passes that but gets hung up trying to fix the file system). I'll wait a while longer and see if it will miraculously finish creating the new data store.
Thanks for your suggestions.

I have a PNY and SanDisk both 4GB class 4. I think bestbuy has the PNY one for like 30 bucks (maybe cheaper?)
I don't know what the problem is but I'm willing to help out how ever I can

I downloaded MiniTool Partition Wizard and deleted the microSD card's partition then recreated it. Then, I recopied the files into the root of the microSD, installed into my FUZE, and clicked on herat... this time it got into the Android graphical portion (no calibration needed since I included the ts-calibration file), stayed at the ANDROID screen for a while then went blank. I waited about 6 minutes then turned it off. When I went to see what's inside the microSD, I found the data.img file 256MB and also messed up file system again - since I shut it off prematurely.
With a lot more confidence this time, I repartitioned the microSD again, placed my Android files under its own folder. Crossing my fingers...

Ah, so you've been using the file path method then? If that is the case all one would need to do is put rel_path=FRX06 in the startup.txt file, between the quotation marks. Additionally, if you prefer more ogranization and plan to run more than one build at a time, it is best to have that command in your startup.txt file for each build. Keeping in mind, once you do this, it pretty much sets the default path for that build to that particular folder. I wasn't aware that you were starting one folder deep, my apologies . It's best to use the root folder for troublshooting and what not. I prefer to only use one build at a time because I find it easier to keep problems isolated and it helps me troubleshoot at the same time.
Additionally, if you want a more easier way to troubleshoot Android issues and you don't mind waiting for the data store (aka data.img) to be recreated at boot time, then one would only need to delete the data.img file (keep in mind if you have any settings or contacts, these may be deleted as well). What I usually do is once I get a good data.img, I make a backup and zip them up (or use your method of archiving). I also make a backup before I make any changes, like if I am testing out a new rootfs or kernel package. Most of this has been discussed and mentioned in the Android forums.

That did not work so I reformatted again and went back to using the root of the microSD for Android... FRX06 was stuck on GUI but blank screen all night - I turned it off in the morning. Back to the drawing board. At least I got the microSD issue figured out... on to the next mystery.
Update:
OK, partitioned my 8GB to 7GB FAT32, 512MB ext3, 512MB linux swap. Loaded FXR06 into the root folder, booted and it works this time. However, once into Android, it would lock up.
Case 1: Boot up android, clicked on Gmail, screen is android but nothing in the screen except background. Took out battery to turn off.
Case 2: Boot up android, left it alone, screen turned off - will not wake up. Took out battery to turn off.
Case 3: Boot up android, went to settings to set up wifi, froze. Took out battery to turn off.
Case 4: Boot up android, went to settings to set up wifi, entered WEP key, Fuze froze (I know because the screen is non-responsive, back button remains lighted after I move my finger away, and the clock on screen is not advancing). Took out battery to turn off.
Case 5: Replaced the modules and zImage files to the new ones you sent me (12/31/2010)... booted up android, went to settings to set up wifi, entered WEP key, shows connected, Fuze froze (I know because the screen is non-responsive, back button remains lighted after I move my finger away, and the clock on screen is not advancing).
Seems my Fuze is locking up soon after Android boot. Tried numerous times... left alone, freeze. Tried calling, freeze. It seems to be time based. So close...
Strange, though, as the phone remains warm to the touch despite being frozen for some time.

Yeah, you lost me at partitioning your device as I don't even touch that stuff. I think you are using something different. Sorry but I can not help you, my friend!

Thanks anyway... the partitioning is just to make the partition "different". Probably no relevance unless it allowed me to exclude some bad sectors from use. As far as Froyo, I guess there is some kind of HW or SW problem with my phone. I may reflash my Fuze to another WM ROM - just to clean it up and isolate SW as the problem.

Let me clarify, I don't partition my microSD because XDAndroid builds simply do not require this. There are Neopeek variants that require partitioning of the microSD but I still think your method is slightly over exaggerated. I'm not sure why but I guess for some reason there may be an issue with your microSD and partitioning may be a way around this issue but I don't know enough about partitioning microSD/non-volatile flash. So, I couldn't say for sure...

Ok, so I installed Tael ROM (WM 6.5) then tried installing, it still freezes after 1-2 min of booting up (or during boot up). So it looks like it's a hardware (phone or microSD) issue for some reason. I guess hardware vs thinking kernel because the 2.1 installs also do not work.
On another note, it seems that the Android boot process corrupts my other files... I have folders for GPS and photo (DCIM) and it "corrects" those errors and kills my files.

Hmmm... I can't say for certain as I've never experienced that issue. All of my files remain intact before and after booting into Android and rebooting into winmo. Are you talking about the files on your phone or microSD. If you are talking about your microSD, you might be experiencing the hardware issue and the while you boot into Android, it is only attempting to "fix" these issues and in the process, kills the files contained with-in. Does this makes any sense?

Yes, the files are those I mentioned are in my microSD. So, yes, looks like some kind of interface issue causing Android to think the files are corrupt and then try to "fix" them. Strange though that WM does not try to fix the "errors".

I think it's kind of like the linux way to make sure there won't be any issues when you run the OS, since Android would run off the microSD and not from the phones storage. Currently, there is some development for this called NAND. Still really nothing solid as to whether it will work or not but always good to know, I guess?

Well, the thing is those files are pictures/videos/GPS maps... so I think WM is able to read them (so not an error) yet Android does during its pre-boot scan. Anyway, since upon successful scan and android actually loads, it would freeze in 1-2 min, so the problem may not be limited to the microSD. Yeah, perhaps the NAND will work better. I did get Warm Donut to run on my old Tilt, so I am still hopeful.

The issue that is stumping me is that I'm not experiencing the same issues you are with XDAndroid and I'm not sure how else to help aside from using another microSD to confirm an issue with your current microSD.. sorry

Apps disappearing after reboot?! [CM6]

Ive had a weird problem the last day or so, when I reboot my device, apps mysteriously go missing. Each time I reboot, like 5 or 6 different apps disappear. This only happens to SD card apps though. This started happening a few days ago but yesterday it got alot worse AFTER I had reformatted my card. Could there be something wrong with my SD card? The apps still appear to be installed in "manage applications" but they look like "com.aac.cachemate.demo" as the name of the app, instead of "Cachemate" and etc...?

did you use link2sd ?

com....whatever in manage applications usually means, that the apk file is missing, while the application data is present
the mess as described, can be seen if your ext partition is mounted too late ...
nadlabak has some fix about it
https://github.com/nadlabak/android...mmit/e5b9b3195687e04af7a7929f8637e77e1efae9a1
but i can't remember where is part of setting the property, after checking and mounting the whole card ...

nikctsh said:
did you use link2sd ?
Click to expand...
Click to collapse
I did not, I used the standard apps2sd built into CM6. Every time I reboot, different apps are missing and then some come back that were missing the time before...They all still appear in manage applications though so they might be intact but I'm not sure if all are, they show up with the default generic android icon, and weird names. "mobi.mgeek.tunnybrowser." (Dolphin Browser) and "net.flixter.android" (Flixter) etc...The storage sizes of the missing apps appear to be different then they are supposed to be. (Maybe)

(This might have something to do with it) Yesterday for hours (before I reformatted) the phone was stuck at "Preparing SD card, checking for errors" so I went online and followed the suggestion an xda member who suggested in another thread to delete the "fsck_msdos" file from "system /bin" which disables the SD card check to see if the SD card has been properly mounted and checked. It seemed to fix my other SD card issue for the rest of the day. could this be related?

Just share my experience , when I was in 2.1 , I used link2sd , and if I boot without sdcard , all my linked apps will happen like that , I think maybe this is the same case as apps2sd . So , what I do is just uninstalled all those apps , and reinstalled some of it ( it's quite annoying to reinstall over 100 apps ) . As you said , all those apps remained as it's package name , so I'm kinda sure our case is almost the same . But when I was in 2.2 , once I booted with sdcard inserted , but after boot completed , all my user apps dissapear , yes , ALL . But anyway , after scan for sdcard problem in OR , all my apps recovered , with no force close , just like nothing happen during the last boot . So also , try to scan for sdcard problem in OR .

It says my card is mounted (about half of my sd card apps show up) but when I bring up the gallery, it says "SD card unmounted or not present." When I try to unmount it in settings, it never unmounts, I just click "unmount" and nothing happens....

donovanx3 said:
It says my card is mounted (about half of my sd card apps show up) but when I bring up the gallery, it says "SD card unmounted or not present." When I try to unmount it in settings, it never unmounts, I just click "unmount" and nothing happens....
Click to expand...
Click to collapse
It sounds like you have corruption in your sdcard filesystem. I would take your sdcard out, put it directly into a Windows PC and run chkdsk (alternately fsck.msdos on a linux PC).

Mioze7Ae said:
It sounds like you have corruption in your sdcard filesystem. I would take your sdcard out, put it directly into a Windows PC and run chkdsk (alternately fsck.msdos on a linux PC).
Click to expand...
Click to collapse
Ok I will run a chkdsk when I get some time to sit down at the computer later. I think it probably is corruption.

Mioze7Ae said:
It sounds like you have corruption in your sdcard filesystem. I would take your sdcard out, put it directly into a Windows PC and run chkdsk (alternately fsck.msdos on a linux PC).
Click to expand...
Click to collapse
SD card fixed with error checking in windows!! Thanks!

Fast Boot option may be the culprit
The advice about checking SD card on Windows or Linux sounds good and I will keep it in mind, but I did not need to fix this sort of problem. I am not familiar with CyanogenMod (CM) in any version, but if it has a fast boot option, read on...
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: http://forum.xda-developers.com/showthread.php?t=1873670
(I am copying this post to other relevant threads, but will not post anything further elsewhere -- only there. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:

Sorry for opening up old thread. My HDC Note3 clone phone having the same/similar issue. The phone have 8G ROM which partition into 2 different name, internal phone (1G) and SD card (5G). Whatever Apps that I install on the SD card will disappear from home menu every-time I re-boot using the power button. However, it it still there when the phone do their own reboot due to something
I try unchecked "Fast Boot" but disappearing act still happen. Any suggestion to resolve the issue?

Cannot access internal or external storage...

Hi,
Did a search but could not find anything like this.
Problem with my new Gemei G9T Android 4 Tablet. Until 3 nights ago it functioned normally, but 2 days ago I switched on and there was a problem accessing storage. File Browser and ES File Explorer cannot access internal SD, nor can QuickPic, MoviePlayer, or Music. Icon continuously shows ‘preparing SD card’. Settings accesses most functions, except ‘storage’ and ‘developer options’ which cause it to freeze. Tried factory reset – did not work. Most apps work fine, but not Camera or Gallery. Cannot access external SD or USB storage, or connect to laptop. Entering sleep mode causes power off. Normal powering on and off now require two presses with time gap between. All of these functions were fine previously. Have you any suggestions, please?

Brian44 said:
Hi,
Did a search but could not find anything like this.
Problem with my new Gemei G9T Android 4 Tablet. Until 3 nights ago it functioned normally, but 2 days ago I switched on and there was a problem accessing storage. File Browser and ES File Explorer cannot access internal SD, nor can QuickPic, MoviePlayer, or Music. Icon continuously shows ‘preparing SD card’. Settings accesses most functions, except ‘storage’ and ‘developer options’ which cause it to freeze. Tried factory reset – did not work. Most apps work fine, but not Camera or Gallery. Cannot access external SD or USB storage, or connect to laptop. Entering sleep mode causes power off. Normal powering on and off now require two presses with time gap between. All of these functions were fine previously. Have you any suggestions, please?
Click to expand...
Click to collapse
Try to take out your SD card and put it in a Card reader, remember to do it while your device is off or unmount it from memory settings, try to swtich on your device later and connect it to your computer and check if it connect through USB or not.

Try some system tools?
Brian44 said:
Hi,
Did a search but could not find anything like this.
Problem with my new Gemei G9T Android 4 Tablet. Until 3 nights ago it functioned normally, but 2 days ago I switched on and there was a problem accessing storage. File Browser and ES File Explorer cannot access internal SD, nor can QuickPic, MoviePlayer, or Music. Icon continuously shows ‘preparing SD card’. Settings accesses most functions, except ‘storage’ and ‘developer options’ which cause it to freeze. Tried factory reset – did not work. Most apps work fine, but not Camera or Gallery. Cannot access external SD or USB storage, or connect to laptop. Entering sleep mode causes power off. Normal powering on and off now require two presses with time gap between. All of these functions were fine previously. Have you any suggestions, please?
Click to expand...
Click to collapse
I'm guessing databaiz's suggestion to take out the card isn't an option because it's the internal sd card, right? If so, for the one-in-a-million chance that the external card is screwing with the bus, I'd take the external card out and reboot anyway, just to make sure; if it works OK then, I would check the external card as databaiz suggests. But assuming it still doesn't work, next question is, do you have a terminal app installed? Please try the 'mount' command and let us know what you see. One other question, will it still go into fastboot mode? Can you see it from your computer when in fastboot mode (the details of how to do this depend on whether you have windows or linux/macOS - I can maybe help with the latter, but not the former).

It could be bad card
It could be bad card.... Remove and test in card reader...

cannot access internal or external storage
Thanks guys, I have been booting without external memory, with problems still the same. So, cannot be problem with external SD.
The internal SD card is not accessed properly. When I go to settings>Apps>All, the line at bottom shows Internal storage 4.1 MB used, 798MB free. (I have uninstalled most apps to see if that helped – it did not.) So, something is accessing the internal SD, also apps are running which must be off the internal SD.
I do not know what a terminal app is, Urilabob. I have downloaded it but what do I do with it?
At: [email protected]:/ $ I keyed in # mount [enter] , making:
[email protected]:/ $ # mount [enter]
But nothing happened, just another line of: [email protected]:/ $
Also, what is fast boot mode – this is not the same as sleep mode? This is all new to me. Appreciate your help.
My laptop is Windows 7.

Brian44 said:
Thanks guys, I have been booting without external memory, with problems still the same. So, cannot be problem with external SD.
The internal SD card is not accessed properly. When I go to settings>Apps>All, the line at bottom shows Internal storage 4.1 MB used, 798MB free. (I have uninstalled most apps to see if that helped – it did not.) So, something is accessing the internal SD, also apps are running which must be off the internal SD.
I do not know what a terminal app is, Urilabob. I have downloaded it but what do I do with it?
At: [email protected]:/ $ I keyed in # mount [enter] , making:
[email protected]:/ $ # mount [enter]
But nothing happened, just another line of: [email protected]:/ $
Also, what is fast boot mode – this is not the same as sleep mode? This is all new to me. Appreciate your help.
My laptop is Windows 7.
Click to expand...
Click to collapse
Sorry, I replied earlier but it seems I messed up so the reply didn't appear.
My problem is I know unix fairly well, and android is very similar, so I forget what is the same and what's different. Sorry, the command you need in the terminal is "df". That will show you a list of what partitions are mounted on your system. I'm guessing you're going to see /system, but not /mnt/sdcard. Why, I don't know. It's possible that the sdcard partition has got corrupted - but suspicious that the external card is also having problems. Is it possible that either the tablet or your pc crashed while you were copying files between them? Or that you disconnected the cable between them before telling the tablet to go out of connected mode? Either of those could explain corrupted partitions. Unfortunately fixing them may not be easy.
There are three different ways to connect your tablet to a computer. One is so it looks like external disks. I got the impression you already discovered this, and that it has now stopped working. The other two require you to install (parts of) the android development system on your computer. The simplest one is adb mode. Please google it to see how to use it. This might give you a chance to check the state of your partitions. The other is in fastboot mode. Fastboot mode is an alternative way of starting your computer, that goes into a fairly bulletproof, but very simple, mode that allows you to do various things on your tablet (it gives you very low level access to the tablet - powerful but dangerous). I'm pretty sure it will still be working. How you get into fastboot mode depends on your tablet; you'll need to google it. And how you access it in fastboot mode is fairly different on windows. So I'm not the best adviser. But please be careful - it's easy to brick the tablet in fastboot mode, you need to make sure you completely understand any steps you might take, especially any that might write to the tablet (of course, reading from it is safe). And of course the simplest alternative is simply to completely reinstall the tablet (sorry, I forget the android term for this). That should restore things OK, but it will mean you lose all your data and will have to reinstall all your applications.

cannot access internal or external storage
urilabob said:
Sorry, I replied earlier but it seems I messed up so the reply didn't appear.
My problem is I know unix fairly well, and android is very similar, so I forget what is the same and what's different. Sorry, the command you need in the terminal is "df". That will show you a list of what partitions are mounted on your system. I'm guessing you're going to see /system, but not /mnt/sdcard. Why, I don't know. It's possible that the sdcard partition has got corrupted - but suspicious that the external card is also having problems. Is it possible that either the tablet or your pc crashed while you were copying files between them? Or that you disconnected the cable between them before telling the tablet to go out of connected mode? Either of those could explain corrupted partitions. Unfortunately fixing them may not be easy.
There are three different ways to connect your tablet to a computer. One is so it looks like external disks. I got the impression you already discovered this, and that it has now stopped working. The other two require you to install (parts of) the android development system on your computer. The simplest one is adb mode. Please google it to see how to use it. This might give you a chance to check the state of your partitions. The other is in fastboot mode. Fastboot mode is an alternative way of starting your computer, that goes into a fairly bulletproof, but very simple, mode that allows you to do various things on your tablet (it gives you very low level access to the tablet - powerful but dangerous). I'm pretty sure it will still be working. How you get into fastboot mode depends on your tablet; you'll need to google it. And how you access it in fastboot mode is fairly different on windows. So I'm not the best adviser. But please be careful - it's easy to brick the tablet in fastboot mode, you need to make sure you completely understand any steps you might take, especially any that might write to the tablet (of course, reading from it is safe). And of course the simplest alternative is simply to completely reinstall the tablet (sorry, I forget the android term for this). That should restore things OK, but it will mean you lose all your data and will have to reinstall all your applications.
Click to expand...
Click to collapse
Thanks, Urilabob. The command df had an effect!
Shows Filesystem with figures for Size, Used, Free, and Blksize (4096), next to each of the following:
/dev, /mnt/asec, /mnt/obb, /system, /data, and /cache. The figures are all different except Blksize.
/mnt/sdcard is not shown.
Does this tell you anything useful?
I have never been able to access the tablet from my laptop with Windows 7. My son’s laptop has an earlier Windows, so I checked today and found that his Windows Explorer finds the tablet (as 2 disks, A and F) and asks “Please insert a disk into Removable Disk H:” (and same for F.
By the way, this problem started when I downloaded the (automatic) firmware update direct to the tablet, not via laptop. But the wifi signal was weak, and files may have been corrupted. I have since downloaded the complete, latest firmware to the laptop (with strong wifi signal), but do not know how to get it into the tablet!
Have not yet done anything on adb or fastboot modes. Will Google adb tonight.
Not worried about losing data or apps.
Thanks again, Brian.

I'm guessing that your tablet is rooted? If so, do you have an app like superuser? I remember having to go through some options to give my file explorers access to my SD card. You may have accidentally set you SD card to be off-limits or something. If you haven't already done it, see if giving an app like ES File Explorer superuser access will help.
Also see if you can enable USB debugging. For my nook color, I have to enable in order to access usb mass storage for one of my memory units. See if you can access your internal SD card content through USB debugging.

cannot access internal or external storage
SacTappingUni said:
I'm guessing that your tablet is rooted? If so, do you have an app like superuser? I remember having to go through some options to give my file explorers access to my SD card. You may have accidentally set you SD card to be off-limits or something. If you haven't already done it, see if giving an app like ES File Explorer superuser access will help.
Also see if you can enable USB debugging. For my nook color, I have to enable in order to access usb mass storage for one of my memory units. See if you can access your internal SD card content through USB debugging.
Click to expand...
Click to collapse
Thanks for your thoughts. My tablet is not rooted. And I cannot enable USB debugging, because Settings freezes when I tap Developer Options to get to USB debug. I am just learning about Android - seems to be 2 partitions on the internal storage, one about 2.6GB with apps and other things on (which is accessible), and the other partition must be about 13GB, but has not been accessible since the automatic firmware update.

Sounds like the update caused you issues. If you have everything backed up with your Google account I recommend that you do a factory data reset and see if that fixes your issue.

cannot access internal or external storage
MissionImprobable said:
Sounds like the update caused you issues. If you have everything backed up with your Google account I recommend that you do a factory data reset and see if that fixes your issue.
Click to expand...
Click to collapse
Factory reset would be great, if it worked, but it does not function.

Can you exchange the device?
Brian44 said:
Factory reset would be great, if it worked, but it does not function.
Click to expand...
Click to collapse
OK, so from your df listing, it's clear that sdcard is not getting mounted. That's a pretty low-level function that is failing. The fact that factory reset also doesn't work suggests (doesn't prove) that the sdcard partition at least has a corrupted filesystem, and quite possibly the partition itself has been corrupted. Could a spotty OTA update do that? I'm surprised - I would have thought they would use fairly high level functions for OTA updates, precisely because any drop-out could cause corruption if you use low-level disk access. But who knows - the mysteries of google? Another possibility is that the sdcard is physically bad, and maybe the update just caused you to get into the bad region (with the dynamic memory mapping in flash memory, once something goes wrong it's almost impossible to figure out what). At this point, I'd be going back to the distributor if possible (you said it was new, right)? I think even if you were an android guru, and knew exactly how to do a complete rebuild from scratch, you would be risking that the device itself is faulty - and that the rebuild would mean you couldn't prove that the device was at fault (rather than your rebuild)...
Best Wishes
Bob

cannot access internal or external storage
urilabob said:
OK, so from your df listing, it's clear that sdcard is not getting mounted. That's a pretty low-level function that is failing. The fact that factory reset also doesn't work suggests (doesn't prove) that the sdcard partition at least has a corrupted filesystem, and quite possibly the partition itself has been corrupted. Could a spotty OTA update do that? I'm surprised - I would have thought they would use fairly high level functions for OTA updates, precisely because any drop-out could cause corruption if you use low-level disk access. But who knows - the mysteries of google? Another possibility is that the sdcard is physically bad, and maybe the update just caused you to get into the bad region (with the dynamic memory mapping in flash memory, once something goes wrong it's almost impossible to figure out what). At this point, I'd be going back to the distributor if possible (you said it was new, right)? I think even if you were an android guru, and knew exactly how to do a complete rebuild from scratch, you would be risking that the device itself is faulty - and that the rebuild would mean you couldn't prove that the device was at fault (rather than your rebuild)...
Best Wishes
Bob
Click to expand...
Click to collapse
Thanks, Bob for all your help. This seems like the end of the line with this tablet. I expected this might be the case, and emailed DinoDirect two days ago for a refund, as I am heading overseas next week and want to resolve the matter before I go. They responded that "we will contact our related department to process your case priority". I have been aware that any actions I might take could invalidate the warranty, and this has inhibited me a bit. I will forward your latest comments in support of my refund claim.
I learned some basics of Android from all this!
Good wishes, great talking to you.
Brian

Just for a great justice :victory:
Got same bug on my Gemei G6, guess it hapens after i connect dc cabel to a fully charged pad that was charged in off mode and turn on. So i just download last firmware fro Gemeitech.com, unzip it on SD card and tnen turn on pad with pressed Home and Power buttons that must be pressed untill robot with green rotating belly appears what mean start of flashin` Thats it.

Got the same issue in Huawei Ascend P-7, I just switched off the mobile, removed the SD card and turned it back on after 5 minutes ....... and that was it, all issues resolved. Just the thing was that once SD card was re-inserted, problem came up again. So i have decided to copy SD card data to PC via Card Reader and format it or get new SD card

Ex-Sdcard mounting issue

This issue just started today, I have rebooted several times, sdcard icon appears and disappears as I insert it, like if its reading it. But it does not appear in any file explorer. Also on the storage setting I get the option of mounting but does nothing when I press it.
Forgot to mention its a Samsung 32gb used less than a month.

No idea how this happened but it turned out I needed to re format it.
Sent from MotoG3 XT1540

Is this after flashing scritchs cm13 test?

christopherrrg said:
Is this after flashing scritchs cm13 test?
Click to expand...
Click to collapse
No, I didn't dare to flash it before fixing the sdcard.
Sent from MotoG3 XT1540

Alright so I'm going on the 3rd day again going through this issue, but now I keep having a popup saying "disk is write protected".
Now I'm using and adapter for the pc, and No... switch it's not locked.
Can't format in any way possible.
Low level formatting seems like the only way to go which actually started, but it's a 32gb it takes wayyyyy too long.
Sent from MotoG3 XT1540

Did you originally try looking at the card with a file manager like Explorer? You would get that error if there was a file or group of files on it that were marked read-only. I've had that happen and I had to change the file properties before I could format.

Tel864 said:
Did you originally try looking at the card with a file manager like Explorer? You would get that error if there was a file or group of files on it that were marked read-only. I've had that happen and I had to change the file properties before I could format.
Click to expand...
Click to collapse
File explorer on phone? If yes as it sits I can't access it when ever this happens, so no option for sdcard1 appears. This is the 2nd this happens all of a sudden than I can't access it at all on the phone. Now on pc it does open, but I can't not delete a single file as I do not get the option for when right clicking due to "disk write protection". I'll check files individually.
Sent from MotoG3 XT1540

I've had this problem before. The adapter was getting switched on when I was putting it into the device and when I was taking it out it was switching off. Just make sure it's in the right position.

Tomadock said:
I've had this problem before. The adapter was getting switched on when I was putting it into the device and when I was taking it out it was switching off. Just make sure it's in the right position.
Click to expand...
Click to collapse
I've read about this, but the adapter is brand new came with the micro sdcard, it's a Samsung. The switch is firm and strong and not loose what so ever. But I'll keep checking.
I just even tried taping over the switch so it won't move still the problem persist. I just reach a month with it, weird.
Sent from MotoG3 XT1540

[SOLVED] Apps suddenly unable to access SD card for seemingly no reason

SOLVED
Found the thing!
This bug is caused by activating the option Disable permission monitoring in the Developper Options.
This is an option that is specific to a handful of phone manufacturers (Oppo in my case).
Enabling this option is needed for using some tweak apps such as Shizuku. However, if it is enabled on phone boot, SD card will be unaccessible.
FIX
Disabling this option and rebooting the phone fixed it.
If you still need to use this option, you can enable it while the phone is on and disable it before rebooting. It will work fine despite this minor inconvenience.
Click to expand...
Click to collapse
Solution answer
So this one is weird.
Everything was working fine untill I rebooted my phone earlier today.
For some reason, since this reboot, apps are unable to access my SD card storage. As far as I know, no update was applied with this reboot. I do not recall tinkering or changing anything related to this recently.
Symptoms
SD card is still visible in the storage tab of the settings (there is no available option to unmount or eject it) or in select cases when choosing a folder from an app, however the content does not show up past the root.
My music player (Oto music) sends an error message "Cannot play this file" while trying to play a song from the SD card
File explorer will not show the SD card directory at all
Resillio Sync has a synced folder on the SD card. It now says "Can't open the destination folder". If I try adding a new synced folder on the SD card and select the root of the SD card, I get the message "Android OS restricts access to this folder"
Google file is stuck in a loop trying to get permissions to access the card
SD card works just fine on another phone.
Other SD cards have the same problem with my phone, not just this one
SD card does not show up when using file transfer with a Windows PC
Rebooting the phone did nothing
Removing the card and putting it back in again did nothing
Formatting the card did nothing
I factory reset the phone. It worked, but the problem came back at the first reboot.
Current state of investigations I have reset the phone a second time and reboot it every time I install an app, uninstall or disable a system app or change some settings. So far the SD card is still accessible so I know what it's not:
it's not the fault of disabling system apps
it's not related to using a work profile (Insular)
still haven't found an app that causes it
Apps I have not tried re-installing on my second reset and that might be the curlprit:
Shizuku (I have my suspicions on this one, let me know if this one is known for causing similar bugs) Not Shizuku per se but a developper option needed for it (see solution answer)
I have no idea what could cause this, all I know is it's related to my phone in particular and it appeared out of nowhere.
I am using Android 13 on ColorOS.
Thanks to anyone who can help.

Format card in phone before using. Do Not share the card with other devices; upload/download to the card through the phone.
Hardware or firmware issue. Inspect phone sd card contacts.

blackhawk said:
Format card in phone before using. Do Not share the card with other devices; upload/download to the card through the phone.
Hardware or firmware issue. Inspect phone sd card contacts.
Click to expand...
Click to collapse
Thanks for answering.
I did format the card to no avail.
I did not use the card on other phones before it stopped working.
As I previously mentioned however, the card WAS working fine until now, and unless I am mistaken you seem to address the problem as if this is a new card or something. The card has been in this phone working fine for months.
It seems pretty clear to me this is a permissions issue so firmware perhaps indeed.
How would I go about checking the phone SD card contacts?

Iune said:
Thanks for answering.
I did format the card to no avail.
I did not use the card on other phones before it stopped working.
As I previously mentioned however, the card WAS working fine until now, and unless I am mistaken you seem to address the problem as if this is a new card or something. The card has been in this phone working fine for months.
It seems pretty clear to me this is a permissions issue so firmware perhaps indeed.
How would I go about checking the phone SD card contacts?
Click to expand...
Click to collapse
You're welcome.
If other cards don't work... regardless just stating things that can cause issues.
Light and magnification if needed to inspect the contacts. Use anhydrous isopropyl alcohol to clean if needed.
I sort of doubt it's firmware. Try a hard reboot and clear the system cache if possible.

blackhawk said:
You're welcome.
If other cards don't work... regardless just stating things that can cause issues.
Light and magnification if needed to inspect the contacts. Use anhydrous isopropyl alcohol to clean if needed.
I sort of doubt it's firmware. Try a hard reboot and clear the system cache if possible.
Click to expand...
Click to collapse
The reason I believe it is firmware is that when setting permissions the SD card IS shown in the list. For instance in my music player if I use the option to authorize access to the SD card it is here. It just does nothing when I authorize it.
I am leaning towards a permissions issue because when I use one of these permission windows to try and create a folder on the SD card, I get an error message that says "Android OS restricts write access to this folder". Hence the problem is not that the SD card is not detected, but that apps are somehow not allowed to use it.
I currently not have what it takes to check the contacts (neither the tools nor the knowledge). This phone is only a couple months old so I also doubt the contacts are damaged as they have been working fine until now and I had never removed the card or opened the tray since day one.
A hard reboot should be last resort, but anyway I did it. It worked and my SD card was accessible again, so I reinstalled all my stuff. But then at the first reboot the problem was back. I am now pretty sure this is a software issue as on my second phone reset, the SD card is still usable as long as I don't isntall the wrong thing (still trying to figure out what that is). I added my investigations to the main thread.

SOLVED
Found the thing!
This bug is caused by activating the option Disable permission monitoring in the Developper Options.
This is an option that is specific to a handful of phone manufacturers (Oppo in my case).
Enabling this option is needed for using some tweak apps such as Shizuku. However, if it is enabled on phone boot, SD card will be unaccessible.
FIX
Disabling this option and rebooting the phone fixed it.
If you still need to use this option, you can enable it while the phone is on and disable it before rebooting. It will work fine despite this minor inconvenience.

Iune said:
The reason I believe it is firmware is that when setting permissions the SD card IS shown in the list. For instance in my music player if I use the option to authorize access to the SD card it is here. It just does nothing when I authorize it.
I am leaning towards a permissions issue because when I use one of these permission windows to try and create a folder on the SD card, I get an error message that says "Android OS restricts write access to this folder". Hence the problem is not that the SD card is not detected, but that apps are somehow not allowed to use it.
I currently not have what it takes to check the contacts (neither the tools nor the knowledge). This phone is only a couple months old so I also doubt the contacts are damaged as they have been working fine until now and I had never removed the card or opened the tray since day one.
A hard reboot should be last resort, but anyway I did it. It worked and my SD card was accessible again, so I reinstalled all my stuff. But then at the first reboot the problem was back. I am now pretty sure this is a software issue as on my second phone reset, the SD card is still usable as long as I don't isntall the wrong thing (still trying to figure out what that is). I added my investigations to the main thread.
Click to expand...
Click to collapse
A hard reboot is not a factory reset! It simulates pulling the battery... It's always better to find the root cause of a problem than to factory reset because the problem is likely to reoccur
Sounds like a trashware 3rd party app is to blame... try in safe mode. If it fails to function in safe mode start uninstalling the 3rd party apps one by one until (if) the problem resolves to find the app that screwed up the hidden user settings*. If that fails to work, another factory reset and start over, being careful what you load, then rebooting and checking after each install.
Meh, you got a real can of worms to play with...
*poorly coded apps can alter hidden user settings and fail to revert these settings to default even after the offending app is uninstalled. Alternatively see if the behavior caused by the offending app can be corrected using the settings in that app.
ADB editing could maybe be used to correct to hidden user settings misconfiguration but finding that setting may prove difficult. Beyond anything I ever had to do.

blackhawk said:
A hard reboot is not a factory reset! It simulates pulling the battery... It's always better to find the root cause of a problem than to factory reset because the problem is likely to reoccur
Sounds like a trashware 3rd party app is to blame... try in safe mode. If it fails to function in safe mode start uninstalling the 3rd party apps one by one until (if) the problem resolves to find the app that screwed up the hidden user settings*. If that fails to work, another factory reset and start over, being careful what you load, then rebooting and checking after each install.
Meh, you got a real can of worms to play with...
*poorly coded apps can alter hidden user settings and fail to revert these settings to default even after the offending app is uninstalled. Alternatively see if the behavior caused by the offending app can be corrected using the settings in that app.
ADB editing could maybe be used to correct to hidden user settings misconfiguration but finding that setting may prove difficult. Beyond anything I ever had to do.
Click to expand...
Click to collapse
Well I searched on Google about hard reboots and the explanations literally described a factory reset haha. I have yet to understadn the difference. Wipe all data VS wipe all data ?
Anyway I investigated and found the cause of the problem, so marking this post as solved! Thanks for the help

Iune said:
Well I searched on Google about hard reboots and the explanations literally described a factory reset haha. I have yet to understadn the difference. Wipe all data VS wipe all data ?
Anyway I investigated and found the cause of the problem, so marking this post as solved! Thanks for the help
Click to expand...
Click to collapse
Yay! Well done. So many settings...
Traditionally a hard reboot is killing the power to the mobo... I believe, or maybe I just watched too many sci-fi movies You do it by holding the power button (or combination of buttons) down for 20-30 seconds.
On cams and older phones you simply remove the battery for a few seconds. It clears any volatile memory settings in the chipsets or semiconductors by cutting to power to everything.