Greetings,
i've android 6.0.1 (MMB29K) December security patch and i want to update to 6.0.1 (MMB29S) the January security patch. i'm rooted , xposed and using twrp with custom kernal . any ideas how i can update without losing any of those ?
??
Flash the factory image (but not userdata.img) then re-root. It's the only way
EddyOS said:
Flash the factory image (but not userdata.img) then re-root. It's the only way
Click to expand...
Click to collapse
what would i lose in this case ?
You should not lose anything as you are not touching the userdata partition.
even the configurations and settings of the system and apps ?
I asked the same question a few months ago. You lose nothing. As long as you don't touch data/userdata, your device will reboot looking exactly as it did before, just without root. I don't have Xposed, so I can't guarantee that, but everything else will be fine in my experience.
Can I use this trick to update to 6.0.1 ? I now have 6.0.0 with franco kernel + xposed framework and root
dont want to install everything from the begininng...
deepstate said:
Can I use this trick to update to 6.0.1 ? I now have 6.0.0 with franco kernel + xposed framework and root
dont want to install everything from the begininng...
Click to expand...
Click to collapse
+1
I have all that and flash a debloated stock, rooted rom that is updated every month, dirty flash, and I loose nothing. Just boots and all is good
Related
Hi all I just got two new security updates on my xt1550 one after the other. the update versions are as follows
24.71.2.en.03 - July, 2016 Security patch
24.201.5.en.03 - October 1st, 2016 Security Patch
Can anyone else confirm they got the security patches?? my android version is on 6.0.1 and not rooted.
Yes many people have received the security updates...
yes, me too
Yes security updates are rolling out now in India, other varients got july update in late November and October patch with us.
yes i got this too and now when it reboots, it reboots to TWRP and loops back. So i cleared cache date and was able to boot properly. But i was not able to update to that version. mobile is rooted and unlocked. Is there anyway anyone can get me that link so that i can fastboot the update?
manohar1121 said:
yes i got this too and now when it reboots, it reboots to TWRP and loops back. So i cleared cache date and was able to boot properly. But i was not able to update to that version. mobile is rooted and unlocked. Is there anyway anyone can get me that link so that i can fastboot the update?
Click to expand...
Click to collapse
I faced the same issue.
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Go to this page. Download your respective factory image. Unzip. Flash the stock recovery. Now update.
After this, flash twrp if you want.
bin.sayantan said:
I faced the same issue.
https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Go to this page. Download your respective factory image. Unzip. Flash the stock recovery. Now update.
After this, flash twrp if you want.
Click to expand...
Click to collapse
I dont wanna flash mobile all over again. just need to update that if possible. I got that 20MB update last month only..
manohar1121 said:
I dont wanna flash mobile all over again. just need to update that if possible. I got that 20MB update last month only..
Click to expand...
Click to collapse
Don't flash the entire stock ROM. Just the recovery image.
But please, don't flash that official update on any custom ROM.
bin.sayantan said:
Don't flash the entire stock ROM. Just the recovery image.
But please, don't flash that official update on any custom ROM.
Click to expand...
Click to collapse
I have flashed newer build in that not long ago.
u mean to say uninstall twrp? is that wat u meant flash recovery image ?
manohar1121 said:
I have flashed newer build in that not long ago.
u mean to say uninstall twrp? is that wat u meant flash recovery image ?
Click to expand...
Click to collapse
No need to wipe recovery. Flash stock recovery on top of TWRP. It will automatically be replaced.
If he is rooted he won't be able to update. OTA updates require pure stock - stock recovery, stock kernel, and an unmodified system. This means no root, xposed, or any other changes to the system including build.prop edits.
Sent from my MotoG3 using Tapatalk
bin.sayantan said:
No need to wipe recovery. Flash stock recovery on top of TWRP. It will automatically be replaced.
Click to expand...
Click to collapse
It worked half way, while it says installing on the stock recovery then error comes with sleeping android with red triangle exclamation mark.
---------- Post added at 02:35 PM ---------- Previous post was at 01:54 PM ----------
riggerman0421 said:
If he is rooted he won't be able to update. OTA updates require pure stock - stock recovery, stock kernel, and an unmodified system. This means no root, xposed, or any other changes to the system including build.prop edits.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
so i should lock my bootloader and flash stock recovery ?
manohar1121 said:
It worked half way, while it says installing on the stock recovery then error comes with sleeping android with red triangle exclamation mark.
---------- Post added at 02:35 PM ---------- Previous post was at 01:54 PM ----------
so i should lock my bootloader and flash stock recovery ?
Click to expand...
Click to collapse
You need not relock the bootloader. I have flashed system updates with stock recovery and unlocked bootloader.
Looks like you have correctly flashed the recovery. Once you get the red exclamation mark, keeping the volume up pressed, press the power button (I don't remember exactly, if it doesn't work, try the reverse).
manohar1121 said:
It worked half way, while it says installing on the stock recovery then error comes with sleeping android with red triangle exclamation mark.
---------- Post added at 02:35 PM ---------- Previous post was at 01:54 PM ----------
so i should lock my bootloader and flash stock recovery ?
Click to expand...
Click to collapse
No need to lock the bootloader, but if you were rooted as stated in your first post, you will the stock system and kernel. You can not update if ANY system files, kernel, or recovery are not FULL stock. Your best bet right now is to flash the stock ROM via fastboot, if you need the update.
riggerman0421 said:
No need to lock the bootloader, but if you were rooted as stated in your first post, you will the stock system and kernel. You can not update if ANY system files, kernel, or recovery are not FULL stock. Your best bet right now is to flash the stock ROM via fastboot, if you need the update.
Click to expand...
Click to collapse
I have stock ROM. 3.10.49-ge6a5415
system version - 24.71.2.osprey_retasia_ds_2gb.retasia.en.03 retin
i got OTA update. so its not possible to update if mobile is rooted is it ?
manohar1121 said:
I have stock ROM. 3.10.49-ge6a5415
system version - 24.71.2.osprey_retasia_ds_2gb.retasia.en.03 retin
i got OTA update. so its not possible to update if mobile is rooted is it ?
Click to expand...
Click to collapse
The updater script checks the system, recovery and kernel. If they do not match what is expected (full stock), then the update will fail. I can't say it any more clearly, you need FULL STOCK, ie no modifications to system files (xposed, added or deleted system apps, build.prop edits, root, custom recovery). If you have done any of this, even one, the update will fail. Flash the stock ROM via fastboot.
Got a new update Jan 2017
Moto g3 xt1550 Osprey
So, to revert back to stock 6.0.1 from custom 7.1.1, do i need to wipe system, data, cache, etc before restoring my back up of the stock?
M-in-M said:
So, to revert back to stock 6.0.1 from custom 7.1.1, do i need to wipe system, data, cache, etc before restoring my back up of the stock?
Click to expand...
Click to collapse
You should. But I think it can be done right after flashing stock ROM also.
After getting these brutal update messages every few minutes on Android 6.0 and not being to update because of root and TWRP, rather than going back to stock, I finally cracked and bit the bullet yesterday and installed Lineage. I am now on Android 7.1.2 with the April security update, and going forward new OS and security updates will be simple updates; in fact the May update as noted by the OP is due this week, and I can either install it OTA from Lineage with a press of a button, or via TWRP if I so desire . I understand others don't want to install a custom ROM for various reasons, but for me it was a no-brainer.
I have a rooted (SuperSU, xposed) MotoG3 with custom recovery (TWRP) running 6.0.
I just got the notification that an update is ready for my phone, which I assume is 6.0.1.
Now, I know that that OTA update is going to fail because of root & modified recovery.
What is the easiest way to update to 6.0.1, while keeping or reinstalling root, xposed and TWRP.
Can I just unroot, reflash stock recovery and update?
Quark^2 said:
I have a rooted (SuperSU, xposed) MotoG3 with custom recovery (TWRP) running 6.0.
I just got the notification that an update is ready for my phone, which I assume is 6.0.1.
Now, I know that that OTA update is going to fail because of root & modified recovery.
What is the easiest way to update to 6.0.1, while keeping or reinstalling root, xposed and TWRP.
Can I just unroot, reflash stock recovery and update?
Click to expand...
Click to collapse
It's just a simple security patch, not an version upgrade, it can be safely ignored. That said, if you really want it you need to be pure, unmodified stock... Restore your pre-root Nandroid or flash the current factory image with fastboot.
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.
Hey everyone,
I have a Nexus 5 that I haven't updated in a long time that I'd like to get the latest possible OS for. The only modifications I've made which I think might be important are:
Unlocked bootloader
Rooted using SuperSU (v2.8.2 currently)
Installed XPosed (installer v2.6.1, not sure what version of the framework but it should be the latest supported by 4.4.4) with a few modules
Installed App Ops and removed permissions from some apps
Installed StickMount
I don't believe I have any custom recovery installed (I'd used a script to root and install XPosed originally and I don't know if it made any other changes). I'm comfortable using adb if needed but I'm cool with tools like FlashFire too.
My end goal is to have an updated OS with root and XPosed. I assume I'll need Magisk for XPosed, but not sure about root.
How should I go about doing this? I'm cool with losing all of my data (I'll be making backups with Titanium Backup) though knowing ahead of time if that'll be the case would be nice. If it's possible to update without losing data and without affecting anything that'd be nice, but maybe a clean start would be good? The OTA guide on this forum is only for 5, not 6, and most online guides start with 5. I don't want to mess up obviously. xD
Any advice/steps would be appreciated! Thanks!
Aecyl said:
Hey everyone,
Click to expand...
Click to collapse
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
pavik62 said:
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
Click to expand...
Click to collapse
The link you gave doesn't have the latest 6.0.1 build and it also says that it requires a minimum bootloader (HHZ12h) that I don't have (I have HHZ11k). Would it be possible to use the latest build from Google? What do I do about the bootloader? And would using TWRP as the recovery prevent me from passing SafetyNet?
Thanks for replying!
Could I follow this guide with the latest factory image and then install Magisk, root, and XPosed? https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Roxasmaker said:
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Click to expand...
Click to collapse
Would I have to do anything to XPosed or supersu first? I'd like to update to 6.0.1, too. I've seen online that there are OTA updates for it too.
Nope. But you may have to reinstall root, which is very easy once you're updated. Just let the updates do their thing, and you'll be on your merry way! Hope I helped
I think what I'll do is flash stock 4.4.4 keeping user data and then use the OTAs to update to 6. That way I have a clean system install to use Magisk with without losing any user data. (If that doesn't work I'll just flash 6.0.1 for a clean install.)
I'm staying in S244, Updating to S251 update is seriously required for upcoming custom Roms install ?
If s251 update required,
it requires to install my stock boot and stock recovery (almost stock rom)
Wonder Wicked Witch said:
I'm staying in S244, Updating to S251 update is seriously required for upcoming custom Roms install ?
If s251 update required,
it requires to install my stock boot and stock recovery (almost stock rom)
Click to expand...
Click to collapse
no it doesn't. at least not for LOS.
im still on S244 but I'm beta testing LineageOS 14.1 which is already based on blobs from S251.
celoxocis said:
no it doesn't. at least not for LOS.
im still on S244 but I'm beta testing LineageOS 14.1 which is already based on blobs from S251.
Click to expand...
Click to collapse
Thanks for the info, Thumbs up?
I'm on s251 and full stock, the 14 days are finished for the bootloader.
So can i root my P2 safely or I must go back to s244 ?
Mathurin239 said:
I'm on s251 and full stock, the 14 days are finished for the bootloader.
So can i root my P2 safely or I must go back to s244 ?
Click to expand...
Click to collapse
no you can stay on s251 of course and still be able to unlock and root your phone.
im on s251 too now and fully reset my phone to test los beta from scratch.
P2 with TWRP and root with magisk, it's all good !!
No plan for updating to s251. Cuz I'm using custom rom and s251 is not a major update, it contains only November security patch + android pay.
Wonder Wicked Witch said:
No plan for updating to s251. Cuz I'm using custom rom and s251 is not a major update, it contains only November security patch + android pay.
Click to expand...
Click to collapse
... which you want to have