Related
Hi all,
I am trying to make sense of how the android system is made up w.r.t to boot/kernel.
I have been looking at the .img files in the build (I built for the "passion" device), and have been googling around to find some more information about the various .img files.
I ran into a nice HOWTO in android-dls.com 's WIKI, titled HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images (I'm sorry, I'm a new user so XDA won't allow me to post links. I will try to modify my post a soon as I'm granted permission for that)
but I am afraid it is a little outdated:
I have several questions, but I will try to be brief, so I'll focus on
one of them, and if that works I'll proceed to the next questions, all related to "Android bringup for dummy embedded linux kernel experts".
I am fairly aware of differences between different linux
configurations, and I am very familiar with linux bringup concepts, so I will just use common examples from the linux world as my terminology. Hope it will be clear enough.
I understood that boot.img a combination of a kernel (e.g. bzImage in linux) and an initial ramdisk (e.g. initrd.gz), wrapped by some header, as in common linux kernel loading practice (piggy.o etc.).
Now, the aforementioned HOWTO says that the "recovery" image is built on
the same way, and that it is stored on the target's /system/
recovery.img .
I would assume that this would be compound of the ramdisk-
recovery.img, and some other kernel.
Now, the problem is that:
1. This /system/recovery.img does not exist from what I saw (on my
Motorola XOOM tablet)
2. What does exist is /system/boot-from-recovery.p , which is
created during the boot process in obj/PACKAGING/
recovery_patch_intermediates/recovery_from_boot.p .
I saw tons of posts referring to the files, all said that "in order to
replace the rescue disk image, this file needs to be renamed" - but I
am looking for a way to figure out what it is, and how to extract its
contents.
I assume /system/recovery.img is deprecated, is that correct?
3. I did not see any flash devices in /proc/mtd (which is strange).
I searched for hours before sending this post, so I would appreciate
your help. I also posted a similar message at the google android-building group, but it has not been answered yet, and I got the impression that these forums are more active and can help me get where I need.
If it is not the right place to ask the question please let me know -
I just assume this is a general android concept and not device
specific.
Thanks,
Ron
I meant of course /system/recovery-from-boot.p , and not recovery-from.boot.p
-R
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Well, it helped me. I'm new to rooting and just came across mention of this file. I am trying to learn 'why' as well as 'how'', so your post was informative.
Was going to ask a dumb question but I figured it out
i need to delet those files
bigrammy said:
Was going to ask a dumb question but I figured it out
Click to expand...
Click to collapse
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
recovery from boot p
ahmed morsy said:
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
Click to expand...
Click to collapse
Hey good day. Did you get your problem fixed...? I have an xt912 it has the same file. For days I've been trying to wipe the phone. Tryed rooting it. I tryed reprogramming it. And I got through with all of that. But everytime the phone boots up it goes back to the same state. Then I used a root browser and while exploring I saw this recovery from boot file. I need help. And I don't think I can downgrade the Motorola phones. Thanks in advance.
jman0 said:
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Click to expand...
Click to collapse
i have deleted it . then flash recovery ,, but it failed .. it wont even now go to stock recovery itself.. any help..
Does recovery from boot has to do anything with ota update applying ? or it will cause issues in system update ?
I have recovery-from-boot.p in my system and i cant root my phone i cant change the recovery img ... Help?
I hadn't had to deal with this for some time, perhaps because I've updated my devices (Nexus 4, Nexus 5, Nexus 7 '13) with the factory images, with "-w" removed from flash-all, then flashing CWM's recovery, ensure SuperSU was installed, then continuing. Today, I used the new OTA image on my Hammerhead/N5, and recovery-from-boot.p seems to be up to its old tricks again.
Solution is simple.
Flash your alternate Recovery in fastboot, fastboot flash recovery [recovery image file] . Boot into Recovery. Apply/install root app (typically via sideload). Mount /system. adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak. Reboot. Done. (If you're unfamiliar with fastboot, adb, and flashing new recovery partitions, you have some reading to do. Commence RTFM.)
I also used to have to move /system/etc/install-recovery.sh but that seems to be gone in Marshmallow. :} Or moved...?
well, after following a guide I have extracted the system.img from a pure-nexus ROM(The ROM I'm currently using), now I can see that "recovery-from-boot.p" file is responsible for recovery lock in my phone. I'll keep it short and straight to the question
"Can I remove this file and rebuild the .dat file and flash it?, so that I won't have any other problems at all"
I want to know if recovery-from-boot.p file is linked to anything other than just locking the recovery or re-flashing it innumerable times.
Dear Friends,
About to pull a trigger on an AT&T LG G4, can someone give me a short answer, ASAP?
Is it possible to have permanent Root and Xposed on the AT&T variant WITHOUT ridiculous bugs like a "green dot" in the camera of the phone? (what does the green dot even mean? It's on every picture? Is it a watermark? Just on the GUI?)
If possible, how? And should I buy the phone?
Appreciate any QUICK responses, about to buy now! Thanks so much in advance!
I just bought the G4 a couple of days ago. I was able to root, but there is no twrp or xposed as far as I know. I also don't have the green dot and everything is working fine!
Thanks for the quick response, my friend. Can you share the method/thread/image you used to Root?
I think you can install Xposed without TWRP via FireFlash? Can someone please confirm?
Thanks guys!
Just got my G4 two days ago. You can root and you can install Xposed with FireFlash. Root requires pushing a rooted version of whatever software version you are currently running. If you can't find one you can inject root into your own system.img using Ubuntu. After root get FireFlash and the right xposed zip and be patient, it can sit black screen, appearing dead for 20-30 minutes. Over all not too hard. Took me a couple hours from The un-boxing to Xposed. Definitely do it. The green dot on camera comes from the PR system.img. I'd stay clear of that. Everything is working great on mine!
@Nowak4G - Thanks bud, that's what I read too. Can you point me to the guide and img file you used that worked for you? I doubt I'd prefer the Ubuntu way...
One other question... Is there a way/app/Xposed module that's kind of like G3TweaksBox for us? Letting us change the Status bar icon colors and toggle colors?
I highly doubt themes work for us since we can't Flash them without custom recovery?
Thanks again!
GravityBox works for status bar stuff and yeah here are the threads I used. Good luck bud!
http://forum.xda-developers.com/showthread.php?p=62028519
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
http://forum.xda-developers.com/showthread.php?p=62664473
I'm not totally sure what stuff can and can't be flashed using FireFlash. But for applying icon themes with Xposed I use this module, Unicon:
https://drive.google.com/file/d/0B1nrydqmmOBUdFoyV0FBLUM1OVE/view?usp=docslist_api
I've had my LG G4 rooted and running Xposed with a lot of modules enabled.
If the phone you buy is on the 10G software version (and want to stay on that version), you should be able to root it following the method in the LG G4 Low Effort Root thread. Follow it to the dot and enjoy partial freedom.
If the phone you buy is on 10I, there is a rooted image floating around. So you could take the 10I update (or make sure your phone's on the 10I version), and root it using the Low Effort Root method.
I would also recommend the following:
1. keeping a copy of your untouched fresh system image in your internal memory (as early as possible after buying the phone). In case of a bad flash you have something to possibly go back to - otherwise you'll end up with the PR ROM and the green dot. The method and commands to extracting the system image is very similar to rooting, except instead of dd'ing into the system partition from SD, you do the opposite (from system partition to SD)
2. disabling system apps and system updates using the debloater tool and a tutorial here on the forums
Regarding flashing files via recovery, I usually extract the files and place them in the correct directory with the right permissions. Usually most files use 0644 permissions, but I would first check the existing permissions with ES File Explorer.
Hello @Nowak4G and @mu3g,
Guys thank you for your response. I can confirm that the seller I bought the phone from took the 10l upgrade. I have little to no experience rooting locked bootloader phones, and I have to be honest, I am more confused than I have the answers. Now that I have confirmed that I will end up with 10l update, can you guys give me a noob boost and give me step by step on how to root, Xposed, and possibly back up my stock image, since I do NOT want to end up with the PR build, with the green dot, in case things go wrong?
Am I correct that the right answer to my problem is, Low Effort Root with the floating 10l rooted img file, located here: https://drive.google.com/file/d/0B54ceS-n3ZAiaVAxMkJFLXNMYmM/view?pli=1
Please help me out guys, would even appreciate more if we can maybe connect on Google Hangouts for some dynamic help? Please let me know and thank you again for your wonderful so far !
Yes, exactly. Use the floating around 10I rootedsystem.img with the Low Effort Root instructions. But definitely keep a unrooted system.img on the internal storage as a backup. Instructions are in the LER thread. Just read carefully and follow the steps and you should be fine. All copy and pasting.
You have the correct 10I rooted system img file. I would recommend following the LER steps and backing up the system image for 10I (see post 2 of the LER thread). This would give you the stock image for later use. Then follow the LER steps to the dot using the rooted system image file you have from the google drive link. The LER thread has pretty clear instructions on backup and flashing system image files for the G4. Just make sure to rename your downloaded file as "system.rooted.h81010i.img" and use it in the command...the file name here is the most important!
Thank you guys, couple of follow up questions:
1. Do I run the backup command to copy my Non Rooted image, right after the step that gives us the DIAG Port Number? Or do I do it after the "id" step?
2. The generated back up, I assume will be done as an .img file in the root of my phone, correct? I assume I just back this up on my computer and/or External HD?
3. This is the scariest step. When I am running the step for flashing the rooted img, I need to rename the downloaded file to, "system.rooted.h81010i.img" as @mu3g recommended? Why not, "system.rooted.h81010m.img" for example?
4. I just use the exact file name we determined above for my downloaded rooted 10l image file, in the flash command when following the LER guide? Exactly that file name, correct?
Thank you again for all your help and excuse me for my continuous noobness!
Answers:
1. Run the backup command in Step 7 of the LER root ("Run the command specified in the section below titled 'Commands to Run' to flash the rooted system image.") <<---replace the commands to run with the command to backup your unrooted clean system image to your internal memory ---- if you compare the commands, it will become obvious on how the data is being moved (pushed or pulled from the phone).
2. The generated backup will be on the root of the internal memory of the phone. Yes, you can then move it to your computer or any other location for safekeeping AFTER you've booted your phone up properly - don't do any of this while you're still in the LER state.
3. I just gave you a recommendation on the name..you can name the rooted system image file whatever you want - you can even leave it as the way it is....just make sure to use the EXACT file name for the image in the commands to run (also 10I, 10M etc. are software version numbers..I'm not aware of a 10M version being released for AT&T. In any case, just use the EXACT file name for the rooted image.
Thank you @mu3g! I think I am now ready to go through the process myself with confidence.
I am, however, still a bit confused about the file name of the rooted image that I will be flashing. If the phone already has 10l installed, and I leave the name of the rooted image intact, that is, "system.rooted.h81010l" would the phone still accept/get tricked into, thinking that it's getting an "update"? Or did you mean that the file name could literally be anything like, "filename.img" and if the commands match it, all will be installed correctly? As in, when the system boots, it will have all the correct build and software information with it being a 10l update and etc?
Please forgive the annoying, detailed questions, but I want to not mess this up, since every guide triple emphasizes the importance of the command being absolutely right! Thank you!
You can literally name it blahblahblah.img as long as you use blahblahblah.img in the commands to run for the rooted system image. The file naming scheme has nothing to do with the acceptance or rejection of a system image. When you're in the bootloader mode ready to download files (which is the mode for LER), you can inject any file into any partition, anywhere on the phone...it's just whether the phone can use it or not properly and whether or not it ends up being a brick
Your file name for the system has nothing to do with the build number showing on the phone after booting up.
EDIT: The only reason I gave you that file naming scheme is because you don't seem to be too comfortable with the command line, thats all..that way you could copy paste the command from the LER guide and just replace "g" with "i" - that's all..if you're good with the command line and careful, you'll be fine..just make sure the file name is correct..you can't get much else wrong.
Understood brother, just needed that clarity. I am not an absolute noob with cmd line, but you know how it goes when you're rooting your phone, the perpetual fear of an expensive paperweight!
I cannot find the thanks button here, wish I could, so I could thank you over and over and @Nowak4G, but either way, thank you so so much @mu3g!!
good luck!
How did it go? Were you able to go through with it?
While the green dot does usually appear on 810 phones running the PR KDZ, I have heard reports of it on some 815 ...its pretty random. I just did a warranty exchange for my 810 so I will likely be staying on the ATT software.
Hi Guys, wanted to update this thread with my results...:
I successfully rooted on H810l (AT&T) with 0 issues, following the Low Effort Root. Per the recommendations of the process, I also backed up my Stock, Unrooted, .img file for restoration to Stock, if it were needed. Well, I might be moving on from this phone and need to return to stock. Can someone advise the exact steps/commands to return to stock using the unrooted .img file I backed up before pushing the rooted .img? And can you confirm that you did this successfully as well?
I would really appreciate it! Thank you!
I have not done it myself, but if you uninstall all your root apps completely, make sure to enable any and every disabled app you may have (like for example AT&T apps etc.) using the debloater software and then follow LER to install the stock image on it, it should come back to bone stock. Remember, the key here to to ensure that no root apps exist on the phone - I guess SU will get wiped out, but its better to do it clean. And secondly, any disabled apps need to be re-enabled for a smooth process. These are just my $0.02...so proceed with caution.
I was frustrated by the huawei encryption and decided to get rid of it once and for all.
At first I faced many bootloops but i finally figured out what was going on. Formatting user data through TWRP is not enough because after booting the device, encryption is still there. This happens because the kernel encrypts the device when booting up. Simply modifying the boot.img file to remove file encryption also doesn't work because you still boot into an already encrypted stock user data. So the answer was pretty obvious by now.
The trick is to format data using TWRP AND THEN boot to bootloader to flash a modified boot without encryption. So let's get to it.
How to create a modified boot.img without file encryption/dm-verity
1. Find and download your current firmware from Huawei Firmware Finder Dtabase (Team MT), or from a source that you trust. (Using a firmware with different cust version or a different update will most likely not work).
2. Download Huawei Update Extractor and use it to extract the stock boot.img file from UPDATE.APP
3. Download ASSAYYED_KITCHEN.
4. Place your stock boot.img file in the "WORK" folder of ASSAYYED_KITCHEN.
5. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 1st one (Unpacking Kernel).
6. The ASSAYYED options don't work for me so i did it manually. Go to your work folder and open the folder boot_unpacked\ramdisk.
7. You will see a file named "fstab.qcom", open it using WordPad.
8. Find the line:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,fileencryption
and delete ",fileencryption".It should now look like that:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check
9. (This step is optional,follow it only if you also want dm-verity removed) Use the same method to remove dm-verity.
Code:
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/product /product ext4 ro,barrier=1 wait, verify
(Just delete the ",verify" part.)
10. Save the file.
11. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 2nd one (Packing Kernel).
12. Follow the instructions below to properly flash your modified boot.img and get rid of encryption.
Removing file encryption/dm-verity from the device
1. Unlock your device.
2. Flash this TWRP on AGS-W09 or the appropriate custom recovery for your device.
3. Boot to TWRP and FORMAT user data (note that it is very important to format data and not just wipe it). •WARNING• this will delete all your data!
4. Go back to the reboot menu of TWRP and select reboot booloader (it's important to not allow your device to boot into system yet).
5. Using fastboot, flash your modified boot.img that you created earlier.
6. Reboot your device (you might get a bootloop on the first boot but force rebooting your device again by holding the power button will fix that).
7. After booting up, your device should not be encrypted anymore.
8. You can now use the root method that you like to root your device and internal storage should be visible on TWRP. TWRP backup should also work normally.
How to fix Magisk modules not showing up on Magisk Manager (! /data/adb/magisk_merge.img mount failed error)
I am not going to get into the technical staff you can find more info here
Edit: As of Magisk 19.0, the following method becomes obsolete. Magisk modules should now work as expected without issues. This method now concerns those who want to stick to an older version of Magisk
1. Download f2fsfix-2018.9.2.zip provided by VR25 on the thread above.
2. Download all the magisk modules that you need to flash and place them on your device.
3. Download the latest Magisk uninstaller along with the latest installer.
4. Boot to TWRP and flash Magisk uninstaller. (If you don't have Magisk already installed, skip this step)
5. Wipe Davlik Cache.
6. Install the latest Magisk.
7. Wipe Davlik Cache.
8. Flash the "f2fsfix-2018.9.2.zip" immediately followed by your modules.
9. Reboot (it should take more than usual).
10. Open Magisk Manager and check your Modules. Hopefully they'll show as installed and function correctly.
Note: This method should also work on similar devices. Just make sure you know how to recover your device in case something goes wrong.
I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!
TRS_80 said:
I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!
Click to expand...
Click to collapse
Glad it worked for you. Yes this is the downside. The device already comes with an encrypted userdata, so it needs to be formatted. So anything you do before that becomes obsolete. That's why this procedure is much more convenient when it happens after the unlock,when the userdata is wiped by the stock recovery to get a stock condition.
AGS-L09 LTE
I just followed your detailed guide to my tablet and finished all the processes perfectly.
Working..Twrp, Magisk, removed encryption & verify from boot.img and from Data successfully.
A big THANKS for your guide, links and trick all in one post!!!!.
Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again
mr_fingy said:
Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again
Click to expand...
Click to collapse
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device here. If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img
Thanostsak said:
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device . If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img
Click to expand...
Click to collapse
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again
mr_fingy said:
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again
Click to expand...
Click to collapse
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.
Thanostsak said:
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.
Click to expand...
Click to collapse
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks
mr_fingy said:
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks
Click to expand...
Click to collapse
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)
Thanostsak said:
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)
Click to expand...
Click to collapse
On it now before work
Extracted stock_boot_(IDremoved).img.gz which contains the img
Will run your guide against this img
---------- Post added at 09:20 AM ---------- Previous post was at 08:33 AM ----------
All done. Nice and easy
No issues other than sweaty palms on Huawei long boot screen after flash :silly:
No reboot loop and no Magisk errors
Much appreciated for the help
Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good
mr_fingy said:
Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good
Click to expand...
Click to collapse
Great! If you need anything feel free to ask.
Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)
TimYuan said:
Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)
Click to expand...
Click to collapse
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
VR25 said:
Those getting everything broken after a second reboot, try the following workaround...
After the first reboot (right after installing), remove </sbin/.core/img/f2fs*bla*bla/service.sh>, </data/adb/magisk_merge.img> and </cache/magisk_merge_.img>.
Note that after doing this, you'll only be able to install modules and update Magisk from TWRP.
Click to expand...
Click to collapse
Thanostsak said:
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
Click to expand...
Click to collapse
It works!!! You are my hero!
TimYuan said:
It works!!! You are my hero!
Click to expand...
Click to collapse
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.
Thanostsak said:
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.
Click to expand...
Click to collapse
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance
an-_-dro said:
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance
Click to expand...
Click to collapse
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.
Thanostsak said:
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.
Click to expand...
Click to collapse
encryption is not a problem. since the first place already done with that data partition.
my problem is system partition, every time i made a change to system (for example deleting chrome.apk), something triggered that makes my system weird (magisk forceclose, all file manager become malfunction because system become read only). something lock my system partition if system change.
i thought change fstab.qcom <mnt_flags and options> ro,errors=panic to >> errors=continue (deleting ro/read only) will change my system behaviour, but it's not
I'm seeing so many different posts. Is it rootable or not? I wanna purchase the device but don't want to not be able to root it. Please let me know directly. I'm tmo btw
Got it already, on launch. It's fair, no real stutters at all, quick, but smooth(so don't mess with settings in developer options "drawing" section. There used to be a way, you could build, or "nominate", a twrp for your phone. I don't see that option anymore, just statistics. I'd like a twrp blog.
reggjoo said:
Got it already, on launch. It's fair, no real stutters at all, quick, but smooth(so don't mess with settings in developer options "drawing" section. There used to be a way, you could build, or "nominate", a twrp for your phone. I don't see that option anymore, just statistics. I'd like a twrp blog.
Click to expand...
Click to collapse
I am reading this comment AFTER I replied to your other on a different post and am realizing that your comment was NOT butchered and you DID indeed mean "builder". You can disregard the second half of my comment on that reply because it assumes you meant "build" and an actual "builder" which I had never even heard of. To that note, that actually would be great if there was still one around to utilize for this phone. A TWRP build is much needed to deal with the update problem I am having. The latest update in Lenovo Rescue does not provide the update since it is the same version number. The boot image can not be patched because they are actually different. I guess I can try my hand at capturing the download file if I only knew where it saved it.
There's an experimental build of TWRP for the Edge (NON +). I haven't tried it personally. Mine is BL unlocked and not rooted with Magisk patcher.
Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...
bronkish said:
Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...
Click to expand...
Click to collapse
Could you lay out the process in detail, or link us to an existing step by step with the correct download(s) that will work for the Edge? I'd really like to root but want to minimize my chance of creating a brick. Thanks!
If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd
Hi,
could you please give the commands you used?
I have completed steps 1-5
I am not sure how to complete step 6
I have the magisk_patched_j5iak.tar file (there is a bot.img file in the archive)
Should I unpack the created magisk_patched_j5iak.tar file?
Please help
Umm, tell you what - try it both ways and then you'll know.
6: your phone is in fastbootd (I told you how to get there) and you flash the boot.img file that you just patched in magisk.
@bronkish Thanks again! I now have my beloved Titanium Backup again! It's been so long since I was rooted I'm going to have to see what else is available again.
[Edit]
Titanium looks a bit dated. Is there a better app now for doing what titanium did?
Rock ON!! SO many "I's" to follow....
I use to use Titanium (pro), too. Today I just export data from apps (settings, really) and I host a nextcloud server - which is handy as fuk (add a calendar event, or contact, on my phone, it's on my server, too, and vice-versa): I can 'share' dumps (exported nova settings, say) and data to nextcloud and if I take a picture 'in the field' it is immediately uploaded to my local nextcloud server and deleted (optional) from my phone. One can achieve all manner of function with nextcloud.
I restore and sync my calendar and contacts from nextcloud (dav), call log from sms backup & restore, which works great - although titamium, 3C, and others do the same.
I do keep handy an apk of every app I like to have installed on my phone, which, really isn't that many. I sometimes use app manager to export apks, or I use FX file manager. I use 3C to backup apps/data. I restore few apps/data with it. 3C can import titanium dumps, as well. I have less need for app/data dumps these days, though. DOn't care at all about twrp, but I'd be more inclined to use the twrp and full system dump restore methodology, as in the past, than using an app like titanium or 3c which requires setting up the phone again first, flashing or installing the app and then restoring apps/data - in this scenario a google account is required for some apps to function again (3c restore) or market links are broken as is handy to do in titanium. A restore from a twrp dump negates all this. You could also use adb for system level (phone) dumps/restore; it's fast and easy.
What do you need to backup? Why? Can you use app exports and a cloud or SD card or some connection to a server/desktop/drive? Can you employ dav? DO you even generate data worthy of backing up?
phone logs
firewall settings (as an example of app settings)
apps/apks in order to achieve function, if you even need to have them handy
texts (if you save them, I use signal and export a text dump to a folder on my sd card, if I even do, which is rare)
contacts, if you don't use google, or whatever
calendar
any important or usable generated data, apps likely have dump scenario
Like anything, there are myriad ways to accomplish the task.
If I'm gonna wipe or reset my phone I have common immediate dumps on my sd card (of course, the phone must have the slot). So, on my card is a folder with some app settings for a quick restore. AFWall settings are there. I have notification sounds and whatnot on the sd root so the phone picks them up. There's a contacts file and calendar file in the dump folder in case I'm near no network when restoring, which, would be odd. There's a couple text dumps, too. Hell, one is 2 years old - why do i keep it? lol.
Also on the card is a key file I use with keepassx as well as a keepass database dump, in case I need it - it's old but has what I need to 'start from scratch' if necessary. I typically just open the keepass dump from nextcloud I just reinstalled from the apk and bam, keepass opens on my phone with my thumb - fuk'n handy. The sd card dumps are just jump-starts if necessary, like, no networking, or something. But, they are there because they would be sorely missed if they were not.
I keep from setting up a google account on the phone for as ong as I can - everything restored, firewall tight, apps frozen, snuffed, or otherwise mitigated. I set the google account up to check fo app updates and for that pain in the ass poweramp which needs to hit the playstore every time it's reinstalled. Pfft. The sd maid and fx file manager apps are so much better to restore because no need for google to validate the purchase.
pffft.
bronkish said:
If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd
Click to expand...
Click to collapse
After doing all of this I'm stuck on the Motorola boot screen. Is there any way to fix this?
bronkish said:
Yes the phone is rootable. I got mine a couple days ago - US retail model at BestBuy. Set the phone up, took the update...
Got: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from a thread here, made a tar archive with boot.img, ran the tar through Magisk, flashed it in fastbootd (I get there by booting the phone to recovery; in recovery hold power button for 3 seconds, keep holding it, hold vol up for 2 seconds, release vol up and there ya go. I 'enter fastboot', which shows fastbootd) - rebooted, opened magisk manager and it told me to continue setup - did. Root. Now, it's mine.
I don't undertand why TWRP is so important - I tried 3.4.0 beta9 on the moto g power last week, what a fuk'n mess. No way I was messing with twrp at all on the edge. AM I missing something? What do we even need twrp for anymore? Make a dump with adb, flash with it, do anything...
Click to expand...
Click to collapse
Question what update is that mine is the same XT2063-2 except mine reads QPDS30.114-80-2
Mine, too.
adbman said:
After doing all of this I'm stuck on the Motorola boot screen. Is there any way to fix this?
Click to expand...
Click to collapse
FastbootD
I gave instructions.
I don't mean to be a rude necromancer of posts but, I know nothing of these... tar files you speak of. I tried to do some homework and I see .tar.md5 and .tar.gz. Question 1: Does it make a difference? Is there a post somewhere I can learn from?
Question 2: How does one, or what software is available to, perform this work?
Respectfully,
Me
tar.md5 or, anything.md5 is just a text file containing the md5 hash of the file. You need or want it only if and when you do - if you don't know, then you don't. A .tar file is an archive like a .zip file. a tar.gz, or, .tgz is a compressed tar archive. tar only makes an envelope for the file(s), it doesn't compress unless you tell it to. There's lots of compression schemes - leave all that alone unless you wanna get back to it later. Magisk needs a .tar archive with the boot.img file in it - let's root
Rooting, with stock recovery, is just a couple simple steps. Magisk really makes it easy.
1 - get the firmware and extract it. You'll need the boot.img file.
2 - make an archive (*.tar) to contain the boot.img file. So, on linux, in a terminal, cd into the extracted firmware directory, do: tar -cvf boot-for-magisk.tar boot.img
windows user do your thing. I got a right-click, I don't even know anymore, check my command.
3 - drop that archive you just made onto your phone for magisk to use
4 - get and install magisk , the apk is fine
5 - open magisk. Top section, choose to install (touch the word: install), in next screen, choose select and patch file - feed it the tar achive you made of the extracted boot.img. point to the .tar file. do it.
Magisk will do its thing to the boot image and will spit out a new one that you can install to take advantage; to have root. Wicked. I copy it back to my computer for fastboot action. DO it - copy the new boot image that magisk generated to your computer.
6 - boot your phone to fastbootD - listen....plug your phone into your computer - usb-c cable.
reboot to recovery. In a terminal, do: fastboot devices <return> to check for your phone.
in recovery, press the power button for 3 seconds - at 3(onethousand), press the vol up button as well, for 2 more seconds
after you count 5, release the buttons and you should see a new menu - one of the items says to enter fastboot - that is fastbootD. If you attempt the power and vol up button task and it doesn't work, do it again - it works. SOmetimes it takes a time or 2 to catch it right. In any case, enter this fastboot. one onethousand...
FastbootD!
now, back in your terminal, flash the new boot image that magisk made for you. So: fastboot flash boot FILENAMEOFNEWBOOTIMAGE.img
following the successful flash, enter: fastboot reboot in your terminal - you may unplug your phone.
Success!
bronkish said:
If I remembered how I got to the firmware, I would have linked it, sorry - I do not. The filename is: XT2063-2_RACER_RETUS_10_QPD30.114-80_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. No doubt I followed a thread here.
1 - obtain firmware, extract the archive, make a .tar archive of the boot.img file
2 - request bootloader unlock code from motorola (you must create an account)
3 - unlock bootloader
4 - install magisk manager
5 - in magisk, top section, install: patch file - feed it the boot.img.tar file you made. It will spit you out a new tar file
6 - in fastbootd, flash the patched boot.img file
you are rooted, unless you flashed in fastboot - you must flash the patched boot.img file in fastbootd
Click to expand...
Click to collapse
I remembered how you got to the firmware
Click this link thing down below the here.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You'll be rooted in no time. Careful, now.
** USE THIS AT YOUR OWN RISK.
** READ THROUGH THE STEPS BEFORE ATTEMPTING. IF AT ANY POINT WHILE READING THESE STEPS YOU GET CONFUSED, YOU PROBABLY SHOULDN'T ATTEMPT THIS.
** BACKUP YOUR FILES AND APP DATA AS THIS WILL WIPE YOUR PHONE.
** BACKUP YOUR WORKING MODEMST1/2 AND PERSIST PARTITION IMAGES WITH BEFORE CONTINUING. THESE PARTITIONS ARE DEVICE UNIQUE, SO IF SOMETHING HAPPENS TO THESE PARTITIONS DURING THE CONVERSION, AND YOU DON'T HAVE A BACKUP, NOT EVEN MSM DOWNLOAD TOOL CAN SAVE YOU. YOU'LL HAVE TO SEND YOUR DEVICE BACK TO ONEPLUS FOR REPAIR. If YOUR PHONE IS ALREADY ROOTED, I RECOMMEND USING PARTITIONS BACKUP AND RESTORE TO DO THIS. JUST REMEMBER TO COPY YOUR BACKUPS OFF YOUR PHONE BEFORE YOU GET STARTED.
** BE SURE TO HAVE MSM DOWNLOAD TOOL AT THE READY FOR IF SOMETHING DOES HAPPEN. FOR THE T-MOBILE ONEPLUS 9, YOU CAN GET IT HERE: https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/
THIS METHOD REQUIRES AN UNLOCKED SIM AND BOOTLOADER
If you don't wish to unlock either, craznazn has released a MSM conversion package you can use to acomplish the same thing without requiring ether to be unlocked. Just download the package from their post, and follow the steps on their 8T MSM Conversion guide, as the steps should mostly be identical.
* I've successfully done this ONCE on my own personal T-Mobile OnePlus 9
* The script used here is just the same one made by craznazn to convert the T-Mobile OnePlus 9 Pro to EU firmware. I just swapped EU OnePlus 9 Pro images for the Global OnePlus 9 images and wrote a bash script for non-Windows users to use. You can just download my conversion package and follow their steps if you want. Just for convenience I'll also be writing the steps on how to use it here as well.
* You can drag and drop my bash script into craznazn's conversion package to use their package on non-Windows systems. You can download the bash script by itself here: https://gist.github.com/Lomeli12/73825a287d3cf60414e244aece9b6bdf
* This package will install Global Firmware 11.2.2.2. You'll need to use Oxygen Updater to update it to the current version (or at least until System Update can do it for you).
* Use the latest platform tools, either from https://developer.android.com/studio/releases/platform-tools or through your package manager of choice (apt, brew, scoop, etc). DO NOT USE MINIMAL ADB, it has not been updated for years.
* If you're having issues with either adb or fastboot detecting your device, consider installing the Universal ADB Driver.
* Have any issues? Describe the steps you take, copy the script's output log, and take screenshots. Include the output of fastboot --version in your post.
Now with all that out of the way...
Steps to convert your T-Mobile OnePlus 9 to the Global (or other) firmware
Unlock your bootloader and SIM. See https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/
Download and unzip the conversion package:
Global 11.2.2.2
MD5: 14e0c5e41df26bacbc11fe7e69a63c0e
SHA256: 10801f12c50e2d9a7e8085d113ac4a90ab312018beb84a10fa4c1a0f84fc95eb
Google Drive: https://drive.google.com/file/d/1h7Hpbde40wLYynUIo83TTIoERhA_04nS/view
AndroidFileHost: https://www.androidfilehost.com/?fid=2188818919693806454
Spoiler: If you want to use a newer or different region firmware, delete all the *.img files from my conversion package and do the following:
Download and unzip the firmware you want from the OxygenOS Repo thread. You'll specifically want to extract the payload.bin file.
Install Python 3 and Python Protobuf. Figure out how to do this on your own system.
Download cyxx's extract android ota payload script from GitHub: https://github.com/cyxx/extract_android_ota_payload/
Place the payload.bin you extracted earlier into the same directory as the extract_android_ota_payload.py script.
Run the extraction script and wait. This step usually takes a while to complete
Bash:
python3 extract_android_ota_payload.py payload.bin tmp/
Open up the tmp folder the script created and copy all the image files from there over to where flash_all scripts are located.
Boot to bootloader
From adb:
Bash:
adb reboot bootloader
From fastboot/bootloader:
Bash:
fastboot reboot bootloader
Execute either flash_all.bat or flash_all.sh from the unzipped conversion package.
Reboot into recovery and wipe everything
Once fully booted and setup, use Oxygen Updaterto update your phone to the latest version the app provides. Oxygen Updater will provide steps on how to use the full OTA zip.
After you've updated using Oxygen Updater, go into Settings -> System -> System Updates and check for new updates, as Oxygen Updater usually takes a few days to have the absolute latest OTA available. If there is another update available, go ahead and let the System Updater do its thing.
Do a regular system reboot, NOT into recovery, bootloader, or fastbootd.
NOTE: The following steps (8-10) may or may not be optional, we haven't 100% figured it out yet
Repeat step 3 to get back into the bootloader.
Flash the T-Mobile modem included in the conversion package
Bash:
fastboot flash modem NON-HLOS.bin
After each full OTA you take in the future, repeat steps 8 and 9 again.
Fixing SafetyNet by installing Magisk
When I first did this on my own phone, my phone would fail SafetyNet, specifically with a CTS Profile Mismatch. Once I installed Magisk and enabled MagiskHide, however, SafetyNet was passed once more. No MagiskHidePropConfig or UniversalSafetyNetFix required. Here are the steps I did.
Make sure you've updated your phone to the absolute latest version of OxygenOS you can. See step 6 of the conversion steps on how to do so.
Copy the boot.img from the conversion package onto your phone.
Install Magisk Manager onto your phone.
Open Magisk Manager and patch boot.img
Tap Install
Select Select and Patch a file and tap Let's Go
Choose the boot.img file we copied over and hit okay
Once the patch is finished, copy the patched boot.img back onto your PC. Magisk Manager usually puts it in your phone's downloads folder as magisk_patched-<current magisk version>_<random string of characters>.img. The logs in Magisk Manager will tell you exactly what it named the patch image as.
Boot to your bootloader. See step 3 of the conversion steps for this.
Boot your phone using the patched boot.img
Bash:
fastboot boot magisk_patched-<current magisk version>_<random string of characters>.img
Once your phone has booted up, open Magisk Manager once more
Go into Magisk Manager settings and enable MagiskHide.
Back out of the settings and install Magisk via Direct Install
Reboot your phone normally. You should now have Magisk and pass SafetyNet.
Issues so far:
Using EdXposed Hide on the Google Play Store or Google Play Services can cause a soft brick requiring resetting your device via recovery. No issues with LSPosed so far.
Google Phone dialer doesn't display option for Visual Voice Mail. The T-Mobile Visual Voicemail app can be used though.
What appears to work:
Everything else
Edit 1 (5/17/2021):
Fixed some wording that I felt was awkward after the fact.
Made a note that flashing the T-Mobile modem may be optional, still up in the air on that.
Included download mirror for AndroidFileHost.
Listed EdXposed softbrick reported by @Josh McGrath.
Edit 2 (5/19/2021):
Added note about VVM missing from Google Dialer, but T-Mobile VVM app being a good alternative.
Adjusted phrasing in modem flashing steps
Edit 3 (6/7/2021):
Added link to craznazn's MSM conversion tool, which is a good alternative for those who don't want to unlock their bootloader.
Excellent. I've been waiting for this. For partition backup, using the MSM readback functionality (password is usually oneplus) is also an option.
If the OP9 is anything like the OP8T, a direct Euro conversion would be better for quicker updates.
Getting to Euro from Global in a GUI-based approach is also possible. Just set the device ID to OnePlus 9 (EU) in Oxygen Updater and follow the rest of the main guide. You might need to enable advanced settings and ignore device mismatch warnings though. Assuming you are already rooted at this point, you can keep root after the local upgrade, but before rebooting, by flashing Magisk to the inactive slot. Modem still needs to be reflashed.
Modem in general is going to be a pain. Somebody will need to extract it from each T-Mobile OTA if you want fixes and new carrier aggregation combos.
Note: I have not tested this and this is not advice. Follow at your own risk.
He said the TMobile modem files were in the download. Are those 2 files not the correct ones or something?
Or are you just talking about updating the modem every time Tmo sends out an update. (which is usually every 3 months )
Talking about modems in OTAs.
That will be a pain to get any updated modem images, but 1) we just need one person who's willing to stay on the T-Mobile firmware and dump it. Just need to find this willing person and 2) like @Josh McGrath said, expecting T-Mobile OTAs to come frequently, especially those with substantially changes to the modem.img, might be giving T-Mobile too much credit.
Just wanted to say thank you to @Lomeli12 for this tutorial! Also..
After following this guide, and updated through oxygen updater to 11.2.4.4 then 11.2.5.5 from factory OTA . I have full 5g internet and phone signal, without ever flashing modem non-HLOS.bin.... has anyone else had this luck? or am I the only one???
Jg1234 said:
Just wanted to say thank you to @Lomeli12 for this tutorial! Also..
After following this guide, and updated through oxygen updater to 11.2.4.4 then 11.2.5.5 from factory OTA . I have full 5g internet and phone signal, without ever flashing modem non-HLOS.bin.... has anyone else had this luck? or am I the only one???
Click to expand...
Click to collapse
I also noticed this on my phone. I still flashed the T-Mobile modem.img just for network compatibility, but it is possible we don't even need the T-Mobile modem.img to begin with.
Lomeli12 said:
I also noticed this on my phone. I still flashed the T-Mobile modem.img just for network compatibility, but it is possible we don't even need the T-Mobile modem.img to begin with.
Click to expand...
Click to collapse
I know they have trouble with the pro version, so far I haven't had any issues. I will report back after the weekend and test it more while I travel, but don't think that will make a difference. Maybe others can test too!
I was about to do this but I've been using Minimal ADB of course but I downloaded platform tools from the link, unzipped it and ADB.exe won't work. It immediately closed.
Anyone had this issue?
And I didn't read that sentence correctly. Any specifics on what adb error ya got
No prob on the misreading my post bro.
There are no errors, it just simply will not stay open. It opens and immediately closed down. I've downloaded it twice already. Any idea? Win 10
Again, sorry. Completely misread the sentence. Without getting logs or anything more specific than "adb.exe isn't working", we can't really help you.
Not a problem. And yes I totally understand that. I was hoping it was a known easy fix that someone knew but I guess not. But thanks for your help anyhow and will ask again if I can't get it working and get the logs.
Just to test things out and see if adb is working, verify that you don't have minimal adb installed anymore and run
Bash:
adb devices > log.txt
and copy whatever got piped into log.txt.
Minimal ADB is too old. Follow directions.
You may need to set PATH for ADB or put everything in the same folder.
LLStarks, I said I was not using min adb. However, I was able to fix my issue by doing the exact rookie error you stated. :Facepalm.
But I got it all converted over now as of last night and everything is working great so thank you for this guide, Lomeli12.
The new edxposed has an Xposed hide option and I will say to NOT try to hide the play store or play services with this cause it soft bricked me and had to do a master reset via recovery. Just a fyi for anyone trying to hide for safety net. (I did use it for Snapchat and it works)
Josh McGrath said:
LLStarks, I said I was not using min adb. However, I was able to fix my issue by doing the exact rookie error you stated. :Facepalm.
But I got it all converted over now as of last night and everything is working great so thank you for this guide, Lomeli12.
The new edxposed has an Xposed hide option and I will say to NOT try to hide the play store or play services with this cause it soft bricked me and had to do a master reset via recovery. Just a fyi for anyone trying to hide for safety net. (I did use it for Snapchat and it works)
Click to expand...
Click to collapse
Good that you've resolved your issue. I've only tried with LSPosed without issue or triggering SafetyNet, but I'll make a note of it for EdXposed.
After replacing the flash, does the VVM voicemail in the dialer work?
After replacing the flash, does the VVM voicemail in the dialer work?
iSkyJIE said:
After replacing the flash, does the VVM voicemail in the dialer work?
Click to expand...
Click to collapse
Can confirm Visual Voicemail does work, so does the Dialer.. Although, i don't recognize the dialer as the oneplus stock one... someone else may be of better use for an answer for that, as I have never used the stock dialer. Although, one slight issue with the conversion.. And it doesn't seem as if anyone else is having this problem.. After I updated to 11.2.4.4 via oxygen updater, I can't get OTA to work.. It starts for two seconds and says Update Failed.. I'm not sure what I could have done wrong, I followed the steps 100% and the only thing I could think of that could have caused it is that when I rooted before this process (while still on the T-Mobile ROM), I accidentally flashed the boot.img from the EU version instead of boot it. I tried to flash the boot img that was in the ZIP package from the download above, and still didn't fix it. Hoping I or someone could figure this one out.