is it the phone?? flashing problems. - Epic 4G Q&A, Help & Troubleshooting

So lemme say first i can over from an HTC and love the way this baby works. i was very active in my HTC and flashed and did a lot of stuff to it, also doing a lot to my brother and sisters phones to. Evo and Captivate. my brothers evo like my HTC wasnt that bad at flashing could just download and go. I had so many problems with getting odin or one click to read my phone i was so upset cause i couldnt get to flashing. WELL now my comp is a champ and working like a charm, my phone on the other hand not so well. I once got SRF 1.0.1 to flash but it was real buggy on me, force closes, browser was screwy. Also Odin flashed SwissCheese but was slow. The reason i Odin flashed it is because no matter what rom i try and flash i get stuck on the samsung screen. even SFR 1.0.1 does it too. I have looked all over for the answer and nothing. I know what i am doing when it comes to these androids and am very good at figuring out the solution, but i am stuck. I am 100% sure i have done everything step by step per the devoloper.... just saying, anyone have a clue? think it could be my phone?

Odin back to stock. I have a video made, click the link in my signature.
Sent from my SPH-D700 using XDA App

2 things, first coming from stock EC05 is screwy to begin with and it is best to do all the wipes. It would be much better to either Odin in an EC05 or EB13 prerooted. Then when you pick a ROM is it EXT4 or RFS? If you pick an EXT4 ROM make sure you have converted to EXT4 somehow first unless the ROM says it will convert it for you. If you try to flash an EXT4 ROM on an RFS system without converting, you will get stuck at the SAMSUNG screen.

Okay well here's a little update... I have tried using 3.0.2.5 many times in the past with the same results. Stuck at samsung screen!! I have made sure to use the flashable rfstoext4 before flashing a ext4 rom, even tho SRF converts for you. I feel like a baffled idiot on this because I have done this so many times on other phones and am very quick to figure out a solution if needed... BUT I AM LOOOOOST I did see a few good suggestions I am gonna try... I am gonna odin a prerooted rom and see.
For ****s and giggles I tried to flash the ONE rom that did work for me SRF 1.0.1 and it worked! But very buggy still. Even a fresh dwnload of he rom will not work as it didn't before. Just the one file I downloaded before as its been the only one that worked. Also I tried to flash SRF 1.2 on top of it and still stuck at the samsung screen.
I am confused as to what is going on. I have tried many different things and to no prevail. I even started to think maybe it is the stock rom I am odin'in to but even flashing over the SRF I had the same outcome....
You think it could possibly be a phone problem?!?!
Sent from my SPH-D700 using Tapatalk

I flashed an EXT4 rom without converting. What can I do to fix this?

B4LLS4GN4 said:
I flashed an EXT4 rom without converting. What can I do to fix this?
Click to expand...
Click to collapse
Did you try to restore a nand backup of your last working configuration? You can install an RFS ROM like RFSplus or one of the Gingerbread leaks. Pull your sd card out and put it into a computer to download and copy an RFS ROM onto it and put it back into the phone and flash.

Related

[Q] Oh Snap!! what did i do???

