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
Related
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:
Hi all.
I got my hands on an LG G2 from verizon which used to be a display model, the problem is it won't charge beyond 38%, it displays a message about the charger not being compatible. So far I've used several chargers with no results
I'd like to know if rooting it and flashing a custom rom would get rid of this message and allow it to charge beyond that cap.
Soon I'll have the official charger anyway.
The second problem I found is that this phone has a different software version than a normal G2, in the end it has a "_DU" so ioroot will not root it as it will not recognize the software version name. This weird software version seems to be for the purpose of downloading an enabling a product showcase animation for using it on display at verizon stores, this animation is downloaded automatically after every factory reset, so it's very annoying, but it can be uninstalled nevertheless. My guess is this "DU" stands for display unit or something similar.
What I'm thinking could solve this problem is flashing an official firmware in download mode (to get rid of the _DU) and then try to root it in the normal way. Later I pretend to install cyanogenmod to see if the charging problem is gone.
Do you guys think this will work? I'm worried this prompt is not related to the rom, but the kernel itself, so uninstalling the stock rom would not work at all. Also, I don't know if it is possible to flash an official firmware just to get rid of the one with de "DU" in the end. I have very little experience with this device in particular.
Otherwise the phone is fully functional in every aspect, so I think this software version is indeed only meant to load the showcase animation. The current Sofware version it has says exactly "VS98011A_DU"
Thanks in advance.
Mr. Dildo said:
Hi all.
I got my hands on an LG G2 from verizon which used to be a display model, the problem is it won't charge beyond 38%, it displays a message about the charger not being compatible. So far I've used several chargers with no results
I'd like to know if rooting it and flashing a custom rom would get rid of this message and allow it to charge beyond that cap.
Soon I'll have the official charger anyway.
The second problem I found is that this phone has a different software version than a normal G2, in the end it has a "_DU" so ioroot will not root it as it will not recognize the software version name. This weird software version seems to be for the purpose of downloading an enabling a product showcase animation for using it on display at verizon stores, this animation is downloaded automatically after every factory reset, so it's very annoying, but it can be uninstalled nevertheless. My guess is this "DU" stands for display unit or something similar.
What I'm thinking could solve this problem is flashing an official firmware in download mode (to get rid of the _DU) and then try to root it in the normal way. Later I pretend to install cyanogenmod to see if the charging problem is gone.
Do you guys think this will work? I'm worried this prompt is not related to the rom, but the kernel itself, so uninstalling the stock rom would not work at all. Also, I don't know if it is possible to flash an official firmware just to get rid of the one with de "DU" in the end. I have very little experience with this device in particular.
Otherwise the phone is fully functional in every aspect, so I think this software version is indeed only meant to load the showcase animation. The current Sofware version it has says exactly "VS98011A_DU"
Thanks in advance.
Click to expand...
Click to collapse
Hey, what happened with the phone ?! Did you manage to root it and fix the battery problem, because i got the same phone, same problem and there is absolutely no info about it...
Probably you bought mr dildo's phone.....
_____________________________Write less read more and be smart
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
Folks I initially tried to root my phone *SM-G935F* using Odin and a CF hero2lte file. The flashing was all good to go with a green pass. Then upon rebooting the phone got stuck on the Samsung logo boot screen with red words at the top that said **Recovery Is Not Seandroid Enforcing**. This being the case all I was able to get into was (Download Mode). I tried to do the samething a few times and gave up after no successful attempts and the phone not being able to successfully reboot.
Fast forward to present I downloaded the phone's firmware which was a zip that contained 4 files (5 total actually because there was another CS file in the event that you wanted to preserve your data etc.). I loaded all of the files in Odin and made an attempt to flash the phone again however it got stuck on *System* and never go to Green *Pass*. So I figured I would try it a couple of more times in case Odin or something just got hung up on the first try. Any how that wasn't the case.
Now with the above being said what did change is when I would try to reboot into *Download Mode* again it said something along the lines of Emergency Smart Switch Recover. I downloaded Smart Switch onto my computer and went through the specific steps to try to Recover the phone using Smart Switch. Now after it was all done I got to the blue screen with the Android and it said *Erasing...* then the phone booted up and its now stuck at the Samsung animation screen. This being said as of current I can now access *Download Mode* and also boot into the black screen or *Recovery Mode* I think its called where I can reboot the phone through a bootloader, power off, factory data wipe / reset, etc etc.
The above being said I have tried the factory reset / wipe. The reboot in bootloader, reboot phone, all with no success.
Also would like to add that before doing all of the above I forgot to tick *USB Debugging* in Developers Mode when the phone was in its normal state. I must also mention that all of this was a first for me and I looked at doing so to try and recover lost data on my phone. Also wanna add that I am not too familiar with ADB or twrp or how to mess with any of that stuff given the limited access I have to my device because it can no longer bootup like it normally would.
I'm currently at a lost of words as to what I can do next as I am out of ideas and could really use some help. I would also be more than happy to donate a little to anyone who is able to help me boot my phone back up and get things back to normal.
Any and all help would be greatly appreciated.
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
Bro would you tell pls , what you did to restore. Thanks
shah22 said:
Bro would you tell pls , what you did to restore. Thanks
Click to expand...
Click to collapse
After me not being successful with the root or with flashing the stock OEM firmware using Odin the phone would get hung up in download mode and the only difference when it would go into download mode it would say to use SmartSwitch Emergency Recover which is what was used and that fixed the issue and the phone rebooted completely fine.
However the above being said I honestly still feel the phone has some small minor issues that I did try to resolve all with no luck. First off when loading to my home screen the icons, and clock, etc etc take about 2 or 3 seconds longer for them to appear on screen than it used like when the phone was new out of the box.
Other thing to note is for some odd reason this issue was thought to be worked out by just booting into recovery mode and doing a factory reset from there, wiping the cache, etc etc. Well this also didn't solve the issue and for some odd reason when performing this the phone didn't reboot on its own.
Basically how it should be normally is after you select that you want to do a factory reset, wipe cache, etc etc, the phone should normally reboot and go through the entire process by itself, however this was not the case. The phone instead went back to the recovery screen and I had to select reboot rather than it normally rebooting on its own.
I've honestly given up on things and given that it is in working order with just a few small minor hiccups I've decided to give the phone to a family member which they plan to use as trade-in credit towards a new Galaxy Note 8.
That being said I will always have a soft spot for the S7 Edge being it was my first smartphone after I had bought a Sony Xperia Z during the same year but returned it the day after because what was to me being poor quality of the Sony phone.
Hmm, looks strange bro , your phone didnt worked after flashing stock rom with odin , and this is the last resort , but you said it was normal before you tried to root , so i guess it was still a software issue other than some hardware problem due to software , but anyways wish you good luck in future , another thing is that my s7 edge has also a very poor build quality , has front camera issues , paint peeling around usb port , wifi issue and high battery degradation , but that happens i guess with today's phones
The version of Odin I used was v3.10.6. I had tried the most current version and a few others, and from the get go for whatever reason this was the only version that would actually pickup the phone being added. Well wait hold on a second the other version would say added when the phone was in but when hitting start nothing would happen, even after waiting an extensive amount of time, also note that the com was highlighted that blue ish color indicating the phone was being recognized by Odin but once again for some odd reason it was only version v3.10.6 that carried out the process of my root attempt and also the attempt I made flashing the original firmware on it.
As for quality the phone had no paint chip or peeling, neither the silver aluminum frame around it either. The build quality was beautiful and up to par with mine. I had a soft spot for my S7 Edge also because it was in the white color which at the time of purchasing was a bit more scarce than the other colors. I purchased the phone from an Amazon.com seller, and during that time I also purchased 2 others from other Amazon sellers but returned those because they had carrier animations for them that were Band LTE or Brand LTE, whatever its called.
This one had no carrier animation upon boot and turned out to be a UK Nougat model. Haven't really seen or came across another one since that would be from a trusted seller or source. Nowadays you never know what you're getting both on eBay and Amazon from these third party sellers.
Yeah thats really strange with odin , its good that you dont have quality issues which struck heavily on me , but yes everyone should be quite careful when ordering online and only should do with trusted resellers
Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?
vini3237 said:
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?
Click to expand...
Click to collapse
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.
Hydranize said:
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.
Click to expand...
Click to collapse
Phone is SM-G935FD
I do not know what caused it, I already got the celuar so, in status it says Custom.
I already tried to blink for odin 3 different Stocks and the same thing continues.
When I got it it could not access the recovery mode, only the download mode was accessible, after flashing the Brazilian Stock 6.0.1 I was able to access recovery mode.
The phone turns on, and hangs at boot, Samsung logo, restarts and stays in infinite looping.
Can it be Hardware?
Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.
Hydranize said:
Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.
Click to expand...
Click to collapse
Ok now i think what was the problem , you didnt enabled usb debugging , and for flashing with odin its a must ! , for guys who want to flash firmware using odin .. please enable usb debugging in developer options or you will have much issues and may also brick your phone , so if you dont want to enable usb debugging or developer options , just use samsung smart switch on pc to flash your firmware.
Yeah that was my issue was I had OEM Unlock checked off and one other thing in Developer Options and forgot to enable USB Debugging leaving me stuck in the process when the phone couldn't reboot normally after the flash attempts. But yeah SmartSwitch Emergency Recovery should definitely be able to fix and resolve the issue if the phone can't reboot normally.
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