Hi, I unlocked bootloader, installed twrp, flashed a Android 10 custom rom (Havoc), flashed gapps and magisk on my US998. Flashed a different modem to get wifi working etc but after trying it for a while, there's just too much that doesn't work properly, specifically the camera and LMT. Anyway, I'm wanting to go back to stock Oreo, then maybe after that another custom Oreo or pie rom. What's the procedure for doing this, I searched around but couldn't figure it out. Thanks!
Best to temporarily downgrade to Nougat, then go back to last Oreo which is very stable.
Your bootloader will remain unlocked but you will have to reinstall TWRP (go through Section 6 of WTF Instructions again). Unless you can find the Nougat TWRP flashable zip someone on Telegram built, which keeps TWRP.
Related
I just now realized this should go into the Q&A forum.
https://forum.xda-developers.com/moto-z/help/how-return-to-stock-7-1-1-reteu-t3753540
Mods please feel free to delete this thread.
-------------------------
I have unlocked my bootloader, installed TWRP, and installed AospExtended v5.1 , which worked fine, except some moto mods are not working correctly so I would like to go back to stock 7.1.1.
Is it possible at all without bricking my phone? I have EU phone, so I suppose I need the RETEU zip, but I can only see it for 6.0.1 https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/ and I have read that after updating to 7.1.1, the bootloader is upgraded to a version that bricks your phone if you try to install MM again.
So what (and how!) to do so I can be back to 7.1.1 RETEU stock? Or I'm stuck with being able to use only custom ROMs forever?
Thanks!
Mods please delete this post. Duplicate of https://forum.xda-developers.com/moto-z/help/how-return-to-stock-7-1-1-reteu-t3753540
Sorry for the hassle!
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.
I've seen this issue crop up in many custom ROM threads but I haven't seen any resolution.
I am using the US998 model.
After installing several custom ROMs (LineageOS 16.9, LiquidRemix 10.X, AospExtended, and ResurrectionRemix 7.0) and opening YouTube it never gets past the loading icon to display any videos. I can see the options such as Library, Inbox, Subscriptions, etc but none of them load content. The app never transitions to even previews of content or text.
I've tried the following
Clean installs of each ROM (and GApps) from stock Pie
Stock Pie and dirty flash of custom ROM
Uninstall of YouTube with Titanium Backup, then install YouTube from Playstore
The only custom Pie ROM that has YouTube working is Havoc.
I've tried Magisk modules like YouTube Vanced but it doesn't fix the problem.
I enjoy Havok but would prefer a less customized ROM like Lineage (it's my first choice).
Has anyone found a solution for this?
Same exact issue after buying a new LG V30. I didn't have this issue on my old one. Also worth mentioning, my camera doesn't work as well. Everything works on Stock pie. Tried a couple custom roms, none of them work. Same issue as mentioned in this thread: https://forum.xda-developers.com/lg-v30/help/camera-app-issues-upgrading-to-pie-t3974765
Except that thread talks about stock pie, not custom roms.
^I'm_With_Stupid said:
Also worth mentioning, my camera doesn't work as well. Everything works on Stock pie. Tried a couple custom roms, none of them work. Same issue as mentioned in this thread: https://forum.xda-developers.com/lg-v30/help/camera-app-issues-upgrading-to-pie-t3974765
Except that thread talks about stock pie, not custom roms.
Click to expand...
Click to collapse
You read about the camera degradation issues and other sensors for custom ROMs if you've been on stock Pie, right? Even if you downgrade back to Oreo, you will forever have to run permissive kernel on LOS-16 based custom ROMs and it can affect certain functions on stock Oreo as well.
We have enough warnings in all the Pie KDZ threads, it's clearly detailed in the Root Sticky Guide, and linked in the WTF INSTRUCTIONS.
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
* ALSO do NOT update to LG stock Pie yet if you wish to run LOS-16 "Pie" custom ROMs -- at least for now. See REASON HERE. Stock Pie update conflicts with LOS-16 Pie, even if you downgrade back to stock Oreo. After stock Pie update, your phone has been permanently changed/degraded when going back to Oreo for custom ROMs. Using Permissive kernel can overcome some of those issues, but you have been warned.
Whereas you do need to update to stock Pie first as a foundation before trying to install "Android 10" LOS-17 custom ROMs. However, those ROMs are still unfinished work in progress -- so if you don't like them and want to go back to the older stable LOS-16 "Pie" custom ROMs, then you've totally ignored the warning above. Again, stock Pie makes permanent changes.
Click to expand...
Click to collapse
Basically don't update to stock Pie if you want to run LOS-16 custom ROMs. If you downgrade back to Oreo, you will have flashlight/camera problems and other sensors. Some of that can be overcome with permissive kernel, some can't.
It's one of the reasons I'm still on stock rooted Oreo with Anxious V30 mod and Xposed mods and have not yet updated to stock Pie on my main phone.
ChazzMatt said:
You read about the camera degradation issues and other sensors for custom ROMs once on stock Pie, right? Even if you downgrade back to Oreo, you will forever have to run permissive kernel on LOS-16 based custom ROMs and it can affect stock Oreo as well.
We have enough warnings in all the Pie KDZ threads, it's clearly detailed in the Root Sticky Guide, and linked in the WTF INSTRUCTIONS.
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Basically don't update to stock Pie if you want to run LOS-16 custom ROMs. If you downgrade back to Oreo, you will have flashlight/camera problems and other sensors. Some of that can be overcome with permissive kernel, some can't.
It's one of the reasons I'm still on stock rooted Oreo with Anxious V30 mod and Xposed mods and have not yet updated to stock Pie on my main phone.
Click to expand...
Click to collapse
Unfortunately I bought it used with Stock Pie on it already, but was still able to bootloader unlock it through the downgrade method.. Is there any way to remove these issues or is it permanent? Would downgrading to Nougat be possible/remedy anything? Is my only option to stay on stock and wait for LOS 10 to be ready?
My apologies in advance if this has been discussed before. My searching has only lead me to threads stating not to flash to pie without upgrading. I had some trouble connecting to the phone but after finally working through it and getting the bootloader unlocked and TWRP on the phone, it was late and I flashed LOS 16 before properly upgrading through each iteration of Oreo(20a -> LOS 16). The phone seems to be working fine. My question is, do I need to flash back to Nougat then oreo as discussed in some of the stock pie threads or can I just flash back to oreo 20e up to 20h?
Thanks.
Phone is US998 flashed to LOS 16 from Oreo 20a
weasellystoat said:
My apologies in advance if this has been discussed before. My searching has only lead me to threads stating not to flash to pie without upgrading. I had some trouble connecting to the phone but after finally working through it and getting the bootloader unlocked and TWRP on the phone, it was late and I flashed LOS 16 before properly upgrading through each iteration of Oreo(20a -> LOS 16). The phone seems to be working fine. My question is, do I need to flash back to Nougat then oreo as discussed in some of the stock pie threads or can I just flash back to oreo 20e up to 20h?
Thanks.
Phone is US998 flashed to LOS 16 from Oreo 20a
Click to expand...
Click to collapse
Yes, you can flash US998 20e, f, g, h, then flash back to LOS 16.
LOS-16 doesn't have to persistent changes LOS-17/Android 10 has. So, no need to go back to Nougat to scrub it clean.
hello so i got a refurbished us998 on android 7.1 i couldnt get it to update vie ota so i flashed oreo firmware with lgup after that i unlocked bootloader and installed twrp all good but after that i wanted to update to pie so i can install android 10 custom roms i flashed the pie kdz and i got stuck at lg logo couldn't boot then i tried with flashable zip same i tried flashing back 7.1 then to pie that didnt work then i flashed all the oreo zip from build 820e to 820h as mentioned in a thread and then pie
that didnt work as well so i tried to flash lineage os 16 or and other pie roms same thing they all dont boot up and got stuck on logo so is there any other ways to try that would be appreciated
stifbaker7 said:
hello so i got a refurbished us998 on android 7.1 i couldnt get it to update vie ota so i flashed oreo firmware with lgup after that i unlocked bootloader and installed twrp all good but after that i wanted to update to pie so i can install android 10 custom roms i flashed the pie kdz and i got stuck at lg logo couldn't boot then i tried with flashable zip same i tried flashing back 7.1 then to pie that didnt work then i flashed all the oreo zip from build 820e to 820h as mentioned in a thread and then pie
that didnt work as well so i tried to flash lineage os 16 or and other pie roms same thing they all dont boot up and got stuck on logo so is there any other ways to try that would be appreciated
Click to expand...
Click to collapse
In the US998 Pie KDZ thread, there's several methods to get to Pie. Look at post #2 and post #6. It sounds like you tried some of those, but read again carefully. Method #4 in post #6 seems to work for almost everyone.
You can't flash LOS-16 immediately after failing to update to Pie. Enough Pie infected the partitions that it will not work. So, if you want LOS-16 you have to flash back to Oreo first. LOS-16 needs Oreo blobs (drivers).
ChazzMatt said:
In the US998 Pie KDZ thread, there's several methods to get to Pie. Look at post #2 and post #6. It sounds like you tried some of those, but read again carefully. Method #4 in post #6 seems to work for almost everyone.
You can't flash LOS-16 immediately after failing to update to Pie. Enough Pie infected the partitions that it will not work. So, if you want LOS-16 you have to flash back to Oreo first. LOS-16 needs Oreo blobs (drivers).
Click to expand...
Click to collapse
thanks i will try method 4 but i already flashed back to oreo and los 16 still cant boot and when i boot back to twrp i find it that nth is installed and everything is wiped out 0mb its like not detecting internal storage or smth maybe partition issue like u said
edit: so i tried method 4 and it worked thanks a lot hopefully i can install adnroid 10 custom roms now