[Fix]Is your chrome crashing after updating to nj4? - AT&T Samsung Galaxy S 4 General

Just in case anyone hasn't figured this out (I just did)
Hey so I think I figured out the fix with chrome, if anyone is still having issues. I've been reading around and have seen that if people change their kernels selinuxmodechanger properly works by sticking on permissive. I noticed that on the nj4 kernel the permissive setting wasn't sticking and chrome kept crashing. So I used Odin again like in the upgrade method and switched my kernel back to nc1's. Permissive sticks and chrome works.
Tl;dr: if you Odin'd to nj4 kernel, Odin back to nc1 kernel. Permissive sticks and chrome works.
To anyone with further knowledge on this, feel free to chime in. I don't seem to be having any issues. Nj4 update, modules, nc1 kernel.

Thanks dude! This kept happening on my GS3 and I couldn't figure out why.

StoneyJSG said:
Thanks dude! This kept happening on ny GS3 and I couldn't figure out why.
Click to expand...
Click to collapse
Glad that I was able to help and that the fix is actually working for others!

It seems that switching the kernel to nc1 breaks WiFi when running on the nj4 base. I switched back to the nj4 kernel and WiFi can be enabled again. But selinuxmodechanger still doesn't work with this kernel. ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have we lost all of our devs before figuring out why the app doesn't work with the nj4 kernel? Or is everyone still on nc1 and not caring about this?

Murasakiii said:
It seems that switching the kernel to nc1 breaks WiFi when running on the nj4 base. I switched back to the nj4 kernel and WiFi can be enabled again. But selinuxmodechanger still doesn't work with this kernel. ?
Have we lost all of our devs before figuring out why the app doesn't work with the nj4 kernel? Or is everyone still on nc1 and not caring about this?
Click to expand...
Click to collapse
I've never been able to switch to permissive mode on NJ4, even with the latest versions of BusyBox and SafeStrap running on 5 different ROMs. Installed NJ4 using both upgrade methods, to different slots and tried about every other idea imaginable.
Went back to NI1. I'm convinced SafeStrap needs to be updated to A04 for full NJ4 support with permissive enabled.

kevinco1 said:
I've never been able to switch to permissive mode on NJ4, even with the latest versions of BusyBox and SafeStrap running on 5 different ROMs. Installed NJ4 using both upgrade methods, to different slots and tried about every other idea imaginable.
Went back to NI1. I'm convinced SafeStrap needs to be updated to A04 for full NJ4 support with permissive enabled.
Click to expand...
Click to collapse
There seems to be a conflict with the nj4 kernel. I ended up putting the nc1 kernel back on, still on nj4 base and my WiFi, chrome, and the play store are working properly. Kept getting a random 492 download error before I switched back.

Did you Odin the nc1 kernel or did you flash via SS?

cryhavok13 said:
Did you Odin the nc1 kernel or did you flash via SS?
Click to expand...
Click to collapse
I odind'd. I eventually started having problems though. While chrome worked, WiFi stopped working and I'm not sure when. I forget what modules I flashed, hopefully the right ones or I put myself through a lot of grief. Anyway, I could only get WiFi to turn on when I was using the nj4 kernel, which broke chrome again and eventually the play store. So I downgraded to nb1 and I'm staying with it.

Related

[Q] First time rooting.

