Database Develop

Stuck on LG screen when using EXT4 ROMs

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.

[Q] ext4 problems when changing ROM's

So I like to switch ROM's quite frequently, the only problem is that I seem to have to format my sdcard and set up the partitions each time I switch. I feel like nandroid either doesn't restore data to the ext4 properly or messes up the partition when I do a factory reset, since it formats the ext4 partition. Whatever the case, I am unable to move apps to the ext4 after a flash.
Whenever I want to switch to another ROM I have to backup my sdcard to my computer, format the card using diskpart, create the partition again in recovery mode, restore sdcard contents, and then finally flash the ROM I want. This can take forever and makes trying new ROM's out a huge hassle.
If I don't restore a nandroid and flash a ROM from scratch, I'll install s2e, reboot, and navigate to /sd-ext using root explorer and there will be no files.
I mainly use s2e with CM7, but I have tried a2sd with similar results. As far as I know though, they both use the same technique to move apps so it shouldn't matter.
Am I doing something wrong? I use nandroid and everything, but once I do a factory reset it refuses to restore the ext4 backup, and I get an error relating to space limitations.
Thanks a lot.

I've changed ROMs a few times, and everytime I've done so, the ext4 partition has remained fine. Although, it is seriously recommended that you flash the latest darktremor a2sd script as the incorporated ones don't seem to work well.
Flash darktremors, then enter the command line emulator on your phone and type:
su
a2sd reinstall (your phone will reboot)
su
a2sd cachesd (your phone will reboot)
su
a2sd zipalign
This should always be done after a ROM switch.

Alright, I will try that out.
Just wondering, will this restore all the apps I have on the ext4 partition? For example, if I flash MIUI for the first time, then commands the commands you gave me, will all my apps be restored? I assume no since clockworkmod wipes the ext4 partition when doing a factory reset.

The S2E and DarkTremor's a2sd apps actually use different ways of utilizing the ext partition, so the two are incompatible (although, S2E includes a way to convert from DT's to its own).
And as long as you didn't wipe the ext partition (which a Factory Reset does), using those commands should restore your apps.
But with what you are doing, it may be easier to use Titanium Backup to restore your apps back rather than nandroid. This will allow you to keep all your app settings and saved info as well. Just be careful to not back up system data. Restoring those on the same ROM can cause issues, and it would probably cause a lot more if it is between two different ROMs.

Switch your Ext 4 Partition to Ext 3 and you'll notice a lot more stability when switching roms.
Some roms don't have the correct Apps2SD or Kernel installed to support ext 4 but most, if not all, support ext 3.
I recommend using AmonRa Recovery as CWM always corrupts the ext partitions.
Re-partition your SD-Card and start again.
If This Helped please Hit THANKS

[Q] STUCK A

got my nexus one week back.its rooted .it has rapassion recovery 2.2.1 and HBOOT v0.35.0017.i wated to try my hands on flashing.so i downloaded [ROM][2.1+3.0/2.3.3] Rev0lutioN v2.8 followed the steps wiped data,done partition swap size 0 and ext 1 1024 mb ,selct ext2 ext2,then ext3 ext 4.then flashed the rom from sd card .but on rebooting it is stuck @ NEXUS ONE X IMAGE .pls show me some way to flash sucessfully i can get back to that fastboot,recovery etc page by volume down and power button

i would dl this to sdcard and flash a couple times thru recovery before flashing rom. wipe dalvik and battery/rotation settings too
http://dl.dropbox.com/u/28338566/Extreme-wipe.zip
not wiping system can cause issues
assume you met ALL other rom requirements
also i don't reformat sdcard while in phone--use sdformatter
the first thing i do when i get stuck is pull battery and reboot--not sure if you tried that

thanks..i will try that...does it matter well i was trying to flash nand version may be that caused problem..one more help can u pls guide me to how to do 1gb ext4 partiton..or sugget me some stable sense version for nexus i can flash easily

