Develop Bugs

[Q] Custom Roms freezing, Midnight, Syndicate, Bonsai.

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

[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.

[Q] Can't boot past boot screen after botched ICS theme transition installation.

I was running Starburst v1.9 and saw a thread on Themes & Apps with ICS transitions. I downloaded both just in case (ICS Transitions & Revert back to stock). I went into Root Explorer and checked my Clockwork/Backup and saw that I had a backup in there. I booted into Recovery and flashed the theme transitions for ICS zip and thus problem began.
I then went to restore to restore the backup and it seems like that file was corrupted because it wouldn't restore. I ended up flashing the revert zip file and wiping my rom. It doesn't boot but I can still get into recovery. I believe that the issue is that the theme was made for the v1.9.5 and I had v1.9 of Starburst.
I was messing around with it and I was able to boot back in and click on the Android to set it up. After a while the phone will go crazy and the screen will flicker on and off. The buttons at the bottom became useless. How can I recover from this.
** I used my friend's Sensation and downloaded v.1.9.5 and threw it on my SD. I booted into Recovery and flashed the ROM and it still won't boot up. Any suggestions? **
The phone booting up I think was a luck of the draw thing. Since then the phone has not been able to boot into the actual ROM. I've been without a phone since yesterday and I'm planning on going into the Sprint store and getting it swapped.

Did you wipe system, data, cache, and dalvik?
THEN reflash the rom?

Yes. I was a flashaholic on my Evo.
I notice another thread in q&a with people the same issue as mines. I'm lost and haven't had my phone working for two days now.
Here's what I did:
Delete system, wipe factory reset, cache and dalvik, flashed ROM.
Could it be kernel related? I'm confused. I have a wedding tomorrow and this couldn't have happened at a worse time. Coincidentally something happened on my At&t dumb phone so I'm phoneless.

stupid suggestion...is your battery low?
with the evo it would see corrupted if the battery was low. may not apply, but hey its a shot.
if you cant figure out, theres always Odin to cure your issues

ReDL the ROM and reflash. Try mounting USB storage while in recovery. Alternatively, Odin the stock .tar for a full refresh.

If you've already retired reflashing I'd go with odin back to stock
Sent from my SPH-D710 using xda premium

here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here

playya said:
here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here
Click to expand...
Click to collapse
Awesome. The wedding made me forget about my phone but now that it's over I'm missing it.
I will flash to stock and re-root.
Sent from my Nexus S 4G using XDA App

[Q] I am really stupid at this stuff, I need your help

Before I get ravaged, I have wandered from thread to thread to thread trying to find answers and unfortunately, everyone's got a different situation, so I'll try and sum it up here.
I have an Epic 4G that I threw the Samsung/Sprint Froyo ROM on as soon as it as available, after which I rooted it, installed CWM 2.5 and called it a day. I've been wanting to upgrade to Gingerbread, but the official EI22 ROM is obviously giving me issues because of root, so I decide, hey, I can try adding on some other ROMs and finally get into this thing.
Now somewhere amongst all this, I have CWM 5.0 installed and my phone is running both older and newer versions and only 5.0 is letting me restore in case I screw up.
So I grab the Gingerbread restore and after wiping my data, restore it. Gets stuck on Samsung logo. Try this a few times, give up, reload my original Froyo image (only after coaxing CWM to load up 5.0 instead of 2.5). Try again tonight with ACS ICS ROM and 2.5, still stuck at Samsung logo. Wipe and try again, same thing.
So my question is: A) would it be better to go back to Odin and try again despite a stable Froyo image, B) how can I eliminate one of these CWMs, C) has anyone else had these issues?

seems like you did a whole bunch of things... probably best to start clean.. odin to stock froyo. then you probably want to root it from there. after that, you can flash the latest cwm, then latest gingerbread rom
when you installed cwm5, did u flash through rom manager or through recovery?

I honestly just downloaded CWM from Marketplace and I found out how I was able to access it: it's a zip in my Clockwork folder. Once I "install" that, it loads into 5.0 and that's how I've been able to work, but it never updates CWM, I have to keep having to boot into it from the zip.

well u have cwm2,5 u said... try booting into cw, (three fingers) and flash the zip. but maybe you can try downloading cwm from the official cwm thread and flash that zip just to be sure
http://forum.xda-developers.com/showthread.php?t=1357655

Yeah, every time I try to flash that ZIP, it just opens up 5.0 instead. I'll have to try doing it from scratch.

isnt that what u want??? 5.x.x.x??

EpicNewb4g said:
isnt that what u want??? 5.x.x.x??
Click to expand...
Click to collapse
Yeah, definitely.

Okay, Odin'ed back to stock Froyo and rooted, loaded on ACS Recovery. This whole process has killed my battery, so I'm going to recharge before trying to load up a new ROM. It seems like it should be easy from here on out...

You should just start over with a fresh install.
Here are the steps. I made this list before CWM 5 was released, but you can get the CWM 5 ODIN .tar file from that thread which was linked a few posts up.
http://forum.xda-developers.com/showpost.php?p=19444784&postcount=93

Yeah I ODINed back with ACS Recovery and now I'm running ACS ICS, which is sooooooo awesome. I think I was afraid about having to ODIN back to stock and losing everything. Now I should still have the Froyo image on there, can't I just run between this new one and that?
Thanks, all!

What do you mean by you have acs ics and still have the froyo image?? are you dual booting

Acs ics = rom.

EpicNewb4g said:
What do you mean by you have acs ics and still have the froyo image?? are you dual booting
Click to expand...
Click to collapse
Does he mean the wallpaper?

