Related
Devices that started to be received today have Oxygen OS 10.5 out of the box.
No flashable zip for that software release is publicly available, meaning its stock boot.img cannot be extracted.
You then need to update to a newer build first. You can do so from my OxygenOS builds repo thread.
Once done, enable developers options and enable OEM unlock.
Reboot to fastboot (enable USB debugging in dev options and use adb reboot bootloader)
Type fastboot oem unlock and accept to unlock bootloader (warning: as a safety measure Android will wipe your userdata)
Go through OxygenOS setup
Install Magisk Manager from https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
Move stock boot.img to your phone internal storage (please open spoiler)
For your convenience, 10.5.2 stock boot.img for EU and India have been extracted
EU download: https://drive.google.com/file/d/18aPqErEMbRqmN4BpdvHE4OKgizDcEbou/view?usp=sharing
India download: https://drive.google.com/file/d/1ZIEYWH2PYkKyojq_S_i_onBstejHKDTJ/view?usp=sharing
For future builds, you can use payload dumper (Windows) , (Linux ) to extract stock boot.img
Click on Install
Choose "Select and patch a file"
Select your stock boot.img
Wait until Magisk patches your boot.img, and once patched it can be found in the Downloads folder
Copy that patched boot.img (which should be named magisk_patched.img) to your computer
Boot into fastboot again
Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.
Reboot to OxygenOS
Open Magisk Manager and your device should now be rooted.
TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
Credits:
@topjohnwu for making Magisk
/u/Jisifus for testing on his device and for screenshots
Some_Random_Username said:
TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
Click to expand...
Click to collapse
Great to see it works this way and thanks for the tip.:good:
do u lose all data while rooting?
#edit1
nevermind, cannot read right
OK, will give this a try asap,have the device here now...
I gave it a try, works like a charm! Thanks for this! Small tip, unlock bootload before u copy your files
now my phone is a bit laggy. with magisk on it.. i will test it later if its getting better
Some_Random_Username said:
Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.
Click to expand...
Click to collapse
You can simply type "fastboot flash boot magisk_patched.img" - it flash boot to current active slot. Just for note.
Can confirm that it works, just tried it myself
If WiFi/data does not work (usually happens when you flash wrong version, but can also happen if you flash correct one), fastboot boot the image, then do a direct install in Magisk Manager.
Also, big thumbs up for adding tips for persist backup, I see too many people needing to send their device back because they messed it up somehow.
Failed for me
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
jmwengineering said:
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
Click to expand...
Click to collapse
The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.
jmwengineering said:
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
Click to expand...
Click to collapse
And that's why it's recommended to boot the patched image first.
Thanks
Lossyx said:
The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.
Click to expand...
Click to collapse
Thanks for confirming file size - Preserve Force Encryption and Preserve AVB 2.0/dm-verity were ticked during the patching process. Guess I'll have to wait until TWRP is verified as Nord compatible.
---------- Post added at 07:06 PM ---------- Previous post was at 06:59 PM ----------
Kollachi said:
And that's why it's recommended to boot the patched image first.
Click to expand...
Click to collapse
Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!
jmwengineering said:
Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!
Click to expand...
Click to collapse
Nah, instead of flash the patched boot image you can boot it only. Not sure why it's not working for you. But usually it should work.
Command: fastboot boot "patched boot image"
Edit: that's also what lossyx said. Boot image and than install it with magisk manager.
And if you boot the image and something went wrong you aren't bricked or anything. It's a safe way to test something.
Thanks for the advice - will boot the image file on my PC rather than flashing first.
Sent from my AC2003 using Tapatalk
Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P
..
CryllicBuster273 said:
Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P
Click to expand...
Click to collapse
Yeah I guess when you unlock your phone it will break L1 as always.
---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------
DIR49DNOR0N said:
I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-nord/how-to/oneplus-nord-repo-oxygen-os-builds-t4138085
DIR49DNOR0N said:
I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?
Click to expand...
Click to collapse
No, keep the bootloader unlocked if your phone is modified, else it can cause some issues.
Btw when you lock/unlock the bootloader, data will be wiped. apps will be reinstated again so that's useless
The guide worked perfectly and I'm up and running with Root!
One thing I have noticed is that the Google Play store is no longer Play Protect Certified.
I've tried registering my device with Google using this XDA guide but I haven't found any change to the Play Store certification.
I should probably wait for a while to see if the registration takes some time. I also couldn't use the adb commands that Google recommends and I had to use the Device ID app to get the Google Service Framework (GSF).
I've read in a few places that it may be because the Bootloader is unlocked and I'm wondering if I should re-lock it now that I have root. Not sure how/if that will affect my ability to keep root when future updates come out though.
Anyone have any thoughts/experience with this?
Possible TWRP without waiting?
Can anyone use this and try? Might be used as an alternate Method for Rooting via TWRP
https://forum.xda-developers.com/an...g/guide-how-to-port-twrp-to-qualcomm-t3420013
Dear Community,
I'm trying to root my Ulefone Armor X7 Pro using Magisk and so far I've experienced several issues, starting with unlocking the bootloader.
I hope you can help me somehow.
Here's what I've done and seen so far:
- OEM Unlock enabled and USB Debugging enabled
- Using ADB from latest Google SDK to reboot in FASTBOOT mode
- Now 'fastboot oem unlock' returns FAILED (remote: 'unknown command'). I've tried to wipe cache partition, it doesn't help, I've tried a few workarounds found on this forum with no luck so far...
- I've read that sometimes this command doesn't work so I used 'fastboot flashing unlock' instead --> that one worked
With this done, and stock boot.img, the phone will display an Orange State warning saying that the device can't be trusted. However it will boot anyway (with the stock boot.img).
Also, the OEM Unlock option will be greyed out in developer options after performing this command.
- However, after flashing the boot image that Magisk Manager generated (from the stock boot.img from Ulefone website), the phone goes into a boot loop with a Red State saying that the boot signature is wrong and verified boot should be disabled. (However I don't know how to do this.)
So I flashed back the stock boot.img and could reboot my phone again (at least it is not bricked -- but that was scary).
Now, here are my questions and thoughts:
- Is it normal that 'fastboot oem unlock' won't work? Is it fine to use 'fastboot flashing unlock' instead?
- The boot image generated by Magisk is only 10 MB while the stock one is 32 MB. I've read the thread of issue #2005 Pad Images to Original Size With Zeros on Github and I thought maybe that's why the phone won't boot with the Magisk image. But I don't know exactly what I should do about it. (I'm on Windows.)
- Finally, if the solution is to disable verified boot, how should it be done? Is there anything to do with the 'Preserve AVB 2.0/dm-verity' option in Magisk Manager?
I hope you'll be able to help me and I wish you all the best anyway.
Thank you.
same deal
- It's never been an issue for me if 'fastboot oem unlock' doesn't work. In fact, in my experience (which isn't really that much), it never works. I've always had to use 'fastboot flashing unlock'
- I tried padding the image with zeroes using
Code:
dd if=/dev/zero of=magisk_patched.img bs=1 count=1 seek=33554431
(on a linux box), but it produces the same bootloop. I've tried this same thing with recovery, no such luck.
- I tried flashing via SP Flash Tools, as well. Both the padded and non-padded magisk_patched.img; neither worked. I updated checksum.ini so that flash tools would accept the scatter file. I've tried formatting the section, as well as the 'write memory' tab. SPFT flashes it just fine, but the bootloop continues.
- I even tried patching and flashing boot-debug.img (because why the hell not?) and again, the loop goes on and on.
- I opened up the preloader....bin file in hex editor and removed all instances of 'verify' and flashed via SPFT. Do not do this. The phone will no longer turn on or anything. Luckily, SPFT flashes before anything else in the phone does anything, so it was recovable.
- I tried sideloading my rom as an 'update' but oddly enough adb won't recognize the phone in sideload.
I haven't tried reflashing the whole phone with magisk_patched.img as my boot. I may attempt this. I'll get back to you if I have any luck.
I plan on using mine as a media device (music, video, camera, etc) that I can bring with me on excursions, because I'm terrified to bring my pixel 4xl.. As such, I don't have a SIM card in mine. I have no idea if this would make any difference, but I'm not receiving the 'red state' status saying that verified boot is the issue. I have tried it with unchecking dm-verify, but maybe this hasn't worked. I'm thinking that it may have something to do with vbmeta*.img files. Like I said, I'll let you know if I have any luck
lunalsmojo said:
Like I said, I'll let you know if I have any luck
Click to expand...
Click to collapse
I'll do the same. Thank you for your feedback!
0
success!
vbmeta.img was the issue! I have successfully rooted via magisk!
What you need to do is first flash an empty vbmeta.img file. You can download one by doing a Google search for "mtk empty vbmeta.img"
Just ignore the stuff for TWRP (unless you want to go that route too). Down toward the bottom of the tutorial, there is a link to download an empty vbmeta.img. Move the image into your adb/fastboot folder (or whichever directory you are working from) Then,
Code:
adb reboot bootloader
fastboot flash vbmeta vbeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
I used the tutorial from hovatek.... I'm too much of a newb to post outside links
replace "magisk_patched.img" if you changed the name. I did mine with my padded magisk_patched.img. Let me know if you have issues with yours not being padded
THANK YOU!
lunalsmojo said:
vbmeta.img was the issue! I have successfully rooted via magisk!
What you need to do is first flash an empty vbmeta.img file. You can download one by doing a Google search for "mtk empty vbmeta.img"
Just ignore the stuff for TWRP (unless you want to go that route too). Down toward the bottom of the tutorial, there is a link to download an empty vbmeta.img. Move the image into your adb/fastboot folder (or whichever directory you are working from) Then,
Code:
adb reboot bootloader
fastboot flash vbmeta vbeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
I used the tutorial from hovatek.... I'm too much of a newb to post outside links
replace "magisk_patched.img" if you changed the name. I did mine with my padded magisk_patched.img. Let me know if you have issues with yours not being padded
Click to expand...
Click to collapse
Yes, that worked for me as well!
So, first I tried to uncheck 'Preserve AVB 2.0/dm-verity' before patching the boot.img in Magisk but this didn't work (same bootloop).
Then I patched the boot.img in Magisk with the 'Preserve AVB 2.0/dm-verity' checked, and edited the file in HxD but found no trace of '2C 76 65 72 69 66 79' or 'verify'.
Finally I resigned myself to flash the empty vbmeta.img found on Hovatek's website (blog post 'DM_Verity is probably why that TWRP flash ends in a bootloop') and flashed the non-padded boot image produced by Magisk.
And this last option worked! So THANK YOU so much for your help!
Thank you sooo much! I finally got my brand new x7 pro rooted!
Have to ask
What os is does this refer to, I take it it's android 9?
What size is your bootloader/recovery in stock folder?
What mtk version?
lecrocq said:
... Thank you.
Click to expand...
Click to collapse
Hi May I ask if after rooting did you install a custom ROM?
Does the stock android that you get contains any personalization, like MUI or similar?
phaleg said:
Hi May I ask if after rooting did you install a custom ROM?
Does the stock android that you get contains any personalization, like MUI or similar?
Click to expand...
Click to collapse
I didn't install a custom rom, but I did eventually flash the Vanilla Bless GSI by @eremitein. Magisk still worked with patched boot, runs super smooth, and offers a ton of great customizations.
The stock rom is lackluster; it's the phone itself that has a ton of cool features like the underwater camera. I haven't really checked if all of those features are still usable with the GSI. To be honest, haven't really thought of it. Haven't gotten much of my intended use out of it during coroneumonia times. Sounds like a fun investigation, though. If it doesn't work straight out, I'm sure it can be made to work with a little tinkering.
@Pachacouti sorry for response forever later.... It's Android 10 with a MT6761 (Helio A22)
Hello boys. Thanks for how to root. I have rooted, but i had to reinstall system complete. Now i have root and new system and i have sms issue. Sometimes sms is coming, sometimes no..
Hello,
I'm trying to unlock my bootloader for my new Armor 7X but i'm struggling with the fastboot command.
First, there is two "fastboot" mode with this phone :
- the first when you do an : adb reboot bootloader. There is "=> FASTBOOT mode" in the screen. In this mode I can't detect my phone with "fastboot devices" command...
- the second mode is when you power on the phone with the volume "-"and you select "enter fastboot" in the menu. In this mode the phone is detected by "fastboot devices" ! But, the command "fastboot flashing unlock" always fails.
The error :
"FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
I've tried severals adb/fastboot tools without any succes. I think it's a driver issue but I'm not sure.
If someone have an idea, I will be greatful !
https://www.getdroidtips.com/unlock-bootloader-ulefone-armor-x6/ but i dont make this command fastboot flashing unlock. On phone you must chose unlock and confirm.
Probleme Solved, Use the NON-EU ROM !
I've find the problem ! It was the EU version of the ROM that blocked fastboot, so use the NON-EU version for that.
I've have succesfully rooted my phone, thank you for this thread !
I don't know exactly what are the differences between the two versions but everything seems to work normally.
Очень интересная тема. Наконец-то дошли руки до рутизации. Чрезвычайно долго описывать свой петь не буду, но скажу одно- знаю способ получения root до перезагрузки. Оранжевое предупреждение навсегда. Я допереведу ваш способ и попроьую сделать так-же. Спасибо!
Thanks for this guide
I got root now, has anyone got TWRP installed? Or another custom recovery
Does anyone have a problem receiving SMS?
Hi all, I've got a question.
I am trying to flash the boot.img but when I download the rom files from the ulefone website for the note 8, it does not include a boot.img. I can only see boot-debug.img and boot-sign.img . Which one should I select?
CupidAlaska said:
Hi all, I've got a question.
I am trying to flash the boot.img but when I download the rom files from the ulefone website for the note 8, it does not include a boot.img. I can only see boot-debug.img and boot-sign.img . Which one should I select?
Click to expand...
Click to collapse
This is not about Note 8.
lecrocq said:
THANK YOU!
Yes, that worked for me as well!
So, first I tried to uncheck 'Preserve AVB 2.0/dm-verity' before patching the boot.img in Magisk but this didn't work (same bootloop).
Then I patched the boot.img in Magisk with the 'Preserve AVB 2.0/dm-verity' checked, and edited the file in HxD but found no trace of '2C 76 65 72 69 66 79' or 'verify'.
Finally I resigned myself to flash the empty vbmeta.img found on Hovatek's website (blog post 'DM_Verity is probably why that TWRP flash ends in a bootloop') and flashed the non-padded boot image produced by Magisk.
And this last option worked! So THANK YOU so much for your help!
Click to expand...
Click to collapse
I would also like to confirm
lunalsmojo said:
success!
vbmeta.img was the issue! I have successfully rooted via magisk!
What you need to do is first flash an empty vbmeta.img file. You can download one by doing a Google search for "mtk empty vbmeta.img"
Just ignore the stuff for TWRP (unless you want to go that route too). Down toward the bottom of the tutorial, there is a link to download an empty vbmeta.img. Move the image into your adb/fastboot folder (or whichever directory you are working from) Then,
Code:
adb reboot bootloader
fastboot flash vbmeta vbeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
I used the tutorial from hovatek.... I'm too much of a newb to post outside links
replace "magisk_patched.img" if you changed the name. I did mine with my padded magisk_patched.img. Let me know if you have issues with yours not being padded
Click to expand...
Click to collapse
I would also like to confirm that this approached worked for me without issue. Some tips that may prove useful for someone, ensure that you have the correct drivers, adb, fastboot, vcom, and cdc. I had issues using fastboot because I did not have the correct drivers, a day was wasted on this.
I also used the tutorial from hovatek, his blog post is where you will find the vbeta.img, I could not correctly flash my patched magisk without first patching the vbeta.img.
Thanks again.
I recently bought an unlocked Moto G Play 2021 with the intent of learning how to flash custom rom's etc. The steps I've done so far are below.
Went to Motorola's site and got the code to unlock the bootloader
Waited for the "OEM Unlock" button to be available in the Developer Options menu.
Followed the directions Here to try to get an unofficial version of TWRP installed.
when I type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img Using the vbmeta.img from the link above, I get some kind of anti-rollback error and can't boot to recovery.img
So far, what I've found says I need to be on Android 10 for this to work but I can't find a stock rom of Android 10 for this device. Electimon posts AOSP builds for this phone Here so I assume there's a way to get this to work, I just don't know what it is and I've gone through these threads a few times now and can't piece it together. Any assistance would be greatly appreciated.
Additionally, thanks Electimon for doing those AOSP builds.
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Luiz Vinicius said:
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Click to expand...
Click to collapse
I'm not sure entirely what happened, but after I used the TWRP app my phone bricked and I had to use the Lenovo rescue app on my pc to factory reset it.
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
svoc said:
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
Click to expand...
Click to collapse
Thank you for the response!
I made sure my phone was on wi-fi and checked for updates. I then rebooted to fastboot and flashed recovery to the MotoGuamnaFixed2.img. I still got a blank screen when I tried to reboot to recovery. I then rebooted to fastboot manually and did
fastboot flash recovery_a MotoGuamnaFixed2.img
fastboot flash recovery_b MotoGuamnaFixed2.img
It said ok both times, and when I try to reboot to recovery, I get a blank screen that I can't interact with. Pressing the power and volume buttons does nothing. Rebooting and letting the phone go through the boot process, to include waiting for the warning about the unlocked bootloader to go away results in a blank screen.
I also tried booting to fastboot and selecting "Recovery Mode" from the fastboot menu. Same result. That being said, I followed the instructions in the second link anyway, which are
fastboot -w
fastboot update (filename).zip
Now my phone has a blank screen I cannot interact with, but when I type "adb devices" I see the phone. Typing "adb shell ls -l" shows there is definitely a file structure there.
Just download the rom for the version that your device is unzip it and manual flash each one to the correct spot except recovery flash the twrp and then reboot and let me know look at flash file.xml to see where to flash each IMG and bin to make shur you download your rom and not another one for the same device but different carrier what it sounds like to me is happening is you downloaded the wrong ROM when you tried to do a force update
Send me a screenshot of your about device screen please I might need to make a change to a few things to get it working
I'm stuck in a boot loop right now. WIll the output from fastboot getvar work?
What carrier do you have
Download your rom first then follow my last post to get it back out of a bootloop
svoc said:
What carrier do you have
Click to expand...
Click to collapse
It's an unlocked phone, no carrier, no SIM. I did the factory reset with the Lenovo rescue tool and sent you the screen shot of the device info page.
Update - svoc has spent a crap ton of his personal time trying to help me with this. I've learned a bunch and wanted to publicly acknowledge his willingness to go way above and beyond trying to get this working.
I don't understand why I can't get twrp to boot I'm not for shut what the problem is if any one has any idea please let me and I will try
Big thanks to svoc for all the phone calls and troubleshooting my device, that is apparently possessed by at least 3 demons and a donkey. There are two links below. The first is the link to the intstructions that worked.
The second is to the compressed file that gave me a degoogled android. It's really, really basic and you'll have to side load the app store of your choice onto the device but it works.
*NOTE* I have not used a sim card or tested the cellular capability. If you do the things below and it doesn't work, reboot to bootloader and flash the radio.img with the one from your stock rom, which can be obtained from lolinet.
Any custom ROMs out there for Moto g play 2021 (guamna)?
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
forum.xda-developers.com
https://github.com/phhusson/treble_experimentations/releases/download/v412/system-squeak-arm64-ab-vanilla.img.xz
I followed the guide to root my device.
Everything went correctly at first. The phone was unlocked.
After I installed magisk and created the magisk patched img and then written to boot_a & boot_b, when I use "fastboot -w", it says the partition not allowed to erase and then I tried to reboot.
The device entered the recovery mode, I used reset to factory data. And it cannot boot and keeps telling me "your device is corrupt".
I cannot enter recovery mode now and when I tried to use xperia companion it told me the phone is locked.
I'm thinking flash recovery img in fastboot mode but I can't find anywhere to download its img.
Please help!
TIA
Fixed by re-flashing original boot.img
zz305 said:
I followed the guide to root my device.
Everything went correctly at first. The phone was unlocked.
After I installed magisk and created the magisk patched img and then written to boot_a & boot_b, when I use "fastboot -w", it says the partition not allowed to erase and then I tried to reboot.
The device entered the recovery mode, I used reset to factory data. And it cannot boot and keeps telling me "your device is corrupt".
I cannot enter recovery mode now and when I tried to use xperia companion it told me the phone is locked.
I'm thinking flash recovery img in fastboot mode but I can't find anywhere to download its img.
Please help!
TIA
Click to expand...
Click to collapse
Remove the "system_ext.." line from fstab, this may solve your issue if is the same issue for xperia 1ii. See link https://github.com/topjohnwu/Magisk/issues/3752
For fastboot command fail, does your device have fastbootd?
zz305 said:
I followed the guide to root my device.
Everything went correctly at first. The phone was unlocked.
After I installed magisk and created the magisk patched img and then written to boot_a & boot_b, when I use "fastboot -w", it says the partition not allowed to erase and then I tried to reboot.
The device entered the recovery mode, I used reset to factory data. And it cannot boot and keeps telling me "your device is corrupt".
I cannot enter recovery mode now and when I tried to use xperia companion it told me the phone is locked.
I'm thinking flash recovery img in fastboot mode but I can't find anywhere to download its img.
Please help!
TIA
Click to expand...
Click to collapse
Reflash the whole FW again.
Hi, here I bring you a small tutorial for upgrading your rooted Realme GT 2 Pro Global Version to latest update (RMX3301_11_A17), as you may know I am not responsible of any damage and I recommend you to back up your data.
First, uninstall all your modules from magisk (technically you could just deactivate them, I prefer uninstall though). Make sure Zygisk is deactivated and turn off all the super user permissions of your apps before the update step. You should deactivate Automatic system updates under developer settings as well.
Here the steps:
1. Go to settings and download the OTA, you´ll get the 200 mb one. Since what we need is the full OTA package, once it's been downloaded when it starts to be extracted force stop the Software Update app in your settings.
2. After previous step go to your file manager (in this case I use Mixplorer, for this you will need the app with root access) and go to the next directory: root/data/ota_package/OTA/ [a folder that starts like .ota], inside you are going to delete the ota file with .zip extension. This first two steps are a way to speed up the process of getting the full OTA.
3. Go again to your software update section in settings, you will see a notification from the app software update app, touch on continue. After that you will see a message of error, and you will see a button that says "Try again", keep clicking on try again several times. You'll see then that full OTA update will start automatically (about 5 gb in size).
4. From here you will have to wait until the "Install" button appears (it'll take a while). Next, you click install.
5. After reboot, transfer the boot.img file attached on this post to your device. Magisk patch it and transfer back to your PC.
6. Open your adb terminal, type the command adb reboot bootloader
7. Test recognition by typing fastboot devices
8. Next type: fastboot boot whatevernameofyourpatchedfile.img (it has to be in the platform tools folder)
9. Your device will boot with a temporary root, check everything is working ok in your device. After that you will go to magisk app, click on install, and in the Method section select "Direct Install", and then Let's go.
10. After reboot you'll have you magisk rooted device updated and working. Now you can install back your modules again.
boot
This method can be done on the phone with root preservation directly via Magisk. No need to copy/patch boot.img files manually, as long as you have restored image in Magisk at least once. This is explained below.
Important notes:
Do not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and patched boot.img must be flashed via fastboot to restore root.
In addition, after installing to inactive partition in Magisk, do not press restart on Magisk's prompt.
The auto-update should be disabled, including the "Auto Download" setting. Otherwise, the updater will attempt to download and install while Magisk is present, and show "Extraction Failed" error, and "Try Again". If that happens, the system will only allow to download a 5GB update instead. To reset it, you can clear Software Updater app data and cache via some root app manager.
When selecting "Restore Images" in Magisk, if a message shows in Magisk "Stock boot image not found", then you need to generate backup stock boot.img on the phone. This is only done once, but you will need a stock boot.img of your current ROM version.
- Copy current ROM version stock boot.img to storage
- Open Magisk and select install -> Patch file -> Select the stock boot.img
- Restart phone.
This will generate Magisk "backup image" folder where it will keep the stock, non-patched boot.img.
This is only done once, on any future update the error will not show.
Click to expand...
Click to collapse
The 300mb OTA update steps:
1. Go to updater and it should show 300-600mb update available. DO NOT press "Download"!
2. Go to Magisk, select to restore image. Do not restart when prompted by Magisk. If you get error, read note on top.
3. Go back to updater and select "Download". It will first download then extract. When it finishes extracting, DO NOT press Install!
4. Go back to Magisk and select install to inactive partition. Once it's done, do not restart via Magisk! Close Magisk.
5. Go back to updater, and press "Install" button
Click to expand...
Click to collapse
Extra notes:
1. If you press Download before removing Magisk, it will fail extracting and show "Try Again". Do not press try again. Go to a root app manager, and clear Data and Cache of com.oplus.ota Software updater. Then repeat the process by restoring images in Magisk first.
2. If you did press "Try Again", it will only allow you to download a 5GB update. Steps are similar as long as you restore Magisk. You might be also able to clear data and cache like in step above to reset it back to smaller update, but I haven't tested this yet.
3. If you restart by Magisk prompt, it will soft-loop. You can hold Vol Up + Power until it boots into non-root partition. Go to updater and press install. It will boot to rooted partition.
4. If you pressed Install in updater before installing Magisk to inactive partition, it will boot to updated partition without root.
5. I have tested the update methods with simply Uninstall -> Restore Images, while I had Magisk modules such as BCR, Shamiko, USF, LSPosed Zygisk. It works fine without the need of removing each module.
Extra side note: Update file is downloaded to: /data/ota_package/OTA/.otaPackage/mymanifest(...).zip
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
shivrajsingh said:
What is need of this lengthly process. Just wait for OTA to show in update. Only full package will show for rooted user. Let it download, Extract and verify. Before Pressing install Button, Go to Magisk and Install on inactive slot. Then Go back to updater and install button.
Phone will reboot and updated. Magisk working, All modules intact.
Click to expand...
Click to collapse
I know what you mean, in fact thank you for telling me that procedure is working well on our device hahaha, since there's no proper flashing tool and no TWRP yet, the idea behind that lengthy process is trying to reduce the risks to minimum n.n
Just confirmed that this works for a 300mb (before restoring images) update file instead of the full 5GB (after restoring images), updated the guide above.
vanya.ag said:
boot
Click to expand...
Click to collapse
now my fingerprint is broken
Quake94 said:
Notes:
When Magisk is removed using Restore Images, the Realme OTA updater will show a full 5GB update. If the Magisk is not removed, the OTA will be around 300mb. Both update files will work OK, there is just small difference in steps. The important part is to not restart the device or select "Install" in the OTA updater until Magisk is reinstalled to inactive partition. Otherwise it will boot into stock ROM, and a patched boot would need to be flashed via fastboot to restore root.
Click to expand...
Click to collapse
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
Terrorigel97 said:
i followed your steps
it was an 5gb OTA update i dovnloaded it and extract it then i go to magisk and install to inactive slot after reboot now im in stock recovery what now?
Click to expand...
Click to collapse
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
Quake94 said:
What what? You post in multiple threads. In one of them you want to lock bootloader and keep it stock, but here you say you installed Magisk after OTA. You also talk about stock recovery that has nothing to do with bootloader.
Help yourself and read up, all the information is widely available.
Click to expand...
Click to collapse
I never said i will be on stock lol I was just asking if you can lock your bootloader again...
Terrorigel97 said:
I never said i will be on stock lol I was just asking if you can lock your bootloader again...
Click to expand...
Click to collapse
Lock only on clean, stock rom as per guide in the other thread.
Can't lock on rooted, but rooted can be reversed to stock clean.
EDIT: resolved, see bottom note.
A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.
Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.
Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.
Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.
Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.
Anyone else in a similar situation?
EDIT: LOL I fixed it . I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......
Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.
TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
I confirm you have to reboot via the installer and not via Magisk, since I had to manually flash boot.img multiple times in the past.
Quake94 said:
EDIT: resolved, see bottom note.
A.19 update screwed something up for me.
I restored image in Magisk, installed a full 5GB update, reinstalled Magisk to inactive slot. Reboot via Magisk.
Phone went to softloop. I held Volume Up and Power, and at some point it switched back to previous slot with A18, works fine except no root.
Restarted to fastboot. Fastboot works OK.
When attempting to restart to bootloader, some "mascot" icon appears and chinese writing, and quits back to fastboot.
Manually switched active partition via fastboot --set_active to try to boot the A19.
Phone still softloops, again, restarted back to previous slot with A18.
Fastboot indicates unlocked bootloader.
Not sure what got messed up, and why bootloader mode refuses to start.
Not a big issue, because my old A18 works ok, so for anyone else reading this that got a softloop, I recommend simply holding Volume Up and Power to switch to old slot, instead of attempting to reflash and screwing both partitions up.
Anyone else in a similar situation?
EDIT: LOL I fixed it . I went to software updater, and "Install" button was displayed.
Pressing install restarted the phone into A19 with Magisk installed......
Very interesting! Because rebooting via Magisk or the --set-active command in fastboot resulted in softloop! So the "Install" must be doing some extra steps.
TLDR; after OTA update and reinstalling Magisk to inactive slot, do not reboot via Magisk, but via OTA updater "Install" button! My guide above was updated.
Click to expand...
Click to collapse
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?
If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?
GIutton said:
This sounds like what my phone is doing but maybe I am confused because you mention fastboot and the bootloader as two different things. Just to be clear, "adb reboot bootloader" is what you are calling the bootloader and "adb reboot fastboot" which goes into fastbootd mode is what you are calling fastboot?
If so then my phone is doing the exact same thing, I can boot to fastbootd mode but when I attempt to "adb reboot bootloader" then just like you said a little mascot with Chinese writing appears for a split second then it reboots back to the system. Did you get your bootloader working again by doing the install?
Click to expand...
Click to collapse
There are four modes:
bootloader - adb reboot bootloader
fastboot - adb reboot fastboot (or the key combo)
fastbootd - fastboot reboot fastboot (from being already in fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry
In my case the fastboot mode would start ok, just not the bootloader mode.
I didn't try fastbootd, but it would probably start ok.
I don't understand the fastbootd mode well though. I read somewhere that it is fastboot in Data partition.
I haven't tested rebooting to bootloader after fix, but can let you know.
EDIT: Booting to bootloader from fastboot (fastboot entered with key combo) gives me the mascot again, then it goes immediately back to fastboot. So I think I am in same position as you
Running "adb reboot fastboot" started "Fastbootd" mode (the one with wipe data/reboot/power off)
Running "fastboot reboot fastboot" from the "Fastbootd" would restart to "Fastbootd"
Running "fastboot reboot recovery" from the "Fastbootd" showed success, but 1. phone stayed in "Fastbootd" and 2. The phone deauthorized ADB (but still showed in device manager as "ossi" device)
Running "adb reboot bootloader" from System, showed the mascot and started the regular Fastboot.
Running "fastboot reboot fastboot" while the regular Fastboot was on, started "Fastbootd"
My suspicions are:
1. Regular fastboot mode is the one with green "START" on top. Somehow it is the same as bootloader. This is confirmed by Realme guide for unlocking/locking bootloader - they ask to use adb reboot bootloader, and then run a fastboot command.
2. "Adb reboot fastboot" starts the "userspace" fastboot called "fastbootd" which is isolated from bootloader and kernel.
This would mean the modes are:
bootloader/fastboot -> adb reboot bootloader (or the key combo)
fastbootd - adb reboot fastboot, or fastboot reboot fastboot (from being already in bootloader/fastboot)
recovery - adb reboot recovery (or the key combo)
EDL - adb reboot edl / fastboot oem edl / short testpoints or modify boot entry
So you can get into the start menu (fastboot/bootloader) by using the button combo but if you try fastboot reboot bootloader it shows a mascot with chinese letters then goes right back to the start menu and adb reboot bootloader shows the mascot and goes into the start menu as well? I think your phone is fine. . . fastboot and the bootloader should both be the start menu right or is there a difference?
For me I get the realme logo then a screen glitch and boots to the system when I try the button combo. When I try adb reboot bootloader I get a mascot with Chinese letters then a screen glitch then boots into the system.
Added some extra notes in my guide. If Auto download was enabled in About Device -> Software Update, the updater will display "Extraction Failed" since it attempts to download and extract update while Magisk is present. It also locks itself out of "Local install". The updater will download 5GB update instead on a retry, and 5GB method would be used.
With the Auto download disabled, user can Restore Images via Magisk and then download and install the update.
I will test this on the next update rollout.
Revised guide after C.12 to C.13 update and testing the smaller update method. The process is much more straightforward than I initially thought. No need for "Local update".