after I upgrade my Note Edge on 6.0.1 OTA ( on the Air )
Ive turned off Location History, S-pen detection , and buy new battery to improve battery life
But, my phone got message ( couldn't use fingerprint after restart ) when im trying to used my phone
After i turn it off ( sleep )
- Phone cant be turned on immediately after I turned it off
then after a while I got this message ( couldnt start boot normally, ddi : mmc_read failed )
Any help ? about what might be happening ?
PS : Im trying to downgrade it to KK 4.4 but had no luck on rooting the device.
Any HELP appreciated. TQ
ps : green light with screen off blinking atm..
no simcard nor external sdcard installed
If you want to downgrade to kitkat try flashing stock firmware from manufacturer site
any link ? tks... and do umthink its the hardware issye or the software issue ?
It's probably software, not big deal.
It's better that you google it but search exact model you have that in 'About phone' or on box in which phone was when you bought it.
And just one more thing did you cleared cache after upgrade? Also factory reset would probably clean up the mess, than you'll probably could use phone with marshmallow on it normally.
tq, but we are suspecting the nvram...because off the symptoms and the excess heat.
and yes ive have wiped cache then factory reset it.
seniors, do u have any experienced IF the problem was NVRAM and it was replaced, will it last ? thx
Apparently the problems was the battery, Samsung Note Edges are very picky about the battery, even when I 've replaced the battery with new battery . Apparenty in my case the battery was not super ORI ( even since ive bought the batt with distributor logo on it ) with the same voltage and not even swollen.
nope, not the battery, im thinking of mainboard / ic power defect. since the battery cannot be recharged after forced shutdown
Related
Need to fix this for a friend...
He made some mistake or odin failed or smth when he tried to root.. not sure.. but download mode was working still..
No Problem I thought and told him to bring it over - but when I flashed the stock rom, odin failed again.. no problem still I thought.. happens and I'll look for another rom or a pit etc..
But then when I restarted it into download mode, it just turned off after a few secs and hasnt been turning on since then.
I'm guessing the battery is empty, since it wasnt charging for a while .. (kernel broken so it doesnt even charge when completely turned off..)
So I need to find a way to charge the battery, a new one costs like 40 or 50 euros and I would like to avoid buying one.. just to be able to get the thing into download mode again to fix the software..
Anyone know how to charge Tablet batteries externally? I already opened up the tablet and exposed the battery, but I know charging Li-Ion is difficult (if possible at all, without special equipment.) so I need some help please.
Hi guys,
I recently bough two S6-G920F really cheap (~80 euros each) that appeared to be functional, but with software issue (one wasn't booting up, the other was bootlooping), in hope of repairing them.
From the start, I'll tell you that the phones are currently at a GSM Service, at a hardware guy. I haven't heard from him yet (leaved them today in service). I tried all possible software solutions, no luck. I'm more interested to see if anyone else encountered these issue, what are the possible causes and maybe if someone managed to fix these kind of issues.
Device 1 : No physical damage on the phone itself or the board. The phone doesn't charge when plugged in, but (tries) to boot up as soon as it's connected. It gets stuck on the "powered by android" screen. I am able to enter download mode, but not into recovery (the button combo doesn't work). The battery itself charges ok externally on a jig. I'm not able to flash any kind of firmware on it with Odin, it always fails at system.img at random percentage. I can flash custom recovery / bootloader / kernel, but has no point, I can't get into recovery or past the the boot logo. If left plugged in on the download screen, the phone gets a bit hotter than normal (not sure if it's because of the screen always being on). While plugged in, the board draws constantly 700mah, not letting the battery charge. The guy I bought it off told me that it died suddenly while gaming and never turned on again.
Device 2 : Was dropped, cracked screen glass and back glass. It charges, I can get into download / recovery mode, i can flash any firmware I find. Doesn't get past the samsung logo (in case of 5.1.1) or the "installing system" screen (in case of 6.0.1). It either bootloops or it freezes. Tried custom rom, custom kernel, original firmware, they all do the same. Tried going into recovery and wiping cache & dalvik, and the phone got stuck on a black screen with the blue led always on. Had to disconnect the batter (key combo didn't want to work anymore). The guy I bought it off told me it worked fine with cracked screen until the 6.0.1 update kicked it, then it started bootlooping and it stayed like that.
What my best guess is :
Device 1 : a short somewhere on the motherboard. Didn't figure out yet where. Maybe caused by faulty charger?
Device 2 : faulty eMMC chip. That's the only thing I can think of that would make any kind of firmware I put on it freeze.
Did you guys ever encounter any of these issues before?
Cheers.
Seems your guesses are right, no i didnt encounter these problems before.
Hi guys,
Small update. Got the devices back from the GSM service, they didn't manage to do anything.
For device #2 I managed to get a stable recovery (that doesn't freezes) by flashing arter97's recovery. From here I proceeded to installing custom ROM/kernels, but no luck, still freezing on the Samsung logo once it reboots after install.
I have access to the terminal via TWRP. Any commands that I can use to do some memory / cpu checks?
Hello everyone
I have a Samsung Galaxy s6 G920F with stock rom.A couple of days back I did a factory reset from recovery in order to make it run smooth again since it was filled with bloatware and such after 6months of use.
All good until I saw a huge drop of battery with Android OS showing in everything ( stock battery consumption , gsam battery, betterbatterystats etc.) The problem is that I cannot use Wakelock Detector because my phone USB suddenly stopped working.... I don't have warranty on the phone.Guys from phone service in my town told me that if i want to change the charger band they have to remove the display etc...( I use a wireless charger)
I tried 3 times to factory reset, clear cache daily, etc... nothing.
NOTE : Even in Safe Mode I have Android OS on top at battery consumption...
What I want to know is , if I can flash a stock rom without root/usb working.
Thanks !
Thread closed, OP reposted
http://forum.xda-developers.com/showthread.php?t=3457580
Good day guys.
[EDIT] : The phone turned on now, it was just completely deprived of battery power ( I'm unsure how to delete this so I'm hoping a mod will see this and remove it as its a "false alert" )
I recently smashed my note 4 ( the seat of the car completely broke it in half, long story ), so I got a tablet that was laying around as a backup, A Samsung Tab 2 ( p3100 ), it was loaded with bloatware from my carrier so I decided to flash cyanogenmod 13 onto it... all went well and soon I booted into the new OS.
I installed the applications I needed from the play store no problem, everything seemed fine, I talked to some of my friends using the phone with absolutely no problems...
That's when I noticed it was getting low on power ( 2% ) , so I told them that I'm going to put it on charge and go to sleep ( this was well over 2 hours post-flash ) , as I reached for the charging cable, the phone showed me a blue face ( cyanogen's logo )
I proceeded to plug in the phone to charge ( thinking it was just turning off ) , but the blue guy stayed on for about another 1 minute, then the screen turned pitch-black.
( at which point the phone refused to turn on at all, no matter how long i press the power button )
I'm hoping I'm wrong, but it seemed to have hard-bricked, but seeing as the phone booted into the OS no problems etc. I'm hopeful...
Does anyone have any insights as to what's going on? can a phone brick even after extended use of the custom OS??
Any help would be appreciated,
Thanks.
Kazutox said:
Good day guys.
[EDIT] : The phone turned on now, it was just completely deprived of battery power ( I'm unsure how to delete this so I'm hoping a mod will see this and remove it as its a "false alert" )
I recently smashed my note 4 ( the seat of the car completely broke it in half, long story ), so I got a tablet that was laying around as a backup, A Samsung Tab 2 ( p3100 ), it was loaded with bloatware from my carrier so I decided to flash cyanogenmod 13 onto it... all went well and soon I booted into the new OS.
I installed the applications I needed from the play store no problem, everything seemed fine, I talked to some of my friends using the phone with absolutely no problems...
That's when I noticed it was getting low on power ( 2% ) , so I told them that I'm going to put it on charge and go to sleep ( this was well over 2 hours post-flash ) , as I reached for the charging cable, the phone showed me a blue face ( cyanogen's logo )
I proceeded to plug in the phone to charge ( thinking it was just turning off ) , but the blue guy stayed on for about another 1 minute, then the screen turned pitch-black.
( at which point the phone refused to turn on at all, no matter how long i press the power button )
I'm hoping I'm wrong, but it seemed to have hard-bricked, but seeing as the phone booted into the OS no problems etc. I'm hopeful...
Does anyone have any insights as to what's going on? can a phone brick even after extended use of the custom OS??
Any help would be appreciated,
Thanks.
Click to expand...
Click to collapse
same thing happend with me... my device was galaxy grand 2... that dead.. may be its motherboared is dead coz of heavy usage
Hey folks,
I'm having a headache with my Samsung Galaxy S5 G900F, running latest official firmware 6.0.1. for Bulgaria. The phone is 1.5 year old, and it's till under warranty, in a mint condition (at least visually).
Yesterday I decided to make a software reset by the many in the operation system (factory reset) and after it did it thing it got stuck on the "SAMSUNG", which is the second thing that appears on the display after it's turned on.
The weird thing is that it starts to heat up quite much on the area on the left of the battery, about two inches above the loudspeaker and one inch down from the headphone jack, this is at the left side of the battery as you look at the phone from behind.
I took the battery off and tried the following:
- enter recovery mode and wipe cache partition and data/factory reset
- tried to boot multiple times
- repeated the two operations several times
- finally I decided to flash stock ROM for my device, which went normal. The knoxx hasn't counted the flash, which probably is a good thing, but...
None of these actions helped and the phone still gets stuck there and starts to heat up.
What is there, underneath that area?
What are your suggestions?
Could just fail of regular factory reset?
It's till under warranty and if I'm not sure it's a software problem, it's probably a bad idea to flash a custom ROM like CM or else.
What do you say?
Thanks!
Hey, the situation has resolved - it needed a very long time to load and I guess I didn't give it the time necessary.
Please, delete the thread, 'cause I ain't have clue how to do that!