Database Info

[Q] SD card 0.00 bytes free, device offline ?

I'm having problems guys
I don't know if I succesfully rooted my phone as when I ran ./root.sh through the linux debian terminal, I received multiple errors saying deivce offline
This also happened when I did Linux/adb reboot "Device offline"
I am now having the problem that my internal sdcard appears to be unusable as my phone keeps saying that is full though it must have over half of the 13gb free
I can access it through mass storage but I can't download/install anything as I apparently have no space
I have not had this problem before, if anyone can help I'd appreciate it.

adb can be weird. it doesn't get covered much on xda but you have to make a file called 70android.rules or something to that effect, I can give better details some other time, right now I can't remember the location or exactly what goes in it besides the samsung vendor id but it basically allows adb to see the phone.
if you have that setup then maybe there is another problem. not sure what issue you have with the sdcard but does it work from the phone and not through a data cable? vise versa? not working at all?

When I go through Settings-SD Card storage my SD card (internal) says that it is full though it's not!
Perhaps I don't understand what the "wipe data/factory reset" does on your phone through red recovery
p.s. If gou actually are running 3e would it say 3e recovery?
I can't install appa as my sd card is entirely full
I had unlocked my phone before through the same comp, I don't know why I am having problems.
Every time I root this phone I do something different everytime (I forget what I did last time)
Others have suggested doing an odin? This phone is a refurb it has many errors aside from freezing then vibrating- force closs
It is slow, sometimes when it freezes the icons (four main on home that you can't movebon stock rom) rotate an entire 90 degrees it's weird as hell
I wish I never sent my Infuse in b/c of the cracked screen I should have just gotten the screen fixed
Thanks for your response

try a factory rest through settings>privacy, then if that doesn't help do an Odin flash back to stock with repartition.
it seems rare on American devices but a lot of galaxy s devices have had trouble with the internal SD card going corrupt. in some cases its fixable but I'm not really sure if that's what's going on here.

Ok so I did reset through settings-privacy that did the trick
Now to start all over again...
I seem to be having a hard time finding the backed up files on Titanium...

oh [email protected] my bad....
I forgot to mention that the privacy reset formats the sdcard. part of why its often successful is that it'll fix certain issues with the SD card and it wipes app data saved to /sdcard/data/
titanium backup keeps the backups on the sdcard...

Dani897 said:
oh [email protected] my bad....
I forgot to mention that the privacy reset formats the sdcard. part of why its often successful is that it'll fix certain issues with the SD card and it wipes app data saved to /sdcard/data/
titanium backup keeps the backups on the sdcard...
Click to expand...
Click to collapse
by the way, I think this reset option also erase everything on your external_SD as well. I found that out the hard way very early on.

+1 qster
Sent from my SGH-I997 using xda premium

[Q] How do I un-**** myself?

I'm having trouble getting feedback, and Google is of little help. I'm sure I'm not the only person with this problem but I can't find anyone else with the answer so I'm hoping one of you has a link to my answer.
Anyways I got a GoTab 6Inch running 4.0.4
It came stock with a main partition of 400MB and an SD partition of 2.3GB.
Out of both of these partitions, the 400MB one was protected in and the 2.3GB on could be "erased" by going into the settings and then storage. So I decide to "Factory Reset" and check the "Erase SD card" box.
Well with no warning from the tablet's home page or included instruction booklets, they say nothing about what was on this "free to erase" open partition. Apparantly it had some way-important files as I now can't get into recovery menu. The 400MB partition went down to 0.00MB but somehow has 39MB reserved for apps. And the 2.3GB is empty as 2.3GB. As well as no recovery menu, you also can't format to factory settings now.
Since the main partition is 0.00MB, you can't install or update apps. Also settings can't be saved, so every app is booting up as if its the 1st time every time.
If I learned anything from my Android 1.5 guides I used to read about 4 years ago, I think I need to somehow manually root, flash a new recovery, make a partition or two, and flash a whole new kernal/OS. Can anyone help with this? Getting a new recovery and partitions working properly is of the utmost imprtance because now if something goes wrong, I cant go into recovery to unbrick a device.

hello?

[Q] Unable to mount /data

My wife's Galaxy S3 suddenly decided it didn't want to boot past the Galaxy SIII logo (which includes the blue Cyanogen mascot at the bottom)
I was going to attempt to re-flash Cyanogenmod 10.2, but for some reason TWRP prompted me for a password upon going into recovery. Hitting Cancel here allows me into TWRP. I flashed the latest version on TWRP, and still I am prompted by that password.
I then found that I was unable to wipe Dalvik Cache, and then found that I'm unable to mount /data.
Well that's not good. I assume that I'll have to use Odin to go back to stock and re-partition? Any suggestions would be appreciated.

Sounds like your /data is encrypted. When you're prompted for a password, that's to decrypt the /data partition (it's probably the PIN she uses to unlock the phone). Hitting cancel simply leaves /data unencrypted and unmounted. If you hit mount within TWRP, you'll probably see a "Decrypt Data" button. Try using the PIN and see if that works.
Joe
erc. said:
My wife's Galaxy S3 suddenly decided it didn't want to boot past the Galaxy SIII logo (which includes the blue Cyanogen mascot at the bottom)
I was going to attempt to re-flash Cyanogenmod 10.2, but for some reason TWRP prompted me for a password upon going into recovery. Hitting Cancel here allows me into TWRP. I flashed the latest version on TWRP, and still I am prompted by that password.
I then found that I was unable to wipe Dalvik Cache, and then found that I'm unable to mount /data.
Well that's not good. I assume that I'll have to use Odin to go back to stock and re-partition? Any suggestions would be appreciated.
Click to expand...
Click to collapse

joeinternet said:
Sounds like your /data is encrypted. When you're prompted for a password, that's to decrypt the /data partition (it's probably the PIN she uses to unlock the phone). Hitting cancel simply leaves /data unencrypted and unmounted. If you hit mount within TWRP, you'll probably see a "Decrypt Data" button. Try using the PIN and see if that works.
Joe
Click to expand...
Click to collapse
Yes, I think you're right about the encryption. How does /data become encrypted? She doesn't recall encrypting it through settings, of course. Her usual pin doesn't work to allow access either. If I can't figure out the password to decrypt /data, what's next?

Within CM, the ability to encrypt /data is selected within settings. It will ask you to set a pin or passphrase, have more than 80% battery and will reset to encrypt (you'll see a green wireframe android icon and an encryption progress meter). This is all a conscious decision, so someone must have gone in there to set it, if that's the reason why it's asking for a password. You can set a different password for encryption, but you would have to do this from the command line, which doesn't sound likely here.
If encryption was interrupted, it's possible the drive isn't encrypted, but TWRP thinks it is (the key data is stored at the end of the partition). I'm paraphrasing, but if that bit is set, it will always think the partition is encrypted. The only way to wipe that is to completely wipe the /data partition, which you probably don't want to do unless you've got good backups (and nandroid will not backup /data/media, so be careful with that option).
Do you know if the phone had adb debugging enabled? You could try running logcat while it boots to see what the issue is. I had something similar happen to mine (hanging at the CM icon at boot) when I upped from the October CM10.2 nightlies to the M1 release and ended up using ODIN to return to stock - it's a good thing I had backups!
You can get a shell while in recovery to poke around. You can try mounting from the command line there (the /data partition will be listed in the /etc/recovery.fstab file).
If all else fails, and you have good backups, you could try wiping /data from within TWRP, but keep in mind that all pictures, texts, music, etc will go with it! I would only do this as a last, last resort.
I've seen several threads lately about issues with the partition layout in recent flashing (esp. with the MF1 update). I've reverted back to stock as a precaution, myself.
Joe
erc. said:
Yes, I think you're right about the encryption. How does /data become encrypted? Her usual pin doesn't work. If I can't figure out the password to decrypt /data, what's next?
Click to expand...
Click to collapse

joeinternet said:
Within CM, the ability to encrypt /data is selected within settings. It will ask you to set a pin or passphrase, have more than 80% battery and will reset to encrypt (you'll see a green wireframe android icon and an encryption progress meter). This is all a conscious decision, so someone must have gone in there to set it, if that's the reason why it's asking for a password. You can set a different password for encryption, but you would have to do this from the command line, which doesn't sound likely here.
If encryption was interrupted, it's possible the drive isn't encrypted, but TWRP thinks it is (the key data is stored at the end of the partition). I'm paraphrasing, but if that bit is set, it will always think the partition is encrypted. The only way to wipe that is to completely wipe the /data partition, which you probably don't want to do unless you've got good backups (and nandroid will not backup /data/media, so be careful with that option).
Do you know if the phone had adb debugging enabled? You could try running logcat while it boots to see what the issue is. I had something similar happen to mine (hanging at the CM icon at boot) when I upped from the October CM10.2 nightlies to the M1 release and ended up using ODIN to return to stock - it's a good thing I had backups!
You can get a shell while in recovery to poke around. You can try mounting from the command line there (the /data partition will be listed in the /etc/recovery.fstab file).
If all else fails, and you have good backups, you could try wiping /data from within TWRP, but keep in mind that all pictures, texts, music, etc will go with it! I would only do this as a last, last resort.
I've seen several threads lately about issues with the partition layout in recent flashing (esp. with the MF1 update). I've reverted back to stock as a precaution, myself.
Joe
Click to expand...
Click to collapse
Hey Joe, I appreciate you taking the time to answer the questions. I did edit my earlier response while you were responding, but to go into slightly more detail, her phone was just sitting on the arm of the couch, when she realized that it was off (it had been on just prior to that). She assumed the battery had died, but when I charged it to 100% and tried to boot it, that's when we found out that it wouldn't boot.
Anyway, wiping data isn't an issue. I have all of her photos and videos backed up, and most of her important stuff is stored in Google Drive. Unfortunately, trying to wipe data actually throws an error. Can you wipe /data if you can't even mount it?
EDIT: When I try to format data in TWRP, I get errors saying "E: Failed to decrypt data", and then it stops at "Updating partition details..."
Possibly a coincidence, She was previously using CM10.2 nightlies and just recently went to the M1 release.
So if we can't mount or wipe /data from recovery, I assume the next step is to go back to stock with Odin? And if that's the case, can you point me in the right direction? I am downloading Official VRBMF1 4.1.2 right now. Do I need a PIT file or something to fix the partitions?
Thanks again

Hrm..
I'd say going back to stock with ODIN will definitely get things back on track. You might need a PIT file to re-partition the device. You'll want to make sure it's the PIT for your model of phone (Verizon 16GB GS3, for example). Google turned up this:
http://teamuscellular.com/Forum/topic/3882-pit-files-for-all-us-variants-of-sgsiii/
I'm the SCH-I535 16GB so I used that one.
One other caveat - be sure you're running ODIN from a real PC - I was using a Virtual Machine and that caused issues.
Joe
erc. said:
Hey Joe, I appreciate you taking the time to answer the questions. I did edit my earlier response while you were responding, but to go into slightly more detail, her phone was just sitting on the arm of the couch, when she realized that it was off (it had been on just prior to that). She assumed the battery had died, but when I charged it to 100% and tried to boot it, that's when we found out that it wouldn't boot.
Anyway, wiping data isn't an issue. I have all of her photos and videos backed up, and most of her important stuff is stored in Google Drive. Unfortunately, trying to wipe data actually throws an error. Can you wipe /data if you can't even mount it?
EDIT: When I try to format data in TWRP, I get errors saying "E: Failed to decrypt data", and then it stops at "Updating partition details..."
Possibly a coincidence, She was previously using CM10.2 nightlies and just recently went to the M1 release.
So if we can't mount or wipe /data from recovery, I assume the next step is to go back to stock with Odin? And if that's the case, can you point me in the right direction? I am downloading Official VRBMF1 4.1.2 right now. Do I need a PIT file or something to fix the partitions?
Thanks again
Click to expand...
Click to collapse

joeinternet said:
Hrm..
I'd say going back to stock with ODIN will definitely get things back on track. You might need a PIT file to re-partition the device. You'll want to make sure it's the PIT for your model of phone (Verizon 16GB GS3, for example). Google turned up this:
http://teamuscellular.com/Forum/topic/3882-pit-files-for-all-us-variants-of-sgsiii/
I'm the SCH-I535 16GB so I used that one.
One other caveat - be sure you're running ODIN from a real PC - I was using a Virtual Machine and that caused issues.
Joe
Click to expand...
Click to collapse
Well, I wish I could come back with more insightful information, but through a bunch of poking and prodding in recovery, I was able to eventually format /data without having to use Odin. Thanks for the link, though. I'm saving the PIT file (same as yours), because who knows when it'll be needed.
This is actually the second time this phone has been stuck at the Galaxy SIII logo screen (with Cid, before the boot animation) in the past couple weeks. Both times were with the Cyanogenmod 10.2 M1 release. I think I might try RC1 to see if it behaves any better, but if not, it's back to stock she goes. If my wife didn't find TouchWiz so hideous, I'd likely go skip trying RC1 and go straight to stock and wait patiently for the 4.3 OTA.

[Q] Failed to mount /data

Hello, I wanted to know if any of you could help me.
My GT-N8000 suddenly shut down, which wouldn't have been that strange if not for the fact that it did so without the usual "shutting down" message. I plugged it in the charger and was greeted on boot by the message "encryption failed, please perform a factory reset" (actual message : "echec du chiffrage"). I have no root nor cfw (I planned on waiting until the end of the warranty, that is next month). I also didn't update to kitkat so the only reason I can see to this problem would be the tablet having shut down improperly as it was low on battery.
I already tried rebooting several times with and without the sd and sim, to no avail, so it seems I will have to reset. Recovery says /data cannot be mounted, so i was wondering if it affected the internal sd and if there was a way to recover the data on it or is it definitely lost ?
I have attached the recovery below. Thank you for your help.
[edit] although I wasn't counting much on it working, I tried to update to Kitkat trough Odin3 just in case. The only change is that now i've got a prettier error message (and startup sound).

Seems like my files are gone for good, but i'm giving an update in case someone has the same kind of problem but more luck than me.Most of the important stuff was backed up but it still sucks.
I wanted to do an adb pull, but due to the fact that it prevented my note from being detected when in MTP mode, I had USB debugging disabled (though I don't know if the note remembered my settings at that point). I installed Clockwork Recovery via Odin to enable adb and did my pull...
C:\Users\XXXXXX\Desktop\adt-bundle-windows-x86-20140321\sdk\platform-tools>adb pull /data
pull: building file list...
0 files pulled. 0 files skipped.
so it cannot be pulled (not surprising as it cannot be mounted). But this could be useful for someone who has a minor error preventing them to boot, but who can access recovery and download mode and would like to make a backup before wiping.

[Q] Soft Bricked tab, no custom recovery and no way of selecting USB debugging option

So i soft bricked my device while trying to install the latest 4.0.1 image. I tried hard wiping the device and wipe cache partion from Stock Recovery but didn't help, still wouldn't boot. I tried installing the image in Stock Recovery from Apply Update From External SD Card, but i got a few errors first "E:Failed to map file Operation aborted", i took a look at the file and it had about 1.67gb extra in "Userdata" i tried deleting that file and reinstalling from external sd card but then i got "E:footer is wrong" "E:signature verification failed" Operation Aborted.
Now i'm trying to install update from ADB (Surprisingly if i have the tab connected and im in Apply Update from ADB the tab is recognized in ADB
Code:
adb devices
serial # sideload and i have updated the drivers) But if i try to flash the recovery file 4.0.1 (provided from the developers site [cant post links]) "i just get waiting for device"
Anyone know how to get around this issue in ADB or properly install from external sd card without getting errors?
(Alternative read to my problem posted in the Nvidia Forums 98% sure i soft bricked my device [cant post links]

Did you ever find a fix? I'm having a similar problem.

Try to use fastboot restore everything.

I can't get it to connect to fastboot. When it loads the boot loader and I try to select fastboot protocol it fails.

Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!

rom fiend said:
Wow this thing sucks! I'm really appreciating my Samsung with Odin right now! So I finally got it to connect to fastboot (don't ask me how, I don't know) unlocked the bootloader and flashed twrp. Now it won't flash supersu in adb sideload so I put it on an SD card (which now magically mounts and works now) and flashed the zip in recovery but it says at the very end of the process while trying to update the partitions that it can't mount the data and system partitions so I'm not sure if I'm actually getting root or not and if so if it's permanent I have no way to tell. I think this is because they have been accidentally wiped. Do you think it is safe to try to flash a rom in recovery from external sd card? And if so which one? I have no idea which version bootloader, kernel, or os is or was on this device...
Update: I think I may start a new thread in the Q&A/Help section so that I can try to get a vast concensus. Thanks!
Click to expand...
Click to collapse
Yes flash a ROM in recovery.
Try Resurrection Remix. It'll resurrect your device

Just tried flashing bliss 6.2 and it won't get past the nvidia screen. It says it flashes successfully but I still get a bunch of "can't mount such and such partition" errors during the flash sequence. Not sure what to do, I can post pics if you guys want.

If you got/can get TWRP on there now, the advanced wipe menu will allow you to check /data for errors. As for /system, wipe it. If you get errors that e2fsck can't fix in your TWRP log, you'll have to put on your data recovery hat on. If it's that important to you, my advice is to adb pull the right file under /dev/block. You won't get a block device, you'll get an exact image of your data partition. Once it's fully pulled (it'll be 10 GB or more on a 16GB device), make a copy of it first thing, and use data recovery tools (testdisk, or if you really know what you're doing, debugfs). If you don't have anything valuable on /data (remember that any backups you took from recovery go in /data/media by default), just format that and be done with it.
Pray that there are no errors after you format everything, because that usually means your NAND is toast.
If your errors are hardware ones, you're royally screwed. Same thing happened to my Nexus 7 2013 model a year ago. Only way to use it is to flash a modified kernel that will use an attached USB drive exclusively as storage. If the NAND is toast inside the boot partiti,try replacing recovery, otherwise, you have to tether boot it (fastboot boot) every time you want to run it, unless you have the guts to try repartitioning the NAND (unlike on PCs, messing up there is an instabrick).
Since the Shield Tablet can use SD cards, you're better off. No USB drive needed.