phone crashing issue - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

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

Related

Samsung Galaxy S I9000 - ICS 4.0.3 - Stopped Booting

Hi,
I installed a Cyanogenmod ICS 4.0.3. build 17 firmware on my Samsung Galaxy S I9000 almost 5 months ago from a tutorial. The update itself has been a fantastic experience from the start and I'm not sure if my current problem is even related to that firmware update. Apparently new users like me can't post URLs so I can't provide it now. If you need it let me know.
I have to admit that lately the phone has been rebooting every couple of days, or Android's been freezing and I had to remove the battery, but I didn't think too much of it. It wasn't too bad of a problem really, but this morning all of a sudden the device has become totally unusable. Help! :-/
The issue that's started since today is that my phone won't boot anymore. It seems to reboot somewhere during the boot process. There's only two screens that will be shown, before it reboots. When I remove the battery, put it back in and attach the charger, I will only see two charging screens. While charging, the device will also*reboot after a while.*
I can get into download-mode (volume-down + ok-button + power-key) but can't get into recovery mode (volume-up + ok-button + power-key).
Any ideas would be appreciated, thanks!
Greetings,
Adriaan
ps -> I have pictures of the booting screens and the charging screens but wasn't allowed to post them here. Again, if you need to see them please PM.
Hi,
I think you have to reflash using odin. You can be happy to reach download mode
I'll try that, thanks.
switch_42 said:
Hi,
I think you have to reflash using odin. You can be happy to reach download mode
Click to expand...
Click to collapse
just to be sure...
Just to be sure, could you please check that my logic is correct?
First off: the tutorial I had followed had me follow a few procedures:
first I updated Galaxy S with XXJVU Firmware
then rooted Galaxy S on XXJVU Firmware
after that I flashed CM 9, ICS 4.0.3. build 17 to the device
To which of these steps were you referring? My guess would be to take the last one, but perhaps it's wiser to restart the tutorial from the beginning. I'd appreciate any additional support you can give me, you can understand that I don't want to brick my device due to my misunderstandings..
Seems like a high overclock or high underclock
Sent from my GT-I9000
Helloworld294 said:
Seems like a high overclock or high underclock
Click to expand...
Click to collapse
Not sure what you mean there. In any event I've never taken any steps to overclock or underclock my device. Maybe it's going senile and I get to buy a galaxy s III soon
*phew* well my problem's been solved. Since I was able to get into download mode I flashed a baseline rom with Odin and found my way back to ICS. One surprise along the way was that from the same tutorial I had followed (and had happy results from) a few months ago, the step of using Odin to root the device wasn't working, it kept getting stuck at 'zImage' during the process! What's more, after that I was getting the BSOD image (the phone, exclamation mark and computer), which I found could be helped by using a 'One-Click Unbrick for Samsung devices'.
That was a XXJVU firmware. After some snooping around I found a different firmware than the one I had previously used and had switched from a XXJVU firmware to a XXJW4 firmware through a page on XDA-Developers. Did that. It worked. And now I'm back to ICS again, yay!
Thanks for the help along the way!

T mobile note 4 restart, and power issues

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

Firmware update, EQC1?