Couldn't find a very clear tutorial anywhere, just a number of different threads saying different things lol. Anyways, need to know how to root my Droid Charge. Also need to know how to install CyanogenMod after.
I know rooting will void my warranty but I heard from a few people that if I unroot the phone, the warranty will be put back in place. Is this true?
If I somehow manage to brick my phone, I can always unbrick in most cases, correct?
Phone Info:
Hardware version - i510.06
Firmware version - 2.3.6
Kernel version - 2.6.35.7-EP4
Build number - SCH-I510.EP4
Not sure what information is important, but I believe it was mainly the kernel and Android version lol.
EDIT: Never mind about Cyanogen, I just want the best/fastest ROM I can get.
First things first. It's very difficult to hard brick this phone. I had to do a warranty return before and it is easy to go back to stock. If you get a soft brick, you can follow this thread and get it back to stock: http://forum.xda-developers.com/showthread.php?t=1111486
Next thing, you can't install CyanogenMod on this phone. We don't have any AOSP rom on this phone. All we have is repackaged stock roms.
As for how to root, it really depends on what you want. Do you just want root, or do you want a rom?
For right now, I just want to root. I've found out how to do that, kinda. I'm stuck now.
I'm trying to install imoseyon's kernel through CWM but I used the backup option before I installed the kernel. So now when I boot into recovery it oly gives me the optinos to "reboot system now", " apply update from sdcard", "wipe data/factory reset", and "wipe cache partition". I tried to apply update from sdcard and when I selected my kernel zip, it gives me back this:
"
-- Install /mnt/sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
You need to reflash CWM.
CWM does not survive a reboot unless you're on a custom kernel, or root and remove the updater script. You have to flash CWM and immediately boot into it. If you let it boot up fully on the stock kernel, it will overwrite CWM with the stock recovery, so you'll have to flash it again, and immediately boot in and flash.
Will I keep the backup I made? Or should I just not worry about the backup and use Titanium?
It will keep the backup. It does the backup to SD, and the only folder on SD that CWM will touch in a wipe is .android_secure.
It worked. All rooted, thank you. Any suggestions for themes, apps to get, or ROMs?
ratchetlock2 said:
It worked. All rooted, thank you. Any suggestions for themes, apps to get, or ROMs?
Click to expand...
Click to collapse
The two most are using are TweakStock and Infinity. I strayed but came back to
TweakStock. Dont think it has a true theme available yet but you could atleast do something like Go launcher or something. With Ifininity there is a theme available. Read about both in the Dev section then decide.
Will do. Any OCable kernels yet? Saw someone post on here that there wasn't any yet.
ratchetlock2 said:
Will do. Any OCable kernels yet? Saw someone post on here that there wasn't any yet.
Click to expand...
Click to collapse
No custom kernels at all, other than repackaged stock kernels, but Tegrak Overclock works with any GB kernel. The free version only lets you change clock speeds. The pay version lets you change voltages as well, and lets you apply at boot.
Uh oh, got stuck in an infinite reboot loop. Tried turning my phone on only to come up to the first Samsung post screen, goes to black eventually for a little bit, then goes right back to the Samsung screen. How do I fix it? Can't find a solid answer.
I went into CWM and tried to restore a backup but it said it was missing the MD5 file or something; can't remember what exactly the error was with the restore. I'll try reflashing CWM soon.
Now I can't do anything... Can't put phone in DL mode, recovery, nothing. Won't even say it's charging.
I'm still under warranty, I'm considering bringing it in and saying I need a replacement because I know they won't be able to fix this on the spot.
EDIT: Got into DL mode luckily and I'm getting into DL mode smoothly now. But I still can't power on or get into recovery...
EDIT2: Using this thread to try and fix my problem. http://forum.xda-developers.com/showthread.php?t=1111486
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are these the right settings?
Trying to odin this file: http://forum.xda-developers.com/showthread.php?t=1172182
EDIT3: What a headache... Fully back to stock now. Going to try and restore everything that I backed up onto my SD card.
Are you leaving in the battery while flashing?
Sent from my SCH-I510 using xda premium
Nope.
numberfix
ratchetlock2 said:
Nope.
numberfix
Click to expand...
Click to collapse
There's your problem. Once you're in download mode and detected by Odin, pop the battery back in.
Sent from my SCH-I510 using xda premium

[Q] Why does it do this?

