Hey guys, I just need to know how far up **** creek without a paddle I am and how I got here. I had a stock JF6, a friend told me to root with unleash the beast so I did. Been running great and aside from using metamorph to install a few swype themes and nav bar themes, it was stock. I had managed to learn a bit and heard clockwork mod was a great thing, and was making backups regularly.
Well since everything was going so well, I decided to dig deeper and install cognition 2.1. Things went fine, until I got to first boot, then I realized all my stuff was gone, should have known and me being changed my mind. So I went and booted into recovery, and tried to restore my most recent backup, well of course it failed when it came to data because cognition had formatted it.
Well after a lot of formatting data/cache, I tried to install the cognition 2.1.zip, got an error message.. Failed to install. After rebooting I was stuck in the att white screen boot loop. So once again formatted data, and this time I ran update.zip(unleash the beast).
HERES my question, now I seem to have some kind of hybrid, on first boot of cognition I got the custom boot sounds and wallpaper. Nothing now, however my baseband is now JH7, and it says something about voodoo lag fix. But still says 'beast .... Teaser' for system info.
I'm so confused, what's the best way for me to get a stable version of cognition running? Ill just install all my data, I just wabt to know exactly what my phone is running.
Sent from my SAMSUNG-SGH-I897 using XDA App
Best bet is to flash back to JF6, root, install ROM Manager, and load Cognition from that.
Also, that question its better suited for q&a, not the dev forum
Sent from my SAMSUNG-SGH-I897 using XDA App
sdotbrucato said:
Best bet is to flash back to JF6, root, install ROM Manager, and load Cognition from that.
Also, that question its better suited for q&a, not the dev forum
Don't forget to disable lagfix before you Odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
Sorry, I just mainly check here and the themes and apps section.. Completely forgot about the other ones.
So if I wanted to flash back to jf6.. Would I just get one of these stock dumps floating around and flash it? Or is there a better way?
Sent from my SAMSUNG-SGH-I897 using XDA App
Use the Odin One Click that's posted at the top of this forum. It will flash you back to stock in a matter of seconds.
Sportsguy15 said:
Use the Odin One Click that's posted at the top of this forum. It will flash you back to stock in a matter of seconds.
Click to expand...
Click to collapse
THANK YOU.
this is what I needed to know. So basically, odin one click, use any method to root (probably just use a one-click this time), and then download rom manager and install cognition from clockworkmod? and thats all it would take?
Much easier then what I had in mind.
bamathrasher said:
THANK YOU.
this is what I needed to know. So basically, odin one click, use any method to root (probably just use a one-click this time), and then download rom manager and install cognition from clockworkmod? and thats all it would take?
Much easier then what I had in mind.
Click to expand...
Click to collapse
Yep, that's all you need to do. I've started doing that any time I flash a new rom, ie, One-click to stock, root, rom manager, flash new rom.
I have had similar issues when I try to flash over an existing rom, plus it is nice to start with a fresh rom, no bugs.
bobbylx said:
Yep, that's all you need to do. I've started doing that any time I flash a new rom, ie, One-click to stock, root, rom manager, flash new rom.
I have had similar issues when I try to flash over an existing rom, plus it is nice to start with a fresh rom, no bugs.
Click to expand...
Click to collapse
Data on ext4 survives an Odin flash, so if you are on voodoo, it's a bit more involved than just flashing.
rajendra82 said:
Data on ext4 survives an Odin flash, so if you are on voodoo, it's a bit more involved than just flashing.
Click to expand...
Click to collapse
I saw something like this in the Cognition thread, about creating a file called "disable-lagfix" or something and placing it on the root of the sd. Is that the extra step you are referring too, and if so, I definitely need to do this?
bamathrasher said:
I saw something like this in the Cognition thread, about creating a file called "disable-lagfix" or something and placing it on the root of the sd. Is that the extra step you are referring too, and if so, I definitely need to do this?
Click to expand...
Click to collapse
Yes. That's the correct method to put /data back on RFS. Once you have created the file and rebooted, a robotic lady will inform you that the /data is being converted. Once this boot finishes, you are at a point where Odin or Clockwork will be able to help you. When /data is in ext4 format, the other programs don't recognize it, and don't work properly.
just for future reference, what type of data are you talking about here? I have no data I'd like to keep at this point, after I bricked my phone last night, I basically tried everything in clockworkmod until I got it back to a workable state so I'd have a phone to use today at work. How am I supposed to make it through a work day without being able to text? its impossible. haha.
So if I have no data I desire to keep, is this necessary or is this a different type of data, important data for the system?
bamathrasher said:
just for future reference, what type of data are you talking about here? I have no data I'd like to keep at this point, after I bricked my phone last night, I basically tried everything in clockworkmod until I got it back to a workable state so I'd have a phone to use today at work. How am I supposed to make it through a work day without being able to text? its impossible. haha.
So if I have no data I desire to keep, is this necessary or is this a different type of data, important data for the system?
Click to expand...
Click to collapse
If you noticed in my post I did not say data but /data. There is a difference.
On your Captivate there is a total of 16 GB of internal memory. The memory is partitioned into several block devices. One of these partitions is mmblk0p4, which once booted, is mounted to /data. This directory stores your apps installed from market, your user information, your call log, your text messages, and so on. It has to be working for your phone to boot up properly. Although /data looks like a directory, since it is a link to an actual device, it can be on its own file system which is different than other devices mounted to other directories. On a default Captivate (i.e., before you install Cognition, which includes a choice of two voodoo lagfix kernels) the block device mmblk0p4, mounted as /data is formatted in a proprietary Samsung RFS file system, which is too slow. When you install the voodoo kernel, on first boot, it formats the device in a much faster ext4 file system if there is no file or folder called disable-lagfix in /sdcard/voodoo, thus severely reducing the lag. The problem is that the default kernel, the recovery mode kernel, and the Odin flasher program understand how to deal with this device formatted in RFS. If your block device is in ext4 and you restore the system through Odin, you will end up with Odin not wiping off the contents of /data, which is what you actually wanted. I am not sure if you end up with a working /data device in RFS and a chunk of unused ext4 information, or a kernel not understanding /data in ext4 and hanging. If you are in this state, your best bet is to flash on a voodoo kernel through Odin, which will then understand the ext4 /data. Once the voodoo kernel boots, you then create the disable-lagfix file and reboot, to get /data back in RFS. Then you go into download mode, and wipe the /data on RFS with Odin.
rajendra82 said:
If you noticed in my post I did not say data but /data. There is a difference.
On your Captivate there is a total of 16 GB of internal memory. The memory is partitioned into several block devices. One of these partitions is mmblk0p4, which once booted, is mounted to /data. This directory stores your apps installed from market, your user information, your call log, your text messages, and so on. It has to be working for your phone to boot up properly. Although /data looks like a directory, since it is a link to an actual device, it can be on its own file system which is different than other devices mounted to other directories. On a default Captivate (i.e., before you install Cognition, which includes a choice of two voodoo lagfix kernels) the block device mmblk0p4, mounted as /data is formatted in a proprietary Samsung RFS file system, which is too slow. When you install the voodoo kernel, on first boot, it formats the device in a much faster ext4 file system if there is no file or folder called disable-lagfix in /sdcard/voodoo, thus severely reducing the lag. The problem is that the default kernel, the recovery mode kernel, and the Odin flasher program understand how to deal with this device formatted in RFS. If your block device is in ext4 and you restore the system through Odin, you will end up with Odin not wiping off the contents of /data, which is what you actually wanted. I am not sure if you end up with a working /data device in RFS and a chunk of unused ext4 information, or a kernel not understanding /data in ext4 and hanging. If you are in this state, your best bet is to flash on a voodoo kernel through Odin, which will then understand the ext4 /data. Once the voodoo kernel boots, you then create the disable-lagfix file and reboot, to get /data back in RFS. Then you go into download mode, and wipe the /data on RFS with Odin.
Click to expand...
Click to collapse
thank you for taking your time to write this up for me. Very helpful.
Related
"You do not have enough free space in /data to use this fix. Please free up space before using this fix"
?????????????????
I checked my /data folder -- it's empty except for a few small .txt files
I have a 32 GB external SD card
My internal SD card is 50% free
WHAT GIVES ??????????
Is there any other lag-fix's ?
I have OneClickLagFix V1+ (1.0 with extra's)
Please help
Use voodoo lag fix
same thing happens to me after flashing JPK..
Sent from my GT-I9000 using Tapatalk
Its your internal built in 2gb phone memory which doesnt have enough space.
OCLF requires 1.2gb of space on it to work.
You can do what I did which was to titanium backup everything, reset to factory (frees up your phone memory), do OCLF/voodoo and then restore your backup.
Voodoo works better than OCLF but there's no permanent way of uninstalling it other than reflashing it. Got sick of waiting for Froyo and did it anyway.
KaliKot said:
Its your internal built in 2gb phone memory which doesnt have enough space.
OCLF requires 1.2gb of space on it to work.
You can do what I did which was to titanium backup everything, reset to factory (frees up your phone memory), do OCLF/voodoo and then restore your backup.
Voodoo works better than OCLF but there's no permanent way of uninstalling it other than reflashing it. Got sick of waiting for Froyo and did it anyway.
Click to expand...
Click to collapse
So in order to do Voodoo i HAVE to reset factory ?
I don't have ODIN do I have to reflash ?
jaju123 said:
Use voodoo lag fix
Click to expand...
Click to collapse
I don't have or know how to use ODIN yet -- im still kinda new
Also, I don't have the 3 button recover/download mode -- (i can't get KIES to upgrade my firmware for the life of me) -- so flashing/reflashing isn't the best option for me
I was hoping for like an App like Ryan's was out there
I guess not. So there's only Ryan's and Voodoo ?
Funkadelick said:
So in order to do Voodoo i HAVE to reset factory ?
I don't have ODIN do I have to reflash ?
Click to expand...
Click to collapse
You dont have to reflash. You need to have 3 button recovery mode though and it will apply the lagfix on boot.
You'll only have to reflash if you want to completely remove voodoo from your phone instead of just disabling it.
A word of warning though. I had the same encounter earlier when OCLF couldnt lagfix my phone because of the disk space. I did voodoo and it worked but then my phone only had like 20mb left.
Its best to reset to factory, apply either lagfix and then restore your apps with Titanium Backup
I had the same issue on JPK initially because OCLF 2.1.0 wasnt able to write to the system folder. It had prepared the files to move but failed at that point.
I assume yours is the same.
I did this to fix it:
open terminal emulator on phone and type:
su
busybox mount -o remount,rw /system
I manually deleted the file "linux.ex2" in folder /data/ext2 to free up the space...
After that rerun the lag fix, works fine
And you couldnt post this problem in one click lag fix topic why? Just wondering what compels everyone to make a dump out of this forum.
This is ridiculous...
You guys really need to calm down with this "new topic" button"
Funkadelick,
This thread has nothing to do with development and does not belong in that section. This topic has also been covered in other threads as mentioned above, and therefore really should not have been posted in the first place.
Before posting any more threads, go read the "please read before posting" thread at the top of the forum section as all of these subjects are addressed there along with other important ones as well.
Thread closed.
Guys, need some help here
I'm generally ok at fixing these sorts of problems but this one has got me well and truly stumped.
Been trying without much luck to flash a working fw onto i9000 since updating to rom with voodoo and forgetting to disable lage fix before flashing non voodoo rom. Even flashing back with voodoo rom doesnt help.
I think I've finally managed to ascertain the root cause of the issue seems to be that either the internal sd card is somehow write protected or the current journalling on the ext4 partition is undoing and changes to that partition (where does journal reside?). I seem to be in a viscious circle as well. I cant mkfs a new ext2 partition as it complains that it wasnt unmounted cleanly, If I ignore I get a segmentation fault. If I e2fsck the partition it complains it cant write to the superblock, If I use alternate superblock it complains there is data in the journal, trys to replay the journal and complains it cant write the superblock. If I tunefs to disable the journal it complains that the needs_recovery flag is set so need to e2fsck the filesystem first :-S.
I've flashed kernel that has recovery option to disable lagfix. If I choose this and reboot it just sits at Galaxy S boot screen indefinite (over an hour waited). If I mount USB using same recovery mode, I can see the files in the partition, I can (through windows) delete the files so folder shows no files however disk still shows a percentage used. If I eject and remount all the files are back. I have formatted the partition as fat32 and re-labeled the drive. Format completes succesfully (done this both using cmd line and right click format). on eject and remount, label change has remained but files are back again. Partition still shows up as ext4 when looking via adb shell.
Have tried to use parted, but despite all parted functions giving success indicator, no changes are ever made.
I'm now at a loss on how to proceed?
Anyone any ideas on what next steps could yield any further results?
I had a similar issue... what solved it was to flash Darky's ressurection rom. Had to flash it 3 times in a row.. Flashed with Odin 1.7.
Hope it helps, i know how frustrating it is.
Sent from my GT-I9000 using Tapatalk
I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
EDIT: Nope tried it 4 times, same result, boots to Galaxy S screen, I get the voice prompt saying its coverting system, will take approx 2 mins, then another voice prompt about restore, then it sits there indefinetly (waited about 20 mins each time). Whilst its in this state adb devices shows device in recovery, and I can get an adb shell, however there seems to be no commands accesible, cd, ls, mount etc
nivenj said:
I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
Click to expand...
Click to collapse
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol
If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.
robbiev80 said:
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol
Click to expand...
Click to collapse
Thanks for the suggestion but this wont work, as I said above, the root of my problem is that the internal SD card wont keep any changes I make to it. Once I upload the zip file and the phone reboots into download mode in order to flash with Odin, the files I would have put on the internal SD card will no longer be there. It seems to me that the FS cant set the recovery_flag to clean and therefore keeps replaying the journal and overwriting any changes on reboot.
I sort of proved this earlier, by managing to flash JP4 with speedmod kernel. This allows the phone to boot, but it has major force close issues. I can take a photo, see it in images, I can even mount it via USB and see it on my laptop. When I reboot, the photo is gone and anything I've deleted is back again.
Fundamentally I need someone who maybe has some experience fixing the filesystem, I cant see any Roms working until this manages to get resolved
thecrucible said:
If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.
Click to expand...
Click to collapse
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.
got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)
azuresystem said:
got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)
Click to expand...
Click to collapse
Yep tried all that, tried formating via recovery mode, says successful, but all data still exists on reboot. Have tried formating using windows, via command line, via adb shell, they all say they are succesfull but on reboot, same problem exists and all data is still there :-S
nivenj said:
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.
Click to expand...
Click to collapse
I am sorry, not sure where to go from there. Keep Googling and maybe you'll come across something helpful.
Sent from my Galaxy S using Tapatalk
Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.
jm_928 said:
Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.
Click to expand...
Click to collapse
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..
fooman123 said:
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..
Click to expand...
Click to collapse
Thanks fooman123. Can you tell me where I can find the void.fstab file?
jm_928 said:
Thanks fooman123. Can you tell me where I can find the void.fstab file?
Click to expand...
Click to collapse
see this tread:
http://forum.xda-developers.com/showthread.php?t=1088474&page=14
use the correct void.fstab for your phone (i9000 and i9003 are different)
backup the original and compare the new and old void.fstab file..
Data wipe error, Can't mount /dev/block/mmcblk0p1, or Vibrant screen boot loop even after flashing stock odin JFD phone will not boot. Phone will only boot Eugenes JK2 but internal and external storage will still list as corrupted and Lists 0.00 MB in storage.
Internal storage has been destroyed, I’ve been able to fix a phone using this technique to be mostly working. The external SD card will always have to be in the phone for this to work.
1. Partitioning the MicroSD Card
Get an 8gb(or larger) micro sd card. Class 10 would be better here. Put it into a Card Reader, then run Gparted.
Gparted (usb method is easiest) - http://gparted.sourceforge.net/liveusb.php
Using Gparted, delete everything else and create 2 partitions and :
6000mb FAT32 as PRIMARY
1607mb(remainder) Reiser as PRIMARY
2. Flash to Stock
Open up Odin flash stock JFD with pit file and repartition checked.
After phone boots completely, power off.
3. Flashing CM9
Take MicroSD out of phone an put it in pc, then copy update.zip, GAPPS, Cyanogenmod Rom all to the FAT32 partition that we created earlier. In Windows it should show up where all of your drives are listed in.
update.zip (https://www.dropbox.com/s/ju5eg5ernxcaqpt/update.zip),
GAPPS (www.goo-inside.me/gapps/gapps-ics-20120317-signed.zip)
CyanogenMod Rom Zip(http://download.cyanogenmod.com/get...e-cm-9-20120520-NIGHTLY-vibrantmtd-signed.zip)
Enter recovery mode with volume buttons and power.
Reinstall packages twice.
Install zip from sd card select update-cm-9-20120520-nightly-vibrantmtd-signed.zip phone will boot loop on vibrant screen so take out the battery then enter recovery a second time installing the cm9 update again.
Then flash Gapps zip the same way.
When phone boots up camera, and gallery will not work until the next step.
4. Edit Vold.Stab file
Downlad ES File Explorer from play store.
Hit Menu button, settings, Check box for Root Explorer, Check box for mount file system, check box for Up to Root
Press Up once, you should now be at "/"
Open system directory, open etc directory, scroll to bottom and select Vol.fstab, select Text, Select ES Note Editor, update text to the following:
#internal sdcard dev_mount emmc /mnt/sdcard 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
#external sdcard dev_mount sdcard /mnt/emmc auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
After edits, click back and click yes to save changes. Exit out of es file explorer and restart phone. Post results:
Should work with any version of CM9, newer nightlies would obviously be preferred. Will make more detailed guide soon.
Credit to these guys for providing the solution -
http://www.youtube.com/watch?v=zdMhYYdMB08
http://forum.xda-developers.com/showthread.php?t=1447303
...and to think that I've "lost" a Vibrant about a year ago because such tecniques had not developed yet (back then we had no CM and the modding scene was all about samsung roms).
If that works, "thanks" on behalf of all those which are in the position that I was in. If only I still had the phone, I would had probably made it working one way or another
Yea luckily for me the phone's internal died about 3 days ago.
Hmm... oddly enough this fixed the internal storage.
This time i made two partitions on the microsd, fat32(6gb) and ext4 (1.6gb)
Flashed to stock through odin. Flashed Overstock through odin(http://cmw.22aaf3.com/aries/sgh-t959/root/cmenard-t959-cwm.tar)
Linda started talking about converting data parition.
After a while it sounded like it stopped converting so i popped out the battery. Took out the micro sd card and oddly enough recovery was booting normally without the card. Flashed to stock again, this time without the micro sd card in, phone booted up, all my old pictures showed up and everything was working perfect. Glad I found this fix, and I hope it works for others.
For reference sake overstock is Cmenard's kernel with ClockworkMod Recovery and voodoo lagfix
ferhanmm said:
Hmm... oddly enough the internal started working again.
Click to expand...
Click to collapse
Good news about this. You are back full and completely. Can you please go to this thread and read the OP and post your findings in it?
The error came up from a phone that was boot looping that was running stock kb5 with the "stock + voodoo kb5" kernel.
I tried flashing stock jfd then ics in attempts to fix the unmountable internal SD data. After that I did receive the encryption bug but only with the initial fix that I applied. But after the second fix I applied the internal was surprisingly brought back to life so I haven't had to deal with the encryption issues yet and I hope never again lol.
Regardless, I'll run those adb commands for you and post them when I see her again. Which should be soon.
ferhanmm said:
Hmm... oddly enough this fixed the internal storage.
This time i made two partitions on the microsd, fat32(6gb) and ext4 (1.6gb)
Flashed to stock through odin. Flashed Overstock through odin(http://cmw.22aaf3.com/aries/sgh-t959/root/cmenard-t959-cwm.tar)
Linda started talking about converting data parition.
After a while it sounded like it stopped converting so i popped out the battery. Took out the micro sd card and oddly enough recovery was booting normally without the card. Flashed to stock again, this time without the micro sd card in, phone booted up, all my old pictures showed up and everything was working perfect. Glad I found this fix, and I hope it works for others.
For reference sake overstock is Cmenard's kernel with ClockworkMod Recovery and voodoo lagfix
Click to expand...
Click to collapse
how did you get this to work. i have followed every step. i did get the encryption error after the first step, but this second step must have been a fluke. i havent even heard lindas voice. what am i missing?
i already have stock jfd, i also have eugenes. i have stock pit. and the sd is formatted as you have it. but still no dice for me.
McBang2023 said:
how did you get this to work. i have followed every step. i did get the encryption error after the first step, but this second step must have been a fluke. i havent even heard lindas voice. what am i missing?
i already have stock jfd, i also have eugenes. i have stock pit. and the sd is formatted as you have it. but still no dice for me.
Click to expand...
Click to collapse
After following my typed up steps you shouldnt receive the encryption error, mine didnt come back after I made edits to the vold.stab file.
The second step may have been a fluke. What I did was.
1. Create two partitions in gparted, fat32(6.0gb) & ext4(1.3gb)
2. Flash to stock JFD.
3. Flash Overstock through odin
4. If linda starts talking after the overstock flash reboot then it worked, if not then it was a fluke and you would have proved that with your test.
please let me know how it goes, or if you want help pm me and we can gchat
ferhanmm said:
After following my typed up steps you shouldnt receive the encryption error, mine didnt come back after I made edits to the vold.stab file.
The second step may have been a fluke. What I did was.
1. Create two partitions in gparted, fat32(6.0gb) & ext4(1.3gb)
2. Flash to stock JFD.
3. Flash Overstock through odin
4. If linda starts talking after the overstock flash reboot then it worked, if not then it was a fluke and you would have proved that with your test.
please let me know how it goes, or if you want help pm me and we can gchat
Click to expand...
Click to collapse
i tried it exactly how you put it. it works fine (the ics fix) but the fix for internal sd card, must have been a fluke. i never even hear linda voice. so you must be extremely lucky.
McBang2023 said:
i tried it exactly how you put it. it works fine (the ics fix) but the fix for internal sd card, must have been a fluke. i never even hear linda voice. so you must be extremely lucky.
Click to expand...
Click to collapse
Hmm thats odd, well i hope after a few days yours starts to work also. And at least your phone is usable with this.
ferhanmm said:
Hmm thats odd, well i hope after a few days yours starts to work also. And at least your phone is usable with this.
Click to expand...
Click to collapse
absolutely. and thanks again
Bump for interest of knowing if anyone else recovered internal memory after doing these steps
So I'm pretty sure I've seen this error. I see it after I odin back to stock from ics...while wiping in recovery. However my internal sd is fine, everything on froyo works. Does this mean my internal is going?
Is there something close to this error I might be mistaking it for? I don't want to go a find out and mess anything up, but I remember seeing the dev/block error...
just not 100% sure it's ---> mmcblk0p1
accordex said:
So I'm pretty sure I've seen this error. I see it after I odin back to stock from ics...while wiping in recovery. However my internal sd is fine, everything on froyo works. Does this mean my internal is going?
Is there something close to this error I might be mistaking it for? I don't want to go a find out and mess anything up, but I remember seeing the dev/block error...
just not 100% sure it's ---> mmcblk0p1
Click to expand...
Click to collapse
If you can access your internal sd after flashing stock jfd, then yes your phones storage is fine.
If you flashed eugenes jk2, check storage if it lists as unavailable then yes its messed up.
i flashed eugenes and it says unavail. but when i flash jfd, my phone never actually boots. its goes to vibrant screen and phone turns off.
McBang2023 said:
i flashed eugenes and it says unavail. but when i flash jfd, my phone never actually boots. its goes to vibrant screen and phone turns off.
Click to expand...
Click to collapse
Can you try flashing my KB5 odin image I make for Moped_Ryder - LINK
If it loads for you... you can try this code to re-format you SDCard *2767*3855#
it's a Full EEPROM Factory Reset with SDCard format.... this WILL delete anything you had on your int SDCard... I use it to get a super clean install to make my Odin images.
fishman0919 said:
Can you try flashing my KB5 odin image I make for Moped_Ryder - LINK
If it loads for you... you can try this code to re-format you SDCard *2767*3855#
it's a Full EEPROM Factory Reset with SDCard format.... this WILL delete anything you had on your int SDCard... I use it to get a super clean install to make my Odin images.
Click to expand...
Click to collapse
i would be willing to try it....but the link is broken. so no valid download.
EDIT: i found a workaround. downloading and flashing now. i will post results later.
EDIT 2: after flashing, the phone does similar to if i flashed stock jfd. the only difference is it will restart after showing the vibrant splash scfeen back to the splash screen. on stock, it completely shuts down.
anybody ever try something like this with samsung tab sph-100..?
or think i could try this? what would i need to change?
I received this tab from someone over ebay and have never once been able to get past samsung boot screen.
I have the same errors in recovery mode, have tried a lot in odin but i came to believe from other xda members that there must be some internal memory / nand chip damage.
I just got an sd card in hopes i could try something with sd card.
Is this what i'm looking for?
mind, I've never worked with android before this.. noob status still.
sender said he never had any issues with it before sending, hoping to take his word for it, i think i can return it if nothing ends up working, but he's caught in hurricane at the moment, so i am willing to work on it a few more days.
wonder if somehow magnets thru shipping could have done something?
I doubt magnets messed anything up. My suggestion is go to the section here in xda for your device and ask your question there. I would also find out if the previous owner had a custom ROM?, if so which ROM. Is it rooted and does it have a custom recovery?
All will be important info to find a fix.
Sent from my SGH-T959 using xda premium
Basically what I need is to use this mod to boot my experimental builds on the external sd w/t wiping my main ROM (which would be installed to my phone). Is that possible?
So that whatever happens I could always boot back to stock (what I will have installed in my phone), with some minor tweaking through adb shell of course. It sounds doable, ain't it?
I'm on latest CM9 with Semaphore 1.2.4, but this latest update used up a lot of space in /system partition which only left me 2MB spaces. I need extra spaces for system app and new bootanimation, how?
You cant change the system partition size however to get the space in it try moving your app to sdcard.
-----Sent using RemICS-i9000-----
Even I need help with it..
Sent from my GT-I9000 using Tapatalk 2
erpurohit said:
You cant change the system partition size however to get the space in it try moving your app to sdcard.
Click to expand...
Click to collapse
How sure are you on that? From what I understand PIT files in ODIN can change partition layout. If one can change partition layout, one should be able to increase /system as well.
That said, I find Android very confusing. Some examples:
Onboard flash is not a SD card. A SD card is something you can just pull out of the device. Yet android refers to the onboard flash - or well, more accurately a specific partition on the onboard flash - as SD card.
CWM backup is supposed to do a *FULL* backup. Yet it does not include my pictures. No matter what format/wipe options I choose in CWM, the pictures don't go away... I have a whole different concept off a full wipe / factory reset / format SD than that.
It seems several tools format the wrong thing.
App data directories seem to move all over the place. I usually make nandroid backups and I have issues restoring my app *data* every time I use another ROM.
All that said, I'm a big time linux user. I'm extremely familiar with system maintenance on computers. However Android is new to me. All the confusing on naming etc. however is a HUGE !#@%!!#% obstacle.
But why explain things clearly or use terms what they're for. Much easier to confuse people right? At least someone can make money of it then.
Get slimbean 2.1
It has 1.9 gb of /system!!
Sent from my Rolls-Royce.
jay_ingale said:
Get slimbean 2.1
It has 1.9 gb of /system!!
Sent from my Rolls-Royce.
Click to expand...
Click to collapse
All new version of jelly bean will be of this size only....
Delete /system/media/videos and convert cyanogenmod wallapapers to user apps. Saves ~15 mb
Sent from my GT-I9000 using xda premium
Sorry to bump such old thread.
I was offered a I9000 that I would like to use as second phone.
I flashed I9000XXJVU_I9000OXAJVU_OXA through odin, and then root (cf-root) and MackayRom 1.7 .
As it says in the rom thread, I have a space problem. Is there any chance better than this one?
Any possibility of repartitioning the internal storage?
Here is my partition scheme:
Ok, first time posting here, so pardon me for any stupidity. I need help, been using unofficial slimkat rom on s3 mini, was trying an app that uses part of your external SD as RAM, turns out my Kernel doesnt have the swap feature, tried to install another kernel, the phone got stuck in a boot loop shows this "unable to mount /modemfs" in recovery whenever I try to do anything, also there was unable to mount sdcard and unable to mount data, but those got fixed by too many formats and wipes and flashing some PIT and Modem files though Odin, have no idea what to do, can someone help please ?
kfatah22 said:
Ok, first time posting here, so pardon me for any stupidity. I need help, been using unofficial slimkat rom on s3 mini, was trying an app that uses part of your external SD as RAM, turns out my Kernel doesnt have the swap feature, tried to install another kernel, the phone got stuck in a boot loop shows this "unable to mount /modemfs" in recovery whenever I try to do anything, also there was unable to mount sdcard and unable to mount data, but those got fixed by too many formats and wipes and flashing some PIT and Modem files though Odin, have no idea what to do, can someone help please ?
Click to expand...
Click to collapse
Also new to android, but I know linux well
modemfs seems like another partition on the internal storage
since you reflashed this it might be in the wrong format / filesystem
my phone reports this entry in the fstab (mine is ext4 format)
/dev/block/mmcblk0p12 /modemfs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check
you need to flash one in the correct filesystem, maybe try one of these from http://forum.xda-developers.com/showthread.php?t=2526831 not sure if these are odin compatible
if all else fails you can download the stock rom from http://www.sammobile.com/firmwares/
thanks for your help
thanks for replying, and sorry for the late answer.
I will try the link you sent me, but there are a couple of stuff i failed to mention last time, before showing me that it used to show failed to mount /data and /sdcard .. I think the internal sdcard is damaged because I did flash the stock rom, the phone boots without the ability to install any apps, no network, yellow text is displayed on the screen saying stuff like PDA and Csc .. etc, inside settings baseband is XXXXXX. also when I connect the phone to my windows ... the internal is empty with incorrect size and you cant create or copy folders in it and was not able to formate it in windows or linux .. even recovery was not able to formate it.
update: I did try one of the files, but it is the same unfortunately .. I think its the sdcard issue .. but that is ofcourse my humble opinion. any other solutions ??
kfatah22 said:
thanks for replying, and sorry for the late answer.
I will try the link you sent me, but there are a couple of stuff i failed to mention last time, before showing me that it used to show failed to mount /data and /sdcard .. I think the internal sdcard is damaged because I did flash the stock rom, the phone boots without the ability to install any apps, no network, yellow text is displayed on the screen saying stuff like PDA and Csc .. etc, inside settings baseband is XXXXXX. also when I connect the phone to my windows ... the internal is empty with incorrect size and you cant create or copy folders in it and was not able to formate it in windows or linux .. even recovery was not able to formate it.
update: I did try one of the files, but it is the same unfortunately .. I think its the sdcard issue .. but that is ofcourse my humble opinion. any other solutions ??
Click to expand...
Click to collapse
I seriously doubt that the internal memory itself is damaged. If you were able to flash anything then it still works.
Or are you referring to the removable SD card? Via USB connection none of the storage size is also not reported correctly on my phone.
What recovery do you have installed?
1. Firstly you should get the phone working again and work off WIFI.
I am not sure if the stock rom installer only copies files or if it dd the whole image (incl filesystem format).
Your IMEI is stored on a filesystem and mounted on /efs - You should not remove / format this filesystem !!! Do not even touch it!
When you installed the custom rom intially you probably formatted in the f2fs file system? I would install the custom rom again, and in the install menu format "data" and "swap" to ext4 filesystem just to be sure.
Flash back to stock make sure about model and baseband
The phone should boot up and at least be able to install apps via WIFI.
I installed the app "ssh/sftp server" and then login via ssh to browse and inspect the phone.
2. Step two is fixing the baseband (not having any network signal)
2.1 What is your original baseband?
2.2 What phone variant do you have 8190/8190L/8190N? If you flash a different one to your phone it will not work.
I mean the internal sdcard, cause previously it showed unable to mount /sdcard, right now I have the stock rom, each time the phone reboots, it resets itself again, all my changes are gone, yes I can turn on wifi but no apps are to be installed, using pc can't copy anything to the internal storage (I can only copy on my external card which I use to flash) right now I have TWRP and I tried CWM as well. as for installing a custom ROM, it didn't work, the phone doesnt get past the s3 mini logo, only the stock rom passes through, my phone is 8190 and I have no clue what is the original baseband um really sorry I am a total noob. I will try again to flash the customer rom using Odin and will get back to you.
thanks so much for going through the trouble.
kfatah22 said:
I mean the internal sdcard, cause previously it showed unable to mount /sdcard, right now I have the stock rom, each time the phone reboots, it resets itself again, all my changes are gone, yes I can turn on wifi but no apps are to be installed, using pc can't copy anything to the internal storage (I can only copy on my external card which I use to flash) right now I have TWRP and I tried CWM as well. as for installing a custom ROM, it didn't work, the phone doesnt get past the s3 mini logo, only the stock rom passes through, my phone is 8190 and I have no clue what is the original baseband um really sorry I am a total noob. I will try again to flash the customer rom using Odin and will get back to you.
thanks so much for going through the trouble.
Click to expand...
Click to collapse
Is
The baseband is linked to your country, it specifies the frequencies that you are allowed to use to communicate with the cellphone network. So If I know what country you are from we might be able to locate the correct Stock ROM on SanMobile. You might be flashing a wrong stock rom to start off with.
What country do you live in and what network operator?
Are you using ext4 filesystem for data and swap?
I personally used twrp 2.8.0. I think this is the way to go.
Do you know Linux?