Related
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
Hi, RomSwitcher has been nagging me to update since I installed it. So finally, I clicked Update.
Now my phone doesn't show the boot logo, it just boots into a blank screen. Adb seems to function:
C:\Unified_Android_ToolKit>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Anyways, if I ODIN any Perseus kernel, then my first ROM boots fine. But if I go into RomSwitcher and install the tools, then reboot boots into blackness again. I've tried to install the tools from the recovery, same thing happens.
I would post this in the Development thread, but I'm not allowed to post there yet. So as I understand it, RomSwitcher boots into it's own environment, changes some directories so one of several ROMS will boot. What seems to happen is that the RomSwitcher environment is just blank. I have no idea where to look, and I can't find the old version of RomSwitcher which worked anymore. I don't really want to reflash everything just to get RomSwitcher functionality back.
There's no information on the internet about how it works or how to fix it. It seems I've probably managed to wipe the configuration when updating it. If anyone can point me to a FAQ or Guide or something about how it works, or summarise it, I'll really appreciate it, as I don't really want to go and dig through the code to figure it out... that might take me several weeks with the little time I have available!
Questions:
What is in the configuration file?
Where is it stored?
Can I re-create it by hand?
What's the simplest way to get RomSwitcher working again, without starting from scratch with all my ROMs?
(I'm just dual booting Phoenix ROM and CM11, which worked fine until I updated RomSwitcher. New RomSwitcher looks good, but doesn't work!)
Thanks
Steps to repeat...
So, I've tried every Perseus kernel: 16, 18, 19
From the main TW based ROM that boots: Phoenix 10.1
RomSwitcher says to install Tools and Reboot before it does anything. Doing that reboots into a black screen, no matter what kernel. I've re-downloaded the main config and the tools several times.
Seems the only thing left to try is re-flash main ROM, re-install RomSwitcher... then it will probably work But that is a 3-4 hour operation I can't afford right now.
:crying: -Sigh- Alright, this has been a pretty stressful two days so I'll try to be as specific as I can.
Device details:
- Samsung Galaxy Tab 4 10.1 T530NU 16 GB Black with WiFi capabilities.
- I was running Lollipop 5.0.2.
Problem:
I wanted to get Xposed installer on my tablet, and found out if I wanted to get the modules I wanted working with what I wanted to do, I needed the Xposed Framework installed onto my tablet. I went to research on how that works/what do to to get that up and running for me, and I found out I needed TWRP, had to add it on my tablet with Odin, and then add what I needed for Xposed in a custom boot through my SD card.
As soon as I got TWRP on my tablet, I've been stuck on a bootloop.
Things I've tried:
- Wiping all data.
- Clearing cache/dalvik.
- Charged to full, and retried clearing cache/wiping again.
Additional Details:
- I have access to a PC
- Able to connect my tablet to a PC via USB cord.
- I'm in the US (Since I've some some region specific things floating around)
What kind of help I'm looking for:
- A updated(?) and working stock firmware for my device.
- TWRP version that will work properly on my device.
- Xposed framework ZIP to add to my device.
I've been spending hours and hours trying to find websites and threads on here and on the internet in general to help me fix it, or find stock firmware for my tablet to start over from scratch. I have had no luck anywhere at all. My desktop is just piled with .ZIP files that have claimed to work but no longer work(?).
I'm just at a loss...It's really diving me crazy. So, as a last resort, I'm writing to see if I can get some help on here. I'm not one to really ask for help on things like this..I usually do enough research to figure it out but I feel like I've visited every single thread/site I can and have had no luck. I would greatly appreciate some guidance
Resurrecting this thread after over a year hoping someone is paying attention...
Tying to the thread hopefully getting enough people talking about this... again.
forum.xda-developers.com/tab-4/help/samsung-galaxy-tab-4-10-1-sm-t530nu-t3441044#post74700970
I have the same problem as well. I have downgraded from 5.0.2 to 4.4.2 hoping that would work. I flashed PACMAN custom ROM and GAPPS 6.0 nano last night and was able to get in and through setup, but the wifi will not work nor does it detect any nearby networks.
Looking for answers here... Corrupted partitions maybe? I have stable stock ROM's
Maybe sideload APK's to evaluate/fix the issue from the ui side - if any apps exist?
Don't ask why I stayed so long on 4.2.2, did PhD and the phone was running nicely and hat no time to update, root again etc. pp. Now that the PhD is finished I wonder if it is worth at all to invest the time to update to higher version. It looks like 5.0 was the last update supported by sony. I don't have a custom ROM, just rooted original Sony firmware with flashtool.
In general I don't see a personal benefit to buy a new phone. Keeping the Z and updating to the best Version or custom ROM running smoothly on the old hardware and which can be rooted is my choice.
Which version and ROM do you suggest?
Thank you for your time and advise
It depends on what you need.
If all you need is a durable battery, then better stay on 4.2.2, but you know...as time goes by, most application will stop their support for jellybean.
If you want more performance, then 5.1.1 is the choice, but not battery friendly. STAMINA mode is present to help saves some battery.
For the best updated OS version, go for LineageOS 14.1. It's based on nougat 7.1.2.
Many thanks, as far as I remember I can do a image with CWM of current system and can give LineageOS a try! I saw now that some modern apps need at least jellybean 4.4 to be installable. Battery shouldn't be a problem, I rather want the camera to work nicely also under a customROM, actually I think the original Sony camera app is quite good and this one I would loose. All other Sony apps I never noticed really. For all the other possible customROM I don't really have the time to study them, camera would be most important. I guess recovering most of the apps from jellybean 4.2.2 to Lineage via Titanium Backup will work so I can check this fast?
Thanks in advance!
You can also try to use RR Oreo if you like the latest Android.
https://forum.xda-developers.com/xperia-z/development/rom-resurrection-remix-o-6-0-0-t3747588
Here what I think about it:
https://mastodon.social/@ahmd_amsyr/99954433452073565
Hmm, I installed lineage 14.1 zip via ROM Manager and it was succesful, but then I also wanted to add directly after this the optional lineage root. The phone was already rooted and unlocked and when pressing the option, the screen went immediatley black. When pressing power button the lamp is short igniting green/red and screen stays black. Installed the newest flashtool and flashtool drivers, but when trying to root or flash the xperia z again via flashtool, it always says in the flashtool log, the driver is too old under Win 7 and Win 10 on 2 PCs. I installed pc companion and additionallly the flashtool drivers.
Do I have to install distinct versions of flashtool and drivers? Flashtool is version 0.9.24...?
I could manage to get it in boot loop now, showing sony logo. But with same flashtool it's not possible to flash ftf in flash or fast boot mode, because it is constantly rebooting. What to do now?
https://forum.xda-developers.com/xperia-z/development/kernel-ub-t3198491
this does not work
https://forum.xda-developers.com/xperia-z/general/disaster-recovery-getting-z1-zu-z-zl-to-t2229250
also doesn't help
Still would like to install lineage.zip again. But how do I get the device booting normally and is the rom manager stil alive? If not I can also flash directly via flashtool a .ftf?
Nevermind, I could repair it, now on 5.1.1 stock.
as someone asked per pm:
I'm also not sure what changed it. I went then to very old flashtool version on my old notebook, probably over 5 years old when I flashed my xperia neo smartphone. With this it worked. Flashtool version is one point. My bootloader was unlocked. The flashing of lineage 7.1.1 also worked, I then made the error to root also via Lineage package directly after flashing the rom, then I was in Boot loop. It's best to start flashing, let flashtool compile the zip, this takes some minutes, progress shown in flashtool, and then you connect via usb smartphone, especially when in boot loop. But start with different flash tool version and post your error messages in the thread i posted. I stil have the old xda tabs in my browser history that helped me to install ics on neo and lollipop on xperia z (and it is really fast again after complete reinstall) no need for new phone
I flashed to LineageOS 7.1.2 and I do not regret it. I have the (almost) latest version on Android. I can manage the apps permissions and it all works great.
I have an unlocked Galaxy S5 from "Three" Ireland (3IE) that restarts many times during the day but only when I leave it idle. Either on its own or while charging.
When its not charging at home, the restarts drain the battery very quickly.
Unrooted, latest stock ROM for this carrier (Android 6.0.1 G900FXXS1CQD1_G900F3IE1CPJ3_G900FXXS1CQA3)
I searched the forum and tried the following in this order:
1. Replace the battery
2. reset factory settings (and reinstall everything)
3. Flash stock ROM using ODIN v3.12.3 (same ROM version)
Nothing helped. :crying:
I didn't reset factory settings (again) after flashing stock ROM since I don't think that will make a difference. Any ideas?
kdizzy07 said:
I have an unlocked Galaxy S5 from "Three" Ireland (3IE) that restarts many times during the day but only when I leave it idle. Either on its own or while charging.
When its not charging at home, the restarts drain the battery very quickly.
Unrooted, latest stock ROM for this carrier (Android 6.0.1 G900FXXS1CQD1_G900F3IE1CPJ3_G900FXXS1CQA3)
I searched the forum and tried the following in this order:
1. Replace the battery
2. reset factory settings (and reinstall everything)
3. Flash stock ROM using ODIN v3.12.3 (same ROM version)
Nothing helped. :crying:
I didn't reset factory settings (again) after flashing stock ROM since I don't think that will make a difference. Any ideas?
Click to expand...
Click to collapse
Did you have any custom rom installed before? Try flashing latest bootloader for the phone and checking, if all else fails try a custom rom and see if the problem persists.
Mufrad said:
Did you have any custom rom installed before? Try flashing latest bootloader for the phone and checking, if all else fails try a custom rom and see if the problem persists.
Click to expand...
Click to collapse
No custom ROM while the phone was in my possession. It could have been before I got it (I'm not the original owner) but when I did get it I was on stock and unrooted (at least according to "Root Checker").
Didn't I get the latest bootloader when I flashed the latest stock ROM? I remember seeing the files "boot.img" and "modem.bin" in ODIN.
Also if you have any suggestions for a good custom ROM I'm all ears :angel: (I like bug-free*, speed and battery life. In that order of importance)
* - I know there's no such thing as "bug-free" but you get the idea
kdizzy07 said:
No custom ROM while the phone was in my possession. It could have been before I got it (I'm not the original owner) but when I did get it I was on stock and unrooted (at least according to "Root Checker").
Didn't I get the latest bootloader when I flashed the latest stock ROM? I remember seeing the files "boot.img" and "modem.bin" in ODIN.
Also if you have any suggestions for a good custom ROM I'm all ears :angel: (I like bug-free*, speed and battery life. In that order of importance)
* - I know there's no such thing as "bug-free" but you get the idea
Click to expand...
Click to collapse
Sometimes you have to flash bootloader again separately, specially if it was changed to an later version than the one you are flashing through odin, and I would suggest a custom touchwiz rom which is close to stock but with bloat removed and some speed tweaks maybe for the most bug free experience. But also maybe give stock android roms a try, most bugs should be ironed out.
Mufrad said:
if all else fails try a custom rom and see if the problem persists.
Click to expand...
Click to collapse
OK, last night I tried a couple of things:
1. I flashed Slim6 6.0.1.build.2.1 and twrp-3.2.3-0-klte (with wiping) - didn't help.
2. I took the sim card & sd card out - didn't help.
3. I ran logcat from ADB using USB debugging to see if I could get the error before the restart - While the phone was connected and logcat was running, the phone never restarted. Even when the screen timed out and turned off. (I guess the phone doesn't count this as "idle")
oh, and thanks for all the assistance so far
The fact that it happens on custom ROM leads me to think hardware. The fact that it doesn't happen if I keep the phone "busy" leads me to think software. What should I try next?