Database Develop

[please help me] Android One Update Issues [long]

Hey, sorry if this information is posted elsewhere, I haven't been able to find it with any google or forum searches. I have an Android One moto x4, on google Fi. I've unlocked the bootloader, and rooted the phone (with magisk). Before doing all this (before rooting, after unlocking), I had used TWRP's backup function.
I decided to try to get the 8.1 update [side question: I was only offered OPW28.1; would OPW28.2 have been offered to me without first updating to 28.1?] EDIT: NO. I know that I need to remove root to successfully update the phone, so I used the in-app uninstall function of Magisk, and then rebooted the phone. I tried to run the system update afterwards---and it failed, about halfway through installing. Since this point I cannot get Android to even see there is OPW28.1 , much less OPW28.2. So, I think "That's cool. I have a backup, I'll just restore from that." So, I made another backup, and then tried to restore just the system and system_image (in TWRP---this was probably a mistake). It didn't work---and I don't remember if the phone even booted. EDIT: I think I didn't wait long enough.
So I tried to restore the full backup---and it failed restoring the "bluetooth" partition: it runs out of space (!?)[1]. The phone did not appear to be able to boot after that (it spent a long time at the "Android One" screen, with the color bar oscillating). The good news for me is that I tried a factory reset (all data, I think the option was "user data and customization", the third option), and the phone starts (hooray, no brick). EDIT: TWRP backup does not work. I'll eventually file a bug about this.
Rebooting the phone, it looks totally new (but it remembered my google account name ?? what ??). However, it still isn't letting me update (still isn't seeing the new version is system updates). I tried the dialing "*#*#checkin#*#*" and it says it succeeds, but even after a reboot it doesn't do anything. I cannot find a "google services framework" (or motorola update services) to clear data on in the apps list, but shouldn't that have been reset in both the factory reset and my failed restore attempt anyway? EDIT: Nobody ever got back to me about this.
Sorry for the length of this, I'd really appreciate any input.
[1] adb shell during the TWRP restore session, "tar_extract_file(): failed to extract /bt_firmware//image/crbtfw21.tlv !!!". df /bt_firmware shows 100% use. Why would that even be possible? EDIT: The ext4 partition must have been made with slightly different options that allowed everything to be packed into the tiny partition
EDIT: I downloaded the original Fi firmware from firmware.center /firmware/Motorola/Moto%20X4/Stock/, and flashed the bluetooth partition (after confirming that the the files in that image are bit identical to the backup I made). Bluetooth still doesn't seem to be turning on. Should I just reflash everything? Can I restore my data partition and expect a functional phone? EDIT: I may have flashed to _b instead of _a. In any case I was later able to fix this by flashing the newer firmware quoted below.

SojPapus said:
Hey, sorry if this information is posted elsewhere, I haven't been able to find it with any google or forum searches. I have an Android One moto x4, on google Fi. I've unlocked the bootloader, and rooted the phone (with magisk). Before doing all this (before rooting, after unlocking), I had used TWRP's backup function.
I decided to try to get the 8.1 update [side question: I was only offered OPW28.1; would OPW28.2 have been offered to me without first updating to 28.1?]. I know that I need to remove root to successfully update the phone, so I used the in-app uninstall function of Magisk, and then rebooted the phone. I tried to run the system update afterwards---and it failed, about halfway through installing. Since this point I cannot get Android to even see there is OPW28.1 , much less OPW28.2. So, I think "That's cool. I have a backup, I'll just restore from that." So, I made another backup, and then tried to restore just the system and system_image (in TWRP---this was probably a mistake). It didn't work---and I don't remember if the phone even booted.
So I tried to restore the full backup---and it failed restoring the "bluetooth" partition: it runs out of space (!?)[1]. The phone did not appear to be able to boot after that (it spent a long time at the "Android One" screen, with the color bar oscillating). The good news for me is that I tried a factory reset (all data, I think the option was "user data and customization", the third option), and the phone starts (hooray, no brick).
Rebooting the phone, it looks totally new (but it remembered my google account name ?? what ??). However, it still isn't letting me update (still isn't seeing the new version is system updates). I tried the dialing "*#*#checkin#*#*" and it says it succeeds, but even after a reboot it doesn't do anything. I cannot find a "google services framework" (or motorola update services) to clear data on in the apps list, but shouldn't that have been reset in both the factory reset and my failed restore attempt anyway?
Sorry for the length of this, I'd really appreciate any input.
[1] adb shell during the TWRP restore session, "tar_extract_file(): failed to extract /bt_firmware//image/crbtfw21.tlv !!!". df /bt_firmware shows 100% use. Why would that even be possible?
EDIT: I downloaded the original Fi firmware from firmware.center /firmware/Motorola/Moto%20X4/Stock/, and flashed the bluetooth partition (after confirming that the the files in that image are bit identical to the backup I made). Bluetooth still doesn't seem to be turning on. Should I just reflash everything? Can I restore my data partition and expect a functional phone?
Click to expand...
Click to collapse
Go here: https://androidfilehost.com/?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.

ptn107 said:
Go here: androidfilehost.com /?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.
Click to expand...
Click to collapse
Thank you. Do you happen to know how I can go about checking the cryptographic signatures for these downloads? EDIT: I never managed to do this. I'm considering re-locking my bootloader, which should presumably allow this guarantee to be made. But then I risk bricking the phone. I'm not afraid to go digging around a little bit in the images (I can mount an ext4 filesystem or run simg2img no problem). EDIT: I did go mucking around, and I don't have the public key to go about verifying the bootloader. So that's probably a dead-end.
Also, is resetting user data after every upgrade just SOP when running rooted? Is there some approach to making that less painful that I don't know about? EDIT: NO CLUE. Nobody helped me with this. Also, TWRP doesn't seem to support encryption after the upgrade, so I wasn't able to try restoring from my backup. EDIT ON EDIT: Restoring a TWRP data backup went fine. However, right now TWRP 3.2.1-1 isn't supporting decryption for OPW28.1, so that's another complication. (Just remove the password, and everything seems to work)
EDIT: I've tracked down otacert.zip (containing ota.x509.pem), the key presumably used to sign the OTAs, but the images on firmware.center and androidfilehost don't seem to be signed. Were those signatures stripped out? Is it possible for me to capture those OTA directly (my phone should be receiving these)? My question still stands: how do I force my phone to download the new OTA. I'll deal with flashing it once I can get my hands on it. ANOTHER EDIT: I was able to capture the OTA, but it still isn't installing.
EDIT2: I think I've got a better link.

