Develop Bugs

[ROM]Glacier_Gingerbread_S_TMOUS_2.32.531.1[Rooted and deodexed][12-09-11]

I am be no means a dev, just ran it through kitchen rooted deodexed and zipaligned. Does not include radio and you will not lose root. No updates to this as im not a dev. Its stock mysense 2.3.4. I guess I should add im am not responsible for any damage to your phone. Currently running on mine with no issues.
Thanks to Football for the source and dsixda's Android Kitchen
New Link: http://d-h.st/l3Q
Download: http://www.multiupload.com/BE6AB9PEGG
Radio pulled by krazie1.
http://forum.xda-developers.com/showpost.php?p=20150354&postcount=10

Thank you.. downloading

Does it include the radio. Can you mention that in the first post
Thanks

Any screen shots?
Sent from my HTC Glacier using xda premium

no its stock mysense, ill upload a few

garynsa said:
Does it include the radio. Can you mention that in the first post
Thanks
Click to expand...
Click to collapse
No, it doesn't. Check the screenshots.

Anybody willing to ice cream theme it? I bet this ROM still runs pretty fast on the glacier
Sent from my HTC Glacier using xda premium

Just flashed this. Pretty neat but too laggy as a daily. Market is slow to open, same with other apps .
But thank you for taking the time to post this up
Edit: after running a fix permissions and rebooting things seem to have picked up the pace.

Wow! Thank you very much for sharing this! Btw, what radio would you recommend for this version?

this is the radio that was pulled by krazie1. http://forum.xda-developers.com/showpost.php?p=20150354&postcount=10

Installs but wont boot
Here's how I did it, tell me where I made a mistake:
Installed updated radio and then using ClockworkMod Recovery v5.0.2.0 did the following:
-wipe data/factory reset
-wipe cache partition
-advanced -Wipe Dalvik Cache
-advanced -Fix Permissions
After all that, installed glacier_signed_120911_211623.zip still using ClockworkMod Recovery. It said: Verification Failed. Toggled Verification to DISABLED and successfully installed glacier_signed_120911_211623.zip
Now, it starts to boot and just hangs there until I take the battery out.
HELP!!!

Sounds like a bad download, try an redownload. It takes a while to boot.

Alright, Ill try to download it again.... server is so slooooow tho oh and btw, I already have S-OFF, just in case if it makes a difference

its been downloaded almost 500 times and no else said anything. i bet its a bad download

Works well, no issues except for Sense crashing every once in awhile. Did you get the 9.4 Mb/s download on this ROM? if not, what were your build.prop settings? I live in Houston, and the highest I have gotten on CM was 6.5 Mb/s, and that was with build.prop ro.ril setting changed. I was going to try and remove some of the HTC logging stuff, have you tried already?

cant remeber the rom but i was probly 100ft from tower im guessing. every time im on that road it his 9mb

Works well
Sent from my LG-P999

just a quick question, we flash the zip and flash the radio zip over after that?
thank you

Flash the radio through hboot

thank you very much, got it all thru
its kinda nice to go back to stock after awhile using other rom,
you know any % battery mod for the stock 1?

Onandroid- Make backups without booting into recovery

I have not tried this yet, but the E4GT is listed under supported devices so here's the linkhttp://forum.xda-developers.com/showthread.php?t=1620255
This could be a very useful tool for us if it works, with our recovery situation... Anybody who uses it please report back and let us know how it works. I just saw this and thought I'd pass it on for somebody with the free time to try it out.

Bump

Looks Kool, dont know when, but ill check it for sure. Shadow_God had a post for something similar, months ago, and I didnt try it. Wont make that mistake again. Thanks RB

bilgerryan said:
I have not tried this yet, but the E4GT is listed under supported devices so here's the linkhttp://forum.xda-developers.com/showthread.php?t=1620255
This could be a very useful tool for us if it works, with our recovery situation... Anybody who uses it please report back and let us know how it works. I just saw this and thought I'd pass it on for somebody with the free time to try it out.
Click to expand...
Click to collapse
I'm testing this now so far;
I downloaded zip file
booted into el29 direct recovery
flashed zip
rebooted
opened Rom toolbox pro
opened terminal emulator
typed su
typed onandroid and it started the backup
will have screenshots when it finished

Screenshots it completed the backup going to reboot and see if it will restore.
Did not restore because I DID NOT SEE THAT THE BOOT IMAGE AND RECOVERY WAS NOT DETECTED ON MY PHONE!!!. If you go to the link posted above by bilgerryan you can download a zip SPECIFIC to your phone that will detect both.
This is where I found the zip for our phones: https://github.com/ameer1234567890/OnlineNandroid/wiki/Supported-Devices
Sent from my SPH-D710 using xda premium

