Database Users

Phone does not start after reboot on jamal2367 ROM, S4 GE Final-R4

Hi all,
I have this annoying issue with [AOSP] Official 4.4.2 - S4 Google Edition - Final-R4 from jamal2367; current baseband installed XXUFNA1.
Problem:
When the phone loses connection, it dies. Then there is no way I can turn it on.
if unplugged from the power: it starts to boot and it dies again, sometimes at the "samsung boot text", sometimes a bit ahead, but it does not go further than the animated logo with 4 coloured bouncing balls (it does not matter how many time I try to restart the phone)
If plugged: it survives the first part of the boot most of the time, but it loops into the animated logo with the 4 coloured bouncing balls and the phone does not start.
Solution:
Every time I have to re-install Android, by:
- deleting Dalvik, Data, System, Cache.
- Install the ROM
- Apply a factory reset
At this point, if connected to the plug, the phone starts, but I have to go through the manual installation process.
This is a bit annoying I have to admin, anyone with this kind of issue, or am I the only one?
A few more info:
Phone was working great with jamal2367 4.3 (don't remember the baseband)
After 4.4 was out I installed it, but it was booting every 5 minutes or so, I decided then to go back to 4.3.
When I went back to 4.3, baseband was changed, but I kept the hold one.
Phone started to have random reboots as well, but once every 3-4 days, so I was ok with it.
4.4 releases were progressing so, after a while I decided to put it back.
I had the problem described above with previous (recent) baseband (like ml6and mj6).
Now I have the latest, but I have got the problem anyway.
A wild guess:
The phone now charges very quickly, I am wondering if the percentage that I see is realistic. Maybe it runs out of battery, which it could explain why the phone dies on reboots, but it does not explain why it loops once plugged in and why it does not turn off normally instead of just dying with a blink of an eye.
mmm that should not be the reason
Another wild guess:
I couldn't target a specific application. Sometimes it dies using fb, sometimes maps, sometimes hangout, sometimes a after a long phone call. The first two have "location" active, but I don't think that the last two are using it.
mmm that should not be the reason either.
A consideration:
I have noticed that once Android is installed, the phone signal is quite good, but then it goes down to one or two lines only. Most of the time I have one line only (in my area) and when it disappear, 6 times out of 7 it dies.
Thanks in advance.
R
PS=I could not post this into "Galaxy S 4 i9505 Android Development"

too long
be sure to flash from zero, wipe everything then flash 4.3
if everything fils go to stock 4.3 or 4.4 TW, then flash 4.4 gpe after

racoonlab said:
PS=I could not post this into "Galaxy S 4 i9505 Android Development"
Click to expand...
Click to collapse
did you try battery calibration?
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care

anu.cool said:
did you try battery calibration?
Click to expand...
Click to collapse
Nope I will give it a try
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care
Click to expand...
Click to collapse
Well, when I delete Dalvik, Data, System and Cache, I do it once I am inside _teamwin recovery_, I can also think about another ROM, but the one from jamal2367 is quite popular and I find it weird that no one else have the same issue.
Thanks for your reply though.
R

Same problem here...
I fixed it by flashing the stock image from samsung, and start all over again with cf_root and recovery. I use CWM, but that dont matter I think.
Loving my 4.4.2 Rom by Danvdh atm!
Good luck!

opticus44 said:
I fixed it by flashing the stock image from samsung, and start all over again with cf_root and recovery. I use CWM, but that dont matter I think.
Loving my 4.4.2 Rom by Danvdh atm!
Good luck!
Click to expand...
Click to collapse
Hi opticus44,
Did you install the stock image through Kies or from any other link? In this latest case, which one?
Thanks,
R

Hi,
you are not alone. we are 2 now.
I have the same problem but the problem stays with samsung stock rom. my phone still reboot random with stock jelly bean.
i use the 4.3 stock rom from this link below, they have high speed host.
http://www.android-hilfe.de/samsung...tes-rollouts-aktuell-xxuemk9.html#post6803655

Xv1nX said:
Hi,
you are not alone. we are 2 now.
I have the same problem but the problem stays with samsung stock rom. my phone still reboot random with stock jelly bean.
i use the 4.3 stock rom from this link below, they have high speed host.
http://www.android-hilfe.de/samsung...tes-rollouts-aktuell-xxuemk9.html#post6803655
Click to expand...
Click to collapse
mmm there must be some way. With the latest R1.1 I cannot even answer a phone call, with Ktoonsez's Kernel, with Alucard's Kernel no button works.
:-O

mmm also installing 4.3 back gives me random reboots. I am wondering if it could a wrong baseband.

it worked perfect for me for some hours. when i deactivated some bloatwares (g. earth, g. music, ...) it crashed and stucks in a loop reboot & crash at googke logo. swipe cache or wait some minutes don`t change anything.
i tried everything, now i have no idea what to do

I installed CyanogenMod and it is more stable. However it cannot do what is supposed to do, make and receives phone calls.
I wonder if it is a baseband issue, now.
R

anu.cool said:
did you try battery calibration?
also format everything in recovery before flashing,that should do the trick..
or maybe try another rom,if you still have issues then you may have to take it to Samsung care
Click to expand...
Click to collapse
Hi,
What tool do you use for a battery calibration?

racoonlab said:
I installed CyanogenMod and it is more stable. However it cannot do what is supposed to do, make and receives phone calls.
I wonder if it is a baseband issue, now.
R
Click to expand...
Click to collapse
Same issue if I put back Jamal [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1,mmm, maybe the kernel....

The last thing I can say about it is that also all the sounds are gone. I cannot reproduce any sounds, notifications, alarm etc., it does not work on videos either.

I fix my problem! And I shared the solution here:
http://forum.xda-developers.com/showthread.php?p=49502855

racoonlab said:
Hi opticus44,
Did you install the stock image through Kies or from any other link? In this latest case, which one?
Thanks,
R
Click to expand...
Click to collapse
Sorry, long time since I last checked in. I downloaded official stock image from sammobile and flashed through odin.

same problem here
Hi guys same problem here,
GOOGLE EDITION 4.4.2 installed by Danvdh, Kryten2k35 & Ktoonsez on Galaxy S4 GT-9505 LTE with knox 0x1, and TWRP custom recovery when the battery reaches 0% turns off the phone I put the phone on charge and starts but hangs on colored dots.
How can I fix this?
Thx

[Q] Buttons and bottom half of screen unresponsive.

After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?

jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:

x102x96x said:
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:
Click to expand...
Click to collapse
It was an official update so short of rooting it and flashing a new firmware i don't see any other options.

jake262 said:
It was an official update so short of rooting it and flashing a new firmware i don't see any other options.
Click to expand...
Click to collapse
rooting is not necessary for flashing stock rom.

I'm having the same problems. Screen locks up often when I'm browsing in Chrome. For Gods sake this has 3gb of RAM!!!!!
Sent from my Nexus 7 using Tapatalk

x102x96x said:
factory reset won't remove bugs.
cause u didn't have this problem in previous firmware it s not because of hardware.
so try flash compatible stock rom from another region.
if problem remains take it to official service.
:good:
Click to expand...
Click to collapse
ok so i flashed a stock kitkat firnware. the problem is still there.

jake262 said:
ok so i flashed a stock kitkat firnware. the problem is still there.
Click to expand...
Click to collapse
flashed original rom via odin 3.09. Them hard reset. I have the same problem with screen. Is software problem.
Sorry for my bad English.

jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
While phone works just pull out the battery and also don't use cover. I think its just about samsungs politics. ..
Sorry for my English

Same issue
jake262 said:
After the update to 4.4.2 my Galaxy Note 3(unrooted), the buttons(home, power and volume not soft keys) and the bottom half of the screen are sometimes unresponsive. It starts functioning again either after a quick lock and unlock or automatically after a few seconds. Is this a bug in the new update or a problem with the digitizer? I have tried resetting the phone a couple of times. Can someone help me?
Click to expand...
Click to collapse
I also have the exact same problem... I already did the factory reset but no luck. I increased the sensitivity but still happens...Can anyone help us? or it is caused by the recent upgrade of OS to kitkat version... Thanks.

GOOD NEWS!
I have been having this issue as well. Lots of research on the net has provided me with no real solutions. I think there is something missing in this update. I do not know what it is im not that smart but something is wrong across the board.
I have done a master reset back to factory and within minutes of the set up it started lagging/ not responding again. Figured i would give it a few days and well nothing changed so I contacted T-mobile and spoke with Tech Support located in Texas and he concluded that it is an SD card. He says that the SD card was on the phone prior to the update and is causing the issue since its old. WTF! I told him that the processor, ram, HDD, CPU are all considered old now. Personally I think its a stupid response.
I am going to give this a shot anyways. NO SD card no pictures no music.... Already within 15 minutes of no SD card issues are still there. I am really starting to hate this phone because of this update. Hoping to get a replacement (new) with 4.3 still on it. NO UPDATE for me till i know this and several issues are fixed.
I know i could root but i dont feel i should have to to fix any issues.
Has anyone else found a solution or heard of one yet?

Just try this , go to setting / general / power save , swith it on.
Then wait a moment before you try your phone again.
my wife phone got this issue because of over heating.
after switching the power save , the issue is gone.

update... contacted Tmobile within the last hour and apparently this rep said this is a known issue. She contacted Samsung and Google (could be blowing smoke up you know what) but she came back and said they are very aware of the issues and are vigorously working on a fix and your informations will be one of the first ones to get it. She was saying 4.4 (kitkat) screwed up a lot of Samsung devices. BTW she was also having the same problems. All replacement phones will come with 4.4 so exchanging is out of the question.
Regarding the power saving thing ill give it a shot. It was on before the master reset. Noticed it was off when i went in. On now so ill try then.

I9505 random reboots

Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks

juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
You have to uninstall every Knox app, that will stop the reboots
Sent from my Galaxy S4 using Tapatalk

juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Remove all Knox related apps via "Titanium Backup" and you are good to go. :good:

there is also an xposed module that deals with these random reboots, but personally i think the best way is to revert to an earlier firmware. fnb8 is rock solid.

I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.

Yes
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to xxufnb9 ?

I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
nm8 said:
I have just upgraded my firmware to NG8 (UK) and my phone reboots randomly, no matter what I am doing. After receiving a call, using gmaps, etc..
I will try the suggested solution with removing the knox sh*t and report back.
Click to expand...
Click to collapse
wuwinso said:
Yes, same problem here exactly. Any solution to fix this WITHOUT ROOT or reverting back to UGNF ?
Click to expand...
Click to collapse

juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
yup same here after reading this thread and removing all knox crap.... phone has not had a self reboot reboot for the day...

Revert
Had to reflash the old XXUFNB9, it was useless with all those restarts. Downgrade went okey, however need to delete the Media Storage `s cache because it will keep crashing. Testing now if it solved the problem.
Update 1: after 2 hours later no restart so far..
I recommend this solution who doesn`t want to loose everything and risking if a factory reset will solve this issue. There is a problem with the KNOX 2.0 update (XXUGNG8) ...
Update 2: Link for the firmware, for whoever choose to do this way: http://www.sammobile.com/firmwares/3/?download=31852

Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...

juzzy16 said:
I found that uninstalling all knox apps and resetting a private app fixed my problem. I have been restart free for the last 2 days! I suggest using BBS to find out what app is causing wakes and reset them.
Click to expand...
Click to collapse
nm8 said:
Ok, just a quick update, I have used googlemaps for 2 hours, and tomtom navigator for 1 hour on my S4, made and received a few calls without issue. No REBOOTS.. I think it was definitely the knox crap...
Click to expand...
Click to collapse
Stabil for 3 hours or 2 days - well that's for sure great ....
You both must be joking - take older NB8 and you can have an uptime of > 1 month without any problem,
All newer version are worse -
As s.o. mentioned, there is an Xposed Modul made by Thomas Hofmann that tries to solve this. This is not a Knox problem but seems to be in AOSP itself - although might mainly be triggered by Knox 2.0 (NB8 is still Knox 1.0). In general situation goes worse the more processes are started, i.e. with heavy load. It is said to happen not only with S4 but e.g. also with N3.
As Thomas Hofmann stated: "I figured out that actually the system server process crashed due to an ArrayIndexOutOfBoundsException"
If you want to know details plz have a look at Thomas's blog. With his modul he mainly catches a faulty parameter value that would otherwise cause a certain method to crash. As a result he manages to avoid the reboot but of course the real problem goes deeper, so to fix this for real Google / Samsung are needed.
=> I want a 4.4.4 rom with towelroot fixed, without those ArrayIndexOutOfBoundsExceptions and as solid as NB8 - but I doubt Samsung is able or willing to do this.

I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......

Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
nm8 said:
I am using STOCK i9505 4.4.2 ROM which is rooted. I don't use towelroot because I don't have to. I also try to stay away from premade Roms and Kernels beause i don't have time to test and tinker with eveything.
After a few days of removing knoxcrap, I can conclude, that it is the issue with my phone. My i9505 is now working perfectly......
Click to expand...
Click to collapse

no random rebooting anymore xugng8 firmware
juzzy16 said:
Hi! I recently updated my i9505 to the xugng8 firmware via kies. Ever since, my phone has been randomly rebooting itself. The reboots are quick enough, so it doesn't look like the phone is completely rebooting, more like a half reboot. I have tried formating, but that didn't help. I have the phone rooted but using stock firmware.
Any ideas what could be causing this? Thanks
Click to expand...
Click to collapse
i have sorted my i9505 to the xugng8 firmware by re-installing with latest odin...download fresh stock firmware xugng8 firmware and i re-installed 2 weeks now no reboot ,but make sure before you do these steps usb debuging mode is selected ,rest you all know

nm8 said:
I don't use towelroot because I don't have to.
Click to expand...
Click to collapse
Yes, many think this to be a nice 'feature' to get root, but that rediculous. Towelroot (plus the older Exynos bug - but that was Samsung specific) is the biggest bug in Android since many years. Using a kernel that is not hardened against this (this unfortunately includes the otherwise almost perfect NB8 rom) could mean you couldn't be save anymore from someone taking over your phone unnoticed using root authorization.
---------- Post added at 02:20 PM ---------- Previous post was at 02:08 PM ----------
juzzy16 said:
Have to agree with you. Since removing all the knox stuff, Haven't had a reboot since! Been over a week now at this stage!
Click to expand...
Click to collapse
As said those reboots most certaintly are caused by a bug in AOSP code itself - but in fact they seem to be mainly triggered by Knox 2.0. Otherwise a lot more phones other than S4 or N3 should be involved.
As we will never know fpr sure if and when Google/Samsung will solve the real reason of this problem and "removing" Knox 2.0 seems to help, it would be very nice of you (juzzy16, nm8, sneazy) to perhaps add another comment in 2-3 weeks about reboot behaviour again including the rom version you are using and what exactly of Knox you had removed.:good:

[Q] Both cameras not working

Bought an S4 last week. Everything looked good, I tested the sound, vibrate, gps etc and it all checked out. However, stupid me didn't check the camera (I know I know).
So the whole phone seems to run fine, but the camera (front and back) can't be accessed by stock or 3rd party applications. (Usually "warning Camera Failed" or something similar). I've factory reset, cleared cache and everything. I even installed the nandroid backup from a working phone, but the camera gives the same issue.
Because it's both cameras I thought it had to be software, but after all the resets and cache clears I'm starting to lean toward hardware.
Can someone give me an idea where to start? Would it be camera connectors or motherboard? Is there a sensor that may be causing this? I'd like to get an idea before I start gutting my phone.
Thanks.

Try this if it works for you?
https://www.dropbox.com/s/xha0lztrny7923s/Restart_Camera.apk?dl=0
If this does not help, clear RAM with a ram cleaner and try starting the app again?
If that does not help either..flash stock rom via oding
If that does not help..turn the phone off..charge till 100%..turn the phone on..clear the ram..and start camera..
Sent from my GT-I9500 using XDA Free mobile app

Had this same issue a while back. What solved it for me was to re-flash the stock firmware. I too tried a nandroid backup, it didn't work but the flash did.

Turns out it was software related.
I installed a few stock firmwares that didn't fix anything. I didn't want to wait the 2 hours to download for free from Sammobile.com, but eventually i bit the bullet and got the appropriate (latest) version of my phone. After the reboot it was solved.
Granted, I tried many different firmwares, and some had the same name as the official firmware that i downloaded from sammobile but it did the trick.
Thanks for the pointers

[Q] Video recording and video codec problems

I have an extremely persistent set of problems:
1. Unable to record video
- stock camera freezes and the phone restarts (no matter the resolution or storage)
- other camera apps (mx, open, google..) either freezes or acts like its recording but it doesn't
2. While playing some videos, the phone freezes and restarts (in 90% its instagram videos, but sometimes it plays them fine)
What i tried:
- a bunch of roms. The problems probably started with some of them.
- returned to a stock lolipop
- several custom and stock kernels
- a bunch of camera apps
Currently i'm on Audax rom v26.1 with its audax kernel.
Does anyone have idea what could i try?
Could it be a hardware problem? (other than that, camera works fine)
Thanks in advance.

So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian

hayder78 said:
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian
Click to expand...
Click to collapse
Hi Bro,
I have same kind of issue posted here.
https://forum.xda-developers.com/htc-explorer/help/sound-speaker-mic-headphones-hardware-t3608070
Can you help me on this or give some idea?

jmsrajkumar said:
Hi Bro,
I have same kind of issue posted here.
https://forum.xda-developers.com/htc-explorer/help/sound-speaker-mic-headphones-hardware-t3608070
Can you help me on this or give some idea?
Click to expand...
Click to collapse
Hi there,
Sorry, but did not face any issue like that before.
If you have searched a lot for a solution and could not solve it, I suggest that you install this ROM:
https://forum.xda-developers.com/galaxy-note-3/development/purify-cm-13-hlte-n9005-unofficial-cm13-t3337234
This happened to me once after a terrible mistake , which is not related to my above issue. Then I installed this ROM and never looked back. Much snappier phone, lower battery usage and less heated device. I just love it. The only thing that I missed, the better camera app in the stock ROM, and the TouchWiz ability to show multiple apps at the same time.
I strongly suggest that you do a Nandroid backup then give this ROM a try. If you did not like it, you can always return to the Nandroid backup again.
You are frustrated now, like I was. Take a deep breath, and remember that we all went through such bad times with our phone, not just you. This is part of the experience of using such complicated devices. You will solve it eventually, believe me!