Database Develop

[Q] Galaxy S stuck in boot-loop

Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?

What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.

Just use odin 1.3 reflash official rom , everything would be OK.

Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.

mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.

porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?

You mean the external sdcard? Maybe try to format it...

OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...

Galaxy Tab P100-cant delete prior owner info

Ive searched and havent been able to find a solution to this, although Ive seen it asked before.
Galaxy Tab P100 bought from a pawn shop. It still has the prior owners (unknown) gmail info minus p/w. I cannot remove the account, or access market because of this. Everytime I tried to data reset (both via Privacy settings and also CWM), add a new rom, or add apps - after I reboot it goes back to the prior owner settings and apks.
I have Odin'd/Heimdall with different roms but they dont stick. Different kernels install though. Ive added two different CWMs. Superuser breaks after every reset - I gain, then lose, root. Ive rooted/added root explorer and deleted accounts.db and user.db - they go back after. Ive spoken with Sprint and we tried everything they had, as well as a ##786# and MSL number (resetting phone activation I think?). Their response was take it in to send back. I want to fix it myself.
It seems to me that this prior info is overriding and reinstalling every reboot, preventing any new flashing/etc from taking place.
Here is my question. I took it apart this morning and disconnected the battery (thinking maybe it will wipe any memory). But does it have a CMOS-type battery? I noticed there is a small round battery-looking connection soldered into the mainboard (see here - step 7/8 http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/1)
Does anyone know what this is? I dont really have anything to lose, but Im not great with a soldering iron, but will try. Im thinking this might be for the memory, and disconnecting/reconnecting this would erase any permanent user information, freeing it up for me to add mine.
Or if anyone has any new ideas I would appreciate it.
Thanks for the time. Ed
Sent from my rooted/rom'd PG86100 using XDA Premium App

It is not a battery backed memory, it is a NAND chip.
Sounds like the chip gone bad.
Sent from my GT-P1000 using XDA

Just an update.
I did not do anything with the round battery thing, as priyana stated the memory is stored on a nand chip. I put the tab back together.
I rooted again, and found the ea24 firmware and loaded it via odin. It took, but the prior user info was still there, and everything (I mean a crapload of apps) began force closing. I did confirm that ea24 was on it. I then flashed back to ef17.
I contacted Sprint repair store again, and they told me that they probably cant fix it, and its something they have to send back. They said that I have done all that they would do in-store.
I dont understand what could be wrong, as I found the prior owner and spoke with her. She had no issues with it. It worked fine prior to her getting rid of it. And it works fine, I just cant get rid of any prior info. I googled it and it seems like there are people out there who have the same problem, but no one has an answer, including sprint or samsung.
So much for my venting. Ill keep trying to find an answer.

roninep said:
I have Odin'd/Heimdall with different roms but they dont stick. Different kernels install though. Ive added two different CWMs. Superuser breaks after every reset - I gain, then lose, root.
Click to expand...
Click to collapse
First of all, I'd like to apologize for posting something that won't really help, but I recognize this from somewhere else. On some devices, there's some kind of file (that you can delete via the adb prompt when you're root) that on every bootup checks to see if the installed ROM matches stock, and if not, restores to stock. This sounds exactly what you're experiencing when you mention that no ROMs "stick".
I think you should try to look into if there's some files that need to be erased in order for a ROM to be cleanly installed that you haven't gotten rid of. It might also be some kind of feature that the previous user enabled, so maybe it's somewhere around in the settings that you can disable it, who knows.
It definitely does not sound like a memory issue because I don't see how a memory issue could make the stock ROM suddenly appear again after you've installed a custom ROM through CWM (assuming CWM gives no errors or anything and the custom ROM has actually been wiped).
Maybe you can do a more thorough wipe of the device memory manually with some guidance from someone who knows more about how these tablets work :fingers-crossed:

