Database Info

Internal SD Card

Just a quick question about rooting to my internal sd cards. Just so everyone knows im using Froyo.
When i mount my phone and go to my computer i click removable disk drive H with 13.4 GB free. After clicking it 5 folders appear: Android, DCIM, external_sd, LOST.DIR, and Nook.
Now i am wondering if the internal sd is what all these folders are located on, or if there should be a folder for my internal sd. I originally assumed that it was all on the internal sd however after trying to root for the last 5 hours and failing its raised question.
after i click "reinstall packages" i then get an error:
_Install from sdcard....
Finding update package...
Opening update package...
Verifying update package...
E:failed to open/mnt/internal_sd/update.zip (No such file or directory)
now i know the "update.zip" file is the file added for the root, but according to this error it should be located to a folder name "internal_sd" however no such folder exists. Like i said before i thought the entire removable drive was supposed to be the internal memory so why would there be need for that folder and if i do need the folder do i just create it is is it a hidden file or... yeah i have no idea, help please?

Unfortunately you can't root Froyo with an update.zip (unless I missed a post). I did it this way Captivate JI6 (v2.2) Hacks (root, non-market, no start up sound)

you are right 2.2 cant be rooted by the update.zip method. Nothing can be loaded by an update zip at the moment due to changes in system

Delldorado said:
Just a quick question about rooting to my internal sd cards. Just so everyone knows im using Froyo.
When i mount my phone and go to my computer i click removable disk drive H with 13.4 GB free. After clicking it 5 folders appear: Android, DCIM, external_sd, LOST.DIR, and Nook.
Now i am wondering if the internal sd is what all these folders are located on, or if there should be a folder for my internal sd. I originally assumed that it was all on the internal sd however after trying to root for the last 5 hours and failing its raised question.
after i click "reinstall packages" i then get an error:
_Install from sdcard....
Finding update package...
Opening update package...
Verifying update package...
E:failed to open/mnt/internal_sd/update.zip (No such file or directory)
now i know the "update.zip" file is the file added for the root, but according to this error it should be located to a folder name "internal_sd" however no such folder exists. Like i said before i thought the entire removable drive was supposed to be the internal memory so why would there be need for that folder and if i do need the folder do i just create it is is it a hidden file or... yeah i have no idea, help please?
Click to expand...
Click to collapse
If you look closely at the messages it is giving you. It has found the update, opened it and then tried to verify it which is where it fails. The reason being that Froyo requires digitally signed updates. The root method we used for 2.1 uses an unsigned update file.
I am curious about the LOST_DIR folder. I have em too. Also note that the external SD card is no longer under /sd but /external_sd.

hmm alright i just hadnt seen anything that said i couldnt do it that way yet, i dont know anything about this stuff. went to that link but have no clue how to do that either so i guess im screwed

Delldorado said:
hmm alright i just hadnt seen anything that said i couldnt do it that way yet, i dont know anything about this stuff. went to that link but have no clue how to do that either so i guess im screwed
Click to expand...
Click to collapse
Read up on how to set up and use ADB from your PC (search this forum), specifically pushing/pulling files and using the shell. Once you've become familiar with that, the instructions for rooting JI6 won't seem so difficult.

i also wish i had read this before spending 7 hours aimlessly in front of my computer thinking i was on the brink of success every time i tried.

Problem with my rooted Inspire running Android Revolution HD not syncing correctly.

I got my Inspire and used it normally for about a month. Then I rooted it and tested out about 5 different ROMs and came to like Android Revolution for it's Gingerbread and Sense 2.0 that could have parts of it individually upgraded. (That's besides the point)
Anyway, as it only comes with an 8 GB microSD I looked on ebay for a 16 GB microSD and found one for about $20 or something, class 4. Anyway, I basically hooked up my phone with the old SD card in it, copied the entirety of its contents and then ejected the SD card and put in the new one. Pasted the contents from the old onto the new. Worked fine for a time. Now my phone will occasionally get stuck in a loop of boot animation, starting and working for 1 minute, then going back to the boot animation. I also noticed that any app installed to my SD through ZDBox becomes unusable. I then have to go back to the market and reinstall the apps as trying to restore from my Titanium Backup doesn't work.
I also have noticed that my photos and music can't be accessed. I even looked with root explorer and on my computer and can't find my music or photos at all. I've tried syncing using DoubleTwist and by copying and pasting the folders from the old SD to the new SD in the same directories.
Finally, just a bunch of force-close issues with everything on the phone. Using Rom Manager to Fix Permissions fixes things for a while but then it restarts.
I know it's a lot to read, but I don't know what is causing this and how to fix this. I even tried restoring a backup I had made, but it only resumed about 3 hours later. Any ideas or suggestions are welcome. Thanks in advance!