New screenshots this time with boot image and recovery backed up
That failed to restore boot image..going to post in that thread to see what I may be doing wrong
Sent from my SPH-D710 using xda premium

This app works fine on my SGS2. It also works on my friend's SGS3.
GIGZ1971 said:
Screenshots it completed the backup going to reboot and see if it will restore.
Did not restore because I DID NOT SEE THAT THE BOOT IMAGE AND RECOVERY WAS NOT DETECTED ON MY PHONE!!!. If you go to the link posted above by bilgerryan you can download a zip SPECIFIC to your phone that will detect both.
This is where I found the zip for our phones: https://github.com/ameer1234567890/OnlineNandroid/wiki/Supported-Devices
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Both BOOT and RECOVERY get unmounted when the OS loads, so without the appropriate Samsung patch, it's not going to find them; however, with the patch, it just makes an IMG of the BOOT and RECOVERY partitions rather than try to TAR the files contained therein.

egingell said:
This app works fine on my SGS2. It also works on my friend's SGS3.
Both BOOT and RECOVERY get unmounted when the OS loads, so without the appropriate Samsung patch, it's not going to find them; however, with the patch, it just makes an IMG of the BOOT and RECOVERY partitions rather than try to TAR the files contained therein.
Click to expand...
Click to collapse
What does that mean, that it will not restore or im doing something wrong? I did download the patch and applied it. Still didn't restore. I wasn't stating that it didn't work just thatvI could not get it to restore the backup I made
Sent from my SPH-D710 using xda premium

GIGZ1971 said:
What does that mean, that it will not restore or im doing something wrong? I did download the patch and applied it. Still didn't restore. I wasn't stating that it didn't work just thatvI could not get it to restore the backup I made
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Onandroid doesn't restore. It only backs up. That said, if you're looking for troubleshooting help, you need to supply more information (e.g. error messages... CWM or TWRP? What version? Whose recovery?).

egingell said:
Onandroid doesn't restore. It only backs up. That said, if you're looking for troubleshooting help, you need to supply more information (e.g. error messages... CWM or TWRP? What version? Whose recovery?).
Click to expand...
Click to collapse
Thanks for the reply. Are they working on a restore feature. This is a really cool app and it does work for me just didnt know it doesn't restore.
Recovery: CWM 5.0.2.7 el26
Error message: was not able to flash boot image
Sent from my SPH-D710 using xda premium

*bumping* an only few-months' old thread. I may have fooled with this script briefly on my HTC Droid Eris, but forgot about it until not too long ago.
Over the last few days, the author of the script diagnosed a problem with the patch for the SCH-D710 which caused boot/recovery not to be backed up (again, I suppose). Over time he worked out the issue, fixed it and I just wanted to report that it's working 100% (I tested a restore, too) with Agat63's v1.42F kernel at this time.
I want to donate but there is no way to donate to him, so he has an eBay wish list I plan on taking a look at.
It's great to be able to backup anytime without going to recovery.
Great customer service, too!
Sent from my Sprint (Page Plus) Samsung Galaxy S2 / Epic 4G Touch using Tapatalk on Re-Calked in Jellybean ROM v1.2 Jellybean 4.1.2, Agat63's v1.42F Kernel+CrossBreeder v6.26 v2 and SwiftKey keyboard.

roirraW "edor" ehT said:
*bumping* an only few-months' old thread. I may have fooled with this script briefly on my HTC Droid Eris, but forgot about it until not too long ago.
Over the last few days, the author of the script diagnosed a problem with the patch for the SCH-D710 which caused boot/recovery not to be backed up (again, I suppose). Over time he worked out the issue, fixed it and I just wanted to report that it's working 100% (I tested a restore, too) with Agat63's v1.42F kernel at this time.
I want to donate but there is no way to donate to him, so he has an eBay wish list I plan on taking a look at.
It's great to be able to backup anytime without going to recovery.
Great customer service, too!
Sent from my Sprint (Page Plus) Samsung Galaxy S2 / Epic 4G Touch using Tapatalk on Re-Calked in Jellybean ROM v1.2 Jellybean 4.1.2, Agat63's v1.42F Kernel+CrossBreeder v6.26 v2 and SwiftKey keyboard.
Click to expand...
Click to collapse
Did you try this on AOSP? Or just touchwiz?

If it works on TouchWiz I see no reason it wouldn't on AOSP

