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..
Hi guys, I am new here, I am now finding help anywhere about my Note III recent problem...
My note III is SM-N9005 Malaysia version, I did root it with CF Auto Root and I had been using it without problems until yesterday morning,
This is my case :
I realized my alarm was written "Clock has been not responding" and I lost my network service, then I tried to restart my phone,
Since I restart, it became worst, my phone went into boot loop and sometimes freeze on the "Samsung Galaxy Note 3" screen,
But in a few times of reboot, it will be able to boot into homescreen, but still no service for the network, and everything processes work extremely slow, even freezing and crashing!
What I tried to do to fix it :
-I went to the Samsung service center, and the technician said that my warranty is voided (Ofcourse I knew it), and he told me that this problem is due to software problem instead of hardware.
-I did flash my kernel with stock kernel again which was downloaded from Sammobile, but it did not fix my problem,
-And I tried to hard reset and factory reset of my phone, it did not help too,
-I am also tried to clear cache and dalvik cache and reboot the device, it didn't seems working...
I have already done what I could but I still yet to fix my phone, what should I do now, any experts can guild me?? T^T
Thank you
KelvinEclipse said:
Hi guys, I am new here, I am now finding help anywhere about my Note III recent problem...
My note III is SM-N9005 Malaysia version, I did root it with CF Auto Root and I had been using it without problems until yesterday morning,
This is my case :
I realized my alarm was written "Clock has been not responding" and I lost my network service, then I tried to restart my phone,
Since I restart, it became worst, my phone went into boot loop and sometimes freeze on the "Samsung Galaxy Note 3" screen,
But in a few times of reboot, it will be able to boot into homescreen, but still no service for the network, and everything processes work extremely slow, even freezing and crashing!
What I tried to do to fix it :
-I went to the Samsung service center, and the technician said that my warranty is voided (Ofcourse I knew it), and he told me that this problem is due to software problem instead of hardware.
-I did flash my kernel with stock kernel again which was downloaded from Sammobile, but it did not fix my problem,
-And I tried to hard reset and factory reset of my phone, it did not help too,
-I am also tried to clear cache and dalvik cache and reboot the device, it didn't seems working...
I have already done what I could but I still yet to fix my phone, what should I do now, any experts can guild me?? T^T
Thank you
Click to expand...
Click to collapse
have you done a EFS backup? it helps if you run into problems like this....
check here...http://forum.xda-developers.com/showthread.php?t=2298104
this works on note 8 though
welard said:
have you done a EFS backup? it helps if you run into problems like this....
check here...http://forum.xda-developers.com/showthread.php?t=2298104
this works on note 8 though
Click to expand...
Click to collapse
I didn't really know about EFS while I root my phone, I just knew it recently due to my current issue, so I didn't backup it....
Is there any other solution??? Or could I recover my EFS eventhough I didn't do a backup??
BTW, thx for reply~
KelvinEclipse said:
I didn't really know about EFS while I root my phone, I just knew it recently due to my current issue, so I didn't backup it....
Is there any other solution??? Or could I recover my EFS eventhough I didn't do a backup??
BTW, thx for reply~
Click to expand...
Click to collapse
check your internal card or sd card for a folder called Backups or something similar, if your running a custom rom normally EFS is automatically stored there if your custom rom does do EFS backup automatically at install....if not do a search on the forum for EFS RECOVERY or re-flash your rom it may help or may not, but im sure it wont though...
also read though the link i sent you there maybe some think there that may help you
you can try to do install new firmware with odin 3:09 kitkate see how it behaves ....
ANDROIDXFOREVER said:
you can try to do install new firmware with odin 3:09 kitkate see how it behaves ....
Click to expand...
Click to collapse
Its not bricked if its still working. Have you tried turning on your phone without a sim card / sd card inserted?
also try *#06# to see if your imei number is presant..
try flashing stock rom
in the same boat hope u get it sorted, i just flashed the omega v14 onto my note and its stuck on the first screen
yulaw5110 said:
in the same boat hope u get it sorted, i just flashed the omega v14 onto my note and its stuck on the first screen
Click to expand...
Click to collapse
Reboot into recovery and wipe cache partition and then scroll to advanced and wipe dalvik cache, then reboot your phone
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thanks guys for the replies
-I went for a search for the backup folder in either of the storage mentioned by I didn't see a file called "backup"... I think I deleted it since the factory reset I've done yesterday, I went to many forums hat talk about EFS, and it wont help my problem cos all of them are talk about "Backup/recover", where I didn't backup my EFS earlier...
-I tried for the IMEI code, that's the reason I know about EFS, it shows "null/null", and most the information are showing unknown, such as baseband version, IMEISV, IP Address, Bluetooth Address.
-My current situation is whatever I flash into my phone, it just wont help, the problem didn't improvise at all...
Thanks..
KelvinEclipse said:
Thanks guys for the replies
-I went for a search for the backup folder in either of the storage mentioned by I didn't see a file called "backup"... I think I deleted it since the factory reset I've done yesterday, I went to many forums hat talk about EFS, and it wont help my problem cos all of them are talk about "Backup/recover", where I didn't backup my EFS earlier...
-I tried for the IMEI code, that's the reason I know about EFS, it shows "null/null", and most the information are showing unknown, such as baseband version, IMEISV, IP Address, Bluetooth Address.
-My current situation is whatever I flash into my phone, it just wont help, the problem didn't improvise at all...
Thanks..
Click to expand...
Click to collapse
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
doodydood said:
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
Click to expand...
Click to collapse
Thanks for the reply
I have tried the odin method and it didn't work...
Now I am trying for the kies emergency recovery method, and I will reply if there are any improvements...
Hi guys, I think have some new clues to determine my problem now
I flashed a custom recovery into my phone this morning,
and I realise that my /system, /efs and /firmware-modem is unmounted,
I tried to mount them, it was successful, but when I reboot the device, the problem still there,
Boot loop, no IMEI, no Baseband Version, Lag Processes,
and I went back to recovery again, I realised they have been unmounted again...
Any idea what is the problem guys??
Thx
doodydood said:
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
Click to expand...
Click to collapse
Hi there,
I have tried the kies emergency recovery method, but it was unsuccessful,
My note 3 was connected to the kies, but when I run Emergency Firmware Recovery,
My device was instantly disconnected with kies
And I have also tried the Firmware Upgrade and Initialisation,
The Kies showed me that my device is not supported with initialisation...
Anything I should do??
Thx
speedyjay said:
Reboot into recovery and wipe cache partition and then scroll to advanced and wipe dalvik cache, then reboot your phone
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i actually found a different kernal in the omega thread and that seemed to sort it, thanks tho
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
not_su said:
I made the mistake of encrypting my phone and am now paying the price. It is rooted and I had installed the Google Edition 4.4.2 ROM by Danvdh, Kryten2k35 & Ktoonsez. I'm using TWRP 2.7.0.1.
I first tried going into recovery and doing a factory reset and got the an "Unable to mount '/data'" error, followed by a big red FAIL. So I rebooted into the system and tried to do a factory reset from there. Went through all the steps, phone rebooted into recovery and I got the same error - unable to mount.
So I did a bit of searching on the forums here and someone had suggested using the format option in TWRP. So I did that and it seemed to work - did not get the dreaded unable to mount error. So I tried flashing the new rom (the updated version from a couple of weeks ago). Got a message indicating it was successful. Rebooted, and to my dismay, got the prompt for the encryption password. Saw the little line drawing Android, then... nothing - I found myself in brick land.
Managed to get back into TWRP and, based on another post I found, tried Advanced Wipe, selecting everything except Micro SDcard and USB-OTG. Tried installing the new ROM again, says successful, but nothing has changed - I still boot into blackness after inputting my encryption password.
Not sure what else to try. Any suggestions would be most appreciated.
Click to expand...
Click to collapse
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Rhymey said:
Can you go into download mode, revert back to a stock rom (or flash a stock one or something) and turn encryption off? edit: on further research it looks like the only way to completely unencrypt is to reset your device. dunno if that's something you'd want to try, but considering you already wiped multiple times.. i'd say try it?
Thanks - that's exactly what I've been trying to do. I haven't tried reflashing back to stock with Odin though. Hmmm...
Also what carrier do you have? That's pretty important. AT&Ts i337 and Verizon's variant cannot flash AOSP roms (more specifically, kernels) due to the bootloader being locked. That might be the issue you're experiencing? I looked up the ROM and it's using ktoonsez kernel, so I imagine that'd be why. Someone just made a version that does not include the kernel and has multiple issues the ROM you're trying to use fixed here.
Click to expand...
Click to collapse
Bell, up here in the Great White North. I don't think locked bootloader is an issue - I was on the previous version of Danvdh's ROM, and everything was hunkydory. I just made the unfortunate decision to encrypt. Big mistake.
May try flashing back to stock. Nothing to lose, at this stage...
Thanks!
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
not_su said:
Hey just wanted to mention for the benefit of anyone else who got into this bind, flashing back to stock using Odin did the trick. Still wouldn't boot, but then I rebooted into stock recovery and did a factory reset, and finally was able to reboot back into stock. What a nightmare. Ugh. Thanks for the tip though - never occurred to me to try to go back to stock. Lesson learned though - no more encryption for me!
Click to expand...
Click to collapse
Good to hear. Should be able to flash to the rom once again no problem now that it's unencrypted!
please help cant get a new phon for another year and this one I almost want to throw in the garbage. Every couple of weeks i get the error saying cant establish a reliable connection for the google play store. Normally I can clear the cache and what not and clear the acount relog in and its fixed. This time nothing I could do that people suggested would help and the last option I had was to restore the phoone. So i restored the phone on the stock firmware for 4.2.2. Got the phone booted up and now my wifi is "turning on" and is stuck there. I've tried a few suggestions of reflashing stock firmware again, clearing ram, rooting the phone. and so far nothing. Please help im getting extremely frustrated and dont no what to do.
kasek55 said:
please help cant get a new phon for another year and this one I almost want to throw in the garbage. Every couple of weeks i get the error saying cant establish a reliable connection for the google play store. Normally I can clear the cache and what not and clear the acount relog in and its fixed. This time nothing I could do that people suggested would help and the last option I had was to restore the phoone. So i restored the phone on the stock firmware for 4.2.2. Got the phone booted up and now my wifi is "turning on" and is stuck there. I've tried a few suggestions of reflashing stock firmware again, clearing ram, rooting the phone. and so far nothing. Please help im getting extremely frustrated and dont no what to do.
Click to expand...
Click to collapse
aalso when i reboot it says SEandroid error for kernel... anyone no how to make that stock as well. and when i went to make a phone call i dial hit call and then screen flickers just goes black and no sound and nothing shows up only way to exit is restarting phone
If you have flashed the nb1 tar file and you still have problems I'm afraid it's a hardware problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you have flashed the nb1 tar file and you still have problems I'm afraid it's a hardware problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
well none of those problems were there before i flashed stock firmware, which makes me wonder if its cuz im not on a stock kernel? Im not sure what you mean by nb1 file though
i flashed cyanogenmod and now its working fine
Howdy, att s5 active was acting up so i downloaded the stock ne4 firmware from sammobile and flashed it via odin. Now the phone is stuck at the s5 splash screen and refuses to boot. I have tried booting into recovery and wiping cache and performing a factory reset to no avail. I have also tried using the firmware upgrade feature in kies but this did not work either. I am at a loss if anyone could point me in the right direction to help me get this thing working again i would be very appreciative.
The phone is completely stock , never rooted or messed with recovery or anything like that.
spazzd said:
Howdy, att s5 active was acting up so i downloaded the stock ne4 firmware from sammobile and flashed it via odin. Now the phone is stuck at the s5 splash screen and refuses to boot. I have tried booting into recovery and wiping cache and performing a factory reset to no avail. I have also tried using the firmware upgrade feature in kies but this did not work either. I am at a loss if anyone could point me in the right direction to help me get this thing working again i would be very appreciative.
The phone is completely stock , never rooted or messed with recovery or anything like that.
Click to expand...
Click to collapse
For anyone experiencing issues similar to what I was i believe i have found a solution : eventually i was able to get 4.4.2 to boot fully up - but then began to experience random resets. What I did was go into developer options and switch from dalvik to art. After all of the apps were done optimizing the s5 active now works perfectly, without issue. Hopefully this information helps someone else get theirs working properly.
hello
What firmware you flas first time? ???4.4.2???
Petreion said:
What firmware you flas first time? ???4.4.2???
Click to expand...
Click to collapse
yeah the ne4 firmware .