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
(Sorry for bad english) i was on 4.4.4 then flashed the Poland Version of 5.0.1 from the thread i found from XDA, the flash went perfect and using the phone normally. but after few hours of usage, i noticed a heat from my pocket. the phone was rebooting constantly, at this time i didnt time the reboot time cycle, i booted the phone to TWRP then restored the 4.4.4 backup that i made, but the update didnt succeed, now i cant boot to the OS, when i got home i wiped all the data then flashed the 5.0.1 ROM again, but this time when its time for the "Updating apps x of xxx" it will reboot indefinitely. i timed the reboot interval and it was exactly 60 seconds after the spinning circle stops and reboots again. i even tried to leave the phone for 20 mins to see what happens. but its still the same. Please someone help. i just got the phone this week and im desparate to find a fix.
carlosalgado123 said:
(Sorry for bad english) i was on 4.4.4 then flashed the Poland Version of 5.0.1 from the thread i found from XDA, the flash went perfect and using the phone normally. but after few hours of usage, i noticed a heat from my pocket. the phone was rebooting constantly, at this time i didnt time the reboot time cycle, i booted the phone to TWRP then restored the 4.4.4 backup that i made, but the update didnt succeed, now i cant boot to the OS, when i got home i wiped all the data then flashed the 5.0.1 ROM again, but this time when its time for the "Updating apps x of xxx" it will reboot indefinitely. i timed the reboot interval and it was exactly 60 seconds after the spinning circle stops and reboots again. i even tried to leave the phone for 20 mins to see what happens. but its still the same. Please someone help. i just got the phone this week and im desparate to find a fix.
Click to expand...
Click to collapse
did you flashed with odin 3.10.6 with adb enabled and run as administrator ?
samsung usb drivers installed ?
wiped data and cache before flashing ?
Salim.Keady said:
did you flashed with odin 3.10.6 with adb enabled and run as administrator ?
samsung usb drivers installed ?
wiped data and cache before flashing ?
Click to expand...
Click to collapse
i used Odin 3.09, wiped data and cache before and after installing. should i use odin 3.10.6?? does the Odin 3.09 causes this specific error?
carlosalgado123 said:
i used Odin 3.09, wiped data and cache before and after installing. should i use odin 3.10.6?? does the Odin 3.09 causes this specific error?
Click to expand...
Click to collapse
I cant confirm just use 3.10.6
Adb installed
Odin run as administrator...
Device drivers installed
I don't know but, if u did backup 4.4.4 rom, and flashed 5.0.1 rom, ur backup does not work cuz u have diffrent bootloader and modem in 5.0.1 than 4.4.4.
It's been awhile since I changed anything on this phone, I've been running CM11 with no issues. The wife was playing with my phone which is on cm12 and wanted me to upgrade it. Great, I hate having to touch her phone but ok.
1. Did a straight upgrade to CM12 nightly (couple nights ago build) with gapps from CM site. After the install everything crashes on the initial load, it's like the baseband is jacked and doesn't know how to handle the new google play services because everything crashes.
2. Went back and wiped internal everything this time, re installed nightly and gapps. No change.
3. Tried step 2 a couple more times and different gapps from PA and other random sites (micro, light, stock versions) and then TWRP just died on me. It's asking for a password when I first go in so now I'm stuck there. Tried to use ODIN to install the latest TWRP after converting it with another script found here (i'll find the link).
so, I'm probably going to have to use ODIN to restore some stock version of S4 ATT but I really don't know which one is stock that would work with CM12. I don't want to get caught in the safestrap crap of dual boot and whatever else. Any help is greatly appreciated.
You'll need to Odin the mdl firmware in Odin. Be careful as it will want to update itself after you flash it. See sammobile.com for the firmware.
Sent from my Nexus 9 using XDA Free mobile app
Awesome, thanks!
Flashed the stock, towelroot, twrp from google play and cm12 nightly. Perfect and back where I left off. Thanks!!
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
kronikwisdom said:
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset
Sent from my Nexus 9 using XDA Free mobile app
Ok, factory reset worked on the second try. Sent it in to a boot loop on the first go around, odd. Thanks!
For a week my G935A worked fine... direct out of the box I flashed ENG Kernel and Rooted, then installed apps and configured - no issues.
Today it was working then it hung on wake.. I tried to reboot and now it gets stuck at the AT&T logo and vibrates 3 times - over and over
I can get to Odin and Recovery screens easily so I tried to flash the ENG Kernel again & deleting Cache Partition few times - didnt fix it.
Also tried booting into Safe Mode - it never gets there, stays at AT&T logo.
When I go into the Recovery menu, I see at the bottom, in red... "dm-verity verification failed"
Anyone know how I can recover from this without Factory Reset? It took 6 hours to reinstall and config all my apps - really want to avoid that.
thx for the help!
as far as I know there is no way to fix and save your stuff. I had the same problem with G930A and even doing a factory reset would only allow my phone to boot but then I get apps crashing and then a reboot puts you back at ATT logo and the vibrates. Best to ditch the whole engboot and go back to stock until a more stable rooting method comes out.
Some searches shows posts that say using Odin to flash HOME_CSC without having to wipe and everything survive
... Where can I get HOME_CSC? I dl'd stock rom and dont see it in there.
thx!
Same here this morning on my 930A w/ PK1....went to watch a youtube vid and everything google related began crashing.
Only been on engboot for a couple days but did flash the v15 debloat last night. hmmmm.
Any luck with the files or procedure LivinOne?
Update: Flashed the PK1 CSC and got into recovery.
Wiped cache and reboot, same failure mode....sad face.
Flashed CSC again, into recovery, factory reset, wiped cache.
Back to setting my "new" device up.
Dec 30 update: Same crash, SEMI same problem.
I get the single vibration followed by the 3 vibrations after I put my pin in from a restart.
Same symptoms prior, all background activities began crashing.
Running all PK1 files from QRhinehardt post.
Any thoughts?
I ended up wiping and flashing the T-Mobile firmware and using the ENG bootloader (but not rooted yet). It is WAY faster than the AT&T was. I've only had issues with Wifi Calling (it doesnt seem to work most of the time)
s7 at&t
Hi, did you first flash with eng bootloader and then tmobile rom? I miss this step...I appreciate your help please
Single vibration followed by the 3 vibrations
Hi, were you able to fix the problem? I'm also getting the single vibration followed by the 3 vibrations.
Do you know why is this occurring? I performed a wipe cache and factory reset but still nothing.
bweegn said:
Same here this morning on my 930A w/ PK1....went to watch a youtube vid and everything google related began crashing.
Only been on engboot for a couple days but did flash the v15 debloat last night. hmmmm.
Any luck with the files or procedure LivinOne?
Update: Flashed the PK1 CSC and got into recovery.
Wiped cache and reboot, same failure mode....sad face.
Flashed CSC again, into recovery, factory reset, wiped cache.
Back to setting my "new" device up.
Dec 30 update: Same crash, SEMI same problem.
I get the single vibration followed by the 3 vibrations after I put my pin in from a restart.
Same symptoms prior, all background activities began crashing.
Running all PK1 files from QRhinehardt post.
Any thoughts?
Click to expand...
Click to collapse