Hey guys, been a while since I've been here.
Currently, I'm running stock android 6.0.1 (N910FXXU1DPB1) on my Note 4 (Snapdragon).
I flashed this via Odin (because back then it wasn't released in my country yet). Did the usual, clean reset and when i flashed there were no problems (besides meh battery time). But since a week or two I'm having a lot of problems, a lot of random reboots, reboot time is way too long, battery drainage is awful and random freezes. A lot of these problems occur when using snapchat, not sure why.
So now I'm wondering what is the most stable ROM around. Battery life and smoothness are most important to me. At this point, I don't really care if it's a custom ROM or stock. With my old phone (S3) i had a lot of problems after i started running custom ROMs so I'm hoping you guys have some options where this won't happen.
Thanks in advance, Sam
BTW: Sorry for my bad English, it's not my main language.
Another weird thing happened. Just installed TWRP (once again via Odin), but when I reboot into recovery, I first get the message 'installing system update', then it says 'no command' and then it reboots in Android Recovery. Any ideas how to solve this?
Note 4 sucks after this MM update it is worst than any other small budget phone.
anasrizvi said:
Note 4 sucks after this MM update it is worst than any other small budget phone.
Click to expand...
Click to collapse
So you'd recommend going back to stock kitkat?
SamC95 said:
Hey guys, been a while since I've been here.
Currently, I'm running stock android 6.0.1 (N910FXXU1DPB1) on my Note 4 (Snapdragon).
I flashed this via Odin (because back then it wasn't released in my country yet). Did the usual, clean reset and when i flashed there were no problems (besides meh battery time). But since a week or two I'm having a lot of problems, a lot of random reboots, reboot time is way too long, battery drainage is awful and random freezes. A lot of these problems occur when using snapchat, not sure why.
So now I'm wondering what is the most stable ROM around. Battery life and smoothness are most important to me. At this point, I don't really care if it's a custom ROM or stock. With my old phone (S3) i had a lot of problems after i started running custom ROMs so I'm hoping you guys have some options where this won't happen.
Thanks in advance, Sam
BTW: Sorry for my bad English, it's not my main language.
Click to expand...
Click to collapse
I use and have been using Alexndr's ROM's for ages! They are reliable have plenty of options (root/no root, odexed/deodexed, xposed or not) ... he regularly updates and sorts out peoples' problems (although I have never had one) and produces a very stable ROM.
His instructions are clear and easily understood and he knows what he is doing! My favourite ROM maker ... Thanks Alexndr!!
robmeik said:
I use and have been using Alexndr's ROM's for ages! They are reliable have plenty of options (root/no root, odexed/deodexed, xposed or not) ... he regularly updates and sorts out peoples' problems (although I have never had one) and produces a very stable ROM.
His instructions are clear and easily understood and he knows what he is doing! My favourite ROM maker ... Thanks Alexndr!!
Click to expand...
Click to collapse
Thanks for you reply.
Seems like a nice ROM, would want to flash it, but seems like I'm not going to be able to flash new ROMs (due to the problem described above.
I had the same problem. you must have the newest version of odin.
DrQuestion said:
I had the same problem. you must have the newest version of odin.
Click to expand...
Click to collapse
Seriously? Is it that simple lol? I'll try that, thanks.
EDIT: Turned out it wasn't that simple, got the message 'There's no PIT partition.'
anasrizvi said:
Note 4 sucks after this MM update it is worst than any other small budget phone.
Click to expand...
Click to collapse
I've been running Marshmallow on my N910C since it was released for my device, and I haven't experienced any major problems with it. Other than not getting the official OEM spare battery to charge correctly on it. Everything is work just fine.
I've been running the MM PaulPizz Rom for a few days and it's been rock solid so far. Not a single crash or error.
SamC95 said:
Another weird thing happened. Just installed TWRP (once again via Odin), but when I reboot into recovery, I first get the message 'installing system update', then it says 'no command' and then it reboots in Android Recovery. Any ideas how to solve this?
Click to expand...
Click to collapse
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download
aaron74 said:
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download
Click to expand...
Click to collapse
Thanks for your reply.
Alright man, I will try that tomorrow.
I think the download should be okay, downloaded V3.12.3 a few hours ago, or do I need a different one?
And should I also do this if I get the message that there's no PIT partition?
Thanks for your help, I'll let you know if it works or not.
SamC95 said:
Thanks for your reply.
Alright man, I will try that tomorrow.
I think the download should be okay, downloaded V3.12.3 a few hours ago, or do I need a different one?
And should I also do this if I get the message that there's no PIT partition?
Thanks for your help, I'll let you know if it works or not.
Click to expand...
Click to collapse
I always use 3.11.1 straight from Sam mobile site. Here http://dl.sammobile.com/Odin3-v3.11.1.zip
Never had a problem with it.
Stock ROM's all the way.
I've used KK, LL and MM. After upgrading to MM (by mistake) and using it for 2 weeks, had to throw it away! MM is the worst case ever! I've went even back to KK, used about 2 days and went finally for 5.1.1 - best case ever! No lag, no "app stop working", no delay (which with MM was about 3 secs between opening closing apps). But, the 5.1.1 has a little distress about battery drain (about 5% more than KK or MM). Is the only thing is keeping LL for being best version. If you rollback from MM to LL or KK, you MUST untick Auto Reboot! Just let the flash go till the end and then take the battery out; put it back, start with recovery and wipe everything prior booting normally. And for the downgrade you have to use:
1. from MM to LL - Odin 3.11
2. from MM to KK - Odin 3.09
After trying myriad of roms(Almost all roms from Snapdragon section) + kernels, I prefer Stock rom for it's batterylife + stable performance. I haven't rooted after returning to stock. But i will return some sort of custom rom soon as my phone looks so boring without ported apps, multi dpi compatible apps, etc. If u prefer stable performance move to pure stock, If u need assortment of features use one of the ported note7/S7 roms, If u want slick and fast roms use AOSP/CM based roms but as far my experience goes they are not much stable while compared to touchwiz.
Currently running latest MM stock on 910G.
Stonewolf said:
Stock ROM's all the way.
I've used KK, LL and MM. After upgrading to MM (by mistake) and using it for 2 weeks, had to throw it away! MM is the worst case ever! I've went even back to KK, used about 2 days and went finally for 5.1.1 - best case ever! No lag, no "app stop working", no delay (which with MM was about 3 secs between opening closing apps). But, the 5.1.1 has a little distress about battery drain (about 5% more than KK or MM). Is the only thing is keeping LL for being best version. If you rollback from MM to LL or KK, you MUST untick Auto Reboot! Just let the flash go till the end and then take the battery out; put it back, start with recovery and wipe everything prior booting normally. And for the downgrade you have to use:
1. from MM to LL - Odin 3.11
2. from MM to KK - Odin 3.09
Click to expand...
Click to collapse
Using Odin 3.11 to downgrade from MM to KK works just fine. I just did 2 days ago.
I had errors with 3.11; once changed to 3.09 worked like a charm. I've posted from my experience. Anyway, good to know other opinions and good to know that works either way (maybe my system had some conflict with vs. 3.11). However, that downgrade was done only to my first device, not the second one. I still keep MM on my second N4.
Stonewolf said:
I had errors with 3.11; once changed to 3.09 worked like a charm. I've posted from my experience. Anyway, good to know other opinions and good to know that works either way (maybe my system had some conflict with vs. 3.11). However, that downgrade was done only to my first device, not the second one. I still keep MM on my second N4.
Click to expand...
Click to collapse
Have you tried 3.12? It's the only one that worked for me.
back to lollipop .......... one of the best Note 4 ROM ever build ...........
Been using Nameless ROM V7 ............
aaron74 said:
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download
Click to expand...
Click to collapse
This did the trick, thanks a lot! I finally got to flash TWRP and ended up installing Alexndr ROM (thanks for the tip @robmeik) but sadly I'm still having random reboots
Related
I am starting this thread, since it seems a lot of users are posting their problems in the Development section. It has become confusing for the other users who are new to this website to post thier queries in other thread. This thread will generally be answered by experienced users and we will continue to help as long as you guys do not create a mess here -:d
My phone have only 11gb internal memory. Is it normal? I though its 16gb phone
Crazy Ushi said:
My phone have only 11gb internal memory. Is it normal? I though its 16gb phone
Click to expand...
Click to collapse
Ya thats normal 11 gb for user...around 2 gigs is for apps...plus rest for system..
New user of a Galaxy Note, I remarked a strange thing with the way the Galaxy Note manage the wifi connexion. At my home, I've one Wifi network. One access point is into my desk and the second into my living room. When I connect my Note on the wifi into my desk room, I got the Wifi at 100% (of course as I'm at 2m of the antenna ;-) ). Now, if I move from my desk to my living room, the Galaxy Note still remain connected to the Wifi of my desk room witch is not good because I lost the 90% of my wifi power.
My question is now: Does it exist any solution to have my Smartphone switching automatically depending on witch room I am ?
For example, with my iPhone and/or iPad, both device automatically use the more powerfull signal (the one of my desk room when I'm in and as soon as I'm more closer of the antenna of my living room it switch to this antenna).
Last information, same problem with a Galaxy S2.
Is it a limitation of Android or a "specificity" of Samsung devices ?
Thx for your feedback !
Force shutdown every time I runs any application
Hello, newcomer's here. I've rooted my N7000 & installed stable CM 10.1.3 ROM, but I can't run any apps more than 10 minutes or less.
When I runs an app (especially games), even when the battery was 100%, the device will force shut. When I immediately turned it on after the
force shutdown, it will force shut at cynogenmod boot screen, but sometimes when I managed to (barely) get in, the battery bar indicates there's
only 1% charge left. So, I thought I should try BatteryCalibration, but still the same issue. Then I thought maybe it's the ROM, so I
installed the updated nightly version CM 10.2 ROM, and the same issue occurs again. I've searched in "All Forums" and found the idea on "wipe
battery stats" in recovery after install new ROM, but I can't find that option in CWM. Then, I read the idea of wiping battery stats has no effect at
all in the battery issue (http://forum.xda-developers.com/showthread.php?t=2256038). So, I flashed the stock ROM back and I didn't
face any issue on force shut and rapid battery drain anymore. But I've found a similar situation faced by other member in this thread
http://forum.xda-developers.com/showthread.php?t=2506468. Do I have to go that far just for remedy?
Is there any solution for this? Because I like custom ROM than using the stock, it's fast and swift RAM usage. Thanks for any advice on this.
Did you try a different battery to start with.?
my N7000 (factory firmware 4.1.2) was in charging, then suddenly its turn off automatically, then i switch on it, it stuck at boot screen..
cannot go recovery mode,
can go download mode with android logo, not ' ! " logo
flash back factory firmware, ordin stuck at boot.bin..FAIL
help
nokiamodeln91 said:
Did you try a different battery to start with.?
Click to expand...
Click to collapse
Nope, I don't have any spare battery for my device. Just bought it 2 weeks ago.
I'll consider your advice. Thanks.
N7000 screen
Hi, I'm not sure wether this is the right thread, but it is a question and I do need an answer..
Does anyone know wether the display of N7000 is the same as SHV-E160L?
I have one N7000 with a broken glass and LCD, and can get hold of a SHV-E160L for same price as the display only.. Would there be a way to frankenstein the LTE possibilities of SHV-E160L into the N7000?
Hope someone has hands on experience with this.. At least the screen part, since it is the main reason for the project..
LTE would be the icing on the cake..
Not sure of the screen but LTE is the compatibly dependent on SOC. The SHV has a snapdragon processor and Exynos doesn't have.
how to disable custom rom flashing twrp recovery? and just stay on cwmr?
First post ever on forum, sorry if i did something bad
You really can't. If the custom rom (may be you are referring to kitkat) comes only with twrp, you need to live with it till some kernel Dev makes a kernel with cwm compatible 4.4.
nokiamodeln91 said:
You really can't. If the custom rom (may be you are referring to kitkat) comes only with twrp, you need to live with it till some kernel Dev makes a kernel with cwm compatible 4.4.
Click to expand...
Click to collapse
Ah, then i get it, thanks for your help!!
Need Help...Plz
nokiamodeln91 said:
You really can't. If the custom rom (may be you are referring to kitkat) comes only with twrp, you need to live with it till some kernel Dev makes a kernel with cwm compatible 4.4.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559371
Please help me with my problem if you can. My mobile is seen by odin but i am unable to find a Stock Jellybean Rom for N7000, i.e either .tar or .md5 file in internet.
lord_pmvk said:
http://forum.xda-developers.com/showthread.php?t=2559371
Please help me with my problem if you can. My mobile is seen by odin but i am unable to find a Stock Jellybean Rom for N7000, i.e either .tar or .md5 file in internet.
Click to expand...
Click to collapse
Then install philz kernel using odin. Then boot into recovery. Flash any custom rom.
I now got another question, i have the 4.4.1 alysum omni and i just can't get the "standard email"(the one that is original on stock rom) app working, its giving me messages saying i cant login, i took it out from the "removed apks .rar file" and just installed it on new fresh rom, everything else works but not that.. what can the problem be?
its chewing and chewing for like 5 mins when i press next for login.. and then gives error "cant sign in to server"
thanks
Ate you talking about the Samsung Email app? Then it won't work without a TW framework.
My phone got stuck at boot screen and unable to go into recovery mode but can go into download mode.
Should i flash back stock gingerbread via odin? Do i need to i stall any kernel? Pls help.
My phone got stuck at boot screen and unable to go into recovery mode but can go into download mode.
Should i flash back stock gingerbread via odin? Do i need to i stall any kernel? Pls help.
shokokatana said:
My phone got stuck at boot screen and unable to go into recovery mode but can go into download mode.
Should i flash back stock gingerbread via odin? Do i need to i stall any kernel? Pls help.
Click to expand...
Click to collapse
Flash philz .tar file from download mode and you should have working recovery
Sent from my GT-N7000 using Tapatalk
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
We have two versions of safestrap and each one works with a different OS.
1.Safestrap 3.71: that works ONLY with jellybean roms. Use it (If your phone says "4.3 MI9, MJ5, or NB4" in your "about phone" in settings) to flash any jellybean rom. Read the title of any rom you're attempting to flash. If it says "4.4.2 KK or Kitkat or NC2" then stay away.
2. Safestrap 3.72/3.75 ([emoji118] this is recommended) that works ONLY with Kitkat roms. Use it (If your phone says "4.4.2 NC2" in your "about phone" in settings) to flash any Kitkat/NC2 rom. Read the title of any rom you're attempting to flash. If it says "4.3 jellybean or JB" then stay away.
K-alz said:
We have two versions of safestrap and each one works with a different OS.
1.Safestrap 3.71: that works ONLY with jellybean roms. Use it (If your phone says "4.3 MI9, MJ5, or NB4" in your "about phone" in settings) to flash any jellybean rom. Read the title of any rom you're attempting to flash. If it says "4.4.2 KK or Kitkat or NC2" then stay away.
2. Safestrap 3.72/3.75 ([emoji118] this is recommended) that works ONLY with Kitkat roms. Use it (If your phone says "4.4.2 NC2" in your "about phone" in settings) to flash any Kitkat/NC2 rom. Read the title of any rom you're attempting to flash. If it says "4.3 jellybean or JB" then stay away.
Click to expand...
Click to collapse
basicaly what he said.. and since you said you did dynamic kat and alliance.. sounds like you are on the nc2 with Kitkat..
So, best bet is going to be make sure you have ss 3.75 and only flash the kitkat roms.. Dynamic kat, Alliance, Tweaked, Firekat, and you should be fine.. just dont try and flash any that are JB
From my Fired-up Note Pro 12.2!
Thank you. A combo of Android version AND baseband at the end?
Are the version numbers I'm looking for, a combination of the Android version (4.4.2) and the end of the Baseband number (NC2)
Basically I tried everything and your suggestions should very very suspiciously like everything I've done But.. I will give it one more shot.
Any possibility of SafeStrap 3.72 would work as opposed to 3.75 not working?
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
Version 4.42. I'll give everything a shot here although, I've tried all of this but maybe I've missed something. Thank you for responding.
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse
bodycode said:
Are the version numbers I'm looking for, a combination of the Android version (4.4.2) and the end of the Baseband number (NC2)
Basically I tried everything and your suggestions should very very suspiciously like everything I've done But.. I will give it one more shot.
Any possibility of SafeStrap 3.72 would work as opposed to 3.75 not working?
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
Version 4.42. I'll give everything a shot here although, I've tried all of this but maybe I've missed something. Thank you for responding.
Click to expand...
Click to collapse
yeah if you are seeing 4.4.2 and nc2 you are on KK.. just make sure you are on 3.75 and all should be ok with flashing..
if for some reason it is borked,, go down to carls thread for odin files and how to odin back to stock nc2 and then start over and you should be fine
From my Fired-up Note Pro 12.2!
NO good. 3.75/stock slot/Alliance ROM fails.
Same ****. Black screen.
David Sanborn said:
I'm an android ROM newbie, but an old computer geek from way back in the 80's, so I do have some kind of understanding. I own an ATT Note 3.
I've experienced only minor problems with the two main ROM flash tools, that is, Safestrap 3.x and Odin 3.x but that's probably my fault and they don't crash. But Safestrap? Oy vay! That works also, but in the final boot, black screen thereafter, after booting from ANY slot, whether it be stock slot of other slots. Thank God for the backup function and Odin.
But I digress. Right in the beginning of my flashing Odyssey, everything worked fine! Flashed Alliance ROM no problem, as well as Dynamic Kat.
Oh yeah. Confused about all those two letter abbreviations, there's no abbreviation key here on the forums?
I tried the other ROMS in the Note 3 Rom sections and stuck wit that, but then, under Safestrap, the machine would reboot to black screen! No matter what I did, wiping, rooting (of course), re-installing different versions of SafeStrap, from early 3.x versions to 3.75, nothing! Odin gets my machine back to it's (I THINK) original state.
Badly confused. Knox is fine at 0x0. Don't know how to move forward. I would like to continue to try different ROMS but the same thing keeps on happening. Hope someone can help me. If anyone wants some kind of log output, I can do that (just tell me how and where).
Thanks
Click to expand...
Click to collapse
NO good. 3.75 fails!
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
warfenix said:
Sounds like maybe your flashing kit kat over jellybean or the other way around. Make sure if you have going to different android versions you flash the right Odin files each time. And install the right right version of safe strape. Or you get black screens
Click to expand...
Click to collapse
AFter creating another slot and wipe, system mounting errors.
System mount errors all over the place after creating another slot, and installing Alliance. What's going on here? Something's really screwed up.
e: unable to mount '/system'
e: unable to mount '/systemorig'
over and over again
Can't check permissions after FActory reset. Please boot rom and try again after you reboot into recovery.
David Sanborn said:
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
Click to expand...
Click to collapse
David Sanborn said:
3.75 and Alliance utterly fails into black screen. Safestrap reboot screen does this, but the other button (restore) gets me back to all the other buttons. Stock slot has size of zero partition size after alliance installation.
Click to expand...
Click to collapse
I would simply restore back to mj5 and start over. I did this last night simply to reset my phone cause I flash way to much lol. I would give that a try though. Thread is in the general section
How to restore to Mj5?
How do I downgrade to Mj5 from KK4.2?
Thanks
warfenix said:
I would simply restore back to mj5 and start over. I did this last night simply to reset my phone cause I flash way to much lol. I would give that a try though. Thread is in the general section
Click to expand...
Click to collapse
David Sanborn said:
How do I downgrade to Mj5 from KK4.2?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559715
I know what your problem is brother. This same crap happened to me. To a T! For some reason when u wipe system in safesteap, it wipes everything out. EVERYTHING. except data. I learned the hard way,like u. So when u flash roms, don't wipe system, only factory reset. I wipe it 3× every time. Then install your Rom. You will b fine. I haven't had one problem ever since I stopped wiping system. And no random reboots or anything, Roms now flash, and boot as they should. Hope this helps.
David Sanborn said:
How do I downgrade to Mj5 from KK4.2?
Thanks
Click to expand...
Click to collapse
Dude. If you're on NC2 then don't ever do the MJ5. It'll give the same problem. Just Odin the first four files from this thread http://forum.xda-developers.com/showthread.php?t=2838117 then root with towelroot/install busybox (make sure to install it from within the app as well) then install ss 3.72 or 3.75 then start flashing Kitkat roms.
K-alz said:
Dude. If you're on NC2 then don't ever do the MJ5. It'll give the same problem. Just Odin the first four files from this thread http://forum.xda-developers.com/showthread.php?t=2838117 then root with towelroot/install busybox (make sure to install it from within the app as well) then install ss 3.72 or 3.75 then start flashing Kitkat roms.
Click to expand...
Click to collapse
True but I think his problem is wiping system when he installs roms. If he's still not able to boot up right then ya he needs to use Odin and those files to get up and running again.
I just wish it was like the note 2. With unlocked bootloader and real twrp recovery.
zounduser said:
True but I think his problem is wiping system when he installs roms. If he's still not able to boot up right then ya he needs to use Odin and those files to get up and running again.
I just wish it was like the note 2. With unlocked bootloader and real twrp recovery.
Click to expand...
Click to collapse
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
K-alz said:
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
Click to expand...
Click to collapse
Oh I agree. I've had to do it. I'm saying going forward so it doesn't happen again.
4 files in odin flash, done that 15 times.
I've flashed Odin stock COUNTLESS times! When I go back to flash kitkat ROMS, same **** all over again. Unbelievable. I'm at my wits end. My phone DOES boot with the Odin files. But when flashing anything else with safestrap, black screen again.
K-alz said:
These four files are as easy as it gets. Literally, put phone into download mode, load files to their respective slots then hit start. That's all. Saves you much bullshiz
Click to expand...
Click to collapse
David Sanborn said:
I've flashed Odin stock COUNTLESS times! When I go back to flash kitkat ROMS, same **** all over again. Unbelievable. I'm at my wits end. My phone DOES boot with the Odin files. But when flashing anything else with safestrap, black screen again.
Click to expand...
Click to collapse
You used the files in the thread I gave you a couple of posts back and it didn't work? Man I hope you still have your warranty. Just flash back to stock and take your phone to the AT&T warranty center and make up and issue with your phone and tell them that you can't deal with your phone anymore and get you a new phone. They believe about anything. If that didn't work then head to bestbuy if there is one by you and ask them to reflash the system for you (that's of course after you flash back to stock).
Not a block screen on Odin and no trips.
Did I mention Odin works fine? Knox is not tripped. All is well right after Odin upload to phone in Download mode. It's only when I flash anything that blackscreen curses me again. heh heh.
K-alz said:
You used the files in the thread I gave you a couple of posts back and it didn't work? Man I hope you still have your warranty. Just flash back to stock and take your phone to the AT&T warranty center and make up and issue with your phone and tell them that you can't deal with your phone anymore and get you a new phone. They believe about anything. If that didn't work then head to bestbuy if there is one by you and ask them to reflash the system for you (that's of course after you flash back to stock).
Click to expand...
Click to collapse
Hi Guys,
Hope someone a bit more clued up than myself can clarify my questions or guide me..
I've done some searching, but am not 100% confident.
So, I have a I9305 running a Boeffla Kernel 5.2. If I recall correctly, I upgraded from 4.1.2 to 4.3, but
kept my old bootloader. So I am rooted and have TWRP on this 4.3 based CFW. No KNOX anywhere.
(Did all this about 12 months ago or more, and have had some significant life events in the last year,
so have been completely out of the scene.. )
Anyway, I was considering upgrading to 4.4.4 (stock)
Can anyone tell me if I can do this and remain Knox free and have a custom recovery such as TWRP.
(If so can you point me to a working guide?)
Thanks Heaps in Advance,
BrikHaus
BrikHaus said:
Hi Guys,
Hope someone a bit more clued up than myself can clarify my questions or guide me..
I've done some searching, but am not 100% confident.
So, I have a I9305 running a Boeffla Kernel 5.2. If I recall correctly, I upgraded from 4.1.2 to 4.3, but
kept my old bootloader. So I am rooted and have TWRP on this 4.3 based CFW. No KNOX anywhere.
(Did all this about 12 months ago or more, and have had some significant life events in the last year,
so have been completely out of the scene.. )
Anyway, I was considering upgrading to 4.4.4 (stock)
Can anyone tell me if I can do this and remain Knox free and have a custom recovery such as TWRP.
(If so can you point me to a working guide?)
Thanks Heaps in Advance,
BrikHaus
Click to expand...
Click to collapse
Hi,
you have 3 options:
- Option #1: Stay with your old 4.1.2 firmware base with OLD bootloader and you can flash which custom KitKat ROM you want (N4 Elite ROM, TGP, AMCHA KK, etc.). If your favorite ROM is NOT compatible with TWRP, you will have to flash PHILZ recovery 6.48.4 instead and then flash the ROM. If the custom ROM is compatible with TWRP, you will only have to flash the ROM.
When you will flash the ROM, don't forget to choose a KK modem (XXUFNI3, XXUFNJ1 or XXUFOA1 depending on the ROM base) to have a working baseband and also, don't forget to choose a compatible Kernel with OLD bootloader (AGNi, HBO kernel or Dlite). Note : Stock kernel is not 100% compatible with OLD bootloader : WIFI will not work.
- Option #2: Upgrade to latest official 4.4.4 stock (I9305XXUFOC1) for i9305 with ODIN : this way, you will have new 4.4.4 KNOX bootloader and you will not have custom recovery anymore. If you want to stay like this, you will be 100% stock and 100% up-to-date from Sammy.
- Option #3: Follow the option #2 and then root your phone and flash custom recovery. You could finally stay like this or flash a custom ROM. If you choose to flash a custom ROM, one good thing is that you will be able to use stock kernel (100% working including WIFI) if available with this ROM.
You can follow that guide from @MaHo_66 : http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
Reminder: To go VERY clean wipe and install a custom firmware :
1. Backup all your data
2. Full wipe (data, cache and dalvik) in recovery including internal sdcard (internal sdcard format option in mounts and storage settings)
3. Flash a i9305 official firmware (4.1.2, 4.3 or 4.4.4) via ODIN. IMPORTANT : If you don't want KNOX BL because of warranty purpose, don't flash official 4.3 or 4.4.4 via ODIN.
4. Root
5. Flash custom recovery : (Philz for instance)
6. Install custom ROM
Steps 4 and 5 can be permuted.
PS: Off topic : @MaHo_66, you're now a RC, well done !
Thanks @FLooDW
Btw. youre spot on as always helping others, very good explanation you gave here :good:
MaHo_66 said:
Thanks @FLooDW
Btw. youre spot on as always helping others, very good explanation you gave here :good:
Click to expand...
Click to collapse
Thanks
Ok, if it's good, I hope it will help BrikHaus.
FLooDW said:
Thanks
Ok, if it's good, I hope it will help BrikHaus.
Click to expand...
Click to collapse
Im pretty sure it will
Legend!
Thank you VERY MUCH @FLooDW! Wish I could give you 10x Thanks!
Just the answer I was after. I wasn't sure if it was even possible to have a custom recovery on KNOX 4.4.4 bootloader.
I dropped out of the scene just as KNOX raised its ugly head...
I'm not worried about the warranty at all. Phone is two years old and well out of warranty period.
I'll go Option #3, sounds like just what I was after.
Thanks again!
BrikHaus said:
Thank you VERY MUCH @FLooDW! Wish I could give you 10x Thanks!
Just the answer I was after. I wasn't sure if it was even possible to have a custom recovery on KNOX 4.4.4 bootloader.
I dropped out of the scene just as KNOX raised its ugly head...
I'm not worried about the warranty at all. Phone is two years old and well out of warranty period.
I'll go Option #3, sounds like just what I was after.
Thanks again!
Click to expand...
Click to collapse
Yes you can have custom recovery with Knox BL. It's my case and everything is ok for me.
I hope you'll be ok
Please let us know.
I saw your sig..
Philz looks like it has more features than TWRP.. Might try that.
How do you find your performance with that kernel & rom?
Cheers Mate.
BrikHaus said:
I saw your sig..
Philz looks like it has more features than TWRP.. Might try that.
How do you find your performance with that kernel & rom?
Cheers Mate.
Click to expand...
Click to collapse
I'm very happy about perf with latest Amcha and AGNi. I have between 26000 and 26600 in AnTuTu without any overclock.
User experience is great in my case.
I don't use Fly-on mod (available in Amcha for instance) because I've noticed some big lags with my config on my phone.
All went pretty well. Had a couple of hangs, but got them all sorted.
Currently restoring, but having an issue where the phone switches from "USB Media mode" to "Dock Mode" and back and forth.
Weird issue I've never seen before....
BrikHaus said:
All went pretty well. Had a couple of hangs, but got them all sorted.
Currently restoring, but having an issue where the phone switches from "USB Media mode" to "Dock Mode" and back and forth.
Weird issue I've never seen before....
Click to expand...
Click to collapse
About your USB media / Dock issue, I've never read such problem. Moreover, I don't use dock at all. I will not be very helpful about this. Sorry.
FLooDW said:
About your USB media / Dock issue, I've never read such problem. Moreover, I don't use dock at all. I will not be very helpful about this. Sorry.
Click to expand...
Click to collapse
Yeah I don't use dock either. It seems it gets confused about what its actually plugged into..
Anyway, I'll figure it out. Thanks heaps for your help Mate. Very much appreciated.
Hi,
One of my friends told me not to do OTAs beta updates because it could bootloop my phone.
Last update I flashed the zip and all worked perfectly fine, but I had to re-root my phone and re-uninstall annoying stock apps with titanium backup.
Now I have a question :
Is it really risked to do the update with an OTA download ?
I really don't want to re-root my phone and do all the other stuff that comes with it.
I guess there is a way to do a safe update which keeps my data with the OTA but I need a confirmation about that.
Thanks !
(Original post [here] but probably faster answers on this forum, I guess ?)
I think it is ok with official updates. I have not any issue. Just i have not rooted or etc. All stock
gioyocho said:
I think it is ok with official updates. I have not any issue. Just i have not rooted or etc. All stock
Click to expand...
Click to collapse
Thanks, but I would like to have the advice of somebody with approximatively the same setup as mine, I mean at least with a rooted op3t
If you have all stock, then I can't tell if doing the OTA update will re-stock my phone too
I always have stock phones, because early time when i tried root, unlock btl, install twrp, change rom... sometimes there were wrong things, examle booting only logo and phone make a stone looks like, also custom roms has some bugs and on stock i am sure that everything works good. I do not understan why people starting root, change roms or etc. Use stock always and everything will be ok
gioyocho said:
I always have stock phones, because early time when i tried root, unlock btl, install twrp, change rom... sometimes there were wrong things, examle booting only logo and phone make a stone looks like, also custom roms has some bugs and on stock i am sure that everything works good. I do not understan why people starting root, change roms or etc. Use stock always and everything will be ok
Click to expand...
Click to collapse
U better off using an iPhone
To answer OP, yes you can struck in bootloop.
Remember it's beta version and not stable release.
Going back to stock from my rooted PopRocksV14. Haven't flashed ROMs in a while, so super rusty. Input welcome. TIA!
Questions:
1 Any faster mirror for N910TUVU2EQI2 than https://www.sammobile.com/firmwares/galaxy-note4/SM-N910T/TMB/?
2 How is the latest stock FW? Any reason not to upgrade? I'm just looking to get a stable phone and decent battery life, don't care about bloat
3 I'm looking to overwrite any Kernel and partition changes that PopRocks might have made, so is flashing back to stock rom going to do this?
Steps:
1 Make sure Samsung drivers installed
2 Download Odin 3.13 - https://odindownload.com/download/#.WyvXuCAnbAQ
3 Download EQI2 rom
4 Factory reset N910T
5 Run Odin as Admin
6 Start N910T in Download mode
7 Connect phone to PC via USB cable
8 Check Odin that COM is connected
9 Click PDA and select EQI2 tar file
10 Make sure Auto Reboot and F.Reset Time are checked, all other options disabled
11 Click start and wait for update to complete and phone to reboot
12 Factory reset N910T
I went ahead and tried it after the Sammobile download completed and it worked!
sfsilicon said:
I went ahead and tried it after the Sammobile download completed and it worked!
Click to expand...
Click to collapse
@sfsilicon - hope you're still monitoring this old thread. I'm trying to revive my old Note 4 I found in a junk drawer - for my 6yo boy. It had some custom rom on it, and I've now attempted with Odin to restore the image EQ12 you had listed - it appears to be the most recent.
Oden gets about 99% done then fails and now the phone is stuck in some sort of emergency mode. I can get into download, but not recovery. I assume I hosed it - maybe the bootloader was the wrong kind from the prior custom rom (and I didn't take note of what it was since I was just wiping it out).
Bummer.
Sorry to hear about your problems. It has been a while since I reflashed back to stock. Did it on two note 4s. From your description only thing I can think of would be that you flashed from a rom that was from an earlier Android version to the latest and it is missing some files or partitions that would normally be part of that type of transition. E.g. if you had done all the updates via OTA vs gone from your custom rom to the latest stock TMO release.
So try to figure out what Android revision your custom rom was before this latest flash. Then check the posts about moving from that revision to the next latest one and see if there is anything special in between. You can then look for the stock TMO rom that matches your custom ROM then flash back to that. Once you have a ROM working, even an older you can flash the next updates till you reach the final/latest TMO version or just OTA it.
One other thing to check is if your custom ROM did any changes to the kernel files or other stuff. Then check with the old custom ROM how to reverse them. Not sure if flashing a stock TMO rom undos all this. Its been a while but would think so but its still a step to check.
Hope this helps and good luck! I'm actually using my N4 currently. I use it to hold a foreign SIM when I am travelling. Sort of a glorified hotspot. Gave my 2nd one to my mom where the large screen helps with reading text. Its still a nice phone.
Thanks for getting back with me. I was under the impression that regardless of what custom rom may have been on the phone, Odin was a way to wipe the slate clean and put it back to day-1 state. I have no idea what OS was on there, but I do recall a warning about the bootloader being modified and it may be impossible to roll back. That's going off of memory (which has a very low confidence level).
Now I can't even get it to power up at all. I think I'm going to bail and just get a cheap Chinese android phablet - don't need cell service. It's getting to the point that my time and patience is worth more than what I'm spending to rehab this thing. Sucks too... When I first got the N4, I was pretty proficient at swapping roms... But since I've not played with them in years, I've all but forgotten the basics.
Thanks for the suggestions, tho...
E