Database Info

[Q] Phone broken or still hope?

Hello everydody, I am experiencing some difficulties with my Samsung, model GT-I9003-phone which "dropped off a lorry" somewhere next to my relatives somewhere in Asia. When I goth the device, it was in a non-working condition, except a boot-loop and the download-mode. Back then, I had the package of the phone where the exact version ( I don't know if this is what is called "Baseband" or at least is called baseband at my wife's GT-I5003) was specified. So, back then, I was able to find the exact ROM for the device. Unfortunately, the box with the version number now is - somewhere.
After flashing a stock-rom, I managed to enter recovery-mode where I read something about the internal memory being corrupt. As far as I can recall, I then mounted the external SD-Card and somehow managed to reboot the system back to almost normal operation. Even reboots appeared to work normal, besides the fact I had no memory access, neither to internal nor to external sd. In addition, GPS malfunctioned, too.
Unfortunately, even this state didn't last for long time. After several weeks of now-and-then-use, the system just broke down again into a boot-loop. After some time of flashing a variety of stock roms, I managed to flash clockworkmod recovery which works perfectly well. Unfortunately, I didn't manage to root the phone before it "collapsed" again. Besides the possibility, I'd guess this could be a resaon for CWM being unable to flash a custom rom? Otherwise, I'd just test my way through the varieties of versions .
Basically, I do have two questions: 1. is there a possibility to find out if internal memory has failed - and if yes: How?
2. Is it possible to install any version of CM on that phone in the condition it is in?
Thanks a lot in advance for any answers

Hello everybody, I finally found the box . It reads GT-I9003MKDTHL. Is my assumption right that there are no such things as basebands in the GT-I9003 any more and I should be able to flash pretty much any firmware? Furthermore, today I tried to format what is specified as "sd-card ext" in CWM fir GT-I9003 and it gives me an error-message. When I flash "sd-card", my external sd-card gets formatted. So, I'd presume the internal sd is just fried. I read about a workaround for GT-I 9000, where someone installed Androd on a partitioned external SD. Is there somebody who knows someboy having heard about somthing similar working with the GT-I9903?

One step forward...
Hello everybody, I finally managed to get some light into my issues as I once again figured out how to get a software installed and running . It's this one:
http://forum.xda-developers.com/showthread.php?t=2329200
Thanks a lot to the guy who just posted it somewhere where id could do good...
By the way, I figured out that this software actually includes the Baseband.
As in this version, the original recovery system is running and giving me an error message when I start it without external SD-card, I am now quite sure that the internal memory has just failed as this error message was specified in another posting of someone who had a similar issue with a GT-I9000.
The biiiig "Outch" is, that I am unable to install any CWM Recovery System with that Baseband..This results in me not being able to upgrade the software to ICS, where - as far as I read some troubleshoot-information - will enable me to mount an additional partition on my SD-Card as Data-Partition which isn't possible yet (i.e.: I can't access my SD for storing data or whatever - it's just specified as "not there").
I tried to install the XXKPE-Baseband to be able to go for KPQ which would enable me to install CWM Recovery. I also installed Bagarias CWM-normalboot-image via Heimdall - but I was unable both to boot the OS and to find any trace of a zip-file on the SD-card.
Edit: I managed to install the right CWM - it's mentioned in the post where I've got the firmware from... now, I only have to figure out how to deal with the fact that "officially" there is no SD-card inserted - or, better, that this SD-card is now flagged as "internal SD" - and how that machine can find the zip-file on it
Thanks for every bit of help with that issue

Try Aroma File Manager with Terminal
For SDCard issue you could probably switch them in vold.fstab in /system/etc
Good Luck !!!

try this- http://forum.xda-developers.com/showthread.php?t=2329200

[Q] Can’t mount external SD