I don't see EQC1 on sammobile, anyone else see the 127 MB update?
I'm on EQB1.
Yup, I see it, 127.53mb on both of mine SM-N910T3 and
SM-N910T
I have it as well. Have you flashed yet?
I have it too. I'm not sure I want to flash, especially if it patches the ability to root my phone.
My phone also suffers from the SD card / reboot issue (the phone constantly boot loops when both an SD card and SIM card are in the phone). I wonder if this update will fix that?
I tried flashing it and it failed, I'm running a stock highly modified rom. I'll try reflashing the original stock unmodified rom when I get a chance tomorrow and apply the update. It looks like it's just security updates
Says "Various system improvements" for the QC1 update.
https://support.t-mobile.com/docs/DOC-28899
I updated to this version the other day, now I'm looking to root. Anyone know if the old root method still works? I may try myself in the next few days myself and find out.
I upgraded to it yesterday. Took about 30 minutes from start of install to finish. It updates the security to March 2017, has the new Google Play Store. Other than that I do not notice any other differences
Can i root after upgrade?
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
febzz88 said:
Does anyone know if this fixes the mmc_read failed issue along with its constant lagging/freezing problem?
Click to expand...
Click to collapse
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
d0ug said:
I'm pretty sure the mmc_read failure issue is failing hardware and no firmware release can fix this. My understanding is some Note4's had dodgy flash memory and will eventually fail. I had this happen to my note4 last year and got it changed out under warranty at a tmobile store. My phone had the constant lagging/freezing for about a month before it would just no longer boot, it wouldn't do anything other than a quick vibrate on power up, no boot screen of any type.
If you are getting mmc_read I would suggest you get the phone replaced ASAP, and make backups of everything you have on it that you want to keep. At some point it probably just wont power back on again. Hopefully you are still under a warranty and can get it swapped out.
Click to expand...
Click to collapse
Hi,
That's certainly is one possible scenario (hardware failing). But based on my extensive research too, many have said that this could be faulty firmware. I went to a Samsung Experience Center and talked with a guy there and he said that it's a known issue affecting many Galaxy Note 4 Sprint users a few months ago. Samsung in the end replaced/repaired the affected units free of charge.
In the past 2 months or so, more and more Galaxy Note 4 users started experiencing this issue. And so it could be that the firmware triggered the issue, and eventually damaged the hardware.
Since we don't really have a 100% certain answer (of course, Samsung will never tell us), I'm just trying to see if anyone has updated the phone to the latest firmware and could tell us if it fixed the issue.
Soooo..... Is this rootable or not?
sino8r said:
Soooo..... Is this rootable or not?
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/no...rom-n910t3uvu3eqc1-stock-rooted-odex-t3592242
I can't seem to get TWRP to work on this. I've tried several times with Odin, it appears to be successful, phone reboots, but then when I try to reboot into recovery there's no TWRP, only stock. Anyone else have this issue or any suggestions?
Edit: Tried something I remembered reading in another thread. I pulled the battery immediately after Odin successfully finished and the booted directly into recovery. It worked. I'm flashing pvsgh's rooted EQC1 and will report back if TWRP sticks
Edit 2: Success. Seems like pulling the battery after Odin/TWRP before the phone reboots did the trick
ok, thanks for the suggestion.
Anybody have a link for the firmware?
thecrunked said:
Anybody have a link for the firmware?
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...firmware-galaxy-note-4-n910tuvs2eqb1-t3569911
Can I autoroot with EQC1?
I tried auto root and got
RECORVERY IS NOT SEANDROID ENFORCING,
AM I screwed? I assume there's some way to get back to EQC1 and boot the phone. There has to be. But could I do it and keep the data. I was trying to get deleted photos back.

My LeEco Le 2 charges slowly and Heat up while charging

Hello Everyone,
I recently ordered a phone from aliexpress.com 3 months ago. and I must confess, its a nice phone. details are:
Device name: Le 2
Model: Le X520
Android Version: 6.0.1
Android security patch level: December 1, 2016
EUI version: 5.9.023s (Stable)
CPU: Snapdragon 625 8 cores 1.8 ghz
And I believe it is a stock ROM. One day after updating all my apps successfully, some days later one of the app (dictionary) started giving me a false update. It will display downloading then the status of the download is paused. Whenever I click on the item downloading it will do nothing. If I reboot the phone, more downloads will appear and so on. So I uninstalled the dictionary app thinking it will stop, but that same downloading still appeared. Then I decided to do a factory reset on the phone but before doing that, I backed up my apps including system and user apps.
After the factory reset, I installed all the applications but I keep getting "sorry google play services has stopped" error messages, I have updated to the current play services 11.7.46 and I am still getting the same error message.
And the most annoying thing is that, after the reset, the phone stopped charging fast, though the fast charging is enabled, now it takes for ever to charge to 100% and it discharges fast too and when charging, the battery temperature raises above 45 degree.
And please don't tell me to change cable and charger because i have about 5 cables including the cable that came with the phone which is still inside the box (new) never used before and its still giving me a slow charging on my phone but will charge my friend's phone fast.
So I believe that the factory reset removed the fast charging from the phone.
please I need help on what to do
thanks
I'd recommend installing 19s or 21s stock as both come with Gapps. 23s does not come with Gapps by default with the Google framework app frozen. Your seller must have installed gapps for you.
Dudeonyx said:
I'd recommend installing 19s or 21s stock as both come with Gapps. 23s does not come with Gapps by default with the Google framework app frozen. Your seller must have installed gapps for you.
Click to expand...
Click to collapse
Thanks for your reply.
I would like to know the steps in getting a stock 19s or 21s and also installing it. I would also want to backup my 23s ROM just in case something goes wrong with it. I'm so sure going through that process will require using a computer and installing the USB driver. Getting that installed on my PC has always been a problem because my PC is Windows 10.
Hello my Friends!
I have one Le 2 x520 and after Flash some roms, whit the last "X527-ROW-5.9.028S_VR10_CUOCO92" . After "maybe" the last rom the phone by turning it on heating.
I believe I think it was done with Kernel....
Please if anyone knows something let help me.
Thank You!
mariosalex said:
Hello my Friends!
I have one Le 2 x520 and after Flash some roms, whit the last "X527-ROW-5.9.028S_VR10_CUOCO92" . After "maybe" the last rom the phone by turning it on heating.
I believe I think it was done with Kernel....
Please if anyone knows something let help me.
Thank You!
Click to expand...
Click to collapse
Why not flash it with stock ROM, go to https://devsjournal.com/download-letv-official-stock-rom.html#Le_2_Qualcomm_Stock_ROM and get the latest ROM for snapdragon
maclee4real said:
Why not flash it with stock ROM, go to https://devsjournal.com/download-letv-official-stock-rom.html#Le_2_Qualcomm_Stock_ROM and get the latest ROM for snapdragon
Click to expand...
Click to collapse
I 'm Sorry but now I could see your quote! I tried
but it has many Chinese applications and when I went to do it antutu test, after the first video he does test
go to the next test that fills the screen with pictures arrived in the middle of the screen and "Stuck" . After that go to home screen...
If has original rom backup or some other and you know how set that rom in my phone please tell me!
Thank you very much my friend!!!

