Database Develop

[Q] How to upgrade bootloader to 10.26.1.18 ?

Hi,
I bought today a 701T ww, with bootloader version 10.26.1.7.
I've been able to unlock the bootloader, root the rom, and install a custom CWM (now 6.0.4.6).
I installed the custom rom CROMi-X 6.0b2
But I'm now unable to upgrade the bootloader to 10.26.1.18.
I reverted to stock 10.27.1.7 rom thanks to the nandroid backup I made prior CROM install, I've tried downloading the official update package from Asus, which is supposed to be the only way to upgrade the bootloader. I've put the UL-K00C-WW-10.26.1.18-user.zip file on the root of a MicroSD, the tablet recognized the update file, and rebooted to install it. Problem is that, after reboot, the tablet enters in the CWM with the following error :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Off course if I try "Yes - install untrusted.zip" it doesn't rework, and the tablet reboots ....
many thanks if you can help !

Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]

berndblb said:
Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]
Click to expand...
Click to collapse
Hi Berndblb, thanks for your reply.
Toggling the signature verification didn't help, I've already tried that.
I didn't miss this, but as I've never been able to upgrade the bootloader thanks to the official update, I thought that with CROMI the bootloader would be upgraded too. I noticed that was'nt the case, that's why I restored my nandroid backup to revert to the stock 10.26.1.7.
Now I'm in 10.26.1.7, and precisely want to upgrade the bootloader to be able to install CROMI with the correct bootloader. Therefore my question.
Would a "fastboot flash boot boot.img" using the boot.img file included in the official asus 10.28.1.18 package be a good idea ?

Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:

usoska said:
Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:
Click to expand...
Click to collapse
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?

Calp said:
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?
Click to expand...
Click to collapse
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go

berndblb said:
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go
Click to expand...
Click to collapse
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!

Calp said:
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!
Click to expand...
Click to collapse
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.

berndblb said:
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.
Click to expand...
Click to collapse
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!

Calp said:
THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
You're very welcome !
That looks correct.

Calp said:
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
WooHoo! excelent. Glad you got everything all sorted out.

Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.

sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
2 days, how dare you. You should be concentrating on b4 and only b4.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
Wow, you're crazy! I really appreciate your help, mate.
For anyone else needing to do these stips, here's the download link for the stock recovery which you have to flash first: http://droidbasement.com/db-blog/?p=3210 ( i also tried a different one but only this one did work in the end)
Also, thanks a lot for the ROM, sdbags. I've been using it for a couple of hours now and it seems to work like a charm. Great work, mate!
Sent from my K00C using xda app-developers app

How can I tell which bootloader (BL) and firmware (FW) I run currently? When I hold power/volume down, the top of the screen says user BL released by "US_epad-10.26.1.7". When I boot into Android and go into settings -> about -> software, I see Build number "JSS15J.US_epad-10.26.1.18". Is the 1.18 the firmware (FW) version?
Finally, is there a way to upgrade BL/FW to ...1.18 version without using an external SD card?

US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card

Thanks. Just to verify, you don't think doing "fastboot flash boot boot.img" will work? (using boot.img from UL-K00C-US-10.26.1.18-user.zip).
Also, by SD-card method, are you talking about the rename “WW_10_26_1_18_SDupdate” to “T4_SDUPDATE.zip" process etc.? It seems that I have the US SKU, and not sure if this would work, being that it mentions WW in the file name.
Sleeepy2 said:
US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card
Click to expand...
Click to collapse

I am no expert but I am pretty sure that the fastboot method doesn't work as there have been several people with the wrong bootloader issue and and the only way to do it was with the official update.
I am not sure about using the WW file or not. I am in canada and I used the other file to update and that did the bootloader also. With the status your in now I am not sure if the US one will work or not. I would try the US one first and then if not go with the steps from pershoot
http://forum.xda-developers.com/showpost.php?p=52187532&postcount=87

Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.

MilesWilford said:
Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.
Click to expand...
Click to collapse
It's still there, try this link
http://droidbasement.com/asus/tf701t/stock/

Does XperiFIX work with 47.1.A.12.145 aka the April patch?

I want to unlock my bootloader and try a custom ROM, but I don't want to get stuck without a camera. I remember reading somewhere that XperiFIX would need to be updated for the most recent patch to be compatible.
Anyone tried it?

Pickx said:
I want to unlock my bootloader and try a custom ROM, but I don't want to get stuck without a camera. I remember reading somewhere that XperiFIX would need to be updated for the most recent patch to be compatible.
Anyone tried it?
Click to expand...
Click to collapse
Have you thought of asking in the Xperiafix thread ?

Didgesteve said:
Have you thought of asking in the Xperiafix thread ?
Click to expand...
Click to collapse
No, because nobody in that thread has answered that question for the March update either.

Pickx said:
No, because nobody in that thread has answered that question for the March update either.
Click to expand...
Click to collapse
Well if no one has answered then it's probably a no then