I agree with you about some type of file and bootup. Thats why I went with maybe it being a cmos/nand issue. I couldnt understand that I wiped everything, and information was still coming back. It makes me think that somewhere, something is being stored separate from the main drive.
Ive used the factory restore, CWM (2 different versions - 3 and 5 I believe), and wiped data (factory reset), cache and Davlik three times each before I flashed the CM ROMs. And I have not had any errors or problems installing any of the CWMs.
I spoke with the previous user, and she did nothing above turning it on/off, and using it. I am not on the Sprint network with it, and the wi-fi doesnt turn on until I set it up, so I cant see it being something that contacts Sprint and OTAs from them.
Can anyone tell me if, using ADB, there is a more thorough wipe I can perform ? More than the normal one done through CWM or Android factory restore?
Something similar to the reformatting of a hard drive?
Thanks
Ed

I have the same problem. Did you find any solution?
I believe the previous owner info is stored on sprint servers. When you reboot, it downloads all the crap.
The long time required to reboot explains the slow transfer of data - wireless.
These wireless service providers are pretty sneaky.
Thanks

Hi,
Have you tried formatting both internal and external Sd via Windows? (connecting via USB)
You can also try CM10, it has a different memory map which will write your device completely.
Regards
Sent from my GT-P1000 using Tapatalk 2

I have this same problem with a tab. Its not connected to sprint,has not been on the internet at all. Was there ever a fix for this?? Please let me know its a christmas present and i need to fix this issue. Thank you

Fingerprint sensor error ?

Hi I'm trying to set up my lock screen whit finger print but no matter homw many time i try i keep getting an error has occurred whit the fingerprint sensor if this messages appears repeatedly restart you phone i restarted the phone multiple times and same problem tried diffrent roms same problem any one else has this problem ?

COCODRILO45 said:
Hi I'm trying to set up my lock screen whit finger print but no matter homw many time i try i keep getting an error has occurred whit the fingerprint sensor if this messages appears repeatedly restart you phone i restarted the phone multiple times and same problem tried diffrent roms same problem any one else has this problem ?
Click to expand...
Click to collapse
Interesting, this happened to me as well yesterday along with some incredible lag with keyboard and scrolling pages. Like the phone is doing something, ive Odin flashed stock fw 4 times with full wipes. seems something just suddenly defected my phone..
EDIT: BTW this happened after trying to flash a custom rom to my phone, phone was running great when i got it.

i got it working i had to flash back to stock via odin that's the only way it works for me as soon as i flash a custom rom it will stop working if you figure out how to get it working whit a custom rom let me now pls

COCODRILO45 said:
i got it working i had to flash back to stock via odin that's the only way it works for me as soon as i flash a custom rom it will stop working if you figure out how to get it working whit a custom rom let me now pls
Click to expand...
Click to collapse
Really? flashing back to stock worked for you? hmm wonder if my stock fw from sammy is damaged, but usually if it was it wouldn't flash via Odin it fail.

yea that worked for me im about to flash it back to stock again i just cant get it to work on any rom I keep getting that error i guess ill go stock rooted for now

COCODRILO45 said:
yea that worked for me im about to flash it back to stock again i just cant get it to work on any rom I keep getting that error i guess ill go stock rooted for now
Click to expand...
Click to collapse
Now when you got that fingerprint error, did you experience and hard core lag in scrolling or in the keyboard? like every 3 seconds it pause like it's doing something?

not really im using nova launcher and for keyboard swiftkey running preety smooth im on firekat rom

Having the same issue with Hyperdrive. Restore my stock rooted backup and it works fine. Really looking forward to an answer on this one.

Must setup first time before rooting and flashing roms. This has been discussed in other threads.

Did that, still didn't work.

Diablohtr said:
Having the same issue with Hyperdrive. Restore my stock rooted backup and it works fine. Really looking forward to an answer on this one.
Click to expand...
Click to collapse
Is it just Hyperdrive or have you tried one of the other ROMs? I am Dynamic Kat and do not have the issue although other people do, ones that did not setup before flashing that ROM.

keitht said:
Is it just Hyperdrive or have you tried one of the other ROMs? I am Dynamic Kat and do not have the issue although other people do, ones that did not setup before flashing that ROM.
Click to expand...
Click to collapse
Haven't tried any others yet. Going to wait it out a few days and hopefully we will have a solution.

COCODRILO45 said:
Hi I'm trying to set up my lock screen whit finger print but no matter homw many time i try i keep getting an error has occurred whit the fingerprint sensor if this messages appears repeatedly restart you phone i restarted the phone multiple times and same problem tried diffrent roms same problem any one else has this problem ?
Click to expand...
Click to collapse
I have your same problem but even worse, not going to solve it stock still gives the same result I am losing faith

