Database Users

Note3 SM-9005 Continuous Reboot Loop When USB Wire Is Connected for Charging or to PC

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

[Q] Phone rebooting randomly - help needed

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:

Yotaphone 2 reboots by itself after after the screen switches off.

Hello
I have a Yotaphone 2 running android 5.0. I have a huge problem with the device which is, that the phone reboots automatically all by itself after the screen turns off. The screen timeout is set at 1 minute and once the screen goes off, the phone reboots! I don't know what the problem is but its making me crazy!
Note: The phone does not reboot if the screen doesn't turn off. So I changed the screen timeout to 30minutes. Also note that Wi-Fi doesn't start immediately. It doesn't even start most of the time and is stuck at "turning on"! And also, the phone isn't detecting my SIM Card!
Hope someone can solve my problem.

Wow, seems a lot of problems here. However you provided very few info about your phone.
1) Where did you buy it?
2) What have you done after you opened it, OTA? Which firmware was installed?
3) Have you tried factory reset by wiping data in the stock recovery? (Accessible with Vol+ and Power)
4) Have you tried to flash from scratch the RU .124 firmware with YotaFlasher?
5) The phone was behaving normally before or it's doing this as soon as you started using it?

I got the phone as a gift
TheArt. said:
Wow, seems a lot of problems here. However you provided very few info about your phone.
1) Where did you buy it?
2) What have you done after you opened it, OTA? Which firmware was installed?
3) Have you tried factory reset by wiping data in the stock recovery? (Accessible with Vol+ and Power)
4) Have you tried to flash from scratch the RU .124 firmware with YotaFlasher?
5) The phone was behaving normally before or it's doing this as soon as you started using it?
Click to expand...
Click to collapse
-The phone was a gift from "Aramex Company".
-Yes, I have factory reset it! Note: It wasn't possible to reset it from settings because it would always get stuck in "Shutting Down" phase and nothing would happen. So I hard reset it.
-I found something strange going on though. Whenever I reset it, It would restart (after the reset is over) and say that "ANDROID IS UPGRADED TO 5.0".
I think it is upgrading by itself to 5.0.
-No, I haven't tried any flashing.
-Yes, the phone was working fine for a while and then started behaving like this!
Cheers!
(Thank You for your support and attention by the way)

Video
Hello!
I have made a video showing what the problems are! Please give me your e-mail so that I can send you the "Dropbox" link to the video.
Thank You!

I think the first thing to do here is to flash a clean firmware (RU or EU) on your phone via YotaFlasher, search here on xda how, and then report back if it's happen again! Seems that the firmware it was shipped with wansn't so stable.

Flashed it!
TheArt. said:
I think the first thing to do here is to flash a clean firmware (RU or EU) on your phone via YotaFlasher, search here on xda how, and then report back if it's happen again! Seems that the firmware it was shipped with wansn't so stable.
Click to expand...
Click to collapse
Hey!
As you had prescribed, I flashed it! First I flashed it with Android 5.0.0-ME1.1.60 and after opening the phone I used it for a while and the phone was same as before flashing! There was no difference at all! The phone was restarting on turning screen off as usual, the WiFi wasn't turning on, and the SIM wasn't being recognized!
But then I flashed it with Android 4.4.3-S01-003-ME1.0.3.61a and the phone is still rebooting by itself upon switching the screen off and the WiFi problem still persists! The WiFi just simply won't turn on. It's stuck at "turning on"! The SIM isn't recognized either! Also, the phone is restarting from the inside now (It wasn't restarting before. I had to keep the power button pressed every time I wanted to restart)! But NOTE that the phone still cannot be just shut down, it can only be restarted!
I don't know what to do!
Cheers

can you please help me find 4.4.3-S01-003-ME1.0.3.61a firmware. i tried yotaflasher and i cant make the program work. it exits close itself. i couldnt find any firmware folder in yotadevices ftp too. can you help me found the spesific firmware please?

Why are you unable to make yotaflasher work
lgk350tr said:
can you please help me find 4.4.3-S01-003-ME1.0.3.61a firmware. i tried yotaflasher and i cant make the program work. it exits close itself. i couldnt find any firmware folder in yotadevices ftp too. can you help me found the spesific firmware please?
Click to expand...
Click to collapse
Hi lgk350tr,
Why are you unable to make yotaflasher work, it is a pretty simple application. Have you tried to see instruction videos on YouTube on how to use it? Instructions are also available on XDA Developers' website. ( https://forum.xda-developers.com/yotaphone-one/general/yota-flasher-download-t3480922 )
Don't hesitate to contact, for any problem!
Cheerio

Please help..................I spent 800 USD on this phone and I can't use it
Can someone freaking help me with my phone's problem, I have spent 800 US Dollars buying that phone, and I can't even use it! It has been 6 months since I opened this thread and no one has helped me yet!
PLEASE HELP..............................................................:crying::crying::crying:

akahomeacc said:
Can someone freaking help me with my phone's problem, I have spent 800 US Dollars buying that phone, and I can't even use it! It has been 6 months since I opened this thread and no one has helped me yet!
PLEASE HELP..............................................................:crying::crying::crying:
Click to expand...
Click to collapse
Try flashing the hybrid modem mentioned in the general guide (Part 2).
Try flashing 2 times before rebooting.
If nothing helps, you could try lineageos, @angelll123 made a lengthy guide how to that in the post quoted here , also check my comment.

Is this what you mean?
tomgaga said:
Try flashing the hybrid modem mentioned in the general guide (Part 2).
Try flashing 2 times before rebooting.
If nothing helps, you could try lineageos, @angelll123 made a lengthy guide how to that in the post quoted here , also check my comment.
Click to expand...
Click to collapse
I have attached a screenshot of the Yotaphone 2 General guide page, I want to know if you are referring to the text that I highlighted in the screenshot!
Thank You

I do experience similar issue, but only recently. I haven't done anything like flashing or upgrading my phone, it started by itself .
I am experiencing reboots whenever battery drops below about two thirds of its capacity. Also, charging and handling some load prevents this.
Note that my Yotaphone has both displays damaged. Still working though.

Successful Recovery Note7 from last Samsung "Death Update" Disabled Battery Charging!

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

Boot help Galaxy S7 Edge

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.