Related
Here you go guys.
This kernel will allow you to use CM6 w/ ext4.
Basic instructions:
Flash back to a normal DK28 rom,
Follow all steps here:
http://forum.xda-developers.com/showthread.php?t=890494
EXCEPT, flash this kernel at the end, after flashing Cyanogen Mod: http://efragtv.com/android/CM6-DUALFS-v1.1.zip
This also fixes wifi, and su.
NOTE: Everytime you flash CM6 (To update to a new nightly, or whatever reason) YOU HAVE TO REFLASH THE KERNEL!! CM6 installs its own kernel.
iam confused...do u have to flash to stock..then do the ext4 then flash cm6...then the kernel or wat
Just as you said.
UPDATE:
This new version fixes lpm battery charging freeze.
Flash in CWM
http://efragtv.com/android/CM6EXT4-Kernel.zip
This combination absolutely FLYS!!
Consistently score in the 2300 range in quadrant (yeah yeah I know), but the whole phone just feels snappier too.
For some reason my 3g doesn't seem to work, so I won't be keeping it (tired of not receiving mms too, so that's as good of an excuse to try out Quantum as any).
Great work Dameon87! Hopefully the cmsgs team implements this in as standard in the future!
jbowen said:
This combination absolutely FLYS!!
Consistently score in the 2300 range in quadrant (yeah yeah I know), but the whole phone just feels snappier too.
For some reason my 3g doesn't seem to work, so I won't be keeping it (tired of not receiving mms too, so that's as good of an excuse to try out Quantum as any).
Great work Dameon87! Hopefully the cmsgs team implements this in as standard in the future!
Click to expand...
Click to collapse
Hmm.... I wonder what would've stopped 3G from working in the modification...
Was there any reason Samsung used RFS in the first place? Is there no downside in using ext4? I usually use ext3/4 when given the choice on a desktop Linux installation, but just wondering if there's something I'm missing here.
AndrewZorn said:
Was there any reason Samsung used RFS in the first place? Is there no downside in using ext4? I usually use ext3/4 when given the choice on a desktop Linux installation, but just wondering if there's something I'm missing here.
Click to expand...
Click to collapse
1) its their proprietary file system
2) ext4 was not made for flash memory..thus will reduce the lifespan of your NAND memory..don't panic though it'll still last a few years...just not as long as it would with RFS...
Mostly 1...
Just for curosity do you have any links for actual half life of data on flash memory, would be a great resource if you did.
Sent from my SPH-D700 using XDA App
So, I've been running Quantum ROM 2.5 with ext4.
Can we flash this and CM6 without going back to stock DK28 and running the bat file?
In case I don't catch you...
You forgot root in the kernel. So, here I am, super fast ROM, and no root access. Oh, and it took three tries:
1st - Formatted everything, couldn't remount anything
2nd - For some reason, 2.5.1.2 recovery just vanished, couldn't boot, house caught fire. Blah.
3rd - Smooth. Everything seems to be going well. Except root.
k thx bai
Yea Clockwork 2.5.1.2 disappears on its own for some reason. Once you have ext4 installed and 2.5.1.2 disappears you're screwed. 2.5.1.0 can't flash, back-up, or restore anything it seems.
i havent tried this with cm6, but the issue with 2.5.1.2 "disappearing," it might actually still be there. in 2.5.1.0, go to advanced > reboot recovery. you might get 2.5.1.2, i'm not sure where it installed, but ROM manager reboot to recovery foes to 2.5.1.0 but adb reboot recovery and reboot recovery from 2.5.1.0 brings up 2.5.1.2.
Is this kernel clockable
Sent from my SPH-D700 using Tapatalk
DevinXtreme said:
In case I don't catch you...
You forgot root in the kernel. So, here I am, super fast ROM, and no root access. Oh, and it took three tries:
1st - Formatted everything, couldn't remount anything
2nd - For some reason, 2.5.1.2 recovery just vanished, couldn't boot, house caught fire. Blah.
3rd - Smooth. Everything seems to be going well. Except root.
k thx bai
Click to expand...
Click to collapse
Meh. Look into it tonight. I used noobs cm initramfs as a base.
Sent from my SPH-D700 using Tapatalk
chaostrodamis said:
Is this kernel clockable
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Nope. It's stock with ext4 support.
no 3g working with this kernal going with the stock RFS and CM6 works fine
bryanfritz1 said:
Just for curosity do you have any links for actual half life of data on flash memory, would be a great resource if you did.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
A google search brings up tons of links.
Sent from my SPH-D700 using XDA App
amosher13 said:
i havent tried this with cm6, but the issue with 2.5.1.2 "disappearing," it might actually still be there. in 2.5.1.0, go to advanced > reboot recovery. you might get 2.5.1.2, i'm not sure where it installed, but ROM manager reboot to recovery foes to 2.5.1.0 but adb reboot recovery and reboot recovery from 2.5.1.0 brings up 2.5.1.2.
Click to expand...
Click to collapse
Reboot recovery from 2.5.1.0 did not bring up 2.5.1.2 for me. It hangs at the Samsung screen. I had to Odin again
Sent from my SPH-D700 using XDA App
Ill get back to you on that. Must be a problem with the initramfs. Ill look tonight.
Sent from my SPH-D700 using Tapatalk
I have had Hienz 57 running for about a month now and it seems to be running really slow. Even while doing the smallest things like typing it will be a couple letters behind. Anyone have any ideas. I have cleaned all the app caches and deleted what I don't use any more but still slow.
1fast72 said:
I have had Hienz 57 running for about a month now and it seems to be running really slow. Even while doing the smallest things like typing it will be a couple letters behind. Anyone have any ideas. I have cleaned all the app caches and deleted what I don't use any more but still slow.
Click to expand...
Click to collapse
Rebooting usually fixes this for me
Sent from my SCH-I500 using XDA App
That sometimes works but I was kinda looking for a more permenent solution. Would wiping the cache or dalvik possibly help?
1fast72 said:
That sometimes works but I was kinda looking for a more permenent solution. Would wiping the cache or dalvik possibly help?
Click to expand...
Click to collapse
you got voodoo enabled. what are your settings like...maybe you just need to re-odin then reflash the ROM and stuff...sometimes phones just need a fresh start
^Agreed. I can't count the times if done that. Mostly after I have went through five or so kernels but none the less it can't hurt and I haven't done it yet and regretted it.
Tap-a-Talked
There's a formatting utility here:
http://forum.xda-developers.com/showthread.php?t=1090127
I used the ext4 (voodoo) version and it worked great. I know they mean nothing, but I was getting 1500-1600 Quadrant scores before I ran it (still with voodoo), and I'm getting 1700-1800 now.
Sent from my Kangbanged Mesmerize
edit: This does wipe everything, so run your backups beforehand if you decide to try it.
That's the one I used today and it is freakin sweet. An excellant tool.
Tap-a-Talked
Yes I have voodoo enabled. I have not changed any voltage settings yet. When you say to re-odin are you saying to flash back to stock ec10 and then reflash the hienz 57? Still learning the terminology. I did go from the voodoo kernel to hienz without a fresh start. I also didn't wipe the data but for the first few weeks it ran awesome. I have also had a few half reboots. Like it would go to the android logo but not all the way to the samsung logo
defenestrado said:
There's a formatting utility here:
http://forum.xda-developers.com/showthread.php?t=1090127
I used the ext4 (voodoo) version and it worked great. I know they mean nothing, but I was getting 1500-1600 Quadrant scores before I ran it (still with voodoo), and I'm getting 1700-1800 now.
Sent from my Kangbanged Mesmerize
edit: This does wipe everything, so run your backups beforehand if you decide to try it.
Click to expand...
Click to collapse
+1 works great
Thinking of trying this but did you have the cwm 3 or just the 2.5.x? Also can I just flash the H57 zip and be back up and working?
Ran the utility and worked great. Have more memory too so the tons have been staying behind a little. Phone is much smoother and faster.
Sent from my SCH-I500 using XDA App
Normally i have zero issues with lag, however as of late I've had some slight issues with lag as well, even with lagfix enabled - to remedy it I simply enabled the 1120 overclock step and it's been fast ever since (and not too bad on the battery)
I just happened to be browsing the Sd card since I just dl the newest H57 and noticed that after formatting I dont have the android secure folder. Is this a problem or will it create a new one?
Sent from my SCH-I500 using XDA App
Would a kernel or a ROM be responsible for random restarts? I ask this because I feel it is my duty to inform the developer.
Droid Charge
0731 PBJ
Altered Beast 5
ZepHed69 said:
Would a kernel or a ROM be responsible for random restarts? I ask this because I feel it is my duty to inform the developer.
Droid Charge
0731 PBJ
Altered Beast 5
Click to expand...
Click to collapse
If you did not wipe data or caches, that could be your culprit. Anyways Altered Beast is a pretty old ROM and has not been updated in a while. There are more recent kernels than that too. Reflash and it should fix your problem.
Good point, although I like the theme, colors, and stuff, it is getting old. What do you suggest for kernel and ROM....I'm ready to try a new combo.
Droid Charge
0731 PBJ
Altered Beast 5
ZepHed69 said:
Good point, although I like the theme, colors, and stuff, it is getting old. What do you suggest for kernel and ROM....I'm ready to try a new combo.
Droid Charge
0731 PBJ
Altered Beast 5
Click to expand...
Click to collapse
Gummycharged.
Sent from my SCH-I510 using XDA Premium App
And Imoseyon's kernel.
Sent from my SCH-I510 using XDA Premium App
i had this issue on gummy 1.8.5. phone would randomly restart every day or two. switch to his GB rom and its gone.
ZepHed69 said:
Good point, although I like the theme, colors, and stuff, it is getting old. What do you suggest for kernel and ROM....I'm ready to try a new combo.
Droid Charge
0731 PBJ
Altered Beast 5
Click to expand...
Click to collapse
I was on AB when I first came to the Charge (my first smart phone). I Odined over GummyCharged 1.9.1 FE and never looked back. Now I'm part of Team GummyCharged as thread support. I came a long way. Lol.
Check out the developer forum.
Use gummy, eclipse or stock debloated. Gummy has nothing that intrigues me until they release 2.0, stock debloated is cool if you just want a good stock rooted experience and eclipse is a really nice looking version of stock, themed after touchwiz 4. As for the kernel? Just use the latest PBJ non-otb for best battery life.
Sent from an awesome phone using an awesome app.
I have a stock Droid Charge and mine randomly restarts too sometimes, and I've only had my phone a week.
I experience these random restarts a lot when I am using a custom ROM/kernel.
Doesn't matter what ROM I try the random restarts happen. I always wipe factory setting, cache, and dalvik cache before each install.
When I revert back to stock the problem goes away.
If anyone has more info on why these random restarts happen that'd be great.
Have you undervolted? Undervolting by too much seems to be the main cause of freezes and restarts for me.
Sent from my SCH-I510 using XDA App
asxa86 said:
I experience these random restarts a lot when I am using a custom ROM/kernel.
Doesn't matter what ROM I try the random restarts happen. I always wipe factory setting, cache, and dalvik cache before each install.
When I revert back to stock the problem goes away.
If anyone has more info on why these random restarts happen that'd be great.
Click to expand...
Click to collapse
Do you use Titanium Backup? Overclock or undervolt at all?
I noticed if I keep flashing without going back to stock first it happens to me as well. No matter what kernel. I also wipe and clear setrings
Sent from my SCH-I510 using XDA App
Same questions that I asked asxa86. Give me some info to work with please.
Well I mainly used GC w/PB&J which undervolts. So I was thinking my processor just couldn't handle the undervolting but then I just tried GC 2.0 recently which uses a new kernel and I'm still getting the random restarts.
I actually went to verizon today and got them to send me a replacement phone to see if i'm having hardware failure. Which doesn't make sense unless these custom ROMs/kernels are stressing my system more than stock would...
To answer the original question, i do not use titanium back up.
This is my process:
stock ED1 + PIT file flashed with odin
OTA EE4 update
Phone runs completely fine other than the usual laggyness of the stock phone
-root phone using ED1 root flashed with odin
-CWM flashed with odin
-factory rest, cache, and dalvik cache wipe
-install through CWM GC 2.0
everytime there is a new GC I get excited and flash the new ROM to my phone only to experience the random restarts the next day
Well, see if your replacement likes everything better, then you'll know it was your hardware.
Sent from my Droid Charge running GummyCharged 2.0
Ok, replacement phone came in today. I am reverting my old phone back to stock so it can be shipped back to verizon. Once I have my new phone up and running I will install gummycharge and see how everything works.
Just to be safe I had installed gummycharge 2.0 on my old phone and like I thought it would it ended up restarting itself x2 yesterday.
So having acquired the replacement phone and installing GC 2.0 FE on it. The phone went almost a full day with out restarting itself...
Don't know what to do now.
asxa86 said:
Well I mainly used GC w/PB&J which undervolts. So I was thinking my processor just couldn't handle the undervolting but then I just tried GC 2.0 recently which uses a new kernel and I'm still getting the random restarts.
I actually went to verizon today and got them to send me a replacement phone to see if i'm having hardware failure. Which doesn't make sense unless these custom ROMs/kernels are stressing my system more than stock would...
To answer the original question, i do not use titanium back up.
This is my process:
stock ED1 + PIT file flashed with odin
OTA EE4 update
Phone runs completely fine other than the usual laggyness of the stock phone
-root phone using ED1 root flashed with odin
-CWM flashed with odin
-factory rest, cache, and dalvik cache wipe
-install through CWM GC 2.0
everytime there is a new GC I get excited and flash the new ROM to my phone only to experience the random restarts the next day
Click to expand...
Click to collapse
I am experiencing the same issues on Gummy 2.0
My install method is:
Odin 1.9, boot to configuration, then cwm Gummy 2.0.
When I was previously on the Gingerbread Gummy I did not have this issue.
I have been experiencing this issue since I first began doing theses flashes.
I started with gummy 1.8.1 have tried other ROMs and even Gingerbread ROMs. It never fails. I get random restarts. I asked verizon for a replacement phone, got one and tried flashing again....random restart.
My process I stated above.
First post! Hopefully it's in the correct place!
Anyways,
I have rooted my phone using the ACE Hack Kit. Once that was completed I wanted to use the cyanogen ROM(recommend from a friend). I fully wiped from phone and then ran the cyanogen zip. Everything is fine until I use my phone for an extended period of time(for instance when I'm trying to set up my phone). For some odd reason my phone will freeze and I will be forced to take my battery out. From what I've read/understand I have done everything properly. Is there anything that I possibly missed or have not done that will cause these random freezes?
Thank you,
-ant_wailes
ant_wailes said:
First post! Hopefully it's in the correct place!
Anyways,
I have rooted my phone using the ACE Hack Kit. Once that was completed I wanted to use the cyanogen ROM(recommend from a friend). I fully wiped from phone and then ran the cyanogen zip. Everything is fine until I use my phone for an extended period of time(for instance when I'm trying to set up my phone). For some odd reason my phone will freeze and I will be forced to take my battery out. From what I've read/understand I have done everything properly. Is there anything that I possibly missed or have not done that will cause these random freezes?
Thank you,
-ant_wailes
Click to expand...
Click to collapse
You or anyone wouldn't happen to know off hand if the kernel is UVed or OCed? This sounds like a UV or OC problem. Its an easy thing to fix if it is and I find that's is always best to rule out the easy stuff first! Some phones don't like to be UVed or OCed at all and freezes like this sometimes are caused by exactly that, UV or OC.
edit: and oh yeah, WELCOME! If you really like CM ROMs, give absolution a try (at the very least, if you or someone doesn't know if the kernel is UVed or OCed, you're be using a ROM I'm familiar with and if the problem persists on this ROM, diagnosing the a UV or OC problem should be fairly simple and I'll know how to get that fixed quickly for you since I haven't used the straight CM ROM in quite some time!) Actually come to think of it, did you check the md5 number? you could have downloaded a bad link causing a bad flash. It's rare most of the time but I have seen it happen..
If you havent downloaded any apps and dont mind reflashing the ROM just down load the full wipe place in ROOT (No Folder) of SD Card go into recovery.
Full Wipe (DO NOT RENAME AFTER DOWNLOAD)
http://www.megaupload.com/?d=CJPE5CB7
1. Choose zip from SD Card (Full Wipe 1.5) and Install
2. Choose zip from SD Card (Cyanogen ROM) and install
3. Reboot system and enjoy.
I dont like to do the wipe cache, wipe dalvik whatever method, the zip 1.5 does a full wipe all on its own. Its an EXT4 Wipe so I use it for all EXT4 ROMS that I like to try out.
!!!WARNING: When you flash the full wipe do not exit recovery without installing your ROM. So make sure that when you enter into recovery thru Rom Manager to reflash make sure that you have both (Full Wipe Zip) and (Your ROM Zip) on your SD Card before installing.
I tried cyanogen and completed hated it. Absolution is the Bomb!!! But to each their own flavor.
ENJOY
@reponse
First off, thank you for the responses!
@MMM-BACONSTRIPS
I do not know if the rom is OCed or UVed(had to look up those). Here's the link to the page where I downloaded it from. Also, I did not check the md5 numbers.
http://forum.xda-developers.com/showthread.php?t=965342
So far today it hasn't froze on me. However, if it does it again I'll def look at some different roms (absolution & puregandroid)
@Reinaldo33897
I did full wipe(I don't remember if the version was 1.5) before I installed the rom. If anything. I'll try absolution and puregandroid.
Once again, thank you!
-ant_wailes
ant_wailes said:
First off, thank you for the responses!
@MMM-BACONSTRIPS
I do not know if the rom is OCed or UVed(had to look up those). Here's the link to the page where I downloaded it from. Also, I did not check the md5 numbers.
http://forum.xda-developers.com/showthread.php?t=965342
So far today it hasn't froze on me. However, if it does it again I'll def look at some different roms (absolution & puregandroid)
@Reinaldo33897
I did full wipe(I don't remember if the version was 1.5) before I installed the rom. If anything. I'll try absolution and puregandroid.
Once again, thank you!
-ant_wailes
Click to expand...
Click to collapse
Not a problem man! Be aware though with the 1.5 wipe that it DOES format your system and data to EXT4, and if I'm not mistaken if you make a back-up on EXT 4 and then format back to EXT 3, it will not work and the same applies for vice versa. If you do end up trying Absolution just drop on by the Q & A if the freezing problem persists, I or one of the devs will try to give you hand the best we can..feel free to PM if you go with Absolution
So does the 1.5 wipe SDCard also? will EXT4 end up being a problem? Also, will do! I really appreciate the help!
I'll def give absolution a shot!
ant_wailes said:
So does the 1.5 wipe SDCard also? will EXT4 end up being a problem? Also, will do! I really appreciate the help!
I'll def give absolution a shot!
Click to expand...
Click to collapse
No, if you use the full wipe it pretty much just does the wipe data, wipe cache and wipe dalvik cache in one flashable zip. I typically use the 1.5 then wipe data, cache and dalvik cache. It is completely overkill and really not necessary but I do it just the same. No, EXT4 should no cause a problem. I'm pretty sure that almost all the ROMs are now EXT4 supported. I believe it would say it if it wasn't at this point. I know the major ROMS (ARHD, CD, Bindroid, MIUI) are all compatible with EXT4. The only issues you will find with EXT4 is the issue I mentioned in my first post and if you want to use gene's tool to unroot.
Welcome to xda and yes I had the same problem I was setting up setcpu and I sneezed and I accidentally pushed it all the way over to 1.9 and my phone didn't like it it just froze...I was worried :/ so I turned my phone back on and went into setting and forced setcpu to close (mind you it took a few restarts lol) but yes I had let it reset itself and now it's working again I just need to remind myself to do a nandroid once a day xD hehe
Sent from my Inspire 4G using xda premium
No problem we are here to help each other. Usually if I want to get back to EXT3 I just flash the rooted ATT gingerbread ROM (PD98 zip) in hboot.
Sent from my Inspire 4G using xda premium
Reinaldo33897 said:
No problem we are here to help each other. Usually if I want to get back to EXT3 I just flash the rooted ATT gingerbread ROM (PD98 zip) in hboot.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
I believe there is a 1.3 wipe that formats to ext 3 again, just in case the OP wanted to format to ext3 before flashing a new ROM as opposed to flashing a new rom and then having to wipe and then flash again.
Cool Thx I'll do s search for the 1.3. It be good to have.
Sent from my Inspire 4G using xda premium
I have been running Tweaked 2.0 for a week or so, and it's great, but I continue to get hotboots. I'm not running anything else...no tweaks, no other kernels, just plain ROM...and still get a couple of hotboots a day.
I wanted to try the FP1 PBJ kernel, but that requires EXT4 for wifi to work.
I have the ext4_formatter_all.zip utility on my sd card, I booted to recovery, ran the formatter, reflashed Tweaked 2.0, then restarted.
My phone hangs on the Samsung logo.
The only method I found of getting it working again is go back to stock, take the OTA, then put Tweaked back on it.
So, I am doing this wrong? I used to be formatted for EXT4 in other ROMs, but I can't seem to get it to work now.
Not sure where you heard that PBJ requires ext4 for wifi to work because it doesn't.
Running the formatter does exactly what is says. It formats the partitions. There is nothing at all in them when it's done. You have to run the formatter, then reflash the rom and kernel.
FWIW, PBJ will likely do nothing at all to fix your hotboots. I'm going to go out on a limb and guess that you're running a lockscreen with music controls available. If you run the Circles lockscreen, it will probably fix your hotboot situation.
I must be mixing things up with respect to file system format, pbj kernel and wifi. My bad.
My steps are the same as you listed except I was not flashing the pbj kernel after flashing the ROM. I thought I could do that from Tweaktools. So I was trying to let the phone boot up, was gonna check that everything was EXT4, then install pbj.
But now that I think about it, are you saying the only way to use EXT4 with Tweaked 2.0 is to have the pbj kernel installed? If so, then that's my answer. If not, then I still don't understand why my phone won't boot after I format ext4/flash ROM.
sbradley07 said:
I must be mixing things up with respect to file system format, pbj kernel and wifi. My bad.
My steps are the same as you listed except I was not flashing the pbj kernel after flashing the ROM. I thought I could do that from Tweaktools. So I was trying to let the phone boot up, was gonna check that everything was EXT4, then install pbj.
But now that I think about it, are you saying the only way to use EXT4 with Tweaked 2.0 is to have the pbj kernel installed? If so, then that's my answer. If not, then I still don't understand why my phone won't boot after I format ext4/flash ROM.
Click to expand...
Click to collapse
Because running the formatter reformats the filesystem where the kernel is stored as well. Tweaked doesn't ship a kernel at all, so if you just flash it, you don't have a kernel on your phone at all.
...and regarding the hotboots, yeah I didn't expect the new kernel would help there. I figured if I'm gonna continue to get hotboots, I might as well see if I can get better performance out of it.
I don't use any lockscreens. I have it disabled entirely. And I rarely play music on my phone...Pandora once in a while. Maybe disabling lockscreens contributes to hotboots too?
sbradley07 said:
...and regarding the hotboots, yeah I didn't expect the new kernel would help there. I figured if I'm gonna continue to get hotboots, I might as well see if I can get better performance out of it.
I don't use any lockscreens. I have it disabled entirely. And I rarely play music on my phone...Pandora once in a while. Maybe disabling lockscreens contributes to hotboots too?
Click to expand...
Click to collapse
have you seen dwitherell's hotboot fix in the TS 2.0 thread? there are several posts about hotboots there (mostly about changing the heapsize from 64 to 80 or 96 I believe).
I read on another forum that it could be attributed to an app or two that you are running (maybe even have that app installed on your SDCard - trying moving them to your phone's internal memory one by one and see if the problem persists).
regarding re-partitioning:
so here's what I think you need to do:
- download and install terminal emulater
- find out if you are RFS or EXT4 (if RFS, proceed to next step)
- download and CWM IMO's kernel (after mounting, wiping cache/dalvik)
- re-boot
- re-install the dirty PBJ kernel via CWM (after mounting, wiping cache/dalvik)
I have not tested this yet - as I have no real need to outside of just curiousity. so if you want to take the plunge, go for it. but I'm not responsible for what happens....
I tried the heapsize tweaks, stepping up the heapsize over the course of a few days. I think it might have reduced the hotboots a little (like 3-4 boots over a 2 day period instead of 4-5 boots.) I will start investigating my apps, though most are already installed on the sd card.
I'm formatting to EXT4 right now...fingers crossed!
Update: all good now! Thanks Shrike!!
Here's what I did when I moved to FP1:
1. Flash FP1 ROM of choice, and then flash imoseyon's Voodoo kernel (the fact that wifi breaks on this kernel doesn't matter)
2. Boot phone. Wait as the phone reformats as ext4 (saves your data too!)
3. Once phone starts up, boot back into CWM and then flash the FP1 PBJ. This will fix your wifi.
Sent from my SCH-I510 using xda premium
Thanks for the suggestion kv. I was hoping my question would result in the documentation in one place of the the methods to correctly format to ext4. Now we have that (assuming yours is correct LOL!) Of course it was my own dumb oversight that Tweaked 2.0 didn't come with a kernel that caused all my problems in the first place.
I opted for the ext4 formatter route mainly because of the hotboots I get with this ROM. I figured, if I'm gonna make changes, make the ones with as clean an install as possible...and the formatter wipes everything.
Fyi, switched over to ext4. Worked great except that my phone was stuck at the boot screen for 40 minutes. A simple power off and power back on and I was good. So the steps I outlined above worked (for me). But curious to see if anyone else got stuck at the boot screen after the repartitioning.
tappin' that....
Yep, same thing happened to me. Got stuck on the first boot after flashing. Powered off, restarted, good to go.
And on a side note, I've had zero hotboots since going to EXT4 and PBJ FP1. Was getting 3-4 a day before that.
actually just got my first hotboot - tried taking a pic with the Camera Zoom FX, and when saving the pic, it did a hotboot.... tried it again, and it was fine - so I don't think it was a direct result of the ROM or anything else...
Help - rfs or EXT4
answer found!
jco23 said:
Fyi, switched over to ext4. Worked great except that my phone was stuck at the boot screen for 40 minutes. A simple power off and power back on and I was good. So the steps I outlined above worked (for me). But curious to see if anyone else got stuck at the boot screen after the repartitioning.
tappin' that....
Click to expand...
Click to collapse
I got stuck too on the reboot. I didn't wait 40 minutes though. Restarted after 5 minutes. Sometimes you just know when to pull the plug.
sbradley07 said:
I must be mixing things up with respect to file system format, pbj kernel and wifi. My bad.
My steps are the same as you listed except I was not flashing the pbj kernel after flashing the ROM. I thought I could do that from Tweaktools. So I was trying to let the phone boot up, was gonna check that everything was EXT4, then install pbj.
But now that I think about it, are you saying the only way to use EXT4 with Tweaked 2.0 is to have thezsweee pbj kernel installed? If so, then thdat's my answer. If not, then I still don't understand why my phone won't boot after I format ext4/flash ROM.
Click to expand...
Click to collapse
zd
Sent from my SCH-I510 using Tapatalk
compumaniajr said:
zd
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
What?
Sent from my SCH-I510 using xda premium