Related
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?
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?
So,
I have a Mi 9T Pro (Global) 128GB. I upgraded it to the latest MIUI version when I got it (11.something).
I unlocked the bootloader and flashed TWRP. So far so good. But then, when trying to flash LinageOS I must have missed a step.
Long story short: When booting I see the linageOS bootlogo for a good 3 minutes or so, and then it kicks me back into TWRP.
It might also be worth mentioning that I flashed the DisableForceEncrypt before.
Can someone tell me what I screwed up? (Note: I did wipe cache & dalvik before rebooting so that can't be the issue).
KuroRyu said:
So,
I have a Mi 9T Pro (Global) 128GB. I upgraded it to the latest MIUI version when I got it (11.something).
I unlocked the bootloader and flashed TWRP. So far so good. But then, when trying to flash LinageOS I must have missed a step.
Long story short: When booting I see the linageOS bootlogo for a good 3 minutes or so, and then it kicks me back into TWRP.
It might also be worth mentioning that I flashed the DisableForceEncrypt before.
Can someone tell me what I screwed up? (Note: I did wipe cache & dalvik before rebooting so that can't be the issue).
Click to expand...
Click to collapse
You need to format data when flashing over MIUI.
You should have formatted data, then flashed dfe, before flashing LOS.
Did you flash dfe because you think it's needed, or because you want to permanently remove encryption? There is no need to flash dfe if you would prefer to keep encryption.
I want to keep encryption, if possible. I just had problems that TWRP didnt decrypt, and I couldn't transfer files.
Anyway, so what steps do you suggest me from here on, to get a rooted, working LOS?
Right now I have a half broken LOS install that can't boot properly.
KuroRyu said:
I want to keep encryption, if possible. I just had problems that TWRP didnt decrypt, and I couldn't transfer files.
Anyway, so what steps do you suggest me from here on, to get a rooted, working LOS?
Right now I have a half broken LOS install that can't boot properly.
Click to expand...
Click to collapse
Best bet is to start again.
Flash the latest fastboot ROM for the phone, making sure that you change the flash option in the Mi Flash Tool, so you don't lock the bootloader.
Boot into MIUI once to finalise the installation. No need to do the initial setup.
Flash TWRP and boot into it.
Do a factory reset, followed by format data. Format not wipe, need to type yes to continue.
Reboot into TWRP to ensure the formatted data partition is properly mounted.
Flash LOS, plus the extras you want.
Reboot to system and you should be good.
This is the best failsafe method when nothing else seems to work.
Encryption can cause issues in future, so when updating LOS or flashing a new AOSP ROM it is a good idea to remove lockscreen security before updating/flashing and you should be OK.
Robbo.5000 said:
Best bet is to start again.
Flash the latest fastboot ROM for the phone, making sure that you change the flash option in the Mi Flash Tool, so you don't lock the bootloader.
Boot into MIUI once to finalise the installation. No need to do the initial setup.
Flash TWRP and boot into it.
Do a factory reset, followed by format data. Format not wipe, need to type yes to continue.
Reboot into TWRP to ensure the formatted data partition is properly mounted.
Flash LOS, plus the extras you want.
Reboot to system and you should be good.
This is the best failsafe method when nothing else seems to work.
Encryption can cause issues in future, so when updating LOS or flashing a new AOSP ROM it is a good idea to remove lockscreen security before updating/flashing and you should be OK.
Click to expand...
Click to collapse
Yeah, you should change "clean all and lock" to just "clean all" in the bottom right corner of MiFlash
formated data partition (not wipe data partition, not the same thing)
check my guide https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
(how to flash roms, the MIUI to AOSP part)
@Robbo.5000 @PapajOhn420 Which fastboot rom would that be then? And where can I find the MI Unblock tool? Just want to make sure I don't break anything in the process.
EDIT: The one from the xiaomi website is an absolute disaster tool, it throws errors everywhere.
Also I am pretty sure I dotn have the MIUI accoutn anymore that I created for when unlocking that. I just used a disposable email (10minutemail) for it.
Here's the Fastboot tool: https://forum.xda-developers.com/attachment.php?attachmentid=4920077&d=1578342342
Here you can find a suitable fastboot rom: https://xiaomifirmwareupdater.com/miui/
Just make sure you choose the correct version corresponding with your device's region.
EEA is for European devices
PapajOhn420 said:
Here's the Fastboot tool: https://forum.xda-developers.com/attachment.php?attachmentid=4920077&d=1578342342
Here you can find a suitable fastboot rom: https://xiaomifirmwareupdater.com/miui/
Just make sure you choose the correct version corresponding with your device's region.
EEA is for European devices
Click to expand...
Click to collapse
The ROM I downloaded is a zip file which contains multiple files. When selecting an image from the flash tool I can only search for files with .img or .bin extension.
Should I renmae the .zip to .img? Also, what partition do I select when flashing? And this version of the mi flash tool doesnt seem to lock the bootloader by default, or am I missing something?
There is an option OEM Unlocker/locker, but thats about it. As long as I dont touch that I should be fine?
Use this one: https://www.xiaomiflash.com/download/
Remember to check "clean all" in the bottom right corner.
Then you select the extracted folder in the tool.
Make sure it corresponds with your device's region.
PapajOhn420 said:
Use this one: https://www.xiaomiflash.com/download/
Remember to check "clean all" in the bottom right corner.
Then you select the extracted folder in the tool.
Make sure it corresponds with your device's region.
Click to expand...
Click to collapse
This is the one that prompts errors everywhere. Missing log file paths etc.
KuroRyu said:
This is the one that prompts errors everywhere. Missing log file paths etc.
Click to expand...
Click to collapse
Can you post a screenshot?
Just says:
{
"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"
}
I specified the folder where I placed the MIUI rom zip file in. And I also selected clean all.
I still dont understand - what is the difference between flashing normally with TWRP and this MIUI tool? Shouldnt that be the same thing?
KuroRyu said:
Just says:
I specified the folder where I placed the MIUI rom zip file in. And I also selected clean all.
I still dont understand - what is the difference between flashing normally with TWRP and this MIUI tool? Shouldnt that be the same thing?
Click to expand...
Click to collapse
You have to extract the zip file and then select the extracted folder in the tool.
KuroRyu said:
Just says:
I specified the folder where I placed the MIUI rom zip file in. And I also selected clean all.
I still dont understand - what is the difference between flashing normally with TWRP and this MIUI tool? Shouldnt that be the same thing?
Click to expand...
Click to collapse
You can get the latest fastboot ROMs from here
https://xiaomifirmwareupdater.com/miui/raphael/
Make sue you choose the region for your phone and you choose a fastboot ROM.
Here's the flashing guide from the official MIUI forums, it also has the link for the official Mi Flash Tool. If it gives lots of errors, make sure you've got the proper drivers for the phone installed and a good quality USB cable.
https://c.mi.com/oc/miuidownload/detail?guide=2
You will need to view the page in desktop mode if viewing on a phone. Make sure you change the flash option in step 5 to 'clean all' before flashing.
Also the fastboot ROM is a *nix compressed tarball. Most Windows apps will need to unzip it twice. First one uncompresses it, it should leave a .tar file. Second time unpacks the tar file, leaving the ROM
Fastboot ROMs are more complete. They have many more partition images inside than standard recovery zip ROMs. They are for completely restoring the phone. The Mi Flash Tool is for flashing the fastboot ROMs.
Once you've flashed the fastboot ROM, follow my earlier process to then install LOS
@Robbo.5000 Thanks to you and all the others - I got it to work now.
Is the procedure you described the go to way to also do a clean flash - e.g. when updating to a newer version of LOS?
Why is the reflashing of MIUI necessary everytime? Does it have something to do with the vendor?
KuroRyu said:
@Robbo.5000 Thanks to you and all the others - I got it to work now.
Is the procedure you described the go to way to also do a clean flash - e.g. when updating to a newer version of LOS?
Why is the reflashing of MIUI necessary everytime? Does it have something to do with the vendor?
Click to expand...
Click to collapse
No need to do all this every time. This is my failsafe method for when you can't get a custom ROM to install successfully.
You should be OK dirty flashing updates. Encryption can cause issues though it is best to temporarily remove it before flashing.
In future to dirty flash an update,
Remove all lockscreen security on the phone - this will temporarily remove encryption, reducing the risk of problems flashing.
Boot to TWRP.
Flash the latest LOS zip file.
When finished select the wipe cache and dalvik option.
Reboot to system.
Restore the lockscreen security.
To change to a new custom ROM with a clean flash.
Remove all lockscreen security on the phone.
Boot to TWRP.
Do a factory reset.
Flash the new ROM, plus any extras.
Reboot to system.
Setup lockscreen security.
{
"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"
}
ArrowOS​
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
Here!
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
INSTALLATION - FASTBOOTD
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and extract it to your adb/fastboot folder
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
In TWRP reboot menu, select fastboot, wait for it to reboot
Open a cmd window where you extracted the files to earlier and flash the ROM with the below commands
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Odin1101/Project-Sofia/tree/Upstream-plus
Device Source: https://github.com/whatthef84/android_device_motorola_sofiar-1
Vendor Source: https://github.com/whatthef84/android_vendor_motorola_sofiar-1/tree/android-11
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!
View attachment 5273685View attachment 5273649View attachment 5273651View attachment 5273653View attachment 5273655
View attachment 5273657View attachment 5273659View attachment 5273661View attachment 5273669View attachment 5273671View attachment 5273673View attachment 5273675View attachment 5273677View attachment 5273679
Agh, plain AOSP. I miss Havoc already.
Testing it out and everything thing seems smooth. I did find one minor issue for the people that like their temperatures in imperial units. You can change the lockscreen temp to imperial and it displays an F for farenheit but the temperature value is still Cecius.
Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?
jonshmorg said:
Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?
Click to expand...
Click to collapse
You will need to go back to rooted stock, and copy your apn_conf.xml file from product/etc to your sd card, amd replace it on arrow (or another rom)
Quantumstate said:
Agh, plain AOSP. I miss Havoc already.
Click to expand...
Click to collapse
Closest thing to havoc is crDroid ATM mate, it's on the forums here
This ROM is marked as only being compatible with sofiar, but I can confirm that everything seems to work on my sofia device.
Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Edit: It turns out I was using the wrong build of TWRP. Use the one linked in the original post, not the one elsewhere on the forums.
RaspberryPiBen said:
Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Click to expand...
Click to collapse
While in twrp, if you select reboot to fastboot, that is fastboot d
Beetle84 said:
While in twrp, if you select reboot to fastboot, that is fastboot d
Click to expand...
Click to collapse
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.
RaspberryPiBen said:
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.
Click to expand...
Click to collapse
Using the twrp linked here or another?
Beetle84 said:
Using the twrp linked here or another?
Click to expand...
Click to collapse
I just noticed that. I was using the TWRP build from https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ because I assumed that was what the link was for. Thank you.
Apps aren't able to see registered fingerprints. Fingerprint auth is grayed out and the apps complain "register fingerprints on the device settings".
I have tried:
Deleting and redoing fingerprints (just one and multiple) with and without rebooting.
Confirmed the fingerprints work for screen unlock and gestures.
Re-installed 08-04-21 Vanilla build with full format, issue persists.
Anything I missed to check? I do not have my phone rooted, so cannot see system logs using the logging app.
Using sofiar (moto g8 power). Tested the apps themselves on my second phone klte (Samsung S5 Lineageos 16) and fingerprints work just fine there.
Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?
jdude520 said:
Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?
Click to expand...
Click to collapse
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.
ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?
Carl-Robert said:
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.
Click to expand...
Click to collapse
I'm not the person with the problem, but thank you for the explanation. I installed my ROMs before Android 11 came out for this phone and I was planning to test the stock Android 11 ROM, so this information will be very useful.
jdude520 said:
ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?
Click to expand...
Click to collapse
I believe you have to roll back to Android 10. Custom Android 11 ROMs may work, but you can't install custom ROMs so that doesn't help.
actually it is rescuing me to android 11 no matter what i do
Disclaimer: NOT RESPONSIBLE FOR ANY BRICKED DEVICES
YOUR DEVICE MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS TO WORK
My first tutorial, gonna keep this short and sweet
1. Go to settings > About Phone > check your version number (eg 10.5.9 for mine)
2. Go to this thread and download the global zip with the corresponding number https://forum.xda-developers.com/t/...ota-oxygenos-repo-of-oxygenos-builds.4253501/
3. Use payload dumper to extract the payload.bin file in the zip (you don't have to extract the whole thing, I killed mine when I got my boot.img file)
4. Install Magisk on your device and patch the just extracted boot.img
5. Copy patched boot.img to your computer
6. Reboot into bootloader, run this command and NOTHING ELSE
fastboot boot <location of patched boot.img>
7. Now your device should be booted into a rooted state and if your wifi or cellular doesn't work, have no fear. This is only temporary and we need root for the next few steps
8. Install Partitions Backup https://www.apkmirror.com/apk/wanam/partitions-backup/partitions-backup-2-3-0-release/
9. Use that to dump boot.img from both slots to your device
10. Use Magisk to patch both boot.img files just dumped from Partitions Backup
11. Copy all dumped and patched boot.img files to your computer
12. Reboot into bootloader and fastboot boot into your newly patched boot.img files
13. If everything works, reboot back into the bootloader and flash the working patched boot.img files to both slots
14. Profit and enjoy! Tested and working on 10.5.9 for my N100, not yet tested on Android 11, do so at your own risk!
Leave a thanks if this helped you, this is for folks like me who couldn't find a backup of their OS build on the internet and needed a temp way to root their carrier devices
I'm going to try this now. Thank you for the idea!
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
Unfortunately, I can't even get into EDL mode. So this brick might be permanent. I'm asking for help from the community here: https://forum.xda-developers.com/t/nord-n100-edl-mode-dead-gone.4341305/
bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it
luridphantom said:
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it
Click to expand...
Click to collapse
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB
bouyakasha said:
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB
Click to expand...
Click to collapse
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine
I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.
bouyakasha said:
I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.
Click to expand...
Click to collapse
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it
luridphantom said:
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it
Click to expand...
Click to collapse
Oh, thank you! That makes sense. I will try to UN-Tar it
I used Zarchiver to unarchive the TAR into boot.img for both, and this all worked! Thanks so much. Awesome guide.
@onlycash You should try this!
luridphantom said:
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine
Click to expand...
Click to collapse
I tried several times and it's not working for me.
Everything appears to be fine till I try to "fastboot boot patched.img".
I'm trying to do this on an Metro N100 which is on 11.0.1BE82CF
I downloaded the global: 11.0.1: OnePlusN100Oxygen_14.O.21_GLO_0210_2107241056 MD5: a895312987628f21d0232d44575d0742
I extracted the payload and dumped the boot.img
I patched it in Magisk
I successfully "fastboot boot" that patched file but then it just hangs at the at the Metro boot screen.
I waited a minute or two but it didn't move past that screen, should I have waited longer?
In any event, I could hold down the power key and reboot into the unrooted stock 11.01 without issue.
Does anyone have an idea what I'm doing wrong?
{
"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"
}
.
onlycash said:
I tried several times and it's not working for me.
Click to expand...
Click to collapse
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.
thomaskmaagaard said:
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.
Click to expand...
Click to collapse
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.
onlycash said:
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.
Click to expand...
Click to collapse
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it
My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.
luridphantom said:
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it
Click to expand...
Click to collapse
I posted a good deal on the TWRP thread. I can fastboot the TWRP on my phone but I can't see any files only folder tree, even with my SD card I don't see any files either with TWRP.
I should add I'm running TWRP on a Metro N100 which is both SIM and bootloader unlocked. Also I didn't flash the TWRP I only fastbooted it, could that be the problem?
I really would rather flash the zip and root that way if I could get the TWRP to work.
I'm unsure what "disable dm-verity by flashing an empty vbmeta image" means in my case. What does this do?
Again I'm truly grateful for any help, thank you.
bouyakasha said:
My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.
Click to expand...
Click to collapse
Just to be clear I have a Metro N100 BE2015 running 11.0.1BE82CF.
With that being said, did you only get root when you went back to 10.5.8?
Are you rooted now on 11 and if so how did you get there?
Did you brick and go back to 10 then root 10 and update to 11 and keep root? How did you patch the img file after going to 11?
Any help and info would be much appreciated.
.
@onlycash I have constructed a small/random theory with no real basis. Could your problems be related to OOS 11? It sounds as dumb to me as it probably does to you, but I'm getting a nagging sensation that folks with success on your model aren't running the new update.
Just a weird hunch with no proper research, but I find it weird that you have these "unique" problems so I'm just spitting random junk at this point.