Has anyone flashed the Omega I9505 Rom on the M919. I did flash it a few weeks ago and it worked great. Used it for two weeks, then flashed a Google Edition Rom and soft bricked my phone.
I am not sure if the soft brick was due to, but I am hesitant to re-flash Omega rom since I have read that I should not be flashing other roms not designed for M919.
Just have the itch to go back, Omega rom ran really smooth and I feel that the phone ran the best on it.
I am just hesitant because I don't want to brick my phone, Soft or not; it is still very scary.
re: flashing roms
dss4me3 said:
Has anyone flashed the Omega I9505 Rom on the M919. I did flash it a few weeks ago and it worked great. Used it for two weeks, then flashed a Google Edition Rom and soft bricked my phone.
I am not sure if the soft brick was due to, but I am hesitant to re-flash Omega rom since I have read that I should not be flashing other roms not designed for M919.
Just have the itch to go back, Omega rom ran really smooth and I feel that the phone ran the best on it.
I am just hesitant because I don't want to brick my phone, Soft or not; it is still very scary.
Click to expand...
Click to collapse
Going back to Omega rom will NOT brick your phone.
Just be 100% sure to do a full wipe in cwm/twrp recovery before flashing any roms.
Complete full wipe includes wipe system, data, cache, dalvik cache and factory reset.
If you don't wipe all of the above you will have at least a 50% chance of bootlooping and or getting stuck
on boot screen and you will need to start all over again.
Omega rom is good but you will loose wifi calling unless you flash a rom specifically for the samsung M919 phone.
I would suggest the Wicked v7 custom rom it has all the bells and whistles including wifi calling and call recording.
Good luck!
Related
Having trouble with all touchwiz roms, I can flssh a Touchwiz rom completely fine and boot jo problem, runs amazing but as soon as I reboot the device it hangs at the s4 boot logo screen and the ojly wwybto get out of the boot loop is to complete wipe and flash over again, I dont have this problem on any aosp roms. If anyone can help id greatly appreciate it , currently running the late stack wicked s4 rom with ktoonsez kernel, scared to death to reboot lol
Sent from my S4 (AKA The baddest of the bad)
re: clean start
CodenameRondo said:
Having trouble with all touchwiz roms, I can flssh a Touchwiz rom completely fine and boot jo problem, runs amazing but as soon as I reboot the device it hangs at the s4 boot logo screen and the ojly wwybto get out of the boot loop is to complete wipe and flash over again, I dont have this problem on any aosp roms. If anyone can help id greatly appreciate it , currently running the late stack wicked s4 rom with ktoonsez kernel, scared to death to reboot lol
Sent from my S4 (AKA The baddest of the bad)
Click to expand...
Click to collapse
To me it looks like it's time for your phone to get a fresh clean start.
Why not Odin flash back to stock firmware and go from there.
Afterwards you can root the phone and flash one of the excellent custom Touchwiz roms.
It's best if before you Odin flash the stock rom to be sure to do a factory reset,
wipe cache, wipe dalvik cache in the phone.
Here is the link to the Samsung Touchwiz Jellybean 4.2.2 MDL M919 stock rom: http://k0nane.info/rom/M919UVUAMDL_M919TMBAMDL_TMB.zip
Good luck!
Actually thought about doing this, I just wish I knew what the problem was
Sent from my S4 (AKA The baddest of the bad)
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Wipe
Data
Cache
Delvik Cache
and Factory Reset.
Make sure you're flashing the correct GApps for android 4.2.x
Flashing a kernel has nothing to do with a status 7 error.
A status 7 error points to a outdated recovery or bootloader.
You should get ANY errors.
If you hate flashing why do it??
I honestly don't get that...
If you're here to make your phone to look "cool" you're in the wrong place.
Galaxy S3 / AoCP / V4A / Turbocharged
duoblade said:
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Click to expand...
Click to collapse
I would get TWRP recovery.. wipe dalvik / factory reset. and re-flash your rom.. I'm on Rogers as well and the status 7 error means that your recovery / bootloader is outdated.
So start by getting the most recent TWRP. I got it from goo.
btw: if you don't like custom rom, i suggest going to the sammobile site and getting your factory firmware. Use Odin to reflash back to stock. That should solve your hiatus towards custom roms...
correction
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
duoblade said:
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
Click to expand...
Click to collapse
sure but its fine custom Roms can be a Pain in the A$$ thats why am running stock rooted stable, great battery life, fast like custom roms, everything is perfect give a try with stock rooted no issues or problems like custom roms
Synergy Rom 4.1.2 w/ Ziggy Kernel using ATT Galaxy S3
HAPPY ROOTIN :cyclops:
Hi there, I am not new to installing Roms in any way but I accidentally installed a d2lte Liquid smooth ROM instead of what my phone is, a d2att. So when installing the above ROM I did everything what I was supposed to do (clean install, format system). However, whenever I go on any ROM (Such as Quantum or Omni) I get an error as soon as it boots up, and my signal keeps turning on and off. I wiped data, cache and dalvik twice and go to a new ROM and the problem persists. For some odd reason, Carbon ROM works but I need a different one due to battery drain. I've never experienced this problem ever and I was hoping someone could please help me out?
Have you tried re-flashing the modem?
audit13 said:
Have you tried re-flashing the modem?
Click to expand...
Click to collapse
Yes i tried that earlier but still no luck. It's weird though how there was no problem on carbon rom and yet there was a problem when i went back to the Quantum Rom. Something happened on the LiquidSmooth Rom but i don't know what. I will again try reflashing the modem though thank you.
EDIT: Re-flashing modem did not help
Is it possible to use Odin to get back to a completely stock rom? If you have a 4.3 bootloader, you can't use Odin to flash a stock ROM.
A way to get back to a stock ROM for those on the MJB bootloader has been provided by enewman17. See AT&T I747 UCUEMJB Stock Restore in the development forum.
At a bit of a loss here. I have here a d2att/I747 that was working up until today on PAC-Rom, then I decided to wipe it clean and install a Touchwiz ROM. I tried S3RX, I tried a supposed Note V port, hell, I'm trying stock. None of them will finish booting. S3RX and the Note V port give me a perpetual boot logo, stock gets past the Samsung logo, plays the sound, then gets stuck at the AT&T logo. I've given each one at least an hour to do something, and they're apparently not going anywhere.
I've tried everything I know how to do; I've wiped EVERYTHING (system, data, internal storage, formatted data, the whole shebang) and nothing seems to make a difference. It's on NJ2 and I even just tried reflashing the NJ2 bootloader/modem, but that doesn't seem to have done anything either. Totally at a loss here. What could be causing this? I mean, it boots into download/recovery fine and always -starts- booting the roms, but never finishes. Could I have a corrupted partition or something?
EDIT: Oh, so I put PAC back on it and it boots again. So yeah, this seems specific to TW roms. I don't get it.
which recovery/version do you have ?
are the touchwiz roms the same android version as the pac-rom version ?
checked the touchwiz md5 to make sure has not been bad downloads ? (i know , far-fetched for them all to be bad DLs. just a thought).
"err on the side of kindness"
First off when you went from CM/AOSP based ROM to TW did you wipe everything but external storage? When going from CM/AOSP to TW & vice versa you MUST wipe internal storage. If you do this & it still fails to boot you'll need to flash the stock recovery wipe with it & install stock. Then Odin TWRP & you're good to go.
You can get the stock recovery from enewman17's NE4 thread.
Just be sure to do your research. d2att is the easiest of all d2's to hard brick thanks to At&t not releasing full firmwares.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Flashable AT&T Galaxy S3 NJ2 Stock Recovery Zip (Pulled last fall) Google Drive Links
https://drive.google.com/file/d/0B0lfMZeSyJnYT2xFbUxKVUR0RGM/view?usp=drivesdk
Chuckles5150 said:
Flashable AT&T Galaxy S3 NJ2 Stock Recovery Zip (Pulled last fall) Google Drive Links
https://drive.google.com/file/d/0B0lfMZeSyJnYT2xFbUxKVUR0RGM/view?usp=drivesdk
Click to expand...
Click to collapse
Nice!
? d2att Oct-M KrAkEn Kernel ?
Jaitsu said:
At a bit of a loss here. I have here a d2att/I747 that was working up until today on PAC-Rom, then I decided to wipe it clean and install a Touchwiz ROM. I tried S3RX, I tried a supposed Note V port, hell, I'm trying stock. None of them will finish booting. S3RX and the Note V port give me a perpetual boot logo, stock gets past the Samsung logo, plays the sound, then gets stuck at the AT&T logo. I've given each one at least an hour to do something, and they're apparently not going anywhere.
I've tried everything I know how to do; I've wiped EVERYTHING (system, data, internal storage, formatted data, the whole shebang) and nothing seems to make a difference. It's on NJ2 and I even just tried reflashing the NJ2 bootloader/modem, but that doesn't seem to have done anything either. Totally at a loss here. What could be causing this? I mean, it boots into download/recovery fine and always -starts- booting the roms, but never finishes. Could I have a corrupted partition or something?
EDIT: Oh, so I put PAC back on it and it boots again. So yeah, this seems specific to TW roms. I don't get it.
Click to expand...
Click to collapse
Flash slimkat ROM and then flash TW ROM. It will work I had same problem
Oh wow, I didn't mean to abandon this thread. I haven't been getting email notifications 'til today for some reason. Anyway, yeah, I've wiped *everything* including internal storage; I'm flashing from an external SD. Nada. I was really hoping there was some NJ2 Odin-able package I could use that'd guarantee I wasn't screwing anything up, but oh well. Anyhow, I don't have the device on hand anymore (doing this for a family member), but perhaps I'll get it back and try that slimkat idea...? To answer mrrocketdog's question, no, actually. PAC is 5.1, every TW ROM I've found is 4.4. Shouldn't matter if I'm wiping every partition I can first, though, no?
Jaitsu said:
Oh wow, I didn't mean to abandon this thread. I haven't been getting email notifications 'til today for some reason. Anyway, yeah, I've wiped *everything* including internal storage; I'm flashing from an external SD. Nada. I was really hoping there was some NJ2 Odin-able package I could use that'd guarantee I wasn't screwing anything up, but oh well. Anyhow, I don't have the device on hand anymore (doing this for a family member), but perhaps I'll get it back and try that slimkat idea...? To answer mrrocketdog's question, no, actually. PAC is 5.1, every TW ROM I've found is 4.4. Shouldn't matter if I'm wiping every partition I can first, though, no?
Click to expand...
Click to collapse
Definitely try flashing the slimkat ROM. I had the same prob as you and read someone's reply about it. It fixed the issue for the touchwiz ROMs. After flashing slimkat go back to a touhwiz ROM. Do this before messing with the phone. I have a slimkat ROM on my SD card ready to be flashed at any moment for whenever I want to go back to touchwiz haha
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
BakedOnSomeSour said:
Definitely try flashing the slimkat ROM. I had the same prob as you and read someone's reply about it. It fixed the issue for the touchwiz ROMs. After flashing slimkat go back to a touhwiz ROM. Do this before messing with the phone. I have a slimkat ROM on my SD card ready to be flashed at any moment for whenever I want to go back to touchwiz haha
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
Click to expand...
Click to collapse
So do I have to flash Slimkat and then dirty flash TW? Seems like that'd have to be the case, otherwise anything it adds would get wiped away, unless it messes with partitions or something... I need to read up on this ****. That's weird.
I've been trying for over a month to get wicked rom installed on my n3 n900t . I'm rooted bootloader unlocked with twrp installed. I've had no issue installing any other rom on this phone I'm currently running alliance 5.0 and resurrection remix 6.0.1 and they work great but I would like to see what wicked is like. ( what it does when trying to install ) OK I have the wicked rom saved to my SD card with 4.4.2 gapps I'll restore my phone to alliance rom which is 4.4.2 and is says in the install it needs to be a 4.4.2 bootloader to install wicked, I'll go into twrp do a full wipe data, delvic,system, wipe it out then install the ROM and gapps package and it'll start to do its thing then get to where it says aramullz xda ( something? ) the progress bar will stop and it'll self boot itself out of twrp and go back to alliance rom and which will be messed up due to doing a full wipe. I like to figure things out on my own that's the fun part but this one's got me. Thanks for any advice.
Did you use terminal or Samsung Phone Info app to verify the bootloader in the phone?
I installed compullsion kernel 4.4.2 before and that failed, tried installing it while flashing the rom and gapps that failed, tried the other older versions of wicked v5 and v4 and v1 they all act exactly the same. I even wiped the whole phone completely cause I got Pissed due to failure ( lol ) flashed a fresh AP in Odin and tried everything again and still failed. I'm in the process of trying to convert the zip file to a tar md5 but having issues that Odin won't except the files cause the ( tar archived ) and I did flash the 4.4.2 bootloader as well. I'm beginning to think wicked doesn't like me.
My bootloader info should be 4.4.2
fastjohnson said:
this the info now which is useless because I'm on alliance 5.0 rom so it originally came from 4.4.2 chainfire zip.
Click to expand...
Click to collapse
Yes, looks like the phone is on 4.4.2 bootloader. Were you able to install the ROM?
audit13 said:
Yes, looks like the phone is on 4.4.2 bootloader. Were you able to install the ROM?
Click to expand...
Click to collapse
No still nothing I've tried everything I even wiped the entire phone installed the B4 Odin files AP and BL and CSC then flash chain fires autoroot file and twrp. The phone was basically stock 4.4.2. I tried all 3 wicked zips V1 V4 V5 and they all reacted the same way. And I already grabbed these files from different locations to make sure I didn't possibly get a bad batch. I've got every rom to flash on this no problem. Pacman, RR, alliance, slimroms, any cyan rom, I've come to terms no wicked for me. Lol
Lol, finally got wicked installed via flashfire. Twrp wouldn't do it. Super happy really fast rom.
What versions of twrp did you try? Just curious.
Using the newest 3.0.2 I think. Btw wicked rom so far is the most stable coolest rom I've experienced so far. I forsee it as my daily.
I have seen reports of some people having issues with 3.0 and higher so I stick with 2.87 for my devices.
No I actually didn't catch that. Besides that it refusing to install the wicked rom I haven't seen very many other issues. Well sometimes when im restoring a rom in twrp when it boots itll sometimes not in stall a lot of Google Play stuff and the UI will crash and I'll have to restore it again. I actually like the look and the button placement better in the version your using.