ptn107 said:
Go here: https://androidfilehost.com/?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.
Click to expand...
Click to collapse
Flash how? From TWRP?

edufur said:
Flash how? From TWRP?
Click to expand...
Click to collapse
from fastboot
TWRP will be removed upon flashing.

ptn107 said:
from fastboot
TWRP will be removed upon flashing.
Click to expand...
Click to collapse
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?

edufur said:
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?
Click to expand...
Click to collapse
This is not an update zip or rom that can be flashed from TWRP. You will have to do the following:
1. Flash this firmware via fastboot which gets you 8.1.0 w/ April update. (Note: you will lose TWRP and root)
2. Boot the new stock 8.1.0 and take the may security update which will be offered almost immediately.
3. Once on 8.1.0 may update you may reinstall TWRP and a root solution. Be aware that if you do then OTAs from here on won't work. So if you want the June update you will have to re-flash stock 8.1.0 and start over.
Flashing stock will automatically remove whatever twrp or root you have.
To flash this firmware:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash logo logo.bin
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear

ptn107 said:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
Is there a reason you are suggesting reflashing the partition table? That would seem to expose a flasher to more risk that needed.
Granted, I'm not able to OTA to OPW28.2. But the android update engine doesn't reflash the partition table, as far as I can tell.
edufur said:
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?
Click to expand...
Click to collapse
Could you let me know if you are able to OTA to OPW28.2 afterwards? I was not able to after reflashing.

SojPapus said:
Is there a reason you are suggesting reflashing the partition table? That would seem to expose a flasher to more risk that needed.
Granted, I'm not able to OTA to OPW28.2. But the android update engine doesn't reflash the partition table, as far as I can tell.
Could you let me know if you are able to OTA to OPW28.2 afterwards? I was not able to after reflashing.
Click to expand...
Click to collapse
Well, now I am afraid to flash since there is a question as to why the partition table was recommended. I almost want to hold out for an official flash to stock tool from motorola.

edufur said:
Well, now I am afraid to flash since there is a question as to why the partition table was recommended. I almost want to hold out for an official flash to stock tool from motorola.
Click to expand...
Click to collapse
I had no problem getting the 28.1 flashable firmware (cited earlier) working on my phone. I would be sure to only flash to the currently disabled slot--and I'd also be sure to backup the data partition before-hand (and move it off-phone). If you're not touching your active slot, there really shouldn't be any way to mess up the phone (just make sure you're able to get into fastboot with both slots first). If something goes wrong, you can just reset the active slot to the old one.
28.1 doesn't have functioning ADB, so you might also consider setting up Termux and an ssh server on the phone so you can still get a command line on it if needed.

Nokia 4.2 Bricked, but can still enter FastBoot

Hello everyone :laugh:!
Tried rooting the Nokia 4.2, did not know which img to use exactly so I tried one from some other shady site and messed up. Luckily, the recovery partition was still working. After trying to boot lots of images, I got tired and accidentally even flashed a Nokia 6.2 TWRP image to my recovery partition. Then I completely messed up. The phone only gets into fastboot now. May I please ask some help of you? I've been trying for days to fix things. I just wanted to root the original firmware. Now when I try to flash TWRP, it even says that the 'recovery' partition has no partition table! I can still write to boot_a and boot_b though. The phone originally had the October patch level, but before bricking it I upgraded it to the December level.
Kind regards,
Alexander47u

Search on google and try do download and flash the stock firmware (unrooted)

Phone does not get detected by QFIL
thegamingcat13 said:
Search on google and try do download and flash the stock firmware (unrooted)
Click to expand...
Click to collapse
I have tried this using QFIL, however the phone is not detected. The phone also goes into fastboot as soon as the cable is plugged in, even when the phone is off.
Have also installed appropiate drivers for QFIL, but no luck.

Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot

Works, Thank you!
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Thank you! This worked flawlessly.

#metoo
Haha, I have done the EXACT same thing as you. Now I can only enter fastboot mode and when I try to flash anything I have downloaded I get an error about missing partitions. I have looked everywhere for details on the partition sizes, mount points and so on but nobody has uploaded the information. In the end I went and purchased a second device in order to dump the entire stock ROM in order to fix the first phone. I've got the second phone running in ADB-mode but I can only backup to an .ab file so now I am back at square one. All of the guides I can find on how to dump the ROM involves flashing TWRP recovery but THERE IS NONE FOR THE 4.2 :crying: And after researching Android forensics I have found a guide to dumping the ROM but it needs root access in the phone shell. All I wanted was root (and LineageOS). Does anyone feel like patching the stock ROM and making a zip-file containing the img-files from all of the partitions?

Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.

alexander47u said:
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
Click to expand...
Click to collapse
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!

You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.

alexander47u said:
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
Click to expand...
Click to collapse
I was able to succesfully patch boot.img with magisk, then I copied the patched boot image to my computer with linux. Fastboot flash boot boot.img worked but upon reboot I got an error message saying "corrupt data" and offered to do a factory reset. Any chance you can upload your patched boot image so I can use yours?

Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129

Posted

alexander47u said:
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Click to expand...
Click to collapse
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?

Oslokalle said:
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Click to expand...
Click to collapse
Up to March. I used the stock rom that is floating around on the internet. Not sure if I am allowed to post stock roms.
I was able to update to April using Magisk but not any further than that.

thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Tried this using a user_update.zip file from www[.]getdroidtips[.]com/stock-rom-nokia-4-2-firmware/. My phone boots again, but Wi-Fi doesn't work. My model # is TA-1133. What should I do?
Edit: tried to install the latest security OTA from t[.]me/nokiarepoen/379, V2.29C, but I get
Code:
E:Package is for source build 00WW_2_29B but expected 00WW_1_17I
. Is there a base user_update for build 00WW_2_29B floating around?

Oslokalle said:
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
Click to expand...
Click to collapse
Kindly provide me that zip too.

Stuck on G logo after root.

I just received my direct from Google Pixel 4 XL running the June 2020 update and proceeded to root it using the instructions found here https://www.xda-developers.com/google-pixel-4-root-magisk/ after flashing the patched boot.img and rebooting the phone doesn't boot past the G logo; the status bar just loops indefinitely. Is there something I'm missing? Any help would be much appreciated.
I have no modules loaded, no custom kernel or ROM.