I had used it on AOSP before, although I was having it use the TWRP backup then and it worked great then too.
Recently, I've only been running TW though.
Sent from my Sprint (Page Plus) Samsung Galaxy S2 / Epic 4G Touch using Tapatalk on Re-Calked in Jellybean ROM v1.2 Jellybean 4.1.2, Agat63's v1.42F Kernel+CrossBreeder v6.26 v2 and SwiftKey keyboard.

[Q] Quantum Rom issues

Well, I don't know if this is how I'm supposed to go about doing this, but I've been having issues recently with Quantum rom, and was planning on posting them in the actual Quantum thread, but I need 10 posts to do that because 10 posts mean something important.
Anyways, Ive been fine previously just doing
1. Wipe Dalvik, cache, and system,
2. flashing rom and gapps
3. the wipe option you get after you flash (TWRP)
Ive been doing that since i started basically, until 1.9. Anything after 1.9, it either constantly crashes, has processes constantly stopping, or on one of the versions (2.1 i think) the screen would constantly flicker (which someone else mentioned happening in the thread). So i figured I should try a clean flash, so I try wiping everything and flashing, and doing the default factory reset option and flashing, neither of which helped. In fact, after doing the clean flash it made 1.9 stop working too, so I had to restore my 1.9 backup to get it working again.
Anywho, if anyone has any advice that could help me get the newer versions working that would be great, Thanks!
EDIT: I might try flashing a different rom, to see if the issues persist elsewhere, but firstly Id like to stay on Quantum, and secondly, iirc I tried one a different rom when 4.3 first started showing up in roms, and I kept having problems, to which I just went back to Quantum.

It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk

codemonkey98 said:
It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
Click to expand...
Click to collapse
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow

DanCardin said:
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow
Click to expand...
Click to collapse
Could be your recovery too. I believe the Quantum ROM developer recommends CWM than TWRP.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

If you do decide to change to CWM, make sure you revert to your TouchWiz backup first since TWRP and CWM backups aren't compatible. My best recommendation is to re-download the newest version (2.35 as of 11/7/13), and wipe data/factory reset, wipe /cache, wipe system, wipe dalvik cache, then install ROM and Gapps, wipe cache and dalvik again, and reboot.

iirc, i noticed a fair enough number of people on TWRP that I would prefer to stay on it (since it *should* work). I did, however just update it, tried again. For 2.31, i just get constant for closes on phone and SystemUI, and others iirc. Im trying carbonRom right now, and its working perfectly fine.
EDIT: I did get one SystemUI force close, on it, but its literally constant on quantum sadly.

also tried a couple random other roms, all work, but no Quantum rom will work after 1.9. I also tried just flashing it and not gapps, and i end up with the same thing. Now its just constant force closes though. I don't think i remember seeing any flickery screens like i was getting around 2.1X i think it was.

What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app

android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think that the leaked 4.3 bootloader (whatever end code they gave it) isn't necessary yet, since it hasn't been officially released by AT&T. I'm personally holding off on flashing any 4.4 rom until they're a bit more mature and don't have as many hiccups (although pwncake's work is superb). The UV depends on your device and how it handles it, usually, mine needs +25 than stock but it doesn't seem to shorten battery life. All throughout 4.3, it was best to keep MP-Decision off since he built one into the rom. In the case of 4.4, IIRC from Quantum v3 beta3 and forward, he removed his own MP- Decision, so you could keep it switched on.

android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.

Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)

DanCardin said:
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.
Click to expand...
Click to collapse
Can't run Quantum either. Same boat. I think it's an issue with the Core kernel and Rev0 processors.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things

DanCardin said:
I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things
Click to expand...
Click to collapse
I get the same thing...

supahdaniel said:
I get the same thing...
Click to expand...
Click to collapse
sorry to hear of your problems. it is not the rom. enough folks are running it and I have had flawless installs. Read the OP and follow the directions, it works.
there is a new TWRP (from their site) that I downloaded as a .tar file and flashed with odin. flashes 4.4 roms now so you might try that rout.
my suggestion, in its limited knowledge is this:
put the rom, superuser, and the gapps on your SD card.
Reboot into the new TWRP and format the system- your phone is now blank.
install rom zip
install superuser zip
reboot.
first boot may take a bit, but not forever. Set up CM stuff and go from there
---------- Post added at 12:29 PM ---------- Previous post was at 12:17 PM ----------
Demminex said:
Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)
Click to expand...
Click to collapse
search the quantum thread about google settings. you have to turn on google now and disable notifications. also, I've been using the swift keyboard and don't have to deal with the google or android keyboard. that seems to have helped.
enable art after loading apps and be prepared for a wait for android to upgrade.

