I5800XXJPS:
http://hotfile.com/dl/125074327/9f0...PS_I5800NEEJP2_I5800XXJP4_I5800XXJPS.rar.html
Pass: sampro.pl
Hi,
Can someone tell me how long does the vibration on SMS receival last on this new ROM ?
Is it ultra short like in XXJPQ (WAY too short to feel it) or is it OK like in XWJPI (about 1 second)
If the vibration is OK I'm flashing it.
Thank you.
I flashed XXJPS's kernel over XWJPI's base.
I confirm sound does not crack (tested just some second, but just some seconds were enough to spot it on XWJPI's stock kernel)
I'm still waiting for input if someone knows about the SMS vibration duration, if anyone has flashed it and knows please tell us
why do i get bootloop when i flash xxjps over xxjpq??? I cleared cache and performed factory reset...
ZOMG i hate this phone! my nandroid backup got corupted so i can't restore cache and data. since i have to start things allover again with titanium, i might aswell get the newest firmware but i always get bootloop after flashing jps...
I managed to flash it over jpm, now im trying to root it. I'm really getting sick of moding my phone, its all fun and great but there is so much trial and error and my phone gets unreliable. I think I'm staying with this firmware, at least until marcellusbe gets a more stable port of CM7. btw, the rom must be deodexed to change themes right?
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
first off i'd like to mention this phone was 100% perfect on stock Samsung rom 4.2.2 using Ktoonsez KT-SGS4 kernel for many months, until the day I installed this dreaded MDOB 4.2.2 rom and the "fix" that came with it
everything went bad on me back while I was running 4.2.2 stock unlocked boot loader and could never get it back to normal so this isn't a issue caused by 4.3 knox or 4.3 itself that i'm currently using. (i'm stuck on 4.3 roms but had this issue way before 4.3 existed)
i'm having an extreme amount of issues AFTER installing the MDOB rom, even after changing rom back to stock (flashed back to stock rom with ktoonsez kernel which is what I was using before I installed MDOB rom and phone has been royaly screwed ever since that day) more specifically I think it happened from the "i337M fix" that's included with the rom, either way after installing this rom I've never been able to get my phone back to normal.
everything runs fine except until I install a custom kernel (Ktoonsez KT-SGS4 kernel) then all hell breaks loose.
I don't blame the kernels or my current rom since I've ran this before for many months until the day i installed MDOB rom on my phone my phone was a dream machine.
issues since this rom has been installed include:
Issues:
A. RANDOM SLEEPS OF DEATH (phone shuts off or freezes)
B. random freezing while trying to turn on phone or enter recovery
C. some kernels won't work proper (specifically ktoonsez KT-SGS4 kernel) example gpu stuck at max while idle and downclocking when screen is touched with this kernel
D. wifi won't work with custom kernel on stock 4.3 rom without build prop edit to ro.securestorage.support, although it should
E. weak wifi and mobile signals
F. bad battery life
G. bad call quality
H. More that I can't remember off the top of my head
here's my flashing process, in attempts to remove as much as possible:
I know a few of these steps are probly pointless but hey can't blame me for trying.
step 1. enable usb debugging & unknown sources
step 2. install root & recovery
step 3. fresh boot phone let files settle so they can save (5mins or more) then plug into computer while turned on and delete everything
step 4. reboot into TWRP recovery (version 2.6.3.1) and clear everything, full advanced wipe, factory reset, format data than clear cache/dalvik afterwards just to be sure
step 5. remove SD card plug into computer and format to make sure there's nothing
step 6. install rom
step 7. (sometimes) clear cache/dalvik/permissions after rom install, although fix permissions seems to break my permissions rather than fix them or maby my permissions just break during flashing and I just can't fix them (haven't tested enough to be 100% sure)
i'm SOOO temped to try a full nand erase since i noticed there ARE still lot's files on my phone directory even after wiping, but i know that isn't a good idea;(
once stock kernel is back on my phone these issues are all gone.
Ktoonsez says it's not his kernel (used to work before, so i have no reason not to believe him), he says it's the rom well i'm on 100% stock Samsung rom (exception of kernel) and the rom was built to act the way it does so you can't really blame the rom so who do i blame??
until i went to go try wicked rom and flash back to stock I didn't realize these things were still on here, but now they emerge! wicked rom was giving me some (unrealated?) issue so i decided ima go back to stock so i flashed stock rom via odin (pc) and right away i noticed the 4G symbol, Samsung wallet, desktop not setup proper (no shortcuts) this ONLY happens when switching from wicked rom to stock rom on the first flash, i flash again everything looks how it should, and in order to get it to do this again i have to flash back to wicked rom and flash stock rom again and BAM it happens.
i knew my issue started on the same day that i installed this MDOB rom but after doing a full wipe and MANY "fresh" stock rom installs later i stopped questioning the rom and just lived with a crap phone that reboots itself all the time and has bad battery life, AS SOON AS I SEEN THE SAMSUNG WALLET bam it hit me like a truck, IT WAS THE MDOB ROM INSTALL.
UNLESS stock Samsung rom comes with wallet preinstalled and hidden on stock/wicked roms than the ONLY other way it coulda got on my phone is from the MDOB rom.
I can wipe/delete/factory reset/flash with twrp & odin on pc all I want, my roms are still messed up after FRESH installs. I believe there is still left over files from this rom/fix, I didn't think there would be anything until I noticed when i'm flashing from wicked rom back to complete stock rom using odin on pc I experience things from MDOB rom (while It should be 100% stock after odin (pc) flash, but it's not)
after the first flash from going from wicked rom back to stock I always experience the following "bug" i'll call it a bug since these things ALL HAPPEN AT THE SAME TIME: once I flash AGAIN all these symptoms go away until I go back to wicked rom and flash back to stock rom than right there after this first flash going from wicked rom BACK TO stock ALL these symptoms come back until I flash stock firmware AGAIN, a second time (even though I just flashed it)
Symptoms:
1. Samsung wallet appears in my apps (this was only EVER on my phone once, when I had the MDOB rom on my phone), this thing shoulda never somehow appeared back on my phone in any way shape or form after ditching the MDOB rom, but again is comes back after the first flash going from wicked rom to stock rom.
2. I get the 4G icon from MDOB rom (not the LTE icon I SHOULD have while on stock, when on wicked rom I have a little LTE icon with a tiny 4G above it, the only time I've ever had just a 4G icon (without LTE) like this is when I had MDOB rom on my phone (which is the only other rom I've run other than wicked rom and stock rom).
3. this icon ONLY shows up after the FIRST flash from wicked rom back to stock, once I install stock AGAIN than it returns to it's normal LTE icon.
4. now i'm not just *****in about an icon here, this is just a part of my problem (indicator if you will), when my rom is "bugged" after first install from wicked rom to stock rom my wifi works normal how It used too. but once corrected (flashing again) AND using custom kernel on STOCK firmware it breaks my wifi 100% broken until I use this little build prop edit fix, set ro.securestorage.support = true to false, bam wifi now working but the rest of my problems are still there (wifi used to work 100% on custom kernels and everything until MDOB rom touched my phone and left this "bug" behind)
5. when this 4G icon appears after this "first" flash back from wicked rom to stock rom I also experience something else, my wifi button works during first boot setup and auto enables itself and I have no issues with my wifi connecting (as soon as I see this toggle on I already know once my phone locks onto the network it's gonna give me a 4G icon and not an LTE icon like it should and sure as shiznit it does, as soon as I get my icon back to how it's supposed to be (LTE icon) all of a sudden wifi won't auto connect on a first boot anymore, never, 100% never. (back before installing MDOB rom I used to auto connect 100% of the time on first boot) like it does now only when it's "bugged" out.
6. apps are missing, when this "bug" appears there's no app shortcuts on the desktop of my phone by default after fresh flash like there should be, sometimes they appear on first flash once in awhile (some apps might not even be installed? or just shortcuts missing, have yet to verify)
7. it feels like the phone flashes way too fast (second flash takes longer, I think?) and more/all? apps get installed on second flash, and Samsung wallet get's REMOVED (how'd it even get there? other than bein left behind from MDOB rom, same with the 4G icon, that icon isn't in either of the two roms I use so how does it get there? and ONLY at the same time the wallet magically appears and the rest of this stuff)
8. when this 4G icon appears my phone seems to be great except for the fact that I know my rom didn't install properly since i'm still missing apps ect, once I flash again, apps appear, Samsung wallet DISappears, 4G icon gets replaced with LTE icon and everything is A-OK until custom kernel is installed, remember this is NOT the kernels fault as it ran 100% perfect for many months ON THIS PHONE until the day this MDOB rom was installed, and it's had these issues ever since.
some of the things I've tried:
- Countless wipes, including full advanced wipe, restore to factory, data wipes
- Ton's of fresh installs of BOTH versions of 4.2.2 - now doing same with 4.3 and wicked rom 9.1
- Tried wiping using TWRP and odin mobile (flashed mobile odin via TWRP, it works incase anyone didn't know)
- Tried flashing roms using odin (pc) v1.85, v3.07, v3.09
- Downloaded new copys of roms from new sources to make sure my roms weren't corrupted in anyway
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Amb669 said:
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Click to expand...
Click to collapse
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
hednik said:
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
Click to expand...
Click to collapse
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
I've flashed his rom on and off. Never had the issue. The rom doesn't invade anything a full wipe wouldn't cure. If it doesn't full wipe then it's the recovery. It helps once in awhile if you Odin back to stock or even copy your sdcard contents and format your sdcard to make it fresh. read up on it first.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
Also I recommend doing 9 wipes when swapping roms. It sound ridiculous I know but I do it and have never had issues.
Sent from my SGH-I337 using Tapatalk
Amb669 said:
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
Click to expand...
Click to collapse
Just odin back to stock and set if that clears things up. It should solve any odd problems. The thing with flashing rom's is that someone's issues cannot always be replicated.
Going back to Odined stock will take it back to factory stock then do a factory reset in stock 3e recovery and you should be fine
Hello,
I recently rooted my sgs4 gt-i9505 to the goolge edition using a YoTube tutorial on how to do so. Everything worked fine at the start but when I tried to install the PAC man rom, it jus stayed in the loading screen.
I restarted and tried rebooting but to no avail. I went back into the recovery mode and wiped the phone (divlac, cashes and system) then I reinstalled the google rom to find my wifi was not working. I tried the same process again, wipe- reinstall. Now I can't receive calls, the wifi doesn't work, home button only works on double tap, pull down status bar works but nothing in displayed.
My question is, does anyone have any ideas on how I would return my device to normal or know a full proof recovery and rom I can use that will correct these problems.
I am in the UK if that makes any difference.
Thanks for all and any help.
Matt
Matt.graham said:
Hello,
I recently rooted my sgs4 gt-i9505 to the goolge edition using a YoTube tutorial on how to do so. Everything worked fine at the start but when I tried to install the PAC man rom, it jus stayed in the loading screen.
I restarted and tried rebooting but to no avail. I went back into the recovery mode and wiped the phone (divlac, cashes and system) then I reinstalled the google rom to find my wifi was not working. I tried the same process again, wipe- reinstall. Now I can't receive calls, the wifi doesn't work, home button only works on double tap, pull down status bar works but nothing in displayed.
My question is, does anyone have any ideas on how I would return my device to normal or know a full proof recovery and rom I can use that will correct these problems.
I am in the UK if that makes any difference.
Thanks for all and any help.
Matt
Click to expand...
Click to collapse
You could try to go back to stock and check if everything still works there.
Did you flash the correct modem/baseband for the ROM / your carrier? There is a thread in general for all the modems. Chances are with a KitKat ROM you need to update your modem. Read that thread and give it a go. The file is about 15mb and takes a minute to flash in Odin. Failing that go back to stock.
Nothing in status bar: that's what it looks like in stock, you can use 2 fingers for the quick settins. Installl WANAM XPOSED fromwork for more tweaks and options!!
Home button double tap: that's the way it works on the google edition, that's just it. BUT wanam xposed can change this with the Gravity Box module!! You could try the Echoe 2.2 kitkat rom it has xposed pre-installed.
Keep in mind things look blanker and less functional as you no longer have samsung touchwiz which adds a LOT of stuff to the stock experience!
One more thing: ALWAYS make a nandroid backup before flashing ANYTHING at all, you never know when you will need it. Backup the nandroid to your PC also just in case, things go missing/ get deleted! T
Ok this is a really strange Problem. I have two notes. On both I flashed the s5 port from Fahadali. Both had v6 on them and everything was awesome. He left development though so I continued the Project trying to make a "v7" Version, while doing that after I flashed the modified v6 many times but suddenly it softbricked. All I did Change though were some apks.
I've done this many times before with other roms without any Problems at all.
Then I reflashed stock NF4 through Odin and the newest twrp. Flashed v6 (the original non modded version) and it softbricked again...
I tried again, same result. I tried to Flash other recoveries, other bootloaders, other fw's through Odin and a lot more but: nothing.
Everytime I Flash v6 it breaks. I tried to Flash v5 and then suddenly: It worked! I tried to Flash other roms like Omega, and they work aswell. Only the v6 Version doesn't.
So if that's the case and the phone itself is clean (wiped 100 times Flashed stock even with a pit file) the Rom must be corrupted right? So I checked the md5 and well it was correct. I redownloaded and still: same md5. I checked the md5 on the note aswell. I tried using a sd Card instead and still: the same result.
In the meantime my other note worked perfectly, even with my modded Rom. So I continued to work on the v7 using that one. And then after like 14 flashes: the same Problem on that one aswell.
In detail:
I use twrp. And get into the Aroma installer of the Rom. It installs without any Errors whatsoever. Then I reboot.
And now the important part: the kernel has not been flashed cause it's not showing up in red (the rom's using a custom kernel).
This doesn't happen when I use the v5 Rom(still), and never happened before even with the v6. So I even tried flashing the kernel afterwards trough Odin and it gets successfully flashed. But the Rom still doesn't boot...
This means though that because of the kernel not being flashed (even though in Aroma it Shows that it does) even the rest might not get flashed. It only wiped the System Partition and that's it. But then the question remains why did it work before?? And why does it work for all the other People that have flashed it? And why did it work on mine until I flashed it more than 14 times?? And why does v5 and all the other roms still work fine?
I really don't get why this happens. Some v6 files have to still be on the device somehow, or idk. It's impossible cause I wiped but who knows. I've never seen anything like it, neither has the original dev of the Rom.
I Need to get v6 working, else I can't continue to build this Rom. Which is a big Problem for all who wants the s5 Rom.
I hope someone knows what to do. Thank you for your time.
whenever i came to a custom rom and suddenly when i want to go back to stock firmware, (after i flash stock firmware via ODIN) when the boot is done ofcourse we undergo to SETUP like brandnew right? but in my case it is black screen and repeating System UI force close,, what do you think the problem? this start happen when i try to use Hades rom, and followed the flashing of updated MODEMS for my variant. Please Help me , thanks in advanced!
EDIT: im currently downloading the latest firmware from Samsung Mobile hoping it fix my A5