Hey guys I'm newly registered to the forum but have always scrolled through various posts to get answers until this bizarre issue.
I have an SM-G935F and as per the title it randomly shuts off and becomes completely unresponsive. If I connect it to a charger it doesn't recognize it and I've tried the pressing the volume down and power button to simulate battery pull, which doesn't work and I can't get into recovery mode or download mode. If I leave the phone overnight and plug it in to charge the next day, it recognizes the charger, I charge it up to 100% and it's fine again and I can get roughly 20 minutes use out of it before the cycle repeats.
The OTA update kept failing so I updated my phone via Odin with the firmware from sammobile (just the BL and AP files), as I've done several times in the past when OTAs have randomly failed. After flashing with odin, I always enter download mode to check it's all official and it now says warranty void: 1 (0x0500) which I know is KNOX being tripped, but I've never rooted my phone. The binary and system status are both official but I'm baffled as to why KNOX has been tripped.
If anyone has any ideas as to what to do to make my phone stop crashing and turning off, (I know you can't reset the KNOX counter so I'm out of luck there, as frustrating as it is) I'd fully appreciate your help. Using a Samsung J3 after my S7 edge is a painful experience
Thanks in advance guys.
Sent from my SM-J320FN using Tapatalk
That's very unusual to trip knox via Odin, was second hand phone?
Maybe try flashing 6.0.1 firmware and hold off updating until 7.0 is sorted.
It was an upgrade on my contract in October so it was brand new.
I'll try to flash 6.0.1 again and see if I have any more luck with it.
I'm tempted to go back to the store and ask for a replacement but I know they'll question the warranty void counter. I'm just so confused as to why it's tripped it.
Sent from my SM-J320FN using Tapatalk
Perhaps is a bad flash reverting back to MM should fix issue but certainly not knox counter.
I'm also awaiting long overdue nougat update and was going to flash via Odin until I read your post. Slightly nerves now wonder if anyone else has had the same issue of tripping knox.
I've just updated via odin and no knox trip, void counter remains the same.
I reverted back to 6.0.1 and the issue still happened which is making me wonder whether or not it's a hardware issue.
I'm going to download a ROM (probably superman rom) and try flashing that through TWRP and see if that fixes it. I won't be able to do it until I'm home tonight but I will get back and update you on how I get on.
I'm glad you successfully flashed 7.0 without any issues, hopefully I'm the only one who has this problem.
Sent from my SM-J320FN using Tapatalk
LukeC981 said:
I reverted back to 6.0.1 and the issue still happened which is making me wonder whether or not it's a hardware issue.
I'm going to download a ROM (probably superman rom) and try flashing that through TWRP and see if that fixes it. I won't be able to do it until I'm home tonight but I will get back and update you on how I get on.
I'm glad you successfully flashed 7.0 without any issues, hopefully I'm the only one who has this problem.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
If the problem occurs on the official ROM, flashing custom one won't help at all. I would recommend you flashing again nougat after wiping all data, system, cache via recovery mode
Sent from my SM-G935F using Tapatalk
dollar7 said:
If the problem occurs on the official ROM, flashing custom one won't help at all. I would recommend you flashing again nougat after wiping all data, system, cache via recovery mode
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
I'll give this a go tonight and see how I get on.
I find it very odd that both 7.0 and 6.0.1 gave the same restarting issues which is why I'm worried it's a hardware issue and not software.
I do have the TWRP file so could flash that, do a dalvik and normal cache wipe too after installing nougat again.
Sent from my SM-J320FN using Tapatalk
So I installed 7.0 again and it is still crashing and becoming a completely unresponsive phone with a black screen. Again, left it over night and plugged in this morning to charge and it's on again. I have absolutely no idea what to do to fix this issue.
Sent from my SM-J320FN using Tapatalk
LukeC981 said:
Hey guys I'm newly registered to the forum but have always scrolled through various posts to get answers until this bizarre issue.
I have an SM-G935F and as per the title it randomly shuts off and becomes completely unresponsive. If I connect it to a charger it doesn't recognize it and I've tried the pressing the volume down and power button to simulate battery pull, which doesn't work and I can't get into recovery mode or download mode. If I leave the phone overnight and plug it in to charge the next day, it recognizes the charger, I charge it up to 100% and it's fine again and I can get roughly 20 minutes use out of it before the cycle repeats.
The OTA update kept failing so I updated my phone via Odin with the firmware from sammobile (just the BL and AP files), as I've done several times in the past when OTAs have randomly failed. After flashing with odin, I always enter download mode to check it's all official and it now says warranty void: 1 (0x0500) which I know is KNOX being tripped, but I've never rooted my phone. The binary and system status are both official but I'm baffled as to why KNOX has been tripped.
If anyone has any ideas as to what to do to make my phone stop crashing and turning off, (I know you can't reset the KNOX counter so I'm out of luck there, as frustrating as it is) I'd fully appreciate your help. Using a Samsung J3 after my S7 edge is a painful experience
Thanks in advance guys.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
Hey buddy it might be because of wrong varient rom flashed so knox may be tripped
Try downlaoding and flashing the original variant and original country rom from samfirmware.com and it might actually do the trick
As for your battery problems, it might be a charger or port problem based on maybe if the cord might be streched more than required accidently or maybe the charger has encountered a fault or power surge so its circuit might have failed to safeguard your phone from over surge of current and over heating.....try using original but substitute charger of someone else
SHREYSTARK said:
Hey buddy it might be because of wrong varient rom flashed so knox may be tripped
Try downlaoding and flashing the original variant and original country rom from samfirmware.com and it might actually do the trick
As for your battery problems, it might be a charger or port problem based on maybe if the cord might be streched more than required accidently or maybe the charger has encountered a fault or power surge so its circuit might have failed to safeguard your phone from over surge of current and over heating.....try using original but substitute charger of someone else
Click to expand...
Click to collapse
Hey mate. Unfortunately I've definitely got the right variants for UK Vodafone, I did use sammobile so I'll give samfirmware a go and see if that fixes it.
The charging thing is an odd one, once the phone boots and is used for 10 or so minutes it will crash, the screen will go black and no matter what trying to reboot, go into recovery or download mode, nothing responds. The only way I've found to get it responding again is if I leave it overnight and plug it in to charge the next day, then it'll start charging and I've tried both mine and my partners cables in both plugs.
I might just take it back to carphone warehouse and tell them whatever has happened during the update has tripped knox and completely ruined my phone, it's only 3 months old to ? they must have a way of finding out if I'd tried to root because if they did, they'd see I've never tried it.
Sent from my SM-J320FN using Tapatalk
LukeC981 said:
Hey mate. Unfortunately I've definitely got the right variants for UK Vodafone, I did use sammobile so I'll give samfirmware a go and see if that fixes it.
The charging thing is an odd one, once the phone boots and is used for 10 or so minutes it will crash, the screen will go black and no matter what trying to reboot, go into recovery or download mode, nothing responds. The only way I've found to get it responding again is if I leave it overnight and plug it in to charge the next day, then it'll start charging and I've tried both mine and my partners cables in both plugs.
I might just take it back to carphone warehouse and tell them whatever has happened during the update has tripped knox and completely ruined my phone, it's only 3 months old to they must have a way of finding out if I'd tried to root because if they did, they'd see I've never tried it.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
Return it. If Stock ROM doesn't fix a problem, the phone is good night
Galactus said:
Return it. If Stock ROM doesn't fix a problem, the phone is good night
Click to expand...
Click to collapse
Since installing Superstock Rom, the phone has, so far, been completely crash free and no random reboots when trying to do something simple like uninstall an app. Fingers crossed it stays this way!
Sent from my SM-G935F using Tapatalk
Search 1st b4 post!
LukeC981 said:
Hey guys I'm newly registered to the forum but have always scrolled through various posts to get answers until this bizarre issue.
I have an SM-G935F and as per the title it randomly shuts off and becomes completely unresponsive. If I connect it to a charger it doesn't recognize it and I've tried the pressing the volume down and power button to simulate battery pull, which doesn't work and I can't get into recovery mode or download mode. If I leave the phone overnight and plug it in to charge the next day, it recognizes the charger, I charge it up to 100% and it's fine again and I can get roughly 20 minutes use out of it before the cycle repeats.
The OTA update kept failing so I updated my phone via Odin with the firmware from sammobile (just the BL and AP files), as I've done several times in the past when OTAs have randomly failed. After flashing with odin, I always enter download mode to check it's all official and it now says warranty void: 1 (0x0500) which I know is KNOX being tripped, but I've never rooted my phone. The binary and system status are both official but I'm baffled as to why KNOX has been tripped.
If anyone has any ideas as to what to do to make my phone stop crashing and turning off, (I know you can't reset the KNOX counter so I'm out of luck there, as frustrating as it is) I'd fully appreciate your help. Using a Samsung J3 after my S7 edge is a painful experience
Thanks in advance guys.
Sent from my SM-J320FN using Tapatalk
Click to expand...
Click to collapse
There's already a thread about this!
Nougat known bugs thread *Updated*
Related
Hi I'm fairly new at this and I've a few questions. I bricked my phone and tried to fix it with kies recovery. Which failed. But obviously from that I got the knox thing. So I fixed it with a PIT file and then I flashed a PDA file via odin from Sam mobile that said I wouldn't be able to downgrade from it, but it works. But when I try run a game or bench mark test my device it will restart and then keep looping on the boot screen. If I take out the battery and then try boot it again it works. I know I've voided my warranty. How would I fix it from restarting? Also would I be able to install a custom rom still or have I blown that by getting the OTA updates?
Sent from my GT-I9505 using xda app-developers app
Boot-loop could also be a faulty battery..? Maybe that causes your device to restart in the first place! You can get a new one from Samsung for free without sending in your phone, they just need serial, IMEI and serial number from battery. I called them 2 days ago to fix this I would do a check just to be sure!
Also see: My phone also hang at the Samsung logo, then rebooted. When I plugged in my charger it suddenly did work. Battery seems to be faulty, waiting for a new one to arrive now!
See: http://forum.xda-developers.com/showthread.php?t=2513767
Hello.
I'm having an International Unlocked Note 3 - SM-9005 using the method in this thread : http://forum.xda-developers.com/showthread.php?p=46511887#post46511887
It's been 2 months now, and there were no problems till now, and since the last 5 days, I've been noting something strange :
Whenever I connect the USB cable for charging, or when I connect the phone using the cable to my PC, the phone keeps rebooting. Continuously. Sometimes it resumes charging after 3 or 4 reboots. Sometimes the loop continues.
The only major changes I have made recently, was installing the Root External 2 Internal app to try swapping the cards. It didn't work fully though. And I have also installed one of those 64GB Sandisk cards. The card seems to work alright.
And I also recently bought a Yoobao 13000mAh YB-651 PowerBank.
I first noticed the reboots when I connected this powerbank at the 4th or 5th time. After that, the problem started whenever I connect the USB cable.
I tried changing the cables, still same result.
I have also tried full factory reset and data/cache wipe at recovery but still no change.
I have tried removing the battery and reinserted, but ditto. Also removing the SD card didn't do anything.
Could it be the powerbank somehow messed up my battery which is causing this problem?
Before I change the battery, I would like to know if the battery is causing this problem.
Today, after the factory reset I noticed the carrier signal is abysmal. Just one or 2 bars, and even complete no-signal. This never happened before, and the bars were almost always full previously from where I'm using it.
All other functions of the phone seems to be working well.
Thank you for any help.
Anyone noticed similar problems?
Flash this and see if it fixes your problems:
http://forum.xda-developers.com/showthread.php?t=2507403
Download the zip and flash it in CWM
zylor said:
Flash this and see if it fixes your problems:
http://forum.xda-developers.com/showthread.php?t=2507403
Download the zip and flash it in CWM
Click to expand...
Click to collapse
Thanks.
Is it safe to flash that in my phone? Currently my phone is working good. Except for the sudden drop in the carrier signal reception quality recently.
It's only when I connect a USB cable to the phone that it goes into continuous reboot loops. If I remove the cable or switch off the power source, then it goes away.
It does not have the random reboots as reported by some.
It goes out of the loop if I remove the cable and reconnect while it's rebooting, and then I can continue using it as it charges.
It's weird and annoying.
Currently I have already flashed the latest official rom from Samsung. And the knox is maintained at 0x0. And the System Status is Official.
Well if you still have it with knox untouched, go to a Samsung Repair Center...
zylor said:
Well if you still have it with knox untouched, go to a Samsung Repair Center...
Click to expand...
Click to collapse
Yes, I'm going to the Service Centre tomorrow. Thank You.
Hmm...I just noticed something.. the reboot problem went away after I removed and reinserted the SIM card....
The problem re-appeared.
So I just sent it to the Samsung Service Centre.
Took 4 days. They said that they have changed the PBA (Phone Board Assembly?).
Now everything's good.
Fortunately I didn't trip the knox, and my phone was still under warranty, even after rooting as I have mentioned in the link in my first post. I flashed the latest official rom to make the Device Status to Official again, before sending the phone for service.
And how do I edit the title of this thread? I would like to add "Solved" to it. Thanks.
The problem re-appeared.
So I just sent it to the Samsung Service Centre.
Took 4 days. They said that they have changed the PBA (Phone Board Assembly?).
Now everything's good.
Fortunately I didn't trip the knox, and my phone was still under warranty, even after rooting as I have mentioned in the link in my first post. I flashed the latest official rom to make the Device Status to Official again, before sending the phone for service.
And how do I edit the title of this thread? I would like to add "Solved" to it. Thanks.
please go in the developers settings and turn off debug usb
i had a similar problem with mine using win7 on vmware
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
KalarAzar said:
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Repulsa said:
hello mate, what bootloader do you have?(Boot into download mode too see if it says Knox void warranty or not) and can you still boot into download mode? thanks
Click to expand...
Click to collapse
Hi and thanks for your reply,
I can boot into download mode - one of the only things I can do! - and it says 0x1 under KNOX WARRANTY VOID, so yes it is showing Knox void.
Just in case you need it, the full information shown on the screen in download mode is as follows:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thanks again..
KalarAzar said:
Thanks again..
Click to expand...
Click to collapse
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Repulsa said:
I want you to flash the 4.3 stock rom firmware from samsung (Sign up)www.sammobile.com/firmwares/1/ make sure to choose the right one such as device, country . Then when your done flash the file via odin 3.09 and select AP ,Or follow the instruction from here, how to do a proper flash. http://forum.xda-developers.com/showthread.php?t=2252982 . have a nice day.
Click to expand...
Click to collapse
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
KalarAzar said:
Hey Repulsa,
Thanks again. Unfortunately, this is what I did. I signed up at samfirmware and downloaded the file: I9505XXUEMK8_I9505BTUEMK5_BTU.zip
The only thing I did different was that I used Odin 3.07 and flashed using the PDA option, but I'm presuming this is the same thing..? After the bootloop, I went into recovery and factory reset, but still the bootloop occurs.
I have since managed to get into my phone after leaving it off for a couple of hours again and looking through the settings it says I have "Samsung" as the secure boot status and "Official" as the device status. The build number is showing up as JSS15J.I9505XXUEMK8 on Android 4.3.
Should I try anything else that you can think of?
Thanks again for the reply.
Click to expand...
Click to collapse
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Repulsa said:
is the problem still persist? if it does Turn off your phone and Press and hold Power+Volume up and do another Wipe cache and Factory reset.
Click to expand...
Click to collapse
Yes, I'm afraid it does, and I have already done the wipe cache and factory reset, but no joy. I did it again anyway and on reboot it went back into the bootloop again, I'm afraid..
KalarAzar said:
Hey everyone,
So, I'm pretty new to Android having had the past two iterations of the Nexus 7 and decided to take the leap from an iPhone (which I had jailbroken) to a Samsung Galaxy S4 GT-I9505 LTE, which I bought unlocked and outright.
I ran stock TouchWiz for a while and then wanted to play, so installed FoxHound 3.2. This worked fine for some time, but then I started getting random reboots which seemed to coincide with listening to music on the device. After a while the reboots suddenly became more regular and it got so I couldn't even open WhatsApp without it either restarting or going into a bootloop. Usually, if it went into a bootloop and I tried starting the phone straight away it would fail, but if I left it off for some time it would start up okay, only to reboot again later if I used it for anything. I also noticed the battery draining quickly.
I tried flashing the device with various other ROMs - PACMan, Google AOKP, etc. - but got the same issue. Many times, the system would crash just when I first started to setup the phone. I finally determined the reason it was crashing at the initial startup was that it was when WiFi was being enabled. So, I ended up following a fruitless several hours of attempting to fix the WiFi using files provided on this page: http://forum.xda-developers.com/showthread.php?t=2192025. I tried XXUDMH8, XXUEMJ7 and XXUEMK8 all to no avail - I installed both the firmware and the WiFi fix files using Odin and thought I had it cracked, only for my phone to eventually reboot again whilst WiFi was not even enabled - it did take a bit longer this time though, admittedly, but it still rebooted and went into a bootloop.
So, I finally followed this page: http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/ to completely return my device to stock TouchWiz, but still no joy.
I have tried factory resetting the device and wiping all cache from the stock recovery and from Philz CWM (which I had while using the custom ROMs), but this does nothing.
I tried connecting my device to Kies now that I have the stock TouchWiz ROM back on the device, but it is now rebooting even more frequently and I can't get in long enough to run the emergency firmware recovery. It used to stay up longer (sometimes indefinitely) when connected to the PC via the Samsung factory cable or to a power supply with the Samsung charger, but now it is even rebooting when plugged in.
I am extremely worried that my device that cost me nearly £600 a few months ago is bricked for good. I did (understandably) think that returning it to default would've resolved the issue, but even this has failed.
Is there ANYTHING else I can try that I have not already........?
Click to expand...
Click to collapse
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Acer4605 said:
it can be a bad battery aswell if your battery serial starts with BD exchange it asap you may also experience any issues mentioned in this thread http://forum.xda-developers.com/showthread.php?t=2570608
Click to expand...
Click to collapse
Ah FFS. My battery serial does start with BD and I was wondering if it was a battery issue, but didn't want to replace it if the fault was wider spread. I guess I may have to try this then..
I'm just flashing to MJ7 right now, but if it reboots again I will see about a new battery from where I bought it on Monday
And, as I forgot to say in the last post: thanks for your reply. If this fixes it, much kudos, my friend..
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
KalarAzar said:
Yep. The flashing of MJ7 did not work. Maybe my battery is a dud as it went straight back into a bootloop at the Samsung logo.
Carphone Warehouse visit on Monday methinks..
Click to expand...
Click to collapse
you can get passed the samsung logo if you boot while your charger is connected to the phone, the battery might swell as well or is already bigger then it originally was
My phone has been randomly shutting down over the past couple of days and the only way I can get it to boot is to connect a charger/cable to pc. I've tried different ROMs and returning to stock. No joy.
I guess my battery could well be the problem
---------- Post added at 11:33 AM ---------- Previous post was at 11:28 AM ----------
My phone has randomly started shutting down over the past couple of days and the only way I can get it to boot is to connect charger/cable to pc. When it dies, it also loses all of my wifi passwords. It's a bit of a head scratcher. Any help appreciated
Definately the battery, dude
I was experiencing the same problems, and I observed that the battery swollen. So I replaced it and now the phone is functioning properly. Do not wait for the battery to modify its volume because you are risking to put pressure on the display and crack it. Beware.
Was, indeed, the battery
Hey everyone,
Just to let you know that I went back to Phones4u with the receipt from September (when I bought the new phone) and they filled out a form to request a new battery from Samsung and replaced mine their and then in the shop with a new battery from another Samsung Galaxy S4.
My old battery did, indeed, have a serial number that started with BD and the new one starts with AA so hopefully I am now sorted.
Massive thanks to everyone who replied and hopefully this thread will save someone else the time and lost data that flashing ROMs can incur.
Cheers,
A very happy Steve :laugh:
Successful Recovery Note7 from last Samsung "Death Update" Disabled Battery Charging!
Ok, so here it goes, Im getting one more piece of Note7, addictive, I know... this piece has latest samsung's "Death Update" installed, thus its reportedly only working while plugged in with usb cable or charger but otherwise does not charge battery anywhere beyond 0%... so thats that.
My goal is to root this unit, and install custom rom (like hydra rom) and after probably reflash with ODIN with earlier version that did not have battery charging @ 0% cap , then again root the phone, install root package blocking program and just run stock rooted rom with updates disabled, thus having battery charging feature enabled. Ultimately my options of course are to attempt retrofit another battery to it like one discussed here in this thread:
https://forum.xda-developers.com/note-7/themes/note7-battery-swap-mod-note5-s6-s7e-t3545371
, since the model Im receiving has no warranty and it is already refunded unit to the original owner but was "written off" by samsung or whatever you call it, I dont care as long as I get it, I know me trading it in for S7e even aint an option so its going to be my test-unit for DIY and such.
Im wondering would charging features still be disabled if phone was powered via Download / Recovery modes? Anybody had first hand experience? Otherwise, is there anything else in place after the latest death update that prevents phone from being rooted and alternatively flashed with custom recovery/rom to enable charging?
Mega curious...
Hope ya'll having great weekend people
Mr.Ultimate said:
Ok, so here it goes, Im getting one more piece of Note7, addictive, I know... this piece has latest samsung's "Death Update" installed, thus its reportedly only working while plugged in with usb cable or charger but otherwise does not charge battery anywhere beyond 0%... so thats that.
My goal is to root this unit, and install custom rom (like hydra rom) and after probably reflash with ODIN with earlier version that did not have battery charging @ 0% cap , then again root the phone, install root package blocking program and just run stock rooted rom with updates disabled, thus having battery charging feature enabled. Ultimately my options of course are to attempt retrofit another battery to it like one discussed here in this thread:
https://forum.xda-developers.com/note-7/themes/note7-battery-swap-mod-note5-s6-s7e-t3545371
, since the model Im receiving has no warranty and it is already refunded unit to the original owner but was "written off" by samsung or whatever you call it, I dont care as long as I get it, I know me trading it in for S7e even aint an option so its going to be my test-unit for DIY and such.
Im wondering would charging features still be disabled if phone was powered via Download / Recovery modes? Anybody had first hand experience? Otherwise, is there anything else in place after the latest death update that prevents phone from being rooted and alternatively flashed with custom recovery/rom to enable charging?
Mega curious...
Hope ya'll having great weekend people
Click to expand...
Click to collapse
Not sure why you think that retrofitting a battery would allow the device to charge. The update on your device is what is preventing the charge cycle and also is stopping the device from using any radios.
You need to try to flash via Odin a complete rom, probably the last version that had the battery limited.
If you can manage this then you should be disable oem unlock under developer options and then install hydra by following the detailed instructions.
clearbox said:
Not sure why you think that retrofitting a battery would allow the device to charge. The update on your device is what is preventing the charge cycle and also is stopping the device from using any radios.
You need to try to flash via Odin a complete rom, probably the last version that had the battery limited.
If you can manage this then you should be disable oem unlock under developer options and then install hydra by following the detailed instructions.
Click to expand...
Click to collapse
Battery retrofitting mod is not to get battery charging - is to keep note7 fail-proof, and with this specific unit that Im talking about it is especially the case only after getting it back to firmware that did not have it bricked.
I know about "OEM unlock" feature in dev mode is a must before any software tampering, so thats not an issue. I am aware phone works while on cable, so I should be able to navigate and activate OEM Unlock from dev menu, also I should be able to do straight ODIN flash with firmware that is of an earlier version without any battery cap's , so my question still remains - is there anything in this latest deadly update from samsung that prevents ODIN from flashing anything to the phone, or is it just charging orientated?
we shall all see once it comes across, should be following week, Im actually eager to start working with it. May as well just go ahead and order myself a S7 battery too so less time to waste waiting
I have a Note 7 that's on the "Death update".
1) Phone cannot be charge in normal mode or download mode.
2) I did not check on whether it could still function with a cable plug in.
3) Attempting to flash older Samsung firmware from ODIN will not work. It will give some errors and stop there.
4) Could not flash anything through ODIN. BL, CSC, CP, AP could not be flash into the phone.
5) Could not flash recovery from ODIN either.
6) Enabling OEM unlock doesn't help in anything. See point 3 and 4 above.
Hope the above helps.
teslapolaris said:
I have a Note 7 that's on the "Death update".
1) Phone cannot be charge in normal mode or download mode.
2) I did not check on whether it could still function with a cable plug in.
3) Attempting to flash older Samsung firmware from ODIN will not work. It will give some errors and stop there.
4) Could not flash anything through ODIN. BL, CSC, CP, AP could not be flash into the phone.
5) Could not flash recovery from ODIN either.
6) Enabling OEM unlock doesn't help in anything. See point 3 and 4 above.
Hope the above helps.
Click to expand...
Click to collapse
Vey well, I have some extra ideas too, we shall see
Besides, what are your current plans for your note7?
are you willing to sell it by any chance?
Mr.Ultimate said:
Besides, what are your current plans for your note7?
are you willing to sell it by any chance?
Click to expand...
Click to collapse
I'm hoping to revive the Note 7 and use it if this is possible at all.
Won't mind selling if there are no other option.
Ok, so got my disabled charging note7, it has about 24% battery remaining and it stays this way if I keep it plugged in on USB or on wireless charger.
I tried flashing TWRP both versions available, both had flashed OK with ODIN however, it still has standard recovery...? wtf...
I remember my S7edge did have very similar behavior, odin would flash TWRP just perfectly fine but when going in to recovery on the phone it still starts in standard recovery, and this would continue until I flashed CF-Autoroot IMG.TAR file , but this time I cannot find it anywhere for note7....
Im thinking trying KingoRoot or OneClickRoot tools but I wanna hold back a little before I launch on those.
Ok good news (so far) , flashed custom kernel via ODIN, worked, but now I figured phone takes charge again while phone is off just on USB, so charge disable mode is within latest kernel update only.
I can still enter my standard recovery and do all I want there (havent tried factory reset yet!)
When powered off from recovery, phone began charging! now I have noticed it went from 23% to 24% and it is showing it is charging, where as before it would vibrate for second when plugged in and then show battery symbol which soon after would go offline and phone would be unresponsive like it is not plugged in - in not charging state. So for now 1:0 me vs note7
EDIT!
YESSS! IT IS CHARGING! NOW @ 26%!!!
Now @ 30% ... ok I should let it charge to 50% and then try perform more firmware DIY
ok, I will confess, I could not wait any longer, thought screw this sh*t, went in to recovery and wiped cache/factory reset, rebooted phone, then witness phone startup OK, welcome wizard started OK with 30% on battery and indicator on shows On-charge thought "yess!!!" , then I get this notification about battery is gonna run out and no longer recharge blah blah blah, but hey , it still charges and now Im at 33%
Yes, latest firmware and custom kernel and VIOLA , note7 is back in the game!
Also got this notification from device security thing asking me to reboot phone to try undo the changes... I guess I will not try just yet out of curiosity will try again to do TWRP reflash, this time it should work
Confirmed, now TWRP flash via ODIN worked liek a charm, so I should root via TWRP now and see if I can disable something in current latest software to disable these notifications playing around now
ok now rooted and lots knox stuff disabled with package disabler and etc, still getting this one notification about discharging battery warning when plugged in, anyone could advice me which file to edit in system root to bypass this?
Thanks
Wow, that's great. I've been trying for weeks but unable to get through to anything. Will it be possible to share on how you get to flash TWRP successfully? Thanks
---------- Post added at 12:36 AM ---------- Previous post was at 12:32 AM ----------
Mr.Ultimate said:
ok now rooted and lots knox stuff disabled with package disabler and etc, still getting this one notification about discharging battery warning when plugged in, anyone could advice me which file to edit in system root to bypass this?
Thanks
Click to expand...
Click to collapse
I'm don't know about the editing stuff but if you could get TWRP to work, wouldn't it be simpler to flash custom ROM that already have KNOX etc disabled?
I was disabling all kind of random packages just to see what results will I get from doing it all , was expecting to somehow find package that relates to USB/wireless pad power circuit monitoring so I could work on it while maintaining the latest patched firmware but no nagging popups every time phone is powered on or plugged in to USB/wireles pad. Otherwise I observe phone is 99.99% perfect aside from the notification that I have described and security centre prompts warning time to time that device has been modified , click restart to undo-modification, which I actually tried and it undone-nothing, so it is permanently patched this way regardless what you try to do within the phone now.
I am in favor of keeping stock rom and stock appearance of note7 as much as possible.... dont know if it makes much sense but I love the way note7 is... with all functions working as much as possible as close to standard as much as possible, so thats why my reasoning trying to make this latest rom work.
I have few firmwares which were the original ones V.1 and V.2 but not V.3, which is what I have, so even if I install custom rom now, there is no way going back to factory firmware since V.3 full factory rom is nowhere to be found.
I am going to look in to ways on how to extract entire current firmware so I can go and learn a bit and maybe do few ROM builds myself, this is actually exciting now once I got this far.
Able to link me to the custom Kernel that you use?
teslapolaris said:
Able to link me to the custom Kernel that you use?
Click to expand...
Click to collapse
do it on your own risk folks, I mean - enjoy...
https://www.androidfilehost.com/?w=files&flid=98347
Mr.Ultimate said:
do it on your own risk folks, I mean - enjoy...
https://www.androidfilehost.com/?w=files&flid=98347
Click to expand...
Click to collapse
Thanks. It works!!!. Thank you so much.
I managed to flash TWRP and Hydra ROM onto it. Everything works except mobile network. Somehow it is unable to detect the SIM card.
Will fiddle with it further. Hopefully I could get it up and running.
Thanks again.
only downside I see so far with current latest kill firmware and this patched kernel are those nagging notifications regardless battery charging to 100% ok, security center notification about modifications and about restart with attempt undoing them, which obviously will fail anyway anytime, and just now noticed it takes a little more time to activate wifi to show available networks, usually its instant, like 0.1second, and now its like 3-5 second delay once switch is toggled to ON position. Also, found out that when network sim card inserted, now phone prompts for network customization and asks to restart now or later to apply settings changes, and I tried restarting but this keeps coming on anyway, so finding the service package and disabling it solves this issue.
Besides no any network issues here, signal comes on every time I change sim cards around and all connectivity is there with data and all is OK, maybe try different kernel? I tried one with APO ,mine is European exynos SM-N930F model
I tried out Hydra kernel but it didn't work. Then I found this https://forum.xda-developers.com/note-7/how-to/spacex7-rom-kernel-kill-galaxy-note7-t3536693. I flash it and my SIM card works again.
This may help someone
Hi.
As I've read that there are people in the forum with problems after the last update from samsung, I decided to write my experience.
My first Note 7 was the Hong Kong version. It was amazing, because it had an fm radio built in, but of corse I couldn't flsh a costum rom on it, as there as none in the forum. In time, a gave up and send it to samsung, and I am glad for, since by now, I would have a death phone.
Anyway, after 2 months with a s7 edge, I found a person selling is international note 7, cause he would go to Brasil, and was afraid to had it apprehended at the aeroport. So I bought it, even with the limited charge at 60% problem.
First, I tried the Dr. Keatan rom, but the limited battery charge still persisted.
So I tried the TEKXodus rom, and I say its amazing.
My phone now as the batery charging to 100%, and even the shealth works fine, if you don't update it.
If it as an automatic update by google, just downgrad it and is fine.
When I received the samsung notification for the last update, I just needed to be sure that the update function was turn off, that the processes in the background were off too, and, with titanium backup, to freeze 2 "urgent update" apks.
Everything works fine.
So, for those who have problems, I recommend the TEKXodus rom.
Best regards
Hi All,
So, I have spent 2 days trying to get my Galaxy s8+ back to normal. However, I seem to only have made it worse. It all happened when I decided to change the /data partition from ext4 to another format and then back again to get the /data partition to mount in TWRP after flashing Pascal Rom. However when I rebooted, nothing worked, no boot up screen, no recovery, no life, but all I could get was download mode. It then must of froze up after another restart and I couldn't get anything for 12 hours or so.
The next step I tried once i got download mode again was to flash stock firmware for the G955F, I can't remember the version of this firmware, but I still had nothing change. So then i flashed the latest firmware from SamFirm's downloading client, which was G955FXXU2CRF7 - Australian Optus Branded Firmware (OPS). I was able to get as far as the "hello start screen" and then my phone restarted, it then tried to upgrade my system again, then started "erasing" and then it rebooted and I still had the same issue, nothing but download mode and still no recovery, it still wouldn't turn on. So I flashed the latest International/Unbranded Australian firmware (XSA) - G955FXXU3CRGH, still the same result. I now can't go back to the OPS version of firmware because I get the Check error with the bootloader (since it's a more recent version), so I can't go backwards. I also can only flash "Official Binaries" now. Oh and to make things worse, I read that Odin Option "Nand Erase" just erased user data, so I thought I might as well try it, and as a result, I now can't flash even the (XSA) firmware because of ODIN failing and I now have an "An Error has Occurred while updating the device software. Use the emergency recovery function in the smart switch PC Software.". I am a bloody idiot :good: . Oh, I have tried multiple versions of Both Samsung Kies & Smart Switch (Which both had the option for "recovery & initialisation"), however, I get a message that my device is unsupported after adding in my device model and S/N. I tried a PIT file and then found out it's now included in all the latest firmware img files.. so yeah lol. Fun times. Soooo I feel like I am out of Options, nothing I do is working. The worst of all this is my wife is not happy haha which means after years of tinkering with android phones (flashing custom ROMS, Kernels, Root Solutions, e.c.t ), this may be the end of the road for me if I can't fix this phone. I really hope this thread isn't true too : https://forum.xda-developers.com/galaxy-s8+/help/sm-g955fd-access-download-mode-t3748228
So Please, someone help me out if it is at all fixable even if it requires opening the phone up lol.
The stats i have on download mode are the following:
RMM State as Prenormal
OEM Lock: OFF
FRP Lock: OFF
CARRIER_ID: OPS (which is super weird because it only accepts XSA to be flashed :S )
Secure download: Enabled
System Status: Custom
Warranty Void: 1
Current Binary: Samsun Official
If you need more, just let me know.
Ok, quick update: I have got rid of the error that I mentioned. I managed to flash XSA firmware again, it went to the blue Andriod is updating the system screen, then started "erasing" then rebooted and nothing again, still only download mode available. Nothing happens when I try to turn it on or try recovery mode.
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Quick Update: Maybe Fixed now!
Even though no one has replied yet, as it's only been an hour or so. I just wanted to let anyone else know who is experiencing a similar issue in the future on how to possibly fix it.
This was a real nightmare, however quick disclaimer, I am not responsible for any damage incurred to your device/property by following my instructions.
So the way I have fixed it, is I flashed the AP file only (from the firmware zip i had downloaded from SamFirm) with "Auto Reboot" Off. When ODIN finished, I held the Vol Down + power button, to reset it. It gave me a blue "No Command" Screen, I then waited and it then went black and the recovery screen appeared. I cleared the cache, rebooted to bootloader, which it didn't turn back on, so I left it because I thought it was the same thing. Came back 10 mins later and turned it on (or hard restarted, can't remember) and it worked. It booted!
I did soon learn it looks like it was having a charging problem because it had no charge and kept telling me there was water in the port (even though it was dry), I restarted it again after putting it on a wireless charging pad and it is seeming fine so far with the USB charger. So big note to anyone in the future, that it could be possibly bugging out with charging as well if you can't get it back on. I did have the device tell me here and there the last two days that there was water in the port when it was off. So kinda weird.
I know this all sounds a little hocus pocus, superstitious almost, but hey, my phone is working, so maybe replicating my actions may just help lol. :cyclops:
spawnlives said:
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Click to expand...
Click to collapse
Oh right, well, I did hear that SamFirm is not supported anymore, as that's where that firmware came from. Maybe it's dishing out incorrect firmware now? Possible the structure of where ever it is getting its firmware from (pretty sure it's pulled from samsung) has possibly been altered?
Just for reference I use www.updato.com for downloading firmware it is usually up to date. No reference to the firmware you mentioned (not for Australia anyway)
The screenshot I took: Imgur link:
https://imgur.com/a/lqyzWW7
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
spawnlives said:
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
Click to expand...
Click to collapse
Yeah, it's seeming to work now, but my fast charge isn't working. However, my other oreo ROM didn't work with fast charge either. So i am unsure if it is my phone or an orio bug :/ lol
Well at least you got it working and not using as a door stop
that was really sad story man.....
spawnlives said:
Well at least you got it working and not using as a door stop
Click to expand...
Click to collapse
Yeah haha, so glad it's not a door stop haha