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.
Related
So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
LiamAtkins90 said:
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
Click to expand...
Click to collapse
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
prasad.adam said:
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
Click to expand...
Click to collapse
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
HamRack said:
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
Click to expand...
Click to collapse
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
HamRack said:
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
Click to expand...
Click to collapse
SD card is OK. As USB disk,haven't give a try.
Ok, cheers. I'll get a usb otg cable and give it a go.
HamRack said:
Ok, cheers. I'll get a usb otg cable and give it a go.
Click to expand...
Click to collapse
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed. You should check the directory first, moreover, that file was released for those KK users. I have no idea whether it would take effect on lollipop or destroy your system. Take your own risk.
purejoy said:
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed.
Click to expand...
Click to collapse
So I found, but because my first reaction to the second bootloop was to erase userdata (as had fixed the earlier one) I lost that.
purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
HamRack said:
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Click to expand...
Click to collapse
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
---------- Post added at 01:29 AM ---------- Previous post was at 01:07 AM ----------
HamRack said:
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
Click to expand...
Click to collapse
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Sorry for not reading all the reply's in this thread before posting (i'm in a bit of a rush)
I got a bootloop while applying the OTA on a brand new XT 1092 right after taking out of the box. After some digging around the forums (you can tell i'm new by the post count) i managed to get an OTA zip for my DE version and pushed it via ADB using stock recovery, with a few hickups:
- had to manually install the driver in windows
- first time the install via ADB push failed with some assert failure on something related to moto.odex
- the second try went ok and got the bootloop sorted.
So definitely give ADB a shot
Good luck!
First, try to recover as much as of your data stored on the device .
Then reflash the old ROM. You'll need a specific program for that - and a PC Surely! ☺
After that to get easier Back-Ups - i recommend unblocking the bootloader.
All the best☻.
purejoy said:
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Click to expand...
Click to collapse
I used TWRP 2.8.1.0, I downloaded it that day. Not sure what else it could have been...
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Click to expand...
Click to collapse
Not sure when I was supposed to do that, couldn't see that in your directions...? Not a really a problem either way as its now sorted.
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Click to expand...
Click to collapse
Ok, thanks for the info. Any idea how to remove those verifications? Would this do the required thing?
Also, what exactly do you mean by the .19 OTA zip? You mean the OTA zip with the new bootloader in with it? If it has an error while trying this, would it give problems or just stop and return as before?
Thanks
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
purejoy said:
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
Click to expand...
Click to collapse
I'm not sure of the differences either...
So I'm wanting to make sure I do this correctly this time. I know a couple of ways of backing up but after all the faff recently I want to have an ironclad backup before I piss around with anything else (foolish me for not doing so before). Can you clarify the best way to back up my device and how I would do that? I have a feeling I haven't been doing it correctly/the most ideal way before and it would be good to know.
Also, how would I go about putting that backup you've pointed too (thank you for finding that, I don't think I'd been searching for quite the right thing) on to my device? Would I go through a similar series of steps to how I recovered my phone before (ie here)?
I'm going away for xmas/NY and will probably do this when I get back so I don't risk borking my phone when I need it most. Nonetheless, it would be good to have things ready to roll when I get back.
Thanks for your help, you've been great.
It depends on what you plan to backup and i don't konw what app your are using. If you use Google service, Contacts and some app data are normally synced to Google Cloud Servers. You can get them back in lollipop 5.0 via your Google account. As your pictures and videos,you can also directly copy them on your PC. What you need to backup are private app data and private messages. You can use some 3rd party backup apps like TitaniumBakcup to solve this. If there are not so much user data, you can backup like this.
You can also backup and restore your userdata via TWRP. If you get so many data, you can try this.
As the full stock recovery,you can restore your phone via fastboot utility or RSD lite.
1.Download and Unzip the image.
2.Put your phone in AP Fastboot Mode.
3. $ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot -w (Erase userdata. Optional,maybe unnecessary)
$ fastboot reboot
I would advise you to put off erasing data. If you get any issues while rebooting into new system, then you can erase your data.
Hope these help. Good Luck!
Great, thanks for the tip.
I tend to have minimal important data on my phone that isn't covered by either google or evolvesms/whatsapp. Nonetheless, thanks for the tips. I've been using titanium for a long while and have that backed up to dropbox too.
I tried flashing TWRP after I fixed the clusterbadger that was the last few days, but had no luck. I still don't seem to be able to push the image over using adb nor use adb to issue commands while booted into TWRP through fastboot. Have you experienced that? I guess worst case is that I copy the zip to an sdcard and flash it from usbotg by issuing commands in the TWRP shell they give you...?
Thanks for the tip on the userdata too.
Below are the instructions for using MoFo to flash the AT&T XT1097 to 5.1. The rooted image has a modified build.prop file for free tether. Thanks go to @Slack3r for making the ext4 image and @btdownloads7 for developing the root method.
Since this is a 5.1 image, in order to get it to boot, you need to do the following BEFORE flashing the 5.1 system image:
1) Download the stock 5.1 files and extract them:
https://mega.co.nz/#!bN0BjKbI!zzq5b9wZBo-XFGNkcWtgw7mnXZgC5BWrEC-GZcGLELo
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /cache - YOU MUST DO THIS!
3) Reboot into bootloader mode and run the commands below to flash the following stock 5.1 files for the XT1097:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
Do NOT flash the 5.1 bootloader (motoboot.img) or partition table (gpt.bin) - if you do, you will not be able to use MoFo ever again!!!!!
4) Download the rooted 5.1 image from here, extract it and flash it using MoFo.
https://mega.co.nz/#!ct8DlQxQ!DRMC_TvCcUk7V-FjCBfjsmIoOvw_f0WEdM7gx2waqzM
MD5 of the unzipped file = 146B6A65D925B985857A2F28D4294765
Note that with the XT1096 we had issues if we tried to boot into recovery after initially flashing the 5.1 system image so instead of booting into recovery and wiping cache where you might get weird flashing dead androids, we had to boot into system first.
Obviously if you want Xposed or anything else in the image, someone will need to add it in.
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Casyis said:
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Click to expand...
Click to collapse
No, the instructions as written in the OP are complete. Like the instructions say, you need to do step 2:
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /data/cache - YOU MUST DO THIS!
Then you can flash the rest of the 5.1 stock files for your device EXCEPT for the bootloader (motoboot.img) and partition table (gpt.bin). Then use MoFo to flash the rooted 5.1 image for your device.
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Casyis said:
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Click to expand...
Click to collapse
This was happening with the XT1096 - you have to get it into system before recovery. You likely hit the wrong button and ended up in recovery instead of system. But once you get it into system, then it is fine.
Thanks again @JulesJam I am downloading now! Do you notice a big performance difference in 5.1? Will be nice to finally kill these memory bugs, so major thanks for that!
The OS is much snappier than 5.0.2. You can tell by going into multitasking and seeing how quickly the tiles load. Very, very nice. No re-draws at all yet since I flashed.
Step 2 implies that I'm already rooted. If I'm not, I assume I need to start with Step 0: Root the device with a 5.0 IMG?
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
bamachevrolet said:
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
Click to expand...
Click to collapse
FYI - like it says in the MoFo Noob Guide - MoFo trips the root checker and it is not able to be undone by flashing back to stock. I don't know how AirWatch works, but if it looks at the qe, then it will see you as rooted even if you aren't.
First thing I would do is flash back to 5.0.2 by flashing the stock 5.0.2 firware (link is in the MoFo Noob Guide)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1 (repeat this for all of the sparsechunks)
then boot into recovery and wipe the cache. Then boot into system. I believe it will need to downgrade the sensor firmware so allow that to happen.
Then boot into bootloader mode and see if your software status still says modified or not. Then boot into recovery and see what your qe status is. If after that your software status is still modified and your qe is still 1/1, I would do a factory reset and see if that corrects it. It probably won't though.
You will then have to decide whether or not you want to take the 5.1 OTA because your phone is going to want to upgrade. Instead of taking the 5.1 OTA which will upgrade your bootloader and partition table, you have the option of flashing stock 5.1 everything but the motoboot.img and gpt.bin. That would keep you stock 5.1 but still keep your bootloader and partition table on 5.0.2 so that if you wanted to sell the phone later, you could sell it with a copy of MoFo that still works. I put this out there because idk how AirWatch works and if flashing back to stock doesn't change your software status from modified or your qe from 1/1, you may not be able to use AirWatch, idk.
Thank you so much for the detailed explanation @JulesJam . Unfortunately I followed the instructions to the T and didn't run into any issues until I tried to boot into recovery. I got the dead android with a line under saying "no command". So I tried running system first. I got through the boot animation and then a black screen. I let the black screen sit for 30 min and nothing happened. I had the exact issue when installing 5.1, I was able to get it to boot using BT tools. Unfortunately this is not working now. I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
bamachevrolet said:
I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
Click to expand...
Click to collapse
For sure you flashed the 5.0.2 logo.bin, boot.img and all of the 5.0.2 system sparsechunks? That sounds like the system partition was not flashed properly.
Perhaps the 5.0.2 system files you have are corrupted? Are you sure the files you have are the stock 5.0.2 files for the AT&T XT1097?
bamachevrolet said:
I got the dead android with a line under saying "no command". !
Click to expand...
Click to collapse
That's OK as long as he is not flashing. When you have the dead android, go ahead and press and hold power then tap volume up to get into recovery and wipe the cache.
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
bamachevrolet said:
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
Click to expand...
Click to collapse
How long do you let the blank screen sit before you try to get into bootloader mode? I remember sometimes it takes awhile for it to boot.
Also, the dalvik-cache may need to be wiped too. That would require a factory reset to do it so you could boot into recovery and do a factory reset. Unless there is some way to wipe the dalvik-cache from bootloader mode.
bamachevrolet said:
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
Click to expand...
Click to collapse
That's fine. I wasn't sure what number they started with.
bamachevrolet said:
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Click to expand...
Click to collapse
And after you do, let it sit at the blank screen for awhile to make sure that it isn't an issue of needing time to boot up. If it still won't boot, try the factory reset.
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!!
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
[/COLOR @JulesJam do you have a donation link?
bamachevrolet said:
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!![
Click to expand...
Click to collapse
Glad it worked out, sucks about the tasker profiles though. So it seems like the dalvik-cache has to be wiped, too. I will note that in the future people should delete the contents of the dalvik-cache folder before flashing back to the earlier version of the software.
Does your software status still say modified in bootloader mode? What is your qe when you boot into recovery?
bamachevrolet said:
@JulesJam do you have a donation link?
Click to expand...
Click to collapse
No but thanks for the offer. If you want to donate, please donate to the ASPCA.
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this
Wow and so it begins, great work thanks!
Thanks
Sent from my Pixel using XDA-Developers mobile app
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.
zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root
T-Mobile G6 H872 11G Stock Collection
Based on OEM 11g KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
SysBoot ROMs were test flashed over 11g and 20a bootloaders. 11h has not been tested.
11G Firmware is ARB01
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
FILE BREAKDOWN
The following Zips DO NOT include stock LAF.
You must flash the provided LAF separately if you wish to go back to stock DL mode
Bootloader: 11g Stock Bootloader ONLY
SysBoot: 11g Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 11g Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
TWRPLAF: Individual LAF image for replacing stock DL mode with TWRP
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
INSTRUCTIONS
Make a FULL TWRP Backup using 3.2.3. Link to thread is below.
Boot to TWRP and do a Format Data to remove encryption from your device.
Reboot back to Recovery after Formatting in order for TWRP to mount System.
Advanced Wipe - System, Data, Cache and Dalvik
Flash your chosen Zip using TWRP
You must have TWRP on recovery to flash LAF images.
It is recommended that Sysboot Images be flashed AFTER Bootloader or FullStock
If you Flashed SysBoot with Patched Kernel and Root, you are good to go. Otherwise, flash Magisk to maintain root access.
Wipe Cache/Dalvik
Reboot to system.
Your phone may reboot once or twice during the initial boot to system. This is normal.
Your phone may hang a while on the boot logo. This is also normal. If hang persists for too long, hold vol-down+power until phone powers off to reboot.
DOWNLOADS
Stable v1.0
Project Files have been moved to SourceForge
TWRP 3.2.3 for H872 by @Eliminator74 - Thank you for all the work you have done for the G6!
Magisk + Magisk Manager
Bootloader - md5:43dcc7f82c501147da6500efdd594d5c
SysBoot ROM - md5:2ac20008794eb74523a442da7b8bafdc
SysBoot Deodexed - md5:b92fcb7649bddf934ff9be0246c9fab6
SysBoot w/Patched Kernel + Magisk Root - md5:ae4bab194a69b2044f3aee69ba495464
FullStock ROM - md5:e919fe16852b5f0b830a48cda914003a
StockLAF - md5:ce70b36e4d293e183544a18409a526de
TWRPLAF - md5:f8ea4e93dc417d2d31f5cb8b77530bfa
These files are long overdue. I hope you all find them helpful. Please let me know if you run into any problems with them. Thanks!
Other H872 Projects
H872 11H Stock Collection
H872 20A SysBoot ROMs (Stock and Rooted)
H872 20D Stock Collection
Announcement
I have officially moved to the V30 and no longer own the G6.
I will still be active in this community, but since I don't have the device any longer I will not be able to test any packages or issues that might arise.
All of my current projects have been tested. If anybody runs into problems, you can still let me know and I'll do my best to support my stock packages.
Thanks guys!
-weakNPCdotCom
XDA:DevDB Information
[STOCK] h87211g, ROM for the T-Mobile LG G6
Contributors
weakNPCdotCom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.2.3
Based On: 11g KDZ
Version Information
Status: Beta
Current Stable Version: 1.0
Stable Release Date: 2018-09-30
Current Beta Version: 0.9
Beta Release Date: 2018-09-30
Created 2018-09-29
Last Updated 2018-10-19
Thx))) I was very much waiting for this.
I'm now at 20a. if I flash the bootloader only, then the fingerprint scanner will work on custom firmwares? Does the custom LAF work?
DmytroPitenko said:
Thx))) I was very much waiting for this.
I'm now at 20a. if I flash the bootloader only, then the fingerprint scanner will work on custom firmwares? Does the custom LAF work?
Click to expand...
Click to collapse
very welcome. if you flash the bootloader only it will leave whatever laf you have untouched, and yes fingerprint scanner will work with custom ROMs like AOSP Extended.
However, I have not tested running stock 20a with the 11g bootloader. But it doesn't sound like that's what you are wanting to do
*edit*
if you have already flashed a custom Rom and FP doesn't work, simply flashing the 11g bootloader zip will fix it. it is not necessary to reflash the rom
also, not sure why anybody would want to, but 11g bootloader with stock 20a rom will not work. it will hang on the boot logo indefinitely which can be dangerous for your phone. so please make sure you are using a custom Rom or stock 11g with this bootloader
Any way to flash one of these stock images. Rom itself. If you can't get into twrp? Check my post from last night in the root thread and you'll see what I'm on about.
Phone boots but system ui stops which keeps me from getting in. Lost twrp from recovery somehow. All I did was apply a then through substratum and it all went South from there.
Not hounding ya just thought I'd prefer over here and see what you been up to.
When I run step 1 in that root thread I get no hash match and something about with laf or lafbak not being present. Haven't fully fired up the pic too see if I can post the output from that here. (Honestly, was never that good with logs lol)
I'm curious though if flashing your laf (how in the heck it happened is beyond me) if it's possible through adb or lgup would put me back to right.
Sent from my XT1575 using Tapatalk
Ken C said:
Any way to flash one of these stock images. Rom itself. If you can't get into twrp? Check my post from last night in the root thread and you'll see what I'm on about.
Phone boots but system ui stops which keeps me from getting in. Lost twrp from recovery somehow. All I did was apply a then through substratum and it all went South from there.
Not hounding ya just thought I'd prefer over here and see what you been up to.
When I run step 1 in that root thread I get no hash match and something about with laf or lafbak not being present. Haven't fully fired up the pic too see if I can post the output from that here. (Honestly, was never that good with logs lol)
I'm curious though if flashing your laf (how in the heck it happened is beyond me) if it's possible through adb or lgup would put me back to right.
Click to expand...
Click to collapse
Do you still have root? if so you can extract the laf.img file from the StockLAF zip and use adb shell to push it to the dev blocks
put the laf.img file on your sdcard and rename it to laf.bin, and run these
adb shell
su
dd if=/sdcard/laf.bin of=/dev/block/bootdevice/by-name/laf
dd if=/sdcard/laf.bin of=/dev/block/bootdevice/by-name/lafbak
that will restore stock laf
weakNPCdotCom said:
Do you still have root? if so you can extract the laf.img file from the StockLAF zip and use adb shell to push it to the dev blocks
put the laf.img file in the folder with adb.exe, rename it to laf.bin, and run these
adb shell dd if=laf.bin of=/dev/block/bootdevice/by-name/laf
adb shell dd if=laf.bin of=/dev/block/bootdevice/by-name/lafbak
that will restore stock laf
Click to expand...
Click to collapse
Have to have root eh? So I'd need dl mode back to flash the kdz to get root but can't unless the kdz restores laf in the process which if it did this wouldn't be required I'm thinking.
Sorry man just thinking through things.
When y'all are putting in " /by-name/ " it would be h-872 right? Stupid question I know but I've never seen it mentioned straight out anywhere
Sent from my XT1575 using Tapatalk
Ken C said:
Have to have root eh? So I'd need dl mode back to flash the kdz to get root but can't unless the kdz restores laf in the process which if it did this wouldn't be required I'm thinking.
Sorry man just thinking through things.
When y'all are putting in " /by-name/ " it would be h-872 right? Stupid question I know but I've never seen it mentioned straight out anywhere
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Yeah you need to restore stock laf another way if you dont have root. Root is needed for ADB shell.
and no, /by-name/ is the actual folder name. I think it's a directory of symlinks, but i might be wrong. Basically it lets you access a partition or mount point by name. in this case the names of the mount points would be laf and lafbak
weakNPCdotCom said:
Yeah you need to restore stock laf another way if you dont have root. Root is needed for ADB shell.
and no, /by-name/ is the actual folder name. I think it's a directory of symlinks, but i might be wrong. Basically it lets you access a partition or mount point by name. in this case the names of the mount points would be laf and lafbak
Click to expand...
Click to collapse
Ok. Figured it was something like that. Always meant to ask somebody, just never did
Sent from my XT1575 using Tapatalk
weakNPCdotCom said:
FILE BREAKDOWN
The following Zips DO NOT include stock LAF.
You must flash the provided LAF separately if you wish to go back to stock DL mode
[/CENTER]
Bootloader: 11g Stock Bootloader ONLY
SysBoot: 11g Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 11g Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
Click to expand...
Click to collapse
Thank you for this weaknpc! This is really saving my a*s. Quick question. If I flash the FullStock version, will I have to unlock the bootloader again? I am using the AEX rom (have twrp 3.2.3 on laf and recovery I believe) and just want to go back to the full 11g firmware. If this works I wont even worry about flashing the laf partition (I would only do that for using LGUP+11g kdz).
ryanrod said:
Thank you for this weaknpc! This is really saving my a*s. Quick question. If I flash the FullStock version, will I have to unlock the bootloader again? I am using the AEX rom (have twrp 3.2.3 on laf and recovery I believe) and just want to go back to the full 11g firmware. If this works I wont even worry about flashing the laf partition (I would only do that for using LGUP+11g kdz).
Click to expand...
Click to collapse
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.
weakNPCdotCom said:
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.
Click to expand...
Click to collapse
Awesome. Yeah, I am going to give it a flash tomorrow morning. I do not think I will need the stock recovery at this time, but thanks for offering! I have been stuck with the whole twrp on LAF issue, not being able to use LGUP, and this just a godsend to get back to 11g. Thanks again! :good:
weakNPCdotCom said:
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.
Click to expand...
Click to collapse
IT WORKED!!!! THANK YOU :good::good: This phone is finally fully useable for me again!
I also saw your post about moving to the V30. Will be investigating that phone at some point.. You rock my friend.
ryanrod said:
IT WORKED!!!! THANK YOU :good::good: This phone is finally fully useable for me again!
I also saw your post about moving to the V30. Will be investigating that phone at some point.. You rock my friend.
Click to expand...
Click to collapse
You are most welcome! But important FYI, I discovered an issue in the original FullStock zip that was causing the laf partition to be flashed over with stock. I am posting an update to the project with another handy file for people with TWRP on recovery. If you downloaded FullStock prior to this morning, you will probably want to reboot to recovery and flash it.
Flashing h87211g_TWRPLAF.zip from custom recovery will put TWRP back on your LAF partition.
If I were to downgrade if able to, would that have a chance? I still am getting stuck in fastboot mode unless I'm hooked up to the pic and let lgup do it's thing.
It detects the device, does it's thing, reboots it and gives me a factory reset phone back just no dl mode.
It's not bricked yet lol.
Sent from my XT1575 using Tapatalk
weakNPCdotCom said:
You are most welcome! But important FYI, I discovered an issue in the original FullStock zip that was causing the laf partition to be flashed over with stock. I am posting an update to the project with another handy file for people with TWRP on recovery. If you downloaded FullStock prior to this morning, you will probably want to reboot to recovery and flash it.
Flashing h87211g_TWRPLAF.zip from custom recovery will put TWRP back on your LAF partition.
Click to expand...
Click to collapse
Ok, so the flash did not go exactly as planned, there was some issues getting into recovery. Let me give you a run down of what I did.
1. Boot into twrp recovery using a reboot app (requires root) from a working rom. (This is really the best way I can get into recovery besides using adb) 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the FullStock zip. 4. Flashed magisk and it was unsuccessful (it was not able to mount system or vendor partiton I believe).
I did not realize you need to reboot into recovery from twrp recovery, then flash magisk for it to work. I thought it may have flashed anyway. Needless to say I booted into the system and I had no magisk so no root. When trying to boot back into recovery using the hardware buttons, I could not get into recovery. It took me to the factory reset screen. Usually at this point if you select, yes factory reset the device, it would boot into twrp (I think this is some initial mask that lg puts on the recovery partition? ), but this time it was just a orbiting rainbow colored cicle animation. At this point I was saying "oh fu*#!". Then once that animation was over the phone began boot looping. I thought I bricked the phone at this point. Then I tried getting the phone into download mode by holding the volume up and inserting the usb cable. I got the download mode graphic, and then a second later, bam I was back into twrp! Lol. Crazy. I guess twrp was still on laf after flashing FullStock! So, I think that maybe your FullStock zip flashes the stock recovery partition and not the stock laf partition.
Now I was in twrp I was back in business. This time I did the steps correctly and magisk did flash, however I did not format data so now I was getting the encrypted data issue when booting into the system. Then on the third attempt I booted back into twrp using the download mode trick and this time I got it all right. 1. fully format data partition to clear encryption 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the fullstock zip. 4. reboot into recovery using the option in twrp 5. Flashed magisk successfully. 6. Reboot into system 7. Phone booted fine, no encryption issue, magisk manager sees magisk is installed and I have root.
So this is where I am now. The phone works fine and I have root. I am afraid to flash that laf zip with twrp becuase if I am correct, there is some specific hash that has to match the device when twrp is on laf. There are steps regarding this for the root method for the H872. Maybe it works on your phone, but I don't want to assume it will work on mine. I would not like to brick this thing, lol. Maybe I don't know what I am talking about...
Also, everything on this rom works great except for bluetooth audio! For some reason bluetooth audio is super super low even at max volume. When I had 11g before, it wasn't like this so I don't know what the heck happened! Through the headphones you get a prompt asking if you want to raise the volume above the limit but nothing like that for bluetooth. Does anyone know how to fix this? (Btw, I thought magisk viper4adroid might solve the issue but it does not work for me with this rom. I tried it and it just crashed system ui after reboot, almost got in a bootloop from it. Luckily I was able to disable the module after another boot)
So, if I can't fix bluetooth volume, I will be running this for a while, then I will flash the stock laf to get real download mode back and do a full kdz flash using lgup so I am truly back to stock. Then I will follow the H872 root process from the ground up, etc.
Either way thanks for this npc. At least I am able to have 11g! Thanks for your hard work. :good:
ryanrod said:
Ok, so the flash did not go exactly as planned, there was some issues getting into recovery. Let me give you a run down of what I did.
1. Boot into twrp recovery using a reboot app (requires root) from a working rom. (This is really the best way I can get into recovery besides using adb) 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the FullStock zip. 4. Flashed magisk and it was unsuccessful (it was not able to mount system or vendor partiton I believe).
I did not realize you need to reboot into recovery from twrp recovery, then flash magisk for it to work. I thought it may have flashed anyway. Needless to say I booted into the system and I had no magisk so no root. When trying to boot back into recovery using the hardware buttons, I could not get into recovery. It took me to the factory reset screen. Usually at this point if you select, yes factory reset the device, it would boot into twrp (I think this is some initial mask that lg puts on the recovery partition? ), but this time it was just a orbiting rainbow colored cicle animation. At this point I was saying "oh fu*#!". Then once that animation was over the phone began boot looping. I thought I bricked the phone at this point. Then I tried getting the phone into download mode by holding the volume up and inserting the usb cable. I got the download mode graphic, and then a second later, bam I was back into twrp! Lol. Crazy. I guess twrp was still on laf after flashing FullStock! So, I think that maybe your FullStock zip flashes the stock recovery partition and not the stock laf partition.
Now I was in twrp I was back in business. This time I did the steps correctly and magisk did flash, however I did not format data so now I was getting the encrypted data issue when booting into the system. Then on the third attempt I booted back into twrp using the download mode trick and this time I got it all right. 1. fully format data partition to clear encryption 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the fullstock zip. 4. reboot into recovery using the option in twrp 5. Flashed magisk successfully. 6. Reboot into system 7. Phone booted fine, no encryption issue, magisk manager sees magisk is installed and I have root.
So this is where I am now. The phone works fine and I have root. I am afraid to flash that laf zip with twrp becuase if I am correct, there is some specific hash that has to match the device when twrp is on laf. There are steps regarding this for the root method for the H872. Maybe it works on your phone, but I don't want to assume it will work on mine. I would not like to brick this thing, lol. Maybe I don't know what I am talking about...
Also, everything on this rom works great except for bluetooth audio! For some reason bluetooth audio is super super low even at max volume. When I had 11g before, it wasn't like this so I don't know what the heck happened! Through the headphones you get a prompt asking if you want to raise the volume above the limit but nothing like that for bluetooth. Does anyone know how to fix this? (Btw, I thought magisk viper4adroid might solve the issue but it does not work for me with this rom. I tried it and it just crashed system ui after reboot, almost got in a bootloop from it. Luckily I was able to disable the module after another boot)
So, if I can't fix bluetooth volume, I will be running this for a while, then I will flash the stock laf to get real download mode back and do a full kdz flash using lgup so I am truly back to stock. Then I will follow the H872 root process from the ground up, etc.
Either way thanks for this npc. At least I am able to have 11g! Thanks for your hard work. :good:
Click to expand...
Click to collapse
I'm sorry that you had a little trouble. It actually makes sense that you needed to format data. I will update the instructions to start things off with that step.
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm glad you still had TWRP on laf. Maybe I was looking at an old updater-script. I do know, however, that I removed the recovery flash from the rom so that never should have been replaced. What I think might have happened with you is the Stock firmware's recovery repair feature. Since Magisk didnt flash correctly and you booted to OS, it would have tried to repair stock recovery.
As for the TWRP LAF zip, it is an exact image of the LAF partition after it was processed by @runningnak3d's root procedure. So there shouldnt be any checksum issues at all. It should be totally safe.
The bluetooth thing is probably the most puzzling to me. I extracted all of the images in these roms directly from the stock KDZ. Your system should be a mirror image of any device flashed with LGUP.
Try flashing the SysBoot ROM on top of what you have now. The file structure in that rom is different. Instead of extracting a system image to your system block (the way fullstock does) it actually flashes all of the individual system directories to their designated blocks. I have a feeling that it may fix your issue.
Thank you very much for the information. If you end up doing anything else let me know how it turns out. If I can help you not have to flash the KDZ then I'll be happy. That was my main goal in creating these packages.
weakNPCdotCom said:
I'm sorry that you had a little trouble. It actually makes sense that you needed to format data. I will update the instructions to start things off with that step.
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm glad you still had TWRP on laf. Maybe I was looking at an old updater-script. I do know, however, that I removed the recovery flash from the rom so that never should have been replaced. What I think might have happened with you is the Stock firmware's recovery repair feature. Since Magisk didnt flash correctly and you booted to OS, it would have tried to repair stock recovery.
As for the TWRP LAF zip, it is an exact image of the LAF partition after it was processed by @runningnak3d's root procedure. So there shouldnt be any checksum issues at all. It should be totally safe.
The bluetooth thing is probably the most puzzling to me. I extracted all of the images in these roms directly from the stock KDZ. Your system should be a mirror image of any device flashed with LGUP.
Try flashing the SysBoot ROM on top of what you have now. The file structure in that rom is different. Instead of extracting a system image to your system block (the way fullstock does) it actually flashes all of the individual system directories to their designated blocks. I have a feeling that it may fix your issue.
Thank you very much for the information. If you end up doing anything else let me know how it turns out. If I can help you not have to flash the KDZ then I'll be happy. That was my main goal in creating these packages.
Click to expand...
Click to collapse
Ahh yes this makes sense. Maybe it was a stock recovery repair due to magisk failure as you mentioned? I still don't understand why with these LG phones (ever since the G3 I think), when you boot into recovery using the hardware buttons, it asks if you want to factory reset the device. Then if you say yes, it doesn't reset/format anything, and it boots right into twrp recovery after that. So weird. I can boot directly into recovery just fine from a reboot app or adb from a running system without getting that factory reset screen...
I'm sure your laf zip with twrp works for the reasons you mention. Luckily I don't have to find out since my laf partition is fine and still has twrp!
Regarding bluetooth, I will give the sysboot flash a try and update you with the results. First I want to wait until my backup phone is running again. I bent the sim pins on the backup phone due to those ****ty plastic adapters that catch the pins (an old E980 w/ the larger sim size) so I ordered another sim reader to fix that. I also read in some forums that wiping cache and dalvik cache resolved others bluetooth issues with the G6. I will try that too.
Either way, I will update soon. I am happy to share my notes as I really appreciate the help!
@weakNPCdotCom
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm rooted and running an old version of aex. I'm still getting the encryption message anytime I try anything without that rom. These last two posts. When you talk about formatting your saying in twrp correct? Or that forced format you can do with the buttons?
Basic point is I'd like to get rid of that encryption message and it looks like your instructions take place after we achieve root. I'm wondering if I should just kdz to 11g and root from there. Or would just flashing your full stock zip do it? I seem to be the only one having such an issue with it so I'm figuring I'm missing something somewhere that y'all are doing or whatever that's getting by me.
Sent from my LG-H872 using Tapatalk
Ken C said:
@weakNPCdotCom
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm rooted and running an old version of aex. I'm still getting the encryption message anytime I try anything without that rom. These last two posts. When you talk about formatting your saying in twrp correct? Or that forced format you can do with the buttons?
Basic point is I'd like to get rid of that encryption message and it looks like your instructions take place after we achieve root. I'm wondering if I should just kdz to 11g and root from there. Or would just flashing your full stock zip do it? I seem to be the only one having such an issue with it so I'm figuring I'm missing something somewhere that y'all are doing or whatever that's getting by me.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.
weakNPCdotCom said:
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.
Click to expand...
Click to collapse
weakNPCdotCom said:
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.
Click to expand...
Click to collapse
Yes that's the message I get. So your saying not to worry about it for the moment? I only see it regularly on a stock rom when going into recovery not aex.
I just wanted to make sure. With the mess I been going through.
So, I can flash this stock build you have and if I wanted normal download back flash the laf zip and I'll have DL mode on laf, twrp on recovery and everything should Mount correctly and all that?
And if I go to flash something custom FP will work? I know I'm a pain I just want to "know" my setup isn't weird somehow. Probably over thinking it, but I think I'm good, except that when I rooted I was getting that message off & on, on the stock build of 20a. I'm hoping that running this build I can get that worked out. Maybe that deal is a 20a thing? Reading through the root thread it seemed to happen less to people on a lower numbered build and it would stop after the format.
I can make backups Burt I've yet to try to restore one.
Sent from my LG-H872 using Tapatalk
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.