I am currently running on OOS12 l, i just miss the battery life and stability of OOS11 i am looking to downgrade my phone but in case i change my mind i need to be able to get OOS12 or 13 if it's released by then, so if not ota to 12 if i update to OOS 12 manually will i get the 13 Update?
Yeah, you can upgrade to OOS12 via OTP update once you downgraded to OOS11.
Thank you!
Related
Hi, I'm a noob seeking advice. I rooted my phone a few weeks back just because I could, but haven't really done much with it since. I haven't upgraded from 2.2.1 yet -half because I've been busy and half because I'm shy about bugs.
My question is: since LG claims it's going to release the official upgrade this month, what are the advantages of official upgrade versus unofficial? It seems like every unofficial one has bugs still, so I'd be tempted to go back to official. Also, since I've already rooted it, I'm under the impression that kills official updates. If I want to go back to the official version, would I have to unroot it first or is there a way to just allow the official update to go through?
seokso said:
Hi, I'm a noob seeking advice. I rooted my phone a few weeks back just because I could, but haven't really done much with it since. I haven't upgraded from 2.2.1 yet -half because I've been busy and half because I'm shy about bugs.
My question is: since LG claims it's going to release the official upgrade this month, what are the advantages of official upgrade versus unofficial? It seems like every unofficial one has bugs still, so I'd be tempted to go back to official. Also, since I've already rooted it, I'm under the impression that kills official updates. If I want to go back to the official version, would I have to unroot it first or is there a way to just allow the official update to go through?
Click to expand...
Click to collapse
About the 2.3 official update, everyone is waiting for that, since 2.3 unoficial Roms have bugs and unimplemented features. For example, I love the CyanogenMod rom but I had to gave up on it since the the bluetooth is not working for auriculars and for the bluetooth system on my car. The 2.3 official update will solve all the problems for these current unoficial Roms, so if you really need a fully working Rom, better not go for those 2.3 Roms available.
You should not upgrade to 2.2.1 (or 2.2.2) using the regular LG update method. That will "unroot" your phone. There are 2.2.1 and 2.2.2 official unrooted Roms (just google for that, you will find them pretty easy). In that case you won't use the KDZ method but the safer Android Recovery method (avoid using the KDZ!! it's the easiest way to kill your phone!!).
So... if you just want to "unroot" your phone, you can always get the official update back in your phone, by using the KDZ method. KDZ reflashes your phone, and that's why the risk is higher than using the Android Recovery method which one wipes out some things like /system/*
mix em both and they will shine...I hope LG's release sky rocket's mik CM7 rom and then i will permanently switch to CM...they simply rock..
l4g4rt0 said:
About the 2.3 official update, everyone is waiting for that, since 2.3 unoficial Roms have bugs and unimplemented features. For example, I love the CyanogenMod rom but I had to gave up on it since the the bluetooth is not working for auriculars and for the bluetooth system on my car.
Click to expand...
Click to collapse
That's exactly why I haven't gone for it yet. That and I've heard the GPS is still buggy.
l4g4rt0 said:
You should not upgrade to 2.2.1 (or 2.2.2) using the regular LG update method. That will "unroot" your phone.
Click to expand...
Click to collapse
I already had the official 2.2.1 before I rooted with GingerBreak, and haven't changed from that. I thought that rooting the phone would automatically block the OTA updates. Is there a way to simply allow the OTA 2.3 update when it comes?
As for kdz versus Android Recovery, everything I've seen around the web for returning to stock says to flash using kdz. Are you talking about using home+vol down+power?
I am currently running a SMG925V with 5.0.2
baseband G925VVRU2OAF1
3.10.61 Wednesday June 17 Kernel
I'm hoping a root option will come around. If I take the update to what ever it is next, will I hurt my chances of finding a root option?
Septaric said:
I am currently running a SMG925V with 5.0.2
baseband G925VVRU2OAF1
3.10.61 Wednesday June 17 Kernel
I'm hoping a root option will come around. If I take the update to what ever it is next, will I hurt my chances of finding a root option?
Click to expand...
Click to collapse
The root exploit was patched in this build. And this build onward prevents downgrading. I personally believe that sometime in the future a new root exploit will be found, but since there is no knowing if or when that will happen, I recommend you take the ota
Hi my step son has this phone running blisspop 5.1.1 I want to update his phone to marshmallow. Can I just flash the latest cm 13 or should I odin back to stock and update that way then go through the rooting process? Im not sure if the bootloader and radio and kernel should be updated the stock way first.
I do know with my note 2 I could just flash the latest cm and flash the radio seperate. But this phone is a little foreign to me.
mojorisin7178 said:
Hi my step son has this phone running blisspop 5.1.1 I want to update his phone to marshmallow. Can I just flash the latest cm 13 or should I odin back to stock and update that way then go through the rooting process? Im not sure if the bootloader and radio and kernel should be updated the stock way first.
I do know with my note 2 I could just flash the latest cm and flash the radio seperate. But this phone is a little foreign to me.
Click to expand...
Click to collapse
Currently all the CM-13.0 based ROMs cannot boot with the official marshmallow bootloader. So it would be better to just clean flash the latest CM 13
Good thing I asked. I'm sure the cm team will figure that out at some point. It's actually the reason I asked because I remember on my note 2 going from JB mr1 to mr2 Samsung implemented Knox and sxrewed up everything. Dam girls phone was stock so I did the over he air update this morning. Oh well she doesn't really care anyway.
it's not like you'll wait long for CM to work with the latest bootloader https://review.cyanogenmod.org/#/c/146515
EDIT: it's not like you cant update either, just install CM13 WITHOUT updating stock (which will include the bootloader), aka if you're G900TUVS1FOL1 or older, then CM13 (marshmallow) should work as it has been for the last 5 months
Hello, my name is Andy.
I'm using Padfone S since 2015 and it's been 3 years now.
I'm trying to downgrade my phone to either LP or KK because GPS in MM is terrible and apps can only use internal storage.
After almost 2 year using MM, I've decided to revert back but ASUS said that they the tools to do it.
I've successfully downgrade from LP to KK using Firmware Version Version WW_99.99.99.0 from https://www.asus.com/Phone/PadFone_S_PF500KL/HelpDesk_Download/. But there's no downgrade from MM to LP.
I want to ask, if someone ever try or from ASUS representative, can I downgrade from MM to KK using the firmware above...?
If it possile, is the process the same as updating it...? (Place it in internal storage and let it auto update it...?)
Thank you very much.
winged_potato said:
Hello, my name is Andy.
I'm using Padfone S since 2015 and it's been 3 years now.
I'm trying to downgrade my phone to either LP or KK because GPS in MM is terrible and apps can only use internal storage.
After almost 2 year using MM, I've decided to revert back but ASUS said that they the tools to do it.
I've successfully downgrade from LP to KK using Firmware Version Version WW_99.99.99.0 from https://www.asus.com/Phone/PadFone_S_PF500KL/HelpDesk_Download/. But there's no downgrade from MM to LP.
I want to ask, if someone ever try or from ASUS representative, can I downgrade from MM to KK using the firmware above...?
If it possile, is the process the same as updating it...? (Place it in internal storage and let it auto update it...?)
Thank you very much.
Click to expand...
Click to collapse
Did you managed to downgrade MM?
Hello,
I have searched a lot on xda and google and didn't find any answer thus far. Maybe somebody knows this.
I have Griffin model 1650-03 I believe. It was running 7.1 stock RETEU. I have unlocked the bootloader, and proceeded to install the 8.0 a whole ago RETUS (I believe it was the december one). Worked fine, installed magisk and it bootlooped. No problem, I'll just install a custom 8.0 ROM (currently RRO), working fin for months, but now, for reasons and mods, I got to install stock. I usually don't use this device, my main is a Google, so I have read countless posts about how dangerous it is to install stock back, devices bricking left and right. I came across an unbricking solution just in case, but sadly that is for nougat faults, oreo is no-go. And all the guides I've found here and on Google are for 7.1 and I'm on 8.1 with feb security patch. I believe I still have the bootloader from that RETUS update.
TLDR, what is a safe way to return to stock from Custom 8.1 rom?
Thanks
I think since the stock rom is 8.0 it might brick your device... Not sure though.
snsone said:
Hello,
I have searched a lot on xda and google and didn't find any answer thus far. Maybe somebody knows this.
I have Griffin model 1650-03 I believe. It was running 7.1 stock RETEU. I have unlocked the bootloader, and proceeded to install the 8.0 a whole ago RETUS (I believe it was the december one). Worked fine, installed magisk and it bootlooped. No problem, I'll just install a custom 8.0 ROM (currently RRO), working fin for months, but now, for reasons and mods, I got to install stock. I usually don't use this device, my main is a Google, so I have read countless posts about how dangerous it is to install stock back, devices bricking left and right. I came across an unbricking solution just in case, but sadly that is for nougat faults, oreo is no-go. And all the guides I've found here and on Google are for 7.1 and I'm on 8.1 with feb security patch. I believe I still have the bootloader from that RETUS update.
TLDR, what is a safe way to return to stock from Custom 8.1 rom?
Thanks
Click to expand...
Click to collapse
Restore the TWRP backup you did for the stock rom, if you didn't do a TWRP backup you should be fine flashing stock rom the same version you had before installing custom ROMs. Remember if you get a brick it means you are most likely downgrading or upgrading (upgrade should be done with OTA and incrementally to stay safe)
Vcek said:
Restore the TWRP backup you did for the stock rom, if you didn't do a TWRP backup you should be fine flashing stock rom the same version you had before installing custom ROMs. Remember if you get a brick it means you are most likely downgrading or upgrading (upgrade should be done with OTA and incrementally to stay safe)
Click to expand...
Click to collapse
Hello, thank for replying,
So I should be fine if I install via fastboot the same stock RETUS I did before going custom. Should I ota over motorola's software or fastboot? Also, can I be able to OTA RETEU over RETUS?
Thank you
snsone said:
Hello, thank for replying,
So I should be fine if I install via fastboot the same stock RETUS I did before going custom. Should I ota over motorola's software or fastboot? Also, can I be able to OTA RETEU over RETUS?
Thank you
Click to expand...
Click to collapse
I would recommend OTA through the device but it's not reversible (once you flash it you can't downgrade because of bootloader upgrade)
Flashing reteu over retus should be fine as long as you are doing it manually and are aware which partitions you are flashing and which you are omitting. I don't recommend this because sometimes it can break certain things like wifi or data signal (especially if you are on stock rom) and doing OTA later through the device can cause errors
Tldr;
If you want to stay on stock rom, flash back to stock then update everything through rom
If you need root or play around with custom ROMs then don't flash anything just reinstall a stock-like custom ROM
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-install-official-oreo-t3768712 this is the guide i've used to update to oreo (which is RETUS and my device is RETEU), then installed RRO. My guess is I have to install all oreo partitions again (I installed all as stated in that guide) and let it do its OTAs. I had no problems with IMEI and signal on RRO.