if you are new as indicated by one week ownership, i would start out with cm7 stable roms from android development section
use the system wipe zip i provided
sounds like your card is already partitioned
best thing to do is read up in wiki and as much of rom thread you are going to flash, the op page has good info and i usually read last few dozen pages
if you flashed nand version, assume you flashed blackrose hboot and repartitioned
hboot to recommended sizes per op page link, if you did you will have to go back to stock hboot to flash cm7 or try sd version of rev rom
i had surgery and not feeling well tonite, let someone else come along to add to my posts
ken

feeling a bit better, here is quick answer
backup sdcard
i use sdformatter to format outside phone--full erase and size adj on
http://dl.dropbox.com/u/28338566/SDFormatter 2.0.mht
this ensures card is fully formatted--phone just does quicky
then put card back in phone and use amon ra to repartition card to 1gb ext 4 0 swap
seems you did those steps already
then copy sdcard data back to phone

create ext4 for use with a2sd

hi,
i'm usin ra passion 2.2.1 and wan't to use a2sd from ics 4.0.3 evervolv. how can i create a part ext4?

Google:
"a2sd partition sd card".
Enjoy.

Try 4EXT recovery www.4ext.net
I think its the easiest way to create partition.
Or else you can do it in pc via partition managers(i use minitool partition wizard)
You can google it and also can search in youtube for video tutorials.
Sent from my Nexus One using Tapatalk

thanks for your help, i've done it in recovery.
one question is left:
what happen if i format the partioned sd-card under windows and do a full wipe in preparation for installing a new rom. i've read sd-ext even survive a full wipe? what does that mean? stays the partition untouched when i format the sd-card with windows? and what about the apps in the partition? are they still there even after a full wipe and can i use them after flashing a new rom out of the box?

Glad u succeeded in partitioning
Now if you format the fat32 partition in windows using those partition tools doesnt affect ur ext. Ext stays untouched but all the data on fat32 will be wiped(so backup first to pc)
If u want to merge there is an option called merge for that.
There is an free windows software called sdformatter, that formats the entire sdcard(fat32+ext)
Hope i helped a bit :thumbup:
Sent from my Nexus One using Tapatalk

ok. i wan't to format it with the windows internal function via right click. is it the same and the ext4 stays untouched?

Full wipe in recovery wipes SD-EXT too.

heinz gruber said:
ok. i wan't to format it with the windows internal function via right click. is it the same and the ext4 stays untouched?
Click to expand...
Click to collapse
i do beleive that it should be untouched, cos normally windows cannot see the ext partition and hence only fat32 will be formatted
Sent from my Nexus One using Tapatalk

ok. when ext4 stay untouched and i flash a new rom the apps are still in the launcher after flashing?

Jack_R1 said:
Full wipe in recovery wipes SD-EXT too.
Click to expand...
Click to collapse
when i flash a new rom i use the format.zip form the xda user temasek which wipes system, boot, data and cache. so is sd-ext untouched when i use this file?

You insist on not listening and/or not understanding.
When you select "wipe data/factory reset" in custom recovery, EXT partition IS WIPED COMPLETELY. It doesn't stay.
I believe the same happens when using temasek's script, never bothered using it, so I can't say with 100% certainty.
If you don't wipe your phone and install a new ROM - be prepared for crashes of anything to everything, unless you install a ROM which is 100% compatible with what you have already - the next generation of the same ROM, usually.
If you're using A2SD and don't wipe EXT partition - you'll have crashes as soon as you boot, since system apps' data will be there (and wrong).
To keep your apps and their data, use one of the backup apps available in the Market, like Titanium Backup.

as Jack_R1 explained its always better to wipe everything(system,cache,dalvik n sdext) to be on safer side to avoid crashes n FCs.
Sent from my Nexus One using Tapatalk

