Hello.
I have a Galaxy Note 4 SM-N910T2. In january of this year i upgraded it to 6.0.1 (N910TUVU2EQI2) from 4.4.4(N910T2UVU2AOG1) using the SM-N910T firmware for the upgrade, everything was working perfectly but the day before yesterday i wanted to perform a wipe cache because the phone was being a bit laggy. after the wipe cache was perform and i hit the reboot, the recovery got stucked on Verifying DMhash tree. so after 30 minutes i took the battery out and powered on my phone, the problem is: The phone started to freeze, reset it self even the process system crashed. I read that downloading the Wake Lock power management helps and it did but i didn't want to use this app forever so i downgraded back to 4.4.4 it's original firmware, it does run better but now my phone reboots itself and it freezes just a little bit. Also i've got the Process system is not responding do you want to close it?
Things i've done so far:
1- Reflashed 4.4.4, 3 times, i've done wipes before reflashing and after. Nothing
2-Flashed TWRP wiped everything, repaired the file system, Flashed the stock again (4.4.4) nothing.
I'm not going back to 6.0.1.
Do i have to buy a new phone or maybe a new rom with a kernel will help ?
Pigoath said:
Hello.
I have a Galaxy Note 4 SM-N910T2. In january of this year i upgraded it to 6.0.1 (N910TUVU2EQI2) from 4.4.4(N910T2UVU2AOG1) using the SM-N910T firmware for the upgrade, everything was working perfectly but the day before yesterday i wanted to perform a wipe cache because the phone was being a bit laggy. after the wipe cache was perform and i hit the reboot, the recovery got stucked on Verifying DMhash tree. so after 30 minutes i took the battery out and powered on my phone, the problem is: The phone started to freeze, reset it self even the process system crashed. I read that downloading the Wake Lock power management helps and it did but i didn't want to use this app forever so i downgraded back to 4.4.4 it's original firmware, it does run better but now my phone reboots itself and it freezes just a little bit. Also i've got the Process system is not responding do you want to close it?
Things i've done so far:
1- Reflashed 4.4.4, 3 times, i've done wipes before reflashing and after. Nothing
2-Flashed TWRP wiped everything, repaired the file system, Flashed the stock again (4.4.4) nothing.
I'm not going back to 6.0.1.
Do i have to buy a new phone or maybe a new rom with a kernel will help ?
Click to expand...
Click to collapse
All i can say is your phone mmc chip is about to die soon or later you will get mmc_read failure message and your phone wont be able to boot into the system and you won'tbe able to flash anything.
My best suggestion is sell it ASAP.
Trex888 said:
All i can say is your phone mmc chip is about to die soon or later you will get mmc_read failure message and your phone wont be able to boot into the system and you won'tbe able to flash anything.
My best suggestion is sell it ASAP.
Click to expand...
Click to collapse
I came across the mmc_read failure before I realized it was happening and have been researching ways to at least verify there was nothing important on the device before retiring it to Samsung heaven.
Instead of useful advice, everyone seems to be spouting "sell it ASAP" as though it doesn't make you trash as a person to attempt selling it as any sort of working device. The inclusion of "ASAP" and lack of "with a disclaimer" tends to suggest they aren't recommending you actually tell anyone about the issue.
Good advice would be to back up everything you can now and begin looking for a new device. You could attempt to sell it for parts, but make sure to inform people of the situation. If it is that close to failure, chances are it will still be well within the 30 day return policy on most sites and they always favor the buyer. Your device is already ruined, but there is no reason to destroy your reputation with it.
Related
Weirdest thing happens, I'll boot my DS7 and it's like if I just did a factory reset...every time. I'll customize my homescreens/gmail and what not, and do a normal reboot and it does a factory reset every time. I've read a few threads about similar topics and no one seems to know what's going on.
I've wiped data/cache/dalvik and fixed permissions, doesn't help. Re-install ROM, doesn't help.
I tried reflashing superuser.zip says installation aborted (bad). Same when I try to flash HC (yes, I'm still on Froyo).
Any clues ladies and genitals? Any help would be appreciated.
Sounds like you are experiencing the READ-ONLY bug that plagues this device. Hopefully it is still under warranty so that you can send it to Dell. Last summer I sent my Streak 7 to Dell. They repaired the read-only bug and had it back to my house in about 2 weeks.
Basically, what happens when your tablet goes into read-only mode... any updates, installs, customizing you do will be lost upon a reset... even though it appears like things are updating, they simply are not saved to the internal flash drive. Also, when it gets really bad some of the apps (along with the web browser) will start to get fatal errors.
That sounds about right, especially since even when I try to move a file from my netbook to the device (such as a new ROM to try to flash in CWM) it wont show up after I reboot either.
Don't think its under warranty anymore, dang.
Yes this is what happened to the one I got off Craigslist too the person I bought it from also changed his phone number instantly, so I got screwed but I'm in the process of getting a replacement or getting an extended warranty on it.
Sent from my Galaxy Nexus using XDA App
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
arvichan said:
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
Click to expand...
Click to collapse
Be in safe kernel if your on ics. You could check your device of the bug by downloading eMMC check in google play. Dont put your fate in that if your on stock ics rom not rooted you will not get the bug, be on the safe side.
arvichan said:
OK, here is my story with my Galaxy Note brick. Though I never tried custom ROMs after upgrading to ICS but rooted with temp CWM & superSU. All seem to be working ok. One fine day I did a factory reset, booting failed, Stock ROM with PC ODIN stuck at FACTORYFS. Then comes XDA with a solution to use a patched PIT file.
Vola, my phone was up and running with ICS but missing 3GB space. It wouldn't have bothered me had the phone been stable. It used to freeze 2-3 times a day especially while downloading from Google play. Digging further in XDA forums for a fix cleared about eMMC bug and and no way returning back to normal So I ran to SSC with a factory reset phone hoping they will replace mobo, as it failed to boot and stuck at Samsung logo. Told them that Kies update to ICS 4.0.4 caused the problem. But couple of hours later, I got my phone back but with 8.24GB space & ICS 4.0.4
Now, I needed a fool proof way of bricking but couldn't go for pulling out battery half way through stock flash ROM. Thought it would be tricky to explain what I was upgrading when I've already got the latest stock ROM just a day ago from SSC. hmmm... then I got hold of stock PIT file... flashed it. And now perfectly stuck at home screen. No recovery menu but only download mode.
Next visit to SSC within 24hours and a simple story line with a sad face.... "Installed many apps, caused force close. So I did a Factory reset. And the phone does not boot now". It was stuck on the very first screen.
Finally it is gone for mobo replacement and expected to be ready in 2 days - covered under warranty Now coming to my question part, "What are the quick essentials checks to be done before accepting my phone from SSC" I really wish that it is all fixed properly and I do not want to visit a service center again
Click to expand...
Click to collapse
Just check the service job sheet whether they replaced the mobo or not before taking the delivery ? As simple As that.
got my gnote back with new mobo
Well, it is almost like the 'law of attraction'... I didn't want any problem and when I got my gnote today... guess what ? phone vibration didn't work. I had to go back to the SSC.
Fortunately, they responded immediately and the SSC guy fixed it on the spot without another round of formal servicing process. As explained to me, an insulation sticker of the vibrator was not removed while slipping in the new mobo. I didn't care less to understand if that is true as I was excited to get my phone with 11GB internal storage .
All seem to be working fine as of now with stock ICS 4.0.4 :good:
Hey folks, first thread ever, I really need help with this troubled N910T, DOK2, Android 5.1.1
Whats wrong with this phone:
The contact app will stop everytime I open it, since contact app is combined into Phone app, so the Phone app will also stop everytime I click on it. However, the situation will be fixed if I change the locale to English. (The phone belongs to a Asian friend)
One of the instant message app, the Wechat, similar to Whatsapp Messager and Facebook Messager, will not receive any kind of notification, at all.
The phone's battery drop from 50% to 1% then turn off itself in minutes.
The last two problems may be unrelated issues to the first one, and that is not the main reason I'm really here. I have ODIN flashed the latest firmware over 10 times and all THREE of the problems still exist after all that.
And whats bothering me is that ODIN flash firmware WILL NOT FACTORY RESET this phone, that doesn't make any sense to me. Please let me know if I make a mistake about that, because every other phone or tablet I have worked on before will always be factory reset after flashing a OEM firmware.
I have also flahed TWRP and wiped everything from the System to the internal storage and reflash the firmware but the problem is still there.
sort of things have been done to the phone may have something to do with the problems:
installed the zips I got from this thread http://forum.xda-developers.com/not...pt-touchwiz-bloating-script-222-apps-t3258537
it debloated the phone.
the phone was lost in a rainy day, found again two days later. Remote lock and wipe preformed via Android Device Manager but the wipe process never go through.
Please let me know if the phone is worth saving at all, I have spent days in this phone fixing and researching for solution. I found no similar issue around here, and the phone is out of warranty.
Thank you and please let me know should I throw this thing away.
Battery needs to be replaced. Are you sure you flashed right firmware for 910t not 910t3?
darekz said:
Battery needs to be replaced. Are you sure you flashed right firmware for 910t not 910t3?
Click to expand...
Click to collapse
It's a N910T, and the ODIN sucessfully passed everytime but will not factory reset the phone,.
Have you tried going into recovery and factory reset it yourself
tat2messiah said:
Have you tried going into recovery and factory reset it yourself
Click to expand...
Click to collapse
Many times already.
If you haven't done so, you may want to do a clean install which means wiping system, data, dalvik and cache at least three times in custom recovery such as TWRP. Then you can try ODIN baseband, bootloader, rom and kernel (if rom doesn't contain one), custom recovery. Next you boot into customer recovery again and do a factory reset and that should do it. Let me know if that helps.
raynaran said:
Hey folks, first thread ever, I really need help with this troubled N910T, DOK2, Android 5.1.1
Whats wrong with this phone:
The contact app will stop everytime I open it, since contact app is combined into Phone app, so the Phone app will also stop everytime I click on it. However, the situation will be fixed if I change the locale to English. (The phone belongs to a Asian friend)
One of the instant message app, the Wechat, similar to Whatsapp Messager and Facebook Messager, will not receive any kind of notification, at all.
The phone's battery drop from 50% to 1% then turn off itself in minutes.
The last two problems may be unrelated issues to the first one, and that is not the main reason I'm really here. I have ODIN flashed the latest firmware over 10 times and all THREE of the problems still exist after all that.
And whats bothering me is that ODIN flash firmware WILL NOT FACTORY RESET this phone, that doesn't make any sense to me. Please let me know if I make a mistake about that, because every other phone or tablet I have worked on before will always be factory reset after flashing a OEM firmware.
I have also flahed TWRP and wiped everything from the System to the internal storage and reflash the firmware but the problem is still there.
sort of things have been done to the phone may have something to do with the problems:
installed the zips I got from this thread http://forum.xda-developers.com/not...pt-touchwiz-bloating-script-222-apps-t3258537
it debloated the phone.
the phone was lost in a rainy day, found again two days later. Remote lock and wipe preformed via Android Device Manager but the wipe process never go through.
Please let me know if the phone is worth saving at all, I have spent days in this phone fixing and researching for solution. I found no similar issue around here, and the phone is out of warranty.
Thank you and please let me know should I throw this thing away.
Click to expand...
Click to collapse
I don't see EQC1 on sammobile, anyone else see the 127 MB update?
I'm on EQB1.
Yup, I see it, 127.53mb on both of mine SM-N910T3 and
SM-N910T
I have it as well. Have you flashed yet?
I have it too. I'm not sure I want to flash, especially if it patches the ability to root my phone.
My phone also suffers from the SD card / reboot issue (the phone constantly boot loops when both an SD card and SIM card are in the phone). I wonder if this update will fix that?
I tried flashing it and it failed, I'm running a stock highly modified rom. I'll try reflashing the original stock unmodified rom when I get a chance tomorrow and apply the update. It looks like it's just security updates
Says "Various system improvements" for the QC1 update.
https://support.t-mobile.com/docs/DOC-28899
I updated to this version the other day, now I'm looking to root. Anyone know if the old root method still works? I may try myself in the next few days myself and find out.
I upgraded to it yesterday. Took about 30 minutes from start of install to finish. It updates the security to March 2017, has the new Google Play Store. Other than that I do not notice any other differences
Can i root after upgrade?
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
febzz88 said:
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
Click to expand...
Click to collapse
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
d0ug said:
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
Click to expand...
Click to collapse
Hi,
That's certainly is one possible scenario (hardware failing). But based on my extensive research too, many have said that this could be faulty firmware. I went to a Samsung Experience Center and talked with a guy there and he said that it's a known issue affecting many Galaxy Note 4 Sprint users a few months ago. Samsung in the end replaced/repaired the affected units free of charge.
In the past 2 months or so, more and more Galaxy Note 4 users started experiencing this issue. And so it could be that the firmware triggered the issue, and eventually damaged the hardware.
Since we don't really have a 100% certain answer (of course, Samsung will never tell us), I'm just trying to see if anyone has updated the phone to the latest firmware and could tell us if it fixed the issue.
Soooo..... Is this rootable or not?
sino8r said:
Soooo..... Is this rootable or not?
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/no...rom-n910t3uvu3eqc1-stock-rooted-odex-t3592242
I can't seem to get TWRP to work on this. I've tried several times with Odin, it appears to be successful, phone reboots, but then when I try to reboot into recovery there's no TWRP, only stock. Anyone else have this issue or any suggestions?
Edit: Tried something I remembered reading in another thread. I pulled the battery immediately after Odin successfully finished and the booted directly into recovery. It worked. I'm flashing pvsgh's rooted EQC1 and will report back if TWRP sticks
Edit 2: Success. Seems like pulling the battery after Odin/TWRP before the phone reboots did the trick
ok, thanks for the suggestion.
Anybody have a link for the firmware?
thecrunked said:
Anybody have a link for the firmware?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...firmware-galaxy-note-4-n910tuvs2eqb1-t3569911
Can I autoroot with EQC1?
I tried auto root and got
RECORVERY IS NOT SEANDROID ENFORCING,
AM I screwed? I assume there's some way to get back to EQC1 and boot the phone. There has to be. But could I do it and keep the data. I was trying to get deleted photos back.
I have a stock AT&T G6, got it when the phone first came out, and I haven't touched the firmware. Update after update, no problems.
Finally this morning my phone had enough - I performed a system update. However during the reboot, the phone froze for 30 minutes on the AT&T logo. Nothing changed.
Reset phone, nothing changed, 15 minutes no change. Reset phone to recovery mode - wipe cache - reset phone. Same thing - stuck at AT&T logo.
Finally I had enough - I did a full Factory reset. AT LAST! After 8 painful minutes stuck at the AT&T logo, my phone came to life and welcomed me to my new phone (FML).
So here I am with a freshly loaded copy of my new Nougat 7.0 software on my AT&T Build ( NRD90M.G920AUCS6EQF1 ) and I am desperately trying to run every possible data recovery option possible.
I WANT to recover my photos and SMS messages before I start using my phone. But I can't - every app I've run shows no results. Everything I'm seeing shows I need to root this phone to make it work.
Unfortunately I have no clue htf to do that. Every instruction I find online does not include my build version. My phone is turned off and not used until I recover this data. I would appreciate any help I can get in recovering this data!
Cassetti said:
I have a stock AT&T G6, got it when the phone first came out, and I haven't touched the firmware. Update after update, no problems.
Finally this morning my phone had enough - I performed a system update. However during the reboot, the phone froze for 30 minutes on the AT&T logo. Nothing changed.
Reset phone, nothing changed, 15 minutes no change. Reset phone to recovery mode - wipe cache - reset phone. Same thing - stuck at AT&T logo.
Finally I had enough - I did a full Factory reset. AT LAST! After 8 painful minutes stuck at the AT&T logo, my phone came to life and welcomed me to my new phone (FML).
So here I am with a freshly loaded copy of my new Nougat 7.0 software on my AT&T Build ( NRD90M.G920AUCS6EQF1 ) and I am desperately trying to run every possible data recovery option possible.
I WANT to recover my photos and SMS messages before I start using my phone. But I can't - every app I've run shows no results. Everything I'm seeing shows I need to root this phone to make it work.
Unfortunately I have no clue htf to do that. Every instruction I find online does not include my build version. My phone is turned off and not used until I recover this data. I would appreciate any help I can get in recovering this data!
Click to expand...
Click to collapse
No known root for current builds to my knowledge. Don't know if anyone is still picking away at it, but I wouldn't hold my breath. Development on this device has been almost silent for many months.
dandrumheller said:
No known root for current builds to my knowledge. Don't know if anyone is still picking away at it, but I wouldn't hold my breath. Development on this device has been almost silent for many months.
Click to expand...
Click to collapse
Pretty much what I've figured. Sounds like I'll just have accept they're lost and move on. Thx