My S3 overheats and drains battery when I'm on a call and when I surf the net Are there apps that manage the phone so it doesnt heat a lot? Are there modems I can download that better manage the battery?
I'm not sure that the modem has much of a role to play in saving battery power.
I always recommend running the latest modem and bootloader to ensure compatibility with the latest custom ROMs.
audit13 said:
I
I always recommend running the latest modem and bootloader to ensure compatibility with the latest custom ROMs.
Click to expand...
Click to collapse
Hi audit. Well I'm not usong a custom rom. I'm using a rooted stock rom, whichbis JB.
But is it possible to install the latest bootloader and modem on JB? Would tjey be compatible? If so, where do I download them from?
The latest bootloader and modem for a T-Mobile phone is a jb. For a Canadian version, which is what I have, the latest modem and bootloader is kk. I don't think the two bootloader or modems are interchangeable.
I honestly can't think of a reason as to why the software would cause the heat issue.
audit13 said:
I honestly can't think of a reason as to why the software would cause the heat issue.
Click to expand...
Click to collapse
I think its got to do with busy box or process by which I rooted the phone. I say this because after I backed up and tried to restore my phone through a nandroid, the restore was a total mess. The restore was incomplete. Ever since then, the phone hasnt been the same. I then tried wiping the cache, dalvik, data, did a reset and reformatted the phone. And that didnt help at all. I'm as dumbfounded as you are about this.
You did a full restore via Odin and did a full wipe via stock recovery before first booting the phone?
Rooting should not cause a heat issue and I don't see how busy box would either.
audit13 said:
You did a full restore via Odin and did a full wipe via stock recovery before first booting the phone?
Rooting should not cause a heat issue and I don't see how busy box would either.
Click to expand...
Click to collapse
Well regardless, my trouble began after I did a restore and the restore wasnt an exact restore. So somewhere in the phone there lies a major bug especially when the restore wasnt an exact duplicate of the backup.
BTW, since I'm running JB and got the regular task manager, do you know how I can get the card stack-like task manager thats prevalent in Lollipop?
All I can recommend at this point is flashing back to stock, performing a factory reset via stock recovery, and use the phone unrooted to see what happens.
Sorry, not sure how to get the stacked manager,
audit13 said:
All I can recommend at this point is flashing back to stock, performing a factory reset via stock recovery, and use the phone unrooted to see what happens.
Sorry, not sure how to get the stacked manager,
Click to expand...
Click to collapse
But I flashed to stock like I told you before.
I know but I wasn't sure if you left it unrooted and tab it that way to see if things changed.
All I can say is mine gets warm during use but not hot.
audit13 said:
I know but I wasn't sure if you left it unrooted and tab it that way to see if things changed.
All I can say is mine gets warm during use but not hot.
Click to expand...
Click to collapse
I understand. I'll just leave it at that. Dont want to waste any more time than I already have on this phone. Not worth all the trouble.
Related
Update The likely culprit, at least for the "install button" problem, appears to be an app called Velis Auto Brightness. A little over three weeks after this problem first arose, I switched my ROM to Dandroid. In deciding what apps gradually to add back, I ran across comments like the following for Velis:
Cannot press install from an APK Found a bug that needs fixing. With this app enabled for some reason installing from an APK it renders the Install button useless but the cancel button still works. As soon as I disabled this App, the Install button worked again.
Click to expand...
Click to collapse
Nice, but one slight issue I really like this app. Very useful and easy to use. My only issue is that when the app is active, if I turn off system auto brightness and try to raise the brightness, Velis overrides this and forces auto brightness.
Click to expand...
Click to collapse
Recently, I had problems with my S3, on which I'd been running Stockorama v2. Starting July 3, the install button stopped working. The eventual solution, alas, was only temporary. I restored a June 27 nandroid and reinstalled apps, except for one that I suspected of causing the problem because it had only recently been installed before the problem occurred,
That worked for almost three weeks, until the phone function stopped working. Whatever telephone number I entered, the phone tried to call 333223. At that point, I had available to me a phone that couldn't make, but could receive, calls or, if I restored a different nandroid, a phone the seemingly functioned fully, except that I could not install any app that required pressing the on-screen install button.
From reading the latter thread and general considerations, I decided to do a clean reinstall of Stockorama. First, I wiped everything and used Odin to install mrRobinson's root66. I wiped again and used mobile Odin to install Stockorama v2. Before doing so, I backed up IMEI and EFS.
Reinstalling Stockorama was frustrating because the Aroma installer kept hanging. Late last night (early this morning), the installer completed. Leaving the phone plugged in to an electric outlet, I went to bed with the screen displaying "Samsung Galaxy SIII." I figured that, come morning, I'd be able to complete the process of setting up the phone.
Instead, I have some kind of brick. When I awoke and checked the phone, the screen had the same display as when I went to bed. Foolishly, perhaps, I thought that pressing the power button might help. It didn't.
Now, although the phone was continuously plugged in, pressing the power button first does nothing or, eventually displays a completely discharged battery with no indication that the phone is charging.
Pressing the power button just now with the phone unplugged again displayed "Samsung Galaxy SIII." FWIW, I've plugged the phone back in.
What to do next is a mystery to me, however.
As always, all advice is appreciated.
I managed to get into Download mode and am using Odin to install, again, root66. Assuming that succeeds, I expect I could use baby-step guidance to prepare the phone for and, once again, install Stockorama. Alternatively, at this point I'd consider another custom ROM that, like Stockorama, is lean and close to stock.
RebDovid said:
I managed to get into Download mode and am using Odin to install, again, root66. Assuming that succeeds, I expect I could use baby-step guidance to prepare the phone for and, once again, install Stockorama. Alternatively, at this point I'd consider another custom ROM that, like Stockorama, is lean and close to stock.
Click to expand...
Click to collapse
1) Aroma is notorious for freezing. Until the recent update, it could, at times, be pretty much unusable. This is not a problem with your device. The new update seems to have fixed those problems, but since Stockorama has not been updated, it is still using the old version.
2) Your issues sound a lot like malware (can't install, can't make outgoing calls). I'm not familiar with any Android malware, but crippling the phone's main functions seems like a good target.
3) You flashed root66 with Odin. Then go on to say you used Mobile ODIN to flash Stockorama. This would imply that your root66 setup was functioning before you flashed Stockorama. Is this true, or have I misunderstood you?
4) Describe to me your "complete wipe" process. Are you using the stock recovery's factory reset? Are you manually wiping the system partition as well? If not stock, what custom recovery are you using, and what version?
5) When you get stuck on the splash screen, you need to factory reset. But, going from one TW ROM to another TW ROM would not require this usually, and could be indicative of another issue. Like bad hardware.
6) If root66 is fine, and you are blaming the ROM, you could go for another one. I personally use S3Rx. I would try Dandroid if it had Wifi Calling. Don't see the point in using TW if I can't have Wifi Calling. Sorry. It's actually pretty handy to have with T-Mobile's less than stellar coverage when out of the city.
7) What firmware are you running? It's an educated guess that you are trying to use the MD5 root66, but what about your bootloader, baseband, rpm, rz, sbl? What versions are those?
Aerowinder said:
1) Aroma is notorious for freezing. Until the recent update, it could, at times, be pretty much unusable. This is not a problem with your device. The new update seems to have fixed those problems, but since Stockorama has not been updated, it is still using the old version.
Click to expand...
Click to collapse
Understood
2] Your issues sound a lot like malware (can't install, can't make outgoing calls). I'm not familiar with any Android malware, but crippling the phone's main functions seems like a good target.
Click to expand...
Click to collapse
You may be right. But I use both Lookout and Avast.
3) You flashed root66 with Odin. Then go on to say you used Mobile ODIN to flash Stockorama. This would imply that your root66 setup was functioning before you flashed Stockorama. Is this true, or have I misunderstood you?
Click to expand...
Click to collapse
Yes, root66 appeared to be functioning. I signed into my Google accounts; reinstalled Root Checker; checked root; and reinstalled Mobile ODIN.
4) Describe to me your "complete wipe" process. Are you using the stock recovery's factory reset? Are you manually wiping the system partition as well? If not stock, what custom recovery are you using, and what version?
Click to expand...
Click to collapse
It was late last night, and I didn't write down my steps. (My bad.) So far as I can recall, from the current TWRP recovery I checked all the available wipe boxes. After wiping, I then went into Download mode, connected the phone to my pc, started Odin, added root66 as the PDA, and clicked start.
I'm not sure what you mean by manually wiping the system.
In installing Stockorama, I chose the full wipe option.
5) When you get stuck on the splash screen, you need to factory reset. But, going from one TW ROM to another TW ROM would not require this usually, and could be indicative of another issue. Like bad hardware.
Click to expand...
Click to collapse
What kind of hardware problem could I have? How do I check?
6) If root66 is fine, and you are blaming the ROM, you could go for another one. I personally use S3Rx. I would try Dandroid if it had Wifi Calling. Don't see the point in using TW if I can't have Wifi Calling. Sorry. It's actually pretty handy to have with T-Mobile's less than stellar coverage when out of the city.
Click to expand...
Click to collapse
I'm not blaming the ROM. I'm simply at a loss.
Why do you use S3Rx? What do you like and dislike about it?
7) What firmware are you running? It's an educated guess that you are trying to use the MD5 root66, but what about your bootloader, baseband, rpm, rz, sbl? What versions are those?
Click to expand...
Click to collapse
I don't know what all the acronyms stand for. But this is what I can tell you.
From "About device," I'm running Android version 4.1.2 and Baseband version T999UVDMD5. The Kernel version is
3.0.31-1128078
[email protected] #2
SMP PREEMPT Mon Apr 15 11:59:10 KST
2013
The Build number is JZ054K.T999UVDMD5
RebDovid said:
Understood
You may be right. But I use both Lookout and Avast.
Yes, root66 appeared to be functioning. I signed into my Google accounts; reinstalled Root Checker; checked root; and reinstalled Mobile ODIN.
It was late last night, and I didn't write down my steps. (My bad.) So far as I can recall, from the current TWRP recovery I checked all the available wipe boxes. After wiping, I then went into Download mode, connected the phone to my pc, started Odin, added root66 as the PDA, and clicked start.
I'm not sure what you mean by manually wiping the system.
In installing Stockorama, I chose the full wipe option.
What kind of hardware problem could I have? How do I check?
I'm not blaming the ROM. I'm simply at a loss.
Why do you use S3Rx? What do you like and dislike about it?
I don't know what all the acronyms stand for. But this is what I can tell you.
From "About device," I'm running Android version 4.1.2 and Baseband version T999UVDMD5. The Kernel version is
3.0.31-1128078
[email protected] #2
SMP PREEMPT Mon Apr 15 11:59:10 KST
2013
The Build number is JZ054K.T999UVDMD5
Click to expand...
Click to collapse
This may not be the case on android, but I know on pc having mulyiple av programs causes all sorts of fun problems! Personally, I don't think any android av apps are worth anything.
Anytime you get hung up at the splash screen, you have to factory reset. If this were hw related it would do this regardless of your rom. And just to clarify, when moving between touchwiz roms, this can happen when when you go backwards from something like MD5 to LJA. This doesn't always happen, but it does happen.
Manually wiping means going into recovery and choosing wipe/format system before flashing your rom.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
This may not be the case on android, but I know on pc having mulyiple av programs causes all sorts of fun problems! Personally, I don't think any android av apps are worth anything.
Anytime you get hung up at the splash screen, you have to factory reset. If this were hw related it would do this regardless of your rom. And just to clarify, when moving between touchwiz roms, this can happen when when you go backwards from something like MD5 to LJA. This doesn't always happen, but it does happen.
Manually wiping means going into recovery and choosing wipe/format system before flashing your rom.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I failed again with Stockorama. To get a working phone, I restored my root66 nandroid.
At all relevant times, I've been on MD5.
I wonder whether I should try:
(a) restoring stock and trying (i) Stockorama or (ii) S3Rx; or
(b) installing S3Rx.
Before trying either, or something else, I'll pull the PIT file for you. Please just give me instructions.
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )
Hi everyone.
I’m currently on rooted SGH-i747M(Rogers) 4.1.2, and I'm trying to find out how to upgrade to 4.4.2 and keep it rooted.
Since my device is already rooted it won’t let me update to the latest firmware.
What would be the proper procedure to move to 4.4.2 rooted?
and does it worth it to upgrade to 4.2.2? I'm asking because I've seen posts on how to downgrade to 4.1.2 from 4.4.2.
Thanks so much in advance.
Once you upgrade to 4.3 or 4.4.2, you cannot downgrade to anything before 4.3.
Is your phone carrier unlocked? If not, I suggest downgrading to 4.1.1, unlock it, then start upgrading the stock ROM.
The easiest way would be to flash back to stock non-rooted 4.1.1, unlock it, and start updating via OTA or use desktop Odin to flash a stock Rogers ROM from sammobile.com.
stssific sarah
audit13 said:
Once you upgrade to 4.3 or 4.4.2, you cannot downgrade to anything before 4.3.
Is your phone carrier unlocked? If not, I suggest downgrading to 4.1.1, unlock it, then start upgrading the stock ROM.
The easiest way would be to flash back to stock non-rooted 4.1.1, unlock it, and start updating via OTA or use desktop Odin to flash a stock Rogers ROM from sammobile.com.
Click to expand...
Click to collapse
Thanks alot for the tips!
I'm on Rogers and I don't remember doing any unlocking.
So do I download the stock 4.1.1 also from sammobile.com and use Odin to downgrade to it?
And after I unlock it on 4.1.1, do OTA update to 4.4.2., and then root it?
newbie386 said:
Thanks alot for the tips!
I'm on Rogers and I don't remember doing any unlocking.
So do I download the stock 4.1.1 also from sammobile.com and use Odin to downgrade to it?
And after I unlock it on 4.1.1, do OTA update to 4.4.2., and then root it?
Click to expand...
Click to collapse
Exactly. That's what I did with my Bell s3. Make sure you are not rooted and running stock recovery before running OTA updates.
audit13 said:
Exactly. That's what I did with my Bell s3. Make sure you are not rooted and running stock recovery before running OTA updates.
Click to expand...
Click to collapse
On 4.1.1 what unlocking method did you use?
http://forum.xda-developers.com/showthread.php?t=2176719
This is my experience with the T999 model but it should be the same here. Personally I hate otas, so I avoid them if at all possible.
You shouldnt need to flash the full 4.1.1 firmware to do the unlock. Just the modem. Then flash the 4.4.2 firmware via odin after unlocking. Reroot and youre done.
Nothing wrong with how audit13 suggested btw. Itll work that way too. Just offering an alternative.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Thanks to you all, I'm now on rooted 4.4.2 with CWM.
One thing I missed is to backup the rom using CWM. I've already restored all my previous apps and data using Titanium Backup, and I had to go through a lot of troubleshooting with errors like *Unfortunately ***** has stopped." I think everything's working well now though. Should I still do backup in CWM or is backing up with TB enough?
My second question is that it seems to drain battery more. When I wake up this morning the battery was only at 85% or so. I have it plugged in now but it's charging very slow. Is this a known issue with a fix?
Did you restore data and settings for system apps? If so, this can cause issues if done from one build to another, such as battery drain, force closes and degraded performance.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Did you restore data and settings for system apps? If so, this can cause issues if done from one build to another, such as battery drain, force closes and degraded performance.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I did TB-> Batch Actions -> Restore all apps with data. Right below there is 'Restore all system data' which I didn't do, but I'm not sure if that 'all' includes system data as well?
The selections under Restore section in Titanium Backup were the following:
RUN: Restore missing apps with data
RUN: Restore all apps with data <<=== this is what I did
RUN: Restore all system data
RUN: Restore missing apps + all system data
RUN: Restore newer versions of user apps
I recharged to 100% then performed a Battery Calibration using an app, but 20% just got drained in an hour and half of pretty much all standby time(screen off).
I would factory reset, reboot and let it sit for a few minutes. Then using titanium, restore only essential apps and data first. You should be able to use the batch restore and then select from a list what you want to include. Test for a bit to see if anything you restored causes problems. If not restore a few more and test. Do this until you narrow down what is causing your problems.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
You're right. I should just do that.
I was following the root method at galaxys3root.com, and the files I was told to use were UPDATE-SuperSU-v2.01, Odin3 v1.85 and CWMS3ATTrecovery.tar in which there was image.img without any version number.
I did some digging and found Odin3 v3.09 which seems to be the latest version. Then I went to http://www.clockworkmod.com/rommanager to download the CWM from the original source, but they're all img files and odin wants a tar file. How do I put this into a tar file, and do I need to rename any? I just want to do everything right this time. Would DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V2.1 be a good idea as well?
edit: oh never mind I went into the CWM and saw the version was 6.0.4.7 which is the latest. So I'll just use the same files again for root.
I just did a factory reset, and the CWM and the root as well as superSU are not lost. Is this normal? I thought factory reset takes away the root... Also I just checked in download mode that the Warranty Bit is now 1. It was 0 when I first rooted, so I'm guess the resetting might have done that. Oh well...
Custom recoveries and kernels are what usually trip the warranty bit, so if you installed cwm, thats what tripped it. I wouldn't worry too much over it. Warranty claims are pretty rare, and a lot of people have reported their warranty was honored even though the bit was tripped.
Root will remain after resetting because it is on the system partition. Factory reset only wipes /data.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
After factory reset I only restored some of the apps this time, and for many of them I restored only the data. But this battery drain issue is still there. It not only drains battery but in the morning when I woke up the lock screen didn't want to come on. I pressed the power button, and the three physical buttons' LED lights were lit but the screen remained blank. It took a long time until the lock screen comes on but it didn't respond to touch, acting very very laggy until I reboot. I tried wiping dalvik cache(although I wasn't quite sure what it was) in restore mode but it didn't help.
I learned about battery drain monitor apps and downloaded Wakelock Detector. It was showing that my AVG Antivirus Pro is awake all the time taking a lot of battery, and I'm not quite sure if it's supposed to be that way since it should be running in the background all the time. But this seem to be still too much. Can I just assume at this point that the Antivirus is what's causing the issue?
I've seen others recommend wakelock detector, but I'm not familiar with it myself. But I doubt your AV should be using that much, nor should Android System. But a dead giveaway that there's a problem lurking is it only spent 1 second in deep sleep. And 7.5 hours awake with the screen off.
Looking at the wld screen, it certainly seems like AVG is the problem, or at least a big part of it! I'm not sure it's the only one though with your system use being so high in the first screen shot.
I'd suggest uninstalling AVG and test it at least for one full cycle. Also, look to see if wld is able to log kernel wakelocks. In better battery stats you have to set it to do so in settings if I remember right.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
never had this problem first here is all the background information from my last thread (yes i must be challenged)
really I don't know what to do
I believe i need to completely erase everything from my device as i cannot think of what else it could be but some conflicting something somewhere I am not educated enough to know
it flashes fine with odin but always system ui error I will be trying to go back to 4.1X as i believe that was my last bootloader and hope it works out. In all i want to update to NC2 and take advantage of the last roms beuing developed for this device.
In all i want to get my phone working again i need to get and send calls and texts so i plead for help Any question i will answer to the best of my ability
I have flashed with odin 3.1 and 3.07 NC2 then MJC basically both root 66 4.3 roms I don't know what my problem is maybe if while im waiting for help and using a root 66 for 4.1.2 (last working state) i will use recovery to wipe the sd card? idk but in all i think i need to start FRESH as long as i can get my contacts from Google i'm fine (and the phone rings and such lol)
IM eagerly waiting for help!!! someone else who is having a crappy holiday season maybe you can relate when you get in a funk where it seams everything breaks or needs to be replaced at one time
TUIA
You can't flash back to 4.1 with Odin. Root66 performs a full update including bootloader so no downgrade. You probably just need to factory reset with recovery. Just make sure you backup your internal sd
serio22 said:
You can't flash back to 4.1 with Odin. Root66 performs a full update including bootloader so no downgrade. You probably just need to factory reset with recovery. Just make sure you backup your internal sd
Click to expand...
Click to collapse
Thanks for sticking in there with me i did a factory reset using the recovery (i guess the android recovery) deleted data and cache which deleted all the apps which were messing things up so now it booted up like a brand new phone my contacts are back via Google and that's all i care ill be installing a rom and such soon but idk im starting over it works and upgrade
thank you a lot for sticking with me serio22 all i can do is thank you for all your posts but if i had the means id buy you a beer or something man
No problem man, glad it's fixed!
BeatnikBandit said:
Thanks for sticking in there with me i did a factory reset using the recovery (i guess the android recovery) deleted data and cache which deleted all the apps which were messing things up so now it booted up like a brand new phone my contacts are back via Google and that's all i care ill be installing a rom and such soon but idk im starting over it works and upgrade
thank you a lot for sticking with me serio22 all i can do is thank you for all your posts but if i had the means id buy you a beer or something man
Click to expand...
Click to collapse
http://forum.xda-developers.com/and...-rendering-t3003534/post58190052#post58190052
Try this
I have a T-Mobile Note 3, all stock, not rooted. I recently installed the lollipop update, and now my screen rotation stops working.
A reboot fixes it, but it will stop working again later in the day.
I have auto rotate on, smart rotate is not on, auto brightness is on (a search said this worked but it was for an older firmware).
Has anyone seen this or possibly know a good fix?
Wow, nobody else has seen this?
WatermelonSlim said:
I have a T-Mobile Note 3, all stock, not rooted. I recently installed the lollipop update, and now my screen rotation stops working.
A reboot fixes it, but it will stop working again later in the day.
I have auto rotate on, smart rotate is not on, auto brightness is on (a search said this worked but it was for an older firmware).
Has anyone seen this or possibly know a good fix?
Click to expand...
Click to collapse
hello
i had a few issues when i upgraded from 4.4.2 to 5.0 stock lollipop... first of all check if the baseband shows same as the build name.. it should both finish in OB6 ....also try booting the phone in safe mode to see if its and app/tweak error... u could also try a factory reset or a full factory reset from recovery screen with a full wipe and cache and dalvik cache erased but i dont know if its possible in stock android recovery since first thing i do when i unbox the phone is to root... always running rooted and with custom recoveries since i like to mod and tweak my phone i suggest you to try to root and release your phone full potential hope this works for you.
Sent from my SM-N900T using XDA Free mobile app
Reinstalling the lollipop firmware may correct it.
Odin, Kies or whatever method you used, try a reinstall.
Pp.
PanchoPlanet said:
Reinstalling the lollipop firmware may correct it.
Odin, Kies or whatever method you used, try a reinstall.
Pp.
Click to expand...
Click to collapse
I just went to Settings, General, About Device, Check for Updates and installed it from there. When I go there now it says the device is up to date, so no way to do it the same way as the first time.
Tostido has a full firmware zip available, you can download extract and reflash using Odin 3.09.
Find it here http://forum.xda-developers.com/showthread.php?p=59257327
This will reinstall the latest update and should correct rotation problem.
Pp.
Funny thing is my wife has the same issue on hers. I guess we'll both have to reflash.
Is there a way to flash that toastido version without losing everything? I have a bunch of apps installed, pictures, memos to myself, etc.
WatermelonSlim said:
Funny thing is my wife has the same issue on hers. I guess we'll both have to reflash.
Is there a way to flash that toastido version without losing everything? I have a bunch of apps installed, pictures, memos to myself, etc.
Click to expand...
Click to collapse
sure there is... i suggest you to root your device... its very easy and means no harm unless you start playing with system stuff but basically it just unleash your phone full power.... and once you rooted you just install titanium backup which is the best back up ever (in my opinion) and u do a full system data/user data back up which it will save ALL phone and apps settings and data and you just save the titanium back up folder to your pc and then put it back once you done flashing... also be careful once u flash and you are reverting the back up since the error might be a misconfiguration somewhere... but u can choose manually which stuff u wanna restore like accounts messages phone call history and more... also remember to root back again and installing a custom recovery like TWRP or CWM so i can flash stuff and back up and get a better recovery experience and also u could flash the SD card write fix since on newer versions phone wont let you write data directly to a SD card.... hope it helps at all and good luck
Sent from my SM-N900T using XDA Free mobile app