CapitanFantasma said:
I have your same problem but even worse, not going to solve it stock still gives the same result I am losing faith
Click to expand...
Click to collapse
I tried using odin, I was on NIH firmware with no luck... and then flashed odin with NJ7 with no luck from that, I must of flashed the firmwares over 8 times,
I went and replaced my white note 4 at a corporate near me, with a black note 4.. no one had them in stock, dialing 611 was no help, they said since u bought it at a store, I had to go there, I found a corp store that had 2 left, I rushed over cause they don't hold it for anyone. employee wanted to charge a $50 restocking fee, I told them the phone is defective, and the manager override the sale..

I am having the same problem of the fingerprint scanner not working after flashing a custom ROM. I followed everything to a T & it didn't install (& yes, it is for my N4). I went back to stock using Odin, several times & have not resolved it yet. I do not want to take it back but I do like having the fingerprint scanner. Luckily, I have another N4 cause I bought 2 when they came out cause I planned on trying to turn a profit on 1 of them, but I'll be damned if everybody didn't make it easy as hell for anyone to get one. I guess I can use the 1 that doesn't work right for flashing & playing around on & then when I find "THE" ROM that I'm happiest with, I can flash it on the good 1. IDK. This is BS though. Somebody has to know how to get it back working right. I know that people that helped create this phablet, are members of this site, so I hope that they or someone else that has fixed this problem replies to our question. I flashed this ROM... http://forum.xda-developers.com/note-4-sprint/development/rom-alpha-semper-fi-t2926682 & the fingerprint scanner still worked, but after flashing this ROM... http://forum.xda-developers.com/note-4/snapdragon-dev/25-october-2014-n4-echoe-rom-1-t2917941 it no longer worked & hasn't since. I am going back to stock (again) & hoping this will work. I'll update if it works.

See this post/thread, it worked for me....
http://forum.xda-developers.com/showpost.php?p=56896357&postcount=85
http://forum.xda-developers.com/not...ure-fingerprint-scanner-t2919478/post56896357

Looks like these are for T-Mobile. What about Sprint? N910P
Sent from my SM-N910P

JoeBear1975 said:
I am having the same problem of the fingerprint scanner not working after flashing a custom ROM. I followed everything to a T & it didn't install (& yes, it is for my N4). I went back to stock using Odin, several times & have not resolved it yet. I do not want to take it back but I do like having the fingerprint scanner. Luckily, I have another N4 cause I bought 2 when they came out cause I planned on trying to turn a profit on 1 of them, but I'll be damned if everybody didn't make it easy as hell for anyone to get one. I guess I can use the 1 that doesn't work right for flashing & playing around on & then when I find "THE" ROM that I'm happiest with, I can flash it on the good 1. IDK. This is BS though. Somebody has to know how to get it back working right. I know that people that helped create this phablet, are members of this site, so I hope that they or someone else that has fixed this problem replies to our question. I flashed this ROM... http://forum.xda-developers.com/note-4-sprint/development/rom-alpha-semper-fi-t2926682 & the fingerprint scanner still worked, but after flashing this ROM... http://forum.xda-developers.com/note-4/snapdragon-dev/25-october-2014-n4-echoe-rom-1-t2917941 it no longer worked & hasn't since. I am going back to stock (again) & hoping this will work. I'll update if it works.
Click to expand...
Click to collapse
sorry dude, I don't know what it was, but when it happened to me, I was on NIH, and had the fingerprint saved, i tried everything, and when i deleted the saved fingerprint, it didn't want to work, nothing worked, i tried for 2 days searching and trying out my own stock odex roms and the firmware, it did not work.. sucks i know...
i had to return it to tmobile corporate store, if u have insurance on it, just play stupid and return it, if u have someone you know on tmobile, just let them put it on their account with put the $8 insurance, have them wait 1 week, call 611 and just say the fingerprint sensor went bad, and just pay $5 and have a replacement sent out,
lucky for me it happened less than a week for me, and went to a tmobile corporate store and they gave me a new phone in a box, but a replacement is still good it is not a refurbished phone...

