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.
Related
ok i got a brand new epic and with my old epic i was on midnight rom v3.0. I put the same sd card into the new epic and i odined to dk28 and ran the 1click root with cwm3. i turned the phone off and rebooted into cwm3 and it turned it over to ext4. after that i went to restore the midnight rom 3.0 that i had saved and now i get stuck at the sammy screen... What did i do wrong? PLEASE HELP ME!
Odin back to stock and do a clean install i believe there is problems when restoring in midnight 3
ok so how do i go about doing a totally fresh install? will you give me steps PLEEEEAAASSSSSEEEE? Cause i tried doing that. this is what i tried first. I odined into dk28 and then i did one click root with cwm3 and the phone booted up. Then i 3 fingure salute into cwm3 and it automaticaly tried to convert it to ext4. everything went fine but the sd-ext that failed. then when i tried to reboot from there it got stuck.
should i partition the sd card? and its been a while since i first went to ext4 from stock dk28 and i cant exactly remember the whole process. LOL, if you could give me step by step from stock dk28 to midnight rom v3.0 i would be so releived cause right now the stock is crap...
Batt pull
download mode (Power on +1)
odin dk28
setting make sure usb debugging is checked
Root with cw3
boot into cw3 power off then (vol down+power+camera)
factory reset x3
wipe cache x3
wipe dalvik x3
flash no journalizing mod
flash midnight 3.0
I cosign on iSaint's comment. Pull the battery, go into download mode, odin to dk28, flash cwm3, no journal zip (if you want), flash the rom (do not restore. do a fresh flash). Once it's up and running, go back to cwm3, do an advanced restore and restore data only. Nothing else.
ill try again and i will let you know what happens, but im pretty sure i tried that and i get stuck at sammy. I dont know if its the new phone and the previous sd card with all my info thats effing it up or what. i think its the cwm3 converting everything to ext4 and it fails. ill let you know in a min. thanx
ok this is what happens everytime. after i root with cwm3 i turn the phone off and 3 fingure into cwm3 and b4 i can choose the zip or anything it starts trying to convert rfs to ext4 and it makes a restore point and says "no sd-ext found. skipping backup of sd ext.
generating md5 sum
backup complete
checking md5 sums...
restoring system...
restoring data...
restoring.android_secure...
restoring cache...
sd-ext.img not found. skipping restore of /sd-ext.
restore complete!
so should i still do the 9xwipe?
cause i did that b4 and it gets stuck at sammy...
i followed those exact steps and on startup it does the regular dk28 startup with a ANDROID word flashing sidways over the startup animation and then my phone starts up but i cant push anything. it keeps vibrating and shuts off and then comes back on and shuts off again and again. something is very wrong and the only thing i can do is odin back to dk28. what should i do? i am very dissapointed...
You could try the other method of converting. Install cwm 2.5.1.0 instead of cwm3 on top of dk28. Get "prepare.zip" from the original ext4 conversion thread, which will set you up with 2.5.1.2. Run the formatter from your computer. Advanced->reboot recovery from 2.5.1.0 to get to 2.5.1.2. Then flash your ext4 rom from 2.5.1.2.
Oh, and sd-ext *should* fail if you haven't formatted your sdcard for apps2sd. It won't cause any problems for you, though.
flash midnight 2.9
then flash midnight 3.0
Ok so while it was acting all bugged out I pulled battery and then 3 fingured into cwm3 and I took a chance and restored on 2.9 and everything is perfect. I think something is seriously wrong with v3.0. What do y'all think?
Sent from my SPH-D700 using XDA App
yea 3.0 doesn't work well with restoring data but glad everything worked out for you
thank all of you soooooo much for all of your help and ideas. dont know what i would do without all of you. thanx
it seems like a lot of the vibrations and boot failures comes from the wiping thing. do oneclick cwm3 and ext4 conversion then factory reset at least 3 times then do cache and dalvik at least once. after that you can install your favorite rom for the most part
Tried Bonsai and Syndicate first, neither flashed properly first time, seemed to work on the second flash, but eventually they would start freezing occasionaly when the screen was off, had to pull out battery to reboot. Tried flashing to stock di18 then flashing to Midnight, it seemed to work for a day or so, and now its freezing a few times a day when the screen turns off. I read somewhere that in odin you only need the victory8g.pit (not sure the exact file name) if you are flashing a custom rom, and I'm only ever flashing a stock rom, then rooting and flashing from the sd card. I've always used the .pit file im odin, and I've eventualy had problems with all custom roms.
Any ideas?
Skimp Killah said:
Tried Bonsai and Syndicate first, neither flashed properly first time, seemed to work on the second flash, but eventually they would start freezing occasionaly when the screen was off, had to pull out battery to reboot. Tried flashing to stock di18 then flashing to Midnight, it seemed to work for a day or so, and now its freezing a few times a day when the screen turns off. I read somewhere that in odin you only need the victory8g.pit (not sure the exact file name) if you are flashing a custom rom, and I'm only ever flashing a stock rom, then rooting and flashing from the sd card. I've always used the .pit file im odin, and I've eventualy had problems with all custom roms.
Any ideas?
Click to expand...
Click to collapse
What version of the ROMs are you trying to use?
If you start with di18 and tried to use a dk28 ROM you would have to odin the new modem.
If you're trying the EB13 ROMs, then you want to odin the EB13 tar that is stock + recovery + ext4; then flash an EB13 ROM of your choosing.
Also, you have to be sure to wipe 3x (factory reset, cache partition and davlik cache)
Be sure to follow each and every step on the first few pages of the ROM thread your going to flash, also read some into the thread too. that will give you a heads up as to what others have experienced and what might be a problem and its fix.
Good luck!!
With syndicate and bonsai I flashed the stock eb13 first, then cwm, then flashed the rom in recovery mode, midnight I flashed from stock di18, followed all instructions. Just tried midnight again, except I didnt used the victory8g.pit file or whatever, just the di18 tar, then cwm then flashed the rom.
I think me using the pit file may be what the problem was, unless you are supposed to use the pit file even when flashing a stock rom, in odin.
Are you using setcpu? Do you have a screen off profile? Are you running your phone at 1.2ghz?
Sent from my SPH-D700 using Tapatalk
Are you using setcpu? Do you have a screen off profile? Are you running your phone at 1.2ghz?
I'm not sure the answer to any of those questions, so I'm assuming no. I think the MidnightROM can run the cpu faster, but you have to download some app to turn that function on or off. I'm pretty much running MidnightRom with the regular **** on it right now. I'm thinking my problem may have been using the victory8g.pit file in odin every time I flashed to a stock rom before running clock work and flashing to a custom rom. I'm running the latest midnight off a clean flash of di18 without the victory8g.pit file, so far that seem to be the only thing I can find that would cause all the custom roms to eventualy crash...
Im going on a few hours with out a crash, but the first time it took a day or so, then started doing it more often.
Skimp Killah said:
Are you using setcpu? Do you have a screen off profile? Are you running your phone at 1.2ghz?
I'm not sure the answer to any of those questions, so I'm assuming no. I think the MidnightROM can run the cpu faster, but you have to download some app to turn that function on or off. I'm pretty much running MidnightRom with the regular **** on it right now. I'm thinking my problem may have been using the victory8g.pit file in odin every time I flashed to a stock rom before running clock work and flashing to a custom rom. I'm running the latest midnight off a clean flash of di18 without the victory8g.pit file, so far that seem to be the only thing I can find that would cause all the custom roms to eventualy crash...
Im going on a few hours with out a crash, but the first time it took a day or so, then started doing it more often.
Click to expand...
Click to collapse
What kernel is midnight using? The reason I ask the questions I'm asking is cause not every phone can be over clocked and it causes data locks. That's what it sounds like that's happening to you. there is nothing to the pit. All the pit is mapping information nothing actually gets flashed from the pit. The full tar as that information in it so its not making any changes.
Another question I have is since you keep coming from stock are you flashing the rom twice? On the first flash wipe data, cache, dalvik and on the second flash only wipe cache, and dalvik.
Sent from my SPH-D700 using Tapatalk
I'm pretty sure Midnightnight uses the Bonsai Kernel. On the about phone section it say 2.6.32.9 for kernel version. When I did bonsai and syndicate I usually data reset 3 times and cache and dalvik or whatever, once, each time I flashed it, which was usually twice.
okay, in the phone it says Bonsai/Kernal-v3.0.0
Obviously I'm on an epic 4g. When it freezes its always when the screen is off, never during actual use. I'm not sure if that helps narrow it down. And I had an epic with a cracked screen, same freezing problems, now on a new epic, still same thing, but I assumed it was the custom roms doing it because the problem only started after that.
MidnightROM and bonsai didn't require a wipe, when I tried syndicate i wiped as per the instructions, except I did the factory reset 3 times on the second flash as well.
Skimp Killah said:
I'm pretty sure Midnightnight uses the Bonsai Kernel. On the about phone section it say 2.6.32.9 for kernel version. When I did bonsai and syndicate I usually data reset 3 times and cache and dalvik or whatever, once, each time I flashed it, which was usually twice.
Click to expand...
Click to collapse
Is the bonsia kernel oced to 1.2 ghz out the box?
Try this when you get a chance.
1) odin eb13 full tar
2) run the cwm3.0.0.6 one click
3) reboot into recovery and let the auto conversion do its thing.
4) flash your rom of choose (after wiping data, cache, dalvik 3 times)
5) let the phone boot all the way up.
6) reboot into recovery again
7) flash the rom again (after wiping cache, dalvik 3 times)
8) let the phone boot
9) install setcpu and see where your clocked at
Sent from my SPH-D700 using Tapatalk
Skimp Killah said:
okay, in the phone it says Bonsai/Kernal-v3.0.0
Obviously I'm on an epic 4g. When it freezes its always when the screen is off, never during actual use. I'm not sure if that helps narrow it down. And I had an epic with a cracked screen, same freezing problems, now on a new epic, still same thing, but I assumed it was the custom roms doing it because the problem only started after that.
MidnightROM and bonsai didn't require a wipe, when I tried syndicate i wiped as per the instructions, except I did the factory reset 3 times on the second flash as well.
Click to expand...
Click to collapse
Theres gonna be problems coming from stock cause of there back up there script performs. Follow the instructions I just posted and lets go from there
Sent from my SPH-D700 using Tapatalk
Flashed to EB13
Ran oneclick CWM 3.0.0.6
Converted.
wiped data, cache and dalvik, 3 times each
Flashed MidnightROM
it did the whole random vibrations flashing two screens thing.
removed battery and booted into recovery
wiped cache and dalvik 3 times each
flashed MidnightROM again
After the second flash it went to the intial start up screen welcoming me to the phone, that was odd, never had it do that before.
Booted to recovery again and installed market and other standard apps.
Downloaded cpu master cause im cheap,
phone is clocked at 1000
I'll let you know if i have any more problems, the whole welcoming me to the phone thing was new, ive never had it bring that screen up any of the other times i flashed a custom rom, hopefully this is a sign of good things
Skimp Killah said:
Flashed to EB13
Ran oneclick CWM 3.0.0.6
Converted.
wiped data, cache and dalvik, 3 times each
Flashed MidnightROM
it did the whole random vibrations flashing two screens thing.
removed battery and booted into recovery
wiped cache and dalvik 3 times each
flashed MidnightROM again
After the second flash it went to the intial start up screen welcoming me to the phone, that was odd, never had it do that before.
Booted to recovery again and installed market and other standard apps.
Downloaded cpu master cause im cheap,
phone is clocked at 1000
I'll let you know if i have any more problems, the whole welcoming me to the phone thing was new, ive never had it bring that screen up any of the other times i flashed a custom rom, hopefully this is a sign of good things
Click to expand...
Click to collapse
Some rom devs have that enabled while others don't. If your flashing the same rom you have been and haven't seen that before I bet your good
Fyi: setcpu is free to xda users you just need to find it as I can't post links from my phone
Sent from my SPH-D700 using Tapatalk
from midnight i flashed to cm7, then wiped installed google apps and re-booted, so far so good
gingerbread
Disclaimer:
I am new at this, I have read a lot and followed a lot of tutorials. I may not use terms correctly so please forgive me.
Problem:
I am trying to flash to MidNIGHT ROM 4.2 zip from stock eb13 on my Epic.
This is my first attempt at such a thing, i was able to successfully root my device via noobnl's instructions: http://forum.xda-developers.com/showthread.php?t=770388
I am able to get rom manager installed and give it SU rights, etc. I got the full rom from the developer’s autism awareness site which is the full package. I make a backup through rom manager and reboot into CWM recovery.
I clear the data/cache 3 times and proceed to update through the zip on sd card option and point it to the midnight rom zip.
It says it is successful, i reboot and I become stuck on the samsung loading screen, I let it sit for 10min just to make sure, but no dice.
I then boot it back into recovery mode and try again multiple times which it is much faster this time but they all fail to load past the samsung load screen.
I go into the CWM recovery and attempt to load my backup, which hangs at installing cache every time.
So I am left with just booting into CWM.
I then resort do using odin to get back to eb13 and I am back where I began.
Sorry for the wall of text but I am lost and have tried to read a lot so I didn’t come on here asking random questions, but I have been working on this for a long time now and figure a forum post was due.
It wont work with CWM 2.5 and RFS. It requires CWM 3.0 and EXT4
After you ODIN back to EB13 go here:
http://forum.xda-developers.com/showthread.php?t=897612
From the midNIGHT ROM first post:
ptfdmedic said:
Instructions:
1) Make sure you are Rooted with NEW CW3.0.0.6 OneClick by Dameon
Click to expand...
Click to collapse
I see now.
I used Rom manager to update my CWM to 3.0 and thought that would work with his first bullet, but I thought wrong.
I guess I dont understand RFS and EXT4, I thought rooting was rooting and noobnl's directions were the easiest for me to follow.
Much appreciated chris5h for the fast reply.
I will test this out when I get home from work.
-sgpigeon
kennyglass123 said:
Do you know how to Odin back to stock? Follow this thread for it:
http://forum.xda-developers.com/showthread.php?t=853209
Then when you restore, only restore data under advanced restore.
If you used Mybackup root or Titanium you can restore your apps from there, otherwise you should download them again from the market.
Click to expand...
Click to collapse
This is the easiest way I have found to root your phone with CWM3 and EXT4. If you don't mind using Odin I would suggest it strongly. I used it and installed Midnight ROM v4.2 and had no problems at all.
Well that was it. Thanks a lot everyone for your help. It took me like 10minutes once I had everything downloaded, much better than the hours upon hours yesterday
I officially have midnight ROM installed and I am rocking some nice speeds on my epic! Finally nice to see just what the phone is capable of.
Glad you got it. I wish people would stop using rom manager for the epic. It doesn't flash cwm
Sent From My Evo Killer!
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
First let me say...its been awhile since I have posted here, I love the auto search based on the title of a post lol. That is awesome. Needless to say I didn't find anything related to my issue...
Here we go,
I have had my phone rooted forever and a day. I have only ever used fresh roms since It's been rooted. ( about a week after launch ) The issue popped up about a few months or so ago with one of his updates. No matter how i tried to download or install it would always bootloop. I have done the full data, dalvic, cache wipes and got the same results. I figured *f* it and just went back to my nandroid of the old version and forgot about it.
There have been several releases that I have tried from fresh that did the same thing. I figured tonight I would try the synergy rom for something new and to see if my phone would take it. I was using clockwork mod for my recovery. I did a nandroid of my phone and away I went.
I flashed amon_ra since that is synergy's recovery of choice and went through the whole process.
3 hours later...here I am with a phone still stuck in a bootloop when i try the rom and now I learned for some reason that amon_ra nandroid restore is not compatiable with the ones from clockwork that i have on my phone. *quick edit* I have also tried downloading several other roms, and am having the same issues.....even tried redownloading the same roms several times thinking it was a corrupt download or something.
There was one restore available that took me back to what seems to be an unrooted phone. I still have access to the recovery and am able to flash roms, but all the sprint crap is back and I don;t have superuser on the phone anymore.
So there is my story. I am an old hand at flashing and know how to wipe and all that before installing and i seem stuck to use this OG sprint crap for the rest of my contract, unless one of you wonderful phone guru's can point me in the right direction.
~owl
There's a thread here with the SU 3.0
install that, go to menu in the app, make sure that permission is toggled on
HipKat said:
There's a thread here with the SU 3.0
install that, go to menu in the app, make sure that permission is toggled on
Click to expand...
Click to collapse
Well at least i can get SU back on the device...
any more advice as to why the phone is refusing to flash any rom??
Maybe try a superwipe script or wipe everything like boot and all except SD card
Sent From My Pocket
{ParanoiA} said:
Maybe try a superwipe script or wipe everything like boot and all except SD card
Sent From My Pocket
Click to expand...
Click to collapse
+1
I usually wipe everything 3 times in Amon then a superwipe zip after that.
Gotta be clean
YEah, do a wipe of everything except SDCard: and Battery stats, if you're not fully charged. Wipe Cache and Dalvik-Cache a few times each. I don't use superwipes myself, but anyhow, after that, flash a stock ROM. Make a nandroid of it, if your phone boots up fine.
Then go back, wipe everything again and flash the ROM you want to use.
I really want to thank all of you that have taken the time to post some ideas here for me, but as of right now I have had no love from my phone with any of them.
It will flash a radio just fine, flash wimax fine as well, but no love for the ROMS.
Anymore ideas out there??