I patched XperiFix myself to use it with the .119 FW and it works.
Currently i'm running FW .119 with XperiFix DRM-patch and TWRP from 05.03.18.
I haven't installed the .145 FW atm, because I couldn't boot into Android with TWRP from 05.03.18.
But I read that TWRP came out for the april patch, so I will try to update at the weekend and check again with XperiFix.
Proof FW .119:
Phone Settings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone Security Settings:
XperiFix:
Edit - After Upgrade .145:
I used the April TWRP and I could boot into Android and TWRP.
Phone Settings:
XperiFix:

Thank you very much! So what is the process like to do this with an "unsupported" firmware? How do I patch this for .145, or do I even need to do anything special other than using a newer version of TWRP?

Raz0Rfail said:
I patched XperiFix myself to use it with the .119 FW and it works.
Currently i'm running FW .119 with XperiFix DRM-patch and TWRP from 05.03.18.
[...]
Click to expand...
Click to collapse
Thank you very much! So what is the process like to do this with an "unsupported" firmware? How do I patch this for .145, or do I even need to do anything special other than using a newer version of TWRP?

Raz0Rfail said:
Edit - After Upgrade .145:
I used the April TWRP and I could boot into Android and TWRP.
Click to expand...
Click to collapse
Is upgrading the XperiFix just as simple as replacing the TWRP in the XperiFix folder with the most recent one? If not, what else is required? If so, what do I do with the xz1c-twrptemp.img file? I'm assuming I rename the downloaded TWRP file to xz1c-twrp.img.
It's mentioned at https://www.xperifix.com/2018/03/06/update-2-2-xz1-and-xz1-compact-update/#comment-40 that a guide for this will be released but I haven't found it yet, and given that it looks above like you've already done this I'd be most appreciative if you'd share the process. Thanks!

nataelj said:
Is upgrading the XperiFix just as simple as replacing the TWRP in the XperiFix folder with the most recent one? If not, what else is required? If so, what do I do with the xz1c-twrptemp.img file? I'm assuming I rename the downloaded TWRP file to xz1c-twrp.img.
It's mentioned at https://www.xperifix.com/2018/03/06/update-2-2-xz1-and-xz1-compact-update/#comment-40 that a guide for this will be released but I haven't found it yet, and given that it looks above like you've already done this I'd be most appreciative if you'd share the process. Thanks!
Click to expand...
Click to collapse
I wrote you a pm to modify xperifix.
You need only the current kernel for the fw installed. It comes with flashing firmware.
The temp TWRP inside the data folder is only get booted from the XperiFix tool.
The XperiFix tool boot this temp TWRP to change the libs, install magisk and so on.
If you change the TWRP temp through another TWRP image, all commands to flash magisk etc. Won't work, so for the work is the temp TWRP required.
Important is that you use the correct kernel before you use xperifix, because this kernel get flashed and TWRP temp got booted as recovery, so nothing changes what you have currently installed as boot or recovery image.
So the second TWRP I let It as it be. After flashing the XperiFix files and the phone restart correctly, I boot into bootloader and flash the new TWRP recovery and then I reboot into TWRP to check if all files shown in /sdcard are correctly named. If the names are correct, you use the right TWRP to the installed security patch from Google. If you have only cryptic names inside /sdcard you have the wrong TWRP to the installed security patch. If it's so that the wrong TWRP is installed download the correct one and flash the recovery again.
Edit: sorry I forget I wrote am pm to pickxx.
I send it to you too.
I can't post it here, because it's not save and if the owner find out, he would fix it, that patching is not possible.