Temasek's Extreme Wipe does Data/System/Boot partitions but don't remember seeing ext in the list
However, as alluded too, I would format all outside phone with sdformatter or I think gparted, although never used that one
I thought I read a long time ago Windows formatter not recommended and do a full wipe not partial with whatever you use
Back up sdcard first
also, I believe you can use the Alignment Cool zip to get ext 4 from 3 on Amon and not lose anything--still backup
you do know MeDroid uses Ia2sd and different from a2sd on implementation

You don't need to wipe the regular FAT partition on SD card between flashes, because there's nothing there that loads automatically. And "wipe data/factory reset" option in recovery also wipes /sdcard/.android_secure.

hey guys, thanks for your answers i will keep them in mind.
edit:
one more question:
if i uses temaseks script and the sd-ext is untouched and i flash a newer version of my rom, are the apps then still there after flashing and booting the updated system? or is there another step i've to do?

No, the apps aren't there anymore - or to be correct, the apps are there, their data is gone (because the app data doesn't reside on EXT partition, unless you use specific mounting methods).
When you flash an updated version of your ROM, just don't wipe anything at all unless the instructions specifically mention having to wipe before installing that version. That means - don't execute temasek's script at all.

[Q] Apps, DalvikCache AND app data to SD on Stock ROM?

On the stock GB ROM, Link2SD requires a FAT32 partition to move the App and DalvikCache to the SD.
EDIT: Actually requires FAT32 OR EXT2 for stock...
Titanium backup requires an ext2/3/4 partition to use the Data2SD feature.
Is it possible to do both of these on a stock rom? Or use some other method to get the App, DalvikCache and app data to the SD without flashing another ROM?
I will be doing this for 3 of my family's phones and would much prefer to not have to flash ROMS and them have to put in extra effort afterwards.
I promise I've searched so apologies if this has been answered elsewhere, the closest I could find was http://forum.xda-developers.com/showthread.php?t=1605006 which didn't answer the question...
Thanks in advance!
Tim

I have created two partitions, one FAT32 and one EXT2 using MiniTool Partition Wizard
Link2SD is correctly setup and working.
Titanium Backup has this to say:
The supported mount points for the ext2/3/4 partition are:
/system/sd/ (“classic” sd-ext)
/sd-ext/ (“Cyanogen” sd-ext)
/data/sd/ (“MIUI” sd-ext)
However none of these mount points are present (it appears to mount under /data/sdext2/) so I'm unable to use the Data2SD functionality as yet.
So the question now becomes, can I create multiple mount points for a single EXT2 partition on a Stock ROM (ideally easily!).

Install a custom kernel with init.d support.
Cf-root is the most common since it's based on stock, and preserves baseband.
After that, there's many choices:
-link2sd as you've beeb using
-cronmod or amarullz scripts (int2ext+) which mount sd partition as extention to internal memory (every app on internal gets installed to the partition).
-s2e has the option to also move data to the partition.
Keep in mind that having data on the partition will lower performance and smoothness as compared to having data on internal.

dxppxd said:
Install a custom kernel with init.d support.
...
...
Keep in mind that having data on the partition will lower performance and smoothness as compared to having data on internal.
Click to expand...
Click to collapse
Thanks for the advice.
I have a class 10 card that I was hoping would help mitigate the problem, am I just being naive?
I was hoping I'd be able to avoid a custom Kernel (haven't researched them enough yet)
I will try and find an S5830 Stock + init.d kernel tomorrow and see how that goes, I'm still planning on Titanium Backup to do the Data2SD.
Does this init.d script mount the partition somewhere that Titanium Backup can get hold of it then?

KingTimus said:
Does this init.d script mount the partition somewhere that Titanium Backup can get hold of it then?
Click to expand...
Click to collapse
I really can't say about titanium backups' data2sd function since i've never used it before.
The init.d script (i found cronmods' int2ext to be the most convenient) mounts the sd partition as part of /data. When making backups of apps+data titanium backup had 0 problems finding and backing up all apps. The problem might arise if the data2sd function tries to move /data (in which the partition is already mounted) to the partition.
Someone in the forum might know more details. You can always make a nandroid backup and see what happens. Good luk.