I'm currently running 4.4.2 and biggins ROM. been running flawlessly since I put it on it when it came out. Now, for about the last month or 2 my WiFi Keeps Shutting off on its own, forgets WiFi passwords, won't connect hardly when it does come in. It's also been randomly rebooting on its own, sometimes 3 or 4 times in a row. Anyone have any suggestions on how to fix it. I've had the phone since the note 3 came out.
Sent from my SM-N900V using Tapatalk
Frankly that sounds more like hardware troubles than software.
(Q) Are you overclocking or undervolting? Using kernel tuning apps? If so, temporarily stop doing that to see if the problem goes away, and if not then there's two approaches for resolving this:
(A) Throw the phone away and get a new one.
(B) Wipe and and install a conservative ROM e.g. Jasmine, retaining the stock kernel. If the same problems continue, then you have verified it is a hardware problem; see (A)
bftb0 said:
Frankly that sounds more like hardware troubles than software.
(Q) Are you overclocking or undervolting? Using kernel tuning apps? If so, temporarily stop doing that to see if the problem goes away, and if not then there's two approaches for resolving this:
(A) Throw the phone away and get a new one.
(B) Wipe and and install a conservative ROM e.g. Jasmine, retaining the stock kernel. If the same problems continue, then you have verified it is a hardware problem; see (A)
Click to expand...
Click to collapse
I'm not overclocked or anything. It's been on Biggins ROM since he came out with it last year. And I haven't done anything since. It's got me baffled as to why it just randomly started doing it.
Sent from my SM-N900V using Tapatalk
donelam304 said:
I'm not overclocked or anything. It's been on Biggins ROM since he came out with it last year. And I haven't done anything since. It's got me baffled as to why it just randomly started doing it.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Actually I guess I wasn't familiar with the Biggins ROM but then I remembered that you said "last year", so (just now I figured that) you were either on a DevEd phone, or it was a "stock kernel" ROM.
So I looked at the Biggins thread. I guess it is actually just a very heavily themed stock-kernel ROM, and you are using Safestrap? And don't have an unlocked bootloader? And don't have a "real" version of TWRP in the recovery partition?
If that's what you did, then you don't have a trivial way of stock reversion short of going back to Odin and starting over with rooting.
Unless you were diligent and backed up the stock slot with Safestrap-twrp right after you flashed Biggins.. Or even better, you also did the same thing right after you installed Safestrap, even before you installed Biggens[/b] Then you could try and dirty-flash the Biggens backup and see if that changes anything. And if that didn't work, restore the original (Safestrapped, pre-Biggens) ROM along with a factory reset and see if that does anything.
But that would only rectify problems that were due to flash memory bit-rot problems (progressive wear & eMMC flash memory pages slowly going bad). And even if that were the case, it's a sign of more of it yet to come.
If you didn't make those backups, then I suppose you have a trip to Odin and re-rooting, re-installation of Biggins - on a phone that might have failing hardware. Either that or you could take the plunge and unlock your bootloader. Then you would have more options.
Are you on NC4?
Hardware does go bad. It happens at a low probability, so usually it doesn't affect most people before the time they would retire their hardware. Although I have to say - based on my experience with other devices - use of MLC flash memory probably does imply a pretty short product lifetime. (It's sort of ridiculous, buying a device that costs $700 and expecting it to be dead in 3 years. OTOH, in those three years most VZW subscribers have spent another $2500+ on service fees for their first line, so it's not the longest pole in the tent.)
bftb0 said:
Actually I guess I wasn't familiar with the Biggins ROM but then I remembered that you said "last year", so (just now I figured that) you were either on a DevEd phone, or it was a "stock kernel" ROM.
So I looked at the Biggins thread. I guess it is actually just a very heavily themed stock-kernel ROM, and you are using Safestrap? And don't have an unlocked bootloader? And don't have a "real" version of TWRP in the recovery partition?
If that's what you did, then you don't have a trivial way of stock reversion short of going back to Odin and starting over with rooting.
Unless you were diligent and backed up the stock slot with Safestrap-twrp right after you flashed Biggins.. Or even better, you also did the same thing right after you installed Safestrap, even before you installed Biggens[/b] Then you could try and dirty-flash the Biggens backup and see if that changes anything. And if that didn't work, restore the original (Safestrapped, pre-Biggens) ROM along with a factory reset and see if that does anything.
But that would only rectify problems that were due to flash memory bit-rot problems (progressive wear & eMMC flash memory pages slowly going bad). And even if that were the case, it's a sign of more of it yet to come.
If you didn't make those backups, then I suppose you have a trip to Odin and re-rooting, re-installation of Biggins - on a phone that might have failing hardware. Either that or you could take the plunge and unlock your bootloader. Then you would have more options.
Are you on NC4?
Hardware does go bad. It happens at a low probability, so usually it doesn't affect most people before the time they would retire their hardware. Although I have to say - based on my experience with other devices - use of MLC flash memory probably does imply a pretty short product lifetime. (It's sort of ridiculous, buying a device that costs $700 and expecting it to be dead in 3 years. OTOH, in those three years most VZW subscribers have spent another $2500+ on service fees for their first line, so it's not the longest pole in the tent.)
Click to expand...
Click to collapse
Here is my current build. I am on NC4.
Sent from my SM-N900V using Tapatalk
Well,
What do you plan on doing? It's not like there's a toggle button in Settings labeled "Act strange and reboot randomly mode" that we can just go in and turn off.
Do you have any Safestrap backups?
How about the NC4 factory Odin firmware file, do you have that? A copy of Odin somewhere & a PC it will run on?
That's how these things go - you need to create a fault hypothesis, and then try something that will hopefully do something to remedy that type of fault... which might or might not work.
The "bit rot" hypothesis assumes that flashing the same software you already have on the phone will correct eMMC memory pages that have gone bad, both by refreshing the data and also through page replacements by the Flash memory controller doing wear leveling. But that's only one hypothesis out of many that are possible. There's no guarantees that this will fix the problems you are having if the origin of the problem has nothing to do with this mechanism.
If it were me I'd probably make TiBu backups of my most frequently used apps, back up the internal SDcard, and start from scratch by Odin flashing NC4 stock*. Its more effort, but pretty much everything gets re-written that way, and if you continue to have issues then you know it is time to move on to a new phone, rather than continuing to diddle with it.
good luck
* I believe that the TowelRoot app works on NC4, does it not?
Yes, towelroot is what I use to root it. I have a backup, but I'm not sure what it is. The Daye on it is 1970. Lol.
Sent from my SM-N900V using Tapatalk
donelam304 said:
Yes, towelroot is what I use to root it. I have a backup, but I'm not sure what it is. The Daye on it is 1970. Lol.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
If you do a "tar tvf filename" on those .win00x files the dates of the files listed will give you a better idea. (I suppose that some widows archive programs also understand .tar file formats, but I can't give you a reccomendation)
Also I sort of recall that the Safestrap version of (twrp) recovery adds the name of the slot from which the backup was made.
You actually have lots of choices. You could unlock the bootloader, install a custom recovery, and try a different ROM. Or when faced with Odin flashing, bite the bullet and upgrade to OF1. (As near as I can tell, using towelroot on NC4 is far less of a hassle then that Yemen tool appears to be with OB6/OF1 ... that sort of argues for flashing NC4 instead of more recent firmware.)
Well anyway. If it's failing hardware none of this will make a whit of difference and your phone will still lockup/reboot/drop WiFi.
good luck
Related
So, I'm not too tech savvy. I do get by though. About two months ago I was "computing" (haha) on my Acer a500 and the thing froze on me, when I restarted it, it when into a bootloop (I guess) of the ACER logo. I pretty much gave up and recently bought a Nexus 7. Anyways... when I tried entering in the recovery it really doesn't do much but show the lil green android guy trying to recover, but alas he falls over each time and a red triangle with an exclamation point appears. I've tried many a button combo to make it reset, recover... etc.. but still no luck. After reading some things, I saw it might be possible that its a hardware issue? Which made me wonder if I purchased a new or refurbished motherboard and plugged it all in, does anyone think it would work again? Or am I grossly underestimating whats going on here? I pretty much want to make it a mission to fix this damn thing, if only for bragging rights. Before I go test my luck and buy a motherboard, I want to know if I'm going to have to go through any other steps or processes so I don't get overly excited, then fail and throw this tablet against the side of my house.
Help me XDA users, you're my only hope.
Sincerely, Radnuh the pseudo tech-geek.
If you fall off your house, then I hope your tab falls my way.
One thing about the 50x, it's pretty bullet proof.
Were you rooted, with a CWM? Or was it stock?
And what OS was it running at the time it died? ICS or HC?
MD
Moscow Desire said:
If you fall off your house, then I hope your tab falls my way.
One thing about the 50x, it's pretty bullet proof.
Were you rooted, with a CWM? Or was it stock?
And what OS was it running at the time it died? ICS or HC?
MD
Click to expand...
Click to collapse
Hey! That's what I have gutters for! It was running ICS, stock not rooted. Oh and in the past I had a display problem. I had to open it up and reconnect the screen display connector, or whatever the technical term is! I've been reading quite a few stories of similar situations about this very same thing occuring, that's why I'm hoping its a software issue!
Sorry to bump this, but I'm just curious if it would be a simple plug n' play situation if I bought a new motherboard. Anyone? Bueller.... Bueller?
Radnuh said:
Sorry to bump this, but I'm just curious if it would be a simple plug n' play situation if I bought a new motherboard. Anyone? Bueller.... Bueller?
Click to expand...
Click to collapse
You don't need no stinking board. Don't sound like it the way you described. Try reflashing the darn thing using the techniques you can find all over this place. It's your chance not to be a chicken, to use Civato's expression, and to liberate yourself and your tablet. Above all, don't listen to your wife or girlfriend.
graphdarnell said:
You don't need no stinking board. Don't sound like it the way you described. Try reflashing the darn thing using the techniques you can find all over this place. It's your chance not to be a chicken, to use Civato's expression, and to liberate yourself and your tablet. Above all, don't listen to your wife or girlfriend.
Click to expand...
Click to collapse
Well I tried the whole putting stock ics as an update zip file on an sd then trying to recover, every time it starts then a few seconds later bam, red triangle. I also tried fastboot, but it would say waiting for device and that's it. I'm not really sure but I think I read something about having to unlock a bootloader, I definitely need to read some more into all this, lol. Is this normal though for this tablet to just freeze, and go into a bootloop?
Radnuh said:
Well I tried the whole putting stock ics as an update zip file on an sd then trying to recover, every time it starts then a few seconds later bam, red triangle. I also tried fastboot, but it would say waiting for device and that's it. I'm not really sure but I think I read something about having to unlock a bootloader, I definitely need to read some more into all this, lol. Is this normal though for this tablet to just freeze, and go into a bootloop?
Click to expand...
Click to collapse
I'm quoting MD for your information. Pay special heed to the 2 files on ICS stock. If you're in stock recovery, and it's corrupt, I doubt it it would let you flash anything. Start with TD's or EUUs found in Civato's stock Roms thread. Better yet, if you're game, get V8 and flash a newer custom ROM. Stock ROM ain't no fun.
"Ok, so here's a little info for you folks. Not sure if it helps you or not, but might clear up some of the mess that's been going on concerning bootloader versions VS Roms.
So you run one of the RUUs files. That's fine. Essentially you should be back on an HC bootloader running an HC rom. At this point, all your partitions should be back in place, especially if you used TD's tool.
While you are in HC, and everything is running fine, you should make a note of your current UID number. Because, after upgrading to ICS, your UID number will probably change. (the converted SBK number should be the same with both). But the RUUs seem to mostly want an HC UID number.
The issue, is when upgrading to ICS. If you do this the normal way via OTA, you should eventually get to ICS with a stock ICS bootloader. At this point, I would leave it alone for a few days, just to make sure it runs normally. Again, get your new UID number.
Now, here may be what you folks are missing.
With the introduction of ICS, Acer pulled a fast one on us. They introduced a little file called recovery-boot.p, and also a recovery.sh file.Both reside in /system (not sure exactly which folder for one of them, might be /system/etc or /system/bin.)
The issue, is that if you NVFlash V8 bootloader, and let's say Thor CWM 1.7.2 or 1.7.3, without deleting those aforementioned files, when you boot your tab, guess what? Hasta La Vista CWM, and mr android is on his back deader than a doornail. Not to mention you might screw up a partition or 2 along the way. And then it's back doing the whole thing again, sorta like groundhog day.
If you get Skrilax_CZ's bootloader running, then there's no real reason why you can't load a compatible CWM to flash roms.
Personally, I don't like the little 1-app-does-all. I prefer the old fashioned way. NVFlash from a command line. This way, you can see if there's errors coming up. Also, you may have better luck trying one of the older packages for the V3 or V4 bootloader. If you guys are interested, I can research my other drives in a day or so, and come up with one of the original packages. Am sure I saved it somewhere.
But if you get the V8 loaded, then you can boot it into fastboot mode. From here, you can fastboot a good CWM image. And at this point, I strongly advise CWM 1.7.2 or 1.7.3. After you fastboot it, boot immediately into CWM recovery. Do not pass go, do not collect $200, and do your wipes and formats and immediately install a custom rom. If you boot back into your stock rom, sianara..... This is why it's best to already have your custom rom.zip on your SD card.
Now, roms, kernels and bootloaders. The rom you choose to install, is pretty important. It needs to be recent, and designed for the ICS bootloader (V8). Using some of the earlier roms with kernels is asking for trouble. HC based roms WILL NOT run on an ICS bootloader. Remember that also, and vica-versa.
It's possible, however unlikely, that one of you may have unrecoverable corrupt data on your chipset. It has happened, but it's rare. Generally, you will find this when you can't get anything running. Period. Or in the case I know, the user could not migrate from HC to ICS. But only 1 or 2 people I know have had this. Oh, 3. I forgot Civato who totally cooked his internal memory (more than likely while inventing his own version of TWRP)
Wipes and formats. Again, I can't stress this enough. There have been issues using TWRP when it comes to wipes and formats. It seems, sometimes, things don't get fully wiped. So, as I always do with CWM, remember those versions I quoted), always
Wipe Data/factory reset
Wipe Cache
Wipe Dalvak
Wipe battery stats (optional)
Goto Mounts and Storage
Format System
Format Flexrom
As we say, be nice, wipe twice.....
Then install the custom rom (not a stock rom, remember the 2 recovery files?)
MD"
graphdarnell said:
I'm quoting MD for your information. Pay special heed to the 2 files on ICS stock. If you're in stock recovery, and it's corrupt, I doubt it it would let you flash anything. Start with TD's or EUUs found in Civato's stock Roms thread. Better yet, if you're game, get V8 and flash a newer custom ROM. Stock ROM ain't no fun.
"Ok, so here's a little info for you folks. Not sure if it helps you or not, but might clear up some of the mess that's been going on concerning bootloader versions VS Roms.
So you run one of the RUUs files. That's fine. Essentially you should be back on an HC bootloader running an HC rom. At this point, all your partitions should be back in place, especially if you used TD's tool.
While you are in HC, and everything is running fine, you should make a note of your current UID number. Because, after upgrading to ICS, your UID number will probably change. (the converted SBK number should be the same with both). But the RUUs seem to mostly want an HC UID number.
The issue, is when upgrading to ICS. If you do this the normal way via OTA, you should eventually get to ICS with a stock ICS bootloader. At this point, I would leave it alone for a few days, just to make sure it runs normally. Again, get your new UID number.
Now, here may be what you folks are missing.
With the introduction of ICS, Acer pulled a fast one on us. They introduced a little file called recovery-boot.p, and also a recovery.sh file.Both reside in /system (not sure exactly which folder for one of them, might be /system/etc or /system/bin.)
The issue, is that if you NVFlash V8 bootloader, and let's say Thor CWM 1.7.2 or 1.7.3, without deleting those aforementioned files, when you boot your tab, guess what? Hasta La Vista CWM, and mr android is on his back deader than a doornail. Not to mention you might screw up a partition or 2 along the way. And then it's back doing the whole thing again, sorta like groundhog day.
If you get Skrilax_CZ's bootloader running, then there's no real reason why you can't load a compatible CWM to flash roms.
Personally, I don't like the little 1-app-does-all. I prefer the old fashioned way. NVFlash from a command line. This way, you can see if there's errors coming up. Also, you may have better luck trying one of the older packages for the V3 or V4 bootloader. If you guys are interested, I can research my other drives in a day or so, and come up with one of the original packages. Am sure I saved it somewhere.
But if you get the V8 loaded, then you can boot it into fastboot mode. From here, you can fastboot a good CWM image. And at this point, I strongly advise CWM 1.7.2 or 1.7.3. After you fastboot it, boot immediately into CWM recovery. Do not pass go, do not collect $200, and do your wipes and formats and immediately install a custom rom. If you boot back into your stock rom, sianara..... This is why it's best to already have your custom rom.zip on your SD card.
Now, roms, kernels and bootloaders. The rom you choose to install, is pretty important. It needs to be recent, and designed for the ICS bootloader (V8). Using some of the earlier roms with kernels is asking for trouble. HC based roms WILL NOT run on an ICS bootloader. Remember that also, and vica-versa.
It's possible, however unlikely, that one of you may have unrecoverable corrupt data on your chipset. It has happened, but it's rare. Generally, you will find this when you can't get anything running. Period. Or in the case I know, the user could not migrate from HC to ICS. But only 1 or 2 people I know have had this. Oh, 3. I forgot Civato who totally cooked his internal memory (more than likely while inventing his own version of TWRP)
Wipes and formats. Again, I can't stress this enough. There have been issues using TWRP when it comes to wipes and formats. It seems, sometimes, things don't get fully wiped. So, as I always do with CWM, remember those versions I quoted), always
Wipe Data/factory reset
Wipe Cache
Wipe Dalvak
Wipe battery stats (optional)
Goto Mounts and Storage
Format System
Format Flexrom
As we say, be nice, wipe twice.....
Then install the custom rom (not a stock rom, remember the 2 recovery files?)
MD"
Click to expand...
Click to collapse
I have much to learn, haha. Thank you for the info *starts researching*
I'm writing this as a new Nexus 7 2013 owner so that people with a moderate level of tech savvy and are still on the fence about unlocking and flashing their device can check it out from a non expert perspective. I think a lot of times people are afraid after reading tutorials and a bit intimidated by the procedures (and XDA).
I decided to get a nexus device because they are very well supported here on XDA and the general consensus is they are nearly impossible to hard brick barring a hardware issue or the user doing something really really dumb
After unboxing the device I put it on charge while making some final decisions on what direction I wanted to go with the "rebuild". As you will see some of these decisions will have cascading effects...
I settled on cleanrom 2.6 and the elementalx kernel, I also decided I wanted to use CWM (non touch) recovery instead of TWRP because I'm familiar with it and hoped that I would not spend enough time to justify having a gui.( and ... to be honest I am not a fan of TWRPs gui ).
So now that I have made my decisions for better or for worse it is time to proceed. I powered on and configured the device for the first time. Since I wasn't paying attention Google started downloading all my apps from Play. This was not a big deal but folks on a data plan might want to make sure they read the screens and decide not to restore their apps. The option for OTA upgrade was available from jellybean to kitkat, so I went ahead and proceeded with the OTA. In retrospect it was a waste of time because you can download the stock images and reflash them later if you want.
ADB and FASTBOOT were already on my Debian desktop and working properly so I went ahead and unlocked the bootloader, then rebooted and flashed CWM. I them installed supersu from CWM. (I left out the part about using adb to push the files but you get the picture...) So far so good except there was a fatal flaw in my plan. Cleanrom and ElementalX both use aroma installer, which doesn't work on CWM. So as I was doinking around In CWMs advanced options looking for a slim possibility of salvaging the situation I managed to end up in the key test application. The problem here being that since the device doesn't have a back button there was no way to get out of they key test. No worries though I simply connected the USB cable fired up adb and did "adb reboot". A few minutes later I had downloaded and installed TWRP and was ready to pick up where I left off.
Here is a note for folks doing this for the first time, read the instructions and erratta for your new kernel and ROM carefully before you proceed so that you avoid time consuming issues. By reading up a little before I started the project I knew that the ROM and kernel were compatible and work well together. I also knew that I would need to install the ROM first, then the kernel, because I I installed the Kernel first I would have to re-install it after flashing the ROM. No point in doing it twice, right?
SO I fired up TWRP and did a factory reset in preparation for flashing the ROM. So far so good. Cleanrom installed, but AROMA did not ask for my installation options. Fearing something was wrong, I clean flashed (wipe first then flash) the ROM 2 more times with the same result. After the third flash I said wth, as long as the ROM flashed and works I can always change software on my own. So a quick reboot and test drive of the device confirmed the ROM was installed and there appeared to be no glaring issues, so I went back to recovery and flashed the kernel. BTW I did check the md5sums and verified that the files were correct and not corrupted.
I know there is an option to flash more than one update with TWRP but since the install did not occur the way I expected I chose to install the ROM and kernel separately, I'm sure some more experienced members of XDA will agree with this decision and others will say that "it's nexus, go ahead and flash the ROM and kernel at the same time, you can't break it
Anyhow the kernel installation went fine and AROMA prompted me as expected before installing. Note to newbies like me, reading the thread really helps, Knowing exactly how you want to configure your kernel before you install it will save you hassles down the line. Expect the first boot to take a little extra time.
In nutshell, there really is no reason to be afraid of installing a custom kernel on your Nexus device. Sure the possibility is there for you to screw things up, but unless you do something very drastically wrong you wont brick the device, trust me -- If I can do it you can do it. Just think ahead a little and prepare yourself by downloading the files you need and maybe even writing yourself an outline of the steps. I'm sure that I could do this again and again now without referring to notes or tutorials, but having them readily available for guidance and reference was comforting.
I could continue with the saga of getting Debian to recognize the tablet in MTP mode but this post has already gone long and that is a rite of passage...
Hello. Sorry for the noobie question. I tried to search the forums, and I did find the noob beginner guide, but I still wasn't sure, so I prefer to ask before I screw up my phone lol.
I have the AT&T SG4 SGH-I337 Phone. It was fine before it was upgraded to 4.4.2 (I didn't want to upgrade, but it did it on its own one day). Once it went to 4.4.2, everything is just DOG SLOW. I mean everything. In Car Audio takes forever to connect, phone calls takes like 5 secs to answer, even after I press the answer button. To unlock the phone I have to press the code 2-3 times, as I can see the keys I press is lagging behind.
What I wanted to ask is this: How can I bring this phone back to the previous OS? Or How can I modify this phone to a stock OS, where all this bloatware crap is not installed?
All I care for is my Bluetooth, in car audio and calls and have a phone that's fast enough as it was originally.
can someone point me to the right thread where it gives me step by step instructions? Ive never modified a Samsung Phone before.
I found this thread, but wasn't sure if its the right one for my phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Thank you VERY MUCH. Thanks....
Don't use those links, some are redirecting me to questionable sites. Not sure if it does to you also.
I don't have time atm but someone will get you the correct info. :good:
It may have been a bad download that updated you--
Also, those files are too old for you if you look at thread date--
---------- Post added at 07:01 PM ---------- Previous post was at 06:25 PM ----------
This would be a starting point
http://forum.xda-developers.com/showthread.php?t=2616221
Assume you are now on NC1
Believe you will need to Odin back to NB1 then update to NC1
If you want to root other steps involved--This thread covers it pretty well
Some one else more familiar can be exact, as I am on old bootloader and no handson exp--
Read the OP on the link very well and generally not a good idea to use links outside xda unless you are 120% sure of what you are doing--good luck--
Cornelp said:
Hello. Sorry for the noobie question. I tried to search the forums, and I did find the noob beginner guide, but I still wasn't sure, so I prefer to ask before I screw up my phone lol.
I have the AT&T SG4 SGH-I337 Phone. It was fine before it was upgraded to 4.4.2 (I didn't want to upgrade, but it did it on its own one day). Once it went to 4.4.2, everything is just DOG SLOW. I mean everything. In Car Audio takes forever to connect, phone calls takes like 5 secs to answer, even after I press the answer button. To unlock the phone I have to press the code 2-3 times, as I can see the keys I press is lagging behind.
What I wanted to ask is this: How can I bring this phone back to the previous OS? Or How can I modify this phone to a stock OS, where all this bloatware crap is not installed?
All I care for is my Bluetooth, in car audio and calls and have a phone that's fast enough as it was originally.
can someone point me to the right thread where it gives me step by step instructions? Ive never modified a Samsung Phone before.
I found this thread, but wasn't sure if its the right one for my phone.
http://forum.xda-developers.com/showthread.php?t=2261573
Thank you VERY MUCH. Thanks....
Click to expand...
Click to collapse
I would suggest getting the Google Play Edition rom as stock android is much better optimized. Tutorials are available on the all things NC1 post. This will require root and installing a custom rom. Your warranty (if still applicable) will be void if you choose to do this. Regardless, the software on the device is not well optimized and the touchwiz UI is unnecessary imo. The GPE rom also does not have the samsung or at&t bloatware.
cxzzcx said:
I would suggest getting the Google Play Edition rom as stock android is much better optimized. Tutorials are available on the all things NC1 post. This will require root and installing a custom rom. Your warranty (if still applicable) will be void if you choose to do this. Regardless, the software on the device is not well optimized and the touchwiz UI is unnecessary imo. The GPE rom also does not have the samsung or at&t bloatware.
Click to expand...
Click to collapse
The google play ROM I would not mind, but I cant seem to find a way to root my SG4 NC1 firmware.
Do you happen to have a link or directions, please?
Thanks...
Cornelp said:
The google play ROM I would not mind, but I cant seem to find a way to root my SG4 NC1 firmware.
Do you happen to have a link or directions, please?
Thanks...
Click to expand...
Click to collapse
you can root using geohot's towelroot.
Cornelp said:
The google play ROM I would not mind, but I cant seem to find a way to root my SG4 NC1 firmware.
Do you happen to have a link or directions, please?
Thanks...
Click to expand...
Click to collapse
Use the "All things ATT" link rugmankc gave you. In the first posts in that thread you will get links to the root method, safestrap, and a list of compatible ROMs. A few thoughtsL
1. Before making any changes to you phone, charge it to 100 %, unplug the charger, and let it sit idle for some number of hours. Then check to see what services are using most of the power. For a while my own 4.4.2 GS4 was slow, and it turned out to be google play framework services bogging things down, and this showed up as an excessive battery drain during idle. If you phone uses more than say 0.5% battery per hour when completely idle / screen off (but with cell and wifi on), something's up. Fix it and maybe your problems will resolve.
2. Next step: back up any data / photos etc. and do a factory data reset from the settings menu. After it has been reset, perhaps whatever problem is going on will be cleared up.
3. You don't need to root the phone to ODIN a stock firmware (NB1 then flash update to NC1). Links are on the ALL Things ATT thread. This should take it all the way back to proper NC1, bypassing any mess that might have happened if you got a corrupt flash during your OTA update.
If the phone still performs so poorly as you describe after a flash back to stock, there's a problem that's more than the OS/ROM. Sure, the stock build is a bit laggy and bloated, but it's not so bad as what you are seeing.
If you find a restored stock ROM to be better but still laggier than you like, I have had good results with the GoldenEye ROM, flashed according to the instructions in the ATT thread. To flash, you must first root and install safestrap (selinux mode changer set to permissive may be required). You then boot to the safestrap recovery, wipe everything but the SD card, then flash the rom, SuperSU, ATT Module, and ATT BuildProp/APN. That should get you up and running on a new ROM.
I'm a died in the wool geek but I read through this forum and others for two weeks before attempting... but I'm very happy with the phone as it works on GoldenEye. I'm on V36, but V38 is current.
Good luck
Frankenscript said:
Use the "All things ATT" link rugmankc gave you. In the first posts in that thread you will get links to the root method, safestrap, and a list of compatible ROMs. A few thoughtsL
1. Before making any changes to you phone, charge it to 100 %, unplug the charger, and let it sit idle for some number of hours. Then check to see what services are using most of the power. For a while my own 4.4.2 GS4 was slow, and it turned out to be google play framework services bogging things down, and this showed up as an excessive battery drain during idle. If you phone uses more than say 0.5% battery per hour when completely idle / screen off (but with cell and wifi on), something's up. Fix it and maybe your problems will resolve.
2. Next step: back up any data / photos etc. and do a factory data reset from the settings menu. After it has been reset, perhaps whatever problem is going on will be cleared up.
3. You don't need to root the phone to ODIN a stock firmware (NB1 then flash update to NC1). Links are on the ALL Things ATT thread. This should take it all the way back to proper NC1, bypassing any mess that might have happened if you got a corrupt flash during your OTA update.
If the phone still performs so poorly as you describe after a flash back to stock, there's a problem that's more than the OS/ROM. Sure, the stock build is a bit laggy and bloated, but it's not so bad as what you are seeing.
If you find a restored stock ROM to be better but still laggier than you like, I have had good results with the GoldenEye ROM, flashed according to the instructions in the ATT thread. To flash, you must first root and install safestrap (selinux mode changer set to permissive may be required). You then boot to the safestrap recovery, wipe everything but the SD card, then flash the rom, SuperSU, ATT Module, and ATT BuildProp/APN. That should get you up and running on a new ROM.
I'm a died in the wool geek but I read through this forum and others for two weeks before attempting... but I'm very happy with the phone as it works on GoldenEye. I'm on V36, but V38 is current.
Good luck
Click to expand...
Click to collapse
Thank you very much for your help. Yeah everytime I redo my phone, from scratch, it works OK for about an hour. Then bam, it goes back to being a low pain in the rear. This is ONLY after the phone upgraded to 4.4.2. I didn't choose that upgrade, actually I didn't want to upgrade, but OTA upgrade took over and BAM, I got screwed.
OK I just installed the Safestrap and rooted the phone. Now I gotta figure out the rom part.
Im still going thru that link that rugmankc gave me above. Now im trying to figure out how to change the OS, since I just rooted the phone. I have to do this. Ive gotten really really tired of the phone being so slow, I basically give up on many tasks that I need to do, just cause its too slow.
Ill update once I get it figured out, hopefully I wont brick it, that's the only thing that im afraid of.
Don't remember, did you consider Odin back to stock and start over. If not, whatever was causing the slow downs may still be there. Could have been a bad update.
Read the SafeStrap thread by HashCode carefully. I read the OP 100% and last 30 pages or so of thread and don't even use it. It is complicated to me. IE which slot to flash to stock or rom. I think stock, Flash Modules. Install Selinux and set to permissive. And using correct SafeStrap. Gives me a headache and I am not even needing to use it--
Good Luck--as mentioned just backup whenever you can before moving to next major step. :good::good:
rugmankc said:
Don't remember, did you consider Odin back to stock and start over. If not, whatever was causing the slow downs may still be there. Could have been a bad update.
Read the SafeStrap thread by HashCode carefully. I read the OP 100% and last 30 pages or so of thread and don't even use it. It is complicated to me. IE which slot to flash to stock or rom. I think stock, Flash Modules. Install Selinux and set to permissive. And using correct SafeStrap. Gives me a headache and I am not even needing to use it--
Good Luck--as mentioned just backup whenever you can before moving to next major step. :good::good:
Click to expand...
Click to collapse
Thank you. Actually I backed up my phone already, as I reformatted it last night again. I don't know how to Odin back to stock. What is that? Is that a stock Android? Sorry I don't know.
Thanks...
It's in the same All Things ATT, MK2 thread under Returning to Stock Odin. An option if you still have issues. Takes you back to stock NB1, firmware and all. Kinda like your update, but think you may have got a bad update. Other options are to wipe internal in case bad stuff still there. Frankenscript was pretty thorough--:good:
SafeStrap is how you are going to flash a new OS/Rom. You can't flash custom kernels and aosp roms unless TW based like a couple GPE mentioned.
Read/Scan the two mentioned threads, as in OP and first and last couple dozen pages. Probably the last are more important. You will see folks asking the same questions you will eventually ask. I have read thousands of pages over the years and it has kept me out of trouble--most of the time--
rugmankc said:
It's in the same All Things ATT, MK2 thread under Returning to Stock Odin. An option if you still have issues. Takes you back to stock NB1, firmware and all. Kinda like your update, but think you may have got a bad update. Other options are to wipe internal in case bad stuff still there. Frankenscript was pretty thorough--:good:
SafeStrap is how you are going to flash a new OS/Rom. You can't flash custom kernels and aosp roms unless TW based like a couple GPE mentioned.
Read/Scan the two mentioned threads, as in OP and first and last couple dozen pages. Probably the last are more important. You will see folks asking the same questions you will eventually ask. I have read thousands of pages over the years and it has kept me out of trouble--most of the time--
Click to expand...
Click to collapse
Man, that link really got me confused as heck lol. Ive been reading that link the entire weekend and still im a bit confused.
I rooted the phone with towelroot. Ive installed SafeStrap, but it worked the first time I ran it. Now if I want to run it again it crashes my phone. Not sure what that is about.
Either way, now my understanding is that I should be able to download a rom for my phone and flash it. From that link that I was given, its very confusing.
Could someone PLEASE PLEASE help me here with this?
My phone is an AT&T US SG4. Here are the details:
SAMSUNG-SGH-I337
Android 4.4.2
BaseBand I337UCUFNC1
Kernel Ver 3.4.0-1125940
Build # KOT49H.I337UCUFNC1
Which ROM can I use for my phone? As long as its stock, I don't care which version, Google Play ROM or CY or Golden, whichever, as long as I get rid of this crappy Samsung and AT&T stuff off my phone.
Could someone please help me out here? I know that link says everything, but jeez, im trying to make sense of it, and so far, I got the phone rooted, but just cant figure out the ROM part.
Thanks...
I can't help with specifics as I don't need SS.
Make sure you have correct SS--3.72, afaik
Flash, I believe, to stock slot not rom slot but confirm that
Install Selinux app from Play and set Permissive--afaik
The above items are things people get into trouble with, so reconfirm them
Just keep reviewing the thread and the SafeStrap thread in Dev section by HashCode. Maybe go back more pages from end of threads as you have time. You can post in All things thread now for help and at 10 posts in Dev section. It will come together in time--:good:
Flash roms only for you build, think there is a list within that thread or another one in General or Q&A.
iB's Goldeneye 38 is good and you can use the Aroma to select SafeStrap and the Slimmed down version.
Read his SS flashing instructions first.
Make sure you use SafeStrap recovery to wipe ALL--System/Data/Caches before flashing--:good:
Cornelp: Having recently been through all this, I wrote up a short summary with some links for another user, and it might help you to look through it. It's an overview written from my end-user perspective, not a replacement for the detailed posts the devs have done.
However, based on your description, I would say the best thing to do is ODIN back to stock because I have a sneaking suspicious you got a bad OTA flash. It happens. Going back to stock will be the best way to eliminate that as a source of problems. Learn how in the All things ATT thread OP.
Best of luck to you!
Marc
Frankenscript said:
Cornelp: Having recently been through all this, I wrote up a short summary with some links for another user, and it might help you to look through it. It's an overview written from my end-user perspective, not a replacement for the detailed posts the devs have done.
However, based on your description, I would say the best thing to do is ODIN back to stock because I have a sneaking suspicious you got a bad OTA flash. It happens. Going back to stock will be the best way to eliminate that as a source of problems. Learn how in the All things ATT thread OP.
Best of luck to you!
Marc
Click to expand...
Click to collapse
Frankenscript,
Thank you very much, I will read up on that link you gave me. How would I ODIN back to stock? Do you have specific details on that? I did read something about that on the All things ATT, but wasn't clear.
Thanks...
Cornelp said:
Frankenscript,
Thank you very much, I will read up on that link you gave me. How would I ODIN back to stock? Do you have specific details on that? I did read something about that on the All things ATT, but wasn't clear.
Thanks...
Click to expand...
Click to collapse
Complete instructions here:
http://forum.xda-developers.com/showpost.php?p=51130818&postcount=5
Basically, download ODIN to your PC, run it, get phone into download mode, connect phone to PC via USB, in ODIN select the NB1 file, tell it to start. When done, reboot phone. Then flash the NC1 update from an SD card using stock recovery.
A good pictorial description of how to flash can be found in this S3 thread here:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
Though for a different phone (the S3, not our S4), the process is still the same.
Good luck. I'm headed off to a work trip and won't be on the forum much this week!
Frankenscript said:
Complete instructions here:
http://forum.xda-developers.com/showpost.php?p=51130818&postcount=5
Basically, download ODIN to your PC, run it, get phone into download mode, connect phone to PC via USB, in ODIN select the NB1 file, tell it to start. When done, reboot phone. Then flash the NC1 update from an SD card using stock recovery.
A good pictorial description of how to flash can be found in this S3 thread here:
http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
Though for a different phone (the S3, not our S4), the process is still the same.
Good luck. I'm headed off to a work trip and won't be on the forum much this week!
Click to expand...
Click to collapse
Thank you all. I was able to revert back to the NB1 stock, but it failed the first time. I had to download and install the NB1 Rootable Odin. For some reason, the NB1 Odin didn't work, but the Rootable one worked.
So im glad I was able to go back. Now I just gotta test it and see if it does slow down as it did before. I will post update, in case anyone else has the same problem, maybe this would be a good solution.
Thanks again to all of you guys, really appreciate it. I really hope it worked.
Hi guys, have a few questions...
For starters, I have a Samsung Galaxy S4 / AT&T
Running Android 4.4.2 Rooted with Towel Root
Connected on Straight Talk
~NC1
SafeStrap 3.72 (TWRP v2.7.0.0) Installed.
Im new to all this ROM/Modules and Rooting stuff.
Last time i fully customized stuff was on my Motorola RZR ages ago
making my keypad/ LED light blink with calls, and replacing the Cingular Logo
with a Pirate/2 Swords Logo. hah... good times.
I mean there was jail-breaking and whatnot but...that's easy stuff.
Any who, Im a quick learner so on to the subject.
My original idea was to FULLY customize this phone and install ROMS/other OS, thats
what im all about, customization. Sadly, i realized im on a NC1 which its Boot loader is
locked if im understanding correctly preventing me from installing other? ROMS?
However if i understood correctly, we still can install certain ROMS? Whats the difference?
Is there any ROM i can install that is clean? no bloatware? but with everything I need?
Whats the best, fastest and best looking ROM i can get? or they dont look different because the
boot loader thing? Or they can only be Samsung/AT&T roms? This stuff can be confusing. lol
Module wise, why do i need them? why arent they included in the actual ROM?
Also, is there any App/or way for me to know what causes my phone to randomly crash/reboot?
A few months ago I was at the GYM and my phone randomly shut off. It didnt want to turn back on.
After a while it turned back on, then it would randomly reboot. That eventually went away.
Last night, i was with some friends in a bar and my phone just turned off again. Didnt wanna turn
on...then the same reboot thing happened again.
Today, is working fine. I thought maybe it was an overheat issue but, i wasnt doing anything on my
phone and on top of that im using a CPU tempt program installed through xPosed and according to the
readings it wasnt hot, as it was in the 50-55c (or is that too hot?) Im at home now and its reading
36c but i dont have its case on (if that makes any difference)
There are 3 kind of "ROM"s :
1- Official ones. made by samsung. flashable via odin exclusively. not rooted
2- A bit modified (maybe more than a bit) Official ones, modified by people, flashable via odin or recovery (1), usually already rooted
3- Completely rewritten ROMS, almost made from scratch (Cyanogenmod, MIUI for exemple...), installable via recovery. already rooted
Now, your phone can be in two states : Rooted or not rooted.
From factory, your phone is not rooted (you can compare it to jailbreak)
with root, you become a "super user", which means you have rights on almost every single aspect of your phone, and you give authorisations to apps so they can act on system files (for exemple, they can get hidden informations, they can automatically install apps etc... infinite possibilites there are.)
As for the best rom there is, is like asking what is the best music ever, it depends on the user, you have to try by yourself to find the one that satisfies you the most.
For random reboots, i personally think that it is comparable to windows Blue Screen of Deaths. you maybe messed up something while installing something. your phone can't handle the bug, so it restart or shut down itself. so the safest way to get rid of this problem is to factory reset your phone (via the recovery)
if you are looking for stableness, don't opt for completely remade ROMS, they are usually experimental. but personally i use MIUI and i didn't have any problem and i love this ROM.
Hope i answered every question.
Thanks a lot for the reply.
I understand a bit better now...
That MIUI looks interesting... Reminded me of DreamPassport for my Sega Dreamcast, hah...
I'm guessing I cant install that one huh? Lol
well since you already have a custom recovery you can... just download a miui rom (one for your phone version (be carefull about the model) ) then put it on the root of your sd card, go to the custom recovery and flash zip from sdcard and choose it... but i advice you to factory reset your phone first in order to fix your reboot problem.
also, make sure you have installed the right android version before installing the equivalent miui version (for exemple if you want to install miui that requires 4.2, install an official 4.2 rom first) via odin.
Gotcha. Thanks.
One last question....
If I want my phone with the original OS it came with. But with all the bloatware removed...
which rom would be the best? , since I want the stock experience but no bloatware.
Also...
I noticed when you click to see how much ram is being used, it says
800/1.77GB
Isnt my phone suppose to have 2GB? Can I do something to get that back? is it cause the bloatware?
I appreciate the help.
Raging Tiger said:
Gotcha. Thanks.
One last question....
If I want my phone with the original OS it came with. But with all the bloatware removed...
which rom would be the best? , since I want the stock experience but no bloatware.
Also...
I noticed when you click to see how much ram is being used, it says
800/1.77GB
Isnt my phone suppose to have 2GB? Can I do something to get that back? is it cause the bloatware?
I appreciate the help.
Click to expand...
Click to collapse
I don't think the above information is correct.
From what I know the AT&T has a locked bootloader. So you can run custom roms, just not all of them. I think only custom roms that match the version you are using.
You could better read in the section for the AT&T (this section is for a different model).
http://forum.xda-developers.com/galaxy-s4-att
Hello,
I am not a phone expert by any means. I am probably in the 'knows just enough to be dangerous category,' but I am quite willing to learn. Here is my situation as I understand it. Please advise whether my premise is flawed.
Phone: rooted Verizon Note 3 KitKat NC4 off contract / pre-paid , no warranty
Ultimate Goal: to wipe my phone and have a clean slate. Bonus if I could be able to backup images of my phone for the future. Heheeeee.
Sitrep: phone is in need of a wipe/do-over to resolve some minor annoyances, but factory reset doesn't work. It says "System software not authorized by Verizon detected...please shove it," or something. That is curious, because, since I am trying to get rid of allllllllll the software, it should just let me do it if it doesn't like some of the software. I probably don't understand this fully. (Or else they just want me to go to Verizon so they can sell me a new/worse/more despotic phone.)
I only get that message if i try to reset it, not every time i turn it on, so it doesnt bother me, but i do want to reset it, because it is full of cobwebs and battery issues. From reading this forum, I think the reason it won't reset is that about a year ago, I installed clockwork and did *something* to the recovery, but it freaked out, because my boot loader wasn't (and still isn't) unlocked, so I uninstalled clockwork. I don't remember why I installed it. It was too long ago. I think i thought i could back up my rom or something. Anyway, it has worked fine ever since, I just can't wipe it and it tells me about unauthorized software. I found instructions on here about 'flashing back to stock kitkat with Odin,' which I gather will fix my recovery, and as long as I don't do that clockwork recovery thing again, I can reset it whenever I want to, on KitKat. (I am not interested in "upgrading.") I was all set to do that, when, last night, to my joy, I saw the Verizon note 3 boot loader unlock has arrived. That (I think) means that I can (eventually) unlock the boot loader and go back to jelly bean. Yay! Or cyanogen!! Yayay!
Question: shall I first reflash KitKat in Odin, so that the recovery is operational, THEN unlock it? Or can I unlock it first, even if the recovery is messed up, skip fixing KitKat, and go back to jelly bean (or maybe cyanogen)? I am afraid that there is a right order and a wrong order, and I'm sure to pick the wrong one.
Maybe these 2 things have nothing to do with each other. I have no idea. I just feel like I might be at a crossroad.
Thank you very much for helping a lady in somewhat unfamiliar territory.
Auralay
Auralay said:
Hello,
I am not a phone expert by any means. I am probably in the 'knows just enough to be dangerous category,' but I am quite willing to learn. Here is my situation as I understand it. Please advise whether my premise is flawed.
Phone: rooted Verizon Note 3 KitKat NC4 off contract / pre-paid , no warranty
Ultimate Goal: to wipe my phone and have a clean slate. Bonus if I could be able to backup images of my phone for the future. Heheeeee.
Sitrep: phone is in need of a wipe/do-over to resolve some minor annoyances, but factory reset doesn't work. It says "System software not authorized by Verizon detected...please shove it," or something. That is curious, because, since I am trying to get rid of allllllllll the software, it should just let me do it if it doesn't like some of the software. I probably don't understand this fully. (Or else they just want me to go to Verizon so they can sell me a new/worse/more despotic phone.)
I only get that message if i try to reset it, not every time i turn it on, so it doesnt bother me, but i do want to reset it, because it is full of cobwebs and battery issues. From reading this forum, I think the reason it won't reset is that about a year ago, I installed clockwork and did *something* to the recovery, but it freaked out, because my boot loader wasn't (and still isn't) unlocked, so I uninstalled clockwork. I don't remember why I installed it. It was too long ago. I think i thought i could back up my rom or something. Anyway, it has worked fine ever since, I just can't wipe it and it tells me about unauthorized software. I found instructions on here about 'flashing back to stock kitkat with Odin,' which I gather will fix my recovery, and as long as I don't do that clockwork recovery thing again, I can reset it whenever I want to, on KitKat. (I am not interested in "upgrading.") I was all set to do that, when, last night, to my joy, I saw the Verizon note 3 boot loader unlock has arrived. That (I think) means that I can (eventually) unlock the boot loader and go back to jelly bean. Yay! Or cyanogen!! Yayay!
Question: shall I first reflash KitKat in Odin, so that the recovery is operational, THEN unlock it? Or can I unlock it first, even if the recovery is messed up, skip fixing KitKat, and go back to jelly bean (or maybe cyanogen)? I am afraid that there is a right order and a wrong order, and I'm sure to pick the wrong one.
Maybe these 2 things have nothing to do with each other. I have no idea. I just feel like I might be at a crossroad.
Thank you very much for helping a lady in somewhat unfamiliar territory.
Auralay
Click to expand...
Click to collapse
It is because you are rooted... A factory reset just wipes user data and applications... It does not totally reload Android.
You can reflash the phone via Odin and a firmware download of the proper version (or higher) for the Verizon Note 3. Firmware is available on www.sammobile.com you have to be a member in order to download but membership is free.
If you want to stick with KitKat... You can unlock the bootloader now and then can load either CWM or TWRP and from them can flash any ROM available here.
Even unlocked i don't think you can move back to Jelly bean
Sent from my SM-N900V using Tapatalk
donc113 said:
It is because you are rooted... A factory reset just wipes user data and applications... It does not totally reload Android.
You can reflash the phone via Odin and a firmware download of the proper version (or higher) for the Verizon Note 3. Firmware is available on ] you have to be a member in order to download but membership is free.
If you want to stick with KitKat... You can unlock the bootloader now and then can load either CWM or TWRP and from them can flash any ROM available here.
Even unlocked i don't think you can move back to Jelly bean
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thank you so much for taking the time to consider my question. As sad as I am to think about not ever going back to Jelly Bean, which I assume is a tyrannical Verizon/Samsung thing, I am very glad for your input. I could have sworn I have reset this phone since rooting it, but I could just as easily be mistaken. I think I will do Odin first, and see everything is A-OK before leaping out into the unknown of unlocking. Hopefully after I do Odin, I can do resets the old easy way, but it's ok if i can't. Anyway, thanks a bunch for helping me get smarter every day. <3
Auralay
Auralay
Have you already flashed with Odin?
Hold your horses if not, I have an idea which is worth trying.
(It involves unlocking and reinstalling stock without losing root in the process.)