Go to recovery and reset the phone,
And reboot the phone in each steps

The guide looks mostly like what I do every month, though I haven't done June yet.
I don't think this will solve your issue, but usually I flash the patched boot image to both slots as Magisk in-place updates seem to fail if I don't...
Code:
fastboot flash boot magisk_patched.img --slot=all
I assume you didn't have any obvious issues with the guide steps aside from not booting after Step 5?
Make sure your platform tools are the newest you can get. Also make sure that you didn't get the Telstra variant of the June update.
If all else fails, try to revert by dirty flashing the (correct) June 2020 stock ROM. You'll only lose root if you do it correctly. (you don't have working root anyways)
Take the giant ZIP file you downloaded to get the boot image, merge it with platform tools and edit the flash-all.bat file... near the bottom, remove the "-w " from the command so it reads
Code:
fastboot update image-coral-qq3a.200605.001.zip
Save the changes and run the .bat file after booting the phone to fastboot and making sure its visible to platform tools.

jljtgr said:
The guide looks mostly like what I do every month, though I haven't done June yet.
I don't think this will solve your issue, but usually I flash the patched boot image to both slots as Magisk in-place updates seem to fail if I don't...
Code:
fastboot flash boot magisk_patched.img --slot=all
I assume you didn't have any obvious issues with the guide steps aside from not booting after Step 5?
Make sure your platform tools are the newest you can get. Also make sure that you didn't get the Telstra variant of the June update.
If all else fails, try to revert by dirty flashing the (correct) June 2020 stock ROM. You'll only lose root if you do it correctly. (you don't have working root anyways)
Take the giant ZIP file you downloaded to get the boot image, merge it with platform tools and edit the flash-all.bat file... near the bottom, remove the "-w " from the command so it reads
Code:
fastboot update image-coral-qq3a.200605.001.zip
Save the changes and run the .bat file after booting the phone to fastboot and making sure its visible to platform tools.
Click to expand...
Click to collapse
Your first suggestion results in the phone booting, but ending up on a black screen with only the power menu
dirty flashing results in a successful unrooted boot, but rooting seems to not be possible for some users including myself. No clue why

Try flashing the patched boot to both boots but don't use the all slots command, do them one at a time, A, then B. See if that gets it.

So I am a fool.
I didn't run these commands using the latest "platform-tools"
but I will remember this instructions if I have issues in the future!

I am on latest platform tools and have tried all options presented and still get black screen with adb access and power menu. Other thoughts?

I just downloaded the full image and was getting ready to patch the boot image and flash it on my 2 day old Pixel 4xl. Maybe I will wait unless others have had success with this. I am on the June update. I made sure I didn't download the Telstra version.
Is there any reason to not just use the "Download Zip" option in Magisk? That always worked fine for me on my last phone.
Thanks, Chris
---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------
I took the plunge and it booted just fine. I am on a G020J if that help. Hardware MP1.0.
I did not realize that TWRP was not available for the Pixel 4xl yet. What is everyone using for a custom recovery?

reedc83 said:
I just downloaded the full image and was getting ready to patch the boot image and flash it on my 2 day old Pixel 4xl. Maybe I will wait unless others have had success with this. I am on the June update. I made sure I didn't download the Telstra version.
Is there any reason to not just use the "Download Zip" option in Magisk? That always worked fine for me on my last phone.
Thanks, Chris
---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------
I took the plunge and it booted just fine. I am on a G020J if that help. Hardware MP1.0.
I did not realize that TWRP was not available for the Pixel 4xl yet. What is everyone using for a custom recovery?
Click to expand...
Click to collapse
I feel like the options inside Magisk are for phones that are already rooted to update Magisk. I guess what your edit is saying is that you used to use TWRP with the ZIP?
Anyways, there are no custom recoveries for the same reason there is not TWRP. The partition scheme for Pixel phones that come with Android 10 pre-installed is too different for TWRP to live on it. I don't know enough about this subject, but I thought I read there was no separate recovery partition that could be made custom.

Everyone has been doing it all along, when people have issues it's usually the wrong boot image, wrong complete image, flashed boot image to wrong slot, used the factory cable (yes, it's a thing, don't use it or flashing), don't have the correct and/or latest tools. There was an issue with windows 8.1 and flashing, I don't remember what that was but those of you flashing and still on 8.1 you'll want to do a search for that.
@Brakiss, you may want to try the whole smash if all else has failed... THIS WILL DELETE YOUR DATA!
Start by going over to Goog ---> https://developers.google.com/android/images and getting the full factory image and the latest tools; even if you already did it do it again being careful to verify you have the correct image. While you're grabbing goods get the Magisk APK so you can install it after the image is flashed. For the flashing portion please follow the directions on that page to the letter. Do not use the factory cable; use an A to C. Before you flash run these commands one at a time
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
After flashing get the boot image directly from the factory image you downloaded and not any other source and move it over to your phone along with the Magsik APK. Install magisk manager and then use it patch the boot image. You'll take that over to your PC and flash it as usual but do it to both slots and do them separately, do not use the all slots.

jljtgr said:
I feel like the options inside Magisk are for phones that are already rooted to update Magisk. I guess what your edit is saying is that you used to use TWRP with the ZIP?
Anyways, there are no custom recoveries for the same reason there is not TWRP. The partition scheme for Pixel phones that come with Android 10 pre-installed is too different for TWRP to live on it. I don't know enough about this subject, but I thought I read there was no separate recovery partition that could be made custom.
Click to expand...
Click to collapse
Correct, there is no recovery partition anymore. That has been a thing for a while now and not specific to the Pixel. My Moto x4 that I used prior to the Pixel 4xl had the recovery in the boot image but there was still TWRP for it. Whenever rooting that phone you have to boot a custom recovery image then from in there flash the separate custom recovery image/zip installer. It would modify the recovery that is embedded into the boot image.
I really hope that devs smarter than myself will figure it out and make a way to get TWRP on there.

On Android 11 Beta 2.5, I patch the original boot image, I then send it via fastboot, I tried flashing all partitions, manually _a and _b and stuck on Google logo ... When I put back the original boot.img, everything works properly. Miss my root but haven't seen any help on this :| Worked until I switched to 11 Beta ...

