Related
So apparently the official 2.2 Froyo is rolling out. I haven't checked yet but I will when I get home. I have some newb questions.
I got my phone and haven't touched a thing to it. Just added lots of apps. No root. No lag fix. Nothing.
My question is, if I upgrade this officially via Kies:
1) Do I lose my contacts / stuff ?
2) Do I lose my apps ?
I heard people saying that once you upgrade to do a hard reset of the phone -- why ? What happens if you don't ?
With this in mind, how and what is the best way to back up all my apps ? I haven't rooted but i DO have Titanium Back up. Would Z4root work for i9000m ? can anyone confirm ?
Funkadelick said:
So apparently the official 2.2 Froyo is rolling out. I haven't checked yet but I will when I get home. I have some newb questions.
I got my phone and haven't touched a thing to it. Just added lots of apps. No root. No lag fix. Nothing.
My question is, if I upgrade this officially via Kies:
1) Do I lose my contacts / stuff ?
2) Do I lose my apps ?
I heard people saying that once you upgrade to do a hard reset of the phone -- why ? What happens if you don't ?
With this in mind, how and what is the best way to back up all my apps ? I haven't rooted but i DO have Titanium Back up. Would Z4root work for i9000m ? can anyone confirm ?
Click to expand...
Click to collapse
1) no
2) no
3) hard resets are only if you experience a ton of lag while operating the phone
4) z4 does not work on jk4
BlackDino said:
1) no
2) no
3) hard resets are only if you experience a ton of lag while operating the phone
4) z4 does not work on jk4
Click to expand...
Click to collapse
how do you root jk4 then ? 2.1 eclair on bell i9000m
1. Phone is currently rooted. Do I have to unroot it before applying the firmware upgrade from Kies?
2. Do I have to perform a factory reset before applying the firmware upgrade?
Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.
rajesh26e4u said:
Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.
Click to expand...
Click to collapse
A lot of people have been complaining that their SD cards have been screwed. Luckily mine went through without any problems and hasn't given me any trouble so far.
Froyo is insane tho, before the phone used to lag a bit, now the moment i touch it it opens. No need for lag fix in my opinion, everything works blazing fast as is.
One thing to watch out for is the WIFI. It was working normally at the beginning but after 3 hours it just disconnected for no apparent reason and has trouble connecting back.
Good luck
rajesh26e4u said:
Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.
Click to expand...
Click to collapse
Don't panic yet...
Try this
Volume UP/Power/Home(middle button)
Factory reset/Wipe
urfase said:
1. Phone is currently rooted. Do I have to unroot it before applying the firmware upgrade from Kies?
2. Do I have to perform a factory reset before applying the firmware upgrade?
Click to expand...
Click to collapse
1. NO
2. Good idea to factory reset before and after. Can't hurt and any noncompatible
programs and data will be gone.
Videonut said:
1. NO
2. Good idea to factory reset before and after. Can't hurt and any noncompatible
programs and data will be gone.
Click to expand...
Click to collapse
1) but will it erase root upon upgrading?
bimmerboii said:
1) but will it erase root upon upgrading?
Click to expand...
Click to collapse
Yep, but for optimised result, this is a must do!
You can probably have it work without doing a factory reset, but you can encounter weird behavior, bugs and stuff!
Anyway, you might end up doing it anyway to solve the firts boot issue
I'm one of the users who upgraded to Bell Froyo (from stock FW with root and lagfix - undid the lagfix before upgrading) and then encountered the broken internal SD card issue. I ran Volume UP/Power/Home(middle button) to reformat everything and it is up again. Inside the OS, I ran the internal factory reset again. So far so good. *crossing fingers*
I updated mine last night. However I've had major problems since. Initially it would just freeze up randomly and require removing the battery to get it back up and running.
Today I decide to reset it to defaults which seemed to go fine, although shortly after getting it all setup again, some Samsung app of sorts came up with an error and had to be forcefully closed. Then I was left with a black screen and only the notification bar.
Powered off the phone and went to turn it back on, and now it just loops through the Samsung GT i9000 screen (white writing). Not even the colourful S logo comes up.
I'm able to get it into Download Mode but not Recovery Mode. I'll have to do some reading about this Odin stuff tonight. Hopefully I can revive it, otherwise I guess I'll had to send it in for repairs. No idea if Virgin Mobile repairs will go through Bell or if I take it to them directly.
This is my first Android phone and I've only had it for just over a week. I thought I was making a good decision, but now I see it has quite a defect with the internal SD card failing.
Slow after upgrade
I upgrade my phone last night ( as per bell and Samsung) It is now slower than before. Quadrant Standard has it under 900.
Any ideas how to fix it?
bimmerboii said:
1) but will it erase root upon upgrading?
Click to expand...
Click to collapse
Just use SuperOneClick after you upgrade to Froyo, I've tested and have root on JK4
http://forum.xda-developers.com/showthread.php?t=803682
I have an unlocked phone from Bell that I already upgraded to the international (or European?) JPP/JPO 2.2, what is the best way to downgrade or restore back to default firmware before using Kies to get the official update? Does factory reset restore stock firmware?
I upgraded to official Bell froyo last night ..thn rooted.But how can i Unlock now? i tried using SGS unlock app it says no unlock codes found?? Please help
God damn samsung and bell!
it seems like they're giving defected phones to their costumers!
I have the corrupted sd card too, took it to guarantee now it takes more than 1 month to fix this!
this is f-ing xmas for god's sake. i want my phone
Same problem here!
I do have 2 good samsung galaxy s vibrants from Bell, however when i got the second one i upgraded to Froyo and now i cant unlock it because i cant read the stupid file inside the phone so,
How can i go back to my previous JH2 baseband?
Or
How can i unlock JK4?
I did my unlock on the other Galaxy using the script you donwload from somewhere in this website and then connecting the phone via usb cable with debugging on and mounting sd but with froyo i dont even know where my USB settings went!!!
Thanks for your help, greatly appreciated.
ciudadbonita said:
I do have 2 good samsung galaxy s vibrants from Bell, however when i got the second one i upgraded to Froyo and now i cant unlock it because i cant read the stupid file inside the phone so,
How can i go back to my previous JH2 baseband?
Or
How can i unlock JK4?
I did my unlock on the other Galaxy using the script you donwload from somewhere in this website and then connecting the phone via usb cable with debugging on and mounting sd but with froyo i dont even know where my USB settings went!!!
Thanks for your help, greatly appreciated.
Click to expand...
Click to collapse
Have you found any solution yet?? I am thinkin to flash back orignal samsung firmware using Odin n then unlock..atleast i will be able to use the phone then
Videonut said:
Don't panic yet...
Try this
Volume UP/Power/Home(middle button)
Factory reset/Wipe
Click to expand...
Click to collapse
what if after this, it's still stuck after the s logo boot up?
does this mean i have a broken internal sd?
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:
ok so i was running a devil kernel on jellybean 4.2 and for some strange reason the rom started acting funny and gave me a message saying i had to type in a password ti decrpyt storage even though i have no passwords on my samsung I897. So i decided to flash back to stock and start all over again from scratch using odin one click but in the middle of downloading my phone was disconnected and it gave me the bricked screen shortly after. Now i am unable to do anything on this phone ive tried pushing the volume buttons and taking the battery and sim card out while running odin 3 again trying to force it back into download but so far no progress has been made. If any one can help me it is much apprecitated.
theklxn said:
ok so i was running a devil kernel on jellybean 4.2 and for some strange reason the rom started acting funny and gave me a message saying i had to type in a password ti decrpyt storage even though i have no passwords on my samsung I897. So i decided to flash back to stock and start all over again from scratch using odin one click but in the middle of downloading my phone was disconnected and it gave me the bricked screen shortly after. Now i am unable to do anything on this phone ive tried pushing the volume buttons and taking the battery and sim card out while running odin 3 again trying to force it back into download but so far no progress has been made. If any one can help me it is much apprecitated.
Click to expand...
Click to collapse
Which Odin did you use? When already on JB, you should be using Odin KK4 without bootloaders to avoid hard bricks.
If your Odin was flashing bootloaders when it got interrupted, chances are that it's hard bricked and only JTAG service will bring it back. You can contact Josh at mobiletechvideos.com for it (of course there's a fee for the service).
You can try a jig before going through JTAG service (build or buy one), maybe you'll get lucky and be able to force download mode but know that if it got interrupted while flashing the BLs, only JTAG can bring it back.
i was afriad you might say that didnt think i would have to go that far to bring it back but thank you for the swifty reponse ill get back to you when my problem has updated
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
-Vatsal
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Re:
alfadog77 said:
sounds like the same software issue I had. Idk what happened but the internal memory failed on my note 4. Have you experienced constant freeze ups? also have you gone into download mode with an error that says "mmc_failed can't boot"? It was something along the lines of that.
Click to expand...
Click to collapse
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Enalay527 said:
Yes I have those same issues. I am getting a new phone but I have to give this one to someone else and I need it in good shape to give it to them. Do I need to just buy a replacement or is there any way I can get it fixed?
Click to expand...
Click to collapse
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
aaldiar said:
Have you tried to update to the latest firmware? DOK2 fixes a lot of issues including the memory leak.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I updated it ota then on Samsung kies with the latest firmware. Everything works fine except the power off issues.
I think this is a common 5.0.1 issue, same thing started happening to me after update. Gotta wait for update or back to 4.4.4.
Enalay527 said:
I have had my Sm-N910T for about a year now. When I first got it I rooted it without thinking it through. I used Odin and flashed cf autoroot. I unrooted it when it started giving me issues. Then it would restart, freeze, etc. I now have an app called wakelock and it prevents my phone from turning off. It works great it has the original firmware that installed through Samsung kies but when I try to restart it just shuts down. When I power off I can't always power back on right away. I have to pull the battery and hold the power button for 1 minutes release, then put the battery back in and it works again. I have put the original firmware and it is not rooted anymore. Is there any way I can fix this issue? So basically it works fine but if I turn it off I have to pull the battery to be able to turn it back on. Every once and awhile it'll go into download mode on its own too.
Click to expand...
Click to collapse
I would recommend downloading the full DOK2 firmware. You can find it in the below linked thread. Make sure you use the newest version of ODIN to flash it 3.10.7.
It should give the phone aq complete clean install of the firmware. Kies sometimes can be janky. It you are going to get rid of the phone the best is to do a full ODIN flash.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
notufatjesus said:
I been having the same issues ...even with full firmware flashed DOK2....I get internal memory failure. Hope someone finds a fix. Have to pull out battery, sim cards, and spen, then press all the buttons, thennnnn....put everything back to boot up. Power button won't work, and reboot won't reboot. It Just turns off. Sucks...I love this phone. Right now it's acting ok...occasionally I get freezes and major lag. Someone please help!
Click to expand...
Click to collapse
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
tony yayo said:
I had this problem too except it got really really laggy and would constantly reboot anytime I tried to do anything. Best I could figure out was it was a problem with the internal sd. Called TMO tech support, told them I did factory reset, tried it without the sd card, blah blah blah. I said it's a hardware issue that is beyond my control and I don't feel like I should have to pay for it. They said well it sounds like you already did the work for us. I guess it was still under warranty but I got a new phone the next day and no problems since. Hopefully whatever was wrong they have fixed the issue by now but so far so good.
Definitely mention the mmc read fail error or whatever it says. All it cost me was a $5 charge. Give em a call.
Click to expand...
Click to collapse
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Willy318is said:
Hello there, I'm having the same exact issue lately, phone is a Year old, and I think its failing, One question though!
Was your phone ever rooted? mine is, but I flashed the Stock DOK2, so its official with NO root now, but I think the Device status is CUSTOM not official, Also KNOX has tripped while rooting, would T Mobile honor a replacement? At least its on the Official OS with NO Root now.
Please enlighten me
Click to expand...
Click to collapse
Not really sure. Mine was never rooted. I've heard of plenty of people sending their rooted phones in with no problem.
thiennvbk said:
I have the same problem, and it only happen when I update the phone to newest firwame, DOK2.
When I use COG1 firwame it very fast and easy use. but when I update DOK2 over Odin, I few very lag and usually restart the phone when I run a big application, then It can't restart after, just turn off.
And after that, can't turn on the phone. I had remove pin in 10s, pull in and it power on normal.
Sometime I turn on the power and the phone go into download mode with notice "mmc_fail can't boot".
Now I just only want to download my phone to old firwame, COG2 and use it normal, but the new firwame with new bootloader don't allow to download old bootloader. So sad
anyone can't show me how to download to COG2 firwame, Please....
Click to expand...
Click to collapse
Make sure you are using the ODIN version 3.10.7 if you are using an older version of may be what caused the issue.
If you did use the newest Odin, then I would factory reset your device, but into twrp and wipe everything but external SD Card, boot back into download mode and flash the firmware again. Most likely a few files for messed up during your Odin flash and it messed up the process. Also make sure you are using the USB cord that came with the device.
I found the fix for this mmc_failed. Making a new thread for this.
---------- Post added at 06:11 AM ---------- Previous post was at 05:38 AM ----------
http://forum.xda-developers.com/showthread.php?t=3277144
Here's is the fix. Don't forget to hit Thanks button
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.