[Q] Internal sd card issue - Captivate Q&A, Help & Troubleshooting

hello, I have the Samsung Captivate and am having a problem with the internal sd card. I went to put android 2.2 froyo and everything went well said success threw odin but my phone will boot up but once it gets to the galaxy s screen it stops. I have done the update threw odin several times and I run into the same problem. I got into system recovery mode and formatted everything cause it says that there was an error in the internal sd card, and needed to be formatted so I did that. Now when I go to reinstall packages it gives me this list.
--install from sdcard...
Finding update package...
opening update package...
Verifying update package...
E: failed to open /mnt/internal_sd/update.zip (no such file on directory)
E:signature verification failed
Installation aborted
any help would be much appreciated thank you.

yeah....reinstall packages doesnt do anything unless there is a file on your sdcard called UPDATE.ZIP
what you need to do is go back into DOWNLOAD mode, not recovery mode and use ODIN.....

I did that and after everything finishes and reset comes up in the blue box the phone starts it will go threw a list and it comes to a data wipe failed in red and formatting CACHE and DBDATA then applying multi-csc, installing multi-csc. Then Install default apk files, please wait
E:Can't mount /dev/block/mmcblk0p2 (invalid argument0
E: copy_data_default_apk:cannot mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
Then I format the sdcard and go threw everything again and it does the same thing. Im trying to give all the details.

I've got the same problem with GT-i9000.
Tried to flash with pit 512 and re-partition and pit 803 with re-partition, but the problem remains.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

exactly the same problem here
anyone got the solution right?

off topic but....
@thebeast
Your posts are hard to read. I keep thinking you are throwing your phone.
threw - past tense of throw "I threw it out the window"
through - by way of "I updated through odin"

Yeah I have that problem sometimes cause I'm typing relatively fast while focusing on other Things. I also do not proof read, relying on spell check too much. Considering I was trying to explain exactly what was happening to my phone from memory and going "through" the process over and over some mistakes are bound to happen. I had my lil bro hussle an att support store and get me a new one hence why I never checked this thread.
If you are having the same problem as me you do or did Not have an update.zip file on your internal SD. You deleted it or it was removed some how so before u tried to install anything you should of put it back to stock and hopefully that would of fixed it but I do not know the solution based on the fact I never bothered fixing mine.
Sent from my SAMSUNG-SGH-I897 using XDA App

lol @ the grammar police.
Stupid question - have you tried to use ODIN to go back to stock before attempting to re-flash? ODIN usually completely wipes the phone and any of the silly issues that come up.

The problem that is encountered is using oden to update while its missing that file so it deletes and starts to install the new rom but cannot. So the phone is stuck in limbo, I tried to use the one click flash countless times left it for hours and it would never work. So maybe if you did that before u tried to put the rom it might have worked but not once the damage is done. As far as I know.

thabeast said:
The problem that is encountered is using oden to update while its missing that file so it deletes and starts to install the new rom but cannot. So the phone is stuck in limbo, I tried to use the one click flash countless times left it for hours and it would never work. So maybe if you did that before u tried to put the rom it might have worked but not once the damage is done. As far as I know.
Click to expand...
Click to collapse
I had a similar issue I think like 2 days back when I goofed up something in the framework folder. Nothing seemed to work.
So I had to revert back to stock using one click. That was the only thing that worked.

Yeah one click would not work for me at all trust me I tried that forever until I got the replacement.
Sent from my SAMSUNG-SGH-I897 using XDA App

thabeast said:
Yeah one click would not work for me at all trust me I tried that forever until I got the replacement.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Did u try going to clock work recovery and doing a "reset to factory settings"

I did and would not work. But I have a fully workout one now so maybe the Guy who is having the problem now should answer these questions lol
Sent from my SAMSUNG-SGH-I897 using XDA App

Related

*-a bootloop crash course and trouble shooting guide-*