Every ICS ROM that I have flashed on my phone has done this. I never hear anyone discussing this and I can't be the only one. Why and is there a fix?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get it in the app drawer as well.
Have you done a full wipe and is hardware acceleration enabled?
Not So Strange...
Well,it backs to several things:
Did You Fully wipe?
What's device current Recovery?
What was your previous Firmware?
Did the Roms you use,support GPU rendering ?
How is your device like with official firmware?
And several other things...
peter_dizai said:
Well,it backs to several things:
Did You Fully wipe?
What's device current Recovery?
What was your previous Firmware?
Did the Roms you use,support GPU rendering ?
How is your devce like with official firmware?
And several other things...
Click to expand...
Click to collapse
Yes, I always do a full wipe when flashing roms.
5.0.2.0
It does it eventually, regardless of the previous firmware.
I believe so, all roms that I flash come from here.
I just flashed a root access version of the IMM76D ROM and it happened on that one.
It only happens every so often, and a reboot is in order to correct it.
Thanks guys.
Now,It's Better...
kazerak2 said:
Yes, I always do a full wipe when flashing roms.
5.0.2.0
It does it eventually, regardless of the previous firmware.
I believe so, all roms that I flash come from here.
I just flashed a root access version of the IMM76D ROM and it happened on that one.
It only happens every so often, and a reboot is in order to correct it.
Thanks guys.
Click to expand...
Click to collapse
Ok,first try to flash latest official firmware which I think is:
Ics 4.0.4
Baseband Version: D720SPRKH1
Build Number:IMM26
and here is a how to:
http://www.techzek.com/how-to-update-sprint-nexus-s-4g-on-android-4-0-4-ics-firmware/
Afterward flash following recovery:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-crespo.img
Then try to flash:
http://bigota.d.miui.com/2.3.30/miui_NS_2.3.30_c1e078377e_4.0.zip
or
a cyanogenmod 9 and report back please...
^ Is that the correct firmware to flash for the 4G nexus s?
That looks like a launcher problem to me. Are you using an aftermarket launcher or are you restoring it from a previous install?
wild1z said:
That looks like a launcher problem to me. Are you using an aftermarket launcher or are you restoring it from a previous install?
Click to expand...
Click to collapse
Stock launcher, I've never used a different launcher other than stock on all my ICS ROMs.
I Edit the firmware,check and flash it.
Update, my phone did it again and I thought I would check the launcher. I did a "force stop" on the launcher and that resolved it. I have always used the stock ics launcher what would cause the launcher to behave this way?
kazerak2 said:
Update, my phone did it again and I thought I would check the launcher. I did a "force stop" on the launcher and that resolved it. I have always used the stock ics launcher what would cause the launcher to behave this way?
Click to expand...
Click to collapse
See my signature for proper FULL wipe. Something tells me you're not wiping system.
I'm having the same problem with one of 2 Nexus S 4G's I flashed with IMM76D. I did a full proper wipe on both of them, but one seems to corrupt the text like in the picture. It happens after it's been running a while and a reboot fixes it temporarily.I wiped it fully again and reloaded the ROM and its still doing it.
Next thing to try is re downloading the ROM. Maybe a corrupt download? Any ideas?
[email protected] said:
I'm having the same problem with one of 2 Nexus S 4G's I flashed with IMM76D. I did a full proper wipe on both of them, but one seems to corrupt the text like in the picture. It happens after it's been running a while and a reboot fixes it temporarily.I wiped it fully again and reloaded the ROM and its still doing it.
Next thing to try is re downloading the ROM. Maybe a corrupt download? Any ideas?
Click to expand...
Click to collapse
I too have done a full proper wipe with that same rom and still have the issue from time to time. Next time you get it try to fore stop the stock launcher. That fixes it for me, until it happens again. But for me its something with the stock launcher.

[HELP]No LTE on CM12s/Signal keep crashing