[Q] Bootloop - Only boots right after cache/dalvik wipe - Kindle Fire CM10.2 20131206

If I boot into recovery, wipe cache and dalvik (I fix permissions too, although this probably isn't necessary), then it boots right up like nothing is wrong with no fanfare.
If I'm lucky, this will even persist for an additional reboot. Otherwise on subsequent reboots it just bootloops forever until I go back to recovery and wipe cache/dalvik again, and then it boots right up again. Once into the ROM, everything runs fine, no issues at all.
I've tried rolling back a nightly or two but it doesn't seem to make a difference. Was there some major change in the last few weeks that I missed? How far do I need to roll back to get this to work?
It's my gf's tablet so I don't really want to wipe data if I can avoid it. Was even thinking of dirty flashing up to CM11.
Any insight is appreciated.

With my phone this problem ended up being using the wrong baseband version for the ROM/kernel that I was using. I was able to fix it by resetting it back to stock using ODIN (tool which can be used to recover Samsung devices) but from the sounds of it you have no such luxury.
Do you have any backups of when everything worked? If not try to find a way to get back to stock however you can. Aside from that make sure that you are using the correct ROM for your hardware.
Good luck and keep us updated.

czahrien said:
With my phone this problem ended up being using the wrong baseband version for the ROM/kernel that I was using. I was able to fix it by resetting it back to stock using ODIN (tool which can be used to recover Samsung devices) but from the sounds of it you have no such luxury.
Do you have any backups of when everything worked? If not try to find a way to get back to stock however you can. Aside from that make sure that you are using the correct ROM for your hardware.
Good luck and keep us updated.
Click to expand...
Click to collapse
The kindle is wifi only, so I don't think there are any baseband issues. Will update when/if I fix it.
Restoring to stock is a good idea. It's been over a year since this thing was stock, so it's quite possible we missed a firmware update or something.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Mine does this after I installed the new sgt7 4.4.2 rom. Did you end up fixing yours?

whatever100 said:
Mine does this after I installed the new sgt7 4.4.2 rom. Did you end up fixing yours?
Click to expand...
Click to collapse
Not yet, but I think it worked fine on cm10.2 for awhile.
Sent from my Nexus 5 using XDA Premium 4 mobile app

UPDATE - I dirty flashed cm11 and gapps as if I were updating any other nightly, and the issue appears to be gone. So freaking annoying, lol.

[URGANT HELP] Flashed CM 4.4, bootloops?

So, I'll tell the story like it is:
I have a Samsung Galaxy Note 2 from At&t. I was on a touchwiz rom, and like most everybody, the lag became unbearable. So, like the other countless times before, I downloaded the Kitkat port for Cyanogenmod. All was well and I transferred it, along with the right gapps onto my phone, went into the recovery and flashed it after wiping user data, cache, and dalvik cache. I booted it and experienced bootloop. I went back into my recovery, CWM at the time, and factory data reset it and rebooted. Bootloop persisted. Baffled, I put re flashed my old touchwiz rom and loaded CM Installer on it, installed through that service and all was well. When it booted I found out that it was an RC build of 4.3, not what I wanted. I then downloaded countess other 4.4 roms like Packman and Illusion as well as Omin, none booted successfully. I then searched on XDA for a bit and found that some older versions of CWM recovery were not compatible. So I downloaded the latest version and flashed through Odin. Tried all 4 of the previously named ROMS again and yet bootloops continue to happen. I've flashed roms before and this has never happened! What am I doing wrong?

abdullaha said:
So, I'll tell the story like it is:
I have a Samsung Galaxy Note 2 from At&t. I was on a touchwiz rom, and like most everybody, the lag became unbearable. So, like the other countless times before, I downloaded the Kitkat port for Cyanogenmod. All was well and I transferred it, along with the right gapps onto my phone, went into the recovery and flashed it after wiping user data, cache, and dalvik cache. I booted it and experienced bootloop. I went back into my recovery, CWM at the time, and factory data reset it and rebooted. Bootloop persisted. Baffled, I put re flashed my old touchwiz rom and loaded CM Installer on it, installed through that service and all was well. When it booted I found out that it was an RC build of 4.3, not what I wanted. I then downloaded countess other 4.4 roms like Packman and Illusion as well as Omin, none booted successfully. I then searched on XDA for a bit and found that some older versions of CWM recovery were not compatible. So I downloaded the latest version and flashed through Odin. Tried all 4 of the previously named ROMS again and yet bootloops continue to happen. I've flashed roms before and this has never happened! What am I doing wrong?
Click to expand...
Click to collapse
Have you tried another 4.3 ROM like
this
http://forum.xda-developers.com/showthread.php?t=2589891 or
this
http://forum.xda-developers.com/showthread.php?t=2704375
Sounds like you got wood for a 4.4 ROM. So was the latest version of TWRP 2.7.X.X? Assuming it is since it's listed right by the OMNIROM....
Are you waiting maybe up to 5-7 minutes to let it boot ? You've been beating the bejesus out of it.
Honestly I would flash one of the above and run it for a day. Then go back to flashing. Get it running stable again on stock.
That's just me.... I'm hoping that works for you after all you've thrown at it.

dicksteele said:
Have you tried another 4.3 ROM like
this
http://forum.xda-developers.com/showthread.php?t=2589891 or
this
http://forum.xda-developers.com/showthread.php?t=2704375
Sounds like you got wood for a 4.4 ROM. So was the latest version of TWRP 2.7.X.X? Assuming it is since it's listed right by the OMNIROM....
Are you waiting maybe up to 5-7 minutes to let it boot ? You've been beating the bejesus out of it.
Honestly I would flash one of the above and run it for a day. Then go back to flashing. Get it running stable again on stock.
That's just me.... I'm hoping that works for you after all you've thrown at it.
Click to expand...
Click to collapse
I thank you for your suggesion but other than what you have said, do you have any other ideas on what I'm doing wrong?

abdullaha said:
I thank you for your suggesion but other than what you have said, do you have any other ideas on what I'm doing wrong?
Click to expand...
Click to collapse
Not a clue.... Sounds like everything is good. I don't think you're doing anything wrong operational. Your phone just ain't happy.
I think it wants what it wants. And it's appearing it's not a 4.4 ROM at the moment.
That's what it's looking and sounding like to me.

abdullaha said:
So, I'll tell the story like it is:
I have a Samsung Galaxy Note 2 from At&t. I was on a touchwiz rom, and like most everybody, the lag became unbearable. So, like the other countless times before, I downloaded the Kitkat port for Cyanogenmod. All was well and I transferred it, along with the right gapps onto my phone, went into the recovery and flashed it after wiping user data, cache, and dalvik cache. I booted it and experienced bootloop. I went back into my recovery, CWM at the time, and factory data reset it and rebooted. Bootloop persisted. Baffled, I put re flashed my old touchwiz rom and loaded CM Installer on it, installed through that service and all was well. When it booted I found out that it was an RC build of 4.3, not what I wanted. I then downloaded countess other 4.4 roms like Packman and Illusion as well as Omin, none booted successfully. I then searched on XDA for a bit and found that some older versions of CWM recovery were not compatible. So I downloaded the latest version and flashed through Odin. Tried all 4 of the previously named ROMS again and yet bootloops continue to happen. I've flashed roms before and this has never happened! What am I doing wrong?
Click to expand...
Click to collapse
Are you sure that you have a kernel that support cm ROM? Just curious.
Sent from my GT-N7100 using XDA Premium 4 mobile app

Format system with your other wipes.

What he ^^^^ said. You probably have so many fragments, wipe system three times.

And internal storage wipe may be needed as well...
But MAKE SURE you have a full backup of a complete and working rom BEFORE wiping....just in case...g
Sent from my SGH-I317 using XDA Premium 4 mobile app

dicksteele said:
Have you tried another 4.3 ROM like
this
http://forum.xda-developers.com/showthread.php?t=2589891 or
this
http://forum.xda-developers.com/showthread.php?t=2704375
Sounds like you got wood for a 4.4 ROM. So was the latest version of TWRP 2.7.X.X? Assuming it is since it's listed right by the OMNIROM....
Are you waiting maybe up to 5-7 minutes to let it boot ? You've been beating the bejesus out of it.
Honestly I would flash one of the above and run it for a day. Then go back to flashing. Get it running stable again on stock.
That's just me.... I'm hoping that works for you after all you've thrown at it.
Click to expand...
Click to collapse
Thank you! You were right! I switched back to stock and rerooted and redid the flashing and it worked like a charm! I have no idea why it didn't work the first time. Thank you for your help.
Sent from my T0LTE using XDA Premium 4 mobile app

abdullaha said:
Thank you! You were right! I switched back to stock and rerooted and redid the flashing and it worked like a charm! I have no idea why it didn't work the first time. Thank you for your help.
Sent from my T0LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Glad it worked. These phones are tanks, hard to crush them. But they will let you know when they are not happy with what you did.