WANT TO RUN HERO? READ THIS FIRST​
I understand that new people dont really know much about hero, and that is alright. They will learn to search and figure things out on their own, but i am a little frustrated with seeing this constantly in the hero ROM threads. " i am stuck in a bootloop, my phone stays on the htc screen"
THIS IS NOT A BOOTLOOP! A bootloop is when you see the hero with the little green android and then the HTC "flashing" logo. I will post a video of a bootloop in little bit, but in the meantime here are a few ways to fix a bootloop.
For a video of what a bootloop is, click on THIS IS A BOOTLOOP RIGHT BELOW THIS​THIS IS A BOOTLOOP​
1) wipe phone and wipe ext and reflash.
to wipe the phone boot into recovery and press alt+w or if running CMRecovery 1.3 or 1.4 you should be able to use the trackball and select the option that way. To wipe ext use these commands in either adb shell or recovery console... NOT IN TERMINAL!!!​
This is how I installed without any problems:
: rename to update.zip (if you are running cm1.4 recovery you can just place the zip in the root of sd)
: place in the root of sd card
: shut off device
: boot into recovery
: wipe
: go to console and hit enter (you can also use adb shell)
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
: now wipe again
: repair ext system
: flash
Enjoy!!
Click to expand...
Click to collapse
- Courtesy of Drizzy Drake Rogers
2) check to make sure you are running a PVT board. Cant remember right now if it is the three finger salute or power+camera. To do the three finger salute, boot holding the green button, menu, and the red button. At the top of the screen that shows up it will either say PVT or DVT.
3) redownload the .zip file for the rom you are trying to flash. Sometimes you may get a corrupt download or the transfer from computer to sd may go bad. A fresh download may help.
4) reformat your sd and recreate all partiitions usingparted in cyanogens 1.4 recovery image. It is one of the easiest ways to do things if you are not running linux.
5) and last but not least, if all else fails just go back to a stable cyan build or jf build.
Hope this helps everyone and cuts down on the questions junking up threads. I will bump this every now and then unless it gets stickied. Also expect edits to this for other questions that get asked. Before junking up threads try these options and SEARCH!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
-helpful links-
CyanogenMod Stable
CyanogenRecovery Image 1.4
How to partition using gparted
THIS IS A QUICK TELL ALL TO GET DANGER SPL, RADIO, AND A STABLE ROM RUNNING
Happy flashing everyone!
WANT TO RUN HERO? READ THIS FIRST​
Fantastic Info. People need someone to spell out what's what.
Thank you it works. When I apply updates do you re-do all of this?
bump this. this will cut threads in half
sillyshyme said:
Thank you it works. When I apply updates do you re-do all of this?
Click to expand...
Click to collapse
not all updates, always read the changelog for a ROM. if you are simply UPDATING to a NEWER version of the SAME ROM, you MIGHT NOT have to do all this. this is mostly for when you get a bootloop. if you are changing hero roms, i would say yes, do everything you can, wipe, wipe ext, and what not. this will help about the bootloop.
I use Hero-V1.5 by Drizzy and it does not state in change-log.
sillyshyme said:
I use Hero-V1.5 by Drizzy and it does not state in change-log.
Click to expand...
Click to collapse
ok so what are you trying to do? go to a different Hero rom? if yes, then you need to wipe phone and ext, if updating from drizzy 1.4, i would say not to wipe, but if you get a bootloop wipe phone and try again.
please make this a sticky!!!! this a good info. hopefully if people search,it will help them out . great write up polosjr
palosjr said:
ok so what are you trying to do? go to a different Hero rom? if yes, then you need to wipe phone and ext, if updating from drizzy 1.4, i would say not to wipe, but if you get a bootloop wipe phone and try again.
Click to expand...
Click to collapse
Do this cause I just updated to drizzy's newest hero. I went from another hero Jac hero and I just did the update zip and got bootloop. I did whats on the top of this page and im running new rom so thanks
Ok, so I've followed all of these steps, except repairing the file extensions. When I try to do that I get an error in the recovery console. Does anyone know of anything else I can try?
rp1783 said:
Ok, so I've followed all of these steps, except repairing the file extensions. When I try to do that I get an error in the recovery console. Does anyone know of anything else I can try?
Click to expand...
Click to collapse
format your sdcard and then recreate your partitions

