S7 Global Update OTA via Flashfire while on TWRP possible? - Samsung Galaxy S7 Questions and Answers

Im getting constant bug reports with a new G930f G930FXXS1APG3 Trinidad & Tobago Baseband G930FXXU1APEQ rooted with TWRP security patch July, 1 2016.
My wife has identical phone/software with no bugs.
It keeps prompting me to update ota, i dont because i havent fully wrapped my head around taking software updates directly from Samsung. Coming from G900t so this is new to me.
For right now i would like to stay stock and custom recovery and keep or re root
Would anyone suggest trying to flashfire the latest ota if someone has it? Or would i flash in TWRP?
Can i Flashfire and keep TWRP?
Will updating 6.0.1 to 6.0.1 help with bugs?
I'm not sure what to do, but i would like to update this or stop the bugs without a custom rom for now.

Related

Huawei MT7-TL10 - what is the latest official update/how to update if already rooted

Hi All,
I am having trouble looking for a thread that would help me update my rooted MT7-TL10, my current version is TL10V100R001C00B120SP04. Is it easier if I just unroot it first then install
via OTA? The new pending version under EMUI updater is TL10V100R001C00B130. I dont think it has a noticeable change with my current version but I really would want a Lollipop OS
for my MT7 (better if its an official update) Hope you could help me and give me the step by step procedure for this since my phone is getting really boring without the lollipop or marshmallow update.
Thanks! :fingers-crossed:
seeker1107 said:
Hi All,
I am having trouble looking for a thread that would help me update my rooted MT7-TL10, my current version is TL10V100R001C00B120SP04. Is it easier if I just unroot it first then install
via OTA? The new pending version under EMUI updater is TL10V100R001C00B130. I dont think it has a noticeable change with my current version but I really would want a Lollipop OS
for my MT7 (better if its an official update) Hope you could help me and give me the step by step procedure for this since my phone is getting really boring without the lollipop or marshmallow update.
Thanks! :fingers-crossed:
Click to expand...
Click to collapse
Here is the correct link to root and Custom Recovery
http://forum.xda-developers.com/mate-7/general/huawei-ascent-mate-7-unlock-recovery-t2941525
You can also root each version KK,LP or MM.
In my case never has a Ota update works, but you can do all by Local Update.
But you must go back to Stock Recovery
Thread is not working anymore.. What version do you have now? How did you upgrade?
Sent from my HUAWEI MT7-TL10 using Tapatalk
letschky said:
Here is the correct link to root and Custom Recovery
http://forum.xda-developers.com/mate-7/general/huawei-ascent-mate-7-unlock-recovery-t2941525
You can also root each version KK,LP or MM.
In my case never has a Ota update works, but you can do all by Local Update.
But you must go back to Stock Recovery
Click to expand...
Click to collapse
I am already rooted btw.. Just want to upgrade.. I just meed specific instructions to do so.. Thread is not working anymore.. Hope you could help. Thank you.
Which version do you have on it now Kitkat or Lollipop?
letschky said:
Which version do you have on it now Kitkat or Lollipop?
Click to expand...
Click to collapse
I have version 4.4.2. The kitkat version. Never updated it ever since i got the phone. Received a notice on a new OTA update.. But it is more on for stability. Not the lollipop update i guess.
what do you want exactly?
Just want to know if there is an official lollipop update for my phone. And on how to install it while im rooted.
Sent from my HUAWEI MT7-TL10 using Tapatalk
I had the same version on my TL10 (120SP04) and I went directly to B331 from dload folder. No problem in it. Just one difference - my device was unrooted. I made root after that and then flashed KangVIP 3A which is really fine ROM. I think I can recommend you the same however I don't know if there is any problem in your root (but I don't think so).
seeker1107 said:
Just want to know if there is an official lollipop update for my phone. And on how to install it while im rooted.
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
Here a the Lollipop Updates for TL09/10
http://consumer.huawei.com/my/support/downloads/index.htm?keyword=mt7
or here
http://forum.xda-developers.com/mate-7/general/official-android-lollipop-update-tl09-t3214970
and Recovery TWRP
http://forum.xda-developers.com/mate-7/orig-development/recovery-twrp-2-8-7-0-mate7-android-5-1-t3156779
P-G said:
I had the same version on my TL10 (120SP04) and I went directly to B331 from dload folder. No problem in it. Just one difference - my device was unrooted. I made root after that and then flashed KangVIP 3A which is really fine ROM. I think I can recommend you the same however I don't know if there is any problem in your root (but I don't think so).
Click to expand...
Click to collapse
Did you reach the lollipop version via OTA? So i know if its easier just to unroot and update.
seeker1107 said:
Did you reach the lollipop version via OTA? So i know if its easier just to unroot and update.
Click to expand...
Click to collapse
Yeah, I did, but my device was unrooted. I don't know if there will be any problem in rooted device..
Is there any whatsapp group of honor 7.I want to join it
letschky said:
Here a the Lollipop Updates for TL09/10
http://consumer.huawei.com/my/support/downloads/index.htm?keyword=mt7
or here
http://forum.xda-developers.com/mate-7/general/official-android-lollipop-update-tl09-t3214970
and Recovery TWRP
http://forum.xda-developers.com/mate-7/orig-development/recovery-twrp-2-8-7-0-mate7-android-5-1-t3156779
Click to expand...
Click to collapse
Hi again, Im receiving error tying to install this in TWRP. Hope you could help. Thanks
Mine was B120 SP04 also. I did the B130 update and kept it that way quite a while, unlocked, CWM recovery and rooted. Also had an older version of Xposed working with some modules. I tried a mod that stuffed it up recently, although it still booted, so decided to go Lollipop seeing as I had to work on it anyway. First thing is to use ADB and flash back to stock recovery, then I unrooted.
Next I applied B324 via local update. It ran fine so I applied B331 via local update.
Running good. Now have TWRP recovery and root. It's a shame Xposed doesn't work on it
I‘ve also not been able to apply lollipop incremental updates. Only a full ROM. Decided not to risk MM yet.
I‘ve noticed that on LP and debloat system apps, I have more free RAM than with KK. It also runs smoother. I installed EX Kernel Manager anyway and with a few basic tweaks the phone flies!
Seriously considering rolling back to Kitkat.
B331 Lollipop runs fine as a daily driver, it's just that even with it rooted, it's so hard to install any mods to customise it how I want.
On reflection, Lollipop doesn't seem to offer me any real benefits over Kitkat

