It won't start unless plugged it shows empty battery. sometimes when i unplug it stays connected. In usb settings if choose mass storage it seems to get in a loop of connect-disconnect. I have tried flashing different roms but it didn't fix. Any idea of what is happening? Could it be hardware problem?
I've got the same problem, I've tried every kind of wipe, flash with repartition, clearing stats and so on. I'm starting to suspect it's a hardware issue. The Phone seems to always think it's plugged into USB no matter what, it keeps rebooting to the battery icon over and over until I plug it onto a power source and then it boots fine.
After that I can get it back to normalish by rebooting with the power disconnected using the extended power menu in Darkys Rom.
Can anyone help? When I get back from my trip I'll likely flash it back to stock and send it in for repair, or just ***** at bell and get another new phone.
I'm having the same issue, I've searched all over internet and I found other posts with the same problem.. and no one has found a solution for this.
I think is a hardware problem. after having this I've bought a chinese compatible battery, and when I put that battery in, the phone boots up without even pressing the power on button, so weeeird!
With the original one.. there is no way to boot up without plug the phone. I've had the phone working well for more than 5 months
if someone finds a solution please tell!
thanks in advanced!
I had the some problem and more. I did something and this one has gone. I think i replaced a new update.zip in the phone and that solve it but i am not 100% sure. My phone starts normal but when its off sometimes the battery still flashes. In a week or so i will send it to waranty i think.
grofudaniel said:
I had the some problem and more. I did something and this one has gone. I think i replaced a new update.zip in the phone and that solve it but i am not 100% sure. My phone starts normal but when its off sometimes the battery still flashes. In a week or so i will send it to waranty i think.
Click to expand...
Click to collapse
what did you did? so do you think it's a software problem?
I tried to use a non-original battery and when I put in this new battery, the phone boots up without even press any button. so something it's really wrong. if I try the same with the original battery.. nothing happens, the screen is black unless I plug the phone to the charger.
well, at least I can boot my phone without plugging it this way.
I look forward to know more details about this issue.
thanks!
I look forward to know more details about this issue.
Search loads of posts on this topic . Dont know if problem solved or not .
jje
JJEgan said:
I look forward to know more details about this issue.
Search loads of posts on this topic . Dont know if problem solved or not .
jje
Click to expand...
Click to collapse
unfortunately I've done the search in this forum and I haven't found any solution for this, I can't believe it!
regards!
This problem is back again. I can`t start the phone unless it is plugged. I am with the nervs down at this moment.
what makes me crazy is to not know if it's a software or hardware failure!
in my case seems to be a hardware problem unless the phone recognize the non original battery and that makes a software change that makes the phone to boot.
I'll wait until the gingerbread update, and if after update it doesn't work, I will bring the phone to samsung repair point.
I see that I'm not alone with this problem.
Maby if i could connect the phone on usb to pc i would do something but that dosent work either for me so god have mercy.
I had that problem for a few weeks. Went away with a firmware change. Flashed back to stock and then docs rom. No idea what it was. Just went away.
Are you sure the battery is charged? I had the exact same problem on cm7, turned out my battery ran flat overnight
Sent from my GT-I9000 using XDA Premium App
Try this:
Format all your mounts in recovery mode with Clockworkmod. You can do this by going to 'mounts and storage' and formatting boot, system, data, cache. I did sdcard and sd-ext to be sure).
When you have done that install a 2.2.1 stock rom and the problem should be fixed. From here you can install custom rom's again.
Also try disabling any lagfixes (also via CMW)
KeesKaas said:
Try this:
Format all your mounts in recovery mode with Clockworkmod. You can do this by going to 'mounts and storage' and formatting boot, system, data, cache. I did sdcard and sd-ext to be sure).
When you have done that install a 2.2.1 stock rom and the problem should be fixed. From here you can install custom rom's again.
Also try disabling any lagfixes (also via CMW)
Click to expand...
Click to collapse
OK, I'll do that thanks for the suggestion.
I only have one more doubt left, If I do that, after formating everything in clockworkmod.. What does it happens to the phone? is it going to be able to boot after formating all of this? I'm asking this because I don't know how to download the official rom without using kies and the phone booted up and connected via usb cable.
thanks so much!
I've got the same problem.
I thought it was me trying to flash JVK, but after flashing and reflashing 2.2.1 and 2.3.3 and back with bootloaders the problem stayed. I'll try the format "everything" from CWM, hope this will work.
Still abit strange
(BTW I recently was in sub 15 degrees temperatures, surely this isn't the case??)
I had a problem like this where I was getting USB connected coming up again and again and my phone not starting when it wasn't plugged in.
This sounds dumb and I may just have been lucky but I turned USB debugging off and it stopped, left it off for a day or so, a couple restarts later I thought I'd see if it was still playing up so re-enabled it and nope everything's ok again. That was a couple weeks ago and so far so good, I hadn't seen any reports of anyone else with this.
Might be worth a try
Oh I'm using Darkys 9.5 by the way
My problem got worst! My phone would not charge at all until i reflashed. It now charge and boot normaly without to have it plugged, but my pc don't recognize it, not even in download mode with odin. I quess it has something to do with the hardwhare because both times the problem started when i charged it in the same plug.
i had the same problem,I just cleaned the usb port,plugged in the cable without connecting it to the pc or power source,and it started now it's ok
Me too
Another victim of this issue.
I was running a Darky Rom when I first noticed it... I think I was on Ficeto's 2.3.5 JVT. s
I have tried several steps to rid myself of this issue, with no success:
1. Reflashed ROM CWM
2. Reflashed Kernal CWM
3. Factory Reset, format internal SD, & ODIN flash Stock ROM.
4. Wipe & Flash Juwe ROM.
5. Each time, I also wiped the Dalvik Cache and battery stats.
I have tried leaving the battery out for a lengthy period, I have tried draining the battery all the way down, charging all the way up.
At least with the Launcher I am using now, it has the "Reboot" option instead of just turn off. However, I have to make sure I have a USB cable close by and charger in the car all the time now, just in case it runs out of juice or locks up for some reason and needs a battery pull.
Frustrating... Of course, the warranty expired the end of October.
If anyone has successfully completed the recommendation of formatting boot, system, data and cache and flashing stock Froyo? If you have done it, PLEASE post your detailed steps and the result so we don't waste time repeating something that won't work.
I was eyeing the SGS 2, but with all of the issues the market went through with the SGS, I am thinking maybe I should get away from Samsung...
MM
Related
Hello,
My G1 stopped receiving usb notifications. each time i connect it to a computer,the battery charges but i get no notifications about the usb.which means, i cannot mount it to a computer.
I run Cyanogen mod 5.0.7 test2, but i dont think its related since its started a couple of days after i installed the new rom.
i also tried it on different computers/usb cables, seems like its device related.
Anyone has any idea?
TIA,
Roy
use fix permissions option in recovery
it works for me
or
simply restart your phone while connected to the pc
It is device related, if you have a recovery that supports usb mounting from it, I suggest go there and mount your phone if you need to get something onto your device asap. If you have time, a full wipe fixed the problem for me.
Just tried the fix_permissions with no success.
the weird thing is that even in recovery mode, when i enable usb mass storage i still dont get anything!!
i'm trying to avoid a full wipe ,and starting to feel like it's a rom issue, anyone thinks the same?
Same Problem
I too have the same issue. Incase you have any solution let us know. I did some search in google but could not find any thing.
Nandroid, wipe, reflash, and retry. Retry with a different ROM and a fresh wipe maybe. You always need to wipe and reflash when you run into errors like this. Like it or not.
However, if that doesn't work, try a few different USB cords. Maybe something happened to yours, or the one you're using doesn't support a G1. Some companies rig theirs to work with just their product.
Edit: Just noticed you tried different cables and computers... How many different cables? Have you just tried your original one and then another one? Or about 3 - 5 maybe? These are quite common cables, and anyone you know should have at least one or two.
this happened to me a few times after i flashed cyans 5.07 test2 rom and all i did was restart and the notification came back. hope that helps.
Happens to me too with T1-T3. I can just reboot with the cable installed and it will mount once the phone is up.
pkrattu said:
this happened to me a few times after i flashed cyans 5.07 test2 rom and all i did was restart and the notification came back. hope that helps.
Click to expand...
Click to collapse
Same thing. This actually happened to me today and a restart brought it back.
I have the same issue
and everyday I have to reboot the phone while connected to the usb cord
to have the phone recognized.
alternative: try using dual mount sd widget out on the market. It lets you mount your SD card and still use the apps on the phone.
Hello everyone, long time reader, first time poster (with a real query).
Actually last Friday my cappy started to show 100% of the battery after being for some time in use, so I reboot it trying to solve the issue.
After the boot, the cell shows the Initially Battery screen for 2 seconds with the battery without charge then turns off. Tried several times and also using a second battery with full charge and same problem persisted.
10 minutes later without having a battery inside the phone, it boots but when I rebooted the problem arises again.
This weekend I installed Illuminance 3.01, after that I have installed CM9 (very nice ROM) and the battery problem still is happening. I am able to use the phone but I don´t know for how much more.
Any suggestion?
Thanks,
Martin
have you tried to wipe battery stats in recovery ?
Felixcm88 said:
have you tried to wipe battery stats in recovery ?
Click to expand...
Click to collapse
Yesterday night I did a wipe battery stats and the problem still is there.
It starts with the loop and the only way I can start the phone is plugging it then it shows the actual charge of the battery and after that I can boot.
It must be something "deeper" than the rom...
Anybody?
Thanks
Somebody can help?
I am having the exact same issue, stock froyo 2.2 rooted 5 months ago. I'm trying everything before updating to 2.3, I'll let you know if I find a fix, please do the same.
Searching google is not working this time, it's been 3 days...
Things I've tried:
1- From recovery, boot phone. Problem persists after phone is turned off.
2- Boot from revovery, then reset to factory settings, after rese, same issue.
3- Wipe cache from recovery. Problem still there.
4- Wipe cache+user data from recovery. Same thing.
5- repeating 1-4 without SD card or SIM card.
- Wipe battery data... nothing...
- Unrooting, same issue, rooted again.
- Run root fixes with Titanium backup. Same...
- Removing battery for hours, while charging it externally, replace battery, same issue.
All to no success. Things yet to try:
- Update to 2.3 using kies
- Update to beta 2.3.5 using odin
- Update to custom rom, maybe try 3 or 4 different...
- Cry, then save and buy a new phone, use cappy as shiny paperweight...
Please let me know if you could fix it...
I'm not sure what you mean when you say "initial battery screen."
But if I am to understand the rest, your problem is:
initial boot - runs fine, but battery stays at 100% no matter how long it runs.
reboot - phone now says the battery is suddenly dead, and shuts-off.
further reboots - same
You can't get the phone to fully boot till the battery is left out for a while and the phone is fully de-energized.
You have tried a different battery and it behaves the same.
- - - - - -
Have you tried using a known "good" battery? (a new one or one from someone who's phone works fine)
Also, what happens if you plug in the USB while the phone is off? (after the inital boot, when it is stuck in the "dead battery loop.")
Still dead after installing update and 2 custom roms...
Yes I tried a good battery from another cappy, if I plug in the cable it does the same, instead of normally booting, it displays an empty battery and goes off.
I am able to make it work but only entering the restore mode, so I cannot for example be on a trip and reset the phone for whatever reason...
have you tried using a different kernel?
Sent from my SGH-I897 using XDA App
sorry, but how can I try a different kernel? do i need to change the rom?
Nah, kernels can be flashed independent of ROMs just look through development for topics that have "[Kernel]" as the fist word in their title.
If you have gone and loaded two custom ROMs and it still persist then it's not a kernel issue. As the kernel is always changed along with the ROM.
That said, I can only think of two other possibilities: one being dirt or such making a short in the contacts of the usb (does it sometimes think it is plugged in when it's not), two something in the circuitry for the battery randomly went bad.
Try cleaning the socket for the usb. If that does not fix then assume the worst
leaked from my ICS- FUSED SGS I897 contaminating you via XDA app.
Ok, here's the thing, I left it without the battery for 24 hrs, then it was worst. The phone would not turn on at all. However, after that I tried putting the battery in while holding the power button, it worked!!! it's better than having to connect to the computer, but still, I don't want to have to do this every time... flashing roms now to try again.
We're getting somewhere now...
DaNaRkI could be right about it being a circuitry problem (which would suck). With that in mind, have you checked to make sure the prongs which connect the battery to the phone are still in good shape?
When you flashed the roms, are you doing complete wipes? (wiping the cache/dalvik/data)? It might be worth it to go one step beyond that and format all the partitions and then reflash. I think if you do that, you could basically rule out any software problems.
Be sure to back up your data!
P.S. When you do all this wiping and formating and reflashing, boot up and check to see if the problem is still there before you put your data back on jic there is some weird corruption in your data which is causing this.
ok.
have you checked to make sure the prongs which connect the battery to the phone are still in good shape?
yes I have, they're perfect
When you flashed the roms, are you doing complete wipes?
many times, actually
I have yet to format all partitions, how can I do that?
Thanks!!
and yes, all my data is well backed up in my PC and cloud...
---------- Post added at 12:31 AM ---------- Previous post was at 12:09 AM ----------
this is rather odd, just tried to factory reset again, then restarted using the battery method, then... turned it off, and now it boots normally!!!
Thanks for your help !!!
I have the same problem. What exactly did you do? I use a custom rom, and I flashed stock gingerbread 2.3.4.
Formatting the partitions won't do anything, since the phone won't even turn on sometimes. So when exactly did this problem start happening? Was it after a particular flash or other incident?
My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Xanthippus said:
My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Click to expand...
Click to collapse
Which version are you using? It was a known bug in an older ROM, which should have been fixed in the newer ones.
Using the 20120816 version that I got from the link in this thread: http://forum.xda-developers.com/showthread.php?t=1803593
I've also had this problem for awhile, with several different ROM's.
Does fastboot work for you? Cause it doesn't for me, but not sure if related.
Xanthippus said:
My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Click to expand...
Click to collapse
Are you using the correct recovery? Not sure that you would be able to get as far as you if it were wrong but ...
I caused myself heartache at some point as a result of using the wrong recovery. It gave my weird results too. I am other 16 Aug ROM and I find it pretty damn good.
Here is the right one
http://droidbasement.com/galaxy/roms/cm10/p3/recovery.tar.md5
GaryWS said:
Are you using the correct recovery? Not sure that you would be able to get as far as you if it were wrong but ...
I caused myself heartache at some point as a result of using the wrong recovery. It gave my weird results too. I am other 16 Aug ROM and I find it pretty damn good.
Here is the right one
Click to expand...
Click to collapse
I got the recovery from the same thread I linked above, so pretty sure it was the right one. Just to be sure I downloaded and flashed the one you linked with Odin, but it's made no difference. However, I have (finally) had success in getting the battery to charge to 100%. I kept wiping the battery stats every time I booted up, and powered it down while plugged in and left it on charge when I wasn't using it. After a couple of days (with it on and off charge) it finally said it was fully charged when I powered it on. I have used the battery calibration app with it at 100%, so hopefully it shall begin indicating properly, although it still says it's charging all the time, and the charging animation when it is powered down does not indicate its actual charge level.
As for it not powering down when it's not plugged in... I am still new to rooting and ROMs, but would it be of help if someone who has no problems powering down uploaded their kernel and I flashed that?
Xanthippus said:
As for it not powering down when it's not plugged in... I am still new to rooting and ROMs, but would it be of help if someone who has no problems powering down uploaded their kernel and I flashed that?
Click to expand...
Click to collapse
Re-download the lastest ROM and flash it; the latest ROM does not have that problem.
pruano said:
Re-download the lastest ROM and flash it; the latest ROM does not have that problem.
Click to expand...
Click to collapse
Where would I get that ROM from? The latest one from the link above at the Droid basement is the 16th August version I already have.
Xanthippus said:
Where would I get that ROM from? The latest one from the link above at the Droid basement is the 16th August version I already have.
Click to expand...
Click to collapse
I would recommend you re-download and re-flash it, since others (myself included) have no such problem with that version.
Didn't work. Redownloaded, reflashed, same problem. I even tried to unroot it so that I could flash it all again fresh, but somewhere along the way something has gone wrong. Odin is not working anymore. I can transfer files to and from my tablet, the computer still recognises it when plugged in, and Odin recognises the USB connection too, but if I try to flash something with it, it always says it is unable to open the COM port.
Tried this many different ways, with different roms, nothing seemed to work. Finally, tried AOKP milestone 6 (based on CM9) and it works perfectly. Go figure...
Hi.
Since yesterday my galaxy s3 lte i9305 does not boot anymore, the blue cyanogenmod logo keeps turning for hours. I can however still go to the recovery (which was a few month old cwm). I completely wiped the phone (both caches, data, internal sd, boot, firmware etc ... all but the modem) and reinstalled the newest cwm and the newest nightly build three times now using heimdall and the external sd (connected my external micro sd to my computer sd card reader via adapter and put the zip on it). Just now I installed twrp-2.8.5.0-i9305 as a new recovery and installed everything again, but everytime - and also now - despite the seemingly successful installation, the phone is stuck at the cyanogen bootlogo.
Any ideas on how to get my phone running again?
Cheers
ScPo said:
Hi.
Since yesterday my galaxy s3 lte i9305 does not boot anymore, the blue cyanogenmod logo keeps turning for hours. I can however still go to the recovery (which was a few month old cwm). I completely wiped the phone (both caches, data, internal sd, boot, firmware etc ... all but the modem) and reinstalled the newest cwm and the newest nightly build three times now using heimdall and the external sd (connected my external micro sd to my computer sd card reader via adapter and put the zip on it). Just now I installed twrp-2.8.5.0-i9305 as a new recovery and installed everything again, but everytime - and also now - despite the seemingly successful installation, the phone is stuck at the cyanogen bootlogo.
Any ideas on how to get my phone running again?
Cheers
Click to expand...
Click to collapse
I would try a factory reset from recovery and see if that helps. You did check the md5 for your downloads right?
Otherwise I would install the stock rom, then try again, this time(making sure you have a compatible recovery) just wipe caches, data, and format system, and then install CM
noppy22 said:
I would try a factory reset from recovery and see if that helps. You did check the md5 for your downloads right?
Otherwise I would install the stock rom, then try again, this time(making sure you have a compatible recovery) just wipe caches, data, and format system, and then install CM
Click to expand...
Click to collapse
I did do the factory reset. I just wiped the areas separately as well. Anyway, I took your advice and installed the latest stock rom. Now I got the Samsung logo slightly flashing blue for hours instead of the cyanogenmod logo. Did not do anything else.
I suspect that its a battery issue in some way. The last weeks the phone lost its charge very quickly very often (not constantly though). Yesterday, the phone was in my pocket and then went off. It went into the constantly trying to restart despite the lack of batteries state until I removed the battery. Maybe that gives any clue?
ScPo said:
I did do the factory reset. I just wiped the areas separately as well. Anyway, I took your advice and installed the latest stock rom. Now I got the Samsung logo slightly flashing blue for hours instead of the cyanogenmod logo. Did not do anything else.
I suspect that its a battery issue in some way. The last weeks the phone lost its charge very quickly very often (not constantly though). Yesterday, the phone was in my pocket and then went off. It went into the constantly trying to restart despite the lack of batteries state until I removed the battery. Maybe that gives any clue?
Click to expand...
Click to collapse
Try booting into stock recovery, then factory reset from there. Last time I went back to stock I had a bootloop until I did this, then it booted properly. If that doesn't work, maybe try new battery.
Have you tried booting up whilst plugged in to a usb charger?
noppy22 said:
Try booting into stock recovery, then factory reset from there. Last time I went back to stock I had a bootloop until I did this, then it booted properly. If that doesn't work, maybe try new battery.
Have you tried booting up whilst plugged in to a usb charger?
Click to expand...
Click to collapse
Thanks for your helpful input.
I did what you said, even tried it twice now. Phone is still booting after 20 minutes now. I also tried booting up while charging the phone, yes. That was my standard procedure actually, but nothing changes when I unplug it. I don't have a different battery and I am wary of buying one just for the sake of trying. Tried that when my galaxy s 1 broke down and that didn't save the phone. At this point I am contemplating if the phone (s3) is broken now or not. It still reliably boots to the recovery, but it doesn't do much else. How are the chances?
Or has anyone any idea on how to proceed?
ScPo said:
Thanks for your helpful input.
I did what you said, even tried it twice now. Phone is still booting after 20 minutes now. I also tried booting up while charging the phone, yes. That was my standard procedure actually, but nothing changes when I unplug it. I don't have a different battery and I am wary of buying one just for the sake of trying. Tried that when my galaxy s 1 broke down and that didn't save the phone. At this point I am contemplating if the phone (s3) is broken now or not. It still reliably boots to the recovery, but it doesn't do much else. How are the chances?
Or has anyone any idea on how to proceed?
Click to expand...
Click to collapse
Try to boot into recovery. Do a factory reset then boot straight into download mode and flash stock rom. You might have to redownload the firmware it could be corrupted.. If that doesn't work then you might have to send it in. It might cost about to fix. Or go to your local phone repair shop and see if they could fix it for cheaper
Sent from my GT-I9305 using XDA Forums
I didn't want to make a new thread. But I've searched high and low.. And nothing has been answered. So here's my story. I have a note 4 sm-n910T. When I rooted the phone everything was fine and good. I then decided to give it to a family member. I flashed it back to stock.. All was fine for a while but it started acting up. Like randomly turning off and not responding to a charge or any commands to turn on into other modes... I had flashed stock again. All was good.. Till now. My madre and received a Ota update, downloaded and installed the update. When I pressed ok to reboot new update. The phone never came back on. So I went through all the fun stuff. I tried kies.. Kies days unsupported device connected.. There is however talk between the two because it's pushed errors onto my phone as well as has tried to download the stock rom. But every which way I've tried it fails. Next. I decided to go for custom roms... And flash cf-chainfire auto root. Then twrp.. Then install supersu.. Then a rom from twrp. Now here's where it gets interesting. Nothing would pass odin if I had auto-reboot and f.reset time checked.. Any and all roms.. Files..etc would only pass with auto reboot checked and f. Reset time unchecked. At first everything seemed ok.. I was able to actually get cm 12.1 installed as well as gapps. But only the one time.. Which you'd think was good enough. But here's what has happened and what I can't seem to fix. The phone yesterday after having everything installed and sitting at home untouched.. I came home clicked the home button.. And it came on.. I scrolled a few pages.. Thought.. OK cool.. Let's get madres Sim card in and call it a night.. When I turned the phone over.. (didn't even take our the battery) tried to see if I could fit the sim in.. Which didn't.. I then turned the phone back around just Cuz I wanted to make sure it was awake.. The screen was black.. I figured it was in sleep mode.. So I hit the home button.. No response.. I hit the power button.. No response. .. The phone had turned itself off.. And when I tried to turn it on it wouldn't. Now mind you the phone has these weird phases where when I try to install or flash a rom and it fails.. And I'm forced to remote battery.. A good portion of the time it won't turn back on.. Sometimes it can be instant.. Others.. A few mins.. Sometimes even longer for it to respond.. Right now I have been accessing twrp.. Wiping all data.. Davik...cache.. System.. One by one.. Then installing a rom.. I go for a reboot.. And I get a black screen. I need help.. I'm running out of ideas and basically just fishing random idea attempts. I'm no scared to brick it.. So all ideas are welcome. Plz. Thank you.
Malistoff said:
I didn't want to make a new thread. But I've searched high and low.. And nothing has been answered. So here's my story. I have a note 4 sm-n910T. When I rooted the phone everything was fine and good. I then decided to give it to a family member. I flashed it back to stock.. All was fine for a while but it started acting up. Like randomly turning off and not responding to a charge or any commands to turn on into other modes... I had flashed stock again. All was good.. Till now. My madre and received a Ota update, downloaded and installed the update. When I pressed ok to reboot new update. The phone never came back on. So I went through all the fun stuff. I tried kies.. Kies days unsupported device connected.. There is however talk between the two because it's pushed errors onto my phone as well as has tried to download the stock rom. But every which way I've tried it fails. Next. I decided to go for custom roms... And flash cf-chainfire auto root. Then twrp.. Then install supersu.. Then a rom from twrp. Now here's where it gets interesting. Nothing would pass odin if I had auto-reboot and f.reset time checked.. Any and all roms.. Files..etc would only pass with auto reboot checked and f. Reset time unchecked. At first everything seemed ok.. I was able to actually get cm 12.1 installed as well as gapps. But only the one time.. Which you'd think was good enough. But here's what has happened and what I can't seem to fix. The phone yesterday after having everything installed and sitting at home untouched.. I came home clicked the home button.. And it came on.. I scrolled a few pages.. Thought.. OK cool.. Let's get madres Sim card in and call it a night.. When I turned the phone over.. (didn't even take our the battery) tried to see if I could fit the sim in.. Which didn't.. I then turned the phone back around just Cuz I wanted to make sure it was awake.. The screen was black.. I figured it was in sleep mode.. So I hit the home button.. No response.. I hit the power button.. No response. .. The phone had turned itself off.. And when I tried to turn it on it wouldn't. Now mind you the phone has these weird phases where when I try to install or flash a rom and it fails.. And I'm forced to remote battery.. A good portion of the time it won't turn back on.. Sometimes it can be instant.. Others.. A few mins.. Sometimes even longer for it to respond.. Right now I have been accessing twrp.. Wiping all data.. Davik...cache.. System.. One by one.. Then installing a rom.. I go for a reboot.. And I get a black screen. I need help.. I'm running out of ideas and basically just fishing random idea attempts. I'm no scared to brick it.. So all ideas are welcome. Plz. Thank you.
Click to expand...
Click to collapse
Also how important is f. Reset time? I don't totally understand it. Next.. What about having the roms and files I flash on internal memory instead of sd. I'm not sure if I can access the Internal storage. But if I can does that help. Also I cannot access Android at all.. I can either access download mode or recovery. I have been using an external battery charger to charge my battery as well. Due to it doesn't read the charge... But! It did read a charge just fine when I had cm 12.1 working.
I would suggest:
1) In twrp wipe system, both the cache's and also data
2) use ODIN to install the stock Note 4 ROM
see -> http://forum.xda-developers.com/not...uide-odin-to-stock-unrooted-firmware-t2957156
3) When it is finished unplug the usb from your computer as the phone is rebooting
NOTE you might want to uncheck Reactivation Lock in Settings - Security first
w8wca said:
I would suggest:
1) In twrp wipe system, both the cache's and also data
2) use ODIN to install the stock Note 4 ROM
see -> http://forum.xda-developers.com/not...uide-odin-to-stock-unrooted-firmware-t2957156
3) When it is finished unplug the usb from your computer as the phone is rebooting
NOTE you might want to uncheck Reactivation Lock in Settings - Security first
Click to expand...
Click to collapse
Answering question one.. I do that already. I wipe everything one by one except sd... Answering question two. I have tried that already and odin fails.. However I'm sure if I tried to flash the rom and didn't check f. Reset time it might work. But as for flash stock.. I have tried several times.. I can't say one error or another I'd a cause because I get a different one each time.. What is the purpose of f. Reset time in Odin? I've searched it and to me the explanation didn't make since.
Malistoff said:
Answering question one.. I do that already. I wipe everything one by one except sd... Answering question two. I have tried that already and odin fails.. However I'm sure if I tried to flash the rom and didn't check f. Reset time it might work. But as for flash stock.. I have tried several times.. I can't say one error or another I'd a cause because I get a different one each time.. What is the purpose of f. Reset time in Odin? I've searched it and to me the explanation didn't make since.
Click to expand...
Click to collapse
Reactivation is unlocked. Also I wouldn't be able to change any setting in the phone.. As the phone does not boot into Android. I was just lucky enough to have usb debugging active before this all happened
I am not sure what that is for
But every time I have done a flash it works if you use the steps I had there. (Not really questions)
Sorry I do not have anymore ideas.
---------- Post added at 02:38 PM ---------- Previous post was at 02:37 PM ----------
Are you booting your phone into download mode before you use ODIN?
(I know it's proly a dumb question but just in case)
Yes I am in download mode when using odin.
Malistoff said:
Yes I am in download mode when using odin.
Click to expand...
Click to collapse
Just now I did another full wipe and wipe of cache, davik, system, internal memory and had a successful install of cm12. 1 with gapps.. Everything installed.. Clicked reboot and the phone never came back on. I will try your idea next. I have not tried an idea where I use twrp to wipe everything and reboot into download then do stock rom via odin. If the phone does boot into download from twrp recovery I will try this one time with auto reboot and f. Reset time checked.. If it fails I will try it again with f. Reset time unchecked. I am currently not by my laptop to try this so it will have to be much later in the day.
To boot into download mode: Power off Note 4, hit all 3 of these at the same time until it wakes and vibrates - Power Button, Home Button and Volume Down
I know how to do that lol. I know I'm a junior member. But I'm somewhat intermediate. So cm12. 1 has booted.. However it didn't from a reboot of a flash.. I just took a while shot.. And powered the phone on.. And it booted.. I'm pretty sure in going to run into the problem again.
OK - Well you never know!
I am only a senior member 'cause I am older than Dirt!
Lol. I'm oldish. And trust me this lucky catch I got.. Is temporarily. There is still boot issues. I fear when the phone goes off or is turned off that it won't come on. I do not have a sim card in the phone at the moment which means I can download helpful apps. Like supersu. .. But so far I was able to check settings and get what I can prepared. Also if like to keep this thread open as a log or research tool.
Alright so I like the rom sit most the day.. With minimal to no use.. Most of the day it was fine.. At one point I took a picture and it did as it should.. I cleared all open tabs.. Took another picture and I got a error saying camera wasn't connected.. Finally the phone froze up and rebooted.. And the Camera worked.. Gave it another rest.. Came back to it checked the camera and it was fine.. I put it away for like 10mins then decided to check recording. When I did the phone was not responding to turning back on from sleep mode. Now for as long as I can remember even before this initial issue started.. I was having thr same problems with the phone not coming back on from when in sleep mode.. I dunno what the cause is or hoe to approach it to fix it.
First attempt was to put it to a charger... Registered no charge.. So I removed the battery.. Gave it a few mins.. Pushed down power button.. No response. Something is off with the boot menu.. Like the boot img. File
And finally it's back on.. Normal boot.. I didn't boot from download menu or recovery.. But in all honesty I'm 100% sure this will just happen again.. It seems to happen when I put the phone in the charger.. Then take it out and play with it.. For now in going to let it sit till the battery is in caution. Then charge it. I still have not added the Sim and loaded apps.. I feel that will be a overload of cpu and will most certainly freeze up and crash the phone
Ok, so up to date now.. Here's what's going on. The phone struggles to reboot from any on screen commands.. Like if I'm in Android.. And hold power.. Click reboot.. Then say like recovery.. Or anywhere.. It just turns off... If I also do this in twrp.. Say like install a rom or supersu.. It won't reboot... But! After it turns off.. And I wait a while and power it back on.. The file.. Rom etc was installed. So I do now have supersu installed and busybox. But the issue remains..which is a unstable OS.. Nothing to do with it being custom os.. But there is something wrong with the booting process.. What can I download if any apks.. Or files to help this?
Malistoff said:
Ok, so up to date now.. Here's what's going on. The phone struggles to reboot from any on screen commands.. Like if I'm in Android.. And hold power.. Click reboot.. Then say like recovery.. Or anywhere.. It just turns off... If I also do this in twrp.. Say like install a rom or supersu.. It won't reboot... But! After it turns off.. And I wait a while and power it back on.. The file.. Rom etc was installed. So I do now have supersu installed and busybox. But the issue remains..which is a unstable OS.. Nothing to do with it being custom os.. But there is something wrong with the booting process.. What can I download if any apks.. Or files to help this?
Click to expand...
Click to collapse
Might be stupid I know, but try wiping clean your SD card (back up a copy on your pc first) as well when you factory wipe and make sure that after that, you only add the files you need for recovery. Start up the phone after reset. To get a backup, if you're synced through google, you'll get everything back. If not, only copy your backup from titanium back into your SD card.
I went through a very similar situation last week. Long story short, it seemed the SD card had copied files which would interfere with the system.
Curious, did it happen after marshmallow update?
And did you try to downgrade back to previous lollipop version?
I assume it was Marsh that I was trying to Ota too. I was unable to boot successfully after that first try, so I honestly don't know.. I'm going to try your SD card idea. .. But once all that's done. Are you wanting me to redo a full rom install like through and wipe system, Davik etc etx? Or like wipe everything and start from like odin installing a recovery and so forth?
I ask these questions because.. What if I was to just take the sd card. And format the whole thing.. And out it back into the phone? I mean I might try that first then the other option.
Malistoff said:
I ask these questions because.. What if I was to just take the sd card. And format the whole thing.. And out it back into the phone? I mean I might try that first then the other option.
Click to expand...
Click to collapse
Well even if you format and you put the SD card back in with all previous files, same might happen.
When you format, just wipe all. Then if you want to downgrade, you need to have the previous version bootloader and baseband FIRST prior to putting the firmware ROM.
A simple (restore) wipe would just keep you at current version. And you can't easily downgrade the easy way from marsh to lollipop. Believe me, I learned the hard way
Flash through ODIN