[Q] Bricked - Samsung Logo Repeat, Can't Fix by Stock Rom

Hi all,
My i9000 cannot boot successfully, it repeats the samasung logo again and again.
And when I try to re-flash the stock rom - 20110531_ZSJV5_2.3.3_ROOT_STOCK by ODIN
After reboot, it shows following Error:
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI menu for format and reboot action.
Media files copy failed
Click to expand...
Click to collapse
Then it keeps repeating the samasung logo again and again.
Please help!!!!
Can you access the download screen (volume down + home + start) or CWM screen (volume up + home + start)?
If you can access the download screen, use Odin and download the stock Gingerbread from online (do google search), make sure you also have a PIT file like PIT 512 or something, and have the re-partition ticked, try that and see if it fixes the problem.
If you access CWM, maybe voodoo lag fix is on and didn't properly format the partitions.
Thanks
I have tried using ODIN 1.8 and I9000ZSJV6
But the problem still retain
The screen shoot :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need to get a .pit file (512) and use repartition in Odin when you are flashing the original rom.
Yeah~I have used PIT512 and selected Re-partition, but problem still remain........
Damn ... it looks bad.
I have a suggestion.
Push a speedmod kernel with odin.
Enter recovery mode.
Convert the partitions to RFS (even if they are reported as such).
Redo the flashing of the original rom.
O...situation goes really bad
After I have flashed SPEEDMOD, I enter CWM
and try to convert to RFS, it said:
Can't mount /mnt/sdcard
Backup failed!
Then quit.
And I try to mount internal SD,
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblo0)
(No such file or directory)
Error mounting SDCARD:!
It looks like you have issues with the nand memory. I'm not sure 100% about it but it sounds like this.
In case your nand flash is dead, I really don't know what can you do ... there are few topics related to this issue. Check them out and see maybe is a solution somewhere.
don't use JV6, try flashing using JVQ, and don't use rooted versions, use a pure stock, try using Odin 1.7. It if can't mount, maybe there's a corrupt internal SD.
You may want to look at the stock rom vs an odin custom rom (like darkys resurection edition) and see if everything that that the custom has (minus the mods) is in there. I would get a mounting error for db_data from my stock rom (drove me nuts) because the stock roms did not update that and there for with a re partition it was missing.
I finally found another post on the CM7 forums that mentioned it so it could be an issue for your rom too?
If you determine which file it might be you can pull it from an earlier stock rom (one of them should have it).
You might even try flashing darky's. if it works then you know its a file issue and the phone is likely fine.
G
I flashed over 10 different roms with re-partition but nothing change...........
but luckily warranty should still cover, it is now in factory.....
Thanks All~
Similar problem: Phone stuck in boot up loop
Okay so about 2 months ago rooted and put a new rom on my vibrant. Last night I decided I wanted to go back to the original stock rom by restore my phone back to its original factory settings (at the time it made sense to me). I did this by turning the phone off, holding the volume buttons and power button until a menu came up where I selected wipe to factory setting. In doing this I cleared the rom I had on my phone and am now stuck in a loop where my phone keeps trying to turn itself on but has nothing to boot up. I am able to get to the menu that enables me to wipe my phone to factory setting etc but that hasnt helped all too much. I'm unable to mount my phone now on my mac in order to put a new rom on the sd and Oden does not seem to work for macs and I do not want to put a virtual machine on my computer but will if thats the only solution. PLEASE PLEASE PLEASE HELP!
That doesn't wipe to factory settings if you had a custom rom. It just wipes the user areas so IF you had a stock rom it would be back like day 1 but with a custom rom its like day 1 of the custom rom.
Though something else happened here too.
G
Sent from my GT-I9000M using XDA Premium App
Don't use a mac use Odin and do it on windows, download the stock jvq rom again except in windows and use the 512 pit file aswell. See if that works.
Sent from my GT-I9000 using XDA App
Also forgot to mention when using Odin in windows make sure you have the windows drivers by downloading Samsung kies. From the Samsung website.
Sent from my GT-I9000 using XDA App