Ok here the deal, Well first i wanna say hello and thanks for reading.
I need a lil help, So here's the deal. I flashed my brand new epic to a custom ROM.
First i followed the steps (DK28-Odin-Modem-PIT) Worked like a charm. Then i flashed (VIPERrom (FRoZeN) DK28) also worked like a charm, But i didnt really like rom much, So i moved to (SyndicateROM) Now wow i Loved it but didnt like the fact that it was 2.1 (meaning no app2sd and and few other thing i didnt like)
Then i was going to try (Mammon's Bonsai4All) Still using CWM z2.5.1.0 to flash all these ROMS. So flashed ok but when i went to reboot its just stuck at the SAMSUNG LOGO.. So i said to my self let me just Wipe (Factory Reset, Cache,Delvik) and BAM!!! this the same problem
So i said well maybe its the ROM it self....
So wipe and again and install ROM i was on maybe that will fix the problem..BAM !!! rite??? NOPE!!! lol still stuck on the SAMSUNG LOGO..
AM I done for??? or is there a way to fix this???
Lucky i still have my evo....
thanks for any help
EDIT: I notice something at the bottom of the recovery menu, It say E:can't open /cache/recovery/log ??? any idea why its saying this?
EDIT: I also notice while phone is powered down and i put on charger the battery Icon its also stuck like its not moving.
Just odin the DK28 modem again
battery pull
press 1 + power button
then if you want to try any of the EXT4 Roms Root with this instead of 2.5.5
http://forum.xda-developers.com/showthread.php?t=897612
iSaint said:
Just odin the DK28 modem again
battery pull
press 1 + power button
then if you want to try any of the EXT4 Roms Root with this instead of 2.5.5
http://forum.xda-developers.com/showthread.php?t=897612
Click to expand...
Click to collapse
Yes this was one of the first things i tried ,was to redo the Ordin
do you know which ROM i should flash once it done??? and is it safe after the Ordin reset to pull out battery and flash ROM??? If so which ROM so i be flashing ???
So far after the Ordin i Tried flashing only the 2.1 custom ROMS that was working at the time, Now im getting a bunch of errors inside the CWM menu while flashing. Its giving me a bunch of LOG errors.
Thank every one for reading and helping (Any modz feel free to close tread) I have phone working now.... What i did was just used ordin to reinstall stock ROM and removed sdcard while using ordin and BAMMMM!!!!!! YES!!!!! Worked like a CHARM..
Good to hear you got it fixed. Your problem was that Bonsai 2.0 is now ext4 only and you didn't convert from rfs to ext4. You need to either convert to ext4 or use rfs compatible roms.
DiGi760 said:
Good to hear you got it fixed. Your problem was that Bonsai 2.0 is now ext4 only and you didn't convert from rfs to ext4. You need to either convert to ext4 or use rfs compatible roms.
Click to expand...
Click to collapse
Yeah i just learned the difference today sadly lol.... but thanks for your input. So far im not liken the 2.2 roms that's out, so ill stick too 2.1 for now syndicateROM is beasty god that thing flys so it will do just find...
Quick question... is there any way i can get the boot up sound and animation from the viperROM?? on the syndicateROM? i love the animation and the sound Fx from the VIPERrom. (FRoZeN) DK28 or have the sounds in a wav format so i can put them on my sdcard???
EDIT: And also the unlocking sound fx from the VIPERrom (FRoZeN) DK28 is this even possible to port something like that from someone ROM to another?

[Q] Clockwork recovery problem...

Hey guys, check it out. I just figured out how to get into clockwork recovery, and assuming and going about flashing a rom just like I would on my evo, I go ahead and download a rom for the epic, flash it, and it works fine. So it loads up like normal after a flash n reboot, and it kept saying no service... so I was like... uh... weird.. so I booted back into clockwork and tried nand back to the backup I did before flashing anything, of course... but I started getting an error saying it couldn't open recovery.log and now it freezes restoring at saying "lost+found" .... so I pull the batter, and now it just automatically revolts to clockwork all the time, and trying to boot the system normally... I'm not using CWM 3+.. rather the older 2.xx ... any ideas?
It's hard to understand your writing. I think the best thing you can do is use Odin to flash back to stock and start over. You didn't say what version of android you were on but if it's dk28 did you flash the modem?
What rom did you flash? I take it you were on stock di18 before?
Flashing a rom based on one of the leaked froyo builds without also flashing a modem could cause the initial problem.
And nandroid doesn't backup or restore the kernel, so using that to restore still leaves you with the kernel of the rom you flashed before, which can cause problems across build versions.
You're best bet is to odin back to di18 and start again.
musclehead84 said:
It's hard to understand your writing. I think the best thing you can do is use Odin to flash back to stock and start over. You didn't say what version of android you were on but if it's dk28 did you flash the modem?
Click to expand...
Click to collapse
Thanks a bunch, I know I re-read my post and was like.. man I wasnt descriptive at all... LOL, but I checked out this Odin, and TBH i have NO idea what all this stuff is for the Epic, only doing it to fix the booboo I did on my g/f's phone I have the Evo so its totally different stuff almost... Anyways im back to stock, now I need to read up before screwing around again .

[Q] Tried to install bonsai, now phone is bricked

I hope someone can help me. My Epic 4g was on EC05, RFS, and I tried to install Bonsai 4.0.0 exactly as written in the installation instructions. Now my phone is trapped in a boot loop, and it's booting into CWM 2.5.1.0 for some reason. I could have sworn I installed CWM 3.0 something.
Anyway, I installed Bonsai, and it seemed to go just fine, but then it froze on the samsung screen. Nothing would work, so I pulled the battery to reboot. And then I was trapped in the boot loop.
I did do a CWM backup before I installed bonsai, but even after restoring, I still get the boot loop.
CW keeps saying something about the sd-ext.img not found, skipping restore of sd-ext.img. and it can't find cache/log or something
I tried to odin back to the EC05 I had before, but even though it says successful, I'm still stuck in the boot loop. It just will not boot back into the main OS.
Is there anything I can do, or is my phone just hosed?
Please someone help me.
unseen wombat said:
I hope someone can help me. My Epic 4g was on EC05, RFS, and I tried to install Bonsai 4.0.0 exactly as written in the installation instructions. Now my phone is trapped in a boot loop, and it's booting into CWM 2.5.1.0 for some reason. I could have sworn I installed CWM 3.0 something.
Anyway, I installed Bonsai, and it seemed to go just fine, but then it froze on the samsung screen. Nothing would work, so I pulled the battery to reboot. And then I was trapped in the boot loop.
I did do a CWM backup before I installed bonsai, but even after restoring, I still get the boot loop.
CW keeps saying something about the sd-ext.img not found, skipping restore of sd-ext.img. and it can't find cache/log or something
I tried to odin back to the EC05 I had before, but even though it says successful, I'm still stuck in the boot loop. It just will not boot back into the main OS.
Is there anything I can do, or is my phone just hosed?
Please someone help me.
Click to expand...
Click to collapse
Try to Odin to the EB13 version prerooted with CWM 3.0.0.6 found here:
http://forum.xda-developers.com/showthread.php?t=853209
And then after the conversion to EXT4 then flash Bonsai.
Ihad this exact same issue. Had cwm 3.0 installed and somehow it got changed to 2.5. I had to odin back to stock.
sultan.of.swing said:
Ihad this exact same issue. Had cwm 3.0 installed and somehow it got changed to 2.5. I had to odin back to stock.
Click to expand...
Click to collapse
I think this is an EXT4 conversion issue. When it encounters an error it reverts to 2.5.x with RFS. So best thing is odin and reflash.
BONSAI 4 and loving it!
Thank you so much. That worked like a charm. I guess I just needed to do a full wipe instead of the no wipe version I had been using. I haven't tried bonsai again yet. I'm kinda scared. I guess though now that I have EXT4, I shouldn't have this problem anymore, right? Woulda been nice if they would've said that RFS will crash your phone on the bonsai install instructions.
unseen wombat said:
Thank you so much. That worked like a charm. I guess I just needed to do a full wipe instead of the no wipe version I had been using. I haven't tried bonsai again yet. I'm kinda scared.
Click to expand...
Click to collapse
No problem. You should have no problems with Bonsai if you have the fresh odin'd eb13 and have the clockwork mod 3.0.0.6 set up. Then follow instructions to odin ec05 modem after Bonsai install.
BONSAI 4 and loving it!
A phone is not bricked if it turns on. A bricked phone is nothing more than a paperweight. I see this word get used so much but 99% of the time the phones go into download mode and then Odin works
Sent From My Evo Killer!
musclehead84 said:
A phone is not bricked if it turns on. A bricked phone is nothing more than a paperweight. I see this word get used so much but 99% of the time the phones go into download mode and then Odin works
Sent From My Evo Killer!
Click to expand...
Click to collapse
To the user asking the question it is a brick
Until someone helps them get it working again.
The term brick means the phone can not enter download mode. Bonsai doesn't support rfs that's what your problem was. There is only one custom rom that is rfs and I won't mention it. Also make sure you go into cwm or you haven't converted to ext4 yet.
Sent from my SPH-D700 using XDA App
Yeah, I guess technically it wasn't a brick. I was flippin out though because I thought my phone was done for.
Anyway, I got brave and installed bonsai. It's working fine, but I'm not sure I like it. Like where did the clock on the statusbar go? Now I only have the date. And my accuweather clock is gone from the widgets. So is the task manager widget.
So if I wanted to go back to stock, I can just use kenny's first link to odin back? Or do I need to do something special now? Is there a way I can do it without wiping all my data again?
unseen wombat said:
Yeah, I guess technically it wasn't a brick. I was flippin out though because I thought my phone was done for.
Anyway, I got brave and installed bonsai. It's working fine, but I'm not sure I like it. Like where did the clock on the statusbar go? Now I only have the date. And my accuweather clock is gone from the widgets. So is the task manager widget.
So if I wanted to go back to stock, I can just use kenny's first link to odin back? Or do I need to do something special now? Is there a way I can do it without wiping all my data again?
Click to expand...
Click to collapse
There is a mod in the bonsaigeek.com website to put the clock back. There is also links there to point you to reinstalling stock apps and widgets. One of the places I remember that has the stock stuff is Frankenstein ROM thread in Development section. If u have trouble finding any of this I can post the links when I get home this evening.
BONSAI 4 and loving it!
And yes, you can always go back to stock with the method I posted. There are EC05 stock links in the threads as well.
BONSAI 4 and loving it!
Thanks man. I just noticed my bluetooth won't connect either. This is getting to be more trouble than I want to go through with my phone. I think I'm just gonna go back to stock. Is there a way I can do it without wiping all my data? Not that I have much now anyway, just what I've put in since last night.
i got fix and this will take you back to the basic
unseen wombat said:
Thanks man. I just noticed my bluetooth won't connect either. This is getting to be more trouble than I want to go through with my phone. I think I'm just gonna go back to stock. Is there a way I can do it without wiping all my data? Not that I have much now anyway, just what I've put in since last night.
Click to expand...
Click to collapse
Since you are rooted you can get titanium backup from the market and backup your apps and data. Then after you Odin back to stock you can download titanium again and restore it. Before you Odin back you might try a factory data reset after backing up and then check your bluetooth.
BONSAI 4 and loving it!
Try this to fix bluetooth before wiping. Might save you some time.
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Mandro1d said:
fourthpost
Click to expand...
Click to collapse
Dear spamming user,
You are proving why there needs to be a post count requirement on the development forum. Please jump in a well and drown.
Love,
k0nane
k0nane said:
Dear spamming user,
You are proving why there needs to be a post limit on the development forum. Please jump in a well and drown.
Love,
k0nane
Click to expand...
Click to collapse
THANK YOU!
Makes me wish there was a way for the OP to ban someone from a thread!
Hmmmm, out of curiosity, is there any work around if the phone wont go into Download mode? scanning posts and i caught this. I have only heard of a few sincerely bricking the epic.... just curious (info for the arsenal..lol)... thx
Odin back to a previous stock and one click root to the right verision of cw mod. Cw3 for ext4 file sytem.
Sent from my SPH-D700 using XDA App

[Q] Need help with CWM Recovery and other issues!

Hello All,
I have been working with my friends EPIG 4g phone for a while now. The first thing I did was use "superoneclick 1.7" to root his phone. Then he got interested in trying different roms+kernels, so he came to me for more help. Almost all the custom roms I was researching are EC05 based roms, so I looked further into it. For reasons unknown, he is still on DI18 Eclair (must not have got the OTA). I dug on forums and found the zip file that would allow him to jump from DI18 to EC05 (froyo), but I need a custom recovery to install the zip. No matter what I try, I cannot get the phone to boot into CWM recovery. (Tried both from rom manager, and using camera button+vol. down+power combination) I have tried just about everything that I can think of, to no avail.
I have also tried:
Unroot & Re-root using process found here:
http://forum.xda-developers.com/showthread.php?t=770388
Wiping all data via factory reset (really wish I wouldn't have, waste of a try)
Tried using methods found here:
http://forum.androidcentral.com/epic-4g-rooting-roms-hacks/34603-clockworkmod-recovery-rom-manager-guide.html
When trying to do anything in the stock recovery, I always get the:
e:signature verification failed errors.
Please bombard me with any and all ideas you guys have. I am currently about to try to manually install the CWM recovery by placing the update.zip file on the SD root directory. IF I can get that part done, I'm confident I will be able to get everything going. Another option I have read from other people's threads that I have not yet used is the Odin revert to stock and then flash some special .tar files. I took a look at Odin and don't remember seeing options for "stock" or anything, so if anyone can point me to a good Odin walk-through, that would be awesome.
PS: Ask me if I have failed to clarify on any aspects of the problem. Forgive me for not including more info on the problem, Ive been through like 8 hours of random stuff while trying to fix this, so Ive seen too much to remember everything I've seen.
Thanks in advance!
-Clarity
Too many words
I kinda fell a sleep in the middle so yeah
If you want to return too stock use odin
If you want to go to froyo from eclair use odin
If you want cw use I've of the one click rooters
Going to cw is just pressing every button that is not on the keyboard
(power + volume up + volume down + camera)
Sent from my SPH-D700 using XDA Premium App
Stock recovery will get you nowhere on this phone, and with all you have tried so far, I believe Odin is the best course of action. Here is a link to the Odin package-
http://www.mediafire.com/file/fn9s5cqkkwyu68d/Odin3+v1.61andepic.pit.zip
Unzip it to a folder on your desktop.
The necessary drivers and instructions for using it are here in the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
Follow the instructions carefully and be sure the drivers are installed before starting. Obviously, wherever it mentions the DI18 tar, you will use the current one in it's place. You can use this one, it's pre-rooted and de-odexed.-
http://forum.xda-developers.com/showthread.php?t=1021305
That tar file is still RFS file system so you will need to install CWM 3.0.0.6 and boot into it with the 3 finger solute so it can convert the file system to ext4. Package and instructions here-
http://forum.xda-developers.com/showthread.php?t=897612
If you made it this far you should be able to install one of the current ROMs you've been shopping for.
Thanks for the responses guys, I will try that out when I get a chance. Might be a while though because I don't see my friend that often.
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Basically, I would like to know what I am doing wrong here. Is the CWM included from that .tar file compatible & ready to flash any custom ROM that I want? Or do I need to use that CWM 3.0.0.6+root that Mattalica suggested? The EC05 was prerooted, so I'm wondering what happens if I use the 3.0.0.6 exploit on top of this root... Let me know guys.
onlyclarity said:
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Click to expand...
Click to collapse
What happend when you rebooted that indicated it was not successful? If you had strange vibrations and a bootloop, that is common when trying to flash these new generation ROMs like ACS and Bonsai. A simple reflash usually fixes it.
Sent from my SPH-D700 using Tapatalk
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
onlyclarity said:
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
Click to expand...
Click to collapse
BakedSnack 1.6 is a RFS ROM and is DI18 based. If you installed CWM 3.0.0.6, it would have converted your filesystem to EXT4. BakedSnack 1.6 does not have kernel support for EXT4. However if you installed an older version of CWM it would explain how ACS failed to install and how BackedSnack 1.6 was able to install and boot.

[Q] Problem with midNIGHT rom 5.2 RFS/Journaling on

I've tried to install midNIGHT rom 6 times now with the same result. I cannot install any apps from the market, titanium backup, or from sdcard. It will vibrate once at the beginning of install than again 2 or 3 times. My phone will then show the bootup animation and return to the homescreen. Ive odined back to stock and rerooted 4 times and wiped everything 3x each time. Each time I get the same result. Ive also tried reformatting my sd card and starting with a fresh download. Other roms work, just not this one. I dont have enough posts to reply to the midnight thread, so what should I try next to make it work?
acburnett said:
I've tried to install midNIGHT rom 6 times now with the same result. I cannot install any apps from the market, titanium backup, or from sdcard. It will vibrate once at the beginning of install than again 2 or 3 times. My phone will then show the bootup animation and return to the homescreen. Ive odined back to stock and rerooted 4 times and wiped everything 3x each time. Each time I get the same result. Ive also tried reformatting my sd card and starting with a fresh download. Other roms work, just not this one. I dont have enough posts to reply to the midnight thread, so what should I try next to make it work?
Click to expand...
Click to collapse
what rom did u have before that workd ??
i had acs with ext then flashed to rooted ec05 with rfs. had several eclair roms installed.
acburnett said:
i had acs with ext then flashed to rooted ec05 with rfs. had several eclair roms installed.
Click to expand...
Click to collapse
MAYBE YOUR flashing the wrong rom to update from the midnight ex: if you use dk28 ... i dnt think thats gets the proper update ec05
so lets see if you flash a dI18 or better get eb13 stick rom ... now u can either flash the ec05 modem or as my phone did when i used the stock eb13 it sent me the update for ec05 then i rooted w 3.0.6 clockworkmod then i went to BONSAI .. i left BONSAi to midnight ... i wiped factory data 3x - cache petition 3x and davlik cache 3x ... then i installed the zip MIDNIGHT V5.2 JOURNALING ON .... THEN AFTER IT BOOTED .... i went back into RECOVERY and flash the ZIP EXTRAS .. bang it was magic ... lol'
but basically im tryn to give you steps that maybe something might help u or give u and idea ..... IT WORKED FOR ME .....
DISCLAIMER : im not a professional if something major goes wrong i dnt not claim responsibility ...
I have the same problem. Worked the first time I installed it but I restored back to stock. Now when I install I can't install from market. Tried odin back to stock but It still doesn't work. Haven't seen a solution in the midnight thread besides going to EXT.
I am having issues as well and cannot post a reply. I have wiped and re installed 3x but my phone will randomly turn off and I have to pull the battery to reset device. If the device stays plugged in I do not have this issue. Any ideas or suggestions would be greatly appreciated!!
You note that this version is the one with journaling enabled... have you tried the version without journaling? You can manually re-enable it by making a CWM Nandroid backup and then restoring that backup immediately after.
acburnett said:
i had acs with ext then flashed to rooted ec05 with rfs. had several eclair roms installed.
Click to expand...
Click to collapse
On the instructions for midNIGHT 5.2 with Journaling On it says not to start with a pre-rooted EC05. Start with stock EC05 and then root with CWM 2.5.5 for RFS or 3.0.0.6 if you are wanting to use the EXT4 one. There is a link for a stock EC05 on the instructions in the thread for the ROM
And how to check if the journaling is actually on or off.
dito33 said:
And how to check if the journaling is actually on or off.
Click to expand...
Click to collapse
I'm not sure if there's a quick and easy way to detect this through the Terminal Emulator. I tried a line of code that I believed would tell me but I didn't get the answer I was looking for. Someone else may have the answer.
The quick and dirty way, however, is to make a Nandroid backup through Clockworkmod, as you should generally just have one at all times anyway. Now turn your phone on, and pull the battery out. If when you turn your phone back on you don't encounter any FC's, then your journaling is on and your data is protected. If not, then restore your Nandroid backup you just made and that will enable journaling.
If you installed a no-journaling rom, rest assured, journaling is off if you haven't restored. Either way you should have a Nandroid backup just in case.
Note: This process has been documented and posted many many many times across XDA at this point.
I was also having this issue so I installed the EXT4 Journal On version and problem solved. No one knows why LOL.

Categories

Resources