I have the problem too
Just as Chronos300 reported, I got stuck on the G logo. Some of my problem may be self-inflicted since I was not careful enough in following the directions: evidently it's important to finish the process for unlocking the bootloader before going to fastboot again to flash the Magisk boot image. I got stuck on the G logo but thought that I would have my way out by flashing the July factory image.
Most of that process worked out: things were good until the end when I saw a lot of messages about files that aren't present in image-coral-qq3a.200805.001.zip like boot.sig or recovery.img. I guess these are optional: the *.sig files may be intended to contain a checksum or hash and the recovery.img may just have gone away with the recovery partitions. Finally was an error that was fatal:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Click to expand...
Click to collapse
That's awful cheery. I see that the difference between flash-all.sh and flash-base.sh is that the former has the "fastboot -w update" that Shayded talks about. I tried running the update command as Shaded recommends, without the -w switch. This time it got farther, but this time the final message was "failed to extract 'product.img': I/O error"
Sure enough, image-coral-qq3a.200805.001.zip contains no product.img file. Is this my problem, or is the solution somewhere else? Would an older factory image have the missing file?

Sigh of relief
My phone's back in the land of the living. I had noticed the links on the factory-image page for the flash tool. Thinking that maybe these were better maintained, I thought to try out the August update for coral.
The flash tool downloaded whatever big image it grabs and then started into the installation. After a few minutes the fastbootd screen came up and the progress bar went to about 80%--and then everything hung. Hoping on hope, I decided I could leave it like this all night if I had to.
It might have taken half an hour, but it did finally come up with the screen saying everything had updated. Sure enough, it made it through the boot and came up to the setup screens.
Enabled developer mode, saw that the bootloader was indeed unlocked, and went about setting some settings. Haven't tried root yet, but it's sure great to be back in business!

