So my issue is similar to the one of Spectre Nine here.
I have bought a N7100 in January 2013. Until about July it ran absolutely fine, but then it started freezing and rebooting at random.
Here is the data:
Model: GT-N7100
Android: 4.1.2
Baseband: N7100XXDLK7
Build: JZO54K.N7100XXDMB2
Country of origin: Austria
I am running a stock rom which was updated using Kies, afterwards root was installed using CF-Autoroot.
I have never used Odin or other flashing software, and I am also on stock recovery on this device.
TriangleAway has been used due to CF-Autoroot increasing the flash counter.
I have already ruled out the SIM and MicroSD cards, as it happens without them as well.
I noticed that there might have been some data corruption, as my SwiftKey dictionary got wiped for some reason.
Unfortunately, I have found no tools or ways to check the internal SD for errors as opposed to the external ones.
My questions are as follows:
1. Are there any tools or methods for checking the internal storage for file system errors?
2. Any ideas as to what could be causing this issue?
3. If I have to send the device in for repairs, is it enough to just remove the root (confirm device normal status) and do a factory reset?
Thank you very much for any leads or replies at all.
PS: I am trying to record a logcat to find out what happens before the reboot, will also attach it,
Crescento said:
So my issue is similar to the one of Spectre Nine here.
I have bought a N7100 in January 2013. Until about July it ran absolutely fine, but then it started freezing and rebooting at random.
Here is the data:
Model: GT-N7100
Android: 4.1.2
Baseband: N7100XXDLK7
Build: JZO54K.N7100XXDMB2
Country of origin: Austria
I am running a stock rom which was updated using Kies, afterwards root was installed using CF-Autoroot.
I have never used Odin or other flashing software, and I am also on stock recovery on this device.
TriangleAway has been used due to CF-Autoroot increasing the flash counter.
I have already ruled out the SIM and MicroSD cards, as it happens without them as well.
I noticed that there might have been some data corruption, as my SwiftKey dictionary got wiped for some reason.
Unfortunately, I have found no tools or ways to check the internal SD for errors as opposed to the external ones.
My questions are as follows:
1. Are there any tools or methods for checking the internal storage for file system errors?
2. Any ideas as to what could be causing this issue?
3. If I have to send the device in for repairs, is it enough to just remove the root (confirm device normal status) and do a factory reset?
Thank you very much for any leads or replies at all.
PS: I am trying to record a logcat to find out what happens before the reboot, will also attach it,
Click to expand...
Click to collapse
well flashing via kies must have created the issue, rather flash a stock rom via odin adn it wil be fine no need to send it for repairs follow ketan guide here in xda on the procedure to follow flashing rom using odin and everything will be fine.
so i definitely suspect kies for your problem
The Kies update happened in february, and the phone has been running fine until july.
If I use Odin, will Samsung be able to detect it in case I send it in?
shhbz said:
well flashing via kies must have created the issue, rather flash a stock rom via odin adn it wil be fine no need to send it for repairs follow ketan guide here in xda on the procedure to follow flashing rom using odin and everything will be fine.
so i definitely suspect kies for your problem
Click to expand...
Click to collapse
Crescento said:
The Kies update happened in february, and the phone has been running fine until july.
If I use Odin, will Samsung be able to detect it in case I send it in?
Click to expand...
Click to collapse
nope your device status must be normal now and binary count 0 so you good to give it now no need to flash anything via odin just unrootand check your system status
A follow-up here.
The issue suddenly disappeared about 3 weeks after my initial post.
I am baffled as to what could have caused this.
Occasionally, it still happens about once in two weeks.
I still couldn't find any tools to check the internal storage.
When 4.3 is out (probably soon for my provider), would a full wipe get rid of possible errors on the internal sd?
Related
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?
Hi,
I've been searching these forum for a while now looking for a solution, yet nothing helpful...
I have a galaxy note 2 SGH-i317m that I rooted last year. I unrooted it completely last month so that I can acces to the Samsung update to 4.3. BUT when I try to update, it tells me that my device has been modified.
I can hear your questions comming so:
Yes I triangled away before unrooting,
Yes I tried wipe the partition cache
Yes I try rerooting then unrooting again
My device status is "modified" in the settings but "custom" in download mode
Yes I'm running everything stock
Yes I tried removing the sd card, in fact I don't even put an sd card in these days
Yes I tried every single tutorial I could possibly found...
Well, now I'm kinda stuck.
Thanks for the help!
Emeriska said:
Hi,
I've been searching these forum for a while now looking for a solution, yet nothing helpful...
I have a galaxy note 2 SGH-i317m that I rooted last year. I unrooted it completely last month so that I can acces to the Samsung update to 4.3. BUT when I try to update, it tells me that my device has been modified.
I can hear your questions comming so:
Yes I triangled away before unrooting,
Yes I tried wipe the partition cache
Yes I try rerooting then unrooting again
My device status is "modified" in the settings but "custom" in download mode
Yes I'm running everything stock
Yes I tried removing the sd card, in fact I don't even put an sd card in these days
Yes I tried every single tutorial I could possibly found...
Well, now I'm kinda stuck.
Thanks for the help!
Click to expand...
Click to collapse
What I did was:
- Root and use triangle away to Official/Official/No
- Flash your local ROM with latest Odin.
- Wipe to factory.
Now my phone is Device Status: Normal, and download mode is perfect
Not sure if anyone encountered this before, that android apps work perfectly fine while on wifi, but when switched over to 3G or LTE, the app will not be able to connect using the 3G/ LTE signal. When starting them, they give a message that no connection was found.
The few apps tested were:
Whatsapp
Chrome
Play Store (able to browse for apps using 3G, but fail to be able to downloaded)
If anyone has encountered this before and solved it, please advice! I'm severely handicapped without 3G while on the road.
So recently I had a Galaxy S3 whose charger port failed and I could no longer use the phone. So I had a replacement sent to me via my phone insurance company.
I stuck with TouchWiz for a few days since the phone was new, and everything worked just fine, camera, snapchat, chrome, you name it. I attempted to use the CMInstaller to remove Touchwiz and go to CM. However, during the installation process, everything appeared to be going smoothly, then the android with its chest open with the red triangle popped up briefly and the phone asked me to choose to root the phone. I hit yes, and the phone rebooted, at first with the CM logo, then it proceeded to boot into TouchWiz, with no sign of Cyanogen.
I did some research and found that this is because the replacement phone has Knox on it, preventing tampering. While I'm fine with TouchWiz for now until I can get a new phone in November, my phone has been acting a bit strange.
I can't download pictures from anywhere, whether its Chrome or Facebook or Twitter (where profile pictures won't even load). In Snapchat, I can only view pictures sent to me, but I can't view videos, I can't send pics or videos, and I can't load stories. Instagram closes when a video post pops up in my feed, but photos are fine. The Spider-Man game that I downloaded from the Play Store won't download the additional file that's needed to even start the game. My camera tells me to insert an SD card before using the camera, even though there is an SD card in the phone that I store music on for Poweramp (which works fine).
Other than these instances, the phone works fine. I'd just like to be able to use the apps I want. I did a factory reset from the settings menu to wipe stuff off the phone and see if that would get these apps to function correctly with no success.
Device info:
Model: SGH-I747
Android 4.4.2
Baseband: I747UCUFNE4
Kernel: 3.4.0-1514807
Build: KOT49H.I747UCUFNE4
I checked with Kies to see what it would do with the Firmware upgrade and initialization, since that was what the guide on here said to do. It's saying it will initialize my phone to 4.1.1 Baseband I747UCDDLK3, but downgrading will brick my phone, if I'm not mistaken.
So I don't know what to do now.
So my question is this: Can/Should I use Kies to attempt to restore my phone or did I permanently bork the hardware?
Try flashing the stock NE4 rom from enewman17s thread in development section. If im not mistaken it will have tge fix for external sd and the insecure kernel should solve the internal sd issues.
This is due to seLinux primarily, not knox. So its something we will have to deal with on every device running stock from now on. The alternative I believe is to format the card and factory reset. If you start everything fresh it should work ok when full stock.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
The problem I'm having with that idea is that I'm not sure I have root access, so I don't think I can flash a rom. If I can boot into recovery, I'll give it a try, but I'm not positive if it'll work.
Thanks for the tip!
You dont need to be rooted. Just need custom recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Try flashing the stock NE4 rom from enewman17s thread in development section. If im not mistaken it will have tge fix for external sd and the insecure kernel should solve the internal sd issues.
This is due to seLinux primarily, not knox. So its something we will have to deal with on every device running stock from now on. The alternative I believe is to format the card and factory reset. If you start everything fresh it should work ok when full stock.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi again,
I tried formatting and factory resetting. So I'm going to try the NE4 ROM, but I can't seem to find it. Would you mind pointing me in the right direction? Thanks for all your help!
This thread may help: http://forum.xda-developers.com/showthread.php?t=2789917
Okay, so I flashed that ROM from enewman's thread and it said it flashed successfully.
After it flashed, I went to do all three wipe options, and it rebooted in the middle of doing so. My phone rebooted normally into TouchWiz, and nothing was wiped and all my apps were still present.
I'm still having the same persistent problems as before. I think attempting another wipe may help, but I figured I'd check in with progress and see if anyone has any suggestions.
Thanks again.
Boot back into recovery and instead of factory resetting, choose Format /data.
This will wipe your internal sd card, just so you know. If that doesn't help, go back to the thread audit13 linked, reflash the rom, then the stock recovery. Reboot recovery and factory reset again. Then reboot and test. Pretty sure choosing format /data will be enough though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hey All!
I have this very interesting problem with my SGH-T989D.
I have for years been installing customs ROMs unto my phone. The last ROM I used was CM11 20141201 Sultan Hercules, with the provided GApps. This was installed using CWM 6.0.4.3. I ran this for months with no issues. Earlier this week, I decided I would try something else. I rebooted and went into CWM recovery and did a few things first. I went and Fixed permissions, and formatted various partitions, and also did a factory reset/wipe of the device. Now when I fixed permissions the time it took seemed odd too me. Like almost a minute, and since then I have been having install issues like crazy. So, I basically ended up using ODIN 1.85 to flash a stock ROM I had from T-Mobile. Which seemed to work fine. When i was satisfied the phone was functioning properly, I then proceeded to install CWM 6.0.4.3 using ODIN. It flashed successfully, and it rebooted my device. However, it brought me to the ODIN emergency download window. where it tells you to plug in your phone to the pc and use KIES to recover to the device. Ok, fine I thought to myself, I'll try that. Now KIES doesn't recognize my device. It's definitely not a driver issue because it used to work fine before these problems. I am assuming it has something to do with the firmware counter on my device. Since it says it's at 6 now, even though it's an official ROM. I have also tried using Lorains thread to re-partition the internal memory using the his unmodified PIT file. But Odin crashes at the SET PARTITION screen when trying to flash it So, honestly I'm at a dead end as to what's going on with my device at the moment. Even when I try to flash an early stock version of a Telus ROM, it just keeps going back to emerg ODIN screen, even though ODIN flashes successfully.
Does anyone have any suggestions for me? If you require more information I will do my best to answer.
Thanks a million in advance.
DrexxHaze said:
Hey All!
I have this very interesting problem with my SGH-T989D.
I have for years been installing customs ROMs unto my phone. The last ROM I used was CM11 20141201 Sultan Hercules, with the provided GApps. This was installed using CWM 6.0.4.3. I ran this for months with no issues. Earlier this week, I decided I would try something else. I rebooted and went into CWM recovery and did a few things first. I went and Fixed permissions, and formatted various partitions, and also did a factory reset/wipe of the device. Now when I fixed permissions the time it took seemed odd too me. Like almost a minute, and since then I have been having install issues like crazy. So, I basically ended up using ODIN 1.85 to flash a stock ROM I had from T-Mobile. Which seemed to work fine. When i was satisfied the phone was functioning properly, I then proceeded to install CWM 6.0.4.3 using ODIN. It flashed successfully, and it rebooted my device. However, it brought me to the ODIN emergency download window. where it tells you to plug in your phone to the pc and use KIES to recover to the device. Ok, fine I thought to myself, I'll try that. Now KIES doesn't recognize my device. It's definitely not a driver issue because it used to work fine before these problems. I am assuming it has something to do with the firmware counter on my device. Since it says it's at 6 now, even though it's an official ROM. I have also tried using Lorains thread to re-partition the internal memory using the his unmodified PIT file. But Odin crashes at the SET PARTITION screen when trying to flash it So, honestly I'm at a dead end as to what's going on with my device at the moment. Even when I try to flash an early stock version of a Telus ROM, it just keeps going back to emerg ODIN screen, even though ODIN flashes successfully.
Does anyone have any suggestions for me? If you require more information I will do my best to answer.
Thanks a million in advance.
Click to expand...
Click to collapse
I think you might have to re-partition your phone. Sultan's ROMs partition your phone a certain way and there is a fix for your phone somewhere on here to allow you to install regular types of custom roms.
I'll try this again (this website crashed when first posting this)
Leased phone (January 2017) use for my business. Has had (3) OTA updates since April. Started having issues after 3rd update mid-June (freezes / reboots). Most times have to pull the battery to get it to boot. Have wiped & restore several times, from Settings and Recovery boot menu. Cleared App cache and partition cache. Had the local Sprint Store 'supposedly' flash the OS from a PC but nothing improved. Described these issues below but was only met with a blank stare and an offer to open my wallet to replace with a refurbished phone without knowing what is causing the issue.
On some occasions when the device is not responding it heats up. Messages of Apps that stop responding include System UI, Package Access Helper, Touchwiz and Gmail, among others.
When going to Boot recovery menu to try clearing the partition cache the Android Icon shows up with the message 'Installing system update', which it's clearly not doing. Sometimes that's followed by the icon laying down and the message 'No command'. Does this mean the update didn't properly install? Another message I've noticed once the menu comes up is 'dm-verity verification failed . . . '
Further trying to diagnose, Sprint Zone / Device Diagnostics / Flagged / System Updates - always states 'Update now', but Settings / System Update / Software update message reads 'The latest updates have already been installed (N910PVPS4DPE2 / N910PSPT4DPE2 / N910PVPS4DPE2).
Investigated alternatives with Samsung (they replied the same day, Sprint Community message July 20th still hasn't replied) I can take it to a service center to have the hardware checked for a fee but it is not nearby and I'd like to first understand what the issue is.
From what I've described does anyone know what could be causing these issues? I have read where some updates were causing problems but I've tried most of those remedies and nothing has helped yet. Perhaps the Sprint Store, in an effort to extract more money (this is how it seemed) did not or was not able to flash the OS?
Any help would be greatly appreciated.
best thing to do is odin back to an older version and retake the update if you wanna go thru that again
but id recommend reverting back to OG5 and then flashing a rom you will have less reboots....as least on my end i did
JLFitzpatrick said:
...When going to Boot recovery menu to try clearing the partition cache the Android Icon shows up with the message 'Installing system update', which it's clearly not doing. Sometimes that's followed by the icon laying down and the message 'No command'. Does this mean the update didn't properly install? Another message I've noticed once the menu comes up is 'dm-verity verification failed . . . '...
Click to expand...
Click to collapse
The stock recovery you describe, it's normal for the Android guy to fall down and display the red x or whatever you saw when there's no update to apply but the dm-verity failure isn't normal. It could indicate bad repair or maybe it was rooted at some point? Wiping and Odin flash doesn't always rid the phone of that but Knox trip remains always until Samsung repairs a rooted phone. Dunno the cause of your dm-verity failure but maybe, if it was stock un-rooted all along, it may a read only partition failed or corrupted?
As suggested above, you may fix the dm-verity by taking a couple of OTA updates after Odin flashing an older one. Don't go back any older than OG5 though.
I think the problem may also stem from old data from Lollipop not getting wiped. I'd recommend disabling the reactivation lock on Settings/Security, remove your accounts from phone, a factory reset within Settings, boot to recovery and factory reset and wipe dalvik and cache in stock recovery and power off. Reboot to download mode and flash an older stock tar and let it OTA a couple of times.
That may solve some issues but it could be hardware failure or a corrupt partition. If the dm-verity goes away, see if your problems are resolved. If you didn't root and have a warranty, make whoever warrants it replace it; the failure is legit.
Sprint Zone and ItsOn is garbage IMO. Bloat that kills the experience that Samsung intended. Albeit, Samsung isn't so innocent with bloat ruining the experience either. Just my opinion on the bloat. By the time users add their own bloat, there's but enough RAM and with all the services running, battery takes a hit and phone lags. Run package disabler (search in Google Play) or root to manage it is what I'd suggest. FWIW, I have no random reboots or phone heating up while in standby running Marshmallow. My phone sleeps like a baby.
If no warranty applies and root is an option, you could try rooting with Chainfire Auto Root for Note 4 and then full un-root. The developer removes the dm-verity flag if it's there for modified read only partition reasons. But of coarse that also trips Knox warranty bit, so be aware. Dm-verity can prevent OTA's from updating but that's an alternative with root and Knox trip risks. No warranty should mean less risk unless the phone belongs to your employer.
Sent from my SM-N910P using Tapatalk
Thank you for your replies.
I had pointed out the 'dm-verity verification failure' text to the goof-offs at the Sprint Store, you'd think I was speaking in a foreign tongue. Phone is leased on our personal family plan and used for my business. I've never rooted it myself, not sure what the Sprint people did at the store but that text was there before they supposedly flashed the OS.
I apologize but am in over my head with the suggested repairs. Although having upgraded PC's am familiar with the process; revert to previous clean OS and upgrade over that. I'll take your suggestions and just have to study a little more to understand the correct procedure.
Yesterday afternoon I tried the folks at Samsung again since their support team had replied the same day before (still waiting for a support response from Sprint since July 20th) and went to a live support chat. The woman was very helpful but unfortunately, I had to jump off for a meeting. Before I jumped off she had me put the phone into Safe Mode. I had tried to get there before but the instructions I was given were incorrect (not found in recovery boot). It has since been in that mode and has been much more stable, still freezes occasionally but doesn't reboot itself and runs zippy as hell except for momentary freezes. I have the Chat ID # and will try again today to see what they can do before trying other suggestions. I gave them the HEX DEC numbers and it sounded like they could access the phone with those, this morning their Chat was full so I'll have to try later.
samep, if you don't mind can you give me some clarification on your suggestion:
"I think the problem may also stem from old data from Lollipop not getting wiped. I'd recommend disabling the reactivation lock on Settings/Security, remove your accounts from phone, a factory reset within Settings, boot to recovery and factory reset and wipe dalvik and cache in stock recovery and power off. Reboot to download mode and flash an older stock tar and let it OTA a couple of times."
My interpretation:
Settings / Security / disable reactivation lock
Remove accounts (first back up phone log & sms to samsung account, back up wifi passwords to google account)
Settings / Backup and reset / Factory data reset
Boot to recovery menu / factory reset again (partition and dalvik cache evidently get cleared through reset)
Boot to recovery menu / 'flash an older tar' ? (Is this 'Apply update from ADB (Odin)' or SD card? This is where things get fuzzy. Can I load the stock tar (OS?) to a formatted sd card and apply the update from there or do I have to install Odin on a PC? Where is the best place to get a 'stock tar' (or Odin) from and which version(s) should I use for a Note 4, or is that explained on a particular website. There are many sources of information on Odin and firmware but I'm not sure which to trust if I need to do this would prefer to do this just once.)
Thank you again for your help, and I apologize for my ignorance on this subject.
But the best thing about ignorance is that it can be overcome with a little effort and knowledge.
To answer the question, boot into download mode from powered down state by holding volume down, menu and power. Yes, you use Odin installed on PC for that. But first you need the Samsung USB driver and Odin installed, plus the stock tar.
This thread will get you going with resources and brief instructions.
http://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
I'd suggest PC1 stock tar, then let it OTA.
(Your interpretation was mostly right up to the question about how to flash the tar after the factory reset and power down.)
Sent from my SM-N910P using Tapatalk
Thank you samep,
Understanding the tar file versions are listed alpha-numeric the oldest version is PD1 so I will start with that version.
Have downloaded Odin and all three tar files (in case of any issues with PD1). Samsung Chat referred me to bring the phone in, after reviewing information on using Odin will try your suggested method first and then check for dm-verity failure.
Another tar file resource found is updato-dot-com (as a newbie unable to post link):
JLFitzpatrick said:
Thank you samep,
Understanding the tar file versions are listed alpha-numeric the oldest version is PD1 so I will start with that version.
Have downloaded Odin and all three tar files (in case of any issues with PD1). Samsung Chat referred me to bring the phone in, after reviewing information on using Odin will try your suggested method first and then check for dm-verity failure.
Another tar file resource found is updato-dot-com (as a newbie unable to post link):
Click to expand...
Click to collapse
If you're feeling overwhelmed, you could bring it in. There's a chance it is hardware and the steps may prove redundant.
Up to you. At least you have something to point to as an issue.
Sent from my SM-N910P using Tapatalk
So I've gone through all the steps, phone is wiped, reinstalled Samsung USB Driver, have Odin open as Administrator and the phone in 'Android Recovery', Phone does not show up in Odin.
Have seen a couple versions of setting a connection (Odin open first, phone connected first); tried all of those and tried Odin open not as administrator. There is no connection. Tried other instructions to put into Developer Mode and enable USB bugging. Nothing, disabled USB bugging and booted back to recovery. Still nothing.
In Recovery mode it does not state 'Odin mode'. Tried the Recovery menu option 'Apply update from ADB' message reads 'Update from external storage diabled'. Tried 'Reboot to bootloader' (WTH), that does show Odin Mode at top of screen but phone still does not show up in Odin on PC. Then have to pull battery to reboot to Recovery mode. What steps am I missing here?
When phone is booted up normally it connects to PC without issue.
Finally got Odin to recognize the phone. Through a few searches I tried one remedy that suggested manually updating the samsung usb drivers in device manager which did the trick. Realized earlier that from recovery mode you do need to select boot to bootloader to get into Odin mode (listed on top).
Installed 6.0.1 - PD1 currently phone is installing OTA updates, hopefully this does the trick. Thanks again for your help.
On Tuesday the phone updated OTA from PD1 (April 27, 2016) installed via Odin to PE1 (June 1, 2016) then PE2 (June 29, 2016). Recovery Mode screen no longer shows dm-verity failure message so that's fixed. Phone is mostly stable, however still not as stable as it was on PE1 from what I recall by the release dates. Phone still freezes although it usually does not crash if I leave it alone but still does crash at least once a day. Safe Mode does not help, as the worst culprits are system Apps (Gmail, Drive are the worst).
It seldom overheats now but did yesterday. 3rd Party CPU cooler found Package Access Helper, Context Service and System UI as causing an issue. Cleared App Cache for all three but problems persist. Clearing App Cache in Settings / Storage takes at least three tries to clear all but 4.00 KB. I have been clearing Partition Cache every morning just to get through most of the day otherwise it will freeze when I first start to use it. Battery is also draining faster than before.
Any suggestions? OTA updates were at work on a stable WiFi signal. I'm thinking of Odin flashing back to PE1 (or PD1) and stopping further OTA updates. Anybody tried this? Will be traveling for a couple of weeks and need a stable phone, like I used to have. Thank you.
Samsung has been having memory management issues. IMO, this is the reason they keep increasing RAM in recent phones and getting help from Google. But 3 gigs of RAM should be sufficient.
A custom ROM may resolve that but you could try a package disabler from Google Play to freeze some unneeded bloat.
I couldn't say which stock version is best because I've ran all of them without random reboots and lag is minimum. The custom ROMs have been daily driver stable for me. I use them when traveling too.
Sending PM to OP as well with additional info.
Sent from my SM-N910P using Tapatalk