Related
Note: You can try this with EU ROMs but I'm not sure if it will work, and won't be testing to see if it works, since I see no reason to flash EU ROMs anyways.
I knew this from day 1, but was switching between various LOS ROMs so didn't have much inspiration to make a guide. Now i'm switching back to Stock-based ROMs (due to other roms having no dolby, no voice capture,...), I'll be making a guide
I'm not responsible for bricked device.
This is a guide for those who are facing issues when trying to flash US, EU stock and stock-based ROMs on the chinese axon 7 (no signal, no wifi, worse battery, or simply not booting after splash screen). Since downgrading is also a part of this guide, I will also be covering how to downgrade Nougat 7.1.1 ROMs back to 6.0.1 Marshmallow.
Important thing to note:
You must be on B13, 6.0.1 marshmallow with stock recovery, and please, DO NOT UPDATE TO B10 China NOUGAT or anything above ! This will cause a lot of problem, as from what I've deduced, US B19 is based on the China B09 update, anything above B10 won't be backwards compatible. and will cause problems like not booting, (or no wifi, signal etc after you recover the boot partition through recovery)
Now, if you're already on Nougat and want to try this guide, downgrade back to Marshmallow using EDL. Try this guide:
- Download B13 EDL (credits to djkuz from 4pda), extract it
- Download and install the latest Xiaomi MiFlash (stable or beta)
- Turn off your phone, plug it in to your PC, Hold Power + Vol Up + Vol Down, go to device manager, look for the "Port" section, and you will see something like Qualcomm HS-USB QDLoader 9008., if you see it, proceed down below. If not try again.
- right click , open properties on the Qualcomm HS-USB QDLoader 9008, go to port settings, if you see the speed is at 9600 bits per second (bps), change it to 128000 (you can skip this step, but doing it will increase your flashing speed)
- Open MiFlash, press select and pick the folder you extracted a few steps ago.
- Press refresh, if you see your device appearing on the list, press flash. (if some random errors appear, unplug the device, plug it back and immediately press refresh and press flash)
- After flashing you'll be back on B13 China Marshmallow.
REMEMBER, DON'T OTA UPDATE IF YOU WANT A SMOOTH TRANSITION TO US ROMS:
Now, to the good part:
- Download the B09 China OTA package from here (credits to Demons-77)
- put the package into your EXTERNAL sd card, internal won't do.
- reboot to recovery (Power + Vol Up)
- select the option with the word "sd" on it
- now go and pick the package that you just put in
- It will begin flashing and after that, you will have B09 China Nougat
- reboot to bootloader and install recovery (fastboot flash recovery *your file name*)
- after that you can install any roms you like, no need to backup and restore the boot partition every time you flash a US ROM, and you won't encounter strange issues like no boot, no wifi, etc.
TL;DR for those who already know how to do most of these: go back to China Marshmallow through EDL, update to B09 China Nougat with stock recovery, install TWRP and then flash whatever US stock or stock-based roms you want (just like how you would with a US phone)
Does custom kernels work after installing US roms?
I want to have a magisk compatible rom but I don't want to install custom roms other than stock.
Chinese roms doesn't boot with these existing kernels in this forum.
otaconremo said:
Does custom kernels work after installing US roms?
I want to have a magisk compatible rom but I don't want to install custom roms other than stock.
Chinese roms doesn't boot with these existing kernels in this forum.
Click to expand...
Click to collapse
what do you mean by magisk compatible rom? I'm running the latest badboyz with magisk root here, no problems at all
spiwar said:
what do you mean by magisk compatible rom? I'm running the latest badboyz with magisk root here, no problems at all
Click to expand...
Click to collapse
Ok that's great. Last time I tried badboyz, I get issues with my signal keep restarting. I'm currently using chinese B01 mifavor5. all is well, just that I can't use magisk due to the stock kernel.
Thanks for your feedback OP.
Hi, great tutorial, but I got few questions. Now I'm on chinese nougat (B15) and if I downgrade to mm, will still I be able to do this operation? Can I relock bootloader on US rom? Because some apps like android pay, pokemon go and snapchat won't work.
@spiwar Mate I could kiss you right now. But could you just point me to one of the us stock ROMs to flash? (E.g, is this one alright - A2017UV1.1.0B19_StockSystem_by_DrakenFX.zip)
Is it safe to perform ota updates of the USA firmware on Chinese axons? Cheers
Fuilares said:
Hi, great tutorial, but I got few questions. Now I'm on chinese nougat (B15) and if I downgrade to mm, will still I be able to do this operation? Can I relock bootloader on US rom? Because some apps like android pay, pokemon go and snapchat won't work.
Click to expand...
Click to collapse
Downgrading IS a part of this operation if you're already on Nougat (you need to go back to MM before you can go B09 Nougat). Why relock your BL though? Magisk root can work with Android Pay, Pokemon Go AFAIK, not sure though (since I don't use any of those apps)
tigrey said:
@spiwar Mate I could kiss you right now. But could you just point me to one of the us stock ROMs to flash? (E.g, is this one alright - A2017UV1.1.0B19_StockSystem_by_DrakenFX.zip)
Is it safe to perform ota updates of the USA firmware on Chinese axons? Cheers
Click to expand...
Click to collapse
Yes that stock ROM will be okay. Personally I'm using the latest version of BadBoyz ROM.
No you can't. Because OTA updates requires the stock recovery, and your phone probably won't boot if you flash the US Stock recovery
otaconremo said:
Ok that's great. Last time I tried badboyz, I get issues with my signal keep restarting. I'm currently using chinese B01 mifavor5. all is well, just that I can't use magisk due to the stock kernel.
Thanks for your feedback OP.
Click to expand...
Click to collapse
Magisk won't work if you're using B10 Chinese as a base (as mentioned above), if you flash on B10 you'll have to flash the boot portion from the stock Chinese ROM for the US ROMs to even boot, and then you just lose magisk.
I see. Thanks for the tips. But I don't think I'll be coming back to b13 mm for that. I hate restoring data ang all the files in my internal storage.
Hi!
Could you please clarify me a doubt?
To follow this guide, must my device already be rooted?
Thanks!
Well, first part went well. After a lot of effort, because device was recognised as DFU. Anyway, I got it back to B13 with stock recovery.
On second part, when I try installing the FOTA update, it fails, giving me error: status 8. In update history, it says that the system package did not match the phone. Obviously I have A2017.
Any suggestions?
So I just unpacked my MOTO Z with great anticipation.
However, I immediately ran into the issue where I can't backup my old phone using TiBU and restore it on my new shining gadget. I was VERY unsuccessful rooting the device.
So I went all in and installed RR which I'm using on all other devices as well. Used this TWRP to do it.
While RR is working well, it doesn't have some of the nice things stock ROM had, like the keyboard adjustability, screen on on hand-over and some adjustments in the camera app. Doesn't really matter, but I'd like to give stock another try before I inevitably commit to RR which will no doubt improve in the mean time as well.
Now, for my problem:
Using the recovery mentioned above, I made a full backup of the phone before I messed with it. Now that same recovery doesn't properly restore that backup: the phone doesn't boot when I restore that backup. it never leaves the bootloader unlocked warning screen.
So I figured: bad backup, let's get a stock image. Eh, again no go: motorola doesn't even publish those. So I grabbed the XT1650-03_GRIFFIN_RETEU... from here.
That one again doesn't even fully flash: I tried partial flash (system partition + recovery partition) - which flashed but didn't boot; then tried full flash, starting with the gpt.bin - but this one didn't even flash. reported some errors and that was it.
So, while not bricked, I'm far from any degree of control over my new phone. I'd like to improve that!
Any advice?
@velis74 to flash firmware you must use adb/fastboot. Is that what you mean by "flashed"?
lollyjay said:
@velis74 to flash firmware you must use adb/fastboot. Is that what you mean by "flashed"?
Click to expand...
Click to collapse
Yes, "flashing" of the "stock image" I tried to do with fastboot - that series of commands flashing one partition after another with images in the archive. I just didn't want to list all those commands in the post because there's more than 20...
If you´ve already updated your Stock, untouched and locked ROM from Marshmallow to Nougat, then you won't be able to Flash back to Marshmallow Stock ROM, because your Bootloader was already updated to Nougat. That's why the whole process fails. Since there's no official RETEU Nougat Stock ROM yet, use the RETBR one. It's practically the same and works as it should: https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
But keep in mind that you won't be able to relock your bootloader, since Motorola/Lenovo haven't released signed Nougat Stock ROMs yet.
doree said:
If you´ve already updated your Stock, untouched and locked ROM from Marshmallow to Nougat, then you won't be able to Flash back to Marshmallow Stock ROM, because your Bootloader was already updated to Nougat. That's why the whole process fails. Since there's no official RETEU Nougat Stock ROM yet, use the RETBR one. It's practically the same and works as it should: https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
But keep in mind that you won't be able to relock your bootloader, since Motorola/Lenovo haven't released signed Nougat Stock ROMs yet.
Click to expand...
Click to collapse
Yep, was just about to post how this thread helped. I'm back at stock and seriously contemplating not rooting. I pretty much only need it for one app where I forgot the password and they make it REALLY hard to reset it
Hello,
yesterday I read about the Generic LineageOS ROM that will work on all Project Treble compatible devices, if I understood it right. So it should also work on the Huawei MediaPad M5 since it supports Project Treble, right?
Does anyone have tried it out? And what's about Root?
I plan to buy the MediaPad M5, cuz my Pixel C is broken, but I want to have Root and a Vanilla Android ROM like LineageOS.
@Marcopoloy13 I would like to test it but as there is no firmware / ota package for the device available yet it's a bit risky. For installation you need to overwrite the recovery with TWRP but if installation fails I do not see a way back to stock. I am new to Huawei devices, probably you know wheter if at least erecovery is working you are able to return to stock?
@AndDiSa No, sadly I have no experience with Huawei devices, too. So I thing we have to wait till someone have the stock firmware?
What's about Root? Is already a rooting method working?
@Marcopoloy13 well, all rooting methods supported by Treble devices should work. I know that @phhusson has already prepared several roms based on Treble which provide root access, but first step is to get TWRP working or to have at least a save way to return to stock in case something goes wrong ...
AndDiSa said:
@Marcopoloy13 well, all rooting methods supported by Treble devices should work. I know that @phhusson has already prepared several roms based on Treble which provide root access, but first step is to get TWRP working or to have at least a save way to return to stock in case something goes wrong ...
Click to expand...
Click to collapse
FWIW, since this is yet another kirin 960, I'm fairly confident it should work, but that would make for a costly brick if it doesn't.
Could you send me your vendor/etc/selinux/nonplat_sepolicy.cil (this doesn't require root) so that I can run some early checks on it?
If GSI works, there is a way to get root/make a full dump, with two users:
User A (the most intripiduous one) installs the GSI, gets root with it, dumps all partition (except system because, well, that's the GSI)
With magisk manager, root the "ramdisk" dump.
Then user B flashes the rooted "ramdisk" partition, he gets root on stock ROM, and he can dump stock system.img
You don't need TWRP to flash a GSI, you just need fastboot, which should work natively on the device.
If the device is running Android 8.0, an Android 8.0 GSI has more chances to work than Android 8.1 GSI.
@phhusson I'll send you the vendor/etc/selinux/nonplat_sepolicy.cil when I am coming home, and to answer your question : yes, the device is running Android 8.0, so chances are not too bad, I think ...
AndDiSa said:
@phhusson I'll send you the vendor/etc/selinux/nonplat_sepolicy.cil when I am coming home, and to answer your question : yes, the device is running Android 8.0, so chances are not too bad, I think ...
Click to expand...
Click to collapse
Got it thanks, it passed the test on 8.1 AOSP.
It is not a guarantee of anything, but it's a bit safer than without the test
phhusson said:
Got it thanks, it passed the test on 8.1 AOSP.
It is not a guarantee of anything, but it's a bit safer than without the test
Click to expand...
Click to collapse
One question: do you know whether /system/etc/recovery-resource.dat contains the recovery image? I know that stock Android generally on boot is overwriting the recovery so I was wondering whether this file is/contains the recovery image ?
AndDiSa said:
One question: do you know whether /system/etc/recovery-resource.dat contains the recovery image? I know that stock Android generally on boot is overwriting the recovery so I was wondering whether this file is/contains the recovery image ?
Click to expand...
Click to collapse
Short answer is no.
Longer answer is that it is a part of recovery. in /system there is recovery-resource.dat and recovery-from-boot.p (or something like that, and recovery is made as a delta of boot.img (which you don't have access without root), and then applying recovery-from-boot.p and recovery-resource.dat on top of boot.img
phhusson said:
Short answer is no.
Longer answer is that it is a part of recovery. in /system there is recovery-resource.dat and recovery-from-boot.p (or something like that, and recovery is made as a delta of boot.img (which you don't have access without root), and then applying recovery-from-boot.p and recovery-resource.dat on top of boot.img
Click to expand...
Click to collapse
Well ... there is no recovery-from-boot.p and there is no extra partition for the recovery kernel but there is a recovery-ramdisk partition. I suppose recovery-resource.dat contains the recovery-ramdisk data, but it's only a feeling.
Edit: Hmmm ... probably not, looks more like a container of images.
I'm interessted too in the m5 but i want aosp or any custom rom. I don't like the emui one. But back to treble. Has anyone tested if it haves treble or any document what says it ? About the system img i think the one from other huaweis will not work correctly a lot of things like dpi and screen size is totaly different.
Anyone knows the codename of m5 ?
rcstar6696 said:
I'm interessted too in the m5 but i want aosp or any custom rom. I don't like the emui one. But back to treble. Has anyone tested if it haves treble or any document what says it ? About the system img i think the one from other huaweis will not work correctly a lot of things like dpi and screen size is totaly different.
Anyone knows the codename of m5 ?
Click to expand...
Click to collapse
The M5 definitely is Treble enabled. The code name for the SHT-W09, e.g. the 8.4 WiFi version is schubert.
AndDiSa said:
The M5 definitely is Treble enabled. The code name for the SHT-W09, e.g. the 8.4 WiFi version is schubert.
Click to expand...
Click to collapse
Okay thanks if we get safe way to restore stock firmware i would try to build twrp and a rom for it ( buidling for z2 and z2 tablet from sony currently) but rom building should be easy at all with treble
Twrp could be a bit harder but i think its possible to make it without kernel source. If kernel source is out it should be easy to do twrp
rcstar6696 said:
Okay thanks if we get safe way to restore stock firmware i would try to build twrp and a rom for it ( buidling for z2 and z2 tablet from sony currently) but rom building should be easy at all with treble
Twrp could be a bit harder but i think its possible to make it without kernel source. If kernel source is out it should be easy to do twrp
Click to expand...
Click to collapse
There is already kind of 'generic' TWRP for the Kirin 960 available. Either this works already or otherwise it should be easy to adapt. Biggest problem currently is the missing firmware package so that you can return to stock in case you need to ..
AndDiSa said:
There is already kind of 'generic' TWRP for the Kirin 960 available. Either this works already or otherwise it should be easy to adapt. Biggest problem currently is the missing firmware package so that you can return to stock in case you need to ..
Click to expand...
Click to collapse
Yes basicly you are right but the problem is the srenn size i think twrp is messed up if you flash the phone one. Another problem could be the display driver at all not sure if the m5 uses same driver as the rest
AndDiSa said:
There is already kind of 'generic' TWRP for the Kirin 960 available. Either this works already or otherwise it should be easy to adapt. Biggest problem currently is the missing firmware package so that you can return to stock in case you need to ..
Click to expand...
Click to collapse
Can't erecovery do that?
phhusson said:
Can't erecovery do that?
Click to expand...
Click to collapse
What do you mean ? Dump the firmware ?
rcstar6696 said:
What do you mean ? Dump the firmware ?
Click to expand...
Click to collapse
No, download and restore to a working stock firmware
@phhusson the functionality of erecovery is new to me. Can you expain how it works? Or can you give me a hint where I can get additional information about this. The only thnig I know is that erecovery is a second recovery which will / can be started when the system is messed up, but will it work on a modified system, too? Will it download the firmware if needed?
AndDiSa said:
@phhusson the functionality of erecovery is new to me. Can you expain how it works? Or can you give me a hint where I can get additional information about this. The only thnig I know is that erecovery is a second recovery which will / can be started when the system is messed up, but will it work on a modified system, too? Will it download the firmware if needed?
Click to expand...
Click to collapse
I don't know a lot about it, and I've never actually tested it.
What I know is that it has its own kernel/ramdisk/vendor/whatever, so as long as you don't flash any erecovery_* partition, you should be safe
I also know it is capable of connecting to WiFi
So considering all of this, I think that it is capable to download restore a fully functional firmware...
Perhaps you should try running eRecovery without doing flashing anything to see how it goes?
Hello everyone.
I am a fan of Android customization, and that's why i installed LineageOS 16 on my Galaxy S7 G930F.
Everything is working fine, but i am now asking myself a question: is it possible to downgrade from that Custom 9.0 to Stock 7.0/6.0 ?
Now that we installed a custom ROM, the Bootloader should be modified, right ? The stock Bootloader blocks Odin from installing older firmwares, but is it now possible ?
I don't want to try, because i have important data on my phone, a really bad internet, and i just want to be sure if it's possible or not.
Thanks to everyone for helping me .
Soriahz said:
Hello everyone.
I am a fan of Android customization, and that's why i installed LineageOS 16 on my Galaxy S7 G930F.
Everything is working fine, but i am now asking myself a question: is it possible to downgrade from that Custom 9.0 to Stock 7.0/6.0 ?
Now that we installed a custom ROM, the Bootloader should be modified, right ? The stock Bootloader blocks Odin from installing older firmwares, but is it now possible ?
I don't want to try, because i have important data on my phone, a really bad internet, and i just want to be sure if it's possible or not.
Thanks to everyone for helping me .
Click to expand...
Click to collapse
Lineage OS does not in any way modify your bootloader. You can flash your stock firmware without any issue. If you intend on keeping the data from apps on lineage os, and using it on stock, it's not going to work.
If you're referring to internal storage, that doesn't need be wiped when returning to stock (unless it's encrypted), only the data partition, system, cache, and dalvik cache need it.
Be aware that if you flash stock firmware using Odin, it will wipe your internal storage unless you use a home csc file. Not all firmwares have them. If you made a backup with twrp, you can restore that without any problems, and avoid worrying about your internal storage.
Thanks for that answer. I read on internet that the bootloader after Android 8.0 was locked at version 4, and did not let older firmwares with different bootloaders being installed with Odin. Of course I can flash the 8.0, but 7.0 and 6.0 does not seem possible because of that "impossibility". We can't use 8.0 bootloader with 7.0/6.0 because some functions will not work suck as vibrator. Flashing a custom firmware made me think that this "lock" would me removed. I already tried downgrading in the paste being on stock 8.0 and I got a fail. Thank for that answer !
Hi!
I have a VS996 with an unlocked bootloader and TWRP. I went from stock, did a full wipe (Dalvik, System, Data, Internal Storage, Cache), and tried flashing Havoc-OS (Android 10) and had issues with connecting to Wifi. So I went back to JohnFauxes VS996 flashable and now I don't have data or a working camera. Not sure what's going on here. Ideas?
TheCoryGuy said:
Hi!
I have a VS996 with an unlocked bootloader and TWRP. I went from stock, did a full wipe (Dalvik, System, Data, Internal Storage, Cache), and tried flashing Havoc-OS (Android 10) and had issues with connecting to Wifi. So I went back to JohnFauxes VS996 flashable and now I don't have data or a working camera. Not sure what's going on here. Ideas?
Click to expand...
Click to collapse
Went from stock what? Stock Oreo, Stock Pie? You have to be on stock Pie to go to LOS-17/Android 10 ROMs. LOS-17 requires LG stock Pie blobs (drivers). Yes, some have Wi-Fi connection issues. There are workarounds.
Went back to JohnFauxes VS996 flashable what? Last Pie, last Oreo? Something in between?
Going from LOS-17 back to stock you will have sensor issues which can be overcome by running in permissive mode. Other ways to overcome it is to Partition DL back to Nougat to scrub the device of all lingering LOS-17 ROM scentk, then upgrade back to newer firmware. If you don't want to do that then you need to run in permissive mode for camera to work.
I don't know what's wrong with your data.
ChazzMatt said:
Went from stock what? Stock Oreo, Stock Pie? You have to be on stock Pie to go to LOS-17/Android 10 ROMs. LOS-17 requires LG stock Pie blobs (drivers). Yes, some have Wi-Fi connection issues. There are workarounds.
Went back to JohnFauxes VS996 flashable what? Last Pie, last Oreo? Something in between?
Going from LOS-17 back to stock you will have sensor issues which can be overcome by running in permissive mode. Other ways to overcome it is to Partition DL back to Nougat to scrub the device of all lingering LOS-17 ROM scentk, then upgrade back to newer firmware. If you don't want to do that then you need to run in permissive mode for camera to work.
I don't know what's wrong with your data.
Click to expand...
Click to collapse
Went from stock Verizon Pie ROM, to Havoc 10 Q. Then from Havoc 10Q to latest John Fauxes Verizon Pie. I'm not sure how to run in permissive mode or the partition DL I'm afraid.
Glad to have you replying. My goal is to have Android 10 Q on my wife's Verizon phone. Not sure if the 'call to activate modem' bug still exists, to where you can't receive texts unless you call after reboot.
TheCoryGuy said:
Went from stock Verizon Pie ROM, to Havoc 10 Q. Then from Havoc 10Q to latest John Fauxes Verizon Pie. I'm not sure how to run in permissive mode or the partition DL I'm afraid.
Glad to have you replying. My goal is to have Android 10 Q on my wife's Verizon phone. Not sure if the 'call to activate modem' bug still exists, to where you can't receive texts unless you call after reboot.
Click to expand...
Click to collapse
* Here's the Wi-Fi workaround for V30 LOS-17/Android 10 ROMs.
* Here's how to change to Permissive mode, even on stock firmware.
* Yes, LOS-17-based ROMs (Android 10) still have the Verizon reboot bug. < There's the current V30 LOS-17 based/Android 10 ROMs bug list, and possible workarounds.
(Ignore that in some of those posts they are are calling it Q ROMs. It's Android 10. Q was merely the beta letter name for what became Android 10, and some people don't want to give that up for some reason. "N" letter beta became Nougat, "O" letter beta became Oreo, "P" letter beta became Pie, "Q" letter beta became... Android 10. Yes, Google ditched the dessert name, but STILL you no longer use the beta letter name when it graduates and gets a statue in the Google Android Park. Call it "10" if you wish, but don't call it "Q." That's like calling a butterfly a "caterpillar". That was just the beta stage of the butterfly!)
____
The major problem you are going to have with V30 Android 10 ROMs is VoLTE -- or rather the lack of it. Read #5 of the V30 Custom ROMS FAQ. End of this year -- 2020 -- Verizon is dropping CDMA. They were supposed to do it end of 2019, but delayed a year. I don't see them delaying again. This means when you make a phone call you will not be able to drop down temporarily from 4G LTE to 3G CDMA for the phone call. You will need VoLTE (Voice over LTE) for all phone calls. Stock firmware has this capability. However, no V30 LOS-based custom ROMs have VoLTE for any carriers.
On V30 you can only get VoLTE on stock firmware or custom ROMs built on stock firmware.
This is September 2020. So, while you can use V30 Android 10 ROMs, in about 3 months you will have to go back to at least rooted stock Verizon firmware to get VoLTE.
T-mobile is dropping 3G HSPA in January 2021. Of the major U.S. carriers, 0nly AT&T is holding out. They will drop HSPA in February 2022.
Discussed in depth here:
All U.S. V30/V3O+/V30S will need stock firmware, not LOS-based custom ROMs. When?
ChazzMatt said:
* Here's the Wi-Fi workaround for V30 LOS-17/Android 10 ROMs.
* Here's how to change to Permissive mode, even on stock firmware.
* Yes, LOS-17-based ROMs (Android 10) still have the Verizon reboot bug. < There's the current V30 LOS-17 based/Android 10 ROMs bug list, and possible workarounds.
Click to expand...
Click to collapse
Thanks for all the info. So I think I should go for your clean flash method by setting a partition, because I tried the WiFi fix and it forced me into Safe Mode and wouldn't otherwise boot. I think I found a flashable stock Nougat ROM, after which I intend to flash MSM Extended and get that working hopefully. So do I create a new partition in TWRP, use that for Nougat then empty the previous partition, flash Android 10 to it and get rid of Nougat again after that? Never done this before.
And setting permissive mode is done through a separate APK? Your link went to a post talking about how they used an unlinked APK to get camera and flashlight to work.
TheCoryGuy said:
Thanks for all the info. So I think I should go for your clean flash method by setting a partition, because I tried the WiFi fix and it forced me into Safe Mode and wouldn't otherwise boot. I think I found a flashable stock Nougat ROM, after which I intend to flash MSM Extended and get that working hopefully. So do I create a new partition in TWRP, use that for Nougat then empty the previous partition, flash Android 10 to it and get rid of Nougat again after that? Never done this before.
And setting permissive mode is done through a separate APK? Your link went to a post talking about how they used an unlinked APK to get camera and flashlight to work.
Click to expand...
Click to collapse
Yes, SElinuxModeChanger.apk.
You can get it here
https://forum.xda-developers.com/showthread.php?t=2524485
or here:
https://f-droid.org/en/packages/com.mrbimc.selinux/
The other ways to change permissive mode is to use a custom kernel that works with stock firmware. This apk solution is easier.
TheCoryGuy said:
Thanks for all the info. So I think I should go for your clean flash method by setting a partition, because I tried the WiFi fix and it forced me into Safe Mode and wouldn't otherwise boot. I think I found a flashable stock Nougat ROM, after which I intend to flash MSM Extended and get that working hopefully. So do I create a new partition in TWRP, use that for Nougat then empty the previous partition, flash Android 10 to it and get rid of Nougat again after that? Never done this before.
Click to expand...
Click to collapse
I can't say I'm familiar with that MSM Extended ROM. I do see it listed in the LG V30 Telegram Update channel.
If you found a working flashable stock Nougat ROM (there were two versions floating around -- one that kept TWRP and one that replaced TWRP with stock recovery) which keeps TWRP, then after using that you can flash back to stock Pie with TWRP flashable zip (you need Pie blobs for LOS-17 based ROMs), then install the LOS-17 based ROM/Android 10 ROM of your choice.
I'm confused about your question of creating a new partition. All you will be doing is flashing back to Nougat to ostensibly repair previous LOS-17 effects. Then flashing back to stock Pie firmware, then flashing your choice of LOS-17 based ROM.
The only people who create new partitions are those who want to use GSI (Treble) ROMs. Those ROMs are inferior and rely upon a user-created "Treble" partition since V30 never had official Treble. Those GSI ROMs lack many stock V30 features which "regular" LOS-based ROMs have.
ChazzMatt said:
Yes, SElinuxModeChanger.apk.
You can get it here
https://forum.xda-developers.com/showthread.php?t=2524485
or here:
https://f-droid.org/en/packages/com.mrbimc.selinux/
The other ways to change permissive mode is to use a custom kernel that works with stock firmware. This apk solution is easier.
I can't say I'm familiar with that MSM Extended ROM. I do see it listed in the LG V30 Telegram Update channel.
If you found a working flashable stock Nougat ROM (there were two versions floating around -- one that kept TWRP and one that replaced TWRP with stock recovery) which keeps TWRP, then you can flash back to stock Pie with TWRP flashable zip (you need Pie blobs for LOS-17 based ROMs), then install the LOS-17 based ROM/Android 10 ROM of your choice.
I'm confused about your question of creating a new partition. All you will be doing is flashing back to Nougat to ostensibly repair previous LOS-17 effects. Then flashing back to stock Pie firmware, then flashing your choice of LOS-17 based ROM.
Click to expand...
Click to collapse
I'm hoping I found the Nougat ROM that keeps TWRP here. When you mentioned "Partition DL back to Nougat" I took that as me needing to create a partition somewhere. Also I did indeed find MSM Extended on the Telegram Channel here.
All's I know is I need to get my wife's phone working before I go to bed (night shift), else she's gonna kick my ass for wiping it in the first place thinking I could just pop Android 10 on there. Ha. So whatever I need to do, I'll do it.
TheCoryGuy said:
I'm hoping I found the Nougat ROM that keeps TWRP here. When you mentioned "Partition DL back to Nougat" I took that as me needing to create a partition somewhere. Also I did indeed find MSM Extended on the Telegram Channel here.
All's I know is I need to get my wife's phone working before I go to bed (night shift), else she's gonna kick my ass for wiping it in the first place thinking I could just pop Android 10 on there. Ha. So whatever I need to do, I'll do it.
Click to expand...
Click to collapse
When I mentioned going back to Nougat via Partition DL I was talking about going back to full stock KDZ, not using a Nougat TWRP-flashable zip. Doing it the old-school way I was suggesting is harder but more thorough. You would use Dev Patched LGUP to go back to Nougat, wiping out TWRP. You would still have unlocked bootloader. Then you would LGUP to a Pie KDZ which has fastboot flash commands, then reinstall TWRP, reformat internal memory, then flash an Android 10 ROM.
Your way is easier.
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
TheCoryGuy said:
I'm hoping I found the Nougat ROM that keeps TWRP here.
Click to expand...
Click to collapse
That link is to JohnFawkes 20k, which is Oreo. Nougat starts with 10 then letter.
Nougat = 10 + letter
Oreo = 20-something + letter
Pie = 30-something + letter (except for Sprint which didn't go by the LG naming rules)
The Nougat TWRP flashable zips were released in the Telegram thread.
ChazzMatt said:
When I mentioned going back to Nougat via Partition DL I was talking about going back to full stock KDZ, not using a Nougat TWRP-flashable zip. Doing it the old-school way I was suggesting is harder but more thorough. You would use Dev Patched LGUP to go back to Nougat, wiping out TWRP. You would still have unlocked bootloader. Then you would LGUP to a Pie KDZ which has fastboot flash commands, then reinstall TWRP, reformat internal memory, then flash an Android 10 ROM.
Your way is easier.
Click to expand...
Click to collapse
Okay... I'm nervous. So you think I can do it without messing up recovery? Darn it.
Could I be so bold as to ask you if you have an instant messenger of some sort? I would greatly appreciate it!!
TheCoryGuy said:
Okay... I'm nervous. So you think I can do it without messing up recovery? Darn it.
Could I be so bold as to ask you if you have an instant messenger of some sort? I would greatly appreciate it!!
Click to expand...
Click to collapse
Flash back to 20K Oreo for now. Use the Permission changer app to make it be "permissive" so camera works OK.
That Oreo is stable. You don't need Pie for now -- if you just want to make the phone work.
If it works, then you can flash back to Pie TWRP flashable zip later if you wish.
In the future you can find the Nougat TWRP flashable zip posted in the Telegram thread.
I'm about to take a shower and go to work. Sorry I can't do Messenger app.