So i waited 4 days for the OTA and still nothing. so I've decided to go ahead and flash manually.
First i tried flashing using TWRP and things went great but as soon as phone reboots there was no signal and few seconds later signal came up and changed to H+ then 3G and went blank and kept going on a loop.
decided something wrong with the flash i did a factory reset. still crashing. so i did a fresh install still crashing.
I was helpless so i restored the Backup of my old XNPH5Q. everything great. back to LTE again. then i thought might be a lolipop issue so i flashed Oxygen os. everything works fine with LTE signal and all. Attached a 44s video on what's going on when CM12s installed. you can see signal icon crash change signal and go on a loop
Please help me fix this.
Same thing is happening to me, and I cannot connect to LTE.
It works for me http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
Fittip4ldi said:
It works for me http://forum.xda-developers.com/one...dio-updated-modem-radio-files-oxygen-t3072516
Click to expand...
Click to collapse
This did not work for me. Still no LTE and signal keeps crashing
jbass350z said:
This did not work for me. Still no LTE and signal keeps crashing
Click to expand...
Click to collapse
For some reason this method worked for me. this is what i did.
So after going between roms i decided to settle and restored my Kitkat XNPH44S backup and then upgraded to XNPH05Q when prompted. and then i flashed the XNPH05Q Modem. then i flashed the lolipop YNG1TAS0YL rom by booting in to recovery.
let the phone idle for few minutes after reboots from recovery. it took about 2-3 minutes to establish the signal but everything went smooth. earlier today i clean installed the new YNG1TAS17L OTA. so far i haven't had any problem.
Hope this helps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I've found luck being on Lollipop and flashing over CM11 05Q modem.
Currently, I'm on the daily Nocturnal build 5.1.1 or CM12.2 and this modem had fixed my problems and works with latest ROMs still.
Make a nandroid just to be incase.
CM11 05Q modem :

S6 Fingerprint Reader Error after Update

I have a Galaxy SM-G920A S6 fully stock that was on 5.0.2. I recently got a update OTA for it to 5.1.1. Of course this update failed to load for some reason. I then downloaded the stock update 5.1.1 unmodified firmware and flashed it via Odin. Worked perfect. Then I tried using it for my fingerprint and this error came up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried rebooting of course. I tried resetting through recovery and wiping cache but it the error still pops up when I use anything related to the fingerprint reader.
Methods that I tried to use to Fix:
I read on a past thread, that if you disable the fingerprint service in application manager and then reboot and then enable, it fixes the issue. I tried that and it was the same thing. I've been reading a few Xda threads and it seems like there is no real fix for this.
This is the name of the file I installed: G920AUCU3BOI2_CL5527015_QB6363222_REV02_user_low_ship
I'm not aware if a newer version popped up, then I guess I could flash that and update.
Thanks in advance.
KillTheSprint said:
I have a Galaxy SM-G920A S6 fully stock that was on 5.0.2. I recently got a update OTA for it to 5.1.1. Of course this update failed to load for some reason. I then downloaded the stock update 5.1.1 unmodified firmware and flashed it via Odin. Worked perfect. Then I tried using it for my fingerprint and this error came up.
I've tried rebooting of course. I tried resetting through recovery and wiping cache but it the error still pops up when I use anything related to the fingerprint reader.
Methods that I tried to use to Fix:
I read on a past thread, that if you disable the fingerprint service in application manager and then reboot and then enable, it fixes the issue. I tried that and it was the same thing. I've been reading a few Xda threads and it seems like there is no real fix for this.
This is the name of the file I installed: G920AUCU3BOI2_CL5527015_QB6363222_REV02_user_low_ship
I'm not aware if a newer version popped up, then I guess I could flash that and update.
Thanks in advance.
Click to expand...
Click to collapse
Flash proper bootloader. Simple as that.
Rakcoon said:
Flash proper bootloader. Simple as that.
Click to expand...
Click to collapse
Sorry I'm really a noob at this. Proper bootloader? What do you mean by that? I'm trying to keep it stock.
Is the firmware I flashed wrong?
what's your model? Country?
Rakcoon said:
what's your model? Country?
Click to expand...
Click to collapse
It is model SM-G920A
Full length name is SM-G920AZDEATT
I'm in the united States.
Rakcoon said:
what's your model? Country?
Click to expand...
Click to collapse
I flashed only the AP file in Odin when I updated. Should I have updated the other files as well?
I fixed it by not being an idiot, and flashing all the files in update.
D:
Hahaha good!
can you tell me how to fix it? where did you download the file? what are you using for the installing? pleasee i want to know i have the samew problem