Hello folks, yesterday I installed 4.2.2 update (ubranded with MG8 ending, i9105p), everything is working fine, with exception to my SD card.
In Settings -> Storage it doesn’t shows up, and the "mount" button is greyed out, just like no card was inserted. The SD card itself is working (checked on other devices), it uses FAT partition (I even tried to re-formate it) and, since the Recovery can acces (and eventualy flash files) from it, Android OS doesn’t see it. I tried mounting via ADB but I have no previous experience with it. I also tried wiping cache.
I’m gonna try re-flashing another firmware tommorow, I hope it will work. :cyclops:
But is there any easier way to fix it? Thx
UPDATE: The card was working fine after re-flashing, but sometimes when copying files on it, File manager hangs, and files wont copy. This issue also unmounts the SD and makes it unable to be mounted until you restart. Propably some sort of kernel issue? (According to testing and 1+ year of trouble-free expirience with the card on another device this doesnt look like a malfunctionic card)

[Q] Help - Can't do anything with my internal storage - Xperia T

So i have kind of a situation,
i'm running cm-11-20141102-NIGHTLY-mint.
So, yesterday, i erased my internal storage (in Xperia T a.k.a SD card 0), to renew my device a little bit.
But after that i literally can't do almost anything. My camera crashes as soon as i start it, gallery says there isn't any external storage, can't make screenshots, can't put stuff into the phone. When i try to put something via usb trough my computer it says that the device stopped responding or was disconnected and when i try it strough the phone file manager it says that can't be done and that i need more permissions which is impossible because i already have all r/w permissions.
I'm kind of desesperate right now. I tried to wipe all the data, syste, storage, cashe. Tried to reflash my rom to different one. Even ran some permissions fixes. But nothing worked.
Forgot to mention, there isn't anything on the internal storage right now except the foulder lost+found which seems empty and the clockworkmod folder into, which is weird, can put things.
Is there someone who run into the same issue ?

[Q] My phone suddenly says "Damaged USB storage"

