Back in December while i was still on 6.0.1 but on the latest monthly update at the time, I have known for awhile that there was a high android system battery drain after the february 2016 monthly update so I wanted to downgrade back to February. But when I was in the process of downgrading, I got an error on odin and it failed. After I restarted my phone I got a message saying "an error has occurred while updating the device software. Use emergency recovery function in the smart switch pc software" so at that time i was freaking out a bit and I went searching around and people said around may of 2016 samsung updated the bootloader so you couldn't downgrade to an earlier month that had the older bootloader.
I just want to know if samsung has updated their bootloader since 7.0 being on the latest bootloader. I'm currently on August security patch and want to go back to March.
I was using, if I'm not mistaken, the Android 7.0 July patch and I wanted to do an experiment. So, I downloaded version 6.0.1 and flashed using Odin.
Everything went through smoothly!
Just a curiosity, why do you want to go back to March? There are no benefits rolling back to an older patch, unless you want to test something.
Also, people say everywhere that their batteries are X with Y update and then, with Z, it got worse (or better). It actually depends on your usage, what apps you have installed, how you use your phone, etc etc etc.
Ah! My S7 Edge is the Exynos version.
Regards
angourakis said:
I was using, if I'm not mistaken, the Android 7.0 July patch and I wanted to do an experiment. So, I downloaded version 6.0.1 and flashed using Odin.
Everything went through smoothly!
Just a curiosity, why do you want to go back to March? There are no benefits rolling back to an older patch, unless you want to test something.
Also, people say everywhere that their batteries are X with Y update and then, with Z, it got worse (or better). It actually depends on your usage, what apps you have installed, how you use your phone, etc etc etc.
Ah! My S7 Edge is the Exynos version.
Regards
Click to expand...
Click to collapse
I've had a serious kernel battery drain and i've tried whatever I could to fix it. It just started out of nowhere and I can't think of any apps that would cause it to continue and so my battery life has been horrible and it doesn't even go into doze half of the time and I also has forcedoze enabled.
If you were able to go back to 6.0.1 without having an error in odin, then what did i do wrong? I put all the right files in the right place.
orlans21 said:
I've had a serious kernel battery drain and i've tried whatever I could to fix it. It just started out of nowhere and I can't think of any apps that would cause it to continue and so my battery life has been horrible and it doesn't even go into doze half of the time and I also has forcedoze enabled.
Click to expand...
Click to collapse
What model is your phone? What country?
Battery drain, doze not starting... it's normally caused by apps.
Post a screenshot from Settings -> Device Maintenance -> Battery -> Battery Usage
angourakis said:
What model is your phone? What country?
Battery drain, doze not starting... it's normally caused by apps.
Post a screenshot from Settings -> Device Maintenance -> Battery -> Battery Usage
Click to expand...
Click to collapse
sm-g935w8 (canada) right now im currently backing up apps and other stuff in smart switch so it is charging but im getting like close to 3 hours of SOT when I used to get 6 hours back on 6.0.1 february and 4 hours on the first 7.0 (march)
Android OS has a high stay awake.
orlans21 said:
sm-g935w8 (canada) right now im currently backing up apps and other stuff in smart switch so it is charging but im getting like close to 3 hours of SOT when I used to get 6 hours back on 6.0.1 february and 4 hours on the first 7.0 (march)
Android OS has a high stay awake.
Click to expand...
Click to collapse
Ohhh Canadaaa \o/
What I would suggest is to start from scratch, without restoring any backup.
If you want, you can download the current and older versions from here: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935W8/
I'm also on August security patch and I consistently get 7h+ SOT but I disable preloaded apps, (especially Facebook), use the resolution in HD and a black theme to get the benefits of the AMOLED screen.
When using Odin, make sure you put everything on the right place and use CSC file instead of HOME_CSC. It will delete all your data!
angourakis said:
Ohhh Canadaaa \o/
What I would suggest is to start from scratch, without restoring any backup.
If you want, you can download the current and older versions from here: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935W8/
I'm also on August security patch and I consistently get 7h+ SOT but I disable preloaded apps, (especially Facebook), use the resolution in HD and a black theme to get the benefits of the AMOLED screen.
When using Odin, make sure you put everything on the right place and use CSC file instead of HOME_CSC. It will delete all your data!
Click to expand...
Click to collapse
I also have apps disabled or at least HAD them disabled..i've might have enabled them except the ones i know for sure i dont need like facebook, chrome and those microsoft apps...you get the idea. I use HD resolution and keep it on black or dark theme. I use substratum and have whatever apps are supported themed to black.
Also why not home_csc if im starting from scratch?
orlans21 said:
I also have apps disabled or at least HAD them disabled..i've might have enabled them except the ones i know for sure i dont need like facebook, chrome and those microsoft apps...you get the idea. I use HD resolution and keep it on black or dark theme. I use substratum and have whatever apps are supported themed to black.
Also why not home_csc if im starting from scratch?
Click to expand...
Click to collapse
HOME_CSC will not wipe /data, CSC will. I may be crazy, but I erase things the maximum I can, so: I factory reset before updating to a new version, I use the CSC file to flash via Odin and I factory reset after I've updated. Then I log in to my Google account and start installing my apps from Play Store.
Of course I don't do it monthly (because security patches make no drastic changes). I only do it when there's a huge update (like Android 6.0 to 7.0) or when I feel the phone becomes sluggish (because I've installed and uninstalled lots of apps, for example).
When I had my Nexus 6, I also used fastboot commands and TWRP to garantee it's 100% clean (yep, you can now shout * crazy dudeeee *)
angourakis said:
HOME_CSC will not wipe /data, CSC will. I may be crazy, but I erase things the maximum I can, so: I factory reset before updating to a new version, I use the CSC file to flash via Odin and I factory reset after I've updated. Then I log in to my Google account and start installing my apps from Play Store.
Of course I don't do it monthly (because security patches make no drastic changes). I only do it when there's a huge update (like Android 6.0 to 7.0) or when I feel the phone becomes sluggish (because I've installed and uninstalled lots of apps, for example).
When I had my Nexus 6, I also used fastboot commands and TWRP to garantee it's 100% clean (yep, you can now shout * crazy dudeeee *)
Click to expand...
Click to collapse
I used to restore all my apps that way too but the last factory reset i did I just restored backup but this time ill do it that way. So now then i gotta take screenshots of where all my apps are placed on my home screen
So I attempted it and it is a success!
Related
I just updated to 4.4 yesterday, now battery life is horrible and tethering is broken. This is the weakest update I've seen since I moved to Android with the N1 launch. Other than the boot animation and a slight boost in wifi speeds I'm really not seeing any redeemable qualities in Kit Kat. I want to go back to 4.3 and block the OTA. What's the best way to do it? Is there any way to stay really close to stock rooted and do that? I'd prefer not to use any highly customized and buggy ROMs but if I have no choice I'll do what I have to.
Any suggestions?
GorillaPimp said:
I just updated to 4.4 yesterday, now battery life is horrible and tethering is broken. This is the weakest update I've seen since I moved to Android with the N1 launch. Other than the boot animation and a slight boost in wifi speeds I'm really not seeing any redeemable qualities in Kit Kat. I want to go back to 4.3 and block the OTA. What's the best way to do it? Is there any way to stay really close to stock rooted and do that? I'd prefer not to use any highly customized and buggy ROMs but if I have no choice I'll do what I have to.
Any suggestions?
Click to expand...
Click to collapse
I'm no expert but surly this would be a case of using something like Wugtool kit and revert to stock, then simply unlock the bootloader and flash a custom recovery this will block the update.
slugger09 said:
I'm no expert but surly this would be a case of using something like Wugtool kit and revert to stock, then simply unlock the bootloader and flash a custom recovery this will block the update.
Click to expand...
Click to collapse
I was already rooted and had a custom recovery on stock 4.3 but read that OTA would still be applied unless a custom kernel was installed or other major differences. I also couldn't tell whether the OTA will just fail and not be applied or if the error encountered would fubar my phone.
GorillaPimp said:
I was already rooted and had a custom recovery on stock 4.3 but read that OTA would still be applied unless a custom kernel was installed or other major differences. I also couldn't tell whether the OTA will just fail and not be applied or if the error encountered would fubar my phone.
Click to expand...
Click to collapse
as long u have custom recovery, the ota will still popup but no install, if i remember to block ota popup u need custom kernel
edit: the error on ota install would háppen b4 the ota would do anyting to the phone.
you do know that you can not judge battery life from one or two of the first battery cycles with a rom, right? first boot is when the device does most of its syncing, and you will get the worst battery life. not until the 3rd or 4th battery cycle will you actually see what the battery life is really like. and tethering isnt broken, the default tethering option works fine. third part tethering apps could be broken in 4.4, until they fix things.
opssemnik said:
as long u have custom recovery, the ota will still popup but no install, if i remember to block ota popup u need custom kernel
edit: the error on ota install would háppen b4 the ota would do anyting to the phone.
Click to expand...
Click to collapse
Thanks! What I needed to know.
simms22 said:
you do know that you can not judge battery life from one or two of the first battery cycles with a rom, right? first boot is when the device does most of its syncing, and you will get the worst battery life. not until the 3rd or 4th battery cycle will you actually see what the battery life is really like. and tethering isnt broken, the default tethering option works fine. third part tethering apps could be broken in 4.4, until they fix things.
Click to expand...
Click to collapse
I'll give it a few days on the battery unless it's out of control. My biggest concern was that it was charging at a slower rate. For the first 8 hours it couldn't do more than maintain current charge level while charging with my MBP. It seems to have overcome that now. I checked usage and couldn't see any heavy syncing.
Many thanks on the tethering. I was using stock tethering but couldn't get any traffic to get to the phone or past it but DHCP was working. After reading your comments I tried again, this time with another Android device and it worked. I want to say I had a similar problem before tethering a Win8 system so I will investigate that more.
Thanks again for all the replies. Really appreciate it.
Update
I thought I was OK with KitKat until I saw the stock email app had been updated to look just like the awful Gmail app. K9 won't work with my exchange accounts so after failing to get the earlier stock email (4.1) to work in KitKat I went back to 4.3. After a week I got nagged by OTA alerts. For others in search of a fix for BLOCKING OTA UPDATES ON THE NEXUS 4, I BLOCKED OTA UPDATES by following this great thread http://forum.xda-developers.com/showthread.php?t=1998378
I installed FOTAKILL, changed permissions, wiped the caches in recovery and renamed the otacerts.zip in /system/etc/security/ (using ES with root and mounting system with RW - plenty of other ways to do this) and no more hard update notification that you can't swipe away. There's a service manager you can try out also but reviews seemed spotty - read the linked thread for more info. Best of all I can use my phone and not be forced to use $h!tShat and I don't have to spend hours researching ROMs and kernel combinations and their respective bugs. Hope this info helps someone else. I couldn't get any hits searching for fixing the OTA problem with the N4 but the Nexus7 instructions have carried over to the N4 pretty well.
As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!
Having problem flashing MM?
Use this method:
Reboot to twrp
2. Full wipe (data, internal card, system, cache, delvik cache, format data) All zip move to external card for a clean flash
3. Flash V2 zip - robalm's thread
4. Flash boot zip - autoprime's thread
5. Flash https://mega.nz/#!gxtwVBwZ!41S8Woy2y...HhK4gcGooK7OIo permissive zip (most important part don't forget to flash this)
6. Flash betasupersu 2.52 https://mega.nz/#!F8E02RyC!XeJhx4QZH...bVd14ccRYHbNKg ( no other version worked only this version worked)
7. Flash sharpening mod 3.5 and reboot system
To me this method works 100%
I've tried on 5 of my friend's G3 and all without fail!
4G ,Titanium and ext card works flawlessly
Reserved
Singaporean user here, so far it's been fantastic on stock marshmallow. With 21c modem there's no problem when it comes to connectivity (I'm on Singtel and I get 4G just like on Lollipop). Battery life much better than lollipop (average about 3.5-4h SOT compared to 2.5-3h on lollipop).
Here's a features review I did for the new stock MM
oceangreen said:
As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!
Click to expand...
Click to collapse
Sorry to ask but really all International Model D855 got MM update or only Poland ? Please confirm.
OTA in Poland for D855 only
krk2krk said:
Sorry to ask but really all International Model D855 got MM update or only Poland ? Please confirm.
Click to expand...
Click to collapse
currently only Poland has update via OTA or LG PC Suite. However, there are zip files and KDZ files available that you can flash on any D855.
oceangreen said:
Having problem flashing MM?
5. Flash https://mega.nz/#!gxtwVBwZ!41S8Woy2y...HhK4gcGooK7OIo permissive zip (most important part don't forget to flash this)
6. Flash betasupersu 2.52 https://mega.nz/#!F8E02RyC!XeJhx4QZH...bVd14ccRYHbNKg ( no other version worked only this version worked)
7. Flash sharpening mod 3.5 and reboot system
Click to expand...
Click to collapse
Hi oceangreen,
Saw this thread late. Black screen, Red & Blue LED flashing problem after following autoprime's thread.
Some questions:
Step 5 - autoprime didn't have this! However, your Megasync link requires decryption key? Can u provide?
Step 6 - Is this the same as autoprime's SuperSU 2.52?
Step 7 - Is this the correct link to the sharpening mod 3.5 (http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648)? autoprime did not provide this! If I have no issues with the sharpening issue, can I skip this?
Thks in advance.
Is this still MM if use 21c modem ?
Preter said:
Hi oceangreen,
Saw this thread late. Black screen, Red & Blue LED flashing problem after following autoprime's thread.
Some questions:
Step 5 - autoprime didn't have this! However, your Megasync link requires decryption key? Can u provide?
Step 6 - Is this the same as autoprime's SuperSU 2.52?
Step 7 - Is this the correct link to the sharpening mod 3.5 (http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648)? autoprime did not provide this! If I have no issues with the sharpening issue, can I skip this?
Thks in advance.
Click to expand...
Click to collapse
This thread really need updating - or at least a sticky note to say that the better thread to use is http://forum.xda-developers.com/lg-g3/development/stock-t2961073/page252
Answer to some of my own questions:
Here are the mega links without requiring key
https://mega.nz/#!gwFhDAIb!ElPjTOntE...nGotozKUyypoAU
https://mega.nz/#!M5tkgDoR!eWGHs5O29...7uP6fiW-8pOwbw
you don't need sharpening mod if you use v2.52 see http://forum.xda-developers.com/lg-g...ables-t3282012. with this method it's simple & root sticks
The SuperSU 2.52 is the same based on the hash files.
fOxunO said:
Is this still MM if use 21c modem ?
Click to expand...
Click to collapse
yes, modem only affects cellular and things like that. The rom is still MM
Does it have volte with sg telco
Followed the flashing guide to the letter - this V2 rom is great - but for only about 3 days.
After around the 3 day mark, the error message will flash "SIM card removed The mobile network will be unavailable until you restart with a valid SIM card inserted."
The phone will reboot within 10 seconds (even if you go to airplane mode immediately). It rebooted repeatedly first time it happened.
Did a complete nuke wipe, flashed again. Same thing - at the 3 day mark - the Singtel SIM will show the same error and reboot. After that, SIM not usable at all. All telco signals (Singtel) will be gone. No phone, SMS, let alone data of any sort.
Think it is the problem with the modem.
http://forum.xda-developers.com/lg-g3/development/stock-t2961073
(Download v2 (modem from v21c) -> https://mega.nz/#!OIlwGLKS!LlcNIImHK...EzSt_ikHlWj3yY)
Tried flashing 21A, 21B, autoprime's hybrid modem. Doesn't work. Anybody else encountered similar problems?
Flashed on TWRP 2.8.7 from Stock Kit Kat 4.4.2.
Preter said:
Followed the flashing guide to the letter - this V2 rom is great - but for only about 3 days.
After around the 3 day mark, the error message will flash "SIM card removed The mobile network will be unavailable until you restart with a valid SIM card inserted."
The phone will reboot within 10 seconds (even if you go to airplane mode immediately). It rebooted repeatedly first time it happened.
Did a complete nuke wipe, flashed again. Same thing - at the 3 day mark - the Singtel SIM will show the same error and reboot. After that, SIM not usable at all. All telco signals (Singtel) will be gone. No phone, SMS, let alone data of any sort.
Think it is the problem with the modem.
http://forum.xda-developers.com/lg-g3/development/stock-t2961073
(Download v2 (modem from v21c) -> https://mega.nz/#!OIlwGLKS!LlcNIImHK...EzSt_ikHlWj3yY)
Tried flashing 21A, 21B, autoprime's hybrid modem. Doesn't work. Anybody else encountered similar problems?
Flashed on TWRP 2.8.7 from Stock Kit Kat 4.4.2.
Click to expand...
Click to collapse
I have the same problem as you. except, I did not do the update and it happened out of the blue today. Been restarting my phone and if I am lucky, sometimes I get connected to the network for about an hour before the error comes on again.
matthewmax09 said:
I have the same problem as you. except, I did not do the update and it happened out of the blue today. Been restarting my phone and if I am lucky, sometimes I get connected to the network for about an hour before the error comes on again.
Click to expand...
Click to collapse
Hi Matthew,
Saw your PM. Just to confirm that you have the same problem.
Error message - "The mobile network will be unavailable until you restart with a valid SIM card inserted"
- Bar counts up to 100% before phone reboots automatically
This is apparently a very serious problem with Android going back a few years and a few Android OS versions (KK I believe). It happens with various phone models ranging from:
LG G4
https://www.reddit.com/r/lgg4/comments/43p26p/sim_card_removed/
Nexus - Google doesn't give a F*CK
http://androidforums.com/threads/sim-card-problems.467384/
Motorola, Nexus, Samsung Galaxy etc.
https://code.google.com/p/android/issues/detail?id=66964
Google apparently doesn't give a rat's ass about it. As such it is very difficult to pin-point the problem. I have flashed & re-flashed robalm's V2 ROM at least 4 times, each time with a complete (nuke) wipe of everything including the Internal SD card. It definitely happens on the default modem (21C supposedly) that comes with it. Different modems have not helped. If you find one that works, let me know.
It cannot be a SIM card problem. Cos I've never ever taken it out since the day I got the phone. Once the problem happened, I've tried re-seating it, wiping the electrical contacts with microfibre cloth etc. Singtel shop customer service checked all the APN and network settings and confirmed it is correct, asked me to try the SIM card in other phones. Done that, nothing wrong with the SIM..
Googling further, some folks discovered that it is due to Google Apps (Play Store, Maps, G+, Gmail, Play Books/Games/Movies/Music/Services etc. etc.), which are system apps (as part of the ROM package), causing the problem after they are updated via Google Play Store. Don't we all update apps to the latest version, no?
I tried uninstalling all the updates for all of them (Settings>>Apps>>) and replacing them with the factory updates that came with the ROM. I usually freeze all the crap money sucking subscription based or in-app purchasing Google Apps that I don't use anyway. However, whether frozen or not, it still happens. Although not freezing any of them does seem more likely to cause the problem to become even more severe - like going into constant reboots as opposed to intermittent ones. When that happens, you have to go to airplane mode BEFORE the countdown completes and reboot happens. At least when it restarts, it won't hunt for the missing cellular signal and triggering another reboot. This then allows you to freeze the suckers more agressively.
It worked for a few days - I thought I had narrowed the problem down to Google Play Store, Play Framework and Play Services. But yesterday or so it has come back again with a vengeance. Freezing Google Play Store does not help by the way - besides what's the point if you can't use Play Store?
Problem is, disabling the auto-update functions on Google Play Store using:
(Play Store>>Settings>>General>>Auto-update apps>>check "Do not auto-update apps")
doesn't stop Google Play Store and Google Play services from auto-updating themselves! F*ck Google! You cannot prevent it no matter what.
Worse, everytime it auto-updates itself (or if you uninstall updates) - note that it will switch to the default setting of "Auto-update apps over Wi-Fi only" again. So you have to be fast in going to Settings in Google Play each time you reboot and open Play Store.
Some netizens have suggested ADB command line means to cripple the auto-updating. But to me that is not the freaking point. It's about trying to isolate and find the problem.
You end up uninstalling updates for Play Store several times a day but when you find that the cellular signal is gone (no bars), you realise that it has sneakily updated to 6.0.5.
But even when I uninstall all updates for Play Store. It can still happen. Maybe less frequently.
No cellular signal is bad enough. The worst aspect is the rebooting. I tried restoring my beloved KK 4.4.2 Nandroid backup but apparently I'll have to find a compatible modem again as TWRP 2.8.0 (or my previous version before upgrading to TWRP 2.8.7 for this Marshmallow) didn't manage to back it up (even though I tick everything).
Still doing trial and error to try isolating the problem. The Google apps clue seems the more likely cause, but I can't say I can discern a definite pattern yet.
It could be a bug in Marshmallow 6.0. Maybe 6.1 will solve it. Maybe its the damn Polish ROM/modem.
In the meantime, I can only say - Do not flash this ROM! Without any cellular signal, the phone is not a phone. The constantly rebooting makes it useless!
Preter said:
Hi Matthew,
Saw your PM. Just to confirm that you have the same problem.
Error message - "The mobile network will be unavailable until you restart with a valid SIM card inserted"
- Bar counts up to 100% before phone reboots automatically
This is apparently a very serious problem with Android going back a few years and a few Android OS versions (KK I believe). It happens with various phone models ranging from:
LG G4
https://www.reddit.com/r/lgg4/comments/43p26p/sim_card_removed/
Nexus - Google doesn't give a F*CK
http://androidforums.com/threads/sim-card-problems.467384/
Motorola, Nexus, Samsung Galaxy etc.
https://code.google.com/p/android/issues/detail?id=66964
Google apparently doesn't give a rat's ass about it. As such it is very difficult to pin-point the problem. I have flashed & re-flashed robalm's V2 ROM at least 4 times, each time with a complete (nuke) wipe of everything including the Internal SD card. It definitely happens on the default modem (21C supposedly) that comes with it. Different modems have not helped. If you find one that works, let me know.
It cannot be a SIM card problem. Cos I've never ever taken it out since the day I got the phone. Once the problem happened, I've tried re-seating it, wiping the electrical contacts with microfibre cloth etc. Singtel shop customer service checked all the APN and network settings and confirmed it is correct, asked me to try the SIM card in other phones. Done that, nothing wrong with the SIM..
Googling further, some folks discovered that it is due to Google Apps (Play Store, Maps, G+, Gmail, Play Books/Games/Movies/Music/Services etc. etc.), which are system apps (as part of the ROM package), causing the problem after they are updated via Google Play Store. Don't we all update apps to the latest version, no?
I tried uninstalling all the updates for all of them (Settings>>Apps>>) and replacing them with the factory updates that came with the ROM. I usually freeze all the crap money sucking subscription based or in-app purchasing Google Apps that I don't use anyway. However, whether frozen or not, it still happens. Although not freezing any of them does seem more likely to cause the problem to become even more severe - like going into constant reboots as opposed to intermittent ones. When that happens, you have to go to airplane mode BEFORE the countdown completes and reboot happens. At least when it restarts, it won't hunt for the missing cellular signal and triggering another reboot. This then allows you to freeze the suckers more agressively.
It worked for a few days - I thought I had narrowed the problem down to Google Play Store, Play Framework and Play Services. But yesterday or so it has come back again with a vengeance. Freezing Google Play Store does not help by the way - besides what's the point if you can't use Play Store?
Problem is, disabling the auto-update functions on Google Play Store using:
(Play Store>>Settings>>General>>Auto-update apps>>check "Do not auto-update apps")
doesn't stop Google Play Store and Google Play services from auto-updating themselves! F*ck Google! You cannot prevent it no matter what.
Worse, everytime it auto-updates itself (or if you uninstall updates) - note that it will switch to the default setting of "Auto-update apps over Wi-Fi only" again. So you have to be fast in going to Settings in Google Play each time you reboot and open Play Store.
Some netizens have suggested ADB command line means to cripple the auto-updating. But to me that is not the freaking point. It's about trying to isolate and find the problem.
You end up uninstalling updates for Play Store several times a day but when you find that the cellular signal is gone (no bars), you realise that it has sneakily updated to 6.0.5.
But even when I uninstall all updates for Play Store. It can still happen. Maybe less frequently.
No cellular signal is bad enough. The worst aspect is the rebooting. I tried restoring my beloved KK 4.4.2 Nandroid backup but apparently I'll have to find a compatible modem again as TWRP 2.8.0 (or my previous version before upgrading to TWRP 2.8.7 for this Marshmallow) didn't manage to back it up (even though I tick everything).
Still doing trial and error to try isolating the problem. The Google apps clue seems the more likely cause, but I can't say I can discern a definite pattern yet.
It could be a bug in Marshmallow 6.0. Maybe 6.1 will solve it. Maybe its the damn Polish ROM/modem.
In the meantime, I can only say - Do not flash this ROM! Without any cellular signal, the phone is not a phone. The constantly rebooting makes it useless!
Click to expand...
Click to collapse
Yes! correct. we have the same problem. I don't think it is a glitch on mm 6.0 because i was on lollipop 5.0 when the problem occurred and I have only flashed 5.0 roms and modems. can you try the candySiX rom and see how it fairs in your phone? CandySix Rom thread link
I tried it on my phone and was able to connect to tower until I started installing Whatsapp which cause the sucker to break and reboot. But that was in a span of 15 mins. I read that it could also be a GPS problem so I disabled GPS but the phone was still broken. From my understanding, your trail and error seems to point to the play store updating itself that causes the phone to break correct? so why not cripple it using ADB and as for the updating of apps, it be done manually through sideload. because i don't think that there will be many apps that need to be frequently updated right? and even so if we do not update the app, it does not mean that the app will lose its functionality??
matthewmax09 said:
Yes! correct. we have the same problem. I don't think it is a glitch on mm 6.0 because i was on lollipop 5.0 when the problem occurred and I have only flashed 5.0 roms and modems. can you try the candySiX rom and see how it fairs in your phone? CandySix Rom thread link
I tried it on my phone and was able to connect to tower until I started installing Whatsapp which cause the sucker to break and reboot. But that was in a span of 15 mins. I read that it could also be a GPS problem so I disabled GPS but the phone was still broken. From my understanding, your trail and error seems to point to the play store updating itself that causes the phone to break correct? so why not cripple it using ADB and as for the updating of apps, it be done manually through sideload. because i don't think that there will be many apps that need to be frequently updated right? and even so if we do not update the app, it does not mean that the app will lose its functionality??
Click to expand...
Click to collapse
Dude –punctuation please …
I wish it was that simple. I've used Android Firewall (AFSWall+) to BLOCK all internet connections for Google Play Store and Google Play Services. The sneaky bastards at Google can still somehow update the factory Google Play Store from to 6.0.5! Upon that happening, all cellular network connection WILL DEFINITELY be lost. It may or may not reboot after that.
The problem is definitely related to Google Play (Store & Services). But it is not limited to it. Even when it has not updated itself, the error message can still show up and the phone can still reboot randomly with the error message. That is why I don’t think using ADB to disable updates solves anything.
Google is definitely doing something very intrusive with their Play Store apps – (why should and) how the hell apps (even if system apps) can be allowed to affect the functions of SIM card and cellular network reception to this extent is beyond me. Big brother is really upon us.
Not keen on trying custom ROMs anymore since my S2 days. Especially when stock Marshmallow already cause so many problems. Maybe this needs to be posted in the other international LG G3 threads.
Flash tool crashed
oceangreen said:
As you guys know, MM has started rolling out to the International Model D855!
I've been on MM for 3 days and quite satisfied with the update! Rom's seems faster and snappier, no more micro lag, juice seems to be better than LP tho... What you guys think? To all Lions, Share your thoughts and comments here! Cheers All!!!
Click to expand...
Click to collapse
Heyy trying to flash MM but lg flash tool 2014 keeps on crashing on win 10. want to retain data so am not using TWRP. What tool are u using and software version?
Good Sharing... thus far my screen not so often give me a blank screen issue after upgrade to MM Global
Hi guys ( @Preter @matthewmax09 )
my friend's SEA device started to giving your "The mobile network will be unavailable until you restart with a valid SIM card inserted" error too.
did you solved this problem? can anyone tell a solution for this?
thanks.
Hi all
I have a Samsung Galaxy S5 G900F, which when I got it 18 months ago was very eager to get involved in rooting and getting a custom ROM on it.
Fast forward to present day and the novelty has worn off, I haven't kept up to date with anything, and I am probably very out of date.
As such I would like to either update to the latest ROM or just flash the latest stock - I am not sure I really use much nowadays that even requires anything other than stock (used to play a lot with Tasker, sysadmin apps)
What has prompted this is of late my phone has been very laggy, crashing, sys apps hanging, etc. I also dropped my phone ages ago and occasionally the screen stops working (although still responsive) and I have to take the battery out to get it back (sometimes it reboots to a full screen of coloured static, and I have to repeat this several times). Now I know this seems like a hardware issue but at times the phone will not have been touched or moved and it'll do this, which makes me hope that maybe updating it will help.
I have a paid version of Omega Files Pro but apparently there has been no update for a very long time.
Hopefully you guys can help me get back up to date and on a level
Android Version: 5.0
Baseband version: G900FXXU1ANCE
Kernel Version: 3.4.0-Omega-1.0
Build Number: Omega V17 - XXU1POCF
I have PhilZ Recovery iirc.
Thanks in advance, if you need anymore info please say.
Install the rom from alxndr thread. Its a stock rom slightly optimized. It is the best for stability, performance and battery. There is only great reviews about it, it has a great community, and he updates it very frequently.
He has roms for either android 5 or android 6, which could can find in the second post of the thread.
If you choose to install android 6, you will have to update the bootloader and modem. They, as well as instructions, can be found in his thread.
http://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
To correct the issues, you will probably need to perform a full factory reset before installing the rom. Before anything, I recommend you to do a full rom backup (using your recovery). That way, if you forgot to backup something (like your taskers profiles), you can always go back.
Before doing the factory reset, you should backup your SMS, calls and apps. The easiest way to do it is by using the integrated backup tools in your S5 options : in the backup&restore sections, you will find a Samsung section that can backup messages and phone calls. There will also be a Google section where you can choose to backup your apps. If everything is set up correctly, once you will boot the new rom, you will be asked sequentially if you want to restore the samsung (Messges, call logs) and google (apps) data.
Thank you I'll have a read.
So how is it? Does camera work? Battery life? Does it have any bugs?
Just got 1.99 Gb update via Firmware finder.
It's excellent! Everything works, it's a lot faster than MM, it's smoother, ram management is finally OK. I advise updating via twrp (don't forget to flash the 2 zips one after the other and to flash stock recovery before the first boot. Then do a factory reset after the first boot)
Battery life is marginally (if at all) worse than MM. With location always on, mobile data always on, wifi always on, even during sleep, I lose about 1-4% overnight, in 7 hours.
Only thing I'm missing from MM is Xposed, but I can make do without it for now. I got all the essentials working, like root, Viper4Android, AdAway, Greenify.
Go for it, I will never return to MM even if they never release another N build.
Thanks for reply!
Well, i dont want to root my phone just yet.So ill update via firmware finder and then will do factory reset!
Yesterday i was on B336 and it was so laggy that i had to rollback to MM.
demlk said:
Thanks for reply!
Well, i dont want to root my phone just yet.So ill update via firmware finder and then will do factory reset!
Yesterday i was on B336 and it was so laggy that i had to rollback to MM.
Click to expand...
Click to collapse
B336 is trash. B370 could very well be a stable release.
Ok I updated. Everything works fine so.far.
Just weird ram management for example, I have opened apps Facebook, youtube, and google chrome. Its says that there is still 1 gb ram aviable but when I reopen chrome it refreshes tabs.
zgomot said:
It's excellent! Everything works, it's a lot faster than MM, it's smoother, ram management is finally OK. I advise updating via twrp (don't forget to flash the 2 zips one after the other and to flash stock recovery before the first boot. Then do a factory reset after the first boot)
Battery life is marginally (if at all) worse than MM. With location always on, mobile data always on, wifi always on, even during sleep, I lose about 1-4% overnight, in 7 hours.
Only thing I'm missing from MM is Xposed, but I can make do without it for now. I got all the essentials working, like root, Viper4Android, AdAway, Greenify.
Go for it, I will never return to MM even if they never release another N build.
Click to expand...
Click to collapse
Please post screenshot of ur Android OS battery usage. On B360 Android OS keeps the phone awake and drains the battery like hell overnight easily 10-15%
zgomot said:
It's excellent! Everything works, it's a lot faster than MM, it's smoother, ram management is finally OK. I advise updating via twrp (don't forget to flash the 2 zips one after the other and to flash stock recovery before the first boot. Then do a factory reset after the first boot)
Battery life is marginally (if at all) worse than MM. With location always on, mobile data always on, wifi always on, even during sleep, I lose about 1-4% overnight, in 7 hours.
Only thing I'm missing from MM is Xposed, but I can make do without it for now. I got all the essentials working, like root, Viper4Android, AdAway, Greenify.
Go for it, I will never return to MM even if they never release another N build.
Click to expand...
Click to collapse
You're lucky my camera doesn't work so am back to MM
Sent from my HUAWEI VNS-L31 using Tapatalk
Usama707 said:
Please post screenshot of ur Android OS battery usage. On B360 Android OS keeps the phone awake and drains the battery like hell overnight easily 10-15%
Click to expand...
Click to collapse
I recently charged so I don't know how much use this is going to be, but I'll post another screenshot in the morning.
This is over night.
zgomot said:
This is over night.
Click to expand...
Click to collapse
Wow its really impressive. Do u have an SD card inserted? On b360 Android OS keeps my device awake for hours overnight even on airplane mode
Usama707 said:
Wow its really impressive. Do u have an SD card inserted? On b360 Android OS keeps my device awake for hours overnight even on airplane mode
Click to expand...
Click to collapse
Yes, I use a class 10 32gb micro sd card.
zgomot said:
Yes, I use a class 10 32gb micro sd card.
Click to expand...
Click to collapse
This is Android OS consumption overnight tried all kinds of reset but nothing fixes this. In Wakelocks i can only see powermanagerservice.wakelocks or powermanagerservice.display
Usama707 said:
This is Android OS consumption overnight tried all kinds of reset but nothing fixes this. In Wakelocks i can only see powermanagerservice.wakelocks or powermanagerservice.display
Click to expand...
Click to collapse
Maybe you should try b370.
zgomot said:
Maybe you should try b370.
Click to expand...
Click to collapse
Unfortunately its not available for C185 region
Cant upgrade from b170 to b370/371
zgomot said:
It's excellent! Everything works, it's a lot faster than MM, it's smoother, ram management is finally OK. I advise updating via twrp (don't forget to flash the 2 zips one after the other and to flash stock recovery before the first boot. Then do a factory reset after the first boot)
Battery life is marginally (if at all) worse than MM. With location always on, mobile data always on, wifi always on, even during sleep, I lose about 1-4% overnight, in 7 hours.
Only thing I'm missing from MM is Xposed, but I can make do without it for now. I got all the essentials working, like root, Viper4Android, AdAway, Greenify.
Go for it, I will never return to MM even if they never release another N build.
Click to expand...
Click to collapse
Emmmmm.
Maybe you can make short tutorial how you upgraded it?
Couse I tried through FF, but it doesnt work :/
Also tried three buttons method, but then it says that "software version is incompatible with current version" :/
GeillGitrell said:
Emmmmm.
Maybe you can make short tutorial how you upgraded it?
Couse I tried through FF, but it doesnt work :/
Also tried three buttons method, but then it says that "software version is incompatible with current version" :/
Click to expand...
Click to collapse
This is how I did it: https://forum.xda-developers.com/showpost.php?p=71764827&postcount=5
I updates via firmware finder! Works fine. Battery good, camera good, Ram good.
demlk said:
I updates via firmware finder! Works fine. Battery good, camera good, Ram good.
Click to expand...
Click to collapse
I think, that's that gonna be a stupid question, but still...
Does my phone have to be rooted?
Nope, it doesnt.
I'm having trouble finding a root that works, unless I'm just doing something wrong. I have dev mode enabled with OEM unlocked and USB Debugging but it just keeps failing. I don't really want any custom features or roms at the moment, I'm fine with stock oreo. I just want to be able to move my apps onto the SD card and to use titanium backup to be able to properly back everything up. Though, I wouldn't be opposed to a custom rom as long as there's no major features that are missing like wifi calling n' such. I mainly want the phone to run smoother until I can replace it and using stock oreo feels pretty sluggish at times for no real reason and battery life sucks pretty bad, though that could just be a problem with the battery.
Baseband Version: G930TUVSBCTA2
Android Security Patch: December 1, 2019
Carrier: T-Mobile
Troika_Tigsky said:
I'm having trouble finding a root that works, unless I'm just doing something wrong. I have dev mode enabled with OEM unlocked and USB Debugging but it just keeps failing. I don't really want any custom features or roms at the moment, I'm fine with stock oreo. I just want to be able to move my apps onto the SD card and to use titanium backup to be able to properly back everything up. Though, I wouldn't be opposed to a custom rom as long as there's no major features that are missing like wifi calling n' such. I mainly want the phone to run smoother until I can replace it and using stock oreo feels pretty sluggish at times for no real reason and battery life sucks pretty bad, though that could just be a problem with the battery.
Baseband Version: G930TUVSBCTA2
Android Security Patch: December 1, 2019
Carrier: T-Mobile
Click to expand...
Click to collapse
Same, I got this crappy update.
This might not be much help If you already known about this option since I'm in the same boat searching for the root solution on my device, but you could use Samsung's Smart Switch app to do the job somewhat.
Basically creates a manual backup on your phone to restore whatever you need it from it. Then you can just move to a newer phone & keep what was saved.
I'm unsure about deep drive of files being saved since I'm trying to do a recovery on my own.
As for the SD card you should be able to put them on It; if you selected the merge with internal memory card, but you have to keep the SD in for It to function right.
As for the battery & sluggish you could have less apps opened up, reduce screen brightness & reducing live notifications etc.
Replacing the battery will remove NFC function as well because it's attached to It.
Best of luck working with what is available.
Hey
You got a B Rev firmware, I think it's not possible to root from what I've read on other threads...
Did you manage to root it?? If so I'm interested in how