New Battery Life update release from Samsung for N10f.

Here is the link and source.
https://m.gsmarena.com/samsung_gala...sing_battery_life_and_security-news-32580.php
Nice. Thanks for the heads up
Typical
I've only just gone n rooted and twrp'd arrrggghhhhh
Yes, I confirm. Bought a used Note 4 for the wife and was surprised to see it getting an update...
I didn't received the update
I have problem to install it,i have downloaded file couple of time and every time when i try to update says update faild tmobile...something like that. .
jjoeshua said:
I have problem to install it,i have downloaded file couple of time and every time when i try to update says update faild tmobile...something like that. .
Click to expand...
Click to collapse
what is youre curent version? drf1?
The problem is when I go to stock recovery I get message like this:
Dm - verify verification failed
Check your DRK first..
I must solve this to be eneble to install update..
I dont know how..
Greetings, I'm new to this forum but I've followed it for a long time in the great HTC days of installing windows on their phones. I live in France (nobody is perfect )
On from the introduction, my girlfriend and one of her friend have batteries problem with their note4 since a couple of weeks now: the phone "dies" at 34% or so reported remaining battery power. It refuses to start again unless plugged, the first days the charging animation even reported 34 remaining power but now it starts at 0%. And though I've ordered a new battery, her friend did the replacement before us and it didn't fix her problem, so I guess battery replacement won't fix mine.
So if it's not the battery, it may be the software (it may be a hardware problem on the board but I don't think it suddenly stroke two note 4) So my question is, how do we know if this upgrade is currently installed ? Is it the "build number" N910FXXU1DRF1 and/or baseband version N910FXXS1DQA1 or something else ?
Thanks in advance for your help.
jjoeshua said:
The problem is when I go to stock recovery I get message like this:
Dm - verify verification failed
Check your DRK first..
I must solve this to be eneble to install update..
I dont know how..
Click to expand...
Click to collapse
This means you've disabled encryption on the boot partition.
You'll have to flash the stock firmware via Odin.
Totally stock, no bells and whistles.
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
jtmasse said:
Greetings, I'm new to this forum but I've followed it for a long time in the great HTC days of installing windows on their phones. I live in France (nobody is perfect )
On from the introduction, my girlfriend and one of her friend have batteries problem with their note4 since a couple of weeks now: the phone "dies" at 34% or so reported remaining battery power. It refuses to start again unless plugged, the first days the charging animation even reported 34 remaining power but now it starts at 0%. And though I've ordered a new battery, her friend did the replacement before us and it didn't fix her problem, so I guess battery replacement won't fix mine.
So if it's not the battery, it may be the software (it may be a hardware problem on the board but I don't think it suddenly stroke two note 4) So my question is, how do we know if this upgrade is currently installed ? Is it the "build number" N910FXXU1DRF1 and/or baseband version N910FXXS1DQA1 or something else ?
Thanks in advance for your help.
Click to expand...
Click to collapse
My note 4 was going through this exact issue.
You'll need either a brand new battery, or you'll have to do a full format and reinstall whatever software you had prior.
ninjasinabag said:
This means you've disabled encryption on the boot partition.
You'll have to flash the stock firmware via Odin.
Totally stock, no bells and whistles.
Click to expand...
Click to collapse
Can you explain me a little more about that encryption on the boot partition.
First I was download official stock firmware for my model sm-n910t T-Mobile, than flash it try Odin and the problem is still stay Odin didn't change nothing. I was havin an OTA update that i couldn't install because of this DM- verify verifications failed.
So I download Smart Switch and through that program install the latest update that was realised this year with security patch from August I think it's Baseband version with N910TUVU2EQI2, but still problem is stay.
Do I need something more to do in Odin or what?
jjoeshua said:
Can you explain me a little more about that encryption on the boot partition.
First I was download official stock firmware for my model sm-n910t T-Mobile, than flash it try Odin and the problem is still stay Odin didn't change nothing. I was havin an OTA update that i couldn't install because of this DM- verify verifications failed.
So I download Smart Switch and through that program install the latest update that was realised this year with security patch from August I think it's Baseband version with N910TUVU2EQI2, but still problem is stay.
Do I need something more to do in Odin or what?
Click to expand...
Click to collapse
Honestly, I can't tell you more than I already have.
DM-verity (encryption) has to be active for you to be able accept an update.
I don't know why it's failing for you, can't fix it either.

Categories

Resources