I bought a LG V30+ from ebay which had Magisk installed but its a system app. I updated Magisk to 18.1 unknowingly it would screw up. I tried to install Magisk through the Manager but unable to unpack the boot image.
I would appreciate any of your help.
zacklim405 said:
I bought a LG V30+ from ebay which had Magisk installed but its a system app. I updated Magisk to 18.1 unknowingly it would screw up. I tried to install Magisk through the Manager but unable to unpack the boot image.
I would appreciate any of your help.
Click to expand...
Click to collapse
Boot to TWRP, uninstall Magisk using the TWRP Magisk uninstaller.
Google it.
Then reinstall Magisk in TWRP.
Clean caches before rebooting.
You can download both the Magisk uninstaller and Magisk itself on PC and transfer over to phone while in TWRP, connected to PC.
zacklim405 said:
I bought a LG V30+ from ebay which had Magisk installed but its a system app. I updated Magisk to 18.1 unknowingly it would screw up. I tried to install Magisk through the Manager but unable to unpack the boot image.
I would appreciate any of your help.
Click to expand...
Click to collapse
Have this happen to me me on every fresh install.
Extract the magisk APK, install it. Have it download the newest manager and flash that in TWRP.
Sent from my LG-H932 using XDA Labs
ChazzMatt said:
Boot to TWRP, uninstall Magisk using the TWRP Magisk uninstaller.
Google it.
Then reinstall Magisk in TWRP.
Clean caches before rebooting.
You can download both the Magisk uninstaller and Magisk itself on PC and transfer over to phone while in TWRP, connected to PC.
Click to expand...
Click to collapse
I don't have TWRP installed yet, but my bootloader is unlocked. Can I install TWRP without wiping my phone's data?
zacklim405 said:
I don't have TWRP installed yet, but my bootloader is unlocked. Can I install TWRP without wiping my phone's data?
Click to expand...
Click to collapse
You can root without TWRP, but it can cause problems. You can't make backups to restore, you might accidentally install OTA updates -- which could brick the phone (which having TWRP custom recovery won't allow).
If you install TWRP the way I recommend, yeah you'll wipe data. On purpose, because you'll disable LG's nosy root checker file (none of their business if I have root) and disable LG encryption. (Then you can enable TWRP encryption if you wish.)
---------- Post added at 06:49 AM ---------- Previous post was at 06:47 AM ----------
zacklim405 said:
I bought a LG V30+ from ebay which had Magisk installed but its a system app. I updated Magisk to 18.1 unknowingly it would screw up. I tried to install Magisk through the Manager but unable to unpack the boot image.
I would appreciate any of your help.
Click to expand...
Click to collapse
What LG V30+ do you have? What is the variant? US998, H930G, H939DS?
ChazzMatt said:
You can root without TWRP, but it can cause problems. You can't make backups to restore, you might accidentally install OTA updates -- which could brick the phone (which having TWRP custom recovery won't allow).
If you install TWRP the way I recommend, yeah you'll wipe data. On purpose, because you'll disable LG's nosy root checker file (none of their business if I have root) and disable LG encryption. (Then you can enable TWRP encryption if you wish.)
---------- Post added at 06:49 AM ---------- Previous post was at 06:47 AM ----------
What LG V30+ do you have? What is the variant? US998, H930G, H939DS?
Click to expand...
Click to collapse
Seems like the best way is to just backup everything I have and install TWRP normally. Is there anything else I should know before doing such a thing? I have the US998 variant btw.
zacklim405 said:
Seems like the best way is to just backup everything I have and install TWRP normally. Is there anything else I should know before doing such a thing? I have the US998 variant btw.
Click to expand...
Click to collapse
That's about it. Your bootloader is already unlocked, so you don't need to downgrade back to US998 20a or 20b.
What software version are you on? 20-what?
ChazzMatt said:
That's about it. Your bootloader is already unlocked, so you don't need to downgrade back to US998 20a or 20b.
What software version are you on? 20-what?
Click to expand...
Click to collapse
20a.
zacklim405 said:
20a.
Click to expand...
Click to collapse
Very old. We're on 20H now with lots of fixes, improvements, DTS 3D stereo. You can upgrade via TWRP flashable zips once you get everything straightened out.
Also strongly consider installing this V30 Magisk mod:
[Magisk Module] AnxiousV30 (v224)
Works with rooted stock firmware, specifically North American variants. Best with US998 and VS996 but can work with others.
ChazzMatt said:
Very old. We're on 20H now with lots of fixes, improvements, DTS 3D stereo. You can upgrade via TWRP flashable zips once you get everything straightened out.
Also strongly consider installing this V30 Magisk mod:
[Magisk Module] AnxiousV30 (v224)
Works with rooted stock firmware, specifically North American variants. Best with US998 and VS996 but can work with others.
Click to expand...
Click to collapse
I've encountered a problem when I installed TWRP through adb, I saw it was done in 0.000 seconds which is kind of fishy. Tried to boot into TWRP, nothing happened, just the normal factory data reset settings. Is this normal?
zacklim405 said:
I've encountered a problem when I installed TWRP through adb, I saw it was done in 0.000 seconds which is kind of fishy. Tried to boot into TWRP, nothing happened, just the normal factory data reset settings. Is this normal?
Click to expand...
Click to collapse
How did you try to boot to TWRP? If you try through the hardware buttons (called hardware button dance) you'll get that until you mash the correct yes buttons. But that's not how you should boot to TWRP unless in case of emergency. Instead you should use the fastboot boot command. It's in my WTF instructions. You did read that, right? You have to boot straight to TWRP after installing or TWRP will not stick, and you have to make it writable before booting back to your OS or TWRP will not stick.
Then after root, you install the Reboot Recovery app and give it root privileges.
ChazzMatt said:
How did you try to boot to TWRP? If you try through the hardware buttons (called hardware button dance) you'll get that until you mash the correct yes buttons. But that's not how you should boot to TWRP unless in case of emergency. Instead you should use the fastboot boot command. It's in my WTF instructions. You did read that, right? You have to boot straight to TWRP after installing or TWRP will not stick, and you have to make it writable before booting back to your OS or TWRP will not stick.
Then after root, you install the Reboot Recovery app and give it root privileges.
Click to expand...
Click to collapse
Ah now I know what I did wrong. Finally got Magisk to work again. I absolutely forgot the fastboot boot command. Thanks man, I really appreciate all the great help.
Related
I did a data wipe accidentally in TwRP. Meant to just get cache. Now I lost root/TWRP apparently. Just recently updated to 20c. I have no recovery when I reboot but I still get the unlocked bootloader info when rebooting. Any ideas/help is greatly appreciated.
Jjavitable22 said:
I did a data wipe accidentally in TwRP. Meant to just get cache. Now I lost root/TWRP apparently. Just recently updated to 20c. I have no recovery when I reboot but I still get the unlocked bootloader info when rebooting. Any ideas/help is greatly appreciated.
Click to expand...
Click to collapse
I don't see how wiping data would remove TWRP, but the way I'd reestablish TWRP once it's gone would be to LGUP the Tungkick 10d tot file and then use that TWRP to flash the 20c zip by Autoprime. Flash SuperSU one way or another and then have a blast. I'm sure there are other ways to accomplish all this, but this way is easy and has been reliable for me.
It seems that you can still boot the phone.
If you still have valid bootloader the issue is not that tricky.
Just do a "adb reboot bootloader" and reflash twrp, like how you installed them in the first place.
I'm not sure which exact version of twrp is compatible with v20*, but that should be easy to find anyway.
Then boot into twrp and flash supersu/magisk/any other thing you need.
ReVanTis said:
It seems that you can still boot the phone.
If you still have valid bootloader the issue is not that tricky.
Just do a "adb reboot bootloader" and reflash twrp, like how you installed them in the first place.
I'm not sure which exact version of twrp is compatible with v20*, but that should be easy to find anyway.
Then boot into twrp and flash supersu/magisk/any other thing you need.
Click to expand...
Click to collapse
So I did a factory reset from the settings menu. Now it boots back into TWRP. Weird. But that's it. No OS. Just the recovery. So I guess I'll try and flash a ROM and see if I can get that back. Thanks for trying to help.
Bulkang U. Antibop said:
I don't see how wiping data would remove TWRP, but the way I'd reestablish TWRP once it's gone would be to LGUP the Tungkick 10d tot file and then use that TWRP to flash the 20c zip by Autoprime. Flash SuperSU one way or another and then have a blast. I'm sure there are other ways to accomplish all this, but this way is easy and has been reliable for me.
Click to expand...
Click to collapse
Wasn't sure if I could do any 10s coming from 20C. I got into TWRP recovery but now I have no OS. Thanks for helping out.
Jjavitable22 said:
Wasn't sure if I could do any 10s coming from 20C. I got into TWRP recovery but now I have no OS. Thanks for helping out.
Click to expand...
Click to collapse
Yeah, as long as the ARB is the same (ANTIROLLBACK 01) you can flash 10 after 20. I don't think 10a qualifies, but 10d should be okay from 20a or 20c.
It's a quirk of the G5 that TWRP can only be accessed from boot by factory reset of the phone. If you are already up and rooted, you can use a command or program AFTER boot to access TWRP without factory reset. But, for now, that's our doorway into TWRP from power-off.
Now that you're in TWRP you can sideload a ROM onto your SD and flash it, just remember to also flash the latest superSU zip afterward to ensure root (unless your ROM is pre-rooted.)
It seems it is impossible to get root with magisk on latest Oreo stock. Maybe someone found solution?
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
its not work for me:crying:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
dolar4ik said:
Try to follow this guide then: https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
But use latest magisk beta instead of suggested 15.3.
And keep in mind that it is possible to easily restore working state with magisk uninstaller.
Do you have any errors during magisk or workaround installation in twrp console?
Click to expand...
Click to collapse
now its working for me.:highfive::highfive:
dolar4ik said:
I asked and I answer =)
To get the root it is required to
- install latest TWRP (current version twrp-3.2.1-0)
- reboot to TWRP
- install 16.2 or higher magisk, link for 16.2
- install f2fs bug workaround
- reboot system
- install magisk Manager
- enjoy your root =)
Click to expand...
Click to collapse
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
evnimaster said:
Hi, does not work for me, stuck at bootloader logo, tried Magisk, followed the steps many times but nothing, can you help please ?
Click to expand...
Click to collapse
follow this: https://forum.xda-developers.com/mot...reo-8-t3743273
Code:
echo keepverity=true>>/data/.magisk
echo keepforceencrypt=true>>/data/.magisk
Is there a way to remove encryption already?
Remove root?
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
DavidKalil10 said:
Is it possible to remove root and the TWRP without hard reset? Does anyone already have the original recovery of Oreo?
Click to expand...
Click to collapse
There is magisk uninstaller provided in official thread.
To remove twrp you just need to flush original recovery via fastboot
Hello guys, can I have some advice on whether I should install this latest Oreo update on my moto z, how is the battery doing on this update? And overall experience?
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
lesbianu said:
Flash the Magisk uninstaller, reboot to recovery (you have this option in TWRP) and flash again only the Magisk 16.3 (without the f2fs bug workaround). This worked for me two days ago.
Today I updated to the latest Magisk 16.4 without any problems.
Click to expand...
Click to collapse
still not work for me.:crying::crying:
---------- Post added at 03:12 AM ---------- Previous post was at 02:58 AM ----------
This is strange. It works on Oreo OTA but it does not work in full flash Oreo ROM.
have anyone help me??
rakee said:
It works on Oreo OTA but it does not work in full flash Oreo ROM.
Click to expand...
Click to collapse
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
rakee said:
@dolar4ik
i reflash the stock oreo ROM,then flash TWRP,flash magisk,flash f2fs bug workaround, stuck at bootloader logo,how can i do it??
Click to expand...
Click to collapse
Uninstall magisk with it's own uninstaller.
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
The Marionette said:
I installed Magisk on the full Oreo release and everything is working.
I did make a "less bloat, less bs" zip version but I doubt it would make a change.
If you guys want, I can upload it when I get home.
Click to expand...
Click to collapse
Could you provide your twrp ZIP Version? That would be great.
lesbianu said:
This is right.
I re-flashed my phone using the OPL27.76-51 firmware. Now, no way to install Magisk (old, new, any version).
The solution, I restored a TWRP backup made at the first bootloader unlock (when the ROM was updated only using OTAs, not flashed). Immediately I was able to install Magisk 16.4 - without any F2FS workaround.
HERE is my TWRP backup containing the partitions: Boot, Data & System. Hope it helps!
Click to expand...
Click to collapse
Just got myself a hand me down Moto z.
My friend who gave it to me hasn't touch the phone for a year.
So i started with 6.0 and after multiple updates, now i am on Oreo.
Since i have done ota from Marshmallow, would this method work?
Bootloader was never unlocked.
thanks for any input
Hello all,
I have a Verizon LG V30 that I converted to a US998 LG V30 using the Frankenstein method. Today, I clicked the Uninstall option in Magisk Manager and the device uninstalled it and rebooted. Upon rebooting, I was thrown into Fastboot mode with no way to get out (No Recovery, nothing.) I tried resetting through Fastboot to no avail. It still connects with Fastboot but nothing else. I can flash firmware with the patched LGUP but no file I have tried has worked. Is there anyway I can flash my V30 back to Stock VS996? Thank you.
Charbleach said:
Hello all,
I have a Verizon LG V30 that I converted to a US998 LG V30 using the Frankenstein method. Today, I clicked the Uninstall option in Magisk Manager and the device uninstalled it and rebooted. Upon rebooting, I was thrown into Fastboot mode with no way to get out (No Recovery, nothing.)
Click to expand...
Click to collapse
Why isn't there a way to get into Recovery? Use the same fastboot commands you got into recovery the first time you installed TWRP. You can even use those commands to boot to TWRP on your phone even when TWRP is not installed on your phone, via "temp" TWRP.
Since you uninstalled root, you can't use the Reboot Recovery app anymore -- as that requires root access -- but you can still use the fastboot flash commands.
Charbleach said:
I tried resetting through Fastboot to no avail. It still connects with Fastboot but nothing else. I can flash firmware with the patched LGUP but no file I have tried has worked. Is there anyway I can flash my V30 back to Stock VS996? Thank you.
Click to expand...
Click to collapse
Yes, go into Download mode manually and use dev patched LGUP to flash VS996 Oreo KDZ with DL Partition method. Flash all partitions. Not sure why you are doing that however. You decided you don't want to own your phone anymore?
People who want to KEEP root and TWRP and go back to VS998 would use DL Partition method -- but UNtick the partition recovery partitions. Then you would still have VS996 but with TWRP. You would no longer have fastboot flash commands, but you would still have TWRP custom recovery. Then you just flash Magisk root. So you would have VS998 with TWRP and root.
And at that point you could even use the reboot recovery app with root to always easily get to TWRP.
ChazzMatt said:
Why isn't there a way to get into Recovery? Use the same fastboot commands you got into recovery the first time you installed TWRP. You can even use those commands to boot to TWRP on your phone even when TWRP is not installed on your phone, via "temp" TWRP.
Since you uninstalled root, you can't use the Reboot Recovery app anymore -- as that requires root access -- but you can still use the fastboot flash commands.
Yes, go into Download mode manually and use dev patched LGUP to flash VS996 Oreo KDZ with DL Partition method. Flash all partitions. Not sure why you are doing that however. You decided you don't want to own your phone anymore?
People who want to KEEP root and TWRP and go back to VS998 would use DL Partition method -- but UNtick the partition recovery partitions. Then you would still have VS996 but with TWRP. You would no longer have fastboot flash commands, but you would still have TWRP custom recovery. Then you just flash Magisk root. So you would have VS998 with TWRP and root.
And at that point you could even use the reboot recovery app with root to always easily get to TWRP.
Click to expand...
Click to collapse
Thank you very much. I am booting up my ADB and Fastboot to flash TWRP, as I still at least have an unlocked boot loader. I’ll download a Oreo KDZ for the Verizon Variant if that doesn’t work out. Do you have any sources for one on the forums? Thank you!
EDIT: Once I get into recovery, should I flash a stock ROM? There are a few on the ROMs section of the forums but I do not non which one to download.
Charbleach said:
Thank you very much. I am booting up my ADB and Fastboot to flash TWRP, as I still at least have an unlocked boot loader. I’ll download a Oreo KDZ for the Verizon Variant if that doesn’t work out. Do you have any sources for one on the forums? Thank you!
EDIT: Once I get into recovery, should I flash a stock ROM? There are a few on the ROMs section of the forums but I do not non which one to download.
Click to expand...
Click to collapse
1) Do your want to keep TWRP and root and just flash back to VS996 (while keeping TWRP and root)?
2) Or do you want to just keep TWRP but you don't want root right now?
If #1, once in TWRP, reflash Magisk.
Then reboot, and go into manual download mode BEFORE opening the patched LGUP. Then Frankenstein back to VS996 with DL PARTITION method, but untick (uncheck) the recovery partitions. Then you'll be back to VS996, but still have TWRP and be rooted.
ChazzMatt said:
1) Do your want to keep TWRP and root and just flash back to VS996 (while keeping TWRP and root)?
2) Or do you want to just keep TWRP but you don't want root right now?
If #1, once in TWRP, reflash Magisk.
Then reboot, and go into manual download mode BEFORE opening the patched LGUP. Then Frankenstein back to VS996 with DL PARTITION method, but untick (uncheck) the recovery partitions. Then you'll be back to VS996, but still have TWRP and be rooted.
Click to expand...
Click to collapse
Don't mind my other comment, I fixed what was going on there for the most part. I have tried 2 different firmware files and both of them will not boot. The Official LG Boot image (flashable with TWRP) flashed with no errors, but i just booted into download mode again. I also flashed LineageOS and the same thing happened. I tried the Refurbish and Upgrade option through LGUP and both stopped at 19% with error 0x2000. Do you have any suggestions? Thank you.
Charbleach said:
Don't mind my other comment, I fixed what was going on there for the most part. I have tried 2 different firmware files and both of them will not boot. The Official LG Boot image (flashable with TWRP) flashed with no errors, but i just booted into download mode again. I also flashed LineageOS and the same thing happened. I tried the Refurbish and Upgrade option through LGUP and both stopped at 19% with error 0x2000. Do you have any suggestions? Thank you.
Click to expand...
Click to collapse
Same thing happened to mine I found no fix other then to lie to both Sprint and LG till LG agreed to take it in and fix it...
There will(hopefully) be a lot of otas coming to Poco F1 for bug fixing. So if we are rooted with Magisk we cannot install Otas directly as magisk modifies our stock boot image. And since poco doesn't have A/B partitions we cannot install OTA's and still keep Magisk. That brings us to Flashfire which can preserve root. Flashfire doesn't work on MIUI 9.6.14.0 (it doesn't work on mine) .So how do we install OTAs while preserving Magisk ? Is it possible or do we have to flash stock recovery and stock boot image and lose magisk ?
OTA update method according to topjohnwu:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Would be helpful if somebody can post a diy in the guide section on how to apply OTAs on Magisk rooted devices.
I would be very interested as well!!
Go to recovery.
Flash Magisk zip to restore old kernel backup.
Boot to system, you will not have root.
Update.
You still have TWRP, install Magisk again.
Profit.
I did flash my ota via stock recovery . You need flash stock recovery then go to system update after done go back to twrp and your magisk
abdohop said:
I did flash my ota via stock recovery . You need flash stock recovery then go to system update after done go back to twrp and your magisk
Click to expand...
Click to collapse
Could you please be more specific?
1. Flash stock recovery (so you loose Twrp)
2. Boot to System and make update
3. Flash twrp again and root again with Magisk?
Thanks
---------- Post added at 07:59 AM ---------- Previous post was at 07:57 AM ----------
trax7 said:
Go to recovery.
Flash Magisk zip to restore old kernel backup.
Boot to system, you will not have root.
Update.
You still have TWRP, install Magisk again.
Profit.
Click to expand...
Click to collapse
You mean that flashing Magisk again will "undo" root?
DoudouJack said:
You mean that flashing Magisk again will "undo" root?
Click to expand...
Click to collapse
Yes.
trax7 said:
Yes.
Click to expand...
Click to collapse
Hi, just booted into TWRP and flashed Magisk zip file, I'm still rooted.
Do you mean then the uninstaller Magisk file? If so, it will remove packages as well and root will still be there... Could you please be more explicit? Thanks!
DoudouJack said:
Hi, just booted into TWRP and flashed Magisk zip file, I'm still rooted.
Do you mean then the uninstaller Magisk file? If so, it will remove packages as well and root will still be there... Could you please be more explicit? Thanks!
Click to expand...
Click to collapse
Magisk makes a backup of ur boot.img, which you need to use OTAs, to restore it, you can flash Magisk again to restore it. (that's how it should work)
trax7 said:
Magisk makes a backup of ur boot.img, which you need to use OTAs, to restore it, you can flash Magisk again to restore it. (that's how it should work)
Click to expand...
Click to collapse
In my case flashing Magisk again did not work. From Magisk Manager -> Uninstall either since it was "unable to download".
For those who would be in the same case, I did following steps to update:
- Download latest Magisk uninstaller (currently 17.3, I tested with 17.1 & 17.2)
- Boot into TWRP (I use an app for convenience), go to Install > flash the Magisk uninstaller zip and (optional) boot to system to make sure root is gone (with Root Checker e.g.)
- Power off device and boot into Fastboot, flash stock boot.img (you can find it in the ROM folder you used to install your ROM), boot to System and install OTA update via the update manager, then reboot
- At this point I was stuck in fastboot screen, I simply booted with TWRP (with decryption working) and it took care of installing the update, I then flashed Magisk from there.
DoudouJack said:
Could you please be more specific?
1. Flash stock recovery (so you loose Twrp)
2. Boot to System and make update
3. Flash twrp again and root again with Magisk?
Thanks
---------- Post added at 07:59 AM ---------- Previous post was at 07:57 AM ----------
You mean that flashing Magisk again will "undo" root?
Click to expand...
Click to collapse
Correct
Sandepp said:
There will(hopefully) be a lot of otas coming to Poco F1 for bug fixing. So if we are rooted with Magisk we cannot install Otas directly as magisk modifies our stock boot image. And since poco doesn't have A/B partitions we cannot install OTA's and still keep Magisk. That brings us to Flashfire which can preserve root. Flashfire doesn't work on MIUI 9.6.14.0 (it doesn't work on mine) .So how do we install OTAs while preserving Magisk ? Is it possible or do we have to flash stock recovery and stock boot image and lose magisk ?
OTA update method according to topjohnwu:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Would be helpful if somebody can post a diy in the guide section on how to apply OTAs on Magisk rooted devices.
Click to expand...
Click to collapse
Try this guide, https://forum.xda-developers.com/poco-f1/how-to/step-step-guide-flashing-ota-beta-t3878730
Darklouis said:
Try this guide, https://forum.xda-developers.com/poco-f1/how-to/step-step-guide-flashing-ota-beta-t3878730
Click to expand...
Click to collapse
Its ok I have already flashed several OTAs, custom roms and kernels on my pocophone.
Sandepp said:
Its ok I have already flashed several OTAs, custom roms and kernels on my pocophone.
Click to expand...
Click to collapse
Is that so? What custom recovery you used?
Darklouis said:
Is that so? What custom recovery you used?
Click to expand...
Click to collapse
Twrp with working decryption
Sandepp said:
Twrp with working decryption
Click to expand...
Click to collapse
About that recovery, data partition will not get encrypted when you flash OTA update?
Darklouis said:
About that recovery, data partition will not get encrypted when you flash OTA update?
Click to expand...
Click to collapse
It will but I am ok with encryption. If you don't want then flash disable force encryption from twrp after flahsing the ota or flash magisk which will disable force encryption.
Sandepp said:
It will but I am ok with encryption. If you don't want then flash disable force encryption from twrp after flahsing the ota or flash magisk which will disable force encryption.
Click to expand...
Click to collapse
Nice nice.. Thanks for the tip
Darklouis said:
Nice nice.. Thanks for the tip
Click to expand...
Click to collapse
You're welcome
I might have done something stupid, would really appreciate it if you folks can help me get back to US998 Oreo.
I installed VS99630c (Pie) on my phone, via TWRP. After this the bootloader warning disappeared, so I suspect my bootloader has been re-locked. I can’t access TWRP anymore, neither from factory reset, nor from ADB commands on PC (the phone just reboots normally). I can’t get to fastboot either. However I can access Download Mode.
How should I proceed?
paxvalon said:
I might have done something stupid, would really appreciate it if you folks can help me get back to US998 Oreo.
I installed VS99630c (Pie) on my phone, via TWRP. After this the bootloader warning disappeared, so I suspect my bootloader has been re-locked. I can’t access TWRP anymore, neither from factory reset, nor from ADB commands on PC (the phone just reboots normally). I can’t get to fastboot either. However I can access Download Mode.
How should I proceed?
Click to expand...
Click to collapse
No, your bootloader is not re-locked. The Verizon firmware does not have a bootloader unlock warning. Verizon never thought they would need one...
You don't have fastboot flash commands on Verizon firmware. That's why you needed to temporarily convert to US998 to bootloader unlock and install TWRP.
To boot to TWRP, have you tried to use the Reboot Recovery app I STRONGLY RECOMMEND in all the Pie KDZ threads? Or boot to TWRP from Magisk Manager? If you have TWRP, either work unless you've wiped out TWRP.
ChazzMatt said:
To boot to TWRP, have you tried to use the Reboot Recovery app I STRONGLY RECOMMEND in all the Pie KDZ threads? Or boot to TWRP from Magisk? If you have TWRP, either work unless you've wiped out TWRP.
Click to expand...
Click to collapse
When I tap the Recovery Reboot app the "No root detected!" box pops up. Seems like Magisk didn't install when I flashed VS99630c either.
paxvalon said:
When I tap the Recovery Reboot app the "No root detected!" box pops up. Seems like Magisk didn't install when I flashed VS99630c either.
Click to expand...
Click to collapse
Did you flash Magisk before rebooting?
Do you have Magisk Manager app in your app drawer? You can reboot to TWRP Recovery from there. Open Magisk Manager, go to Modules, then three dot Menu.
ChazzMatt said:
Did you flash Magisk before rebooting?
Do you have Magisk Manager app in your app drawer? You can reboot to TWRP Recovery from there. Open Magisk Manager, go to Modules, then three dot Menu.
Click to expand...
Click to collapse
No, I guess Magisk didn’t flash. Downloaded the Magisk Manager app and it says “Magisk is not installed”. Should I click on install? I figure that may be risky because I’m not sure I have TWRP.
paxvalon said:
No, I guess Magisk didn’t flash. Downloaded the Magisk Manager app and it says “Magisk is not installed”. Should I click on install? I figure that may be risky because I’m not sure I have TWRP.
Click to expand...
Click to collapse
At this point in time you need Magisk installed. You can only install in TWRP.
At this point in time, you have two options:
1) try the "hardware button dance" again to see if you can boot to TWRP. If you get to TWRP, flash newest Magisk.
If you can't do that, you will have to:
2) use Dev Patched LGUP via Refurbish mode to flash back to US998 Oreo KDZ, to get back fastboot flash commands. Your bootloader is still unlocked. BEST to flash back to US998 Nougat via Partition DL, Master Reset, then US998 Oreo. Since your Bootloader is already unlocked, you can go to US998 20h after Nougat.
Then, go through WTF Section 6 instructions completely to re-install TWRP and the three root files. Do not skip any steps of that section.
Finally, re-flash VS996 TWRP 30c flashable zip and this time flash Magisk before rebooting.
ChazzMatt said:
At this point in time you need Magisk installed. You can only install in TWRP.
At this point in time, you have two options:
1) try the "hardware button dance" again to see if you can boot to TWRP. If you get to TWRP, flash newest Magisk.
If you can't do that, you will have to:
2) use Dev Patched LGUP via Refurbish mode to flash back to US998 Oreo KDZ, to get back fastboot flash commands. Your bootloader is still unlocked. BEST to b flash back to US998 Nougat via Partition DL, Master Reset, then US998 Oreo. Since your Bootloader is already unlocked, you can go to US998 20h after Nougat.
Then, go through WTF Section 6 instructions completely to re-install TWRP and the three root files. Do not skip any steps of that section.
Finally, re-flash VS996 TWRP 30c flashable zip and this time flash Magisk before rebooting.
Click to expand...
Click to collapse
After failing to boot to TWRP, I've been attempting the LGUP route but no matter what I try it doesn't recognize the device (it says "There is no handset connected"). Here's what I've done exactly:
Deleted old LGUP from Program Files
Followed all the instructions here in the section "HOW TO INSTALL DEV PATCHED LGUP": https://forum.xda-developers.com/lg-v30/development/vs996-lg-v30-vs99630a000704arb00-kdz-t3952254
Didn't work so tried again (different USB ports, used a different computer, reinstalled drivers, reinstalled LGUP, used different cable, even used different Dev Patched LGUP, etc).
LGUP recognizes my device just fine when it's booted normally, but in Download Mode there's no connection
After trying all kinds of stuff for the past few days I was just about ready to throw in the towel. Must have gone through a hundred threads on this forum.. finally I came across someone with a similar problem who fixed it with his Windows 7 PC. Found my old laptop that’s over a decade old and booted it up. Installed the drivers, LGUP, etc. Booted up my phone in Download Mode.. still no connection. Reinserted usb cable.. and the damn thing finally showed up. That ancient behemoth of a computer managed to save my phone
Thanks a bunch for helping me out Chazz
paxvalon said:
After trying all kinds of stuff for the past few days I was just about ready to throw in the towel. Must have gone through a hundred threads on this forum.. finally I came across someone with a similar problem who fixed it with his Windows 7 PC. Found my old laptop that’s over a decade old and booted it up. Installed the drivers, LGUP, etc. Booted up my phone in Download Mode.. still no connection. Reinserted usb cable.. and the damn thing finally showed up. That ancient behemoth of a computer managed to save my phone
Thanks a bunch for helping me out Chazz
Click to expand...
Click to collapse
Same here. Can't access fastboot, and the patched lgup doesn't says "no handset connected."
It's as if bootloader mode and recovery have become the same thing.