Moto G4 Plus US XT1644 Stock Unmodified 6.0.1 TWRP Backup & Recovery/Logo Images

Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin​
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .

[ROM][v521] LG Stock Nougat ROMs for LG G Pad X 8.0 (2018-06-18)

Disclaimer:
I am not responsible for anything that may happen to your phone as a result of installing this rom. You do so at your own risk and take responsibility upon yourself.
About:
The Stock ROMs posted here are extracted from official LG KDZ files for the T-Mobile LG G Pad X 8.0 | v521 | b3.
Only change made on ROM was to prevent stock recovery from restoring itself
ROM includes modem/radio, however you can also manually flash the modem/radio from here
root is NOT included. However feel free to flash your choice of root with Magisk, SuperSU, or any others at anytime to get root.
Info:
Android version: 7.0
Kernel version: 3.10.84
Build number: NRD90U
init.d support
forceencrypt disabled
Requirements:
Your device must be or have been on 20f or newer at one point or another. If your device has always been on Marshmallow and has never been updated to Nougat by kdz or OTA, you'll need to upgrade to Nougat and re-root first. (Thank to monkeyass408 for verifying)
You can follow this guide to do so: Guide to Update V521 LG GPAD X 8.0 to 7.0 and Root
You must have TWRP or another custom recovery already installed in order to flash this rom.
Instructions:
Download the version of your choice from below.
Boot into TWRP and make a backup. You may want to remove any lock screen security before doing this as restoring with lock screen may cause unexpected issues.
Optional: Wipe data and/or system. As of TWRP 3.1.1.0, you will want to reboot recovery after wiping data/system before flashing as TWRP may get stuck on a black screen during the flashing process without a reboot.
Flash ROM.
Optional: Flash the disable OTA zip to prevent and disable official LG OTA updates & notifications
Reboot and you should be all set.
Downloads: (Listed by Sofware version / Android security patch level)
Note: As of 2017-02-21, TWRP 3.0.2-0, will sometimes give the error "Failed to map file" when attempting to flash this rom. Rebooting TWRP will resolve it and allow you to flash the zip.
v52120n >> Apr 1, 2018
v52120m >> Feb 1, 2018
v52120l >> Dec 1, 2017
v52120k >> Oct 1, 2017
v52120j >> Aug 1, 2017
v52120i >> Jun 1, 2017
v52120h >> Apr 1, 2017
v52120g >> Feb 1, 2017
v52120f >> Dec 1, 2016
All Stock ROMs Folder
Disable Stock OTA
Note: This should prevent you from verifying and updating via OTA. The OTA notification may still pop up but it should go away when you attempt to update after flashing this. I haven't fully tested this so backup first and don't be surprised if it returns you to full stock.
Credits/Thanks:
tungkick for the initial root method
shabbypenguin for TWRP on the LG G Pad X
All other devs who make rom building possible
Reserved - Unlikely I'll need it but who knows?
Can this be flashed over marshmallow 10c? If so, what should be wiped? Thanks.
channeledbymodem said:
Can this be flashed over marshmallow 10c? If so, what should be wiped? Thanks.
Click to expand...
Click to collapse
Yes you can flash this over Marshmallow v52110c. Technically a dirty flash (no wipe) would work fine but you never know so don't be surprised if issues spring up. After you flash the rom, since you're upgrading from Marshmallow, you'll want to update the radios too. The flashable zips for it can be found @ https://forum.xda-developers.com/lg...irmware-modem-flashable-modem-zips-t-t3564590. I'd recommend flashing the respective radio of the Nougat version you end up using.
so after I flash the 20g my 5ghz wifi keeps on disconnecting, same thing after flashing the 20g modem. wiped data as well. coming from official 20f rooted with dirtycow.
my 10 other devices are fine so it's not my router. not sure if it's an issue with the 20g, never had any issue with 20f
supaet said:
so after I flash the 20g my 5ghz wifi keeps on disconnecting, same thing after flashing the 20g modem. wiped data as well. coming from official 20f rooted with dirtycow.
my 10 other devices are fine so it's not my router. not sure if it's an issue with the 20g, never had any issue with 20f
Click to expand...
Click to collapse
Hmmm I haven't had any issues with my 5ghz on my tablet. The roms are ripped straight out of the kdz files so any changes between 20g and 20f are strictly from LG/T-Mobile. Although I do recommend keeping the modem version and the rom version the same, I am curious, would you be able to test and see if it still happens if you downgrade the modem version to 20f while you're on the 20g rom?
Long overdue but added 20h, 20i, and 20j.
Decided to get rid of AROMA and root selection so any root method can be manually flashed afterwards.
Stock recovery shouldn't restore itself now. init.d support and forceencrypt is set to disabled by default since TWRP doesn't play along nicely with encrypt anyways.
.fenrir said:
Long overdue but added 20h, 20i, and 20j.
Decided to get rid of AROMA and root selection so any root method can be manually flashed afterwards.
Stock recovery shouldn't restore itself now. init.d support and forceencrypt is set to disabled by default since TWRP doesn't play along nicely with encrypt anyways.
Click to expand...
Click to collapse
Appreciate the update Thanks!!!
A bit quicker this time around. 20k has been added.
Amd4life said:
Appreciate the update Thanks!!!
Click to expand...
Click to collapse
No problem.
.fenrir said:
Yes you can flash this over Marshmallow v52110c. Technically a dirty flash (no wipe) would work fine but you never know so don't be surprised if issues spring up. After you flash the rom, since you're upgrading from Marshmallow, you'll want to update the radios too. The flashable zips for it can be found @ https://forum.xda-developers.com/lg...irmware-modem-flashable-modem-zips-t-t3564590. I'd recommend flashing the respective radio of the Nougat version you end up using.
Click to expand...
Click to collapse
i flashed from 10c marshmallow to nougat 20k. i am having problems getting lte data to even show up. Would u happen to know how to get it working?
i did wipe and started fresh install. I also flashed the k modem and it didnt work.
monkeyass408 said:
i flashed from 10c marshmallow to nougat 20k. i am having problems getting lte data to even show up. Would u happen to know how to get it working?
i did wipe and started fresh install. I also flashed the k modem and it didnt work.
Click to expand...
Click to collapse
Shouldn't need to do anything for LTE to work. Does it get signal at least? I would confirm the APN settings just to make sure they aren't missing for whatever reason.
Otherwise, try another version and see if it does the same thing. Although it shouldn't be the case, it's possible that the device may need to be kdz'd to Nougat first before a Nougat ROM works without any problems. That being said, I do remember being able to manually flash Nougat on my tablet from 10c with no issues back when I was on it.
.fenrir said:
Shouldn't need to do anything for LTE to work. Does it get signal at least? I would confirm the APN settings just to make sure they aren't missing for whatever reason.
Otherwise, try another version and see if it does the same thing. Although it shouldn't be the case, it's possible that the device may need to be kdz'd to Nougat first before a Nougat ROM works without any problems. That being said, I do remember being able to manually flash Nougat on my tablet from 10c with no issues back when I was on it.
Click to expand...
Click to collapse
I figured it out. I had to take 10c marsh to 20f nougat stock and rerooted +twrp in order for it to work. No longee had grayed out lte and apn and missing imei. Thanks for the reply.
Flashing straight 10c marsh to a nougat rom will always give me those errors. Same when tried with resurection remix.
monkeyass408 said:
I figured it out. I had to take 10c marsh to 20f nougat stock and rerooted +twrp in order for it to work. No longee had grayed out lte and apn and missing imei. Thanks for the reply.
Flashing straight 10c marsh to a nougat rom will always give me those errors. Same when tried with resurection remix.
Click to expand...
Click to collapse
Glad to hear it worked out for you. I stand corrected on it being flashed over Marshmallow so I've updated the first post to reflect that. Thanks for trying and verifying it.
Hello,
The V52120l_00_1201.kdz is OTA, so could you please make the lastest ROM base on V52120l_00_1201.kdz
thanks in advance
@ .fenrir: I appreciate all the work you've done on this and don't really need the monthly patches. Is there a way to disable ota download and notification on a rooted tablet?
Thanks.
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Char_Liu said:
Hello,
The V52120l_00_1201.kdz is OTA, so could you please make the lastest ROM base on V52120l_00_1201.kdz
thanks in advance
Click to expand...
Click to collapse
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
channeledbymodem said:
@ .fenrir: I appreciate all the work you've done on this and don't really need the monthly patches. Is there a way to disable ota download and notification on a rooted tablet?
Thanks.
Click to expand...
Click to collapse
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
.fenrir said:
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
Click to expand...
Click to collapse
Thank you for the update.!
Appreciate the update
Thx a lot
.fenrir said:
20l has been added. I also realized on the older files I accidentally called the device 8.3 instead of 8.0 in the zip so that's been corrected now.
Thanks for the heads up. Been busy with the holidays so didn't have a chance to do anything.
When rooted, you should be able to delete /system/etc/security/otacerts.zip which should prevent the device from verifying for the OTA. Afterwards if the OTA was already downloaded on the device, you can delete the OTA update file at /cache/update.zip . That SHOULD be enough to do it but I won't make any guarantees until I get a chance to test it as you would probably need to delete the other LGFOTA as well. I'll make a flashable zip for it later on if necessary/when I get a chance.
Click to expand...
Click to collapse
I have always had excellent battery life but after a dirty flash of v.l it is terrible. I am losing 30% overnight. Can I roll back to v.k? I am reluctant to clean flash v.l; it's a lot of work getting back to normal.

