Well, my SM-T700 Tab S 8.4 Wi-Fi wants some Lollipop. I wanted to know, given that I am from Portugal, can I flash the other region's ODIN 5.0 ROM without having to perform a factory reset? Because I don't want to reset it.
Do I have to reset anything to install 5.0?
You can flash any other region, no problem there
A normal Odin flash would not erase data.
Some people have mentioned that they perceived slowness or lag after upgrade to Original Samsung lollipop, which went away with a factory reset. Personally, I only bought my tab recently, and I didn't mind resetting with lollipop. So I did it for peace of mind.
I suspect a lot of this reported lag is imaginary; and most or all can be got rid of by wiping cache or data *on the lagging app* specifically, and not the whole tablet. (Also,it's hard to track down for these reports what they had installed before flashing lollipop. There's a lot of variables involved )
Then again, if you don't want to reset, it might be a sign you don't have a good enough backup system in place. Imagine you lose your tab tomorrow. What would happen then?
Sent from my SM-T700, running Swiss 5.0.2.
Ps: I will probably flash the Saudi rom that arrived yesterday... it has an international base XXU1 with newer build. Or wait for a European rom on the same base. It really doesn't matter much which CSC is involved, AFAIK
EDIT: typo fix
just upgraded to 5.0, all samsung apps kept crashing, but after rooting with CF Autoroot + TWRP and wiping all caches, it works flawlessly.
fred_be9300 said:
You can flash any other region, no problem there
A normal Odin flash would not erase data.
Some people have mentioned that they perceived slowness or lag after upgrade to Original Samsung lollipop, which went away with a factory reset. Personally, I only bought my tab recently, and I didn't mind resetting with lollipop. So I did it for peace of mind.
I suspect a lot of this reported lag is imaginary; and most or all can be got rid of by wiping cache or data *on the lagging app* specifically, and not the whole tablet. (Also,it's hard to track down for these reports what they had installed before flashing lollipop. There's a lot of variables involved )
Then again, if you don't want to reset, it might be a sign you don't have a good enough backup system in place. Imagine you lose your tab tomorrow. What would happen then?
Sent from my SM-T700, running Swiss 5.0.2.
Ps: I will probably flash the Saudi rom that arrived yesterday... it has an international base XXU1 with newer build. Or wait for a European rom on the same base. It really doesn't matter much which CSC is involved, AFAIK
EDIT: typo fix
Click to expand...
Click to collapse
so saudi arabia has the ota faster than uk?
Related
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
chrowley said:
my galaxy grand continue to reboot, i even flash the stock 4.1.2 and 4.2.2 firmware but still the phone reboots, it only reaches the wifi setup, then it restarts, please help.
Click to expand...
Click to collapse
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
ashwin77sgg said:
The information provided by you is not sufficient.There are some points i would like to know about.
Have u rooted your device?
Are you flashing through ODIN?
ROM version?
Did you make data wipe/ cache wipe before flashing over a previous firmware?
There are many threads associated with this.So please take a look over that.If you don't find answer then we are here to help you
Click to expand...
Click to collapse
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
chrowley said:
yes sir rooted, i flash the firmware through odin, then i figured out that i have a backup so i restore it and its a yes it starts, , but the problem is sometimes it reboots and the screen is blinking sometimes, any solution for this sir? thanks in advance
Click to expand...
Click to collapse
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
ashwin77sgg said:
Thanks for Calling me "Sir". But seriously no need to say it. Say it to real developers.
Now coming to the topic,
For your information,keep in mind that when u flash the Official firmware through ODIN, You loose the root access.
Don't restore any backup. Just flash through ODIN. After flashing Wipe Cache and Data wipe is recommended too.
To gain the root access again you need to flash recovery from ODIN.
Other members looking at this this thread please correct me if i am wrong .I still not getting which backup the guy is talking about.
Click to expand...
Click to collapse
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
chrowley said:
oh sorry sir, i'll make it clear, my last firmware is 4.2.2 and my rom is GENNEXT, but when i encounter the problem, i tried to go back and flash the 4.1.2 stock firmware, then later i discovered that i have a backup from my previous rom(GENNEXT running 4.2.2 firmware) so i flash again the 4.2.2 stock firmware and flash the philz touch recovery, wipe data/factory reset, wipe cache and wipe dalvik cache then restore the back up, then my phone is restored but theres another problem sometimes the screen blinks and the phone reboots in a few minutes after the startup.
Click to expand...
Click to collapse
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
ashwin77sgg said:
OK. Then it may be the problem with your GENNXT ROM cause the problem occured after restoring Backup.Try the fresh install of latest build of GENNXT rom.
Click to expand...
Click to collapse
i already tried it sir but it didnt solve the problem, it passes the setup but after a few minutes the phone reboots.
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
naufalhadyan said:
You might want to try one of the AOSP-based ROMs (CM11/Slimkat/Carbon/Omni/ProBAM) and see if it fixes the issue. If it still reboots even after installing one of those ROMs, then you probably has a faulty hardware. If it stops rebooting,then you probably has a corrupted installation of stock firmware...
Faulty hardware = get it to a service center, but be prepared to pay some bucks because you have already lost your warranty...
Corrupted stock firmware = try to flash the firmware again via Odin but DON'T RESTORE ANY BACKUP. If it still reboots, redownload the firmware package and reflash.
I'm not an expert, but I figured that your phone is already unusable by constant rebooting... let's just solve it by trial and error.
Click to expand...
Click to collapse
This is probably the best explained and most direct definition of what to do and what may be happening with our ever-rebooting Grands.... Thank you!!!
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
victorsmarotta said:
Had to create an account to thanks naufalhadyan
I was running on LineAgeOS 13.0 for a while until yesterday, when I went to install some random play store app and it crashed then went on a infinite rollercoaster with absolutely no fun making loops every time it got of the boot animation, did a factory reset, on the 2nd or 3rd app it crashed and looped, flashed another .zip with the rom, same, installed an RRemix on the same version (I like the 6) and when installing another random playstore it crashed the same way, now i'm on a AOSP 6.0 flashed from the recovery and so far i've been downloading the entire play store (just for kicks) and its smooth.
I don't use come to this troubleshooting section but on the last 24 hours there were some major bugs regarding endless loops, maybe a play store update came bugging our grand duos'? Is that even possible?
Click to expand...
Click to collapse
Even iam facing the same issue
phone reboots automatically and doesnt even start... infinite bootloop. Was working fine and suddenly this issue came up from nowhere(past 2 weeks) ..
Iam using Resurrection rom 5.7.4 (Marshmallow)
Damn I was on AICP 11, when this exact strange bootloop problem occurred for no rhyme and reason. I know the hardware is fine, the issue arises from installing apps from playstore, the moment it goes beyond a certain app limit in the device, it will start endless bootloop, I am sure this is Google's doing. Anyways this is not a hardware issue and I know more people will be coming here looking for answer to this issue. I have tried both the opengapps and deltagapps, same behaved this way, it never happened before and lately google have introduced one other app which is google's android instant app that will sit in your device, even though you need it not not. very well google for using our precious internal data to around 500Mb to 1Gb.
formating data partition solves this issue, temporarily but you lose your apps and data.
I had successfully avoided this issue when I stopped installing more apps on my device, It took me 2 tries and I found a perfect balance of 4-5 apps, it came crashing again when I tried installing the 7th app.
I don't know if other ROMs will be able to handle this bug, but I know it's time for me to look for another ROM, I was happy with AICP 11, for more than a year. Sad.
Reading about this issue, I came to know this is prevalent on all CM marshmallow based ROMs. So, going to flash Nougat or kitkat or the stock ROM should probably fix this.
Try a new battery.
I decided to un-root and push the Lollipop update today, but it took all day thanks to alot of issues. I figured I would start this thread to help others along with upgrading from KitKat.
So alot of the tutorials you will come across for un-rooting and flashing back to stock using ODIN, so your phone will update, then rooting Lollipop so you can push custom ROMS are INCORRECT. After updating to Lollipop, alot of tutorials said to re-flash the stock Lollipop firmware, then immediately flash CF-Auto-Root and then TWRP Recovery. This is WRONG, for two reasons. Firstly, the .tar file used for flashing Lollipop STOCK is the INCORRECT file. I visited FIVE tutorials and every time I would get Force Closes or get stuck in bootloop, this is because if you watch carefully your phone will name itself NOTE 4 instead of 3 by default after flashing firmware from the links. I didnt catch on to what was going on for over 5 hours as I tried again and again with different methods and then following instructions Step-by-Step all unsuccessfully until it hit me. ALL OF THE LINKS ARE POINTING TO THE WRONG FIRMWARE, instead of flashing Note 3 Firmware, you flash Note 4 Stock Lollipop Firmware, which as you can imagine, causes SERIOUS issues with your phones system.
To fix this problem, find the KitKat NF9 4.4.2 Firmware and flash that, then allow your device to update ITSELF to Lollipop VIA official T-Mobile OTA. This is what worked for me. After updating, then I simply use CF-Auto-Root and then TWRP flashes in NORMAL FASHION, allowing restarts IN BETWEEN FLASHES, clearing cache/dalvik after each install, and allowing 10 mins of settle time after every boot. Then I installed a Custom ROM and Mods, and now it all works perfectly.
Let me know if this helps or if you have experienced similar issues.
What are the links to all these incorrect firmwares?
Posting the links would be more informative than suspicions.
Pp.
wallacengineering said:
I decided to un-root and push the Lollipop update today, but it took all day thanks to alot of issues. I figured I would start this thread to help others along with upgrading from KitKat.
So alot of the tutorials you will come across for un-rooting and flashing back to stock using ODIN, so your phone will update, then rooting Lollipop so you can push custom ROMS are INCORRECT. After updating to Lollipop, alot of tutorials said to re-flash the stock Lollipop firmware, then immediately flash CF-Auto-Root and then TWRP Recovery. This is WRONG, for two reasons. Firstly, the .tar file used for flashing Lollipop STOCK is the INCORRECT file. I visited FIVE tutorials and every time I would get Force Closes or get stuck in bootloop, this is because if you watch carefully your phone will name itself NOTE 4 instead of 3 by default after flashing firmware from the links. I didnt catch on to what was going on for over 5 hours as I tried again and again with different methods and then following instructions Step-by-Step all unsuccessfully until it hit me. ALL OF THE LINKS ARE POINTING TO THE WRONG FIRMWARE, instead of flashing Note 3 Firmware, you flash Note 4 Stock Lollipop Firmware, which as you can imagine, causes SERIOUS issues with your phones system.
To fix this problem, find the KitKat NF9 4.4.2 Firmware and flash that, then allow your device to update ITSELF to Lollipop VIA official T-Mobile OTA. This is what worked for me. After updating, then I simply use CF-Auto-Root and then TWRP flashes in NORMAL FASHION, allowing restarts IN BETWEEN FLASHES, clearing cache/dalvik after each install, and allowing 10 mins of settle time after every boot. Then I installed a Custom ROM and Mods, and now it all works perfectly.
Let me know if this helps or if you have experienced similar issues.
Click to expand...
Click to collapse
Yes, could you post the links that you say have the issues?
AxAtAx said:
Yes, could you post the links that you say have the issues?
Click to expand...
Click to collapse
Sure thing guys, A good example would be this guide here: http://forum.xda-developers.com/showthread.php?t=2672393
Really great guide, makes everything nice and easy, until you get past flashing the Lollipop Stock firmware VIA THIS LINK: http://www.sammobile.com/firmwares/database/SM-N900T/ in one of the very first seps.
If you download the N900TUVUFOB6 (Lollipop) Firmware and flash it, you will get alot of random force closes once the ROM boots and settles. If you pay attention after flashing, you will note the device name defaults to Note 4, and there's your clue.
I still cant believe Ive been working on this phone for the past 13 hours trying to get everything working properly. Happily I have found a ROM I like that is INSANELY FAST AND STABLE and I've installed all the Mods that I want. All I need to do at this point is re-download all my apps and set all the settings.
wallacengineering said:
Sure thing guys, A good example would be this guide here: http://forum.xda-developers.com/showthread.php?t=2672393
Really great guide, makes everything nice and easy, until you get past flashing the Lollipop Stock firmware VIA THIS LINK: http://www.sammobile.com/firmwares/database/SM-N900T/ in one of the very first seps.
If you download the N900TUVUFOB6 (Lollipop) Firmware and flash it, you will get alot of random force closes once the ROM boots and settles. If you pay attention after flashing, you will note the device name defaults to Note 4, and there's your clue.
I still cant believe Ive been working on this phone for the past 13 hours trying to get everything working properly. Happily I have found a ROM I like that is INSANELY FAST AND STABLE and I've installed all the Mods that I want. All I need to do at this point is re-download all my apps and set all the settings.
Click to expand...
Click to collapse
I just put that stock rom on my wifes phone a few days ago, and it defaulted to Note 3 on hers. well, never mind, as you have seem to have got it rolling now.:good::good:
I must be taken crazy pills.
Pp. :what:
Can i ever unbrick my note 3
Frustrated at the moment. I've been trying to unbrick my note 3 for 2 days without any luck. I switched it off after after a week of rooting it and bang it wouldn't go past the samsung logo, it restarts itself automatically without going past the samsung logo. I've downloaded countless version of kitkat stock firmware from different sources for my sm-N900T, flashed with odin more than 10 times, followed every instruction about unbricking.
Any help would be greatly appreciated.
boofydon said:
Frustrated at the moment. I've been trying to unbrick my note 3 for 2 days without any luck. I switched it off after after a week of rooting it and bang it wouldn't go past the samsung logo, it restarts itself automatically without going past the samsung logo. I've downloaded countless version of kitkat stock firmware from different sources for my sm-N900T, flashed with odin more than 10 times, followed every instruction about unbricking.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do you have stock recovery installed and can you get to it? You might want to try wiping cache and doing a factory reset. If that doesn't fix it then maybe try downloading a stock firmware from Sammobile and flashing it with Odin. You might have have an incompatible app that was installed with a previous rom and a wipe of the Data partition might be needed. You will lose all of your data and apps though.
Next step I'd do if none of that worked would be flashing twrp and wiping data, cache and dalvik and hope...
Good luck.
Ravoz88 said:
Do you have stock recovery installed and can you get to it? You might want to try wiping cache and doing a factory reset. If that doesn't fix it then maybe try downloading a stock firmware from Sammobile and flashing it with Odin. You might have have an incompatible app that was installed with a previous rom and a wipe of the Data partition might be needed. You will lose all of your data and apps though.
Next step I'd do if none of that worked would be flashing twrp and wiping data, cache and dalvik and hope...
Good luck.
Click to expand...
Click to collapse
Thank you for your time. I flashed it with a new stock from sammobile but it's still in a boot loop state even though odin always show pass. And when I flashed it with twrp my note 3 was unable to enter recovery mode.
Hi, everyone.
As I have discussed in my two previous threads, my Samsung Galaxy Tab S 8.4 has been constantly forcing itself into a bootloop and refusing to move past the Samsung logo.
Since my last thread post, I had decided to upgrade from KitKat 4.4.2 to Marshmallow and for about a month and a half, I have not had the bootloop issue. A week or two ago, the device began going through the same bootloop issues after the screen freezes and either I force-reboot it by holding down the Power button and Volume Down button, or the device reboots itself. I have cleared the cache partition each time this happens with no successful result.
The only way I have found it to have started working again is to wipe the cache partition, factory reset the device, then wipe the cache partition again and flash the official Marshmallow ROM. So far in the past one or two weeks, I have had to factory reset this device at least five times (around two to three days after the last time it was reset) and it's just becoming a nuisance.
Is there anything that anyone could suggest that might work so that I do not have to factory reset the device and flash the ROM on such a consistent basis?
AussieMouse said:
Hi, everyone.
As I have discussed in my two previous threads, my Samsung Galaxy Tab S 8.4 has been constantly forcing itself into a bootloop and refusing to move past the Samsung logo.
Since my last thread post, I had decided to upgrade from KitKat 4.4.2 to Marshmallow and for about a month and a half, I have not had the bootloop issue. A week or two ago, the device began going through the same bootloop issues after the screen freezes and either I force-reboot it by holding down the Power button and Volume Down button, or the device reboots itself. I have cleared the cache partition each time this happens with no successful result.
The only way I have found it to have started working again is to wipe the cache partition, factory reset the device, then wipe the cache partition again and flash the official Marshmallow ROM. So far in the past one or two weeks, I have had to factory reset this device at least five times (around two to three days after the last time it was reset) and it's just becoming a nuisance.
Is there anything that anyone could suggest that might work so that I do not have to factory reset the device and flash the ROM on such a consistent basis?
Click to expand...
Click to collapse
Can i ask how you updated from kk to lp did you use oden or kies.......for me i use oden and jump to mm use updato to get a good clean rom to flash in oden.....you may have flashed a crupt file is has happened to me once.....
stinka318 said:
Can i ask how you updated from kk to lp did you use oden or kies.......for me i use oden and jump to mm use updato to get a good clean rom to flash in oden.....you may have flashed a crupt file is has happened to me once.....
Click to expand...
Click to collapse
I used Odin but skipped past Lollipop to Marshmallow (the ROM was the Official ROM from Samsung Updates). I don't think the file was corrupt as I had this problem with the tablet before I started flashing the same KitKat ROM it was originally preinstalled with, and Marshmallow later on.
AussieMouse said:
I used Odin but skipped past Lollipop to Marshmallow (the ROM was the Official ROM from Samsung Updates). I don't think the file was corrupt as I had this problem with the tablet before I started flashing the same KitKat ROM it was originally preinstalled with, and Marshmallow later on.
Click to expand...
Click to collapse
Were did you download the rom from.....
stinka318 said:
Were did you download the rom from.....
Click to expand...
Click to collapse
This website http://live.samsung-updates.com/, I believe.
AussieMouse said:
This website http://live.samsung-updates.com/, I believe.
Click to expand...
Click to collapse
Try updato and download the required rom it is fast and clean
stinka318 said:
Try updato and download the required rom it is fast and clean
Click to expand...
Click to collapse
I have already done so. It's up to date with the latest official version in my region.
AussieMouse said:
I have already done so. It's up to date with the latest official version in my region.
Click to expand...
Click to collapse
Well if update with the rom that you got from updato there would not be a problem....in my experience if a download take a long time it has a greater chance of having issues if it is a fast clean download it would be clean with no errors.
stinka318 said:
Well if update with the rom that you got from updato there would not be a problem....in my experience if a download take a long time it has a greater chance of having issues if it is a fast clean download it would be clean with no errors.
Click to expand...
Click to collapse
I don't think the issue did start with the update. If anything, flashing the ROM (combined with factory resetting) seems to temporarily fix the bootloop.
AussieMouse said:
I don't think the issue did start with the update. If anything, flashing the ROM (combined with factory resetting) seems to temporarily fix the bootloop.
Click to expand...
Click to collapse
When a download is slow it get interrupted with advertising bots and sometimes depending on were the errors happen it may have been a crupt....i had the same problem with t705y and t805y until i download it from updato now i get nothing no errors......just my experience thats all.
stinka318 said:
When a download is slow it get interrupted with advertising bots and sometimes depending on were the errors happen it may have been a crupt....i had the same problem with t705y and t805y until i download it from updato now i get nothing no errors......just my experience thats all.
Click to expand...
Click to collapse
Ah, I see! No worries, I'll download the ROM again and make sure the download isn't interrupted. Thanks for the advice! I shall let you know how it turns out.
AussieMouse said:
Hi, everyone.
As I have discussed in my two previous threads, my Samsung Galaxy Tab S 8.4 has been constantly forcing itself into a bootloop and refusing to move past the Samsung logo.
Since my last thread post, I had decided to upgrade from KitKat 4.4.2 to Marshmallow and for about a month and a half, I have not had the bootloop issue. A week or two ago, the device began going through the same bootloop issues after the screen freezes and either I force-reboot it by holding down the Power button and Volume Down button, or the device reboots itself. I have cleared the cache partition each time this happens with no successful result.
The only way I have found it to have started working again is to wipe the cache partition, factory reset the device, then wipe the cache partition again and flash the official Marshmallow ROM. So far in the past one or two weeks, I have had to factory reset this device at least five times (around two to three days after the last time it was reset) and it's just becoming a nuisance.
Is there anything that anyone could suggest that might work so that I do not have to factory reset the device and flash the ROM on such a consistent basis?
Click to expand...
Click to collapse
Well, this may not get to the root of your problem, but it's a bit of a no brainer really.
If your having to restore your device so much why not just bung twrp on it, make a device back up, literally a few minutes and if it all goes Pete Tong again, simply boot to twrp, hit restore and you're back up and running in a few minutes?
I recently flashed Nougat QB2 and it works great. I have noticed that AT&T has released security patch level updates QC2 (1st March) and QD4 (1st April) since. Does anyone know how important it is to keep up to date with security patch levels? Is it ok to stay on QB2 for a while?
P.s. I'm overseas so can't get the OTA updates
Did you flash QB2 directly from Odin? I have downloaded it but wasn't sure if using Odin was the accepted method? I am running the engineering rom now PL4 and it is very laggy and would like to update to hopefully something faster and less laggy?
Yep flashed QB2 with Odin. Certainly seems to be buttery smooth and working without issue so far.
I obtained the link here: https://forum.xda-developers.com/s7-active/how-to/g891a-android-n-offical-odin-package-t3581042
Thanks Scroob hoping someone was going to answer my question. Did you have to factory reset? Did flashing wipe the phone?
No problem,
Unfortunately yes. it does reset the phone. Smart switch definitely helps ease the pain of reinstalling all the apps but its a pain re-configuring the phone none the less.
if you update via the sdcard with the zip in recovery, and exit at the right time (you gotta be ready and quick) you can get away with not having it totally reset everything
Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!
Have you tried looking through the various posts within the forum to find your answer? I just scrolled through and found a few without searching. Exerting a bit of effort could yield amazing results, at least that's what I've had happen over my years on here
bumperjeep said:
Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!
Click to expand...
Click to collapse
My Verizon Note 4 is exactly at the same update level as yours and it is working great.
When you did the factory reset did you completely wipe all user data on both the phone and the SD card? If not I would give that a try.
I would also suggest that you not let Android restore any applications when you first start the phone after the factory reset. You could have an errant app causing problems. If it seems to work phone without any user installed apps I would then reinstall apps one by one and make sure the phone continues to work fine. It it starts to run incredibly slow again then the last app you installed is likely the culprit.
If these options don't work I would take the phone to a local Best Buy. Go to the Samsung Experience counter and talk to them. They can do a deep factory reset that will completely reinstall the firmware and thereby restore the phone to a pristine factory image.
If these options do not fix the problem you may be in the early stages of hardware failure. The Note 4 has developed a bad reputation for the motherboard slowly failing and causing progressively worse problems. That is what happened to me and the phone eventually became unusable. I finally had to contact Samsung technical support (1-800-SAMSUNG) and they had me send the phone in. They replaced the motherboard and other printed circuit boards. It did cost me $70 since the phone was out of warranty, but it works like new now.
Good luck. The Note 4 is still a great phone and worth the effort (and possibly cost) to get it fixed.
Can anyone confirm that Foxfi tethering works (not usb) on a non rooted Verizon Note 4 phone (marshmallows 6.0.1) with the following security update installed (mmb29m.n910vvrs2cqe1)
bumperjeep said:
Hi,
I've taken all of the OTA updates up until June 2017. I have 6.0.1, May 1st 2017 Security Path Level and Baseband Version of N910VVRS2CQE1, Build Number of MMB29M.N910VVRS2CQE1.
Can I root and use a version of CM or go back to Kit Kat 4.4.4?
I'm hoping that I can still get some play out of the phone, it's incredibly slow. I've done a factory restore once or twice as well.
Thanks!
Click to expand...
Click to collapse
Yeah im thinking the problem is this phone came just packed with bloatware nobody uses a third of the garbage that came preloaded (200+ apps you use 10 of). You can root but you have to downgrade with odin back 5.1.1. bpa1 . you could also try a less invasive approach and just disable the bejeezus out of pretty much anything allowable there is an easy disable option that lets you do it in batches from the apps drawer. I did this to root the phone given the unstable root method.