So, here's the problem - I was just using my phone normally, when it froze - no big deal, recently it has been getting slower and I was just planning on factory resetting it after I back up everything. But, when it booted and went on the start screen, it says "Scanning USB storage for problems" or something like that and it says then "Damaged USB Storage -You may have to reformat it" and unmounts my SD card, so, I have no storage altogether. When I click on the notification it asks if I want to format USB storage. I just want to know if there's a way of retrieving some files, because in my phone FIle Manager there's nothing, and when I connect it to the PC (Windows XP), it doesn't dettect any stotage, if I do it through "USB Utilities" on my phone it shows two Removable Disks on my computer, which are empty, when I click on them it just says "insert disk into drive", and if I click "Turn on USB Storage" on my phone it just keeps on trying to connect, but can't.
I tried restarting it, taking the battery out, booting without an SD card, booting into safe mode, using adb to pull some files, searched the internet for a few hours but to no avail, found this "Tenoshare Android Data Recovery" but it needs root, which I'm not, so I tried rooting it with SuperOneClick - doesn't work, tried installing super user from the recovery menu from SD card, but it can't install it - I'm wondering if it's wortht it. So, now I don't know what to do - do I root my phone using the methods here (with odin and etc) and use that utility, do I just factory reset it (maybe try recovering files after I've reset it?), or is there any other available option to somehow recover the files? I'm on Android 4.0.4 unrooted with Baseband version I9103XXLQ3 - I had installed it a few years ago (my phone came with 2.3.6 and I just followed the instructions here on updating my firmware).
I'll be very grateful with any help, I just had a few more important files and the last time I backed up was in December, so any help is appreciated

Mounting a supposedly corrupted adopted-SD with TWRP?

Hi all. Apologies for the wall of text, I have a few questions following all of the background below.
Device info: Samsung Galaxy S7 32GB running LineageOS 16.0, NOT rooted; SD Card in question is a 128GB Sandisk MicroSD. All commands being run on computer running Ubuntu 19.10.
Yesterday, my phone gave me the "SD Card Missing" notification suddenly, and in the settings it said it was corrupted. I had had it set up as adopted storage, so it isn't a matter of just losing photos and such unfortunately - it seems as though there's important app and system data on it.
After trying several recovery programs to no avail, I came across this thread:
https://forum.xda-developers.com/general/help/corrupted-sd-card-adoptable-storage-t3801250
Which is very similar to my situation. Unfortunately I didn't find a fix here, but I did manage to make a full .img copy of the card itself, and find the encryption key at "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key" as per https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html . The problem I ran into with this guide was that I couldn't get the dmsetup command to work. However, when reading the comments of the post to see if anyone else had the problem, I saw someone mention retrieving the files through TWRP. So, I put the card back in the phone, and booted into TWRP.
In TWRP, I was able to browse through the SD Card perfectly normally with the file manager, despite the fact that it still read as corrupted when booting back into the system. So, I used adb pull (side question on this later) to retrieve the folders I was most worried about - largely what I could find of app data, my photos and videos, etc. I did not just pull the whole card at once, and I'll elaborate on why when I get to the side question about adb pull.
So, here are my questions:
1. Is it possible to mount this SD Card back to normal through TWRP? If so, how? I'd like just enough so that I can restore my apps as is onto the phone, and then convert the card to portable storage to avoid this mess again. While I do have the data pulled, it's little things like NewPipe playlists that I've got in mind here.
2. If above is not possible, how much loss am I looking at if I choose to 'forget' the adopted card? Will I have to do a factory reset?
3. (adb) When doing the adb pull, it was unable to skip any files it couldn't copy - i.e. corrupted images - and would simply stop on finding one. This means that, for example, in one folder it hit a corrupted file after 3400 successes, and stopped without copying the remaining 300. Naturally, if I had just done 'adb pull /external_sd/', then I probably would have lost a lot more because of this. Can I add any options to the command adb pull to circumvent this? I was unable to find any decent documentation on the command, but maybe I was searching for the wrong thing.
Any and all help is much appreciated, thanks in advance!

johnfr92 said:
Hi all. Apologies for the wall of text, I have a few questions following all of the background below.
Device info: Samsung Galaxy S7 32GB running LineageOS 16.0, NOT rooted; SD Card in question is a 128GB Sandisk MicroSD. All commands being run on computer running Ubuntu 19.10.
Yesterday, my phone gave me the "SD Card Missing" notification suddenly, and in the settings it said it was corrupted. I had had it set up as adopted storage, so it isn't a matter of just losing photos and such unfortunately - it seems as though there's important app and system data on it.
After trying several recovery programs to no avail, I came across this thread:
https://forum.xda-developers.com/general/help/corrupted-sd-card-adoptable-storage-t3801250
Which is very similar to my situation. Unfortunately I didn't find a fix here, but I did manage to make a full .img copy of the card itself, and find the encryption key at "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key" as per https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html . The problem I ran into with this guide was that I couldn't get the dmsetup command to work. However, when reading the comments of the post to see if anyone else had the problem, I saw someone mention retrieving the files through TWRP. So, I put the card back in the phone, and booted into TWRP.
In TWRP, I was able to browse through the SD Card perfectly normally with the file manager, despite the fact that it still read as corrupted when booting back into the system. So, I used adb pull (side question on this later) to retrieve the folders I was most worried about - largely what I could find of app data, my photos and videos, etc. I did not just pull the whole card at once, and I'll elaborate on why when I get to the side question about adb pull.
So, here are my questions:
1. Is it possible to mount this SD Card back to normal through TWRP? If so, how? I'd like just enough so that I can restore my apps as is onto the phone, and then convert the card to portable storage to avoid this mess again. While I do have the data pulled, it's little things like NewPipe playlists that I've got in mind here.
2. If above is not possible, how much loss am I looking at if I choose to 'forget' the adopted card? Will I have to do a factory reset?
3. (adb) When doing the adb pull, it was unable to skip any files it couldn't copy - i.e. corrupted images - and would simply stop on finding one. This means that, for example, in one folder it hit a corrupted file after 3400 successes, and stopped without copying the remaining 300. Naturally, if I had just done 'adb pull /external_sd/', then I probably would have lost a lot more because of this. Can I add any options to the command adb pull to circumvent this? I was unable to find any decent documentation on the command, but maybe I was searching for the wrong thing.
Any and all help is much appreciated, thanks in advance!
Click to expand...
Click to collapse
Hey...did u get dmsetup to work?