How can I know if my phone receives OTA updates?

I just flashed the latest Nougat BTU ROM for my SM-G920F. And after checking CSC using *#1234# it says BTU. Does this mean I'm already in the BTU update cycle and will continue to get OTA updates in the future?
I came from root. But now that I'm on Nougat and Xposed isn't updated to Nougat yet, I'm OK with not having root to get OTA updates. I just can't afford to download a ~1GB file from sammobile/updato every time just to get the latest security patches.
Thanks for the help.

Update a rooted Stock Nougat to Oreo?

Hi,
I've got a MHA-L29 C432 B198.
Currently the bootloader is unlocked, TWRP flashed into 1st recovery partition and phh's Superuser installed.
Now I got a message that Orea is available and even downloaded... but I cannot find any dload folder or anything else with >2GB on the sdcard.
Anyhow, I would like to know if I could simply start the update when I flash stock recovery again. Or will it trouble with root?
My phone is setup like yours but I'm L29 C567 B190 and xposed installed, I just tried to take the OTA update by flashing back the stock recovery and it still fails.
Can someone point me to the correct path to either take the OTA update, or to a TWRP flashable version of the update? I'm still new to the Huawei ecosystem (or lack thereof) and cannot determine how to do this properly and desperately want to avoid wiping my phone in the process.

Categories

Resources