Hooray....It's up and posted. Just Downloaded
Here fast download link for all: https://www.androidfilehost.com/?fid=889764386195905698
Docmjldds said:
Hooray....It's up and posted. Just Downloaded
Click to expand...
Click to collapse
Can I root after this update
dunbar28205 said:
Can I root after this update
Click to expand...
Click to collapse
Yes. Just reinstall TWRP from ODIN, then Magisk or SU.
Docmjldds said:
Hooray....It's up and posted. Just Downloaded
Click to expand...
Click to collapse
Docmjldds said:
Yes. Just reinstall TWRP from ODIN, then Magisk or SU.
Click to expand...
Click to collapse
Yes!Thank you
dunbar28205 said:
Yes!Thank you
Click to expand...
Click to collapse
So far everything running really snappy. Did the *#0228# battery reset suggestion and initially my Battery went from 100% to 82%. Really a large recalibrate. Let it charge up from powered off state and it took two hours to get it back to 100% which was rather slow, but then again, proof will be running now to see how it fairs vs MM.
BTW...sorry for thread drift here Will respect thread etiquette in future.
EDIT: my bad...just realized this was in the TMob section
Docmjldds said:
So far everything running really snappy. Did the *#0228# battery reset suggestion and initially my Battery went from 100% to 82%. Really a large recalibrate. Let it charge up from powered off state and it took two hours to get it back to 100% which was rather slow, but then again, proof will be running now to see how it fairs vs MM.
BTW...sorry for thread drift here Will respect thread etiquette in future.
EDIT: my bad...just realized this was in the TMob section
Click to expand...
Click to collapse
ok will do
dunbar28205 said:
ok will do
Click to expand...
Click to collapse
Battery looks great so far. Reading 99% now after 1 hour 15 min idle. Says 33H left. Can't complain. CPU Plus showing Deep Sleep at 74% too.
dunbar28205 said:
ok will do
Click to expand...
Click to collapse
im stuck on the t mobile splash screen
dunbar28205 said:
im stuck on the t mobile splash screen
Click to expand...
Click to collapse
nevermind lol
dunbar28205 said:
nevermind lol
Click to expand...
Click to collapse
LOL.... I only dropped 5 % battery overnight. Have 15 hours now and show 94%. Today will be a good test since I am out and about all day. I decided to NOT charge it overnight to see how it will go today.
When rooting should I just flash the regular Magisk V12 zip for systemless?
ketwi15 said:
When rooting should I just flash the regular Magisk V12 zip for systemless?
Click to expand...
Click to collapse
Yes....
How long were you guys stuck at the splash screen? After flashing Magisk I've been stuck on T-mobile splash screen for about 20 mins.
Thanks
Thanks
ketwi15 said:
How long were you guys stuck at the splash screen? After flashing Magisk I've been stuck on T-mobile splash screen for about 20 mins.
Click to expand...
Click to collapse
Did you first install the stock firmware and setup NON rooted. Start over with a clean wipe using TWRP which will of course reinstall stock recovery. Set your phone up. Reinstall TWRP. then flash magisk. Only 5 min or so of the TMobile splash for me.
Got it working.
Received the 7.0 update OTA today. Just throwing it out there.
kpeezy said:
Received the 7.0 update OTA today. Just throwing it out there.
Click to expand...
Click to collapse
One advantage of NOT being rooted
Has anyone figured out how to get Viper for this?
Related
Went on the market and my phone went pop and keeps bootlooping. Now I can get into the bootloader and fastboot mode but nothing else.
Now what should I do any suggestions?
Flash Google's stock images?
It went pop? Trying to picture that.
tgerbracht said:
It went pop? Trying to picture that.
Click to expand...
Click to collapse
It made a pop sound, like when an old filament light blew.
restore an old backup try flashing a ROM or flash stock image
Did you do a battery pull? Sounds like it just crashed.
done a battery pull etc. just flashed stock images now and its booted up ill see how everything goes. It was just weird because I was already on stock images so I don't see how what I done made a difference.
tgerbracht said:
It went pop? Trying to picture that.
Click to expand...
Click to collapse
My phone will make that speaker pop when I use ROM Manager to reboot into recovery.
champers said:
My phone will make that speaker pop when I use ROM Manager to reboot into recovery.
Click to expand...
Click to collapse
Well then that's a bug in your kernel/rom you're currently using. :/. I've also had this too, but haven't seen it for approximately 2 1/2 months (first two weeks it scared the **** out of me and thought it was gonna blow the speaker, lol).
anton2009 said:
Well then that's a bug in your kernel/rom you're currently using. :/. I've also had this too, but haven't seen it for approximately 2 1/2 months (first two weeks it scared the **** out of me and thought it was gonna blow the speaker, lol).
Click to expand...
Click to collapse
Stock 4.0.2?
champers said:
Stock 4.0.2?
Click to expand...
Click to collapse
No... but you have a custom recovery but on stock...? O-o okay. Anyway. It was Android Revolution HD (4.0.2-based).
Phone turns on when charging off? Is it a faulty battery? I haven't charged my phone while it's off for awhile now and tried just now and am realizing it turns on by itself. Took the battery out for a couple of minutes and tried again, same thing. Anyone have the same issue?
norml said:
Phone turns on when charging off? Is it a faulty battery? I haven't charged my phone while it's off for awhile now and tried just now and am realizing it turns on by itself. Took the battery out for a couple of minutes and tried again, same thing. Anyone have the same issue?
Click to expand...
Click to collapse
Are you on a GPE ROM? If so that's how it is because we don't have the right bootloader.
johnny crapple said:
Are you on a GPE ROM? If so that's how it is because we don't have the right bootloader.
Click to expand...
Click to collapse
No, I'm using Setup A in my sig. Omega v19 4.3 TW JB, on MDL bootloader. Thanks for your help and input.
norml said:
No, I'm using Setup A in my sig. Omega v19 4.3 TW JB, on MDL bootloader. Thanks for your help and input.
Click to expand...
Click to collapse
Oh sorry the SIG didn't show up on tapatalk. I've only heard of this happening on GPE ROMs.
johnny crapple said:
Oh sorry the SIG didn't show up on tapatalk. I've only heard of this happening on GPE ROMs.
Click to expand...
Click to collapse
No biggie, in my sig I have also have a Setup B which is
Setup B
Rom.........• VirginROM v3.1.2 Google Edition 4.4.2 I9505GUEUCML4
Kernel.....• KT GPE v2 Stock 4.4.2
I switch between the two with backups, but I'm on the Omega right now and it's turning on when charging. Is it normal? Thanks in advance.
norml said:
No biggie, in my sig I have also have a Setup B which is
Setup B
Rom.........• VirginROM v3.1.2 Google Edition 4.4.2 I9505GUEUCML4
Kernel.....• KT GPE v2 Stock 4.4.2
I switch between the two with backups, but I'm on the Omega right now and it's turning on when charging. Is it normal? Thanks in advance.
Click to expand...
Click to collapse
I searched the thread with keyword charging and seen someone mentioned it and they said it was kernal related, so yeah I guess its normal.
johnny crapple said:
I searched the thread with keyword charging and seen someone mentioned it and they said it was kernal related, so yeah I guess its normal.
Click to expand...
Click to collapse
Thanks Johnny Man!! I formatted data on my phone and went stock UVUAMDL, rooted with cf-auto-root just in case of OTA, lol, didn't even set up, shut it down. And it's charging, phone off. So I guess it's not hardware, that's what I was worried about. Thanks again for giving a crap, straight up, stay up Man and take it easy!!
Figured someone should start a thread now that its out. I had this update waiting for me this morning when I woke up. Had to replace some modified system files and then took the update. Lost root of course.
Points of note on ZVD:
Do not accept an OTA update with custom recovery or rom installed. If you have modified system files the stock files must be put back. Failure to consider this will lead you to problems you dont need. You can always .tot your device if necessary before taking the OTA, or wait (and be patient) for Devs to develop their roms to support zvd.
It does not include wifi calling.
ART Runtime is now available as an option in the Developer Menu.
It enables Knock Code.
You can reroot with ioroot 25 after update.
There were other fixes listed on Android central including:
A Google Patch
Improvements for group messaging
HD Voice Icon
Updated Email Signature
http://m.androidcentral.com/sprint-lg-g2-update-brings-knocking
I also noticed that Auto Brightness is not switching brightness up and down randomly all over the place and stays pretty well fixed but low intensity even at 100% with auto brightness enabled. Also of note is my battery draining really fast today after I updated and several restarts. Android system seemed to be running away over 28% battery usage but it seems to have settled down. Im gonna recalibrate my battery just be sure anyways. I always do after updates.
ZVD thread. Have at it!
any chance were you able to capture the file and might be able to upload it?
RawCarnage said:
any chance were you able to capture the file and might be able to upload it?
Click to expand...
Click to collapse
If I did I would have posted it but I believe some of the Devs already have the files. Dont quote me on that but I thought I had read someone grabbed it already.
ah okay sorry. but yea hopfully if one of them has it they post it soon. lol. thanks for the update on zvd tho. i went back to stock trying to see if i can get it. no luck tho
So are you able to get root again after the update?
Sent from my LGLS990 using XDA Premium 4 mobile app
OTA captured: http://forum.xda-developers.com/sprint-g2/development/ota-zva-update-ls980-t2823872
Does anyone happen to have a copy of the original build.prob from ZVC? I changed some things up and its messing up my update.
Just out of curiosity, how do you recalibrate your battery??
iDoc21 said:
So are you able to get root again after the update?
Sent from my LGLS990 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes
Sent from my LG-LS980 using Tapatalk
@iDoc21 i rooted just fine.
jcwxguy said:
Yes
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Just the latest ioroot I suppose? I havent rerooted yet. Was waiting to see what others experiences were.
iruntrains said:
Just out of curiosity, how do you recalibrate your battery??
Click to expand...
Click to collapse
I read this along time ago so hopefully Im retelling it correct. Here's what I do:
Let the phone batt run down and phone shut off completely.
Plug it in and leave the phone off till it charges to 100%.
Turn it on use phone as normal thru the day. Try not to power cycle the phone at all.
Let the batt run down again and phone shut off.
Again plug it in while off and charge to 100%.
Turn on phone with it still plugged in and when the LG screen comes up unplug it.
Your batt is now calibrated.
My G2 is stuck!
I took the ZVD update about 10 minutes ago and once the phone rebooted im suck in TWRP...what am I doing wrong??
your suppose to be fully stock to take the update. in you have a nandbackup use it now. btw i rooted using ioroot manually and installed the twrp recovery using autorec. also for some reason knock on doesnt work for me anymore. worked before zvd
pimpsqueak said:
I took the ZVD update about 10 minutes ago and once the phone rebooted im suck in TWRP...what am I doing wrong??
Click to expand...
Click to collapse
NEVER update with custom recovery or rom.
abhinav.tella said:
NEVER update with custom recovery or rom.
Click to expand...
Click to collapse
So what should I do in the future when OTA's come? im pushing a restore from the 17th right now.
pimpsqueak said:
So what should I do in the future when OTA's come? im pushing a restore from the 17th right now.
Click to expand...
Click to collapse
Next time flash the . Tot file to return to stock before flashing the update.
pimpsqueak said:
So what should I do in the future when OTA's come? im pushing a restore from the 17th right now.
Click to expand...
Click to collapse
After doing restore with TWRP my phone is still in TWRP...how do I boot it back up? what am I doin wrong...I aint even all that new to rooting...but TWRP i dont mess with much
---------- Post added at 04:30 AM ---------- Previous post was at 04:24 AM ----------
abhinav.tella said:
Next time flash the . Tot file to return to stock before flashing the update.
Click to expand...
Click to collapse
Can you help me get my phone booted back up please?
pimpsqueak said:
After doing restore with TWRP my phone is still in TWRP...how do I boot it back up? what am I doin wrong...I aint even all that new to rooting...but TWRP i dont mess with much
---------- Post added at 04:30 AM ---------- Previous post was at 04:24 AM ----------
Can you help me get my phone booted back up please?
Click to expand...
Click to collapse
Find the ZVC sprint tot file. and use this guide with it. how to use a tot file for lg g2
RawCarnage said:
Find the ZVC sprint tot file. and use this guide with it. how to use a tot file for lg g2
Click to expand...
Click to collapse
How the hell you get this Flashtool to even do anything??
I'm pretty sure this has been asked a lot, but I'm trying to install the "TeamSPR Rom" and i'm following the steps exactly. I still get stuck on the bootscreen with the logo with the blue LED glowing. What am I doing wrong, and this happens with TeamSPR and Renegade.
Software Version: G920PVPU3CPF4
Hardware: G920P.02
Model: SM-G920P
Android: 6.0.1
Saafir said:
Wait 20 minutes.
Click to expand...
Click to collapse
My versions are correct for this right? and do I need anything else besides twrp?
steezoe said:
My versions are correct for this right? and do I need anything else besides twrp?
Click to expand...
Click to collapse
Make sure that you are rooted (goes without saying) and using the correct version of TWRP: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Saafir said:
From the information in your post, you seem to be on the right track. That ROM has taken upwards of 25 minutes to boot for some folks. As long as the blue light is slightly pulsing, it's doing it's thing. As long as you have TWRP installed and working, you should be good to go.
Click to expand...
Click to collapse
So pulsing plus the samsung logo, is a good thing?
koop1955 said:
Make sure that you are rooted (goes without saying) and using the correct version of TWRP: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
And I'm using the latest TWRP.
p.s. Thank you guys so much, I'm skepticle when it somes to asking for help on forums, cuz usually people are short tempered and or a-holes. I really appreciate it though.
1 last thing, do i install/flash the OTA part after it optimizes all the apps?
finished everything, it's booted up now, but my screen is spamming "unfortunately, "APPNAME" has stopped" is that normal?
EDIT: Can't get into my text messages either.
Saafir said:
You shouldnt receive any errors. I would reboot to TWRP, do a wipe and reinstall the ROM. Let the device boot and set it up. Once all is good with the initial install, reboot to TWRP and install the update.zip. This should ensure a nice clean start.
Click to expand...
Click to collapse
1. Flashed ROM, waited 20 is mins.
2. Phone loaded up, restarted into TWRP and Flashed the OTA zip.
3. Phone loaded up. This is when I start getting a popup saying "Unfortunately the process android.process.acore has stopped working." and my message app still won't open after i cleared cache and data.
Thanks in advance
Saafir said:
Set the device up before flashing the OTA.
Click to expand...
Click to collapse
Meaning I was supposed to wipe everything on my phone?
Saafir said:
Setup the device as go through the Setup Wizard..
Click to expand...
Click to collapse
I did exactly that. Im currently reflashing the Full ROM taking longer at the samsung screen. But I'll wait. If all else fails I'll probably go back to stock.
I'm now back to stock 6.0.1, going to give this one more go.
Would anyone mind giving me specific step-by-step directions. please?
I feel like im forgetting something crucial.
everthing finally worked out. just having an issue with xposed literally taking hours at the boot screen
October security update is out A52s 5g. A528BXXS1CVI6 is availble at:
https://samfw.com/firmware/SM-A528B and https://samfrew.com/model/SM-A528B/ and if you have the app Frija. Most of the regions are getting it. Nothing too much in this one other than updating some security stuff and bug fixes...
how to install ota updates on rooted samsung galaxy? I have flashed magisk and twrp
Carson Yang said:
how to install ota updates on rooted samsung galaxy? I have flashed magisk and twrp
Click to expand...
Click to collapse
You can't
bobfrantic said:
You can't
Click to expand...
Click to collapse
I have a rooted A52S 5G, can I install the new update through Odin, and if so will it wipe everything in my phone? Also what's a good way to backup everything, I'm talking about the apps and modifications I have installed already. Thanks in advance!
YouWotm8 said:
I have a rooted A52S 5G, can I install the new update through Odin, and if so will it wipe everything in my phone? Also what's a good way to backup everything, I'm talking about the apps and modifications I have installed already. Thanks in advance!
Click to expand...
Click to collapse
You can install the update with odin. As for backup, I use smartswitch. When I install any updates I start from scratch. I use the non_home csc to ensure it's a clean install. You may try the home_csc that will leave your phone as is as far as any apps go but you'll probably have to re-root the phone anyways. You may have minor issues as well...
bobfrantic said:
You can install the update with odin. As for backup, I use smartswitch. When I install any updates I start from scratch. I use the non_home csc to ensure it's a clean install. You may try the home_csc that will leave your phone as is as far as any apps go but you'll probably have to re-root the phone anyways. You may have minor issues as well...
Click to expand...
Click to collapse
Yeah, a clean installation is what I'm after as well.
So if I understood correctly, I'll just update like you do to a clean install, then root again and restore backup using smartswitch and that's it?
YouWotm8 said:
Yeah, a clean installation is what I'm after as well.
So if I understood correctly, I'll just update like you do to a clean install, then root again and restore backup using smartswitch and that's it?
Click to expand...
Click to collapse
yup thats about it all right
bobfrantic said:
yup thats about it all right
Click to expand...
Click to collapse
Perfect, should I use the same method I did last time with same magisk versions and all that? I still have April's build and rooted with Arobase's guide (I can't find it here anymore though). Thanks for all the help nonetheless!
I never did clean so many months now. I follow the procedure for rooting and i update without any problems.
Guys you have too much spare time to do this every month
BlueChris said:
Guys you have too much spare time to do this every month
Click to expand...
Click to collapse
Oh boy you don't know the half of it lol
This is the worst update so far in terms of battery life. SOT is significantly dropped
AbhiAndro said:
This is the worst update so far in terms of battery life. SOT is significantly dropped
Click to expand...
Click to collapse
I share the same feelings as you, let's hope the November fixes the things.
AbhiAndro said:
This is the worst update so far in terms of battery life. SOT is significantly dropped
Click to expand...
Click to collapse
No drop in battery life here, at all. No drop in SOT, still very good.
gerhard_wa said:
No drop in battery life here, at all. No drop in SOT, still very good.
Click to expand...
Click to collapse
I'm seeing atleast 20-30% less SOT in this update. Also some apps started crashing unexpectedly, I get a dialog box saying a specific app has crashed. Haven't happened before.