Hello. All of a sudden, my Note Edge started rebooting for no reason and the battery got really hot. I tried using Safe Mode, removing the SD card, etc. It went on for 2 days. I tried deleting the cache, resetting to factory, all from CWM. That didn't work, when it reboot, some or most apps were still installed even after going though the "new device" configuration.
I panicked and tried to reinstall the ROM DPE3-N915T] NOTE EDGE - STOCK - ROOTED / DEODEXED URv0 - MM 6.0.1 -> TEKHDway!*.
Now it's stuck on the installation screen. BTW, I had the same ROM for months with no issues whatsoever.
Any ideas on what I should do?
Hi,
I had a similar problem where the device would overheat and keep rebooting. This made it impossible to flash or install any Roms or recovery.
The culprit here is most likely your battery. It may not hold charge, I bought a new battery and it solved my problem.
Also, there are voltage testers available at almost all mobile repair shops, I'd suggest you get your battery checked out. Also look for physical signs in the battery such as swelling.
If you are not willing to buy a new battery as you aren't sure if that is causing the trouble. I read somewhere that if you put a plastic bag over your battery and put it in the freezer for a certain time (sorry, you will have to google this), it works for an hour or so. That might be the time window you need to install the software and test out the battery.
Thank you but I don't think it's the battery, I have 2 of them, both OEM and one of them is about a year old. The phone behaves the same way with both.
octavia said:
Hello. All of a sudden, my Note Edge started rebooting for no reason and the battery got really hot. I tried using Safe Mode, removing the SD card, etc. It went on for 2 days. I tried deleting the cache, resetting to factory, all from CWM. That didn't work, when it reboot, some or most apps were still installed even after going though the "new device" configuration.
I panicked and tried to reinstall the ROM DPE3-N915T] NOTE EDGE - STOCK - ROOTED / DEODEXED URv0 - MM 6.0.1 -> TEKHDway!*.
Now it's stuck on the installation screen. BTW, I had the same ROM for months with no issues whatsoever.
Any ideas on what I should do?
Click to expand...
Click to collapse
For whatever reason that ROM is failing the install for me as well. Have you tried one of the AOSP roms? Try The SLIMRoms build from AlaskaLinuxUser in the Tmobile section. It is good and stable and at least will get you back up and running. Also, may help to try a different card, I've had terrible issues from time to time when an sd card has become corrupted and I didn't realize it. If all else fails you may have to Odin the stock rom.
I had the same problem... I had to give up my Note Edge
Sent from my SAMSUNG-SM-N915A using Tapatalk
Related
Hello everyone. It seems like the issue is getting worst and I think I've narrowed down the problem... Now I just need a solution and we can all be happy
So sometimes my phone decides to restart itself and it will not boot back up. The only solution is to remove the battery and try again. It could be solve after a couple tries in the past, and now I find myself sitting for half an hour + trying to get this phone running again. I do have clockwork installed, and it seems like my issue is with my SD card. When trying to mount/unmount my SD card via clockwork, there is an error doing do. Sometimes I can't access my pictures because of the same problem. Does anyone know if there is anything I can do to remedy this situation?
Thanks!
ritzbits said:
Hello everyone. It seems like the issue is getting worst and I think I've narrowed down the problem... Now I just need a solution and we can all be happy
So sometimes my phone decides to restart itself and it will not boot back up. The only solution is to remove the battery and try again. It could be solve after a couple tries in the past, and now I find myself sitting for half an hour + trying to get this phone running again. I do have clockwork installed, and it seems like my issue is with my SD card. When trying to mount/unmount my SD card via clockwork, there is an error doing do. Sometimes I can't access my pictures because of the same problem. Does anyone know if there is anything I can do to remedy this situation?
Thanks!
Click to expand...
Click to collapse
are you using a custom rom or kernel?
I used to, but now it is just stock rom rooted
Edit: I lied, seems like when I restored, the kernal stayed the same.... I assume I can just flash a stock kernal over my modded one?
ritzbits said:
I used to, but now it is just stock rom rooted
Click to expand...
Click to collapse
have you tried redownloading the rom and reflashing it?
Note the edit above. Just checked my settings and it looks like I still have my old kernal..( non stock) I dont seem to be able to find a stock kernal anywhere... Do you happen to know where I can find one?
theres probably a version of the stock rom floating around with the stock kernel already included. check the developement threads.
Stock rom, check stickies in General section.
Sent from my Nexus S using XDA App
I reverted everything back to stock with the exception of the bootloader still being unlocked. I thought the issue was fixed, and I have not had issues with the phone since. Until today when I decided to restart it. Same issues as before not being able to mount the sd card, which seems to be required to boot. Any ideas? Is the sd card in the nexus s actually there? Maybe it came loose?
Basically I have bought a xoom MZ604 UK off ebay that had reboot issues. I assumed it was due to software issues, I am now unsure. When it came it would stay on, but when you tried browsing, watching a film or on Youtube it would reboot after around 3mins.
I installed EOS 3 stable and the xoom would reboot within around 1 min if that, sometimes as soon as booted.
So I installed CM10, now it will last around 7-8mins without a reboot(with use). I'm sure it must be a software issue now, although obviously I could be wrong and would like an opinion on what to do next?
Any help will be much appreciated as I would love to give this my son as a crimbo present.
Thanks.
I think I have now bricked it? I did a system restore with TWRP and I didn't make a nandroid backup. I tried to install the zip I had saved on SD card and it would allow it, so I tried to reboot the system and I got a error message about there not being a OS on the system.
Is there anyway to unbrick, or have I well and truly knackered it?
I used Ace Hack Kit to root. It worked.
I flashed a ROM (Sabsa Prime), and, after not being impressed, changed it to ICESense (And I used the wifi fix as well).
Because I was not thinking clearly, I did not back up my stock ROM after running ace. I did, however, back up the Sabsa Prime ROM.
I had AdBlock plus installed from the market on both ROMs. On IceSence, after AdBlock was infuriating me, I uninstalled it. I went to reboot the phone. It loaded, and about 30 seconds after it was done, it froze for a second, and rebooted. the only way for me to stop this cycle was to pull the battery. It can still boot into HBOOT and CWM Recovery, however, the phone will not stay powered on long enough for me to place anything onto the SD card, such as another ROM, or the ZIP for IceSense, because I removed it from the SD card to save space.
So, I went to CWM, did a factory reset, and I restored my Sabsa ROM, only to have the same thing happen with the reboot cycle.
Am I bricked? If not, what would you recommend doing to fix this issue?
Arkona said:
I used Ace Hack Kit to root. It worked.
I flashed a ROM (Sabsa Prime), and, after not being impressed, changed it to ICESense (And I used the wifi fix as well).
Because I was not thinking clearly, I did not back up my stock ROM after running ace. I did, however, back up the Sabsa Prime ROM.
I had AdBlock plus installed from the market on both ROMs. On IceSence, after AdBlock was infuriating me, I uninstalled it. I went to reboot the phone. It loaded, and about 30 seconds after it was done, it froze for a second, and rebooted. the only way for me to stop this cycle was to pull the battery. It can still boot into HBOOT and CWM Recovery, however, the phone will not stay powered on long enough for me to place anything onto the SD card, such as another ROM, or the ZIP for IceSense, because I removed it from the SD card to save space.
So, I went to CWM, did a factory reset, and I restored my Sabsa ROM, only to have the same thing happen with the reboot cycle.
Am I bricked? If not, what would you recommend doing to fix this issue?
Click to expand...
Click to collapse
Have you tried remaining plugged into charger to reflash Rom. Possibly the battery is bad. Or does it only reboot when you mount your USB storage? Do you have another SD card to try?
Sent from my Inspire 4G using xda premium
I recently upgraded to the 4.22 PAndroid ROM, however, I'm having a battery problem. Furthermore, this problem followed me when I switched over to the 4.22 CM ROM.
When I plug in my charging cord (OEM; have tried computer and wall plug), the phone charges for about 5 seconds before ceasing to charge. However, it charges fine if the phone is off. I've tried wiping the cache/factory resetting on both ROMs, but that didn't solve the problem either.
When I flash back to my current ROM, 4.12 PAndroid, the problem goes away completely and it charges on everything exactly as it should.
If anyone has any idea, I'd love to finally be able to use 4.22.
Thanks!
EDIT: I've used two different OEM cords, so I'm fairly certain it's not a hardware issue. Just to clarify.
Bump
Sent from my SAMSUNG-SGH-I727 using Tapatalk
SlushySolid said:
Bump
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
Bump again.
I've tried about 5 ROMs now. This is super frustrating because my current ROM will randomly stop receiving texts, and I don't know how to fix that. I would really appreciate any advice I can get about why I can't install a new one. My install order is:
Backup, Wipe Data, Wipe Cache, Wipe Dalvik, Format /system, ROM, GApps, Reset.
Even changing the kernel doesn't fix this problem.
Which recovery and version are you using? Try updating the recovery
jd1639 said:
Which recovery and version are you using? Try updating the recovery
Click to expand...
Click to collapse
CWM, just updated to the newest (6.0.4.3). Still not charging
Multiple problems(charging,texting) that you can't solve? Best bet would be to Odin back to stock, complete wipes and proceed from there.
jondroid2 said:
Multiple problems(charging,texting) that you can't solve? Best bet would be to Odin back to stock, complete wipes and proceed from there.
Click to expand...
Click to collapse
So, I did that this afternoon. Basically went back to stock, redid the recovery, and then flashed another ROM. It still wouldn't charge properly. Then, when I reverted back to stock (from a backup I did before the flash) I started getting warning pop ups with "Battery Disconnected." Now, even stock won't charge my phone, and now that it's dead, it won't charge when it's off either.
I'm beyond confused about where to go from here, and I'm very frustrated with my Skyrocket. I'm almost at the point of just jumping ship to a Nexus 5 haha. I would hate to waste about tree fiddy though if this is something that is still fixable.
SlushySolid said:
So, I did that this afternoon. Basically went back to stock, redid the recovery, and then flashed another ROM. It still wouldn't charge properly. Then, when I reverted back to stock (from a backup I did before the flash) I started getting warning pop ups with "Battery Disconnected." Now, even stock won't charge my phone, and now that it's dead, it won't charge when it's off either.
I'm beyond confused about where to go from here, and I'm very frustrated with my Skyrocket. I'm almost at the point of just jumping ship to a Nexus 5 haha. I would hate to waste about tree fiddy though if this is something that is still fixable.
Click to expand...
Click to collapse
go back to stock w/odin and see if prob persists, don't use ur backups and don't flash anything else, just stay on stock.
if jb stock fw fails then try stock firmware gingerbread and ics and test each one w/out flashing anything else, stay on pure stock.
some users did have issues w/charging on jb but cant remember their solution if any.
if prob is still there on stock, then it could be battery, battery contacts, bad cable, dirty phone port, bad phone port.
since it does charge albeit w/screen off you could try to live with that instead of chucking it
Found this old thread with a similar problem to what I'm seeing. I'm running liquidsmooth 3.2-2014-08-20 since late November but had something similar before I reinstalled this ROM.
I have two batteries - the original that's 3+ years old and a new Samsung battery bought 4 months ago. When I have the old battery in, it charges when the phone is off or on. With the new battery in, it charges fine when the phone is off. When the phone is on, it charges for about 5 seconds then stops. If the remaining battery is low, I then get the message popping up saying to plug in the charger. When the new battery is in my phone does recognize the chargerbecause it pops in to USB mode and because I have a Tasker profile that's triggered when it's powered. The triggered action doesn't revert until I unplug the cable.
Does this suggest my problem is with my new battery?
Robnw
I have a well and heavily used Galaxy S5 (GM-900P) and about 2 months ago it started accting up pretty hard. Becoming very very slow so I decided to update to the latest sprint firmware and install a new(er) rom ([ROM][QD1][6.0.1]14Dec2017] Stock-ish Plus Tidbits and Magisk) and all was good for about 5 days and the phone started having apps crash/force close like crazy and most the time just reinstalling them would fix it but a bunch of google play services would crash and would have to uninstall the updates then it would work again for a day or so, sometimes it would randomly restart and get stuck at the boot screen and the phone would get crazy hot and the only way out of it was to boot into the recovery and then reflash the stock firmware in odin again then reinstall the rom. Then I had my phone all of a sudden act like there was no sim card in it and originally though it was a sim card issue but turns out it wasnt, I had to boot into the recovery and do a full wipe of everything reflash the stock firmware yet again and then reinstall the rom again. That happened twice in a matter of a week. At my wits end I decided to give LineageOS v16 a try so I boot into recovery, do a full wipe, boot into download mode, flash the latest stock firmware in odin, then boot right to recovery, flash LineageOS 16.0 then latest Magisk and all was great, for about a week, then Google services start crashing again and random apps crash over and over and even times the phone would slow down and reboot, get stuck at the boot screen and then eventually just reboot back into recovery by itself after failing to boot. But with LineageOS at least just reflashing the rom in the recovery will let it boot right back up sometimes and work as it should for another few days, other times too much stuff will just keep crashing so I do a full wipe and reflash LineageOS and all will be great for another few days to a week and it starts all over again. Its like stuff just randomly gets corrupted on the device and the only way out of it is to reflash the whole thing and start over and enjoy it until it does it again. Sometimes it will go days, sometimes a day later its all screwy again.
Also, TWRP always fails when I try to do a back up and it seems to always fail when in the data or data/private-app part of the system and its never at the same point.
I guess my question here is, could the onboard flash (the motherboard/logic board) be taking a crap on me? I really really dont want to give up on this phone just yet as it has everything I want in a phone and frankly, I just really really like it. I can get a new (used) motherboard for like $20 but even that kind of worries me cause I dont want to possibly be in this same position 3 months later again. I have a Galaxy S8+ (unlocked AT&T phone) that I refuse to use yet just cause I can not root it or unlock the bootloader.
Any help or ideas would be much appreciated and sorry for the long winded post.
could be wrong, on this one, But.....
If it was mew, I would go to stock . run that for a day, maybe 3... if all it well, then flash over what ever Rom you would like.
"KNOWING IT Work" is the key. Oh, another thing, that may help too . seen this on one of the LineageOS 15.1 or 16 is when you wipe ... System and Data, can be Reformatted, they have had some major success by also formatting it, (YES EXT4) but this will help to ensure nothing left over....
May even help with others Android 8.0, 8.1, 9.0....
Well, I have a new motherboard on the way so we'll see how that goes but I did manage to get the stock firmware on there and booted then I reflashed TWRP and then Magisk and going to just run it that way for a bit and see what happens.
I initially went in to TWRP, wiped data,system, etc... then flashed the stock firmware in Odin, then rebooted, got stuck at the Samsung boot logo so pulled the battery, booted to stock recovery, did a factory reset (Wiped everything, internal sd card included), then got it to boot, set the phone up, then rebooted to download mode, flashed TWRP, then rebooted again, set the phone up a bit more then decided to flash Magisk so I have root, and so far its working. 100% stock with magisk. Fingers crossed.
I still think there is an issue with the internal flash memory though as I can not get a TWRP backup to actually complete without failing. It always fails when backing up stuff in the data partition/section and never at the same point like its having read errors or something. I'll grab a TWRP log and post it up in a bit.
Well, that didnt last long. Within an hour, apps started crashing. I will make this thing work! LoL