Related
Hi all,
My firmware has been the same since the day I bought it, which also was the day of release here in the UK, so it was 2.3.3. Today it said that a firmware upgrade was available, so I selected to download and install it. After a while it rebooted, showed it installing, then booted up normally. I got the main screen again and it said there were more software updates available, so I said to install those too. Again it rebooted, showed installation progress, then when booting up, it now gets permanently stuck on the boot screen where it just shows the Samsung Gaiaxy S II logo (along with the GT-I9100 text). I've left it for over 30 mins and nothing changes. I've tried rebooting several times, both with charging cable in and out, removed the battery for a few minutes and tried again, but it won't get beyond this screen anymore.
I looked at the thread about what to do about this situation (boot loop) which involved erasing user data, so I did this. The message that also came up during erasure said that it wiped the cache too. Tried rebooting after that but it's still stuck.
Is there a way to fix this?
Note that I've never installed custom firmware and never rooted my phone. I also don't have a 32-bit version of Windows, so can't use Odin (it never picks the device up). Plus I don't wish to void the warranty. Is it possible to get the official update zip package which I can flash from the recovery menu?
Thanks
Thom
Is there not a warranty provided by your cell carrier? I know in the us most carriers provide a 1 year warranty with all devices. They would exchange it gladly especially since you did everything by the rules.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.
xijar said:
Is there not a warranty provided by your cell carrier? I know in the us most carriers provide a 1 year warranty with all devices. They would exchange it gladly especially since you did everything by the rules.
Click to expand...
Click to collapse
Yes, it's under standard warranty. I bought it sim-free without being tied to a network. I have already contacted Samsung and they said they'll email me details of the service centre to return it to, but I was hoping for a solution before needing to do that.
Nothing you can do without odin picking the phone up.
I use 64bit windows and it picks up fine, make sure you have the drivers installed (see the link in my sig, for my 4shared, where you can get them) or if you have kies installed you have them but make sure to kill all kies processes first in task manager.
But in the end, best bet is just to send it in, to make sure you dont void your warranty
Sorry this is a mistake.
darkixion said:
Hi all,
My firmware has been the same since the day I bought it, which also was the day of release here in the UK, so it was 2.3.3. Today it said that a firmware upgrade was available, so I selected to download and install it. After a while it rebooted, showed it installing, then booted up normally. I got the main screen again and it said there were more software updates available, so I said to install those too. Again it rebooted, showed installation progress, then when booting up, it now gets permanently stuck on the boot screen where it just shows the Samsung Gaiaxy S II logo (along with the GT-I9100 text). I've left it for over 30 mins and nothing changes. I've tried rebooting several times, both with charging cable in and out, removed the battery for a few minutes and tried again, but it won't get beyond this screen anymore.
I looked at the thread about what to do about this situation (boot loop) which involved erasing user data, so I did this. The message that also came up during erasure said that it wiped the cache too. Tried rebooting after that but it's still stuck.
Is there a way to fix this?
Note that I've never installed custom firmware and never rooted my phone. I also don't have a 32-bit version of Windows, so can't use Odin (it never picks the device up). Plus I don't wish to void the warranty. Is it possible to get the official update zip package which I can flash from the recovery menu?
Thanks
Thom
Click to expand...
Click to collapse
How did you erase user data?
Sent from my GT-I9100 using XDA Premium App
inkyadrian said:
How did you erase user data?
Click to expand...
Click to collapse
When it was switched off, I held down Vol-Up, Home and the power button. There was an option in the menu called "wipe data/factory reset". There's also a "wipe cache partition" option, the action of which is performed in the wipe data option anyway.
Hi guys
I have LTE sm-n9005 32gb from Holland (PHN).
As the Lollipop leaked i flashed it and got an error, hidden.ext4 FAILED!!
Of course phone rebooted and was showing the logo for a long time, so i just plugged the battery off, gave it a few seconds time and put it back.
Phone booted, was working but with glitches (bad reception and no 3G, only GSM or LTE).
I left it as is and now, when the Polish 5.0 was out so i flashed it. This time it went through and showed me PASS! sign, but phone is stuck at logo.
I can't enter recovery, i flashed TWRP and could not wipe because the TWRP failed to mount /data partition.
Then i though maybe i have partition problems, so i flashed MSM8974.pit but nothing changed.
Any idea how to recover the phone?
Solved
Cool that so many people tried to help, but anyway i managed to recover the phone by flashing this ROM
https://mega.co.nz/#!IVAykBTD!-LGw1U9ajSSLPylhdrGVxJzCY5B6_rW0-z3dXWJgSmM
Then on top of it i flashed the Polish Lollipop and it worked. The data from the phone is lost, but the phone itself works like before.
But there was one problem before, and it exists now too: the 3G or 4G networks are not supported. Phone fails to connect, but the GSM one works as expected good.
Did anyone have this problem with the note 3 (EU) ?
Very funny you are. What do you think, people are just sitting here waiting to answer your questions ? Patience.
But you are the 4 millionth person to have this issue, so there are definitely fixes out there, you just have to do some searching.
Ages ago because i was impatientto update my phone so i flashed the Polish Stock using Odin, since then i have used Odin to flash the UK Stock, though when i wipe and reset the phone it still initially comes up with the polish language, (not a massive issue i know but i want to get UK OTA if it ever comes) also if i go to sell the phone at the end of this year when the Note5 is out im sure the new owner would want to turn it on and see english.
Ive tried
Clearing the EFS cache and resetting the phone from recovery before and after flashing BTU
I made sure reactivation lock was off as I wondered if that would cause an issue though that hasn't helped. does anyone have any other ideas?
Im un-routed as i sometimes use my phone to test out corporate BYOD so cant root of flash a custom rom.
thanks all for any help.
ooMoo said:
Ages ago because i was impatientto update my phone so i flashed the Polish Stock using Odin, since then i have used Odin to flash the UK Stock, though when i wipe and reset the phone it still initially comes up with the polish language, (not a massive issue i know but i want to get UK OTA if it ever comes) also if i go to sell the phone at the end of this year when the Note5 is out im sure the new owner would want to turn it on and see english.
Ive tried
Clearing the EFS cache and resetting the phone from recovery before and after flashing BTU
I made sure reactivation lock was off as I wondered if that would cause an issue though that hasn't helped. does anyone have any other ideas?
Im un-routed as i sometimes use my phone to test out corporate BYOD so cant root of flash a custom rom.
thanks all for any help.
Click to expand...
Click to collapse
Download Phone INFO Samsung from Play and check the CSC.
But it might be you are rebooting into DL mode instead of shutting down the phone then starting it in DL mode. I usually remove the battery for a bit and hold the power button for a few secs to make sure the mainboard is completely discharged. Odin (& other methods) all have problems changing BL and Modem if you just do a reboot into DL.
You might want to take a look at Multiboot and Recovery for the possibility of having the ROM you want, rooted etc. AND still have a stock ROM you can choose to boot into for work purposes.
Note 4 Stuck in Boot Loop - Help
I have a Note 4 SM-N910F, never been rooted, stock rom upgraded to 5.1.1 back in October, working fine until yesterday when it got stuck in a Boot loop.
Not sure what caused it but before it got stuck I was messing around with Google Photos which was running a bit slow.
Also I put it on the Qi Charger just before the loop started. It has an aftermarket Fone charger stuck to the battery. I’ve had this and the Qi Charger for 6mths with no problems before now.
It gets to the Samsung page waits a couple of seconds then boots again.
Here’s what I’ve tried - unsuccessfully - to fix the boot loop:
1: recovery mode.
I can get the little recovery text to appear in the top left but after a few seconds it boots again.
2: volume down, home
This gets me to the screen with up/down for continue/cancel.
This is the _only_ screen I can get to stay up without rebooting. It sits there waiting for input.
- Cancel, causes restart, of course, but back into the bootloop
3: Mashing on power button. Banging it, wiggling it, blowing on it.
I read somewhere this could cause a boot loop, but I doubt it is my case because
a. I’ve never had problems with the power button before
b: When I take out the battery and put it back in, it does NOT turn on. If I do the same holding the power button, it powers into the boot loop. So if the button were jammed on I would expect it to never remain off with the battery in.
3: flashing stock rom
I’m not 100% sure what build I had before. I know it was stock 5.1.1 OTA, and I’m pretty sure it was unlocked (my wife bought the phone and i inserted my old sim, but she may have bought it from my carrier and can’t remember)
So anyway I tried all three versions of TPH (unlocked) 5.1.1 from Sammobile.
Installed Odin 3.10.7 and flashed them.
It reboots to recovery but immediately boot loops again.
I doubt its to do with the version of the rom anyway since the symptoms are identical after flashing. Only now the boot loop always shows the little ‘recovery booting...’ text in the top left.
Here’s what I have NOT tried but am thinking about:
A: Re-partition option in Odin
B: Nand Erase All option in Odin
C: Buying a new battery.
On A/B: as far as I can tell what I have done so far should have left the data intact. I’m prepared to wipe all my data if it fixes my phone (no lectures about backups please!) and I’m tempted to do one of these on the off chance that the problem is caused by data or the “disk" problems.
But I don’t want to brick it. Can someone recommend how likely these are to help
And what they actually do?
(Please refrain from responses I see elsewhere like “this will brick your phone if you don’t know what you’re doing”. I don’t know what I’m doing, thats why I’m asking - just the facts please)
On C: the battery seems ok in that the power is solid even after not being plugged in for a long time, but since it was on the Qi Charger with that aftermarket thing stuck to it when it happened, I’m suspicious. Can any one say if this is a likely cause?
If so, it might be worth waiting till I get a new batter before doing A or B (can I wait days for Amazon!?)
[UPDATE] Got a new (genuine) battery at a local electronics store. No dice. Same problem, so it's not the battery. Shall I go ahead and re-partition.
[UPDATE] Got a PIT file from another forum, and flashed again with re-partition checked and PIT loaded. same results.
Is Nand-rease worth trying?
The phone is still under warranty so maybe I can return it.
But in that case I want to erase what's on it first.
thanks for any help
rhubarb
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
You can flash TWRP through ODIN while on COJ5 bootloader. It's locked but you still can flash recoveries and kernel and 5.1.1 ROMS
I am very interested in this thread. I have the EXACT same problem as you have after installing SimplRom, which was a ROM prior to COJ5. It could indeed be that our bootloaders are locked now?
I am using the N910F and just like you, installing any ROM/Custom Recovery/Bootloader/Kernel doesn't help. Perhaps installing a COJ5 ROM might help. I will give that a try, but I've recently used Kies to install the latest official firmware, but it didn't fix the issue.
I will report back here and we'll work on this together to make our phones work again!
Osama lakdawala said:
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Click to expand...
Click to collapse
Thanks but:
1: I have no custom rom. I have never had a custom rom on this device. I want to take it to Samsung, but want to clear the memory first. How can I do that?
2: I _am_ a software engineer_
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
roverrhubarb said:
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Click to expand...
Click to collapse
I have the exact same as you. I did install a custom recovery (multiple) and still get the bootloop. From my tries yesterday, I indeed also suspect it may be a hardware issue. Perhaps to do with the battery/charging port. When I have my device unplugged and try to start in recovery/normalboot, it does not have a bootloop but simply turns off (and then doesn't respond until I pull the battery out). I think a NAND erase wouldn't do anything as I've personally tried that already.
Have you prior (upto a week) before you got the issues had your phone in a moist environment (bathroom while showering for example). I got my problems a week after I accidentally left my phone in the bathroom and installed custom ROM (which was done earlier and had no issues).
I've read online that it may have caused oxidation on the inside and may need some cleaning/drying with alcohol.
I still hold hope that we just have a software issue as download mode is working fine (apart from the Power off not working unless we pull out the battery).
Anybody have any experience with oxidation on their phone? Perhaps have had a similar bootloop due to hardware failure?
roverrhubarb said:
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
Click to expand...
Click to collapse
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
dork997 said:
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
Click to expand...
Click to collapse
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
Since you can get into download mode I'd flash firmware through ODIN again after verifying it's correct.
I'm seeing off the sammobile site for the 910F not all are the COJ5 locked bootloader.
Since you did update in Oct you may be on the COJ3. I'd try one of those and see if it works.
If it doesn't work and stops on the sboot.bin file then you have the COJ5
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
i am sorry i don't know any way to remove personal data other than doing it via recovery. There is an option of "nand erase" in odin it is used while flashing firmware and it wipes everything on the phone but i have never used it (and also don't know whether it can help you or not) ... Senior members kindly help us with this.
Any update to your situation?
very interested as I am in the same situation as you are. Download mode works, recovery+normal boot not. No matter what ROMs/recoveries I install
Same issue I think
I am also in the same situation, although I can enter the recovery mode - home power and volume up - I have tried the wipe cache and then factory wipe to no avail - I have also entered download mode and flashed the stock recovery and even though Odin says pass, it is still in a boot loop. Also when I go to the download screen it has a line saying knox warranty void 0x1(4) does this mean I have voided the warranty even though I only used Odin to flash stock recovery?
Did anyone found a solution
Did anyone ever found a solution to this problem I'm having the exact same issue on a note 4 smn910a
I have a slightly different issue with my Note 4 SM-N910G, wherein am not able to start the phone at all, it is completely dead, if i put the cell phone on charge then also there is no LED on the top but if i connect the device to the PC it does make the connected sound on the PC but Odin is still not able to recognize the device neither kies. I tried draining the power by removing the battery, connected the device to PC without battery and then inserting it but the same problem. Please suggest me any resolution for this dead body am carrying from past few weeks.
hi Op,
did you find any solution for this issue?
Hello all. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
Hope someone can help with some ideas, im really lost how to fix this now.
I have my S4 on the latest stock 5.0.1 Lollipop which is rooted with CFAutoRoot.
I9505XXUHQK1 (edit: Samsung international update 2017 - only installed in a hope to cure the problem in Feb 2018 but made no difference)
Since about last October I have a problem booting about once every 6 weeks, basically it runs great then something starts acting up like you get with all phone, so I do a restart to get things running smoothly again.
It goes through the splash screen no problem, I get the music and it stats booting with the colourful samsung logo with fireworks behind but it just sticks there forever and won't finish a boot, I notice when I get a good boot there is a vibration as it finishes, this vibration never comes when it fails.
The first time, I put changed the recovery to (twrp-3.2.1-0-jfltexx) thinking next time it would be easy wipe the cache and dalvik/art and get it booted, using twrp to clear the cache and dalvik/art did not help so I was forced to reset it again.
Next I noted there was an unexpected update to the S4 from Samsung, I thought applying this update might help things so went ahead and installed it giving my phone all the latest security updates etc, but again the same happened a few weeks later.
Here post 979 (Bootloader, Modem & kernel): https://forum.xda-developers.com/ga...rom-untouched-stock-rom-t3419034/post75164948
I then decided after another painful reset I would keep a weekly Nandroid backup so I could at least get it up and running again quickly.
Last week it failed again, this time I the data icon light would not turn off without clicking through and unticking the checkbox, even then with the data off the green light was on in notification, so a restart and as expected a freeze....
This time I had my Nandroid backup and I had a fresh(ish) Titanium Backup and has backed up my texts and call lists via Samsung so after an hour it was all backup and normal and this time only lost a few days texts and call logs.
Really i'm in a situation where all I can be is spend my life being prepared to restore my phone with good backups but completely unable to prevent it.
My only thought is there must be an app that is playing up during boot, but how do I identify it, the symptoms are never the same (except the boot freeze), no apps are showing high battery use and my battery usage is great, I have hardly used today but it's been off charge since 9am (its now 3.20pm) with 82% left and estimating 27 hours more usage.
Does anyone have any ideas what could be causing this or any tips on how to identify the problem, I would rather spend time fixing it that spend my time preparing for an inevitable recovery.
Thanks in advance for any thoughts.
Edit: Just for info, I regularly reboot it to do a Nandroid backup and it restarts just fine, just fails about once every 6 weeks or so.
I9505XXUHQK1 is meant for branded Greek and German networks only, if your device is unlocked international you will experience problems, especially at boot as it looks to load the branded stuff. Eventually it will give up and just boot.
Although this last update looks all sexy, it's almost identical to XXUHKP2 just a newer security patch and a few minor changes, really not worth the hassle of getting it (or the problems your having).
I believe the latest "MachineX" ROM is built off this firmware which has the branding stuff removed and also links to the correct XXUHQK1 boot loader. Have a look in the ROM section.
cooltt said:
I9505XXUHQK1 is meant for branded Greek and German networks only, if your device is unlocked international you will experience problems, especially at boot as it looks to load the branded stuff. Eventually it will give up and just boot.
Although this last update looks all sexy, it's almost identical to XXUHKP2 just a newer security patch and a few minor changes, really not worth the hassle of getting it (or the problems your having).
I believe the latest "MachineX" ROM is built off this firmware which has the branding stuff removed and also links to the correct XXUHQK1 boot loader. Have a look in the ROM section.
Click to expand...
Click to collapse
Thank you but the I9505XXUHQK1 update is not the issue, the problems started months before this update
I can easily revert this but it is really not the cause of the issues.
are you sure about I9505XXUHQK1? XXU is international unbranded is it not?
XXU= international
H=5.0.1
Q=2017
K=November
1=version 1
Refference:
What do the letter-codes mean?
Example: XXUHPA1 for the I9505
XXU: is the region, in this case international.
H: is the android version, in this case ‘5.0.1’
P: is the year in alphabetical order, P is the 16th letter, thus 2016
A: is the month, again in alphabetical order, thus it’s January.
1: is the revision. In this case 1st
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-s4/general/ref-galaxy-s4-i9505-modems-bootloaders-t3315987
Also:
Samsung bootloader /modem /firmware NAMING:
GT-I9505XXU#(version)
Example: GT-I9505XXUCNE4
GT-I9505 = phone model
XXU = baseband cellular network
XXU is Global and valid almost everywhere, any country regardless of carrier
C = baseband build version
NE4 = version
Version translated
N = year = 2014 (14th letter of alphabet)
E = month of year (May in this case, 5th letter of the alphabet)
4 = build # of that month ( they start 1-9, then letters, A=10,...)
Example:
NE4 = 2014, May, Build 4
NE5 = 2014, May, Build 5
OH2 = 2015, Aug, Build 2
Click to expand...
Click to collapse
kudos1uk said:
Thank you but the I9505XXUHQK1 update is not the issue, the problems started months before this update
I can easily revert this but it is really not the cause of the issues.
are you sure about I9505XXUHQK1? XXU is international unbranded is it not?
XXU= international
H=5.0.1
Q=2017
K=November
1=version 1
Refference:
https://forum.xda-developers.com/galaxy-s4/general/ref-galaxy-s4-i9505-modems-bootloaders-t3315987
Click to expand...
Click to collapse
OK i'll try explain
XXU can mean international as in 2 different branded networks in different countries or regions, understand? Also In with that firmware are the csc codes for the country you;re in, detected off the SIM at start up, sometimes the correct csc codes are loaded sometimes they're not and then you get stuck on boot. This why you should only flash firmware which is device AND region specific.
Anyway, flash XXUHKP2, run it for a few weeks with frequent restarts, if no boot loops then you have your answer.
cooltt said:
OK i'll try explain
Anyway, flash XXUHKP2, run it for a few weeks with frequent restarts, if no boot loops then you have your answer.
Click to expand...
Click to collapse
Thanks but it wont make any difference, I had that for months and was on the phone when this all started, I did several resets and an odin reflash of XXUHKP2 but still had the problem, I only flashed XXUHQK1 a month ago in a last ditch hope it might cure the issue but I have had one boot problem since I installed it.
Both XXUHKP2 & XXUHQK1 behave exactly the same, they work for weeks with no issue, I can reboot as many times as I like without a problem then all of a sudden something will start playing up on the phone (start running slow or unable to turn off data etc) and the restart freezes.
cooltt said:
OK i'll try explain
XXU can mean international as in 2 different branded networks in different countries or regions, understand?
Click to expand...
Click to collapse
You don't need to explain anything XXUHKP2 and XXUHQK1 are both international and will work in almost any country that's what XXU means, not a couple of regions or countries, I don't think Samsung have this classification.
More information, had problems overnight last night.
During the night I was woken by the phone restarting, I looked at it and it was in the middle of preparing all my apps, this normally only happens after a wipe, I left the phone and went to sleep.
I woke this morning to find the phone restarted and asking for my sim pin, my happiness was soon gone as it then asked my which launcher to use and only listed the two Touchwiz, Google Now which I normally use wa not listed. I chose Touchwiz full but after a few second the phone went into a soft reboot loop (not asking for a sim pin).
I did my last nandroid 4 days ago, so I set that going but it failed right at the end with error 255, next I tried an old nandroid I have used twice before but it failed in the same way. Next I did a file system check and restore and reformat (saves personal files), still error 255. Next I reformatted the data partition as a full reformat (this TWRP method deletes personal files) and finally the latest nandroid ran without problems and I'm up and running.
There must have been something wrong with my internal personal files which TWRP was trying to preserve. I actually keep very little on my internal as everything is stored on my external sd.
All this is making me start to think my internal storage may be beginning to fail, on the other hand TWRP check and repair did not find any problems, still at a complete loss what the problem is and every time the issue is slightly different but always points at data corruption causing the bootloop.