I got it figured out & will post a file once it finally uploads, but in the mean time. If you have registered at SamMobile.com go there, click on the firmware tab, scroll halfway down to where it says FIRMWARE on the left side of the column & search device here on the right side. Type in your model number & it will show up right below the search area. Click & download the newest file. Here is the link for the Firmware site with search field filled in with N910 http://www.sammobile.com/firmwares/ While that is downloading, do a factory reset on your phone, DO NOT backup your info, you will need to restart it, but it's worth it. Once the reset is done, your phone will reboot, don't worry about going into setup, just turn the phone off & go into download mode (while phone is completely off, hold, in this order, VOLUME DOWN, HOME & POWER, press VOLUME UP when prompted. Connect your phone to computer. After the file downloads, open Odin (I'm assuming you already have Odin installed on your computer, if not you can find the link here http://odindownload.com/ I didn't have luck with Odin 3.09, but the 3.07 version works great. Your Firmware file should be done downloading by now, if it is, put it in your Note 4 folder (or whatever folder you have designated for your N910-) & extract it to there. Open Odin & click on the PDA button (& DO NOT CLICK ANYTHING ELSE), click on the file you just extracted & then click Start. Once that loads, your phone will reboot & be just like it was from the factory. Hope this helps everybody. Once the file uploads to my Dropbox, I'll post it on here to save you some time.
Here's the link for N910P https://www.dropbox.com/s/f5f63rb4d8ybsm3/N910PVPU1ANK2_N910PSPT1ANK2_XAS.zip?dl=0
If this was helpful, please hit thanks.

mdiaz33685 said:
sorry dude, I don't know what it was, but when it happened to me, I was on NIH, and had the fingerprint saved, i tried everything, and when i deleted the saved fingerprint, it didn't want to work, nothing worked, i tried for 2 days searching and trying out my own stock odex roms and the firmware, it did not work.. sucks i know...
i had to return it to tmobile corporate store, if u have insurance on it, just play stupid and return it, if u have someone you know on tmobile, just let them put it on their account with put the $8 insurance, have them wait 1 week, call 611 and just say the fingerprint sensor went bad, and just pay $5 and have a replacement sent out,
lucky for me it happened less than a week for me, and went to a tmobile corporate store and they gave me a new phone in a box, but a replacement is still good it is not a refurbished phone...
Click to expand...
Click to collapse
I stuck with it & fianlly got it figured out. What a pain in the a$$ that was, lol

[Q] ****URGENT****Please Help

Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.

[OP] Photo of Camera Issue
Here is a photo of what I mean by the Camera color dilation. Demonstrated by a couple of Multi-Color Expo markers.

Download the G900A_Downgrade_to_NCE.tar from here:
https://www.androidfilehost.com/?fid=23622183712464416
Use Odin 3.09 and flash in AP slot. Once it is done then take the OTA for NG3 then OA1
Thanks to @muniz_ri

Tried it once before. It didn't work, ended up with a bootloop after flash of NCE.

ElectricBiskitz said:
Tried it once before. It didn't work, ended up with a bootloop after flash of NCE.
Click to expand...
Click to collapse
Did you use the same file from the link I provided?
Sent from my SAMSUNG-SM-G900A

I have used the same link you provided.

ElectricBiskitz said:
Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.
Click to expand...
Click to collapse
*UPDATE*
Fingerprint scanner does not work anymore either. Camera fixes itself if you change a setting and put it back.

[OP] It's Fixed!
ElectricBiskitz said:
Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.
Click to expand...
Click to collapse
Thank you for helping me with my problems. I did realize when I came back to the forum a couple of hours ago that my NCE download was only a kernel and not a firmware. I flashed the link provided and voila! It's fixed. I hope others that may have this problem can use this guide as an example. Because let's face it, you're living on the edge with an Android.

ElectricBiskitz said:
Thank you for helping me with my problems. I did realize when I came back to the forum a couple of hours ago that my NCE download was only a kernel and not a firmware. I flashed the link provided and voila! It's fixed. I hope others that may have this problem can use this guide as an example. Because let's face it, you're living on the edge with an Android.
Click to expand...
Click to collapse
I have the same issue exactly it says my bootloader is fused or something I have to flash the newest kernel to get it too boot up . I think I tried this already but can't hurt to try again .

All help needed, is my note 4 dying ?

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.