Database Develop

Boot loop after CM7 & Baseband 15

Hi Guys,
I had a reboot loop problem in my X8 after installing Viber from a Wifi connection and decided to mod it. I successfully unlocked the boot loader & rooted my Xperia X8. Flashed it with CM7 RC1 V4. I rebooted the phone to see the Cyanogen Mod screen with the skate board and it proceeded to ask me a question about the setup wizard or market option, I made a selection and the phone went dead. It rebooted and started hanging on the SE logo. I thought it was due to Baseband 15 and flashed it but no luck.
I have Clockwork Mod on it and can randomly enter it also. I would appreciate any help and pointers, is this an issue due to using the wifi and is the hardware at fault. Once the boot loop starts the battery drains pretty fast I can see the Cyanogen battery status icon and try to wait for it to charge completely
Many thanks & regards

bytecodeboy said:
Hi Guys,
I had a reboot loop problem in my X8 after installing Viber from a Wifi connection and decided to mod it. I successfully unlocked the boot loader & rooted my Xperia X8. Flashed it with CM7 RC1 V4. I rebooted the phone to see the Cyanogen Mod screen with the skate board and it proceeded to ask me a question about the setup wizard or market option, I made a selection and the phone went dead. It rebooted and started hanging on the SE logo. I thought it was due to Baseband 15 and flashed it but no luck.
I have Clockwork Mod on it and can randomly enter it also. I would appreciate any help and pointers, is this an issue due to using the wifi and is the hardware at fault. Once the boot loop starts the battery drains pretty fast I can see the Cyanogen battery status icon and try to wait for it to charge completely
Many thanks & regards
Click to expand...
Click to collapse
* Did you factory reset it from CWM before installing the ROM? Boot loops are common when one doesn't, particularly if you're coming from another ROM (from what you say, I guess you're coming from stock 2.1)
* It seems that you flashed baseband 015 AFTER flashing the new ROM. AFAIK it should be done BEFORE flashing a new ROM, while still on stock 2.1. If that's the case, you'd have to go back to 2.1 using SEUS (or Flashtool; there are stock ROM images here on XDA), THEN flash baseband 015, THEN root, THEN flash CM7 again.
---
As a side note, you unlocked your bootloader but didn't install a new kernel, which is what one normally unlocks the bootloader for. Unlocking the bootloader isn't needed to flash a ROM as long as it works with the stock kernel (most don't, but yours should.)

Mod issue or battery or hardware fault
Cheshire-Cat said:
* Did you factory reset it from CWM before installing the ROM? Boot loops are common when one doesn't, particularly if you're coming from another ROM (from what you say, I guess you're coming from stock 2.1)
* It seems that you flashed baseband 015 AFTER flashing the new ROM. AFAIK it should be done BEFORE flashing a new ROM, while still on stock 2.1. If that's the case, you'd have to go back to 2.1 using SEUS (or Flashtool; there are stock ROM images here on XDA), THEN flash baseband 015, THEN root, THEN flash CM7 again.
---
As a side note, you unlocked your bootloader but didn't install a new kernel, which is what one normally unlocks the bootloader for. Unlocking the bootloader isn't needed to flash a ROM as long as it works with the stock kernel (most don't, but yours should.)
Click to expand...
Click to collapse
Many thnks for the reply mate, what you said is right. I might have missed a few things. But I reflashed Baseband 15 yesterday before your reply to my post and now it seems to be booting into cyanogen mod happily but each time it takes only a few seconds and through a few setup screens before it reboots again.This is exactly what was happening even on the stock ROM before doing any Mod procedure and the battery gets drained too. Could this be a hardware fault.

bytecodeboy said:
Many thnks for the reply mate, what you said is right. I might have missed a few things. But I reflashed Baseband 15 yesterday before your reply to my post and now it seems to be booting into cyanogen mod happily but each time it takes only a few seconds and through a few setup screens before it reboots again.This is exactly what was happening even on the stock ROM before doing any Mod procedure and the battery gets drained too. Could this be a hardware fault.
Click to expand...
Click to collapse
i didnt get it, when on setup screen you mean when it tells to add your email.....and when you are finished it reboots?!
if i understood well,there is no hardware problem, go to cwm, full wipe-factory reset,advanced>wipe dalvik, reinstall your rom(install custom zip) and it should work:fingers-crossed:

stamatis16 said:
i didnt get it, when on setup screen you mean when it tells to add your email.....and when you are finished it reboots?!
if i understood well,there is no hardware problem, go to cwm, full wipe-factory reset,advanced>wipe dalvik, reinstall your rom(install custom zip) and it should work:fingers-crossed:
Click to expand...
Click to collapse
Thanks for the reply stamatis, basically its just shutting down because there is no battery left to power it, it seems. At times it reaches upto the setup wizard (shown when booting for the first time), the next time it could go up to adding a gmail account or language selection screen. I have even seen it load the home screen before it shuts off. This all started happening after downloading some apps from a wifi connection. I have done that before wiping and re installing but will try again. My presumption is that since it was happening on stock ROM and now on CM7 too then it's probably a hardware issue
Regards

bytecodeboy said:
Thanks for the reply stamatis, basically its just shutting down because there is no battery left to power it, it seems. At times it reaches upto the setup wizard (shown when booting for the first time), the next time it could go up to adding a gmail account or language selection screen. I have even seen it load the home screen before it shuts off. This all started happening after downloading some apps from a wifi connection. I have done that before wiping and re installing but will try again. My presumption is that since it was happening on stock ROM and now on CM7 too then it's probably a hardware issue
Regards
Click to expand...
Click to collapse
ok i see now,your problem is battery drain,
is it that extream? i mean, you charge to full and when you open it up it shut down by low battery?
have you try to opening while charging?is it the same?
are you sure its charging?
that way too xtream to be software problem so its more likely that its hardware...

stamatis16 said:
ok i see now,your problem is battery drain,
is it that extream? i mean, you charge to full and when you open it up it shut down by low battery?
have you try to opening while charging?is it the same?
are you sure its charging?
that way too xtream to be software problem so its more likely that its hardware...
Click to expand...
Click to collapse
yes you got it right. I do charge it fully and when it boots the CM7 UI for a few seconds the battery goes down half or even less or nearly empty. I have tried opening it while charging and thats when the above happens, yes I can see the Cyanogen charging icon. So you think its a hardware issue and I should not pursue it further

bytecodeboy said:
yes you got it right. I do charge it fully and when it boots the CM7 UI for a few seconds the battery goes down half or even less or nearly empty. I have tried opening it while charging and thats when the above happens, yes I can see the Cyanogen charging icon. So you think its a hardware issue and I should not pursue it further
Click to expand...
Click to collapse
yea, i guess your battery almost dead.....and i dont think its a good idea to by new battery, you better buy new phone,as the batteries are quite expensive if you think that the worth of the x8 right now would be 50 euros....

Try ebay bro
Sent from my E15i using Tapatalk 2

Flash rom with xrecovery not cwm
Sent from my X8 using xda premium

[Q] Help with G-Note Revival...

Hi Guys...
I got a Galaxy Note GT-N7000, and its been more than a week i tried to revived it using the any method i've found in this great forum.
So let me tell u guys the stories of my Note :
1. It was always updated OTA so the last ROM i used is Indonesian Note ICS 4.0.4
2. One day (last Friday) while i was browsing Internet using it, it suddenly got very hot, and the battery seems like draining very fast
3. In the mid day it reboot by its self, and entering countless reboot... a never ending reboot
4. So i tried to enter recovery, and yes sadly i've might triggered the emmc bugs by doing factory reset. But i'm not sure i've done it or not, coz i've a CWM recovery installed.
5. Anyway then i tried to flash stock room found in dr.ketan's thread...many thanks to him for those collection using PC ODIN and i got the "factoryfs" stuck problem
6. I also tried to flash countless kernel over and over, tried install Stock GB and ICS, tried RocketROM, CM10 and it all failed. In dowload mode i still got a Stock Firmware installed. So any ROM i've tried to install using Kernel didn't succed.
7. So i decided to take it to Samsung Service Center nearby, and i found that my battery is BAD, it wont charge (wonder would it because of the battery i got that problem in the first place). Since i got this Note for around 8 months, and the warranty for the battery is 6, the make me bought the new one, ordered and available in 2 days.
8. So I get back to the service center, put the new battery restarted the phone, and it stop on samsung logo (no yellow triangle there). So I complained, and they look into it, and said we may try to install new software, but there's a risk that your Note got damaged. They said the risk is mine and they wont have any responsible for it.
9. So furiously i bargain about my Warranty (12 month), coz the said that i've updated the ROM my self, so i explained to them that it was OTA's update, all i do was press YES, and they said even OTA official update will cancel my warranty. Its getting weird, i got angrier and they just said its their company procedure so there's nothing they can do to help me. So Samsung Indonesia will cancel warranty for every attempt to update the ROM OTA's, only their service center is allowed to do so. Wasted my valuable working hours there...
10. So i get back, determined i officially will do anything to get this Note life back. So i started to look at Forrest1971 (many thanks to him) thread about bricked note and tried many kernel and got one working with adb (T-Kernel V0.9) doing the checking and found faulty partition 9 and 10 and doing the step and finally got the partition fixed. Lost 3GB of space.
Then here came the real problem :
1. Still wont work with ODIN, stuck at Factoryfs with stock ROM GB N7000DXLC2_N7000OLBLC2_N7000DXLC1_HOME.tar and ICS N7000DXLR5_N7000OLBLR2_N7000DXLR1_HOME.tar. But working fine flashing Kernel so my guess it is not the connection problem. I've tried on 1 PC, 2 Laptops, 2 OS (Win7 32bit and WinXP 32 bit) still the same.
2. Then i tried to flashing via Kernel (CWM, Abyss, T-Kernel, CM9 Safe Kernel) i got to do trial and error coz not all ROM can be installed using any given Kernel. Seems that T-Kernel v0.9 is working for most of the ROM. Sorry i didn't keep note about the kernel-rom coupling. Here is the list of ROM i've tried :
cm-9.1.0-n7000 + gapps-ics-20120429-signed
cm-10-20121209-NIGHTLY-n7000 + gapps-ics-20120429-signed
RocketROM v2 XXLS7_stock_odexed
SuperNexus-N7000-BUILD5-20121017 + gapps-jb-20121011-signed
RocketROM_ICS_XXLPY_v1
3. All of those ROM came out with the same problem :
- Freezing on the Samsung/Mod Logo Screen (Got very HOT)
- Entering the "Andoid is Upgrading" and then updating Apps but stuck at random number (# of ###) (Got very HOT), i've tried to wait overnight but stay on the same number
- Succeeded boot up but Freeze after couple of minute (Got very HOT)
4.All those problem seems happened randomly, but most of the time it happened like this :
Stuck and Logo Screen - Reboot by me - Stuck and Upgrading - Reboot by me - Boot fine, but freeze very soon - Reboot by me, and back to the Logo stuck... (but still sometime its just random), the only thing same that it got very hot.
5. This is my last resort, i'll try to flash Supernexus, CM9 or CM10 without the GApps. Now i'm on Supernexus ROM, not yet freeze while i'm typing this. But without the GApps i wont have G-Play, and cant reinstall Apps that i bought in G-Play. Dilemma...
So any thoughts or advices will be greatly appreciated...
I really like this phone, wish i can revived this phone... :fingers-crossed:
Thanks B4 for any comment...

Well, i guess no one have the same problem here...
I'm running the rocket ROM ICS right now, this is the one ROM that got me closer to "STABLE" state.
Still got self reboot, most of the time when i'm using browser (Android, FF, Chrome), or after a long run on youtube or downloading something.
I've also tried the PA Experia ROM by AmniX : http://forum.xda-developers.com/showthread.php?t=2100083
But it was worse than rocket ROM ICS, more likely have the same symptom with the CM9/10 i've tried.
So seems like i've to manage to use this defect/handicapped gadget... :fingers-crossed:

diasdroid said:
Well, i guess no one have the same problem here...
I'm running the rocket ROM ICS right now, this is the one ROM that got me closer to "STABLE" state.
Still got self reboot, most of the time when i'm using browser (Android, FF, Chrome), or after a long run on youtube or downloading something.
I've also tried the PA Experia ROM by AmniX : http://forum.xda-developers.com/showthread.php?t=2100083
But it was worse than rocket ROM ICS, more likely have the same symptom with the CM9/10 i've tried.
So seems like i've to manage to use this defect/handicapped gadget... :fingers-crossed:
Click to expand...
Click to collapse
I would complain to the service center. It's absolutely rubbish that an ota update voids warranty, they're lying through their teeth and I wouldn't stand for it. So long as you have no trace of custom rom or root, they are required by law to fix the phone or replace it within 12 month warranty. If you'd left traces of root or Cwm that's a different story.
Try a second repartition, often a first scan will not find all bad sectors, run through it again just to be safe. Also, after repartitioning its usually the case that stock or tw based Roms won't work without freezes and reboots because they occupy too much space on the emmc. You're best with cm or aokp Roms.
Sent from my GT-N7000 using xda premium

N910W8 Bricked?

Hi.
I am using a N910W8 from wind mobile.
I got this phone not too long ago.
My last rom used was cm12.1. Nightly 2016 04 26
A few days ago, it started to hang, I did a system format via recovery and swiped fix permissions (huge mistake)
It booted up and I was installing my apps by play store when the phone hanged.
And now, my phone would only turn on if I pulled the battery out for a couple of minutes. My phone would keep freezing if I tried to install or rom, any rom.
It is unable to boot. Not even to the logo.
It would freeze if I basically turned it on for more than 30 seconds, in recovery or download mode.
Is my device bricked?
I am open to all suggestions and recommendations.

Boot into twrp and wipe EVERYTHING at least 3 times (I do 5 lol) re-flash rom and see if that works.
If it didn't fix your problem, Odin back to stock (use any stock firmwear from sammobile i.e. Rogers/Bell/Telus ect).

mistamikel said:
Boot into twrp and wipe EVERYTHING at least 3 times (I do 5 lol) re-flash rom and see if that works.
If it didn't fix your problem, Odin back to stock (use any stock firmwear from sammobile i.e. Rogers/Bell/Telus ect).
Click to expand...
Click to collapse
I have tried wiping everything more than 3x, sometimes it freezes while wiping. It freezes while flashing via twrp and it freezes while flashing via Odin.

Sounds like a main board problem.
I think you might be SoL

mistamikel said:
Sounds like a main board problem.
I think you might be SoL
Click to expand...
Click to collapse
Do you know how much it would cost to replace a n910w8 mobo?
Where can I buy one...?

Arcfour said:
Do you know how much it would cost to replace a n910w8 mobo?
Where can I buy one...?
Click to expand...
Click to collapse
Honestly you're gonna have to keep your eyes peeled for a used one to pop up on kijiji or something. Maybe look for ones with broken screens to keep costs low.
You could try eBay as well.
But before you do all that, maybe try a different battery ??
Shoot me a pm If you need any advice

Arcfour said:
Hi.
I am using a N910W8 from wind mobile.
I got this phone not too long ago.
My last rom used was cm12.1. Nightly 2016 04 26
A few days ago, it started to hang, I did a system format via recovery and swiped fix permissions (huge mistake)
It booted up and I was installing my apps by play store when the phone hanged.
And now, my phone would only turn on if I pulled the battery out for a couple of minutes. My phone would keep freezing if I tried to install or rom, any rom.
It is unable to boot. Not even to the logo.
It would freeze if I basically turned it on for more than 30 seconds, in recovery or download mode.
Is my device bricked?
I am open to all suggestions and recommendations.
Click to expand...
Click to collapse
You device is just a soft brick, nothing major, 1) you can use Kies to restore the firmware, 2) you can use ODIN to restore the firmware .
firmware can be download at SamMobile

mistamikel said:
Honestly you're gonna have to keep your eyes peeled for a used one to pop up on kijiji or something. Maybe look for ones with broken screens to keep costs low.
You could try eBay as well.
But before you do all that, maybe try a different battery ??
Shoot me a pm If you need any advice
Click to expand...
Click to collapse
At those prices, I should be looking to get another phone eh?
y2k-inc said:
You device is just a soft brick, nothing major, 1) you can use Kies to restore the firmware, 2) you can use ODIN to restore the firmware .
firmware can be download at SamMobile
Click to expand...
Click to collapse
I tried setting it into download mode but kies does not detect and ODIN always freezes half way. (more like 20%)
Thanks for replying guys.

Arcfour said:
At those prices, I should be looking to get another phone eh?
I tried setting it into download mode but kies does not detect and ODIN always freezes half way. (more like 20%)
Thanks for replying guys.
Click to expand...
Click to collapse
in Kies, try firmware recovery, when asked enter your phone information (remember, all information should be in CAPITAL LETTERS)
and then when ready put your phone in DOWNLOAD mode.

phone crashing issue

So, question.... This might not be a Rom issue. But I figured I would ask. Has anyone been having issues of the phone crashing and completely shutting down when you open the camera app.... Or any camera app? I've found two ways to get the phone back on after this happens. You can pull the battery and restart... Or plug the phone into any charger and after a second it will show you the battery w lightning bolt.... Then show its charging normally with the phone off... Then you can reboot.
Now things to point out.... It doesn't matter if the battery is at 96%....or 46%.....this still happens. Also, I just bought a brand new battery for the phone maybe a month ago, and it's still doing the same thing....
Another also.... I kept thinking this was a hardware issue.... And had tmobile replace the phone.... This is my 4th phone... And they've all been doing the same things.
I also thought this could have been a conflicting app issue. So I uninstalled almost everything that I don't use and still have been having the same problem..... So.... Anyone? Any thoughts? Thanks
My phone is rooted , running [ROM] Maximum OvrDriVE 6.0.1 MM V3.2 (8/24/16) [910T/910W8/910T3] Running update 3.5

SamJamz said:
So, question.... This might not be a Rom issue. But I figured I would ask. Has anyone been having issues of the phone crashing and completely shutting down when you open the camera app.... Or any camera app? I've found two ways to get the phone back on after this happens. You can pull the battery and restart... Or plug the phone into any charger and after a second it will show you the battery w lightning bolt.... Then show its charging normally with the phone off... Then you can reboot.
Now things to point out.... It doesn't matter if the battery is at 96%....or 46%.....this still happens. Also, I just bought a brand new battery for the phone maybe a month ago, and it's still doing the same thing....
Another also.... I kept thinking this was a hardware issue.... And had tmobile replace the phone.... This is my 4th phone... And they've all been doing the same things.
I also thought this could have been a conflicting app issue. So I uninstalled almost everything that I don't use and still have been having the same problem..... So.... Anyone? Any thoughts? Thanks
Click to expand...
Click to collapse
For folks to assist, you will need to provide basic info like rooted or no what firmware are you on, what model of note 4 etc....

I have the exact same problem with OP and will also have chance of crashing if you open Facebook or FB Messenger or Google Chrome. Sometimes it will die instantly around 80% where once die on 90%+ when trying to take a picture using stock camera apps. When it die you see a quick less-than-second horizontal matrix line.
Some detail of my current phone is as below:
Model: SM-N910T3
Android OS: 6.0.1
Baseband: N910T3UVU3EPJ2
Kernel: 3.10.40-9385989 ; [email protected] #1 ; Wed Oct 12 15:31:09 KST 2016
Build No.: MMB29M.N910T3UVU3EPJ2
Root Status: None (Never rooted)
Firmware: Stock ROM (Never flashed Custom ROM, flashed latest Stock ROM once, success)
The problem occur when I get OTA update from LL to MM. Few months later update again through OTA to current firmware but problem still occur. Then tried factory reset but didn't solve the problem. I thought of bad update download with OTA, so I download the latest firmware on SamMobile and flash it with Odin3.11.1 hoping will fix the problem. It didn't fix the problem, but I seen some new apps shown up as below:
- Android System WebView
- Beaming Service for Samsung
- ANT Radio Service
- ANT+ Plugins Service
- Briefing for Samsung (Update) <--- Exact apps name shown in Google Play
None of these apps were what I'm aware of even after I did the latest OTA updates. I hope anyone can help troubleshooting this issue as this is really annoying and now I have to always carry a power bank with me. For now I will try to re-download the firmware again and see if that will help although I doubt it will. Many thanks in advance!
---------- Post added at 12:42 PM ---------- Previous post was at 12:36 PM ----------
Also I have the same issue as the OP in the link below with the same battery usage drop picture.
http://forums.androidcentral.com/samsung-galaxy-note-4/610523-note-4-sudden-battery-drain.html
I go through the whole thread but none of the solution work. Though it might be helpful to post it here.

http://forum.xda-developers.com/note-4-tmobile/help/note-4-issues-post-11-06-2016-t3495012

sloanster said:
http://forum.xda-developers.com/note-4-tmobile/help/note-4-issues-post-11-06-2016-t3495012
Click to expand...
Click to collapse
I see your post is for N910T. Mine is N910T3, will flashing T2 stock firmware works?

jackgan said:
I see your post is for N910T. Mine is N910T3, will flashing T2 stock firmware works?
Click to expand...
Click to collapse
You can try..
Odin will either let you or not!
I find it hard to mess up the device, I've tried lol...
But that's just me!!!
It's yours to risk...
I'm currently on the T2 firmware!

After update to EPJ2, my Note is crashing too. Seems like there is a heekup in a processing power/ram. It lags for a moment and shuts down. So far this happened with Camera app, Chrome, Facebook, and a few other apps. Sometimes I would get "emmc read fail" or something along the lines and the phone would not boot. The only thing that seems to be MORE stable is Dirty Unicorns ROM, anything based of the STOCK or any Samsung ROM crashing.

Same issue: Note 4 restarts itself, many times.
This is my first post. I have the same problem with my Note 4: Bought it new a month ago (via eBay with 30 days warranty, then cannot return or exchange). The phone restarts itself many times, especially when I use the camera. A friend suggested me to download the stock ROM (N910TUVU2EPJ2) and use ODIN. Now, as long as I slow a bit, pressing and wait then the phone is okay. If I press anything fast, many times, then it restarts itself again. Seems like the RAM is dead. I have read somewhere that we can downgrade from N910TUVU2EPJ2 (version 6.0.1) to N910TUVU2DOK2 (version 5.0.1) and it runs smoother. Anyone has any idea, please help. If downgrading to the DOK2 can solve the problem, please let me know. Thank you for this great forum.

Skinny7 said:
This is my first post. I have the same problem with my Note 4: Bought it new a month ago (via eBay with 30 days warranty, then cannot return or exchange). The phone restarts itself many times, especially when I use the camera. A friend suggested me to download the stock ROM (N910TUVU2EPJ2) and use ODIN. Now, as long as I slow a bit, pressing and wait then the phone is okay. If I press anything fast, many times, then it restarts itself again. Seems like the RAM is dead. I have read somewhere that we can downgrade from N910TUVU2EPJ2 (version 6.0.1) to N910TUVU2DOK2 (version 5.0.1) and it runs smoother. Anyone has any idea, please help. If downgrading to the DOK2 can solve the problem, please let me know. Thank you for this great forum.
Click to expand...
Click to collapse
I'm on pe3 is that a good one I'm a noob on this form

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.