BLAZER ROM Install Issues...help?

I just decided last night to switch from Calkulin to Blazer so I could try it out.
The results were disastrous.
I took my phone, which was running on Rogue Desperado Kernel, EL29 Modem, Calk 2.8.1, and backed up everything. Then I booted into ROGUE recovery, and flashed CALKS FORMAT ALL. This was a success.
Then I flashed BLAZER ROM 3.7. This was a success, according to my little black and green screen.
**HOWEVER, upon reboot I was stuck at SAMSUNG GALAXY S II screen. I waited...and waited...and waited. It never moved past this screen.
Then I tried booting into recovery - no dice. I had to download the Stock EL29 Kernel/Modem/ROM ODIN Full Restore and flash everything back to square one.
Once this was completed, I rooted using the Auto Rooter and took my phone to EL29 with CWM. Then I flashed my Kernel over to the stock EL29 with Rogue Kernel (this is easier to use than stock CWM IMO).
FINALLY, I booted into recovery, flashed CALK FORMAT ALL, then flashed BLAZER ROM 3.7. Now I'm back to the ** from earlier in this post - SAMSUNG GALAXY SII is on the screen, and I can't get past it or boot into recovery.
I'm going to run through the steps again to bring my phone back to stock, but I'd really like to try this ROM out. Does anyone have any ideas?
Any help is greatly appreciated.

With no background information, it sounds like it may have been a bad download. Have you tried downloading another copy of Blazer rom?
The process you described was correct, and sometimes bad downloads lead to infinite splash screens.

jyaworski said:
With no background information, it sounds like it may have been a bad download. Have you tried downloading another copy of Blazer rom?
The process you described was correct, and sometimes bad downloads lead to infinite splash screens.
Click to expand...
Click to collapse
+1. Definitely sounds like a bad download

jyaworski said:
With no background information, it sounds like it may have been a bad download. Have you tried downloading another copy of Blazer rom?
The process you described was correct, and sometimes bad downloads lead to infinite splash screens.
Click to expand...
Click to collapse
OK it looks like you correct. I re-installed Calk 2.8.1 with no issues and did a restore through Titanium. I then got a message saying "download incomplete" of BLAZER ROM. It's odd, because the download went through fine yesterday and the notification cleared before I booted into Recovery to flash everything.
Now I'm trying to re-download the ROM and the link is down with no mirror. Does anyone have a copy saved that they can create a mirror with?

webbiam said:
I just decided last night to switch from Calkulin to Blazer so I could try it out.
The results were disastrous.
I took my phone, which was running on Rogue Desperado Kernel, EL29 Modem, Calk 2.8.1, and backed up everything. Then I booted into ROGUE recovery, and flashed CALKS FORMAT ALL. This was a success.
Then I flashed BLAZER ROM 3.7. This was a success, according to my little black and green screen.
**HOWEVER, upon reboot I was stuck at SAMSUNG GALAXY S II screen. I waited...and waited...and waited. It never moved past this screen.
Then I tried booting into recovery - no dice. I had to download the Stock EL29 Kernel/Modem/ROM ODIN Full Restore and flash everything back to square one.
Once this was completed, I rooted using the Auto Rooter and took my phone to EL29 with CWM. Then I flashed my Kernel over to the stock EL29 with Rogue Kernel (this is easier to use than stock CWM IMO).
FINALLY, I booted into recovery, flashed CALK FORMAT ALL, then flashed BLAZER ROM 3.7. Now I'm back to the ** from earlier in this post - SAMSUNG GALAXY SII is on the screen, and I can't get past it or boot into recovery.
I'm going to run through the steps again to bring my phone back to stock, but I'd really like to try this ROM out. Does anyone have any ideas?
Any help is greatly appreciated.
Click to expand...
Click to collapse
The EXACT same thing happened to me and I did the same as the OP. I followed the instructions, I thought, verbatim. I'm not a newb when it comes to flashing, I've been doing this for years. Stupid me, I flashed a ROM and locked up the phone for a few hours until I got home from work. The only thing that brought it back was Odin to stock and start all over. The only roms that work for me are cal's rooted stocks, his custom roms and strong Steve's Smurf love ROM. Such is life.

was trying to download the new blazer rom and seems the link is broken so will try later.

PhantomHacker is having issues with his host (see quote below), I'm sure he'll have it handled asap. Blazer ROM is awesome, hope you guys enjoy once he gets it back up and running.
PhantomHacker said:
Having problems with my host... -_- Working on getting this back up.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse

Im not sure if you are or not but if you are trying to download the rom from your phone that is the first mistake. I have had allot of bad luck doing it this way. Always download it from the computer and never transfer it through Kies air always use a usb cable. I cannot tell you how much trouble I have run into when trying to download from the phone or transfer roms/themes wireless.

PH's site is back. Download to PC

OK I'm all good. Someone posted a mirror last night for the Blazer Rom (nibrwr notes that PhantomHacker's site is back up today for anyone else trying to download) and I downloaded it on my phone.
rbtrucking - I know you mentioned to always download on PC and transfer, but I've had almost no issues with the downloads direct to the phone. I did all of the Calk install when I first rooted this way, and the Blazer issue was probably my own fault, I must have ended the download before the file finished and then tried to Flash it.
I downloaded the full Blazer Rom on my phone directly yesterday and flashed it in Recovery and it worked fine.
Everything is working perfectly, and I've got it overclocked to 1.35GHZ. Stable as all hell and pulling over 5,000 on Quadrant, whatever the hell that test is good for.
Thanks for the help everyone.