"No SIM card - 31000" - Galaxy S5 G9000P

Recently I have flashed my S5-G9000P for the first time with the Resurrection OS RR-O-v6.0.0-20180405-klte-Official.
After working alright for the first day or so, texts would not send. Then, at the top of my screen it says "No SIM card - 31000". I don't really know much about modding phones, so here is what I tried so far:
- Resetting the phone
- Removing the SIM card then reinserting, then resetting the phone again
- Resetting my mobile data options
So far these above options haven't helped the problem. I have looked at similar threads to this and none seem to have the same problem based on their descriptions.
Thanks for your time.
Phone - G9000P Galaxy S5
Android Version - 8.1.0
Kernel version (if that's important) - 3.4.113-lineageos-g592be94 (gcc version 4.9.x 20150123 (prerelease) (GCC) ) [email protected] #1 Thu Apr 5 13:41:19 CEST 2018
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.
Well I can State the Facts... has happened here tooooo..... on LineageOS 16 and 15.1. The only fix that I have done, which may help, is Rebooting the Phone.
Yep, tat was the only thing I actually have done, When and IF it happens.
Same thing though, "NO SIM Card" " Corrupt Sim Card" and I Tink there was another one too. All if which, (Knowing that it was running correctly, prior this) I just rebooted. maybe once, maybe like 3-4 times. before it actually goes away.
Now, knowing the phone was running correctly is the Key , I believe. IF your in the process of Flashing, yep, maybe restart that. However, if its running right an all, no reason to do any flashing. why--- Well, was built in the First run batch of them. the phone is rather good and all, cant even see me spending over a $1,000.00 for a new phone, that's Ficking Nutz !!! I am sure, they did built it to last a life time, but what is it, a cell phone built in 2012. Before my warranty was over, I rooted, and got rid of all thre Samsung crap. Ran smooth. Been Flashing ever since.....
E.4.113-LineageOS-g592be94 mobile data not working
Hippie459MN said:
Mine did that out of nowhere also. Saying no sim card was inserted or some junk. I have never flashed custom kernels so maybe that is an issue. I tried reflashing my custom rom I was running at the time (the one in my sig at the moment) and nothing. I ended up reflashing the stock firmware in odin then booting straight to recovery and reinstalling my rom and that seemed to fix it. That happened twice and thats how I got it fixed.
I have since flashed the latest stock sprint firmware and then installed LineageOS 16 and it has not happened since but I have been having a ton of other issues with the phone, on both custom sprint roms, and LineageOS so pretty sure my phone is on its way out. Might have to do a motherboard replacement. Hope not though.
Good luck and report back.
Click to expand...
Click to collapse
You have in your signature a new rom, does that rom is working ok? The only thing that is driving me nuts is that I can’t have my data usage, I installed RR-O-v6.0.0-20180405-klte-Official on my gsm900M what do you suggest!?
Edited, i found it! just needed to edit the APN settings! i google them for my case that is Mexico, and now i have mobile data!!
Im still running lineageOS. I just havent updated my signature yet. I am going to be getting a new phone in the next week or so though. Pretty sure the motherboard (Internal storage) is taking a dump on me. Phone will work great sometimes for 2 weeks then apps start crashing like mad and only way to fix is to uninstall and reinstall and only way to fix it is to do a full wipe and reinstall the rom. Sometimes it will even start messing up within an hour or two. Things like google play services, the stock dialer, and bluetooth will randomly crash. I have tried just about everything. Different roms, going to stock software, nothing works. And when it tries to do do a backup in TWRP, it always fails in the data partition and always at different points saying it cant read the data partition or some junk. I forgot but I am giving up on it. I have another S5 but wont have it for another week or two.

Categories

Resources