Related
Just a couple of quick questions, have searched but couldn't find an answer.
Firstly, have been having a few problems with a lot of the custom ROMs I've been using recently, they usually work well for a while, then start going wrong. I've heard you're meant to flash a stock ROM in between each custom one, was wondering if that's true, as I've never seen it written anywhere. I flash using USPL if it matters. Currently using Dutty's Leo R5, which has also just started going wrong for me.
Also out of interest, how would I go about flashing a stock ROM? Same process as normal? And where would I be able to get the latest one from?
Cheers for any help.
Tyrrell9 said:
Just a couple of quick questions, have searched but couldn't find an answer.
Firstly, have been having a few problems with a lot of the custom ROMs I've been using recently, they usually work well for a while, then start going wrong. I've heard you're meant to flash a stock ROM in between each custom one, was wondering if that's true, as I've never seen it written anywhere. I flash using USPL if it matters. Currently using Dutty's Leo R5, which has also just started going wrong for me.
Also out of interest, how would I go about flashing a stock ROM? Same process as normal? And where would I be able to get the latest one from?
Cheers for any help.
Click to expand...
Click to collapse
I've never once flashed back to a stock rom in-between custom roms (and I've tried a few) .
But I have also heard that it works for some people having issues with flashing. If you are using uspl, then your stock spl is still intact and you should just be able to flash back to a stock rom (AFAIK in any case - sorry you can see I use hspl)
You can find many of the shipped roms (stock) here
Depending on the rom you choose and your current spl you may get the blue/green screen after the flash, but that would only be due to a rom/spl mismatch.
Thanks for the help, gonna flash a stable ROM for the next few days I think. Just one other thing I've been thinking of, I've got SPL 1.54 showing up in bootloader mode. You know if that's still the one you're supposed to use? Not sure if it should be 1.56?
Tyrrell9 said:
Thanks for the help, gonna flash a stable ROM for the next few days I think. Just one other thing I've been thinking of, I've got SPL 1.54 showing up in bootloader mode. You know if that's still the one you're supposed to use? Not sure if it should be 1.56?
Click to expand...
Click to collapse
Is it still 1.54.0000? This is actually an updated stock spl which you loaded when using uspl, so you should be able to just flash one of the later version stock roms. There is no need to downgrade your spl to your original (unless of course you need to return your phone for service)
1.56 is only as a result of using hspl and AFAIK there is no stock 1.56 version.
ClydeB1 said:
Is it still 1.54.0000? This is actually an updated stock spl which you loaded when using uspl, so you should be able to just flash one of the later version stock roms. There is no need to downgrade your spl to your original (unless of course you need to return your phone for service)
1.56 is only as a result of using hspl and AFAIK there is no stock 1.56 version.
Click to expand...
Click to collapse
Ah that's alright then, yeah it is still 1.54.0000. I'd just seen something about SPL 1.56 mentioned, so I wondered if there was a newer version of that stock spl. I'll find another ROM to flash for now, seems like I've been doing everything right. Thanks again for your help.
Tyrrell9 said:
Just a couple of quick questions, have searched but couldn't find an answer.
Firstly, have been having a few problems with a lot of the custom ROMs I've been using recently, they usually work well for a while, then start going wrong. I've heard you're meant to flash a stock ROM in between each custom one, was wondering if that's true, as I've never seen it written anywhere. I flash using USPL if it matters. Currently using Dutty's Leo R5, which has also just started going wrong for me.
Also out of interest, how would I go about flashing a stock ROM? Same process as normal? And where would I be able to get the latest one from?
Cheers for any help.
Click to expand...
Click to collapse
Flashing back to stock ROM worked for me, my spl has bee upgraded since i started flashing (first one was Dutty 3.9XT). This solved many of my problems encountered flashing the latest Win 6.5 + Manila 2.5 ROMS.
Tyrrell9 said:
Ah that's alright then, yeah it is still 1.54.0000. I'd just seen something about SPL 1.56 mentioned, so I wondered if there was a newer version of that stock spl. I'll find another ROM to flash for now, seems like I've been doing everything right. Thanks again for your help.
Click to expand...
Click to collapse
My pleasure - hope you come right.
jigners said:
Flashing back to stock ROM worked for me, my spl has bee upgraded since i started flashing (first one was Dutty 3.9XT). This solved many of my problems encountered flashing the latest Win 6.5 + Manila 2.5 ROMS.
Click to expand...
Click to collapse
What stock ROM have you been using? I've only been having problems with 6.5 roms, 3.9xt was the only one I've used so far that's worked flawlessly.
Hallos Tyrrell9,
they usually work well for a while, then start going wrong.
Click to expand...
Click to collapse
Fortunatly we are dealing with a form of Windows and as in any windows there is not so much difference. This means that it is silly to think that the same windows OS u installed is running as well or the same as to when u first installed it. We have to MAINTAIN it....
Think of ur phone rom as if it were a windows version on a regular PC. What happens after a few weeks is that it gets cluttered with unnused registry keys (even from installing and uninstalling apps), cache files, temp files and all other junk that gets installed by default. This means that u as a user have to clean it once in a while to get get rid of all this stuff that is going to make ur windows and thus ur phone slow after a while. Fortunatly there is help for us to do so. I use Pocket Mechanic and SKTools for this reason. Another thing is that u can look at the windows startup folder to see what is started. The less it is starting the faster and snappier ur phone will be..
I think it is also silly to think that u have to reflash a new rom every other day. I only flash a new rom if i see some major upgrades in the new one.
I hope this helps some...
Greetz
Caved
caved said:
Hallos Tyrrell9,
Fortunatly we are dealing with a form of Windows and as in any windows there is not so much difference. This means that it is silly to think that the same windows OS u installed is running as well or the same as to when u first installed it. We have to MAINTAIN it....
Think of ur phone rom as if it were a windows version on a regular PC. What happens after a few weeks is that it gets cluttered with unnused registry keys (even from installing and uninstalling apps), cache files, temp files and all other junk that gets installed by default. This means that u as a user have to clean it once in a while to get get rid of all this stuff that is going to make ur windows and thus ur phone slow after a while. Fortunatly there is help for us to do so. I use Pocket Mechanic and SKTools for this reason. Another thing is that u can look at the windows startup folder to see what is started. The less it is starting the faster and snappier ur phone will be..
I think it is also silly to think that u have to reflash a new rom every other day. I only flash a new rom if i see some major upgrades in the new one.
I hope this helps some...
Greetz
Caved
Click to expand...
Click to collapse
All true, but some of us have this strange addiction that needs to be satisfied regularly....
Undoubtedly and Unashamedly a member of Flashaholics United
Hallos ClydeB1,
If u enjoy flashing 4 roms a day to see if one or other rom will run better go right ahead, that seem to be a hobby in itself for some people. If thats is doing any good to you or ur HD ? Doubtfull but who am i to judge...
I just said that things don't have to go bad after a period of time becouse it doesn't have to be that way, u are the boss and not ur windows OS.
Greetz
Caved
Hi,
I have really googled this but cant really figure it out.
I have been through several excellent custom roms. Good work to you all !
.. but very often they crash hang etc. Sometimes during the day. Often when I charge the phone at night etc.
Is it correct that it is very important to first flash the latest stock rom before you flash the custom rom !?!?
I believed that flashing the custom rom image would replace all prior rom data?
Please help me out !
If I do it is just to flash stock rom with Hard SPL and then hardreset and another custom rom? I read something about someone bricking the phone.
/P
Lombiz said:
Hi,
I have really googled this but cant really figure it out.
I have been through several excellent custom roms. Good work to you all !
.. but very often they crash hang etc. Sometimes during the day. Often when I charge the phone at night etc.
Is it correct that it is very important to first flash the latest stock rom before you flash the custom rom !?!?
I believed that flashing the custom rom image would replace all prior rom data?
Please help me out !
If I do it is just to flash stock rom with Hard SPL and then hardreset and another custom rom? I read something about someone bricking the phone.
/P
Click to expand...
Click to collapse
hi
crashes might happen, right
sometimes it could be the rom, or an app, or rhe sd card, or radio+ril combo,...
its not always easy to trace and single out
some reported that -although indeed everything of the previous rom should be removed during flash- they still fared better when flashing stock before custom
I must say I never did and fortunately also didnt have hlaf of the problems reported by other users
so: find out for yourself, as it cannot be generalised
cheers
Two phones. result very different !
Thanks !
What I really find strange though.
My friend and I have the same X1. Released at about the same time etc.
So hardware should differ mouch.
The rom is flashed so any difference in updates shouldnt matter too much.
After flashing my phone works great and his barely starts.
/peter
from my experience there is a difference
flashing a custom rom only replaces the previous rom
but flashing the latest custom rom replaces (rom+radio+ and 2 other things that i cant remember)
u wont get a problem free mobile after flashing the stock rom
but i'm sure that it decreases them to a very noticeable degree
less freezes better performance etc...
in my opinion: u won't loose anything from doing it, but it might help
so y not to try, it worth the shot
I searched around quit a bit and couldn't find this info.
If you go to one of the Froyos, with/without radio, is it possible to just flash it back with another custom Rom over that and all is good?
Just wondering if there are any gotchas like if you put the radio update on etc...
Thanks
how about using search!!!!
http://forum.xda-developers.com/showthread.php?t=687795
craigacgomez said:
how about using search!!!!
http://forum.xda-developers.com/showthread.php?t=687795
Click to expand...
Click to collapse
One person in that thread claimed, with an unlocked bootloader, that he just put the old radio and custom rom on the card, and did the usual wipe and flash and it worked fine.
Others that posted were all over the place, including some convoluted approach that pretty much wiped everything on the device and SD card to get it back to stock..which I don't care about stock. I just want to be able to go back from 2.2 to my Modaco R21 if necessary without any gotchas.
Yes you can just flash any ROM like you normally would. I've done it a few times now in the last few days. I did the old radio and all.
RogerPodacter said:
Yes you can just flash any ROM like you normally would. I've done it a few times now in the last few days. I did the old radio and all.
Click to expand...
Click to collapse
Thanks.
So I got the original radio, plus my R21 and intersectR kenerl setup I know is good.
Looks like you just flash the radio, then the Rom and kernel and setup again...
Thanks for the reply.
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.
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