[help] XT1921-1 root - Moto E5 Questions & Answers

Hello all,
I was wondering if there has been any development / root process for the E5 Play XT1921-1?
Thanks

smeogle said:
Hello all,
I was wondering if there has been any development / root process for the E5 Play XT1921-1?
Thanks
Click to expand...
Click to collapse
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.

MotoJunkie01 said:
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.
Click to expand...
Click to collapse
I will give it a go, thank you for your info!

smeogle said:
I will give it a go, thank you for your info!
Click to expand...
Click to collapse
To play it completely safe, instead of actually flashing TWRP as an initial step, use the boot-only method:
fastboot boot twrp.img
This way, you can ascertain whether the TWRP build functions on your device normally before flashing the /recovery partition.

MotoJunkie01 said:
To play it completely safe, instead of actually flashing TWRP as an initial step, use the boot-only method:
fastboot boot twrp.img
This way, you can ascertain whether the TWRP build functions on your device normally before flashing the /recovery partition.
Click to expand...
Click to collapse
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!

smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
Very glad you tried and confirmed this. I'll add the info to my stock ROM thread regarding the intercompatability between these two devices.

MotoJunkie01 said:
Very glad you tried and confirmed this. I'll add the info to my stock ROM thread regarding the intercompatability between these two devices.
Click to expand...
Click to collapse
Upon further use, there is some stability issues. When I navigate to Settings -> System -> About Phone -> Hardware Information, the popup 'Motorola Settings has stopped' appears. Additionally, camera doesn't launch.

smeogle said:
Upon further use, there is some stability issues. When I navigate to Settings -> System -> About Phone -> Hardware Information, the popup 'Motorola Settings has stopped' appears. Additionally, camera doesn't launch.
Click to expand...
Click to collapse
Interesting. That would appear to indicate some minor differences between the two devices in terms of firmware configurations. Try this, using the factory firmware package for your device, flash the /boot and /oem partitions only (since the camera drivers are located in /boot). Then boot into TWRP recovery and flash Magisk (or a no-verity script) in order to disable dm-verity and for root patching. Wipe the cache and Dalvik and reboot system.
If that doesn't do the trick, do a clean firmware install and do a TWRP dump of your system image and /boot partition. Upload them to a host like Google Drive, send me a link, and I'll build you a TWRP flashable stock ROM specifically for xt1921-1.

MotoJunkie01 said:
Interesting. That would appear to indicate some minor differences between the two devices in terms of firmware configurations. Try this, using the factory firmware package for your device, flash the /boot and /oem partitions only (since the camera drivers are located in /boot). Then boot into TWRP recovery and flash Magisk (or a no-verity script) in order to disable dm-verity and for root patching. Wipe the cache and Dalvik and reboot system.
If that doesn't do the trick, do a clean firmware install and do a TWRP dump of your system image and /boot partition. Upload them to a host like Google Drive, send me a link, and I'll build you a TWRP flashable stock ROM specifically for xt1921-1.
Click to expand...
Click to collapse
After following the flash boot and oem steps, it got caught in a bootloop. Once that occurred, I wiped and reflashed your stock rom (followed by Magisk). Once it booted again, the previously mentioned instability (camera and hardware settings) have disappeared. Good job!

smeogle said:
After following the flash boot and oem steps, it got caught in a bootloop. Once that occurred, I wiped and reflashed your stock rom (followed by Magisk). Once it booted again, the previously mentioned instability (camera and hardware settings) have disappeared. Good job!
Click to expand...
Click to collapse
Give me a TWRP backup of your system image and boot partition and I'll make a TWRP flashable stock ROM for the XT1921-1.
Thanks for testing. I'll add the intercompatability info to my stock ROM and firmware threads.

Unlocking Bootloader on XT1921-1
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
---------- Post added at 09:57 PM ---------- Previous post was at 09:46 PM ----------
smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?

dcluvsme said:
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
---------- Post added at 09:57 PM ---------- Previous post was at 09:46 PM ----------
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
Click to expand...
Click to collapse
I followed the guide the on the following Motorola website:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

Thanks
smeogle said:
I followed the guide the on the following Motorola website:
Click to expand...
Click to collapse
Using Linux, I was refused, did the exact same thing in Windows,and it worked.
Who knows.
Thanks for the tip.

