Hiya folks.
Well that was a fun brick - And I still don't really know what I did wrong.
I have a T-Mobile LE2127 and it was on Android 12 - I don't need to use it yet, so I am happy to play with it. Bootloader and SIM are unlocked, I can fastboot boot magisk_patched-25200_JdBlm.img to get root, and I can fastboot twrp-3.6.2_11-0-lemonadep
In TWRP-3.6.2 I used dd to grab the boot.img dd if=/dev/block/bootdevice/by-name/boot of=/usbdrive/boot.img and I patched that with the latest Magisk (1)
I tested to see if that would boot up with a fastboot boot and it worked fine - Sooo, I decided to "fastboot flash boot" it and then everything went very wrong.
The boot told me: "Qualcomm CrashDump Mode / da-verity device corrupted / verify_ctr" -- And then it went into an infinite bootloader loop which wouldn't let me into EDL mode (2)
When I was in the infinite loop, I couldn't "fastboot boot" anything, it told me it wouldn't load anything with: error: FAILED (remote: Failed to load/authenticate boot image: Load Error)
Eventually, I used the very useful MSM/lemonadept_22_O.04_210409 package to recover it and now it's working again. (3)
So - What did I do wrong? -- I suspect it may have patched my boot to slot B but I am not sure that should have mattered too much, I popped one back into Slot A as well.
I see a thread on using "adb reboot "dm-verity enforcing" but I didn't have to do that with things I booted from rather than flashed... And I couldn't get into adb at that point anyway. Does this mean my patched boot.img will not do what I want it to anyway?
Anyway, I should stop speculating and ask the experts!
Thanks.
(1) https://www.droidwin.com/extract-boot-img-directly-from-device-without-downloading-firmware/
(2) https://www.droidwin.com/boot-oneplus-9-pro-9r-9rt-to-edl-mode-5-methods/
(3) https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/ -- [No instructions, but just run it as admin, connect phone and it does it all].
What I do is in bootloader mode, fastboot boot twrp, in twrp I install magisk.zip, then reboot system and tap on magisk app and follow prompts. Done
If you have the boot image, place it in your root folder on the phone. Use the magisk manager app ( install on phone) to patch the boot.IMG. Place the patched boot.IMG on your PC. Should be in downloads folder. Fastboot boot this patched IMG. It should boot your phone. Go to magisk manager app and install magisk directly. ( option in manager install). Reboot -- done.
kjslabber said:
If you have the boot image, place it in your root folder on the phone. Use the magisk manager app ( install on phone) to patch the boot.IMG. Place the patched boot.IMG on your PC. Should be in downloads folder. Fastboot boot this patched IMG. It should boot your phone. Go to magisk manager app and install magisk directly. ( option in manager install). Reboot -- done.
Click to expand...
Click to collapse
Ah! That worked and was very simple, thanks... For some reason in my head, I was thinking that Magisk would only patch the booted image, which would be pointless; but it patched the real phone one.
I assume I'll just have to do the same every update.
Thanks!
Related
I'm on fw Global 9.6.6.0.
(Bought the phone 'bogus' unlocked with "fake" 9.6.4.0, bricked it while trying to restore chinese fw and re-lock bootloader using miflash - I'm not doing that again
brought it back to life using the steps from Omer919's thread - thanks Omer919 and Nijel8)
I deleted install-recovery.sh from system/bin using TWRP's file manager before first boot, but it still overwrites MIUI recovery.
It's not a huge deal because I guess I can always fastboot flash twrp before flashing any new ROM, but does anyone have a solution? Much appreciated!
You have to boot to twrp right after flashing.
Go to twrp official site, choose your device and follow exactly instruction to the end.
It wouldnt harm your device if you reboot it to twrp twice.
Thanks, I tried but it reverts to stock recovery. After flashing TWRP in fastboot, I either try Fastboot boot twrp.img or disconnect the cable and hold power and vol+.
Either way, it goes into TWRP, and I make it boot back into TWRP several times with no problem.
But as soon as I boot to System, it reverts to stock.
TWRP site gives me this info (but it didn't work):
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
OMG I found it - Google really is a friend. All I had to do was install Magisk before booting to System.
Below are my exact steps, if that helps someone.
Preliminary:
Download Magisk 17.1 zip, place it on a USB flashdrive.
Install latest magiskmanager apk from Play store (or sideload it if not on the store)
1- In Fastboot:
fastboot flash recovery twrp.img
fastboot boot twrp.img (If all goes well, this boots to TWRP; if prompted for a code, hit cancel)
2- Disconnect the cable.
Reboot to recovery once more (just to make sure, this is probably redundant; hit cancel if prompted for a code)
3- Mount USB-OTG, connect your flashdrive.
Install Magisk.
During the installation, you'll see some red fail lines, but Magisk seems to work around the encryption, just be patient.
4-Reboot System. You're done! Launch MagiskManager. Device is rooted in the process, too. (Verify with a root checker app).
Power Off. Hit Power + volume Up - You should boot to TWRP.
thanks a million McNoob. I was lost, but due to your hints I managed to install Magisk
Hi i cant boot to twrp and it keeps reverting to stock recover..
already tried this "fastboot flash recovery twrp.img
fastboot boot twrp.img (If all goes well, this boots to TWRP; if prompted for a code, hit cancel) "
after sending the last command line the phone reboot but its just black screen.. i try to reboot the phone again and boot it to recovery but still stock recovery is preset.. thanks
Thanks man! It worked for me as well!
Lamantin001 said:
Thanks man! It worked for me as well!
Click to expand...
Click to collapse
How did it work for you
thanks but.... the twrp for nitrogen is corrupted apparently and nothing work
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Thanks so much! Will try this out! Nice work!
Thanks, after i root my mix 3 can i flash the xiaomi.eu rom on it too without problems ?
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
PJF16 said:
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
Click to expand...
Click to collapse
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Please report back your success and how it goes for you!
SacredSovL said:
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Click to expand...
Click to collapse
It's risky and something I won't be trying, I would wait for TWRP
Hi PJF16
How did you get the boot.img from your device without root? I'd love to make a unmodified copy before trying this out
I got it from the fastboot ROM which I also uploaded to the forum. See here: https://forum.xda-developers.com/mi-mix-3/development/xiaomi-mi-mix-3-fastboot-roms-t3869532
Tested and 100% working! Recommended
smiba said:
Tested and 100% working! Recommended
Click to expand...
Click to collapse
Did u flash xiaomi.eu rom or something else ?
PJF16 said:
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Click to expand...
Click to collapse
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
souless poet said:
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
Click to expand...
Click to collapse
Nevermind figured it out...duh.
Not working on 8.11.15 dev china rom...
Patched boot is much smaller than it should be and after flashing and fastboot reboot command, phone goes back to fastboot mode
It's normal that the patched boot.img is smaller.
PJF16 said:
It's normal that the patched boot.img is smaller.
Click to expand...
Click to collapse
I know that.
But this is quite smaller than usual and, anyway, it doesn't boot after flashing
Anyone have any issues with v4A magisk module? After I flashed it I lost the ability to turn on wifi. Wondering if anyone else has had that issue.
where can i find the pre patched boot img of 10.0.12.0?
Just use the one for 10.0.11.0.
nosidefcp said:
where can i find the pre patched boot img of 10.0.12.0?
Click to expand...
Click to collapse
Hi, here You can find patched boot for 10.0.12.0:
https://yadi.sk/d/aVlSEC_r7xj0VA
Any help would be appreciated. This is my first time dealing with Magisk, I've always used SuperSU in the past. I finally used my unlock code and the bootloader says unlocked, that was easy. I installed the Magisk Manager apk but am having trouble with Magisk itself. I'm used to flashing in TWRP, which I apparently can't install until Magisk is installed. I have two options, install - download zip only, and patch boot image file...
So I was trying to use the boot image file from this thread https://forum.xda-developers.com/mate-20-x/development/guide-mate-20-x-root-t3883269 and either patch it or used the patched one, but when my phone goes into the bootloader screen, adb is not recognizing the phone or finding the file which I set inside the adb folder itself. Sorry, I am not a noob to flashing. Done many many phones rooting, unlocking, roms, modems, etc. I am just new to adb and Magisk. Any help would be great as I've been at this all day reading and downloading things I needed. Thank you.
EDIT: I'm not sure if I'm putting the .img file in the wrong folder??? I am stuck on step 5 in that thread.
So more specifics on where I am stuck, hoping for help. I've tried, tried and tried and Googled lots...
When I run fastboot devices it does show my phone. I took the Patched Recovery Ramdisk for EVR-AL00 from the site above. I renamed it to recovery.img and put it inside the folder c:\adb where adb and fastboot are located. When I am in the command prompt under c:\adb> I put "fastboot flash recovery_ramdisk recovery_ramdiskMagiskrecovery.img". And I get this error... fastboot: error: cannot load 'recovery_ramdiskMagiskrecovery.img': No such file or directory
DavidMT909 said:
So more specifics on where I am stuck, hoping for help. I've tried, tried and tried and Googled lots...
When I run fastboot devices it does show my phone. I took the Patched Recovery Ramdisk for EVR-AL00 from the site above. I renamed it to recovery.img and put it inside the folder c:\adb where adb and fastboot are located. When I am in the command prompt under c:\adb> I put "fastboot flash recovery_ramdisk recovery_ramdiskMagiskrecovery.img". And I get this error... fastboot: error: cannot load 'recovery_ramdiskMagiskrecovery.img': No such file or directory
Click to expand...
Click to collapse
If you renamed the file recovery.img then the command should be
'fastboot flash recovery_ramdisk recovery.img'
lightning413 said:
If you renamed the file recovery.img then the command should be
'fastboot flash recovery_ramdisk recovery.img'
Click to expand...
Click to collapse
Thank you, but I may have messed up my phone now. I was trying this from the thread above, and even his example shows Magisk in it.
Step 5:
-Once the device is in bootloader and connected to the PC, run the command "fastboot flash recovery_ramdisk recovery_ramdiskMagiskVARIANT" with VARIANT being whatever ramdisk you downloaded. For example with AL00 you would input "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00.img"
As soon as I tried your way it seemed to work... except when I booted it still did not have root. And now I cannot get into fastboot or recovery. It just keeps rebooting to the phone if I try recovery or fastboot. I used to be able to do this stuff following directions. It just doesn't seem to be working out. Thanks for trying.
My devices still lists in adb, but not fastboot. I'm still working on this. I do make an effort to do things myself.
Okay, I don't know what happened. My Magisk had an update, I installed it and rebooted and for the first time two green checks in Magisk, ran root checker and I have root. So hopefully I can install TWRP now and on to the ROM. Slow progress...
I have TWRP. Time to make a backup, and I'll install a ROM next.
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixelxl.img
You will boot with root but modules disabled. If something additional is needed, once booted to core-only, unzip the attached zip onto your pc where you can run ADB/fastboot and run the bat file. It will push .disable_magisk to your cache folder so that your modules will be disabled even after a reboot (zip says crosshatch but will work on any phone)
Boot image uploaded 11-4-19
https://www.androidfilehost.com/?fid=4349826312261618461
Hey so this would save my life but the boot image attached couldn't be flashed through fastboot and then I realized that the flashing command is mispelled. It should be
fastboot flash boot image....img
So this file didn't quite work, it makes Magisk Manager crash so I can't uninstall a conflicting module. I tried flashing the latest boot.img from the december update and it's enough to boot the phone but it disables magisk, obviously. Is there anyway you can update this file to the latest image? Pleaaaase
EDIT: I ended up reflashing the magisk patched image and manually deleting the folders of my conflicting modules.
For those who can't root via TWRP or somehow lost root while updating (like I did), I have a patched boot image to aid others in this endeavor. This is a boot.img from a T-Mobile 7T which I had converted to the Global ROM, extracted and patched by Magisk after applying the latest update (10.0.13.HD65AA). Fully tested and working!
Instructions:
Unzip and place it in a convenient folder (ie, C:/adb/ or whatever's easy to remember.
Open a cmd prompt and navigate to your fastboot/adb folder.
Then run the command
Code:
fastboot boot boot.img
Your phone will be "temp-rooted" once it boots. If you haven't already, install Magisk Manager, then flash Magisk itself (ALWAYS do direct install!).
Don't install any modules yet. Just reboot when prompted after the Magisk flashing process is done.
Profit!
Download from Google Drive
[I dunno where else to upload this that XDA would consider "safe," so GDrive it is, I suppose.]
Spoiler: Process for manually patching the boot.img without TWRP:
Requirements: Stock device with unlocked bootloader only (no other mods), most recent OTA update applied and system rebooted. Fastboot and ADB Windows executables.
1) Enable advanced reboot and usb debugging in developer options.
2) Reboot to bootloader.
Code:
adb reboot bootloader
3) Boot to twrp
Code:
fastboot boot twrp.img
(or whatever you named it).
4) Once booted, enter:
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the PC:
Code:
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to Android.
6.5) Copy boot.img back to phone:
Code:
adb push stock_boot.img /sdcard/boot.img
7) Make sure you have a data connection.
8) Install Magisk Manager.
9) Select option to install Magisk (not the Magisk App). Choose "Select and Patch a File."
10) Point to the boot.img.
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) Copy this file to your PC, either using MTP or ADB.
Code:
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode again.
Code:
adb reboot bootloader
14) Boot the patched boot from step 12:
Code:
fastboot boot magisk_patched.img
15) Launch Magisk Manager again. You should see the current version available and the installed version below that now. If all is good, choose to install/update Magisk, then "Direct install" and reboot when finished.
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
>Akshay< said:
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
Click to expand...
Click to collapse
OH! You're right. I goofed. I'll ask a mod to move it.
This will delete all the data from the phone + bootloader needs to be unlocked?
Brontok said:
This will delete all the data from the phone + bootloader needs to be unlocked?
Click to expand...
Click to collapse
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
GuyInDogSuit said:
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
Click to expand...
Click to collapse
never mind!
someone already did!
https://forum.xda-developers.com/showpost.php?p=83780229&postcount=12
thanks anyway!
Will this work for 10.0.13 tmobile ? Thanks
gershee said:
Will this work for 10.0.13 tmobile ? Thanks
Click to expand...
Click to collapse
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
GuyInDogSuit said:
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
Click to expand...
Click to collapse
Thanks!
Worked like a charm.