Raz0Rfail said:
I wrote you a pm to modify xperifix.
I can't post it here, because it's not save and if the owner find out, he would fix it, that patching is not possible.
Click to expand...
Click to collapse
I still haven't gotten a PM.
Also, the link I posted above was one to the creator of Xperifix (@sToRm// (Heiko Frenzel) on this forum) mentioning that he was going to publish a guide on how to do this update on the XperiFIX website, so I think you'd probably be fine to publish that yourself. Far from causing him to fix it, I think you'd just save him some work. If anyone knows otherwise please feel free to correct me.
Finally, the above discussion is helpful in clarifying what to do (or not to do) with the temp, but I'm still not sure what I need to replace or update in the XperiFIX to enable it to work on the most recent firmware.

nataelj said:
I still haven't gotten a PM.
Also, the link I posted above was one to the creator of Xperifix (@sToRm// (Heiko Frenzel) on this forum) mentioning that he was going to publish a guide on how to do this update on the XperiFIX website, so I think you'd probably be fine to publish that yourself. Far from causing him to fix it, I think you'd just save him some work. If anyone knows otherwise please feel free to correct me.
Finally, the above discussion is helpful in clarifying what to do (or not to do) with the temp, but I'm still not sure what I need to replace or update in the XperiFIX to enable it to work on the most recent firmware.
Click to expand...
Click to collapse
I couldn't share the PM, because my PM settings wasn't configured to save it in send mails.
I will write a Tutorial after my work 19:00 (UTC +1), how to patch XperiFix.exe to use it with the new firmwares. I won't share my patched .exe files. If you want it, you have to follow the tut.
You should leave the files in XperiFix folder as it currently is.
You only need TWRP for current Security Patch if you want to change files inside /sdcard, flash files from /sdcard, or create a working Nandroid Backup.

Raz0Rfail said:
I couldn't share the PM, because my PM settings wasn't configured to save it in send mails.
I will write a Tutorial after my work 19:00 (UTC +1), how to patch XperiFix.exe to use it with the new firmwares. I won't share my patched .exe files. If you want it, you have to follow the tut.
You should leave the files in XperiFix folder as it currently is.
You only need TWRP for current Security Patch if you want to change files inside /sdcard, flash files from /sdcard, or create a working Nandroid Backup.
Click to expand...
Click to collapse
Cool; will look forward to the details!
To be clear though, I have an unpatched, unrooted device that's on the most recent firmware. I'm not just updating to access the sdcard and create backups, I'm updating to crack the phone in the first place (without having to do a downgrade, which I haven't worked out the full process for yet). Not sure if that changes anything or not but figured I'd mention in case.

I had .34 firmware, used Xperifix, than upgraded to .119 and indeed it stopped working.

This is a Tutorial about patching XperiFix from Storm// to use it with new Firmwares.
It's not officially provided or allowed by him!
At first I have to be clear at the following points:
The Patch has the same requirements as XperiFix itself (without the old firmwares)
Your Device must have a unlocked bootloader.
With unlocking your bootloader, you will loose your DRM Keys for this phone forever!
The XperiFix is only simulating DRM-Keys, so the camera and other things can be used again.
You should have installed the correct drivers for bootloader and USB-Debugging
Get Software
Download and install XperiFix first on your PC:
https://www.xperifix.com/download/xperifix-latest/ Version2.2
For patching XperiFix download DnSpy on Github(https://github.com/0xd4d/dnSpy/releases/tag/v4.5.3)
Get TWRP for your FW: https://androidfilehost.com/?w=files&flid=232371 (current for .145 FW is twrp-3.2.1-0-lilac-10-patchlevel-2018-04-05.img)
Get and install Firmware
At first you need the Current firmware on your Device.
I use FlashTool to download and flash the Firmware: http://www.flashtool.net/downloads.php
Download new XZ1c-Firmware trough XperiFirm inside FlashTool.
After the download close XperiFirm to create the new FTF-file from FlashTool automaticly.
In FlashTool click Flash --> Flashmode --> Select new Firmware (don't change anything at wiping or excluding), execute the flash.
After flash reboot phone into system, it needs time just wait!
If reboot is from Android needed to finish upgrade, let the phone do it.
Patch XperiFix
Extract DnSpy from zip-file.
open DnSpy.exe, Open XperiFix.exe under File --> Open (C:\XperiFix\XperiFix.exe).
In "Assembly Explorer" switch to XperiFix (2.2.0.0) --> XperiFix.exe--> (XperiFix (Yellow Color) --> Form1 in tree structure.
Right Click on public Form1(), "edit Method".
In the new Window, you are able to change the source code.
replace the following variable
this.validfw = new List<string>
{
"47.1.A.8.49",
"47.1.A.12.34",
"47.1.A.12.75"
};
with
this.validfw = new List<string>
{
"47.1.A.8.49",
"47.1.A.12.34",
"47.1.A.12.75",
"47.1.A.12.119",
"47.1.A.12.145"
};
Click on the Button compile. You will see the changes in the main Window from DnSpy.
Click on File -> Save Module --> enter name, save the .exe-file.
Start the patched XperiFix.exe
reboot phone into Bootloader and connect it to your pc, because there XperiFIX can detect it without crashing.
If everything was correct patched with DnSpy you should be allowed to use it.
Set the hook and click on "FIX my Device!" then let XperiFIX do it's work.
if you see magisk and XperiFIX get flashed inside twrp everything is fine.
if the phone restarts into system, reboot phone into bootloader to flash your twrp recovery.
Flash Recovery
reboot phone into Bootloader and connect it to your pc.
"Path to fastboot\fastboot.exe" flash recovery "Path-to-Twrp\twrp-3.2.1-0-lilac-10-patchlevel-2018-04-05.img"
"Path to fastboot\fastboot.exe" reboot
Phone should start into android, first time needs time because it has wiped dalvic and cache.
In Android take a photo and check album if there is a green picture or not (shouldn't be).
You can start telephone APP call *#*#SERVICE#*#* or *#*#7378423#*#* and inside the Service Menu switch to "service tests" and there to Security.
Should be near identically to mine, some Thread entries before.
You have now the new Firmware and XperiFIX installed.
Afterwards I'm using root Explorer and Titanium Backup to clean the Bloatware which come from installing the new Firmware.
If something is not clear or detailed, please write it to me.

Raz0Rfail said:
This is a Tutorial about patching XperiFix from Storm//
Click to expand...
Click to collapse
Thank you so much; that's amazing!!!
One note; you mention manually flashing the new firmware with flashtool. Is there any difference between this approach and using a device that has been updated to that firmware via OTA update from Sony?
Related to that, where does the new TWRP connect in? I see that you download it, and later you mention that it gets loaded; presumably it needs to get saved somewhere specific in XperiFIX or linked to via the dnSpy changes?
I'm concerned because it sounds like everyone else here is upgrading an already flashed system and can re-flash the new twrp from the old one. I've got a fresh OTA rom I'm patching and rooting so it doesn't yet have twrp. As XperiFIX installs TWRP I assumed I'd have to link it to the correct twrp file somehow (perhaps replace the one in the XperiFIX file structure?), but I don't see that here. Something additional required in this case?

nataelj said:
Thank you so much; that's amazing!!!
One note; you mention manually flashing the new firmware with flashtool. Is there any difference between this approach and using a device that has been updated to that firmware via OTA update from Sony?
You only need the Firmware, how you get to the Firmware is secondary. But if you unlocked your bootloader you can't install the new OTAs.
Related to that, where does the new TWRP connect in? I see that you download it, and later you mention that it gets loaded; presumably it needs to get saved somewhere specific in XperiFIX or linked to via the dnSpy changes?
The TWRP recovery is only in your phone. XperiFix pushes it's own twrp trough the process.
The XperiFix TWRP is located at C:\XperiFIX\DATA\TWRP\xz1c-twrp.img.
But if you flash your own recovery as in step 5 described, the xperiFix twrp is obselete.
I'm concerned because it sounds like everyone else here is upgrading an already flashed system and can re-flash the new twrp from the old one. I've got a fresh OTA rom I'm patching and rooting so it doesn't yet have twrp. As XperiFIX installs TWRP I assumed I'd have to link it to the correct twrp file somehow (perhaps replace the one in the XperiFIX file structure?), but I don't see that here. Something additional required in this case?
I understand your concern. You will be able to forget about the OTA updates as soon as you unlock the bootloader.
My recommendation is to wait as soon as a new firmware is out until TWRP has been adapted.
Because I had to redo my mobile 3 times because I didn't wait and couldn't flash XperiFix.
This means you need to download 2.5 GB+- for each update, patch XperiFix, and start the process from the beginning.
This is the price to use the phone with root and Magisk.
Translated with www.DeepL.com/Translator
Click to expand...
Click to collapse
Do you understand better now?

@Raz0Rfail everything worked. I had to wipe and install janjan's ROM because magisk wasn't working after XperiFIX, but other that your guide worked perfectly. Thanks again.

Raz0Rfail said:
Do you understand better now?
Click to expand...
Click to collapse
Seems to have failed for me. I now get green camera images and have no root; something went wrong somewhere... :-/

Try using xperifix again. Boot into bootloader, plug phone into pc, start modified xperifix, execute it again. And check if in TWRP is flashing magisk and xperifix kernel.
Did you flash recovery with fastboot flash recovery or fastboot flash boot?
If you use the second variant, it is clear that this was your mistake, because magisk and xperifix kernel is patched into the installed kernel.

Raz0Rfail said:
Try using xperifix again. Boot into bootloader, plug phone into pc, start modified xperifix, execute it again. And check if in TWRP is flashing magisk and xperifix kernel.
Did you flash recovery with fastboot flash recovery or fastboot flash boot?
If you use the second variant, it is clear that this was your mistake, because magisk and xperifix kernel is patched into the installed kernel.
Click to expand...
Click to collapse
Hmm, maybe I could use more clarification on that step then. I actually just went into TWRP and then hit install and pointed it to install the new file (copied to the phone) as a new recovery. Would that not work? If not, is the above meant to say I should use flashtool and flash that new TRWP with it?
EDIT: Hey!!! Something worked! I checked the logs and saw some failed file copies and permission errors so I played around with it some and reran as you suggested and it seems to have worked now! I'm up and running and my photos are no longer green!!
I am not seeing Magisk as an app though, and when I try and open Titanium Backup it just cycles while looking for SU and Busybox. If I get the Root Checker app it says not rooted too even though it finds an Su; does that actually mean not rooted or does Magisk work in some other way to give permission?

Q: Howto get my X4 to a working LOS setup after having bricked it and used blankflash

Hello,
I few weeks ago I got myself a Moto X4 XT1900-7 after my old mobile suffered a broken display.
I unloaded the boot loader and proceeded to install LOS right after getting the phone and getting it unwrapped from its shipping box.
This is now my 4th mobile were I installed LOS or Cyanogenmod and out of hubris I did not create a backup before the install.
I followed the instructions on the LOS website for installing and ended up with a bricked X4 (https://wiki.lineageos.org/devices/payton/install).
Now after xmas I investigated further and was able to use the blank flash as provided here (https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529/page6) to get to the state were the mobile is at a fastboot screen after the blank flash.
https://imagebin.ca/v/4RUBbOmjIGs9
At this point I can fastboot boot twrp (https://dl.twrp.me/payton/)
fastboot boot twrp-3.2.3-1-payton.img
to get into a twrp recovery.
But installing a LOS install package (https://download.lineageos.org/payton) and rebooting only gets me back to the state of the bricked phone, so I must be missing something.
So my question is how do I proceed to get the phone back to a working state ? The LOS install instructions to not work at this point - I tried and after installing LOS I just get back to the state were the mobile is bricked and I have to use blank flash again.
My end goal would be a working LOS installation.
Thanks
BR

Hey let's compare build numbers and kernel info, Android version etc. Maybe ours differ from others on here. Since I had a similar experience as you in that flashing a ROM bricked my phone, maybe we'll find a commonality that others here don't have...
I could not get blankflash to work for me. The phone showed in device manager the way the instructions said it should with the port number. I downloaded stock rom unzipped it to my address folder and unzipped the blankflash package to the same folder. I would run the .bat file but it errored out everytime. Luckily I was able to bring the phone back and Fry's just accepted it and gave me another one .
I don't want to end up with another bricked phone. Out of curiousity was yours freezing up after rooting, but before the rom installation.?
---------- Post added at 02:52 AM ---------- Previous post was at 02:36 AM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did you try following the guide in the ROM thread (https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265)?
I bricked my device on the first attempt while following the LOS site install instructions, but after getting it back to stock I followed the ROM thread instructions instead (with a minor adjustment).
First things first, if you haven't gotten back to working bootable image on your device, boot to the bootloader and follow this thread's instructions. I am not 100% sure this is necessary, but I don't have another device to test with atm. One thing to note, make sure to get your variant's stock 8/8.1 Firmware. I have an XT1900-1 variant while that thread features links for the XT1900-6 variant.
Next follow these instructions:
erfanoabdi said:
How to install:
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Click to expand...
Click to collapse
Following those instructions should get you a working LOS install. Make sure to get the correct Copy Partitions Zip for your variant.
All that said, I diverged a bit at the start and end:
Before starting TWRP, I ran the Copy Partitions Zip flash_all.bat/sh at the bootloader.
Before letting the system start, I ran the flash_all.bat/sh at the bootloader again.
For the first change, I couldn't get TWRP to run the ZIP, so I extracted it and realized the bat/sh scripts were fastboot flashing the contents of the ZIP. The second deviation is because my system wouldn't make it past the boot logo screen and when I loaded TWRP, it was giving errors about firmware issues in the terminal.
After performing all that, your LOS should boot and be configurable. Your experience may be different to the difference in variant.

Ty for the pointer to the ROM thread, I am reading through that.
How do the different variants of the X4, i.e. XT1900-1 through XT1900-7 (that is the one I do own), differ ? And connected to that question - can I flash a stock image from a different variant (maybe a XT1900-1) than my XT1900-7 to my XT1900-7 without causing further problems ?
Also what is the purpose of Copy Partitions Zip ? What does it do ? I downloaded the zip file and I understand that I shall install it via adb sideload or from the sd card when I have booted the twrp recovery from fastboot. Do I need to modify anything in copy partitions zip specifically to match my XT1900-7 ? Or does Copy Partitions Zip work the same on all variants of the moto X4 ?
Ty
BR

I'll be honest, a more experienced member would have to answer that because I don't really know how they differ. You can try to push a XT1900-1 to -7, but I wouldn't recommend that. I have two versions of this device, an A1 and Retail. The A1 version is generally Fi related and I accidentally loaded the firmware for the Fi version on my Retail and now it is giving me issues with my carrier (I think this is the cause, but am not 100% sure).
From what is said by TadMSTR in the thread, the Copy Partitions Zip is for duplicating partitions between the two OS slots:
TadMSTR said:
The Moto X4 uses the A/B slot setup that Google introduced with the Pixel. However, Motorola decided to only setup the partitions in slot A. The copy partition zip copies the partitions from slot A into slot B. This allows you to now flash/install a ROM into slot B. Without flashing copy partitions zip I'm not sure you would even be able to change to slot B. You definitely would not be able to flash anything to it.
ROMs should include everything needed to boot into the OS. Lineage includes boot, system, and recovery. If you don't want to use Lineage recovery then you need to flash the TWRP zip after flashing Lineage, even after just flashing an update. So technically all you need is the Lineage zip to have a fully functioning Android OS. However, you will most likely also want gapps. You should be good following the tutorial in the beginning of this thread. For applying updates see my post above.
Click to expand...
Click to collapse
You won't be sideloading that zip. As I stated before, it's a bunch of fastboot commands in the a bat/sh file with support files included. You will be running while at the bootloader according to Skeeterdrums in the thread:
Skeeterdrums said:
See the previous post, you need to unzip and run the flash_all bat/sh file while connected to your phone in the bootloader. Those scripts run a series of fastboot commands to get everything copied over and installed.
Click to expand...
Click to collapse
You don't need to modify the zip, it should work on your variant according to posts in the thread.

erukami said:
I'll be honest, a more experienced member would have to answer that because I don't really know how they differ. You can try to push a XT1900-1 to -7, but I wouldn't recommend that. I have two versions of this device, an A1 and Retail. The A1 version is generally Fi related and I accidentally loaded the firmware for the Fi version on my Retail and now it is giving me issues with my carrier (I think this is the cause, but am not 100% sure).
From what is said by TadMSTR in the thread, the Copy Partitions Zip is for duplicating partitions between the two OS slots:
You won't be sideloading that zip. As I stated before, it's a bunch of fastboot commands in the a bat/sh file with support files included. You will be running while at the bootloader according to Skeeterdrums in the thread:
You don't need to modify the zip, it should work on your variant according to posts in the thread.
Click to expand...
Click to collapse
@erukami I have the Android One variant with the Fi firmware. Only had data when using my Verizon work sim. Flashing the US Retail firmware loaded the correct radios and I was able to get full service on Verizon. Custom roms typically do not include the radio files. Restore the US Retail firmware and you should be fine. Can flash any custom rom after that.
I may have misspoke a bit about the copy partitions firmware. It doesn't setup the partitions as they are already there. It merely copies what is on A to B and vice versa, depending on which slot you are currently on. Though I think when coming completely from stock the B slot is "empty" as Moto didn't bother with it. Not sure if you need to bother flashing the zip when restoring to stock but I did anyway. Fastboot was only flashing to slot A. Maybe that can be tweaked with the flash-all.bat file.
@Afongo You should restore the stock firmware for your variant and start over. Making sure to flash copy partitions zip in TWRP before flashing LOS. When I restored stock firmware I made sure slot A was the active slot. After the restore let the phone boot up into stock. Reboot to the bootloader then boot TWRP. Flash copy partitions zip. Flash Lineage and then flash TWRP zip. Reboot to recovery. Flash gapps and Magisk (if you want root). Factory reset or wipe data/cache as needed before booting into Lineage the first time.
You need to reboot back into recovery after flashing a ROM due to the A/B slot logic. Flashing a ROM automatically changes the active slot so in order to flash anything after the ROM, with the exception of TWRP, you need to reboot to recovery to continue. Due note that LOS overwrites TWRP recovery on a fresh install and any updates. You'll need to boot TWRP from the bootloader if you need to get back in TWRP or you can just use LOS recovery.

Ty all for the provided info. I understand more now than before.
I am still looking for a firmware for a XT1900-7, does anybody know the filename so that I can google for it ?
For example I downloaded a PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, but how do I know for which variant of the Moto X4 that file is ? What is the naming scheme ?
Ty
BR

Afongo said:
Ty all for the provided info. I understand more now than before.
I am still looking for a firmware for a XT1900-7, does anybody know the filename so that I can google for it ?
For example I downloaded a PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, but how do I know for which variant of the Moto X4 that file is ? What is the naming scheme ?
Ty
BR
Click to expand...
Click to collapse
You have the correct and most recent Android 8.1 firmware for you device (PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip). This works for all regions. The firmware does not determine the region. The xt1900-7 is 'reteu'.

Look here for Pie ROM.

[RESOLVED] Bricked after flashing firmware for Pie, stuck in md5 checksum bootloop

Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.

bump pls
even bad news is appreciated

Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?

Javellinh said:
Even fastboot cant saw your device thru "fastboot devices"? Do your ADB drivers up-to-date?
Click to expand...
Click to collapse
Thank you for answering.
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.

Hmm.. does phone in TWRP works like USB storage?

Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

swumo said:
Phone fails to boot into recovery.
I flashed TWRP but it always boots into the failed md5 checksum anyway.
Recovery doesn't work.
Click to expand...
Click to collapse
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok

swumo said:
Worth noting is that TWRP flashing causes the recovery: ok message to also read as recovery:failed.
Flashing the stock recovery that came with the unbrick tool using fastboot makes it recovery: ok
Click to expand...
Click to collapse
you can boot to stock recovery?

vinoxflame said:
you can boot to stock recovery?
Click to expand...
Click to collapse
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.

swumo said:
It won't boot into any recovery, stock or otherwise. Only brings up the screen pictured above.
EDIT: By "stock recovery" I mean whatever the unbrick tool had flashed into the phone using the MSMDownloader utility.
The version of OOS included in the tool is mentioned as 3.2 or some dated system. Maybe a more recent recovery might work?
I can't find a standalone, recent stock recovery image. I'd flash one if I found it.
Click to expand...
Click to collapse
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

vinoxflame said:
are you using op3 or 3t?
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
I'm using a OP3T.
The link you provided points to a similar guide to the one I used. https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-tool-3t-unbrick-data-babloo-t3737791
I've already performed these steps, and the md5 problem happened after the process mentioned was completed.

swumo said:
Fastboot can see and use the device. Flashing is possible through it.
ADB cannot. I'm not sure if it's the latest version on my PC, but I recently had the phone connected to a different PC with a recent ADB installation and the results were the same. ADB doesn't see the phone.
Click to expand...
Click to collapse
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.

redpoint73 said:
Fastboot and adb will never work at the same time, by definition. If Fastboot works, you are in fastboot mode. adb only works in OS or alternately in TWRP, and will never work in fastboot mode.
Click to expand...
Click to collapse
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Are there steps in fastboot that I can take to fix this phone?

swumo said:
In this case, how would I get into ADB if neither the OS nor TWRP want to boot past the the error?
Click to expand...
Click to collapse
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
swumo said:
Are there steps in fastboot that I can take to fix this phone?
Click to expand...
Click to collapse
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).

swumo said:
Hello,
I post here after 12 hours of continuous search and attempts at fixing things on my own, which may have dug me deeper into trouble than if I've asked for a tailored solution to this issue. Apologies for repetitiveness if I've failed to find answers elsewhere.
I was running LOS 15.1 with custom kernel and maybe the 5.0.8 firmware or lower. I don't recall the version.
In an attempt to flash LOS 16.0, I performed a nandroid backup, but didn't back up my internal storage. That was stupid of me
I grabbed all the files needed, and started by flashing the firmware version stated in the flashing guide for LOS 16., which was 9 point something.
Phone bricked, blank screen.
Got hold of a factory reset tool from an unbrick guide here, followed their steps to completion despite repeated failures in the MSMDownloader.
Now my phone boots in fastboot mode only, adb on PC neither can detect nor interact with the phone, and it is stuck in a md5 checksum bootloop with "modem" and "dsp" in the red, and all attempts to boot into recovery lead back to the md5 checksum screen.
On fastboot mode, "Bootloader version" and "baseband version" are both blank.
This is all I know to provide at the moment. If there is any way to salvage the phone with the internal storage intact, I would prefer that please. But I won't look a gift horse in the mouth at this point if I ultimately have to wipe everything clean to fix the phone.
Click to expand...
Click to collapse
I forgot a detail in the middle of the story.
Right after I flashed the pie firmware, it restarted and I was given a prompt that said something along the lines of "Flash successful and everything, but decryption failed. You will lose all data if you boot, are you sure?"
I turned off the phone, from there it bricked with a blank screen. It was then that I got the unbrick tool and went through the rest of the earlier story.

redpoint73 said:
You simply can't. adb will only work in OS or TWRP, period. Nothing you can do can change that fact. You're stuck with fastboot.
I can't personally think of anything. I just wanted to point out the fruitlessness of trying to use adb, so you don't waste time trying to get it to work (since it never will).
Click to expand...
Click to collapse
I appreciate you reaching out and offering closure. It seems this phone is fried.
Thank you.

I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?

swumo said:
I got past the MD5 checksum hurdle, and I flashed TWRP. It works.
I can't access internal storage to flash anything from the phone, not even the TWRP nandroid backup, but ADB is an option again.
Decryption refuses to take my password even though it's correct.
I do have a backup of the nandroid on my PC. Could I flash that via ADB?
Click to expand...
Click to collapse
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs

BillGoss said:
It would help others who get into the same situation if you post how you got passed the MD5 checksum hurdle.
If you can get into TWRP I would suggest you use the latest version 3.3.1-0 and use wipe>format data (not wipe>advanced wipe) which will clear the encryption. It will give you an ext4 data partition, which is fine. If you want to change it back to f2fs use wipe>advanced wipe to reformat it to f2fs.
I don't recommend using an unencrypted phone so my next step is to copy from your PC to the phone the ROM zip file and anything else you need to flash. I would flash the full OOS zip and let it boot up as this will automatically encrypt your data. It will also replace TWRP with the stock recovery but you can flash TWRP again using fastboot. You can then go back to TWRP and set things up the way you want, including restoring the backup you have.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thank you for dropping by.
Regarding the couple of errors in the MD5 checksum, "modem" and "dsp", the problem lied in that I didn't know which files I'm supposed to flash using fastboot to fill their spots.
By referring to the forum post of the firmware here, I found one workaround was to "consult META-INF/com/google/android/updater-script in the flashable zip of the firmware ... to check which file from the firmware-update directory goes to which partition."
From there, I inferred that "modem" takes the file named NON-HLOS.bin, and that "dsp" takes adspso.bin
Flashed them via fastboot, and I was greeted by a successful boot to stock OOS 3.1.2, the version provided by the unbrick tool I used.
However, it seems that the damage done to the phone (either by the failed firmware flash or the unbrick tool) has led to the internal storage being corrupted, or perhaps the damage was done to how the system decrypts internal storage. I am a medical student, so most of these intricacies are way out of my league.
I was hoping to recover the internal storage, but would gladly part with the data if it means I can use the phone again. There was nothing particularly important on the phone that the TWRP backup didn't have.

Pardon me, but which file system would be most suitable for each partition?
The Wipe>Advanced Wipe menu offers several file systems for several partitions. I'm inclined to leave everything as it is, but should I perhaps format the /system partition as f2fs for instance?

THE root method. (any android version. yes 10 stable)

Alot of people still dont seem to understand or know how to root their devices and the help ppl find online can be misleading and sketchy. I just want to share this easy method to hopefully save some ppl from trying to do this or that and having bad results. This IS the common sense duh way to root. Use magisk to root it. Long as you got adb and fastboot on ur pc and the phone's bootloader is unlocked you can root like this...
1)download the magisk manager.
2)get the ota .zip file for the android version you are running.
3)get payload-dumperwin64.zip and unzip it.
4)unzip the ota.
5)put the payload.bin file from the ota into the input folder for payload dumper.
6)run payload dumper.
7)get the boot.img from the output folder of the payload dumper.
8)copy the boot.img to your phone.
9)open magisk manager.
10)press install, then install, then 'select and patch a file'.
11)select the boot.img
12)once the boot.img is patched it will be renamed magisk_patched.img, copy the magisk_patched.img to your computer.
13)start your phone in fastboot mode
14)on your computer open a command prompt and type 'fastboot flash boot (and the magisk_patched.img file location)'
15)once successful type 'fastboot reboot'
ROoT! Super easy right? And yes, it works with 10 stable. Just make sure to use magisk manager 20.1.
As far as twrp goes, you can try flashing it with magisk if you like, but I can't say whether or not it will work on 10 because I didnt bother. Twrp hasnt been very helpful to me on my 6T.
I know to a lot of us this is pretty common sense, but it looks like there are still a lot of ppl needing help getting rooted on 10 stable for some reason... Thats why I posted this. Don't hate. Help.

