I updated my phone to Cognition 2.1.2, and think i bricked it. I was on Cognition 2.1.1, i disabled the lag fix as per the instructions, and then installed cognition 2.1.2 with Rom manager. when my phone rebooted it seemed to work fine. Then i realized that there was no calculator app installed anymore. I went into the settings screen, but when i clicked on any of the options it would highlight, but not do anything. I rebooted, but i got stuck on an ATT boot loop.
I then pulled the battery, got into the download mode with the button combo, and did an odin oneclick back to stock. however, when it rebooted it went into the stock recovery console and gave an error message "cant mount \dev\block\ stl11"
After that i tried updating with odin 3 to JH2. Everything went ok, but when it reboots it still goes to recovery, but this time it gives me a differnet error
Code:
format_vfat_device -> argv[4] : android
format_vfat_device -> argv[5] : /dev/block/mmcblk0p1
run_program: child exited with status 1
E: Can't mount /dev/block/mmcblk0p1
(No such File or Directory)
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
I can boot into download and recovery with the button combos
I can use adb when in recovery , I'm not sure what to do though (I can't mount with shell, nor can i get to su
I can't get to ClockWork Mod Recovery as it was'nt the last update.zip, and when i try to reinstall packages it says
Code:
E:can't mount SDCARD:update.zip
Installation aborted.
I'm pretty sure this has to do with the lag fix. I think that odin can't wipe the ext4 partition even though i disabled the lag fix.
Please help, am i completely bricked? If so should i return to att even though its been rooted? I guess i could say it was from the OTA.
I would suggest making sure that you disable the lagfix by
Code:
adb shell
touch /sdcard/voodoo/disable-lagfix
Reboot, and it will probably say "converting back to rsf blah blah blah" It takes like friggin 10 minutes to disable
Then I would try to replace the update.zip with the clockwork recovery update.zip. I uploaded it here: http://dl.dropbox.com/u/115587/update.zip To do this I would use
Code:
adb push [local path to update.zip] /sdcard/update.zip
In my case since I'm using a mac (I put it in my downloads folder) I did
Code:
adb push ~/Downloads/update.zip /sdcard/update.zip
Then try to go into recovery mode and reinstall packages, hopefully clockwork will come up and you can restore a good version of your phone
Hope it helps
Laundry? Do you have insurance on it?
Sent from my 42 node TI 89 cluster
i dont know a whole lot about adb or even know if this is possible, but is there a way to reformat the internal sd card in adb like there is in the stock settings menu? if you reformat that should get rid of all traces of anything including lagfixes correct?
I am unable to use the touch command because it can't mount the Internal SD. it gives me
Code:
touch not found
even when i touch files that i now were there.
I wonder if i could flash the voodoo kernal back on to it if it would take care of it. is there a .tar of it that can be flashed with odin 3?
Is there a way to see what partitions are on the internal sd, and like di11igaf said, is there a way to reformat with adb?
Also i don't think warranty covers putting it through the laundry and w/ insurance it costs like $125 to replace
Wow this one is a bit of a headscratcher.
Have you tried manually flashing in a voodoo compliant kernel just to see if it will boot? It's not mounting the internalSD, which is bizarre, but I do know that stock kernels can't read EXT4 data- now I don't know why your internalSD might get switched over, and I have very little expectation that this will work, but at this point what's the harm?
I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)
I have flashed a voodoo kernel but it just tries to create the ext4 partition, fails and reboots. The problem is that there is now no /dev/block/mmcblk0p1 or /dev/block/mmcblk0p2. There is still a /dev/block/mmcblk0 but since we both tried to flash stock with Odin we no longer have root to attempt recreating the partitions. We also can't flash anything from recovery since there is no /sdcard.
We need a rooted ROM that is flashable with Odin. The e3 recovery also has an option to reformat the internal sdcard but I've only found it with i9000 ROMS where the captivate power button doesn't work to select it.
Trump211 said:
I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)
Click to expand...
Click to collapse
This may sound crazy, but do you happen to have the update.zip from ROM Manager on the root of your sdcard? From the sounds of it, once you switch back to the voodoo kernel your phone is able to mount your SD again, now it's just encountering errors on your NAND. If you can get into clockwork recovery go in there and have it format your SDCard, once you've done that, try to flash back with Odin one click and see if everything starts working again.
Zilch25 said:
This may sound crazy, but do you happen to have the update.zip from ROM Manager on the root of your sdcard? From the sounds of it, once you switch back to the voodoo kernel your phone is seeing that, now it's just encountering errors on your NAND. If you can get into clockwork recovery go in there and have it format your SDCard, once you've done that, try to flash back with Odin one click and see if everything starts working again.
Click to expand...
Click to collapse
that wont work, I have been messing with this all morning. The op has a corrupted internal SD card. Nothing will fix this because it wont mount. Its just like any other sd card that gets corrupted.
I even went as fas as flashing eugene's froyo that dont brick from the vibrant forums. thats the only 2.2 rom that will partition the internal sd. but a corrupted sd is a whole other ballgame. Just get another phone.
Devin5277 said:
that wont work, I have been messing with this all morning. The op has a corrupted internal SD card. Nothing will fix this because it wont mount. Its just like any other sd card that gets corrupted.
I even went as fas as flashing eugene's froyo that dont brick from the vibrant forums. thats the only 2.2 rom that will partition the internal sd. but a corrupted sd is a whole other ballgame. Just get another phone.
Click to expand...
Click to collapse
You did catch the part where after flashing the voodoo compliant kernel he's no longer getting the error where he can't mount the internalSD, and is instead getting a message about a partition on the NAND not initiating? The theory here is that perhaps SOMEHOW the internalSD has got some EXT4 data on it that the stock kernel can't understand, so it refuses to mount it, the voodoo enabled kernel DOES understand it, and as such will mount it. The objective is to get that internalSD formatted again so that he can switch back to a stock kernel and have it recognized
I'd also like to add that eugene's kernel also doesn't read ext4 =P Noticing a pattern here?
Another thing that might be worth trying... though doubtful. Do an Odin 1 click, yank the battery as soon as it completes before it gets a chance to boot again. Restart Odin and get your phone back into download mode, and flash in the Voodoo kernel, see what errors it spits out on first boot (if any)
Trump211 said:
I thought of manually flashing in a voodoo kernal, but the only ones I can find are update.zip or with clockwork mod methods neither of which i can get to. Is there a voodoo kernal that can be flashed with odin3?
Edit: I just flashed unhelpfuls kernal and i am now getting a different error message
Code:
E:Can't mount /dev/block/stl11
(Invalid argument)
Click to expand...
Click to collapse
Zilch25 said:
You did catch the part where after flashing the voodoo compliant kernel he's no longer getting the error where he can't mount the internalSD, and is instead getting a message about a partition on the NAND not initiating? The theory here is that perhaps SOMEHOW the internalSD has got some EXT4 data on it that the stock kernel can't understand, so it refuses to mount it, the voodoo enabled kernel DOES understand it, and as such will mount it. The objective is to get that internalSD formatted again so that he can switch back to a stock kernel and have it recognized
I'd also like to add that eugene's kernel also doesn't read ext4 =P Noticing a pattern here?
Click to expand...
Click to collapse
No worries bro, was just trying to help. You probably have more exp when It comes to this, I was just letting the OP know what worked for me in the same situation. Seems like the captivate is a little different beast.
for the record I wasnt talking about flashing another kernal. I was talking about flashing a 2.2 rom ( which thru odin) repartitions the internal sd to stock, which will cut out the ext 4 lag fix issue. It did for me anyway.
With the cant mount issues, I think its currupted. ATT gave my friend another phone with next day shipping. they also said that phones are soft bricking like crazy because of the ota update. so I dont think the OP will have much of a issue saying it was the ota update and getting another phone.
Devin5277 said:
No worries bro, was just trying to help. You probably have more exp when It comes to this, I was just letting the OP know what worked for me in the same situation. Seems like the captivate is a little different beast.
for the record I wasnt talking about flashing another kernal. I was talking about flashing a 2.2 rom ( which thru odin) repartitions the internal sd to stock, which will cut out the ext 4 lag fix issue. It did for me anyway.
With the cant mount issues, I think its currupted. ATT gave my friend another phone with next day shipping. they also said that phones are soft bricking like crazy because of the ota update. so I dont think the OP will have much of a issue saying it was the ota update and getting another phone.
Click to expand...
Click to collapse
Sorry I didn't mean to come off harsh My theory here is that SOMEHOW voodoo is writing EXT4 data to the internalSD outside of the NAND area and in some cases it's corrupting it in such a way that the internalSD cannot be read by the stock kernel (since it has no EXT4 support) so in theory if you can get the internalSD mounted again it can be reformatted to allow a stock kernel to return to use... if this is the case, or at least close enough to what's happening it would fully explain why the froyo kernel with repartition couldn't touch the internalSD (It couldnt mount or read it due to the limitations for file systems in a stock kernel)
Looks like the sdcard on mine has had it. I got root and ffdisk and parted still give I/O errors when trying to read or write to /dev/block/mmcblk0.
kakalaky said:
Looks like the sdcard on mine has had it. I got root and ffdisk and parted still give I/O errors when trying to read or write to /dev/block/mmcblk0.
Click to expand...
Click to collapse
Is this after using a Voodoo kernel? And are you attempting to perform the ffdisk and parted commands while using a voodoo kernel, or stock? I'm just trying to gather as much information as possible on this problem, so forgive all the questions
I'm about to try parted with a voodoo compliant kernal (unhelpful's) But for some reason adb isn't finding my phone when its in recovery. Does this have something to do with the unhelpfuls kernal, or should i just uninstall and reinstall the drivers a few more times?
Trump211 said:
I'm about to try parted with a voodoo compliant kernal (unhelpful's) But for some reason adb isn't finding my phone when its in recovery. Does this have something to do with the unhelpfuls kernal, or should i just uninstall and reinstall the drivers a few more times?
Click to expand...
Click to collapse
Nah, make sure you have the phone plugged in when you turn it on and go into recovery. For some reason plugging it in when it's already in recovery doesn't work. At least it doesn't for me...
Ok, i tried that, but its still not connecting. Tried multiple usb ports, and uninstalled/reinstalled drivers. If i put it in download mode it gets recognized instantly.
Trump211 said:
Ok, i tried that, but its still not connecting. Tried multiple usb ports, and uninstalled/reinstalled drivers. If i put it in download mode it gets recognized instantly.
Click to expand...
Click to collapse
Not sure =/ I had it running last night without too much issue, but I did have to juggle it around a bit before it would find the device. You might want to try doing an adb kill-server before you try to connect in case the system still thinks its running
I was just wondering about the folders that the voodoo lagfix actually changes to EXT4? As in my other thread(s), I bricked my phone by installing 2.2.1 over 2.2.1 + lag fix (without uninstalling voodoo), and fixed it by going to JM8 + 512 PIT repartition then back to JPY without repartition.
Basically I know the repartition option in ODIN converts SPECIFIC folders back to RFS within the system partition (the ~2gb section in the internal SD). In this way I'm assuming that Voodoo applies the ext4 file system to these same folders, does it not?
While the phone is working now, I want to positively make sure that there isn't some random unused EXT4 portion in my phone waiting to rear its ugly head with random bricks and bugs. In my mind this could occur because voodoo and ODIN don't format the same folders, and there could be some sort of overlap happening. Is there a valid method to my madness?
I might get on the voodoo IRC later and ask for help there, or if someone could get hold of curio/know the answer themselves it would be even better!
Thanks for any replies!
data
cache
dbdata
Thanks
I'm assuming odin repartitions these sections then (obviously because my phone is working now) + another section , right?
I saw a thread with the folders that ODIN repartitions but can't find it now!
Nevermind, found the thread and ODIN repartitions the /data, /dbdata, /system and /cache files. Same as voodoo except with /system included. Back to stock RFS yay!
Correct Odin repartitions everything or else there wouldn't be much point to it
Hi all,
I dont know if this is hardware related since my LG 2x is a white one which is made in Oct 2011 as LG may change the hardware a little to prevent support in EXT4.
Anyway, here is my problem...
Anytime I flash my 2x with ANY EXT4 ROM or kernel (eg: Topogigi v2.0, Thanatos2X v4.2, NeoBlaze EXT4 kernel etc...) I cannot boot my phone pass the LG logo screen. (This is without the progress bar at the bottom of the LG logo).
The phone is stuck there forever unless I pull the battery and reflash the ROM with backtoext3.zip and an EXT3 ROM. All EXT3 ROM work 100%, like LG's Stock, Modaco GR5, Slick2X, BlazingDragon2.1 and CM7 etc.
So I am wondering if it is my phone that is causing this problem or whether I am missing something along the way.
I would love to try EXT4 ROM thus any help/suggestions would be appreciated. Thanks!
Hello!
1st it isn's your phones hardware. LG isn't preventing anyone from using EXT4 - this is solely in the software implementation.
…and CM7 isn’t a “EXT3” ROM. CM7 supports any ext (2/3/4 doesn’t matter).
The kernel or some messed up installation script is most probably the culprit…
When installing a new ROM you should always:
Format /system and /cache and then wipe dalvik – this way you get a clean system but you don’t lose your user data! Afterwards install ROM and gapps if needed/not includes in rom and then the kernel if needed + scripts.
Good working combo should be topogigi/thanatos and horsepower kernel.
Verify that /cache is reformated, certain version of backtoext3 don't reformat /cache.
CM7 is an ext4 ROM (last time I used it it was...months ago), but perhaps it's just a 'remount as ext4' and not a native fresh ext4 formatting..
So basic things: format all partitions in CWM: /system /cache /data, erase Dalvik. Then to be sure backtoext3.
There are no reason to not be able to use ext4 as it is only a matter of kernel driver and partition format = software and not hardware.
Thanks for the info.
I forgot to mentioned in my 1st post that I always wipe system, cache and dalvik cache before flashing all the ROM I mentioned before.
I checked again and yes, CM7.2 is EXT4, so my title of my post is not correct.
Anyhow, I just tried to flash the Kernel 'ironkrnL32-20111214h1547' over my working CM7.2 ROM; however, the same thing happened. After the flash, the booting will be stuck at the LG logo screen and does not move past that point.
Moreover, I have also tried the Topogigi ROM w/ SP merged (just 1 file) and it did not boot past the LG logo point as well.
I am really out of ideas now.
I had same issue before, what I do is after I flash, I let it load for 10 mins, and of course its stuck on booting, take out the battery and sd card and put back battery only, after that, it loads. I don't know why but it works for my phone so it might work for you.
I installed corn kernel and its running fine and I found out that it is lagfix enabled.........just one doubt ....do I need to disable lagfix before flashing any roms? if so how to disable it ....I can see rfs and ext4 in cwm what are these?
which Corn version are you running?
I run 7.0a and by default, it has no lagfix. don't need it afaik.
rfs and ext4 are different types of linux file systems that are used to store data in partitions on your phone. my phone had froyo os with rfs partitions when I bought it new. It still has rfs partitions with Corn 7.0a GB KK4.
If you are messing around with file partitions in cwm recovery, just remember that any change from rfs to ext4 will completely reformat the partition and you will lose any data on it.
If you flash ICS or JB, you are going to an ext4 file system.
goes without saying: backup everything with cwm and a backup app like titanium bu, then copy all of it to an external sd, computer or cloud. if on sd, remove it before flashing, to be safe.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
laughingT said:
which Corn version are you running?
I run 7.0a and by default, it has no lagfix. don't need it afaik.
rfs and ext4 are different types of linux file systems that are used to store data in partitions on your phone. my phone had froyo os with rfs partitions when I bought it new. It still has rfs partitions with Corn 7.0a GB KK4.
If you are messing around with file partitions in cwm recovery, just remember that any change from rfs to ext4 will completely reformat the partition and you will lose any data on it.
If you flash ICS or JB, you are going to an ext4 file system.
goes without saying: backup everything with cwm and a backup app like titanium bu, then copy all of it to an external sd, computer or cloud. if on sd, remove it before flashing, to be safe.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I'm 7.0 A btw ......thanks for reply it was booting up pretty fastly so I thought it has lagfix enabled .....if it doesn't have lagfix then I can flash ics roms directly without problems rite
The Ext 4 is not enabled by default in the Corn Kernels.
And Yep...flash away.
Sent from my SGH-I897 using xda premium