epic_task said:
{...}
Sure enough, image-coral-qq3a.200805.001.zip contains no product.img file. Is this my problem, or is the solution somewhere else? Would an older factory image have the missing file?
Click to expand...
Click to collapse
Personally, I don't understand how you ended up without product.img... it's literally half of the internal ZIP file. (you're not supposed to extract this ZIP, anyways)

jljtgr said:
Personally, I don't understand how you ended up without product.img... it's literally half of the internal ZIP file. (you're not supposed to extract this ZIP, anyways)
Click to expand...
Click to collapse
No, I never altered that zip file and was not trying to extract individual files from it when making that final run of fastboot update.
What I can tell you is that I was sleepy by the time I was doing that. There were two things I missed noting at the time but see this morning: product.img is indeed in the internal zip file and a message a couple of lines above the final error message (I had left the terminal window open):
extracting product.img (2102 MB) to disk...ziparchive W 08-18 00:00:43 31524 31524 Zip: unable to allocate 2204832024 bytes at offset 0: No space left on device
Click to expand...
Click to collapse
I would think that my failing to wait for a complete boot with an unlocked bootloader before attempting to flash magisk_patched.img did something unfortunate to the partitioning scheme. Evidently the web-based flash tool cleared it up.

Maybe I'm suggesting the obvious... but do you have 2-4GB available on every drive? It's complaining there's no available space. Typically product.img is split into 500MB parts and sent separately... so you'd need at least 2x the space available for the parts.

The flash-all is generic and looks for some files which are not used by these phones. This failure described is usually the wrong cord, you must use a USB A to USB C rather than a C to C. If not that it's going to be a tools/driver issue. There are a number of guides which can show how to find and delete old drivers and reinstall new drivers. Removing the W gets rid of the wipe but doesn't otherwise affect the flashing and will have nothing to do with it's success or failure; you are in effect dirty flashing when you remove it from the flash-all.

Restoring OTA for stock

Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.

pastorbob62 said:
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
Click to expand...
Click to collapse
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA

KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
Thanks KtownJeff, that does sound much easier. Why aren't others posting this much simpler solution? Has anyone else tried this?
I haven't tried it yet as it looks like they may be about to figure out the low call volume issue in custom ROMs and then these OTA updates won't be necessary anyway? I'll wait and see what happens over the next week or so.
I'm wondering why it's necessary to wipe the data though. Why isn't uninstalling Magisk and booting with the original kernel enough?

JerseyChewi said:
Yeah the calling issue is just a lineage thing...and lineage is so generically lame. mokee or corvusos are my favs. Most of the custom Roms work well.... and there is a lot more ROMS for our device that is not on XDA.... The Data may be fine Just back it up first....and I put this on telegram and if you haven't checked it out there is five channels for our phone with tons of stuff.....more ROM builds We also have Pitch Black Recovery now available which is twrp with a cleaner UI and lots more options
Click to expand...
Click to collapse

KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
WHHAAAT?? I got a few questions...
Why is it important not to have the copy-partitions.zip installed?
Why you should be on slot _a?
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.

WoKoschekk said:
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Click to expand...
Click to collapse
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
WoKoschekk said:
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
Click to expand...
Click to collapse
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.

JerseyChewi said:
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
Click to expand...
Click to collapse
Assuming this is not your first time flashing the firmware and you already have a flash script/.bat file:
1. run the script
Done! One command and 5 min later you are on the latest firmware.
JerseyChewi said:
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
Click to expand...
Click to collapse
Motorola provides you OEM signed images and a .xml sheet with proper commands to flash them as a .zip file. I've never heard that someone bricked his device by using the manufacturer's recommended way. I think it's risky to use your own workaround just because you're nervous about it.
Even if you unplug the device in the middle of the flashing process you won't face any trouble. Every single flashing command loads the image into your device's RAM before it gets written to the device.
fastboot oem fb_mode_set = no matter what reboot command you run your device boots into bootloader
Why are you nervous about it?

Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary.... so that way when OTA comes it will move to the B partition the way that it was intended to.....but the boot-loader is unlocked now both slots start with a boot-loader, bootloader_a and bootloader_b.. .and the on board preboot chip will trip the first flag that communicates with stock flashed boot image which also holds the recovery and the kernel... even if its backed up stock.img with magisk, it will break the next flag on the device along with the custom logo.bin.... now the custom logo if it is cloned with a moto signature official it wont matter and the only one Im aware is logo.bin for the TMOBILE REVVLY variant.... when you boot not flash the stock boot.img it bypasses the security chain until reboot.... I've flashed b slot on accident and then booted several GSI and other lake Roms and at some point ill notice on the bootloader screen that maybe i have April 2020 when Im running July 2020 version....which is headache to fix and i booted to b slot flash stock as normal let boot to the setup wizard then reverse to a and do it again because it brings it back together... now the mapping for the AB partition with duel slots t is standard for all ARM64 AB devices Bootloader a and b Boot a and b Radio a and b which is (firmeware) slot Vendor a and b System a and b....
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
the reason why I wrote it the way that I did was because I tried everything to OTA back and this was the only way it worked for me.... and trust me I stayed up for weeks trying to break it or fix it....I finally I came across a moto g6 thread where some one relocked there bootloader and didnt have the oem unlock set and they couldnt do anything to unlock it again using fastboot because the switch was grey out on developer options which means they couldnt root to fix..., I believe it was Sd_shadow that recommended trying to boot the boot.img like how we boot the twrp.img because it bypasses the security flag... well my first attempt it didn't work which led me to the mismatched boot-loaders and I kept at it and by process of elimination and fully learning the way these partitions communicate..... which is totally backwards from the way it used to be... If u leave data then flash back stock, the boot-loader thinks its fresh but finds its not......so boot-loop... tried it cussed and tried again and screamed but now its automatic. for me because of trial and error... I've been at this a few years now and I'm learning something new all the time and most of time when people don't post is because they either don't know or don't wanna give wrong info or maybe nobody showed them. There kinda is an unwritten bylaw at XDA (tough love)... you gotta learn by experience that way when get an opportunity to help or find a new way it makes it worth the stress
That is why I wrote it the way I did step by step in the easiest way possible because of my experiences and headaches...If it don't work you didn't follow directions.... Now I'm gonna tell you I re-locked my bootloader too and was not able to flash back ota don't even try its a waste of time because the only way to get that flag back is to re ball a chipset, or replace the motherboard, or buy a new phone....
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing

KtownJeff said:
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary....
Click to expand...
Click to collapse
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
BTW: You can call me what you want but that doesn't make your statements right either.

WoKoschekk said:
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
Click to expand...
Click to collapse

KtownJeff said:
Yes correct it easier to flash rom after it is available for download with a month behind....
Click to expand...
Click to collapse
You should check your sources.

KtownJeff said:
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
Click to expand...
Click to collapse
I also want to leave my device in oem_locked state and not in flashing_locked

Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.

pastorbob62 said:
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
Click to expand...
Click to collapse
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!

WoKoschekk said:
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Click to expand...
Click to collapse
I'm thinking not, since this was the first thing I tried when I got the notification for the update. And the update still failed.
WoKoschekk said:
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
Click to expand...
Click to collapse
Telegram didn't have it when I installed the update. LMSA kept giving me a "Decompression failed" error message. So I just reinstalled the stock version I was already on and allowed the update to complete. Then reinstalled TWRP and Magisk without any issues once I had all of my apps and data restored.
Not taking any offense here, but I am not a noob and while I didn't give all of the details to what I had tried I also didn't want to reinvent the wheel. I didn't think about eliminating the line "erase userdata". Since it was very simple with previous devices to do it I knew there had to be an easier way. By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/

pastorbob62 said:
Telegram didn't have it when I installed the update.
...
By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
Click to expand...
Click to collapse
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker

WoKoschekk said:
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
Click to expand...
Click to collapse
That's nice. But the one for my phone was not available on tracker until the day after I updated via OTA.

KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
Click to expand...
Click to collapse
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks

[email protected] said:
I tried this to go back to stock rom from LOS17.
I've never seen that error before have you tried google search for the error?
Click to expand...
Click to collapse

[email protected] said:
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
Click to expand...
Click to collapse
Don't know what your error means, but flash the stock ROM and it should be fine.

Need help with TWRP patching - V409N

Hello everyone.
My phone is currently on V409N30f_00_LGU_KR_OP_0126.kdz, i was successful in unlocking it via 9008 method, and just a moment ago i was also successful in patching it with magisk (thanks to great guide here: https://forum.xda-developers.com/t/root-eu-lmv405ebw-magisk.3912959/ ). I had some problems, mainly i didn't know that you actually need proper abl_a/abl_b to boot the OS (i thought it's not a part of boot process, unless you push some buttons, but that doesn't seem to be the case). My final problem is that i can't seem to be able to get a proper permanent fastboot installed, and by proxy i can't get TWRP as well. Therefore i have couple of questions here:
1. How to get proper fastboot on an encrypted phone with android Q? Do i have to get rid of the encryption? How?
2. From what I understand, the boot partition needs to be patched to include TWRP, similar to how magisk was prepared - is there guide how to do that?
3. Why the phone fails to boot if i try to sideload/fastboot to TWRP image provided on this forum?
Thanks in advance for all your support

Scorcerer said:
Hello everyone.
My phone is currently on V409N30f_00_LGU_KR_OP_0126.kdz, i was successful in unlocking it via 9008 method, and just a moment ago i was also successful in patching it with magisk (thanks to great guide here: https://forum.xda-developers.com/t/root-eu-lmv405ebw-magisk.3912959/ ). I had some problems, mainly i didn't know that you actually need proper abl_a/abl_b to boot the OS (i thought it's not a part of boot process, unless you push some buttons, but that doesn't seem to be the case). My final problem is that i can't seem to be able to get a proper permanent fastboot installed, and by proxy i can't get TWRP as well. Therefore i have couple of questions here:
1. How to get proper fastboot on an encrypted phone with android Q? Do i have to get rid of the encryption? How?
2. From what I understand, the boot partition needs to be patched to include TWRP, similar to how magisk was prepared - is there guide how to do that?
3. Why the phone fails to boot if i try to sideload/fastboot to TWRP image provided on this forum?
Thanks in advance for all your support
Click to expand...
Click to collapse
Follow this link for the 30f boot_a with twrp injected.
Let me try to clarify a bit; The engineering v35 abl is Oreo. So if you have it installed, the phone won't boot, unless your OS is Oreo (which it isn't).
So the purpose of having that abl isn't to boot the phone, it's only to be used for things like 'fastboot oem unlock' or 'fastboot flash abl_a abl_original_a.img'
it's not to boot the phone. And yes, absolutely it's a part of the boot process abl stands for 'android boot loader'.
So to make use of that v35 eng abl (after you've unlocked the boot loader), would be to flash it to the inactive slot on the phone (most people that would be abl_b). That way, you can use twrp to switch slots, use fastboot, then switch back to the active slot.
To use that proved boot_twrp_a.img, you need to 1st, save your original boot partition, just in case. Then flash it (using qfil) to boot_a (assuming that's your active slot). Then, don't boot the device, go directly to recovery. Once in twrp, format data. Then reboot recovery. Then flash magisk and dm_verity.
then u should be all set.
cheers

AsItLies said:
Follow this link for the 30f boot_a with twrp injected.
Let me try to clarify a bit; The engineering v35 abl is Oreo. So if you have it installed, the phone won't boot, unless your OS is Oreo (which it isn't).
So the purpose of having that abl isn't to boot the phone, it's only to be used for things like 'fastboot oem unlock' or 'fastboot flash abl_a abl_original_a.img'
it's not to boot the phone. And yes, absolutely it's a part of the boot process abl stands for 'android boot loader'.
So to make use of that v35 eng abl (after you've unlocked the boot loader), would be to flash it to the inactive slot on the phone (most people that would be abl_b). That way, you can use twrp to switch slots, use fastboot, then switch back to the active slot.
To use that proved boot_twrp_a.img, you need to 1st, save your original boot partition, just in case. Then flash it (using qfil) to boot_a (assuming that's your active slot). Then, don't boot the device, go directly to recovery. Once in twrp, format data. Then reboot recovery. Then flash magisk and dm_verity.
then u should be all set.
cheers
Click to expand...
Click to collapse
Thanks for the TWRP image, i'm gonna flash it after weekend, when i'll have acces to the phone and will report back
One more question here though, are fastboot flashable files also flashable via qfil ?

Scorcerer said:
Thanks for the TWRP image, i'm gonna flash it after weekend, when i'll have acces to the phone and will report back
One more question here though, are fastboot flashable files also flashable via qfil ?
Click to expand...
Click to collapse
Yes, absolutely. With qfil you can pretty much flash anything to any partition. That's why it's wise to be very very cautious, you could flash the wrong image to a partition, it won't stop you, and it could be too big of an image for that partition but qfil will keep writing it and write over the neighboring partition(s)!

Alright,
I went in and flashed v35 eng abl via qfill into abl_a. That gave me fasboot, which i used to do:
fastboot flash boot_b boot-twrp-30f_a.img (the twrp image i've got from you)
and
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
Then, i switched over to b slot, and rebooted straight to recovery.
In TWRP, i wiped data with formatting it, rebooted to recovery again (didn't got asked for password, i think that's a good thing), then installed magisk.zip via sideload (didn't have it on sd card) and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip afterwards.
I still have 2 problems though:
1. I can't mount vendor - in the log i'm getting "Failed to mount /vendor" (unknown error 150)
2. If i try to boot to system it loops over, i have to wait till it switches over to a slot, which gives me fastboot back, which i'm using to boot to recovery on slot B.
Should i just YOLO it and try to install Lineage directly from here (as i have TWRP)? That's my end goal...
EDIT:
I just noticed by DDing off the vendor_a it's reeeeeally different form vendor_b, and i'm considering copying stuff over, especially since i already did KDZ couple of times, so i'm not afraid of starting over.
EDIT: this let me mount /vendor finally, but boot to OS still loops.

Scorcerer said:
Alright,
I went in and flashed v35 eng abl via qfill into abl_a. That gave me fasboot, which i used to do:
fastboot flash boot_b boot-twrp-30f_a.img (the twrp image i've got from you)
and
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
Then, i switched over to b slot, and rebooted straight to recovery.
In TWRP, i wiped data with formatting it, rebooted to recovery again (didn't got asked for password, i think that's a good thing), then installed magisk.zip via sideload (didn't have it on sd card) and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip afterwards.
I still have 2 problems though:
1. I can't mount vendor - in the log i'm getting "Failed to mount /vendor" (unknown error 150)
2. If i try to boot to system it loops over, i have to wait till it switches over to a slot, which gives me fastboot back, which i'm using to boot to recovery on slot B.
Should i just YOLO it and try to install Lineage directly from here (as i have TWRP)? That's my end goal...
EDIT:
I just noticed by DDing off the vendor_a it's reeeeeally different form vendor_b, and i'm considering copying stuff over, especially since i already did KDZ couple of times, so i'm not afraid of starting over.
EDIT: this let me mount /vendor finally, but boot to OS still loops.
Click to expand...
Click to collapse
First thing I see is that you flashed, assuming what you typed above is exactly what you did, vbmeta wrong.
it should be fastboot --disa... --disa... flash vbmeta_b vbmeta_blank.img
The 1st parameter, after 'flash' should be the partition you want to flash to. Then, after that, the image you want to flash to it.
2nd, just ignore the 'can't mount vendor' in the output of when you zip install magisk or dm_verity, it's irrelevant.
So why is it bootlooping when trying to get to system? Possibly the incorrect vbmeta command? Or maybe you didn't format data? (for format, you have to type in 'yes'). Possibly it's not the right image for the os? It is, beyond doubt, 30f that you flashed?
cheers

AsItLies said:
First thing I see is that you flashed, assuming what you typed above is exactly what you did, vbmeta wrong.
it should be fastboot --disa... --disa... flash vbmeta_b vbmeta_blank.img
The 1st parameter, after 'flash' should be the partition you want to flash to. Then, after that, the image you want to flash to it.
Click to expand...
Click to collapse
But that's what i did - i didn't change the command in my command and i copy-pasted it straight from command line and it says vbmeta_b everywhere...
AsItLies said:
2nd, just ignore the 'can't mount vendor' in the output of when you zip install magisk or dm_verity, it's irrelevant.
So why is it bootlooping when trying to get to system? Possibly the incorrect vbmeta command? Or maybe you didn't format data? (for format, you have to type in 'yes'). Possibly it's not the right image for the os? It is, beyond doubt, 30f that you flashed?
cheers
Click to expand...
Click to collapse
Yup, i didn't change name of the boot image you provided so i won't make any mistake here. Also, i noticed that after i restored from KDZ it forced me to grant access to internet and downloaded some kind of patches - can it be that those affected the booting sequence somehow and i should just take clean dump of abl_b for example so that it can be patched properly?
Oh, just now it occured to me, i can basically take two dumps, one after kdz restore and the other after booting it, then compare them with md5 and i'll know if it actually does something to them...
EDIT: one more question, is KDZ restoring both slots properly? or only the currently active one?

Scorcerer said:
But that's what i did - i didn't change the command in my command and i copy-pasted it straight from command line and it says vbmeta_b everywhere...
Yup, i didn't change name of the boot image you provided so i won't make any mistake here. Also, i noticed that after i restored from KDZ it forced me to grant access to internet and downloaded some kind of patches - can it be that those affected the booting sequence somehow and i should just take clean dump of abl_b for example so that it can be patched properly?
Oh, just now it occured to me, i can basically take two dumps, one after kdz restore and the other after booting it, then compare them with md5 and i'll know if it actually does something to them...
EDIT: one more question, is KDZ restoring both slots properly? or only the currently active one?
Click to expand...
Click to collapse
hmmmm, confusing. So u speak of clean dump abl_b so it can be patched... but we never patch abl (a or b).
and no, the 'downloaded some kind of patches' are just updates to their specific apps, it's not making any change to 'system'.
when using lgup, you should first use Part D/L and choose all partitions (you can clearly see it's doing both a & b by the list). Also, if doing a 'refurbish', it should be updating both slots. Only 'upgrade' would do one side and then switch to that side.
cheers

Okay, so, step-by step, i'll try it once again and will also be taking notes meanwhile
First, i restored from KDZ by refurbishing V409N30f_00_LGU_KR_OP_0126.kdz to be exact.
Just now i flashed eng35 into abl_a which got me into fastboot no problem - the fastboot screens says SECURE BOOT is "yes" and DEVICE STATE "unlocked" which seems okay i guess...
Flashing the TWRP image you provided with
fastboot flash boot_b boot-twrp-30f_a.img
I intend to leave abl_a with fastboot for the future and so i plan to boot from b side
Now the vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
went in just fine.
Reboothing to recovery - set the b slot to be active:
fastboot set_active b
rebooting form the phone buttons directly into recovery...Got TWRP 3.3.1-0 - asks for password, i have to cancel it obviously. Swiping to allow modifications and going directly to Wipe->Format Data->yes - works and done, but complains about /vendor and /data/media/TWRP/.twrps.
Going back a bit and rebooting TWRP to recovery again - This time it doesn't ask me for password so i think i got rid of the encryption.
Flashing Magisk-v22-0.zip from their webpage, i'm clicking on add more zips and adding Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip as well, clicking on reboot system aaaaand bootloop

Okay good, making progress for sure.when I get back to my computer I'll post a link to the magisk and DM verity I use that I know will work. Not positive that those are the problem, but everything else seems to be exactly what you should be doing.

Scorcerer said:
Okay, so, step-by step, i'll try it once again and will also be taking notes meanwhile
First, i restored from KDZ by refurbishing V409N30f_00_LGU_KR_OP_0126.kdz to be exact.
Just now i flashed eng35 into abl_a which got me into fastboot no problem - the fastboot screens says SECURE BOOT is "yes" and DEVICE STATE "unlocked" which seems okay i guess...
Flashing the TWRP image you provided with
fastboot flash boot_b boot-twrp-30f_a.img
I intend to leave abl_a with fastboot for the future and so i plan to boot from b side
Now the vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta_b blank_vbmeta.img
went in just fine.
Reboothing to recovery - set the b slot to be active:
fastboot set_active b
rebooting form the phone buttons directly into recovery...Got TWRP 3.3.1-0 - asks for password, i have to cancel it obviously. Swiping to allow modifications and going directly to Wipe->Format Data->yes - works and done, but complains about /vendor and /data/media/TWRP/.twrps.
Going back a bit and rebooting TWRP to recovery again - This time it doesn't ask me for password so i think i got rid of the encryption.
Flashing Magisk-v22-0.zip from their webpage, i'm clicking on add more zips and adding Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip as well, clicking on reboot system aaaaand bootloop
Click to expand...
Click to collapse
check this folder for the version of Magiisk I know works. Don't remember why, but have read the latest version of Magisk is a problem somehow. Pretty sure if you follow the steps as u did above, with this magisk, it will work.
cheers

Hiho, thanks for sticking with me.
I did everything the same except for using the Magisk you provided, and when i finally got to it, it bootlooped all the same
I tried to flash stuff in different order and stuff, but accomplished nothing.
And then I remembered i read somewhere that the OTA only does update one slot at a time, so i thought maybe Refurbish behaves the same and flashes the other slot (in my case it'd be A since i'm trying TWRP and stuff on B)
I started comparing partitions, and almost all of them were the same, except:
515cddf67500d0be189f6fc386bad7c7 /dev/block/by-name/OP_a
7fe5ca2a051d6dbb9ef191fbee0af98c /dev/block/by-name/OP_b
a4b4bbed1d0a0aa668d76558a9d10fb4 /dev/block/by-name/abl_a
4c47ecd7254de2dd84f88dbc3e31ccc2 /dev/block/by-name/abl_b
65c4413067309174d839b98b3c7eff0e /dev/block/by-name/laf_a
e7e47f8e1e05f21cf06c638bf537be67 /dev/block/by-name/laf_b
c62e2c813eeaba8682bb7dd5e26ffa8b /dev/block/by-name/oem_a
65b0e730e47fd0017c11852917ef1d2b /dev/block/by-name/oem_b
dd90de59c1b08c949326d1625a8e4d55 /dev/block/by-name/system_a
d192b99fd2cc8a48dd3f106d9f0f8233 /dev/block/by-name/system_b
Obviously abl_a is different since i installed v35 eng to it, but the rest should be the same, right?
Since they're not, can i just dd from a to be and be done with it? A slot always booted fine, but since I'm installing eng into it I never tried to do twrp and stuff there...

Aaaand it works
So the trick was just to make sure that the proper OS is actually here, and then, well, everything works like a charm i guess I used newer magisk, and so far everything looks okay
Now i'm gonna put in Lineage, but this should be easy
This also means that Refubish doesn't flash everything as we thought it's supposed to be

Scorcerer said:
Aaaand it works
So the trick was just to make sure that the proper OS is actually here, and then, well, everything works like a charm i guess I used newer magisk, and so far everything looks okay
Now i'm gonna put in Lineage, but this should be easy
This also means that Refubish doesn't flash everything as we thought it's supposed to be
Click to expand...
Click to collapse
yeah the only one I trust to flash everything would be part D/L. When doing it, you select ea individual partition, and they are all listed, both a and b slots.
The purpose of the 'dual' slots (and no recovery partition any longer) is to update 1 slot at a time, while the other slot is the older OS version. That's the way OTA's are suppose to happen. But if you use LGUP and do a Part D/L, then both sides have the same OS.
it's confusing. Good u got it working!
cheers

Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.

sptw said:
Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.
Click to expand...
Click to collapse
If you want to stay on Pie, your situation is easier, you can just follow the guide to unlock and then use fastboot to boot twrp, use 'ramdisk inject' to inject the twrp image. Reboot to recovery, format data, reboot recovery again, flash magisk and dm_verity.
cheers

sptw said:
Hi AsltLies,
I could see that you sent a 30f boot_a image with TWRP injected on it for Scorcerer. I'm on identical situation. Only difference that i want to stay on Pie. Probably i cant use that file as i'm on Pie.
Could you point me please how do i get to inject TWRP on a boot_a pie firmware. My devide and situation is identical as for Mr. Scorcerer. V409N, korea version.
I would like to try this guide here as it seems very confiable
Thanks in advance.
Click to expand...
Click to collapse
Didn't realize it was available, but follow for the 20n boot+magisk boot image. This Link
I'd suggest using qfil to (first backup your original boot partition) to flash this to your active boot partition. Then exit edl mode and use the key combo to go directly to recovery (now twrp). Format data, then reboot recovery, then flash magisk and dm_verity. All set!
cheers

Hi AsltLies,
Thanks for both of informations. Let me try to explain a bit more. I am able to root the device with magisk. I made a boot_a patched using magisk apk and inject diretly into boot_a using qfill. It works like a charm. No problem at all.
The problem is that there are something wrong with viper4android using magisk. I want the older 2.3.4 driver and it has a kind of problem using convolver and system inject. User app method does not work.
I own a LG V20 with viper4android on it, and i can confirm that there are something wrong with viper on LG V40. My LG V20 is not a Bang & Olufsen and not even Merodian tune. Maybe the problem lies on this meridian audio tuned on LG V40. Chances are great about that. Devices sound differents and i have to accept this. But...
I would like to try the method that i used to root the LGV20 : Supersu and not magisk. I dont care about safety net. I dont use it. And a second problem with magisk : two apk refuse to open with magisk root method. I know they work with rooted devices but using rootcloack on xposed and xposed is very hard to get to work on magisk ( very limited )
So, i would like to use SuperSu method and not magisk to inject the old 2.3.4 viper4android directly on TWRP. I know how i can do it to works using the original drive and apk from the original devs. ( I dont like the new version 2.7 )
So, sorry for the long explanation, but do you know how i can install TWRP without to use magisk? ( That [TWRP] LG V40 / Judypn does not work. I only get bootloop ).
Thanks again.
In time: Maybe i'm doing something wrong to install TWRP. Do i need to instal it in both slots ( a and b? Do i need to access TWRP using the slot that is not active and make the zips install from there and not from the active slot? It's a kind of confusion for me. I already read a lot about it, but i'm still in doubt how it really works. I'm not interested to use another ROM, just stock.

sptw said:
Hi AsltLies,
Thanks for both of informations. Let me try to explain a bit more. I am able to root the device with magisk. I made a boot_a patched using magisk apk and inject diretly into boot_a using qfill. It works like a charm. No problem at all.
The problem is that there are something wrong with viper4android using magisk. I want the older 2.3.4 driver and it has a kind of problem using convolver and system inject. User app method does not work.
I own a LG V20 with viper4android on it, and i can confirm that there are something wrong with viper on LG V40. My LG V20 is not a Bang & Olufsen and not even Merodian tune. Maybe the problem lies on this meridian audio tuned on LG V40. Chances are great about that. Devices sound differents and i have to accept this. But...
I would like to try the method that i used to root the LGV20 : Supersu and not magisk. I dont care about safety net. I dont use it. And a second problem with magisk : two apk refuse to open with magisk root method. I know they work with rooted devices but using rootcloack on xposed and xposed is very hard to get to work on magisk ( very limited )
So, i would like to use SuperSu method and not magisk to inject the old 2.3.4 viper4android directly on TWRP. I know how i can do it to works using the original drive and apk from the original devs. ( I dont like the new version 2.7 )
So, sorry for the long explanation, but do you know how i can install TWRP without to use magisk? ( That [TWRP] LG V40 / Judypn does not work. I only get bootloop ).
Thanks again.
In time: Maybe i'm doing something wrong to install TWRP. Do i need to instal it in both slots ( a and b? Do i need to access TWRP using the slot that is not active and make the zips install from there and not from the active slot? It's a kind of confusion for me. I already read a lot about it, but i'm still in doubt how it really works. I'm not interested to use another ROM, just stock.
Click to expand...
Click to collapse
Well... i got to install TWRP in slot a. No more encrypt data. Install Selinux ( SuperSu ) too. Reboot to recovery and no more ask for password, so it works. Data continue to be there. TWRP see the Selinux root, but it always return to TWRP. It does not matter reboot to system, recovery and power off, it always return to TWRP. So, i go to the EDL mode, install v35eng on abl_a, install ablpiestock again to abl_a and...TWRP again...I cant boot.

sptw said:
Well... i got to install TWRP in slot a. No more encrypt data. Install Selinux ( SuperSu ) too. Reboot to recovery and no more ask for password, so it works. Data continue to be there. TWRP see the Selinux root, but it always return to TWRP. It does not matter reboot to system, recovery and power off, it always return to TWRP. So, i go to the EDL mode, install v35eng on abl_a, install ablpiestock again to abl_a and...TWRP again...I cant boot.
Click to expand...
Click to collapse
Hmmm, not sure yet what's going on but I updated the link above in prev post, it now points to a gdrive folder called 20n.
There's a new boot image in it that has just twrp injected, no magisk. Try that and see if it doesn't help. Be sure though of which is your active slot. The way a treble enabled device does ota updates is it will update the inactive slot, with the new version, switch slots, and then boots the new version. What that means is the OLD version is now the inactive slot.
So if u are on 20n, be sure to flash the new image to that slot, not the old one. If need be, use twrp or fastboot (getvar all) will tell you which slot is active.
cheers