dcluvsme said:
Using Linux, I was refused, did the exact same thing in Windows,and it worked.
Who knows.
Thanks for the tip.
Click to expand...
Click to collapse
When you tried in Linux, what do you mean it did not work? I performed mine with Linux Mint. Did you get any specific error? How did you install adb and fastboot?

smeogle said:
When you tried in Linux, what do you mean it did not work? I performed mine with Linux Mint. Did you get any specific error? How did you install adb and fastboot?
Click to expand...
Click to collapse
I used Puppy Xenial,but I also have Linux Mint. I am sure it was an error on my part. No worries.

smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
can u please help me i think im stuck in the same boat you were in

MotoJunkie01 said:
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.
Click to expand...
Click to collapse
is there a way to do it without twerp? my phone is in a boot loop i installed the wrong rom i think i cant find the correct one for this phone.

Related

Progress towards Root/Twrp/Roms

This thread is strictly for info regarding Root/Twrp/Roms
If you have any ideas or have tried anything please post here
I AM IN NO WAY A DEV ,i am using google and common sense
Here is the link to the sprint boot.img (https://drive.google.com/file/d/0B9Vkl8ldvnNdOGlyLW4wOXNDRUk/view?usp=drivesd)-Thanks to @XirXes
Heres what i have tried
-So far i have tried signing the sprint boot.img to magisk with no luck,it gives me files are read only errors.I was able to get past the the first two steps of this post for systemless root via adb (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
-Flashing the stock sprint boot.img to confirm compatibility hint hint its compatible
ROOT HAS BEEN ACHEIVED!!
UPDATE- As of 9/13/17 we now have root in the form of a patched boot.img thanks to @themustached for patching the boot.img so gracefully for us
To install the boot img you need to reboot to fastboot and run the command "fastboot flash boot (name of boot.img).img
https://drive.google.com/file/d/0B8kodjBRTHoZR2Zob1VLX0xOVkU/view?usp=sharing
Just a update as I have been away from this phone for a bit
We have kernel source now (like 2 months ago) and there are 3 AOSP ROMs that I know about being worked on so far I don't know any details or anything but what I do know is that they completed the build process they are working on getting it running on our phone
joemossjr made the the ncp Rom and got TWRP for us so big thanks to him!
Substratum works on legacy with root and newest version of TWRP just in case anyone was wondering.
https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing
joemossjr said:
https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing
Click to expand...
Click to collapse
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.
altimax98 said:
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.
Click to expand...
Click to collapse
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk
I have insurance and I'm willing to risk my device worst case,it's not a problem,I've noticed if you boot it,it doesn't like to set correctly
joemossjr said:
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk
Click to expand...
Click to collapse
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk
Downloaded them all found no recovery
Verified ATT & Sprint boot.img works om Tmobile
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!
bart bart said:
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!
Click to expand...
Click to collapse
We are all in this situation. It is likely going to be quite some time before we get root due to the dual partition system.
Based on the Pixel info, we need TWRP first
Sent from my Moto Z (2) using Tapatalk
The recovery is in the boot.img of 7.1 and up devices
Dumper US Cellular Boot.img
altimax98 said:
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Here is dumped boot.img of US Cellular Boot.img. There is a recovery under sbin folder. Hopefully you can make a bootable TWRP from it?
https://www.dropbox.com/s/hjfr8wj2da...ootus.zip?dl=0
If anyone wants to join our efforts the let us know and we can add you in
I want to join your efforts.
Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.
joemossjr said:
Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.
Click to expand...
Click to collapse
Thank you
Sent from my SM-N930F using XDA-Developers Legacy app
Deleted
Any progress? Anything I can do to help? I have T Mobile variant with unlocked bootloader.
We brought in another guy from the pixel forum who made their twrp recovery he's going to take a look and see what can be done
Question before I delve further.
fastboot -i 0x2b4c flash:raw boot <kernel> [ <ramdisk> ] rather than just flash <partition> [ <filename> ] perhaps for the twrp? Just a spit ball idea as I wrap my head around. Been a few years since I bothered with phones rather than.. other systems. I'm sure this round probably already been tried but curious of the turn before I fry the new toy xD.
joemossjr said:
If anyone wants to join our efforts the let us know and we can add you in
Click to expand...
Click to collapse
I can test stuff when the time comes.

Official Android 10 Beta - RETBR Channel

UPDATE - LIVE NOW IN BR AND MX CHANNELS
https://piunikaweb.com/2020/01/23/motorola-moto-g7-plus-android-10-update/
Stumbled across this the other day, wondering if anyone has tried it. Seems this is the second 10 beta released to the RETBR beta channel. Link to download is included in the OP at the bottom.
https://piunikaweb.com/2020/01/09/moto-g7-plus-android-10-update-soak-test/
As of this writing, those who already had the first Android 10 build on the Moto G7 Plus are now receiving another update as version QPW30.61-21, this time with a newer December 2019 security patch.
Device: Moto G7 Plus
Codename: XT1965-2
Channel: Beta (RETBR)
Version: QPW30.61-21
Android: 10
I havent grabbed it yet as im on a horribly slow connection atm so can't confirm contents of zip.
Thank you
Thank you very much... how to install? trying to copy to the root of my storage but recovery dont find it to install! THx in advance
chiconanni2 said:
Thank you very much... how to install? trying to copy to the root of my storage but recovery dont find it to install! THx in advance
Click to expand...
Click to collapse
1. just keep the zip file in root of Internal storage
2. Give storage permission to Motorola update services by going to settings app -> apps -> show system apps -> Motorola update services
3. reboot the phone..
4. After this, just check for updates.. then your phone will start updating..
Didn't worked...
But i saw now that my phone is in amxbr channel! Thank you anyway!
ajaikumarnadar said:
1. just keep the zip file in root of Internal storage
2. Give storage permission to Motorola update services by going to settings app -> apps -> show system apps -> Motorola update services
3. reboot the phone..
4. After this, just check for updates.. then your phone will start updating..
Click to expand...
Click to collapse
I believe this zip is made to be installed with twrp, not the stock recovery, thats why it didn't work.
ajaikumarnadar said:
1. just keep the zip file in root of Internal storage
2. Give storage permission to Motorola update services by going to settings app -> apps -> show system apps -> Motorola update services
3. reboot the phone..
4. After this, just check for updates.. then your phone will start updating..
Click to expand...
Click to collapse
Ok, when you say root of internal storage, you mean keep it on internal storage or in a folder named root? Because it's on internal storage and I've tried it three times.
---------- Post added at 10:33 PM ---------- Previous post was at 10:17 PM ----------
I found out it's all the same. So why isn't it working for me? Should I install twrp? Can it be installed without root?
Hello?
This is what i did
1.-i went back to stock rom (your device's firmware)
2.-reboot to system
3.-flash twrp
4.-flash the soak test zip via twrp (let it do it's thing the updater script is in Portuguese)
5.-reboot to system
6.-enjoy android 10
7.-"profit"
Thanks, things is, I don't have TWRP on this phone. Can it be installed without root?
Nhyphk said:
Thanks, things is, I don't have TWRP on this phone. Can it be installed without root?
Click to expand...
Click to collapse
Installing twrp doesn't mean you are rooted once the installation is done you won't have twrp unless you install it again!!
HELP ME !!!
Hello !! My phone and G7 Plus (Blur_Version.29.271.13.lake.retai), locked on the logo,
I tried everything with the Bootloader blocked and impossible to put a current room,
I tried to put everything, and my phone is still unsuccessful
Danjunio28 said:
Hello !! My phone and G7 Plus (Blur_Version.29.271.13.lake.retai), locked on the logo,
I tried everything with the Bootloader blocked and impossible to put a current room,
I tried to put everything, and my phone is still unsuccessful
Click to expand...
Click to collapse
Try using the lenovo moto smart assistant it may help you!https://support.lenovo.com/us/en/downloads/ds101291
tried but device appears not found try again
ajaikumarnadar said:
1. just keep the zip file in root of Internal storage
2. Give storage permission to Motorola update services by going to settings app -> apps -> show system apps -> Motorola update services
3. reboot the phone..
4. After this, just check for updates.. then your phone will start updating..
Click to expand...
Click to collapse
Jairsantana said:
This is what i did
1.-i went back to stock rom (your device's firmware)
2.-reboot to system
3.-flash twrp
4.-flash the soak test zip via twrp (let it do it's thing the updater script is in Portuguese)
5.-reboot to system
6.-enjoy android 10
7.-"profit"
Click to expand...
Click to collapse
Jairsantana said:
Installing twrp doesn't mean you are rooted once the installation is done you won't have twrp unless you install it again!!
Click to expand...
Click to collapse
Hi, I know, I just didn't know that it was possible. Also, they say it's very complicated to install TWRP now because of the a/b slots thing, what tutorial did you follow?
Nhyphk said:
Hi, I know, I just didn't know that it was possible. Also, they say it's very complicated to install TWRP now because of the a/b slots thing, what tutorial did you follow?
Click to expand...
Click to collapse
Follow this guide to install twrp recovery.... https://www.androidinfotech.com/root-moto-g7-plus-pie/
Jairsantana said:
Follow this guide to install twrp recovery.... https://www.androidinfotech.com/root-moto-g7-plus-pie/
Click to expand...
Click to collapse
Hi, I had already installed when I saw this, but thanks. Now I have a problem, I managed to do everything ok, I installed Android 10, installed my apps, I was even using them, so I decided to restart the phone and it gets stuck on the Phone Is Starting screen. I can access settings, but some things are locked.
I factory reset it, I've restarted twice now and it's opening, but I'm getting so many erros, like apps that won't download, there's not a single folder on internal memory. Is this fixable? Should I try reinstalling it or downgrade it? ?
---------- Post added at 12:05 PM ---------- Previous post was at 11:13 AM ----------
I think it's a problem with storage or slots, because whrn I try to screenshot it says it can't save due to limited storage although I only have 34% used
I just got the update and was able to capture the zip file.
Please be aware that after the update my phone was in a boot loop, and I had to do a full wipe. I'm full stock with the bootloader still locked.
This is the .zip I captured: http://fastdl.hostzone.com.br/zip/ab_delta-Blur_Version.29.271.13-10.1.22.lake.retail.en.US.zip
Thank you
marocampos said:
I just got the update and was able to capture the zip file.
Please be aware that after the update my phone was in a boot loop, and I had to do a full wipe. I'm full stock with the bootloader still locked.
This is the .zip I captured: http://fastdl.hostzone.com.br/zip/ab_delta-Blur_Version.29.271.13-10.1.22.lake.retail.en.US.zip
Click to expand...
Click to collapse
Thank you very much, worked like a charm!
marocampos said:
I just got the update and was able to capture the zip file.
Please be aware that after the update my phone was in a boot loop, and I had to do a full wipe. I'm full stock with the bootloader still locked.
This is the .zip I captured: http://fastdl.hostzone.com.br/zip/ab_delta-Blur_Version.29.271.13-10.1.22.lake.retail.en.US.zip
Click to expand...
Click to collapse
I've got another software channel, Does it works too? How can I update with that zip?

[STOCK] Stable realmeUI/Android 10 ROM for RMX1991

Hi folks,
What we used as beta ROM is now published as official stable release known as version RMX1991_11.C.12 for Chinese model of Realme X2.
Probably anyone can upgrade the phone now in any possible way.
The bad news is FP stops working as soon as you patch vbmeta for disabling AVB...
The good news is that there's no verification of system partition. You can leave vbmeta untouched and modify whatever you want except boot.
yakovpol said:
The good news is that there's no verification of system partition. You can leave vbmeta untouched and modify whatever you want except boot.
Click to expand...
Click to collapse
Then, you will not loose fingerprint?
AlAneed said:
Then, you will not loose fingerprint?
Click to expand...
Click to collapse
Exactly
yakovpol said:
Exactly
Click to expand...
Click to collapse
Magisk can be installed and we still have the fingerprint working?
AlAneed said:
Magisk can be installed and we still have the fingerprint working?
Click to expand...
Click to collapse
No, Magisk is patching boot, which will require you to disable verification by means of vbmeta. You can try system-based methods like one of SuperSU.
yakovpol said:
No, Magisk is patching boot, which will require you to disable verification by means of vbmeta. You can try system-based methods like one of SuperSU.
Click to expand...
Click to collapse
but in order to fix twrp replace issue vbmeta verification is needed to be disabled right??
I will try to search for it. Is it just a normal app to install from Play store? or requires other method?
One more thing, TWRP working with it or no?
Thanks
---------- Post added 10th April 2020 at 12:36 AM ---------- Previous post was 9th April 2020 at 11:38 PM ----------
I guess I am not able to understand how to do root? I searched for system base root in the web with no luck
Would you mind explaining how to do root without Magisk?
osamanazim said:
but in order to fix twrp replace issue vbmeta verification is needed to be disabled right??
Click to expand...
Click to collapse
No. At least a few last CN ROM versions are insensitive to recovery replacement. You can keep stock vbmeta and flash custom recovery. But recovery will be replaced when you boot system, i.e. you flash custom recovery for single and immediate use
yakovpol said:
No. At least a few last CN ROM versions are insensitive to recovery replacement. You can keep stock vbmeta and flash custom recovery. But recovery will be replaced when you boot system, i.e. you flash custom recovery for single and immediate use
Click to expand...
Click to collapse
Will i lose any file if i update from color os 6.1 to realme ui or i need to backup first?
Mikelsteven said:
Will i lose any file if i update from color os 6.1 to realme ui or i need to backup first?
Click to expand...
Click to collapse
Backup is a nice thing. I would always insist on creating backup.
I successfully switched onto realmeUI without losing data. As I understand, you have to do it from A.17 (for CN device). My path was A.16 -> C.02, but now many are suggested to upgrade from A.17 straight to C.12.
yakovpol said:
Backup is a nice thing. I would always insist on creating backup.
I successfully switched onto realmeUI without losing data. As I understand, you have to do it from A.17 (for CN device). My path was A.16 -> C.02, but now many are suggested to upgrade from A.17 straight to C.12.
Click to expand...
Click to collapse
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Mikelsteven said:
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Click to expand...
Click to collapse
Put some labour on searching through Internet please. So you will be sure if to update or not
To me it works just fine.
Mikelsteven said:
Thanks man. I don't know what reliable backup method i can use on an unrooted phone. I'm on A17 so i guess it's safe to upgrade without backup. Again, have u experienced any bug so far on realme ui?
Click to expand...
Click to collapse
Black Screen problems while playing COD Mobile. Iit is a common problem on sobre Android 10 upgraded devices.
But all the rest of software running and working smoothly.
can someone please confirm if the feature of Waze returning to top during voice call is working? i have the globalized version by mettis and it doesn't work there (have CN device)

Battery issue after flashing

Hi folks! I humbly ask for your help after hours and hours of DIY attempts. I rooted a Z5 Compact a few years ago and, mistakenly, expected this to be similar: I didn't read instructions carefully. Admitting to noob mistakes now.
I followed this:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
with this option:
https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
I went with the G8441_47.1.A.8.49_CE1.rar firmware, as it seems most compatible. THANK YOU j4nn! Marvelous and relatively simple procedure . Flashed with newflasher (Flashtool doesn't work with XZ1 Compact?).
Rooting worked, but when the phone is on battery it never goes above 20%. It was 100% before and 20% immediately after flashing. Red warning light is on, unless the phone is off and plugged in.
So. I missed the part about omitting persist* and Qnovo*. Somehow my attest keys didn't break (PROVISIONED in service test).
It looks like what happened is I replaced the battery config? Info:
https://forum.xda-developers.com/xperia-x/help/flashed-xperia-x-low-battery-t3441158
https://forum.xda-developers.com/xperia-xa/help/strange-battery-issue-jumping-33-3-0-t3688178
Can't repair with Xperia Companion because unlocked bootloader (no way it could be re-locked, is there? My DRM keys are backed up).
Someone wrote about wiping the Qnovo partition. Any advice on how to do this? fastboot format Qnovo didn't work (looks like it doesn't find that partition)
Unrelated, and sorry if this is a total n00b question, but where on earth is TWRP compatible with this device/FW? j4nn's rooted kernel doesn't play well with TWRP install, so I'm hoping to just fastboot boot recovery.img. I can't find any recovery.img that works - I tried several of these:
https://androidfilehost.com/?w=files&flid=232371
But it just gets stuck on SONY logo, needing soft reset.
ben_pcc said:
Hi folks! I humbly ask for your help after hours and hours of DIY attempts. I rooted a Z5 Compact a few years ago and, mistakenly, expected this to be similar: I didn't read instructions carefully. Admitting to noob mistakes now.
Click to expand...
Click to collapse
Try this - https://developer.sony.com/develop/open-devices/get-started/flash-tool and report back.
WORKED. Flashed the US firmware with "Software Update Content Erase", battery now seems to be working normal again. Thank you so much!
Another question: I'd love to set this phone up to work with fastbooting TWRP (so, not a TWRP install on the phone). Is that possible with 47.1.A.8.49? If not, advice on what firmware to use that'll allow rooting per j4nn's methods? Preferably compatible with https://forum.xda-developers.com/xp...oted-kernel-hiding-bootloader-unlock-t3898711
ben_pcc said:
Is that possible with 47.1.A.8.49? If not, advice on what firmware to use that'll allow rooting per j4nn's methods?[/url]
Click to expand...
Click to collapse
Why use such old FW? If you're sticking with Oreo then you want the FW ending .20 for the latest. An unlocked bootloader is all that required to boot TWRP from fastboot on any FW.
Because I didn't know better. Emma gave me 47.1.A.16.20, I'll stick to that
Would you mind sharing what *img file exactly would work with fastboot that way? I had no trouble finding it for the Z5 compact, but one that would work here is eluding me. For example, if I run:
fastboot boot twrp-3.2.3-0-lilac-1.img
The phone boots up to SONY logo (black on white background) and stays there, unresponsive. Got the file from https://androidfilehost.com/?w=files&flid=286271
ben_pcc said:
Would you mind sharing what *img file exactly would work with fastboot that way?
Click to expand...
Click to collapse
Have you missed this post, which is linked to in the threads you've posted links to? - https://forum.xda-developers.com/showpost.php?p=79880858&postcount=1029
I missed it but I also miss how that would help. I read the whole thing, and this stands out: fastboot boot twrp.img
I've done that with my old phone (Z5 Compact). I can't find a usable twrp.img anywhere. I fear like I'm missing something obvious
ben_pcc said:
I missed it but I also miss how that would help. I read the whole thing, and this stands out: fastboot boot twrp.img
I've done that with my old phone (Z5 Compact). I can't find a usable twrp.img anywhere. I fear like I'm missing something obvious
Click to expand...
Click to collapse
From the last page - https://forum.xda-developers.com/showpost.php?p=83844543&postcount=1657
Although I would simply install the latest and use one of the unrooted kernels then root it with Magisk.
Hmm. I was aware of that. I tried several of the twrp*.img files, they all get stuck booting on the SONY logo.
Are you sure this is true:
An unlocked bootloader is all that required to boot TWRP from fastboot on any FW.
Click to expand...
Click to collapse
I'm wondering if a FW update would solve the TWRP booting problem.
I've setup this phone a bit at this point and flashing a new firmware (erasing everything) would be painful. Is there a way to safely do a firmware update on a rooted device? Emma offers 47.2.A.*, but only for UK ROMS. I'd installed the 47.1.A.16.20 US ROM.
ben_pcc said:
Are you sure this is true:
Click to expand...
Click to collapse
I know it used to be. Done a bit more searching for you https://forum.xda-developers.com/search/thread/3706704?query=fastboot twrp, and found this command...
Code:
fastboot reboot bootloader
fastboot boot twrp-3.3.1-0-lilac-pie-5.img
...I've just tried it, in fastboot mode and it booted TWRP.
ben_pcc said:
I've setup this phone a bit at this point and flashing a new firmware (erasing everything) would be painful. Is there a way to safely do a firmware update on a rooted device? Emma offers 47.2.A.*, but only for UK ROMS. I'd installed the 47.1.A.16.20 US ROM.
Click to expand...
Click to collapse
Starting over is always painful but sometimes it's the best option. I have a rooted stock ROM and TWRP installed with no issues, on Oreo or PIE so if you do, then I suggest backing up the essentials and starting again.
YES. Thanks so much SXUsr! You were right after all, I tried a few different TWRP images and they work now. What I was missing was fastboot reboot bootloader. My Z5 Compact doesn't require it.
There was one more thing I had to figure out: data partition is encrypted, and for my (Android 8.0.0) device the TWRP you mentioned fails.
twrp-3.2.3-0-lilac-1.img on the other hand asks for my unlock pattern when it boots up, and backs up fine.
Now that I have a complete backup I'll consider my next steps (possibly flashing a new ROM. Honestly 8.0.0 seems fine, we'll see). Thanks again!!
ben_pcc said:
YES. Thanks so much SXUsr!
Click to expand...
Click to collapse
You're welcome. I've always installed it on this phone so wasn't aware of that command myself either, so we've both learnt something.

General [IMG] Boot + magisk patched boot images

Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links): ​
EU NE2213_11_A.12​
Stock boot.img - link
EU NE2213_11_A.10​
Stock boot.img - link
​Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come. ​
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot ​
Reserved
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/
kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.

Categories

Resources