Related
THIS APPLIES ONLY TO THE A2017U VARIANT, DO NOT USE THIS FILE ON OTHER VERSIONS
Disclaimer - don't blame me if something goes wrong
As title says, this is a full stock unmodified B20 TWRP system image. It kan be used in addition to stock boot and recovery images to restore the US A7 to conditions which will be like stock and allow to flash upcoming OTA. This was tested by @jkuczera here http://forum.xda-developers.com/showthread.php?t=3459107
Link to system image
https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy
If you are BL unlocked, you will need to lock it before flashing old recovery and boot (this may not be necessary to get MR2 to flash, depending on what it checks, but the phone might not boot, unknown). This will make your phone verify boot, recovery and /system again, so flash TWRP from tenfar's thread to be able boot after relocking since his is signed
To restore, unzip the file above to TWRP folder on the SD Card, then in TWRP under mount points unmount /system and put check mark on mount system as read-only. The read-only part is important so that TWRP does not modify the /system apon exit. You can then restore boot, recovery and system image.
Another partition, fastboot, was altered if you applied B20_boot, but so far no OTA has check it so it should be fine as is. Chance is it will be just overwritten by next OTA, but in case that changes, info will be added. This step is more risky since it involves using dd command and has to be applied carefully.
EDIT: looks like @Unjustified Dev posted new build that will flash fastboot image http://forum.xda-developers.com/showpost.php?p=68677272&postcount=133
You should then boot to stock recovery and factory wipe
In case you did not dump your boot and recovery, they can be found in @rczrider's post here
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Thanks to @swehes for providing the space on his cloud for this file, @rczrider for rest of the files and @jkuczera for trying this all out
So you need TWRP for this, but will this overwrite the TWRP recovery and make it truly stock?
imp3r10 said:
So you need TWRP for this, but will this overwrite the TWRP recovery and make it truly stock?
Click to expand...
Click to collapse
Indeed and before rebooting , you MUST Wipe Data + Internal Storage, cuz you are flashing new boot and system and will get in conflicts if there no wipe.
Just for clarity sake these are the steps I need to take to get back to B20 from B20_Boot?
1. fastboot oem lock
2. put system image from OP's post AND stock_boot_backup.img AND stock_recovery_backup.img from rczrider's post into TWRP folder.
3. in TWRP unmount /system and check mark on mount system as read only.
4. Flash boot, recovery, and system image.
5. Wipe Data and Internal Storage.
6. Profit?
runderekrun said:
Just for clarity sake these are the steps I need to take to get back to B20 from B20_Boot?
1. fastboot oem lock
2. put system image from OP's post AND stock_boot_backup.img AND stock_recovery_backup.img from rczrider's post into TWRP folder.
3. in TWRP unmount /system and check mark on mount system as read only.
4. Flash boot, recovery, and system image.
5. Wipe Data and Internal Storage.
6. Profit?
Click to expand...
Click to collapse
Pretty much. I would reboot to stock recovery after and factory wipe from there. you might wan't to flash fastboot from B20 OTA for extra profit but seems like it's a moot point so far if you have seen the Unjustified Devs trick for BL unlock via TWRP
peramikic said:
Pretty much. I would reboot to stock recovery after and factory wipe from there. you might wan't to flash fastboot from B20 OTA for extra profit but seems like it's a moot point so far if you have seen the Unjustified Devs trick for BL unlock via TWRP
Click to expand...
Click to collapse
Thanks.
I'm having to do a warranty replacement on my device so i'll probably want to do the fastboot flash. Any idea where to get a fastboot image?
runderekrun said:
I'm having to do a warranty replacement on my device so i'll probably want to do the fastboot flash. Any idea where to get a fastboot image?
Click to expand...
Click to collapse
Step 6 to pull your own: http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Or you can download the one I pulled from my device (it can be found in the Mega folder linked in the OP): http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
And as option 3 it's inside the B18toB20 OTA file floating somewhere around here
Alright I tried this and something went wrong.
First thing I did was copy all the files where they needed to be. Then I booted into fastboot and did a "fastboot oem lock".
Then my device would do nothing. I would boot up to the ZTE logo then go black a second later. I tried to force into recovery by selecting recovery in fastboot but same thing, ZTE logo then blackness.
I got it back by getting into fastboot and performing a "fastboot oem unlock" again. All it did was wipe data.
What did I do wrong? I thought I am supposed to lock bootloader first before I restore system and flash recover and boot????
runderekrun said:
Alright I tried this and something went wrong.
First thing I did was copy all the files where they needed to be. Then I booted into fastboot and did a "fastboot oem lock".
Then my device would do nothing. I would boot up to the ZTE logo then go black a second later. I tried to force into recovery by selecting recovery in fastboot but same thing, ZTE logo then blackness.
I got it back by getting into fastboot and performing a "fastboot oem unlock" again. All it did was wipe data.
What did I do wrong? I thought I am supposed to lock bootloader first before I restore system and flash recover and boot????
Click to expand...
Click to collapse
Ok so if you modified boot, system or recovery in anyway then after BL lock it will not boot since it will fail secure boot, so you need to load the signed TWRP from tenfar's thread via EDL after locking. That will let you run TWRP with locked BL. Although ig you just want stock for upcoming OTA, then you might be good staying unlocked. If for return, then you should lock it
peramikic said:
Ok so if you modified boot, system or recovery in anyway then after BL lock it will not boot since it will fail secure boot, so you need to load the signed TWRP from tenfar's thread via EDL after locking. That will let you run TWRP with locked BL. Although ig you just want stock for upcoming OTA, then you might be good staying unlocked. If for return, then you should lock it
Click to expand...
Click to collapse
I apologize if I am fundamentaly not understanding this but wouldn't it be easier to flash system, boot, recovery, and fastboot back to stock via my current twrp THEN relock bootloader?
runderekrun said:
I apologize if I am fundamentaly not understanding this but wouldn't it be easier to flash system, boot, recovery, and fastboot back to stock via my current twrp THEN relock bootloader?
Click to expand...
Click to collapse
Yeah, now that we know fastboot will work even on stock boot that will work as well. The only thing you won't be able to do is flash back the B20 fastboot image that way, but enough to pass OTA most likely. The long way you can revert the fastboot image as well. I only wanted to post the image to begin with, but then wrote out instruction as they rolled around in my head. This will change soon anyways so a proper write-up will happen, just not by me, Documentation was never my forte
My BL is unlocked from ZTE right now, If I want to get CM for future but also want upcoming update from ZTE? What are the exact steps that I need to follow to get future OTA but also keep the BL unlocked for future CM? Please help as I'm confused with all these instructions.
peramikic said:
THIS APPLIES ONLY TO THE A2017U VARIANT, DO NOT USE THIS FILE ON OTHER VERSIONS
Disclaimer - don't blame me if something goes wrong
As title says, this is a full stock unmodified B20 TWRP system image. It kan be used in addition to stock boot and recovery images to restore the US A7 to conditions which will be like stock and allow to flash upcoming OTA. This was tested by @jkuczera here http://forum.xda-developers.com/showthread.php?t=3459107
Link to system image
https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy
If you are BL unlocked, you will need to lock it before flashing old recovery and boot (this may not be necessary to get MR2 to flash, depending on what it checks, but the phone might not boot, unknown). This will make your phone verify boot, recovery and /system again, so flash TWRP from tenfar's thread to be able boot after relocking since his is signed
To restore, unzip the file above to TWRP folder on the SD Card, then in TWRP under mount points unmount /system and put check mark on mount system as read-only. The read-only part is important so that TWRP does not modify the /system apon exit. You can then restore boot, recovery and system image.
Another partition, fastboot, was altered if you applied B20_boot, but so far no OTA has check it so it should be fine as is. Chance is it will be just overwritten by next OTA, but in case that changes, info will be added. This step is more risky since it involves using dd command and has to be applied carefully.
EDIT: looks like @Unjustified Dev posted new build that will flash fastboot image http://forum.xda-developers.com/showpost.php?p=68677272&postcount=133
You should then boot to stock recovery and factory wipe
In case you did not dump your boot and recovery, they can be found in @rczrider's post here
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Thanks to @swehes for providing the space on his cloud for this file, @rczrider for rest of the files and @jkuczera for trying this all out
Click to expand...
Click to collapse
Can someone please explain exactly how to do this. I have an unofficial twrp on my phone and the bootloader is unlocked but after i tried to flash super su it got stuck on bootloop so I wiped every thing and I also accidentally wiped my os too. So now I don't have an os and I want to go back to stock. Can someone please explain step by step on how to fix this? I just got the phone.
seby1234 said:
Can someone please explain exactly how to do this. I have an unofficial twrp on my phone and the bootloader is unlocked but after i tried to flash super su it got stuck on bootloop so I wiped every thing and I also accidentally wiped my os too. So now I don't have an os and I want to go back to stock. Can someone please explain step by step on how to fix this? I just got the phone.
Click to expand...
Click to collapse
All right I'm no expert either but I'll try to make this as straightforward as possible.
1) Format your SD card as exFAT. This is important as otherwise you will not be able to transfer the system image to your SD card since it is 6GB. To do this you can just plug it in to your PC, right click, Format and then select exFAT from the dropdown.
2) Download tenfar's tool for B20, rczrider's boot and recovery backup, and the system image backup from the link in the OP.
3) Create a new folder in /external_sd/TWRP/BACKUPS/serial_number/.Move the stock_boot_backup and stock_recovery backup into the folder.
4) Using a program such as 7zip, extract the 6GB system image file and move it to the same folder.
6) Go to into fastboot mode. Before you do anything you have to relock the bootloader otherwise the system will be modified and you want to be 100? stock. Execute 'fastboot oem lock'. You should then boot to a black screen.
7) Unzip tenfar's tool. Go to the unzipped folder, then hold down shift+right click and select 'Open command window here'. Execute 'axon7root.exe -p [COMPORT #] -r. To figure out your com port #, go to Device Manager, then go to down to where it says "Qualcomm Loader..." and your com port number is the number at the end. So for example if your com port number is 5, you should execute axon7root.exe -p 5 -r. Allow the program to do its thing.
5) Boot into TWRP. Do not swipe to allow modifications. Once in TWRP, go to "Install", "Install Image" at the bottom right hand corner, and then navigate to the stock_recovery_backup in the folder that you moved it to to. Select it and then choose the Recovery partition to flash it to. Do the same thing for stock_boot_backup.
6) Once you have flashed boot and recovery, go to the main menu, then "Restore" and then Restore the system image backup.
7) Go to wipe and then slide to factory reset. Finally, reboot system.
Hope that helps! If you have any questions, feel free to ask me.
rczrider's stock boot and recovery thread
http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818/page7
tenfar's tool thread: http://forum.xda-developers.com/axo...xon-7-root-bootloader-unlokced-t3441204/page1
Has anyone who requested the bootloader unlock from ZTE (and mistakenly installed it) returned to stock and been able to get OTA's? I followed this guide and seemed to have returned to stock fine but the only OTA I can get now is the bootloader unlock OTA. I've downloaded and discarded it several times but that is the only one I can get. Anyone know of a way to bypass this OTA and get the new MR2 that was just released? I want to get OTA's until the custom roms start flowing.
Thanks!
shifuharris said:
Has anyone who requested the bootloader unlock from ZTE (and mistakenly installed it) returned to stock and been able to get OTA's? I followed this guide and seemed to have returned to stock fine but the only OTA I can get now is the bootloader unlock OTA. I've downloaded and discarded it several times but that is the only one I can get. Anyone know of a way to bypass this OTA and get the new MR2 that was just released? I want to get OTA's until the custom roms start flowing.
Thanks!
Click to expand...
Click to collapse
From what I can tell, once you apply for official bootloader unlock, your IMEI is placed on a list that will not get any future OTA updates set to it.
However, the OTA for B20 to B27 has been uploaded here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ
Try flashing that via stock recovery.
Quick question for anyone who might know.
The Link to system image which is : https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy has the following;
1. system_image.emmc.win
2. system_image.emmc.win.md5
Am I suppose to rename system_image.emmc.win to system_image.emmc.img and load?
it's not as clear that's why I ask but I ended up downloading rczrider system.img and reflashed via TWRP since I was a bit confused.
Thanks!
***************
I simply just went into TWRP backed up by boot so it would create a directory that contains the info I needed copied the system_image.emmc.win and system_image.emmc.win.md5 and restored.
xtermmin said:
From what I can tell, once you apply for official bootloader unlock, your IMEI is placed on a list that will not get any future OTA updates set to it.
However, the OTA for B20 to B27 has been uploaded here: https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ
Try flashing that via stock recovery.
Click to expand...
Click to collapse
I suspected as much. I downloaded the update and tried to flash it via the stock recovery using the update for ADB option but it fails saying that the package is not a ks package. Booooo. I really wanted this MR becasue they addressed the weak cell signal which I think contributes significantly to my battery drain. Not sure if there are any alternatives to get the update installed. Not very a happy about the ceased OTA's due to the bootloader unlock. Thinking the new Nexus (or whatever they are going to call them) is looking pretty good at the moment.
shifuharris said:
I suspected as much. I downloaded the update and tried to flash it via the stock recovery using the update for ADB option but it fails saying that the package is not a ks package. Booooo. I really wanted this MR becasue they addressed the weak cell signal which I think contributes significantly to my battery drain. Not sure if there are any alternatives to get the update installed. Not very a happy about the ceased OTA's due to the bootloader unlock. Thinking the new Nexus (or whatever they are going to call them) is looking pretty good at the moment.
Click to expand...
Click to collapse
Try the microSD card method instead.
First, make sure OEM Unlocking is checked in developer settings, rename the OTA to "update.zip", put on microSD, boot into stock recovery, and choose update from microSD.
I have an Android One Moto x4 running 8.1.0 OPW28.2 (OPW28.46-18) and I am getting a notification for the OPW28.3 OTA update. I want to install it, but I have TWRP and Magisk installed.
I tried to uninstall Magisk and then install the OTA, but it said "update failed". Did I do something wrong? Do I also need to uninstall TWRP/restore a 100% stock boot.img?
You have to be completely stock to apply otas.
Thanks, that helps. The only "non-stock" things are TWRP and Magisk. Hopefully restoring a stock boot.img should be enough to let me install it.
Try this method.
Tried to restore images in Magisk but got the message "Stock backup does not exis!"
I think when I installed Magisk I chose Direct Install (recommended). Does Magisk only create a backup boot file if installed another way? (Patch Boot Image File)
Ok, so not only did I completely uninstall Magisk, I also restored a stock boot.img (from https://forum.xda-developers.com/showpost.php?p=77096052&postcount=2).
When I went to install the OTA, it said "failed". I'm not sure what else I need to do.
Well, I have a few other ideas... when I opened TWRP, it said I was on slot B. Is that right? What if I switch to A? Or what if I stay on B, but I erase A's system partition? Do I need to copy system from B to A or something?
OH! What if I use TWRP to restore the backup I downloaded to slot A, boot to that, then try to install the OTA?
Why is this failing even though I have a stock system and boot?
Do you have stock recovery? Because OTA uses that, not TWRP.
MacFett said:
Do you have stock recovery? Because OTA uses that, not TWRP.
Click to expand...
Click to collapse
installing stock boot.img would have installed stock recovery.
MacFett said:
Do you have stock recovery? Because OTA uses that, not TWRP.
Click to expand...
Click to collapse
Yeah, the recovery is back to stock. There's something I'm missing, but I'm not sure what it is. Something to do with the A/B slots, I think.
I've been messing around with installing the OTA on an A1 phone today as well. I've flashed back to stock at least a half-dozen times. So far all I've been able to determine is that the OTA updates are supremely touchy.
If I do nothing in fastboot after flashing back to stock 28.1 then 28.2 and 28.3 will install just fine, and if I do anything with booting TWRP or flashing images the OTAs fail.
Also, the 28.3 update seems to take way longer to install than the 28.2.
NTICompass said:
Yeah, the recovery is back to stock. There's something I'm missing, but I'm not sure what it is. Something to do with the A/B slots, I think.
Click to expand...
Click to collapse
Do you need to relock the boot loader?
MacFett said:
Do you need to relock the boot loader?
Click to expand...
Click to collapse
Wouldn't that factory reset the phone?
tormin said:
I've been messing around with installing the OTA on an A1 phone today as well. I've flashed back to stock at least a half-dozen times. So far all I've been able to determine is that the OTA updates are supremely touchy.
If I do nothing in fastboot after flashing back to stock 28.1 then 28.2 and 28.3 will install just fine, and if I do anything with booting TWRP or flashing images the OTAs fail.
Also, the 28.3 update seems to take way longer to install than the 28.2.
Click to expand...
Click to collapse
That's what I wound up doing to get all the way up to date. I flashed the stock 28.1 (modifying the flash_stock.sh script to not flash the partition file or erase userdata) and then I was able to OTA update to 28.2 and then 28.3
MacFett said:
Do you need to relock the boot loader?
Click to expand...
Click to collapse
Unlocked bootloader worked fine for me.
boot image it's your stock kernel, not your recovery. I don't understand how you get stock recovery. The only way I know to do that, its flashing a stock recovery and then fully unroot your phone, Now try to installed the OTA update. You can get the recovery image from a stock firmware, but to be sure it would work, try to use the same version as your phone is (Europe, Latam, India...)
downface said:
boot image it's your stock kernel, not your recovery. I don't understand how you get stock recovery. The only way I know to do that, its flashing a stock recovery and then fully unroot your phone, Now try to installed the OTA update. You can get the recovery image from a stock firmware, but to be sure it would work, try to use the same version as your phone is (Europe, Latam, India...)
Click to expand...
Click to collapse
I think the moto x4 is a little weird and the recovery is actually part of the boot image.
NTICompass said:
That's what I wound up doing to get all the way up to date. I flashed the stock 28.1 (modifying the flash_stock.sh script to not flash the partition file or erase userdata) and then I was able to OTA update to 28.2 and then 28.3
Click to expand...
Click to collapse
How'd you do that? If you dont mind me asking, how to edit it? Thanks
nabhse90 said:
How'd you do that? If you dont mind me asking, how to edit it? Thanks
Click to expand...
Click to collapse
I grabbed the stock image from https://forum.xda-developers.com/moto-x4/how-to/oreo-8-1-official-firmware-available-t3805173 and grabbed a "flash_all" script from https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I opened up the flash_all.sh script and just removed the line "fastboot erase userdata" (I also removed "fastboot flash partition gpt.bin", not sure if I really needed to).
NTICompass said:
I grabbed the stock image from https://forum.xda-developers.com/moto-x4/how-to/oreo-8-1-official-firmware-available-t3805173 and grabbed a "flash_all" script from https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I opened up the flash_all.sh script and just removed the line "fastboot erase userdata" (I also removed "fastboot flash partition gpt.bin", not sure if I really needed to).
Click to expand...
Click to collapse
Yey! Thank you thank you! I can now update without having to go through all that process of updating multiple times just to have the latest version. So just removing the "erase userdata" is fine right? If I dont do the other it still works fine? Just making sure because I think Im just gonna boot TWRP and flash Magisk so I can stick to stock boot.img and just update whenever they pop. Thanks again!!!
nabhse90 said:
Yey! Thank you thank you! I can now update without having to go through all that process of updating multiple times just to have the latest version. So just removing the "erase userdata" is fine right? If I dont do the other it still works fine? Just making sure because I think Im just gonna boot TWRP and flash Magisk so I can stick to stock boot.img and just update whenever they pop. Thanks again!!!
Click to expand...
Click to collapse
I'm not 100% sure what all the lines in the flash_all.sh script do, so I can't provide any guarantees. It worked for me to remove the 2 lines: "fastboot flash partition gpt.bin" and "fastboot erase userdata". Then I was able to flash the original/stock 28.1 image to the system. When it booted, I installed the 28.2 OTA, rebooted and then I was able to install the 28.3 OTA.
I had to do this craziness because the 28.3 OTA was failing to install for me otherwise.
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.
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
I have a G7 Plus Retail version on stock ROM, rooted and Magisk installed. Via other threads, I have learned how to manually flash updates by extracting the zip file and then running fastboot command lines. Yesterday, I received an alert that QPWS30.61-21-18-7-8 update is available, via OTA updates on my phone - of course I know I can't run the OTA update, even if I uninstall magisk and restore boot image, etc., but I am wondering if anyone knows where to find this update as a downloadable zip so I can manually flash it? It doesn't seem to be on the mirrors.lolinet.com site where all the other g7 plus stock ROMs are.
I've been into custom ROMs in the past but to me this stock ROM is reliable and un-bloated enough that it's acceptable for my needs.
Is your device xt1965-t by any chance?
Could you back up your unmodified /system in TWRP as an image, and send it to me? It should be QPWS30.61-21-18-7-3 right now. I'd greatly appreciate!
Technically, if you booted TWRP externally and did not decrypt /data, you should be able to replace boot to the unrooted stock, and it would take OTA if all the partitions are stock. Then your current partition of A/B will be QPWS30.61-21-18-7-8, and the other one of A/B will be QPWS30.61-21-18-7-3 (the one you are currently running). At this point you can reroot the boot image for QPWS30.61-21-18-7-8.
See this for some details:
rooted XT1965-T, can I boot earlier OS version via A/B switch to apply OTA?
I got this weird non-Tmobile XT1965-T phone that was discussed elsewhere (XT1965-T non-Tmobile). I only rooted boot.img, kept stock recovery & /data encryption, as in this link. But then I flashed a program into /system (my bad!) by accident. So...
forum.xda-developers.com
bibikalka said:
Is your device xt1965-t by any chance?
Could you back up your unmodified /system in TWRP as an image, and send it to me? It should be QPWS30.61-21-18-7-3 right now. I'd greatly appreciate!
Technically, if you booted TWRP externally and did not decrypt /data, you should be able to replace boot to the unrooted stock, and it would take OTA if all the partitions are stock. Then your current partition of A/B will be QPWS30.61-21-18-7-8, and the other one of A/B will be QPWS30.61-21-18-7-3 (the one you are currently running). At this point you can reroot the boot image for QPWS30.61-21-18-7-8.
See this for some details:
rooted XT1965-T, can I boot earlier OS version via A/B switch to apply OTA?
I got this weird non-Tmobile XT1965-T phone that was discussed elsewhere (XT1965-T non-Tmobile). I only rooted boot.img, kept stock recovery & /data encryption, as in this link. But then I flashed a program into /system (my bad!) by accident. So...
forum.xda-developers.com
Click to expand...
Click to collapse
Unfortunately, I have the xt1965-2 if I do a fastboot getvar -all.
cllewis1 said:
Unfortunately, I have the xt1965-2 if I do a fastboot getvar -all.
Click to expand...
Click to collapse
Ok, nevermind then.
But for you - my recommendation is that you put back the stock boot, and see if takes the OTA update. Unless you installed TWRP & decrypted /data, in that case you are out of luck.
All OTA cares about is that partitions that it's about to patch have the original checksums. If they do, it'll proceed.
bibikalka said:
Ok, nevermind then.
But for you - my recommendation is that you put back the stock boot, and see if takes the OTA update. Unless you installed TWRP & decrypted /data, in that case you are out of luck.
All OTA cares about is that partitions that it's about to patch have the original checksums. If they do, it'll proceed.
Click to expand...
Click to collapse
Yeah, I have TWRP. Therefore I think my only option for the update is to get hold of the zip file, extract it, and manually install it piece by piece (which takes all of 10 minutes to do once I have the file downloaded.)
Hey, when I boot into fastboot I see xt1965-T, which is apparently the non-tmo version since I got it retail direct from moto. Do you need me to backup system or system image and send to you?
cllewis1 said:
Hey, when I boot into fastboot I see xt1965-T, which is apparently the non-tmo version since I got it retail direct from moto. Do you need me to backup system or system image and send to you?
Click to expand...
Click to collapse
Oh, could you back up /system for QPWS30.61-21-18-7-3 as an image if that's what you have? And put it somewhere?
Is your channel RETLA in settings?
I think if you back up your /data (unencrypted I assume?) in TWRP, you could just flash the entire new OS from here:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Backup of the /data is important in case things go south. You could later pull programs from the TWRP backup using TitaniumBackup. For /sdcard, use TotalCommander, zip it, and if you unpack later, TotalCommander can even restore time stamps if you give it root.
These versions are a bit confusing, that's why I'd rather restore /system, and let it OTA instead of flashing the full ROM. But it does not seem you have this option anymore (if you decrypted /data, your /vendor is probably modified).
Update: If you want, I could give you stock /boot, /recovery, /vendor. But if you are decrypted, you are better off just loading that entire new ROM. If you find a good guide for A/B Moto phones, please let me know (it's important not to mess up A/B stuff).
So it turned out that the RETLA firmware works fine for my phone, which is indeed the xt1965-T. I manually installed the update using the fastboot flash command line for each of the component files, then used fastboot to boot back into TWRP and reinstalled TWRP and Magisk from there.
Where's a good place for me to put that file so you can access it?
cllewis1 said:
So it turned out that the RETLA firmware works fine for my phone, which is indeed the xt1965-T. I manually installed the update using the fastboot flash command line for each of the component files, then used fastboot to boot back into TWRP and reinstalled TWRP and Magisk from there.
Where's a good place for me to put that file so you can access it?
Click to expand...
Click to collapse
Good news! Did you wipe /data too? Or did you keep it? Did you keep the log of commands by any chance? I am still a bit hazy with this A/B business, and as such, want to proceed more carefully than usual
For storage, you can use one of the free options (something like Dropbox or Mediafire, or even Google Drive):
15 Best FREE Cloud Storage & Online Unlimited Drive Space
Cloud storage is a way of storing data online. It requires an internet connection in order to maintain, manage, and share documents, presentations, spreadsheets, images, audio, video, etc. with others
www.guru99.com
You can just PM the file link to me (not in the forum).
Thanks for the effort!
I ran the commands from the command prompt by extracting the zip file and then putting fastboot.exe into the folder where I put the contents of the zip file:
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 dsp adspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot reboot
Note that this is a "dirty" flash and will leave all your apps, all your data, all your settings intact. Note that you will lose TWRP recovery by doing this.
To get TWRP back, after rebooting and letting the update finish installing, you can go back into fastboot and do a
fastboot boot twrp.img (fill in whatever the name of your twrp boot image is)
This will boot you into TWRP. From there you can install twrp recovery and magisk.
Note - do not do:
fastboot flash twrp.zip - attempting to flash twrp recovery from fastboot will soft brick your phone and you'll have to go back and run all these commands again.
cllewis1 said:
I ran the commands from the command prompt by extracting the zip file and then putting fastboot.exe into the folder where I put the contents of the zip file:
...
To get TWRP back, after rebooting and letting the update finish installing, you can go back into fastboot and do a
Click to expand...
Click to collapse
OK!
It looks like TWRP can read /data partition now, which is different from when I tried it last time for a moto g6.
I could not use your TWRP system backup since it is not a bit-for-bit "system image" version (it was just a straight system backup with files). It would not restore "dm-verify" checksum to enable OTA. To have a bit for bit one gotta do "system image" in TWRP.
Your list of commands is slightly different compared to flashfile.xml file. You may want to double check that since it seems you've missed some partitions.
I think your original system image may be gone from your phone - depending on A/B situation, so I better use the full ROM and just install it directly (as you did).
Is everything working fine for you with the updated ROM?
Short answer is yes, everything's working fine.
I skipped
fastboot erase userdata
Because I didn't want to erase all my data.
I knew I hadn't used BTFM.bin, frankly, I didn't know what to do with it, so I just skipped it. Now that I realize it's for the bluetooth radio, I have gone ahead and flashed it just now, after the fact. Hopefully this will improve my bluetooth performance a bit...I've found that if this phone is in my hip pocked and I squat down to work on a piece of lawn equipment, my bluetooth gets very choppy.
I also skipped the
fastboot logo logo.bin
because I don't really care about the boot logo when I turn the phone on.
I also pulled a backup (pre-upgrade) of system_image in TWRP...do you think that would work better for you?
cllewis1 said:
Short answer is yes, everything's working fine.
I skipped
fastboot erase userdata
Because I didn't want to erase all my data.
I knew I hadn't used BTFM.bin, frankly, I didn't know what to do with it, so I just skipped it. Now that I realize it's for the bluetooth radio, I have gone ahead and flashed it just now, after the fact. Hopefully this will improve my bluetooth performance a bit...I've found that if this phone is in my hip pocked and I squat down to work on a piece of lawn equipment, my bluetooth gets very choppy.
I also skipped the
fastboot logo logo.bin
because I don't really care about the boot logo when I turn the phone on.
I also pulled a backup (pre-upgrade) of system_image in TWRP...do you think that would work better for you?
Click to expand...
Click to collapse
YES! It's great if you still have it!!! Could you upload it to your drive that you shared before?
Thank you in advance!
It's good thing I checked - I was already on the way to start getting ready for a more laborious update.
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
cllewis1 said:
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
Click to expand...
Click to collapse
Interesting ... Could you still upload that system image file for QPWS30.61-21-18-7-3 to your file storage? I have not updated yet - too busy with other things, and wanted to do it carefully. Much appreciated!
cllewis1 said:
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
Click to expand...
Click to collapse
Alright, I restored my system with your system image (many thanks!), and put back the stock boot. So it goes through the update (meaning the checksums are good), but then I get the dreaded "software update unsuccessful" message.
You could try this too, put back stock boot/recovery from the ROM, and see if it would update.
Edit: It looks like simply unlocking bootloader makes OTA fail:
"verity mode set to disabled"
I unlocked the bootloader of my G7plus, installed TWRP and then used TWRP to install Magisk. So far, everything is working, root hiding is working as it should and Magisk's "SafetyNet Check" is reporting success. Yay. Almost. a) During the boot...
forum.xda-developers.com
cllewis1 said:
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
Click to expand...
Click to collapse
7-10 is available now:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETLA/XT1965-T_LAKE_RETLA_10_QPWS30.61-21-18-7-10_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
bibikalka said:
7-10 is available now:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETLA/XT1965-T_LAKE_RETLA_10_QPWS30.61-21-18-7-10_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks, got it installed. Works fine.
cllewis1 said:
Thanks, got it installed. Works fine.
Click to expand...
Click to collapse
Looks like 7-12 is available:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Way too many updates, LOL
Is that 7-12 fie working on your xt1965-T (cause on lolinet its labled xt1965-2) and that doesnt seem right.