Things I would do:
If AR requires EXT4 sd card (it will say on the front page, and I believe it does)
-Format your sd card.
-Follow the steps for converting it to EXT 4 ( should be found on the front page)
-Create a back up with recovery or rom manager.(it doesn't matter which)
-Retain the 8gig back up.
-Wipe your phone through recovery (not through rom manager.)
-Redownload the rom.
-Re flash the rom.

Thanks, I'll be sure to try this later tonight.

Hate to reopen this topic, but when I tried to reflash the ROM, I was greeted with a an error saying I cannot open "(insert filename here).zip (bad)".
I've looked, and tried a couple of solutions other people have had, but so far they haven't worked. What can someone suggest?
I'm assuming it has something to do with the fact that the md5 checksums are different and don't match. I've downloaded AR HD about 5 times and moved to the phone. I get a different md5 checksum everytime.

Ssssschwartz said:
Hate to reopen this topic, but when I tried to reflash the ROM, I was greeted with a an error saying I cannot open "(insert filename here).zip (bad)".
I've looked, and tried a couple of solutions other people have had, but so far they haven't worked. What can someone suggest?
I'm assuming it has something to do with the fact that the md5 checksums are different and don't match. I've downloaded AR HD about 5 times and moved to the phone. I get a different md5 checksum everytime.
Click to expand...
Click to collapse
Make sure all anti virus is shut off when you dl the rom

zelendel said:
Make sure all anti virus is shut off when you dl the rom
Click to expand...
Click to collapse
Thanks for the advice. The checksum for the downloaded ROM matched, then I pasted it onto the SD and it matched when I checked it on the computer. Then I went into recovery and tried to load it and it's still giving me a the file bad error. I checked the checksum through recovery and it was a completely different checksum.
I'm really confused as to why I'm having these issues.....

make sure you disconnect the phone/sd card properly - sometimes the OS will report the file has fully written but the cache is still writing the file. If you can, use a service like dropbox or another file sharing (via web) and download the rom directly to the sd card - might get better results.

No need to bring back a very old thread. Thread closed

[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

Problem with large games not being able to decompress their data.

I've got Cyanogenmod 12.1 on a Galaxy S2 i9100 and the storage is a pain in the arse to be honest. I know the switch from FAT32 to EXT4 with JB or KK was supposed to be better for security, but for access it is abysmal. I can't copy large folders to the internal SD or else half way through the process Windows will tell me the device has been disconnected, I also can't install large games like Football Manager 2015 or Sims Freeplay because after they have downloaded their zip/rar and try to extract it they just crash (even when the phone is not plugged in), and if I copy the downloaded archive to my PC and extract it there it will crash when I try to copy the extracted folder back to the Android/data/ folder.
Is there a fix for this? I had no problems using FAT32 for many years, but now I have an internal storage that seems to choose when it wants to be visible to my computer and will decide to unmount(?) when something is being copied to or extracted on to it.
krashd

Nobody have any ideas? I've googled like mad but can't find this problem anywhere. It has to be ext4-related though because apps and games have never had a problem uncompressing their data until after 4.4
This is annoying the bejesus out of me because Football Manager keeps me sane on the train :/

Not even 'adb push' works! I did adb push with the -p switch to see progress and everything is fine for a minute or two and then
failed to copy 'xx.xx' to '/sdcard/data/xx.xx': Read-only file system
This is officially driving me up the wall now, surely someone has an idea of why my internal storage stops extracting an archive or copying files after a short period :/

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?