Hello! This is my first time creating a post for a problem I had because I'm really desperate.
Some days ago, my Note 8 showed the wet port notification and gave some problems when charging. Then, the notification dissapeared but the problems remained. For some days, I've not been able to charge the mobile when it had battery. I had to wait until it was completelly empty, not just to turn off, but to not be able to turn on again. That's the only time when it charged. I've tried to reinstall the original ROM (I don't remember wich one I have but I installed some things and rooted the phone when I got it, half a year ago.), but I can't use ODIN as when I connect it to my PC it says that the device was not recognised and is not detected at all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've now wiped the phone and I think that now is able to charge when off, but I'm not sure as it seems to charge whenever it wants.
Thanks for the help to anyone who responds.
[Update]
I've wiped dalvik cache and it seems to charge while on. But my PC still doesn't recognise it.
[Update]
Fast charging does not work, just as before (when it charged was on slow mode).
[Update]
As root was not installed I thought that maybe I had the stock fimware and disabled OEM Unlock. Now it gives me the "Custom binary blocked by FRP Lock." error both on system and twrp so I'm bricked. Also, Odin still doesn't recognise the phone. I don't know what to do now...
Related
Hi,
My problem is yesterday, I tried to upgrade my Tab from 2.3.4 OS to 4.0.4 OS using Odin v1.85 and aokp ICS rom. During the process, I realized that I hadn't recharged the tab to full battery (as I remember, it was around 30 - 50%). The upgrade failed and now my Tab is bricked.
I tried to connect it to main AC power, for several hours, it came up like below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And no matter how I try to boot it up, using vol up/vol down + power button,...etc, it always kind of shutting down, battery icon disappears then after several hours, it turns back on again.
Any ideas? I really need your help
Can you try to enter into recovery mode or download mode? Try to enter to download mode and install stock rom from from this link. If you want install Cyanogenmod. Cyanogenmod is curently have version 4.2.2 and have so many things and you can install updates like piece of cake he said to you updates are available and you download and install it with no roblems. If you are interested for Cyanogenmod see on this Youtube channel how to install Cyanogenmod and root your tablet.http://www.youtube.com/watch?v=iI79j97R4qw
Reply
Thanks but somehow I let the battery drained to zero, then recharged it and connected to the PC, restored the tab normally through its factory mod. Again thank you!!
I was using Night Owl Beta 4 on my n7000 yesterday.. today morning when i woke up.. The screen wasnt responding to the power button so i rebooted the phone by pressing the power button for 5secs.. the phone got stuck on the samsung screen which comes in the starting.. then i tried to wipe data/factory reset through recovery because i hadnt taken a backup..so that got stuck too. so i decided to flash the stock rom via odin but no that is getting stuck too! please help!!! :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Now the device doesnt even go to download mode.. and when i connect the usb to pc it says SEC S5PC210 Test B/D
I assume you tried to flash with an old battery or a not fully charged battery.
The driver message SEC S5PC210 Test B/D is a hint for a corrupted bootloader (search XDA and you can see by yourself).
You'll find this thread with an old search by me two years ago. It seems that only a Samsung repair center will help.
Nope. The battery was atleast 80% when i tried to flash!
ThaiDai said:
I assume you tried to flash with an old battery or a not fully charged battery.
The driver message SEC S5PC210 Test B/D is a hint for a corrupted bootloader (search XDA and you can see by yourself).
You'll find this thread with an old search by me two years ago. It seems that only a Samsung repair center will help.
Click to expand...
Click to collapse
I think the emmc is damaged..
So recently I did a stupid and accidentally switched off my OPO during an update installation and completely screwed it all up. I tried switching it back on only to find that it was stuck in a recovery mode loop. I then hit factory reset in a last ditch attempt to save the poor bugger without flashing it and even that didn't work.
I've then had to resort to flashing it using the OPO toolkit software on my PC however when connecting to the PC, my OPO only shows up as an MTP USB Device and nothing else. I have tried installing recommended Samsung drivers for the phone but I wasn't able to as it the "update drivers" button was greyed out on the MTP USB Device properties window.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically, the OPO toolkit will not work as no android devices are recognised by the PC even though an android device is showing up in the control panel.
There is no way I can currently access the settings on my phone due to recovery mode loop obviously.
The last thing I want to do here is end up with being forced to use the OnePlus support which I hope most of you understand why.
Thanks for any suggestions!
Hi,
This thread is being moved to your own dedicated forum , where the experts may be able to help you better.
Good luck!
Put it in downloading mode and then use adb to use the toolkit since bow u don't have a os on the OPO happened with me too but I fixed it this way
Sent from my A0001 using Tapatalk
My LG D415 has been acting weird lately. The phone would randomly reboot even in TWRP and when the phone is actually usable, the hardware buttons + touch would not work for a minute or two sometimes. Then out of the blue one day the phone just bricked itself and was detected as Qualcomm HS-USB QDloader 9008 when plugged into a PC. Since theres no known way for D415 users to get out of that I just simply left the phone alone for a few days and it started working again somehow. I reflashed the bootstack and went back to CM13 (was on turbo 7.0) and that seemed to stop the random bricking but the random reboots still occur along with the hardware issues.
The thing that really freaked me out was when I adb shell my phone and got garbled text for the phone name
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What i'm really wondering is if my D415 board is screwed and if it is could I fix this with reflashing the .kdz?
The phone appears not to turn on but when I plug it in it mounts as a usb?
Inside theres modem files and such. Totally clueless on what to do here I need help ASAP!
Edit: I pulled the battery out in panic and plugged in the phone w/o battery and it shows a picture of a battery with a triangle BUT so i put battery back in and this time around it boots into fastboot and only fastboot.
Edit2: Pulled the battery again to try to get the phone to mount as a usb and instead started working normally again... fml
My Samsung Galaxy S Advance (GT-I9070) suddenly auto shutdown whenever i turn it on. I have tried flashing stock firmware using Odin but it didn't helped. Seems like the only thing i can do is booting phone in the download mode. And as i already told, i flashed stock firmware but nothing happened and it's still performing the same as before.
I hope you people understood the problem clearly. However, if you need any further information, please ask and i will answer you.
Regards
Does it work when plugged into a charger? The battery might be failing as it's probably old already.
3liteking148 said:
Does it work when plugged into a charger? The battery might be failing as it's probably old already.
Click to expand...
Click to collapse
When i plug it into a charger, it auto restarts (restart loop).
It also happened to me. The way, I repaired this, is a connnecting a external battery charger e.g.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and leaving it for approx. 12h, until it fullfil the accumulator.
luke9813 said:
It also happened to me. The way, I repaired this, is a connnecting a external battery charger e.g.
and leaving it for approx. 12h, until it fullfil the accumulator.
Click to expand...
Click to collapse
You mean, all i have to do is charging the battery 100% in an external charger?
Yes, that's it. Sorry for late reply.