[help] E:failed to mount /sdcard (File exists)

hey guys,
I have this following error after i restarted my phone
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet, please UI menu for format and reboot actions
Media files copy failed.
i have searched everywhere and found a solution in http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
However, im new to adb commands is there anyone who can give me step by step guide or anyone who had previous experience could help me
i have also tried http://forum.xda-developers.com/showthread.php?t=984140
did not work
thanks in advance
so im guessing no one had this problem
Does this happen under clockwork mod when you boot up the phone? As in you get the clockwork mod recovery right after you boot up with messages like "Error.." etc saying it can't mount stuff? If yes then you should use the PIT file 512 through odin, then flash a stock ROM. This should resurrect your phone.
thanks for your reply
I have flashed 512 pit file followed by 3 files of a stock rom still no luck
*sigh*
Is your signature up to date? You use the Oserx?
So one time you rebooted your phone, this error suddenly appears?
yea i was using oserx v1 with lagfix, after couple of days i got couple of FC than restarted this error emerged
This is just a wild shot, but you can try if you are desperate
http://www.sammobile.com/forum/showthread.php?t=17
Choose the I9000XWJS3 ## with 512 pit
Tick the Repartition box like in the picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After flashing, do a factory reset from the recovery meny. Good luck
Thanks for ur reply
I have already done this with no luck :-(
Anyone else have any idea?
Cheers
I also had this problem. Was on stock JVT with semaphore, partitions converted to ext4.
I decided to reboot my phone for no particular reason (was working reat) and when i powered it on kept boot looping without really getting past the samsung gt-i9000 white letters / black background screen.
CWM recovery said it was unable to mount any partition. External SD mounted fine, just nothing from the internel sd. No system, data, whatever. Got me thinking i may had my internal sd malfunctioning.
I just flashed it with odin and my stock branded operator rom (2.3.3) and done nothing more. No repartition. Working great. Was probably some ext4 error.
Before that i had been using cyanogen stable. Started giving FC like mad, so i flashed that stock JVT. On hindsight it may only had been the data partition that had run out of free space but i had no way of knowing when it happened and needed my phone running.
Reflashing got mine running again. Maybe try with Heimdall if odin's not working for you? Be sure to get a complete rom, with bootloaders and such. I'd suggest your operator's stock one. That way you can also send it back to samsung if it still doesn't work.
Thanks for ur reply guys...
Went to some phone repair shop.. They said internal memory card is "fried" and it's going to cost me from $120-250 (Aussie dollar)
worst come to worse it's gonna cost 250 and add another 150 I can get a new phone
So thinking now lol
deadey3 said:
hey guys,
I have this following error after i restarted my phone
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet, please UI menu for format and reboot actions
Media files copy failed.
i have searched everywhere and found a solution in http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
However, im new to adb commands is there anyone who can give me step by step guide or anyone who had previous experience could help me
i have also tried http://forum.xda-developers.com/showthread.php?t=984140
did not work
thanks in advance
Click to expand...
Click to collapse
Same situation here. I've tried everything and now I dont know what to do anymore
Flash to stock rom than root agn.
Sent from my GT-I9000 using xda premium
Flashing with odin any stock rom, with 3 or 1 file, repartition on or off, pit 512 or 803 it is not working.
I begin to think that internal sd is hardware damaged
Got the same problem. My battery died on me when i was taking a nap. Plug it into the charger, turn it on and got a bootloop on the galaxy s screen. No matter what rom i flashed. I'm getting lots of red text when the phone reboot. Failed to mount is always in that list and i also know that after flashing my old directory is still being listed when i try to "install update.zip" from a dir. So i'm guessing my eternal memory is fried too. Shame that i had that chip replaced 2 month after i bought the phone brand new. Only lasted me little over a year. And now my provider want $200+ for repair. What a joke. i just bought a s2 galaxy 2 for 460 off craiglist so i don't have to deal with it anymore.
Guys it's a hardware problem. I've tried so many solutions but still no luck.
I don't even remember how did i end up with this problem !​
Had this issue and resolved it no problem.
Flashed with odin 1.85 used pit 512 and three files (csc, pda, phone) & repartition checked followed by second flash of csc, pda, phone, no pit and repartition unchecked.
If not working try another stock rom. I had this with one and downloaded a different and all worked. also make sure kies and and kies services aren't running in the background.
Sent from my GT-P7500 using xda premium
Deleted link. Thread contained incorrect info.
Sent from my GT-P7500 using xda premium
got the same issue here

Bad SBF

Hi guys!Sorry for my post but i don't know where to post.So,let's start.
First i install a sbf file from sbf room's.The process was a success.When i start the phone to look i saw i don't have the Play Store and File Manager to install a new ROM.
When i try to install the ROM i have an error:
E:Can't open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
E:failed to open /sdcard/update.zip(No such file or directory)
E:signature verification failed
Installation aborted.
I have a Motorola Milestone A853.It is rooted.
I need help because i don't want to go in service because i know we can fix this problem.This SBF is bat because the battery is go to 0% in just few hours.Sorry for my bother but i need much help.Thanks you!
You have to flash vulnerable recovery again.
Eiertschik said:
You have to flash vulnerable recovery again.
Click to expand...
Click to collapse
ok i will try
dragosneagu95 said:
ok i will try
Click to expand...
Click to collapse
I had made the root.Everything goes ok.My phone was rooted again.But the error with sd card persist.:crying:
I don't know what can I do....
Are you sure the update.zip file and "OpenRecovery" folder are on your SD card?
Eiertschik said:
Are you sure the update.zip file and "OpenRecovery" folder are on your SD card?
Click to expand...
Click to collapse
First,beause of this SBF i don't have on my phone the File Manager and Play Store.I don't see the files.Just see the memory in settings.
Second, the update.zip goes successfully. Appeared a message that my phone was successfully rooted.
I will come with somes images...mybe you will now.
dragosneagu95 said:
First,beause of this SBF i don't have on my phone the File Manager and Play Store.I don't see the files.Just see the memory in settings.
Second, the update.zip goes successfully. Appeared a message that my phone was successfully rooted.
I will come with somes images...mybe you will now.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Take a look and reply please.
Guys do you know some answers or can i go to service?
Did the apps HSTcmd, My Sign, Superuser Whitelist already come within the sbf?
If yes then you did NOT get an original sbf.
Eiertschik said:
Did the apps HSTcmd, My Sign, Superuser Whitelist already come within the sbf?
If yes then you did NOT get an original sbf.
Click to expand...
Click to collapse
no,they didn't come
but if i install a SBF over SBF i brick my phone?I tried this solution on a Defy and i bricked.Tell me please.
You can get the stock SBFs from HERE.
Erovia said:
You can get the stock SBFs from HERE.
Click to expand...
Click to collapse
Ok but who is the original SBF?
And if I install a SBF over SBF I brick my phone?
These are all original ones. You should choose the one which is closest to your mobile carrier.
I can't say for sure, but I don't see how it could brick your phone. Writing the same data over and over into the memory of your phone doesn't make any difference.
Erovia said:
These are all original ones. You should choose the one which is closest to your mobile carrier.
I can't say for sure, but I don't see how it could brick your phone. Writing the same data over and over into the memory of your phone doesn't make any difference.
Click to expand...
Click to collapse
I will try and I'll come with news
GOD Bless You!I fix the problem with yours answers,special Erovia(your guidance was great),but all members.Sorry for my raunchy style to write but I was sad.Thanks you again!:fingers-crossed:

Bricked phone, what can I do?

Hi there. My cousin's phone stopped working some weeks ago. He tried to wipe everything via TWRP and installing different ROMs but no ROM seems to work. Now, when he does a complete wipe, he gets the error "E:Unable to wipe '/sdcard1' -- unknown file system 'auto'" and "Unable to mount storage". Also, now everytime he tries to copy a ROM to the TWRP folder (the only folder which appears on his MacBook or his friend's PC) it stops at 16k and he can't copy it.
What can he do to fix this? Nothing seems to work and a guy at a service center said it was a disk error and that there was no hope for the phone.
Here's a screenshot of it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance!
Uhm... Why don't you remove the faulty micro SD from the phone?
This doesn't look like a bricked phone at all - "storage" and "sdcard1" refer to external storage.
Remove the phones's cover and remove the SD card (do NOT go beyond step 2, FFS). Then you can try to run some diagnostics or format it on your working phone, tablet, MAC or PC or you can buy a new one - they are quite cheap.
Then add a proper ROM (and proper GApps) on the card and stick it back in. Moto G 2014 comes in two variants - make sure your cousin's device is an actual Titan - chances are it is a Thea, if you're in Europe; that's why the TWRP doesn't want to install it. Choose one from here.
Remember you have to delete everything on the internal card through the recovery utility I see in your image before flashing a new ROM - do NOT wipe the SD Card; it stores your installation files: the properly chosen ROM and GApps you add after you format it through a different device.
If it works, make sure you do NOT format it as adopted/internal storage when/if asked by the installation wizard at first run, once the flashing is complete. This is probably why the phone got in this state in the first place.
Now I have it in my hands, this is the situation:
- Both on my PC and in TWRP it says I have 766MB free of a total of 5637MB when I don't have anything stored there and when I try to copy anything onto it it just gets stuck at 0% forever
- Tried repairing and changing file system: apparently Data is F2FS and the rest is EXT4 but everytime I try to repair or change any partition it says it worked but then it's all the same (still not working, with the file system it had before)
- Tried updating to the newest TWRP (via fastboot and also TWRP) - like what happened above, it says "done" but then it shows the TWRP version number I had before (3.0.2-3 and not the 3.1.1-0 I tried to install)
- He had no SD card inside but apparently had already tried to install a ROM with it. I put a 4GB one inside with the lastest LineageOS and all I get is "E1001: Failed to update system image unconditionally... / E:unknown command [log] / Updater process ended with ERROR: 7 / "Error installing zip file '/sdcard1/lineage.zip'
- Also the error "Unable to mount storage" is constant
I am running out of options here, don't really know what else I can do...any help? Thanks in advance!
Framboesa96 said:
Now I have it in my hands, this is the situation:
- Both on my PC and in TWRP it says I have 766MB free of a total of 5637MB when I don't have anything stored there and when I try to copy anything onto it it just gets stuck at 0% forever
- Tried repairing and changing file system: apparently Data is F2FS and the rest is EXT4 but everytime I try to repair or change any partition it says it worked but then it's all the same (still not working, with the file system it had before)
- Tried updating to the newest TWRP (via fastboot and also TWRP) - like what happened above, it says "done" but then it shows the TWRP version number I had before (3.0.2-3 and not the 3.1.1-0 I tried to install)
- He had no SD card inside but apparently had already tried to install a ROM with it. I put a 4GB one inside with the lastest LineageOS and all I get is "E1001: Failed to update system image unconditionally... / E:unknown command [log] / Updater process ended with ERROR: 7 / "Error installing zip file '/sdcard1/lineage.zip'
- Also the error "Unable to mount storage" is constant
I am running out of options here, don't really know what else I can do...any help? Thanks in advance!
Click to expand...
Click to collapse
Why don't you try reflashing the stock rom..Once I encountered a similar problem and reflashing the stock rom solved it

Categories

Resources