Related
Alright, So I bought a brand-new Galaxy S4 i-9500 a couple of weeks back. Ever since day one, the phone has major problems working with my Sandisk Class 10 64gb sdxc card, which I was using in my Galaxy Note N7000, without any problems. The card also works perfect in my wife's Galaxy S3 i9300.
The problems include:
-> The phone showing card as "Damaged" and not mounting it.
-> Sometimes it mounts the card, but shows the card as 'Blank' or 'Wrongly Formatted'
-> And yet sometimes, it mounts the card, but does not read some specific files. Opening those will give a message which says "File format not supported". In the process, the phone heats up to pretty nasty levels, and the battery drain will be massive. The phone also becomes very slow, gets stuck, and sometimes even restarts, and the problem keeps continuing.
If I remove the memory card, the phone works like a charm. I tried a 16gb memory card which also produced more or less the same results.
Now, the real problem is this. Recently, I had tried to root the phone, and for that purpose, I tried flashing CWM from cofface, through ODIN 3.07 and 1.85. Both the times, the flashing process was successful, with ODIN giving the green "PASS" message. However, nothing seemed to change on my phone, and CWM was never installed. I could never get the CWM screen no matter what I tried (every instruction on the net, literally). I then left the matter.
When my aforementioned card problem bothered me a lot, today, I decided to re-flash the stock firmware to my phone. So I downloaded the stock ROM from Sammobile, the correct pit file from XDA and started the flash process. Flashing was successful, as shown by ODIN, and the phone rebooted. But to my horror, the phone was exactly in the same state, when I had switched it off. Nothing was ever changed, all my files and everything were intact, and nothing had happened at all!!!!
How is this possible??? The bootloader shows "Downloading" and the blue bar while flashing, ODIN shows everything and even says it succeeded, but then how come things on my Phone remains absolutely unchanged??? So then what did it re-flash and where to?? And is there any way to get rid of this memory card problem??
I googled a lot to see if anyone else is experiencing the same problem as mine, but never found anything, which leads me to believe that my device is one weird thing!
vivz990 said:
Alright, So I bought a brand-new Galaxy S4 i-9500 a couple of weeks back. Ever since day one, the phone has major problems working with my Sandisk Class 10 64gb sdxc card, which I was using in my Galaxy Note N7000, without any problems. The card also works perfect in my wife's Galaxy S3 i9300.
The problems include:
-> The phone showing card as "Damaged" and not mounting it.
-> Sometimes it mounts the card, but shows the card as 'Blank' or 'Wrongly Formatted'
-> And yet sometimes, it mounts the card, but does not read some specific files. Opening those will give a message which says "File format not supported". In the process, the phone heats up to pretty nasty levels, and the battery drain will be massive. The phone also becomes very slow, gets stuck, and sometimes even restarts, and the problem keeps continuing.
If I remove the memory card, the phone works like a charm. I tried a 16gb memory card which also produced more or less the same results.
Now, the real problem is this. Recently, I had tried to root the phone, and for that purpose, I tried flashing CWM from cofface, through ODIN 3.07 and 1.85. Both the times, the flashing process was successful, with ODIN giving the green "PASS" message. However, nothing seemed to change on my phone, and CWM was never installed. I could never get the CWM screen no matter what I tried (every instruction on the net, literally). I then left the matter.
When my aforementioned card problem bothered me a lot, today, I decided to re-flash the stock firmware to my phone. So I downloaded the stock ROM from Sammobile, the correct pit file from XDA and started the flash process. Flashing was successful, as shown by ODIN, and the phone rebooted. But to my horror, the phone was exactly in the same state, when I had switched it off. Nothing was ever changed, all my files and everything were intact, and nothing had happened at all!!!!
How is this possible??? The bootloader shows "Downloading" and the blue bar while flashing, ODIN shows everything and even says it succeeded, but then how come things on my Phone remains absolutely unchanged??? So then what did it re-flash and where to?? And is there any way to get rid of this memory card problem??
I googled a lot to see if anyone else is experiencing the same problem as mine, but never found anything, which leads me to believe that my device is one weird thing!
Click to expand...
Click to collapse
Same problem for me... i wanted reinstall the stock firmware completely but when i flashed it with ODIN nothing happened...
Markz88 said:
Same problem for me... i wanted reinstall the stock firmware completely but when i flashed it with ODIN nothing happened...
Click to expand...
Click to collapse
Odin doesnt wipe your device or delete anything of your data...
If you flash the same firmware with your device firmware then nothing's really happened..
But if you root or change anything to system - boot - recovery - modem partition then simply is going again to stock or to the version you flash..
Thanks
Maybe there is something wrong with flashing memory (emmc).
There is an app on play store to check it, but i dont know if it works on s4.
I suggest to replace your phone. Or send it to service center
Edit: flash another different stock firmware, and check pda and csc if has changed
sent from my galaxy
vivz990 said:
Alright, So I bought a brand-new Galaxy S4 i-9500 a couple of weeks back. Ever since day one, the phone has major problems working with my Sandisk Class 10 64gb sdxc card, which I was using in my Galaxy Note N7000, without any problems. The card also works perfect in my wife's Galaxy S3 i9300.
The problems include:
-> The phone showing card as "Damaged" and not mounting it.
-> Sometimes it mounts the card, but shows the card as 'Blank' or 'Wrongly Formatted'
-> And yet sometimes, it mounts the card, but does not read some specific files. Opening those will give a message which says "File format not supported". In the process, the phone heats up to pretty nasty levels, and the battery drain will be massive. The phone also becomes very slow, gets stuck, and sometimes even restarts, and the problem keeps continuing.
If I remove the memory card, the phone works like a charm. I tried a 16gb memory card which also produced more or less the same results.
Now, the real problem is this. Recently, I had tried to root the phone, and for that purpose, I tried flashing CWM from cofface, through ODIN 3.07 and 1.85. Both the times, the flashing process was successful, with ODIN giving the green "PASS" message. However, nothing seemed to change on my phone, and CWM was never installed. I could never get the CWM screen no matter what I tried (every instruction on the net, literally). I then left the matter.
When my aforementioned card problem bothered me a lot, today, I decided to re-flash the stock firmware to my phone. So I downloaded the stock ROM from Sammobile, the correct pit file from XDA and started the flash process. Flashing was successful, as shown by ODIN, and the phone rebooted. But to my horror, the phone was exactly in the same state, when I had switched it off. Nothing was ever changed, all my files and everything were intact, and nothing had happened at all!!!!
How is this possible??? The bootloader shows "Downloading" and the blue bar while flashing, ODIN shows everything and even says it succeeded, but then how come things on my Phone remains absolutely unchanged??? So then what did it re-flash and where to?? And is there any way to get rid of this memory card problem??
I googled a lot to see if anyone else is experiencing the same problem as mine, but never found anything, which leads me to believe that my device is one weird thing!
Click to expand...
Click to collapse
go to this link....
http://forum.xda-developers.com/showthread.php?t=2219803
get rooted from here ( even if u are)
in the same page u get a link to flash back to stock recovery. get that flashed
boot into stock recovery and get a factory reset done.
pull battery and back in...
turn on ur phone into download mode and flash ur stock rom using odin....
this is how i got mine working.... i had ur similar issue....
kiwimalayalee said:
go to this link....
http://forum.xda-developers.com/showthread.php?t=2219803
get rooted from here ( even if u are)
in the same page u get a link to flash back to stock recovery. get that flashed
boot into stock recovery and get a factory reset done.
pull battery and back in...
turn on ur phone into download mode and flash ur stock rom using odin....
this is how i got mine working.... i had ur similar issue....
Click to expand...
Click to collapse
ok..will try this now...my last resort
vivz990 said:
ok..will try this now...my last resort
Click to expand...
Click to collapse
i assure u its gonna work perfectly...
I am literally having the same problem on my S4 I337M, I'm gonna try what was suggested on here, maybe it'll work lol
i have exactly the same problem right now, i searched for a solution and i found ur thread.
going through the thread to see a solution
vivz990 said:
ok..will try this now...my last resort
Click to expand...
Click to collapse
was ur problem solved after flashing cf-auto_root? i mean were u then able to flash custom recovery via odin?
Is solved?
vivz990 said:
... I decided to re-flash the stock firmware to my phone. So I downloaded the stock ROM from Sammobile, the correct pit file from XDA and started the flash process. Flashing was successful, as shown by ODIN, and the phone rebooted. But to my horror, the phone was exactly in the same state, when I had switched it off. Nothing was ever changed, all my files and everything were intact, and nothing had happened at all!!!!
How is this possible??? The bootloader shows "Downloading" and the blue bar while flashing, ODIN shows everything and even says it succeeded, but then how come things on my Phone remains absolutely unchanged??? So then what did it re-flash and where to?? And is there any way to get rid of this memory card problem??
I googled a lot to see if anyone else is experiencing the same problem as mine, but never found anything, which leads me to believe that my device is one weird thing!
Click to expand...
Click to collapse
OMG. I just experienced the EXACT same issue with a Galaxy Exhibit (MetroPCS) SGH-T599. I picked up this phone 2nd hand. It has Philz Touch v6.25 recovery already installed on it. But the phone is stuck in a boot loop. So I decided to flash the stock ROM, a custom ROM via ODIN and later even via flashable zips from the Philz recovery! I even tried to flash TWRP to replace Philz Touch thinking there was something wrong with Philz recovery.
No matter what I did, EVERY TIME, the phone remained in EXACTLY the same state, i.e., with Philz recovery still on there.
I have searched everywhere for the last 3 days including XDA but never found anyone else with the same ODIN flashing issue. Thank goodness I found your post. I'm reading the thread now looking for a solution.
I've noticed a couple other things beneath the surface. When I flashed a CM custom ROM for the phone, the default.prop indicated that there was a new system on the phone (I can access the phone via ADB and look at the files including the system files). It also appears the phone was rooted by the previous owner. Another thing I noticed is that some cases when I tried to install a custom ROM via the custom recovery, the phone would suddenly reboot just at the point the recovery attempts to write the ROM.
Yes, it is clear the phone is good and bricked. But how on earth to unbrick it if ODIN isn't actually changing ANYTHING on the phone and installing a ROM via Philz recovery changes little to nothing either.
CVAngelo said:
OMG. I just experienced the EXACT same issue with a Galaxy Exhibit (MetroPCS) SGH-T599. I picked up this phone 2nd hand. It has Philz Touch v6.25 recovery already installed on it. But the phone is stuck in a boot loop. So I decided to flash the stock ROM, a custom ROM via ODIN and later even via flashable zips from the Philz recovery! I even tried to flash TWRP to replace Philz Touch thinking there was something wrong with Philz recovery.
No matter what I did, EVERY TIME, the phone remained in EXACTLY the same state, i.e., with Philz recovery still on there.
I have searched everywhere for the last 3 days including XDA but never found anyone else with the same ODIN flashing issue. Thank goodness I found your post. I'm reading the thread now looking for a solution.
I've noticed a couple other things beneath the surface. When I flashed a CM custom ROM for the phone, the default.prop indicated that there was a new system on the phone (I can access the phone via ADB and look at the files including the system files). It also appears the phone was rooted by the previous owner. Another thing I noticed is that some cases when I tried to install a custom ROM via the custom recovery, the phone would suddenly reboot just at the point the recovery attempts to write the ROM.
Yes, it is clear the phone is good and bricked. But how on earth to unbrick it if ODIN isn't actually changing ANYTHING on the phone and installing a ROM via Philz recovery changes little to nothing either.
Click to expand...
Click to collapse
Totaly same problem with my Galaxy Note 10.1 (N8010). Tried flash stock ROM over Odin a totaly nothing changed. It is in bootloop everytime with totaly same Marshmallow logo, even if I flash stock ROM which is KitKat... Only sometime it boot to system where it say to me "Encryption unssucessfull" - WTF? i never have password, and when i click on something it just reboot to BootLoop...
I have TWRP recovery on it, but when i want to flash some ROM it flash it but nothing change... Maybe EMMC memory chip is death or I dont know...
Fellas, try on other PC/Laptop or reinstal Windows/Ubuntu whatever you use... That helped me..
Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.
engwee said:
Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.
Click to expand...
Click to collapse
read this - http://forum.xda-developers.com/note-4/help/note-4-issues-t3453048
there are links to more threads related to your issue.
Short version though:
it is dying. install wake lock application, add it to start up and set settings to #4.
accept the fact that your phone will eat the battery faster and one day WILL die completely
Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.
engwee said:
Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.
Click to expand...
Click to collapse
no need to be rooted, just download, install and set it to autostart
I'll try it if I somehow manage to get the phone working again, Smart Switch just fails now midway through.
golden_m said:
no need to be rooted, just download, install and set it to autostart
Click to expand...
Click to collapse
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.
engwee said:
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.
Click to expand...
Click to collapse
yes, that is the app.
i've read it does not allow your phone to go to sleep mode.
drains the battery faster, but this is the only way to keep note 4 working without swapping its motherboard...
I have a question, my gf recently bought a note 4 and we may swap our phones and if we do, i'll flash CM and tinker with it because i find this phone very interesting, just a question, does this bug affect the N910C (exynos) model? Do i have something to worry about? Because the phone is warrianty protected and if it's the case, i don't want to break it. I hope someone will shed some light on this
A friend gave me a bricked samsung S5, he bought it while he was in China and upon coming home it wouldn't read the sim card so somehow he got to the conclusion that it was a copy and he bricked it.
Now two years forward he gave it to me, and I discovered that it wasn't a copy. I unbricked it but I have been having problems with the screen, when the phone goes to sleep and I try to wake it up only the buttons and the led will turn on, I can hear the phone vibrate and I can contact it via adb.
It also happens when I try to turn on the device, sometimes the screen will turn on sometimes it won't, the same with recovery and download mode.
This is what I have done to the phone until now:
1. Flashed twrp.
2. Flashed several custom roms.
3. Flashed the samsung firmware including the stock recovery (I had to flash each img separately since hidden.img wouldn't flash properly)
However still the problem persist, I have tried several solutions that I have seen online but none works and I am out of ideas.
Same Thing
loomely03 said:
A friend gave me a bricked samsung S5, he bought it while he was in China and upon coming home it wouldn't read the sim card so somehow he got to the conclusion that it was a copy and he bricked it.
Now two years forward he gave it to me, and I discovered that it wasn't a copy. I unbricked it but I have been having problems with the screen, when the phone goes to sleep and I try to wake it up only the buttons and the led will turn on, I can hear the phone vibrate and I can contact it via adb.
It also happens when I try to turn on the device, sometimes the screen will turn on sometimes it won't, the same with recovery and download mode.
This is what I have done to the phone until now:
1. Flashed twrp.
2. Flashed several custom roms.
3. Flashed the samsung firmware including the stock recovery (I had to flash each img separately since hidden.img wouldn't flash properly)
However still the problem persist, I have tried several solutions that I have seen online but none works and I am out of ideas.
Click to expand...
Click to collapse
I hope I am doing this right not on forums much. I am having the same issues. Any solutions
loomely03 said:
A friend gave me a bricked samsung S5, he bought it while he was in China and upon coming home it wouldn't read the sim card so somehow he got to the conclusion that it was a copy and he bricked it.
Now two years forward he gave it to me, and I discovered that it wasn't a copy. I unbricked it but I have been having problems with the screen, when the phone goes to sleep and I try to wake it up only the buttons and the led will turn on, I can hear the phone vibrate and I can contact it via adb.
It also happens when I try to turn on the device, sometimes the screen will turn on sometimes it won't, the same with recovery and download mode.
This is what I have done to the phone until now:
1. Flashed twrp.
2. Flashed several custom roms.
3. Flashed the samsung firmware including the stock recovery (I had to flash each img separately since hidden.img wouldn't flash properly)
However still the problem persist, I have tried several solutions that I have seen online but none works and I am out of ideas.
Click to expand...
Click to collapse
Hi,
You didn't mention a factory reset nor internal memory full wipe. Have you tried these?
JCSIGNGUY said:
I hope I am doing this right not on forums much. I am having the same issues. Any solutions
Click to expand...
Click to collapse
I did a factory reset and wiped the cache later on and it helped a bit but it still constantly turns off.
Same thing
loomely03 said:
I did a factory reset and wiped the cache later on and it helped a bit but it still constantly turns off.
Click to expand...
Click to collapse
I took cm 14 completly off took off GAPPS 7.1 wiped everything reformated micro sd . Went downloaded CYAN13 and GAPPS 6 saved to micr sd card and reinstalled all that . It seems to have worked. I don't know if it was me or I got a buggy CYAN14 probaly me.
JCSIGNGUY said:
I took cm 14 completly off took off GAPPS 7.1 wiped everything reformated micro sd . Went downloaded CYAN13 and GAPPS 6 saved to micr sd card and reinstalled all that . It seems to have worked. I don't know if it was me or I got a buggy CYAN14 probaly me.
Click to expand...
Click to collapse
I will try that, the phone worked fine for like 5 days but now the screen wont turn on, even when I try to access recovery or download mode.
I have a I9505 and it was working fine (samsung ROM), when I decided to 'encrypt' my device! It was fully charged and connected to a charger.
After starting, it stayed connected for 5-6 hours, but nothing was seemingly happening.. After 6 hours I switched it off. Then back on again.
The device after starting (just the system) didnt let me do anything else, and told me that since encryption failed, I need to format the device. So I restarted, formatted. Still same msg
Wiped the device completely. Still same issue. Tried changing file system from ext4 to ext2.. still same problem! I installed a couple of roms, they seemingly installed ok, but after starting, the same msg!
Please help me!
My bootloader is TWRP by teammate I think
Did you attempt to flash the stock ROM via Odin?
find a place that can do a JTAG
I had this issue last week.
1. Flash Stock rom with Odin
2. Boot into stock recovery (Must be stock)
3. Choose factory reset
Fixed.
SOLVED
Thank you guys! Flashing with ODIN worked fine! Not sure why I didnt think of that earlier!!
hdaackda said:
I have a I9505 and it was working fine (samsung ROM), when I decided to 'encrypt' my device! It was fully charged and connected to a charger.
After starting, it stayed connected for 5-6 hours, but nothing was seemingly happening.. After 6 hours I switched it off. Then back on again.
The device after starting (just the system) didnt let me do anything else, and told me that since encryption failed, I need to format the device. So I restarted, formatted. Still same msg
Wiped the device completely. Still same issue. Tried changing file system from ext4 to ext2.. still same problem! I installed a couple of roms, they seemingly installed ok, but after starting, the same msg!
Please help me!
My bootloader is TWRP by teammate I think
Click to expand...
Click to collapse
Dude did you try to use an aosp rom
So my dad is using the old S4 as 2nd phone for multimedia, gps etc. Recently he went and installed and app from store. He locked the phone and when he tried to unlock it, the phone started giving pink screen after swiping to unlock. I tried reinstalling the lineage os but after a reboot the same thing happend. Tried another rom but the phone got stuck in bootloop(keeps rebooting when trying to start up). So I decided to revert to stock ROM, flashed the pit though odin because it was throwing errors about it missing, then went and flashed the stock rom. Tried to start aaaaaand - bootloop. Any suggestions on what to do?
Try flashing the latest stock ROM again without a pit file and with the original Samsung USB cable.
audit13 said:
Try flashing the latest stock ROM again without a pit file and with the original Samsung USB cable.
Click to expand...
Click to collapse
Ok, I tried flashing stock lollipop(though not the one for my country). It tries to boot up, goes through the first model screen, starts the "samsung" animation, but only gets to show 3 letters before it goes black and restarts after 10-15secs. Is it hardware damaged or what? It is was used as secondary phone because it wouldnt read sim card anymore.
DId you perform a factory reset using stock recovery?
audit13 said:
DId you perform a factory reset using stock recovery?
Click to expand...
Click to collapse
yup
It could be pure coincidence but is it possible the internal memory is damaged? Possible loose connection?
audit13 said:
It could be pure coincidence but is it possible the internal memory is damaged? Possible loose connection?
Click to expand...
Click to collapse
dunno, the phone was used lately by my dad and he usually takes good care of phones. Before it was my sis phone(until sim wont read anymore) and well, it got dropped a lot.