<Mod edit>
To install TWRP,
download - android Q twrp img and the installer zip. Place the TWRP installer zip in your phone storage.
download magisk installer zip into your phone storage.
1. boot in fastboot, open command line in your PC.
2. flash twrp img - fastboot flash boot <your twrp>.img. You lose root and custom kernel here.
(fastboot boot <your twrp>.img for android 9.)
3. Reboot to recovery from phone's fastboot menu
4. install the <TWRP installer>.zip file in TWRP.
5. Reboot TWRP to flash magisk.
6. Flash <magisk installer>.zip in TWRP
7. Reboot system. Exit your command line on PC.
The end.

Can't we just flash Magisk on TWRP?

yot2703 said:
Can't we just flash Magisk on TWRP?
Click to expand...
Click to collapse
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.

e5p10nage said:
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
Click to expand...
Click to collapse
Seeing as how I haven't made a reliable backup in TWRP/custom recoveries in like two years, I appreciate this route. Swift Backup and frequent OTG backups are enough for me, I just want root.

There is a new version of twrp, build .27 that is meant to fix backup / restore issues

Striatum_bdr said:
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Click to expand...
Click to collapse
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.

e5p10nage said:
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
Click to expand...
Click to collapse
No it doesn't work at all forever. Fastboot is modified in 10 you must write 'fastboot flash boot file.img'

Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.

Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.

UberFiend said:
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Click to expand...
Click to collapse
I have heard of that being a bug with Q. Just look it up on google. Lots of pixel owners havin that same issue. I didnt have this problem, so I am not sure what caused it or how to fix it. You FOR SURE used the boot.img from the ota you currently have installed? Anyway, I think I saw someone say something about the throttling in the developer settings.. IDK if that really has anything to do with it though.. Im sorry that happened though.

greentag said:
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
Click to expand...
Click to collapse
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.

e5p10nage said:
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
Click to expand...
Click to collapse
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.

greentag said:
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
Click to expand...
Click to collapse
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?

Tl;dr: this is not THE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]

Timmmmaaahh said:
Tl;dr: this is notTHE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching

e5p10nage said:
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
Click to expand...
Click to collapse
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."

e5p10nage said:
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
Click to expand...
Click to collapse
The payload dumper thing I was talking about is a method of obtaining the boot.img from the ota on your own instead of looking for one on the web. Doesnt matter what payload dumper you use, that was just the one I found. Hopefully this makes it a lil more clear.

e5p10nage said:
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Click to expand...
Click to collapse
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.

greentag said:
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
Click to expand...
Click to collapse
I see. Well I am glad you pointed this out cuz I wasnt aware of the need to factory reset. The only reason I did is because after the local upgrade my phone wouldnt boot to anything but recovery UNLESS I reset it. So I didnt have an option not to really. I was rooted with twrp on 9.0.17, got the ota from oxy updater, local updated, just like ya said you did. Not sure why it wouldnt boot after that without the reset. Im not entirely sure that it is 100% needed to factory reset to root this way though. Ive talked to other people who tried this and said they had no problem. Then Ive also talked to other people who have. I feel like there are some variables we arent considering at work here. But thank you for pointing this out. The only goal I have here is to be helpful, so all problems with this method also need to be part of the conversation. So I appreciate it.