this is a great device but its pretty new. Will we be getting TWRP for it? Is there at least an unofficial version yet?
My understanding is it won't work on Android 10.
androiddiego said:
My understanding is it won't work on Android 10.
Click to expand...
Click to collapse
You are correct! Here is the official blog post I just found:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
This is super bogus and especially since this phone (at least mine) does not seem to have a stock recovery (I get a no command dead android). I think I am going to return this phone. Shame. It's pretty slick, but no way I am going to have one that has no viable recovery!
It sounds like they'll get there, just not quickly. If you read that link closely, this seems to apply to all phones shipped with android 10. So jumping to another phone is not necessarily a solution.
does anyone with a Moto G Stylus have a working stock recovery?
fronto said:
this is a great device but its pretty new. Will we be getting TWRP for it? Is there at least an unofficial version yet?
Click to expand...
Click to collapse
Did u unlock the bootloader
Sent from my moto g stylus using Tapatalk
When you go into recovery hit the + and - volume buttons together and it will pop up.
Yes their is recovery software. It's rescue mode.
fronto said:
You are correct! Here is the official blog post I just found:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
This is super bogus and especially since this phone (at least mine) does not seem to have a stock recovery (I get a no command dead android). I think I am going to return this phone. Shame. It's pretty slick, but no way I am going to have one that has no viable recovery!
Click to expand...
Click to collapse
https://motorola-global-portal.custhelp.com/app/mcp/service
twrp
why do you need a recovery when you can unlock the bootloader and use the factory recovery to flash what ever you want and they have a nice recovery option using the rescue and smart assistant software for pc mac or lin. i fail to see why you would want a custom recovery.
Has anyone tried flashing a system image yet, just rooted my Metro Stylus and wondering what's good to flash
DMedina559 said:
Has anyone tried flashing a system image yet, just rooted my Metro Stylus and wondering what's good to flash
Click to expand...
Click to collapse
How did you root? Are there instructions somewhere for Android 10 root?
cyrusalmighty said:
How did you root? Are there instructions somewhere for Android 10 root?
Click to expand...
Click to collapse
I unlocked my bootloader through Motorola then flashed a magisk patched boot.img through fastboot
DMedina559 said:
I unlocked my bootloader through Motorola then flashed a magisk patched boot.img through fastboot
Click to expand...
Click to collapse
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
cyrusalmighty said:
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
Click to expand...
Click to collapse
I haven't kept up with the android modding scene for years so I'm kinda out of the loop, but the general rule of thumb is to not do ota updates unless you're flashing full images with fastboot or using an OEM recovery software (Lenovo\Moto have one here)
As for the patch, I got the boot.img from the recovery software I linked above and installed magisk manager on my phone to patch the img which I then moved to my laptop to flash in fastboot
cyrusalmighty said:
Where can I get the patched boot.img or did you patch one? Will the device brick when next stock update comes out? It sucks not having custom recovery to have a backup
Click to expand...
Click to collapse
Hi,
First download Rescue and Smart Assistant from Motorola website, make sure activate the developer options and usb debugging and download your phone's software with Rescue and Smart Assistant (it will find it automatically), find boot.img from inside the downloaded zip file and copy it to your phone, download Magisk Manager to your phone, and patch the boot.img with Magisk Manager, copy patched boot.img to your computer and flash it with adb.
If you have a desire to get TWRP, you should write to Telegram @mauronofrio and raise some donate to develop TWRP for this device.
Root Moto g stylus
fronto said:
does anyone with a Moto G Stylus have a working stock recovery?
Click to expand...
Click to collapse
My moto G stylus if it has an active recovery, when I buy it at 2 hours I unlock the bootloader and root with magisk, I put Xposed and BusyBox, the Xposed does not seem to work very well android 10, Aceves if and sometimes it turns off, buxybox is necessary reinstall again and again every time you turn the phone off and on, and Xposed works 60%, my Motorola G Stylus is from Metro
Luiszipatla said:
My moto G stylus if it has an active recovery, when I buy it at 2 hours I unlock the bootloader and root with magisk, I put Xposed and BusyBox, the Xposed does not seem to work very well android 10, Aceves if and sometimes it turns off, buxybox is necessary reinstall again and again every time you turn the phone off and on, and Xposed works 60%, my Motorola G Stylus is from Metro
Click to expand...
Click to collapse
Same issue, I've had the same provoking anger problem with this phone and previously a Moto e5 plus. It's rooted yet no Magisk module seems to work. This phone I can't even get lucky patcher to work. Android 10 sucks, I miss the good old days of Android 6 and 7.
Anyone else notice the modules not working at all but it's rooted?
Also to do a backup, adb backup and adb restore are your friends.
Rooted you can clone the device at least with adb commands. Slower but it's an exact copy at least.
Anyone with a rooted phone who could grab kernel logs after a fresh boot and post them here ?
vache said:
Anyone with a rooted phone who could grab kernel logs after a fresh boot and post them here ?
Click to expand...
Click to collapse
Going to flash the patched boot IMG once the firmware is done. Is there an app to catch the log or an adb command?
Related
Links attached for those interested from Essential Web Site, and source.android.
https://support.essential.com/hc/en-us
https://source.android.com/source/running
The real question is kernel source. Not much reason to unlock the bootloader without that.
Goronok said:
The real question is kernel source. Not much reason to unlock the bootloader without that.
Click to expand...
Click to collapse
Exactly.
I'm not holding my breath.
I think I'm jumping ship.
thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol
gqukyo said:
thought Magisk works now with just an unlocked bootloader... or was it the other way around... lol
*edit*
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Guess we'll need some patched boot image... which I'm assuming no one has yet... lol
Click to expand...
Click to collapse
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.
drocny87 said:
Magisk manager will patch the boot image when installing magisk 14.0
We just need the boot.img from the rom or the OTA before it installs.
Click to expand...
Click to collapse
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
Some people got the update today. If you happen to get it can you try to pull the boot?
I have the update waiting to be installed.
graffixnyc said:
That's IF You can access the OTA zip. A lot of times it's downloaded to /cache which is not accessible without root. Some OEM's have it downloaded to the SD card but most bigger OEM's have it downloaded to the cache partition
Click to expand...
Click to collapse
in the build thread, a user was able to capture the OTA url. the only issue, the boot.img is stored in the payload.bin file. Are you familiar with this file and how to extract it?
So is this phone rootable?
Sent from my SM-G950U using XDA-Developers Legacy app
canynballa said:
So is this phone rootable?
Click to expand...
Click to collapse
At this time no. Hopefully soon that will change.
In the Andy Rubin AMA, the official Essential reddit account posted that the kernel and factory images would be released to the public "in the next few days". That probably means next week, business days and all, but it looks like they fully intend to support external development of this phone, and soon. Makes sense--why else would they allow a bootloader unlock from the get-go?
In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help
Sarzeck said:
In adb I can find my phone but once I adb reboot bootloader and fastboot devices it doesn't display. Plz help
Click to expand...
Click to collapse
You need to select correct driver in device manager, maybe even install different drivers
See
https://forum.xda-developers.com/es...nofficial-usb-drivers-essential-ph-1-t3678231
Sent from my PH-1 using Tapatalk
Thanks buddy! It worked
i love unlocking bootloader on mine but for now until no ROM's mod i will stay locked mode. im a Android Pay dude lol
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Yeah, try another computer. Seriously, my main PC just didn't want to work with the phone. Used my laptop, worked fine. Can't think of anything different, both are Win10, both have the same drivers and sdks. Both work for my other phones, just not this one. Didn't hurt to try. Of course you'll need access to another computer but if you have one or more extras, worth a try. Worked for me.
oowaymike said:
Does anyone have any advice for getting the phone recognized. I installed android studio and google usb drivers. I've unlocked bootloaders on onepluses before but nothing happens when I type fastboot devices, and it stays at "waiting for any device" when I try the unlock command.
Click to expand...
Click to collapse
Did you reboot the computer? I've seen that help alot when device is not recognize
I'm having same issue, flashing unlock command do not work. I am on the oreo beta version. Someone help please.
Hi guys!
I've bought Moto E5 XT1944-2 just few days ago, I was looking for some info to root the device but I couldn't find any tutorial, and after a couple of hours I found a way to root the device, so I'm going to explain how to root this device.
Disclaimer
I'm not responsible for any dead phones, even if they explode or cause a war
If you didn't follow the steps one by one
VERY IMPORTANT!!
There's no way to backup using TWRP (cos is not available yet)
Also it seems that it doesn't works with XT1944-1 (try by your own risk)
REQUIREMENTS:
1. Unlocked Bootloader
2. Magisk Manager apk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. Boot Image from stock rom (you need to choose your current variant to avoid some possible problems) https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901
4. Motorola Drivers and ADB/Fastboot Drivers also
5. PC
6. A good brain and some patience LOL
Well, considering that already have all what I've mentioned lest begin.
FIRST STEP
Download and install Magisk Manager, It will show and advertisement asking if you want to install Magisk v16 (the screenshot says v16.7 but it's because I've got root already).
https://www.dropbox.com/s/a8mj0w0mk7uho7x/Screenshot_20180803-232248%5B1%5D.png?dl=0
Press no thanks, then open the app and in settings change the Update Channel into Beta , it's very important to know that because only Magisk v16.7 works, previous versions wont work!!
https://www.dropbox.com/s/vk404a1d0oou0ji/Screenshot_20180803-225740%5B1%5D.png?dl=0
https://www.dropbox.com/s/fyi6b3c1tgtfj5u/Screenshot_20180803-225745%5B1%5D.png?dl=0
SECOND STEP
After you have already downloaded the zip from your variant, use Winrar/7 Zip or any program to extract boot.img and then copy boot.img to you internal/external storage
THIRD STEP
Open again Magisk Manager, it will show if you want to install Magisk v16.7, press install, and select Patch Boot Image File
https://www.dropbox.com/s/9xyqgu8p4mm2ddy/Screenshot_20180803-232254%5B1%5D.png?dl=0
Then you need to look for the boot.img previously unzipped and moved onto your storage
https://www.dropbox.com/s/xlik3p9cau4952f/Screenshot_20180803-232720%5B1%5D.png?dl=0
After that the process began and it will save a new file called "patched_boot" that will be located on storage/MagiskManager
FOURTH STEP
Reboot your phone to bootloader mode and move to your computer the patched_boot.img, then flash that boot image via CMD with this command:
fastboot flash boot patched_boot.img
https://www.dropbox.com/s/xlik3p9cau4952f/Screenshot_20180803-232720%5B1%5D.png?dl=0
https://www.dropbox.com/s/h0r03mio06jezzz/XDA2.png?dl=0
It might delay less than a minute.
Finally run the command:
fastboot reboot
In my case shows a black screen saying, invalid key with white letters, if that is your case wait a minute, it will boot, if says N/A maybe something is wrong but first wait until the phone starts, if not, you have chosen the incorrect boot.img, to fix that just flash the original boot.img you've extracted with the command:
fastboot flash boot boot.img
And your phone will start normally, you don't need to wipe, and you wont loose your data
If you have some questions, let me know, oh, forget to mention, I'm not a dev so I don't know if it will be any rom available soon...
P.D I've tested only Substratum and it doesn't works, Xposed not tested yet because it turn the phone slower (in my experience) also some modules are not compatible and it will brick your device, Viper4Android works fine, you only need to install it via Magisk but keep in mind to use version 6.1 designed for Masigk v15 and upper...
I've created a telegram channel to help each others =)
https://t.me/joinchat/AAAAAEkiNbz-qY1tlKVgGQ
Woooow the scene grow up!. This guide is compatible with the Moto E5 xt1944-1?.
intherior said:
Woooow the scene grow up!. This guide is compatible with the Moto E5 xt1944-1?.
Click to expand...
Click to collapse
If it is nova_row I guess so, but well you need to try, remember that you need the stock ROM to extract boot and then in case of something wrong, also bootloader unlocked sir
Nice work @Fersho. Thank you for your contribution and your time.
Good descriptive guide.
I try to follow the guide using the Xt1944-1 stock rom image and after do it everything my Moto E5 get stucks on the Moto logo and reboots everytime. Only restoration guide of pal MotoJunkie01 revives.
intherior said:
I try to follow the guide using the Xt1944-1 stock rom image and after do it everything my Moto E5 get stucks on the Moto logo and reboots everytime. Only restoration guide of pal MotoJunkie01 revives.
Click to expand...
Click to collapse
Glad you got it back to life.
MotoJunkie01 said:
Nice work @Fersho. Thank you for your contribution and your time.
Click to expand...
Click to collapse
Thank you, all in the name of development and to help each others
intherior said:
I try to follow the guide using the Xt1944-1 stock rom image and after do it everything my Moto E5 get stucks on the Moto logo and reboots everytime. Only restoration guide of pal MotoJunkie01 revives.
Click to expand...
Click to collapse
You've tried flashing only boot? beause I mentioned that it wasn't necessary to flash the whole time, just flashing the stock boot the phone will start normally, but well that means that the XT1944-1 is unable to root, did you follow the correct steps? I mean you tried with Magisk v16.7?
Fersho said:
You've tried flashing only boot? beause I mentioned that it wasn't necessary to flash the whole time, just flashing the stock boot the phone will start normally, but well that means that the XT1944-1 is unable to root, did you follow the correct steps? I mean you tried with Magisk v16.7?
Click to expand...
Click to collapse
I think that i follow well. And i put my boot.img from stock rom with Magisk to make the patched_boot.img. Then i connect to the Pc to copy that file to the adb directory, reboot on bootloader mode and flash with the command that you post. Everything well, buy when i reboot after flash that appears the N/A letters and stucks rebooting everytime. When i reflash the smartphone with the stock rom then the Bad Key letters appears and make the boot well.
I dont know if isn't compatible yet
intherior said:
I think that i follow well. And i put my boot.img from stock rom with Magisk to make the patched_boot.img. Then i connect to the Pc to copy that file to the adb directory, reboot on bootloader mode and flash with the command that you post. Everything well, buy when i reboot after flash that appears the N/A letters and stucks rebooting everytime. When i reflash the smartphone with the stock rom then the Bad Key letters appears and make the boot well.
I dont know if isn't compatible yet
Click to expand...
Click to collapse
Well at least you've restored your phone, I think the same, that is not compatible, but well we won't know if something works til' we try, but thanks to share your experience I've edited the thread telling that issue, that happened to me but it boots while shows N/A
Does not work on xt1944-4
Hi, the ROM link for the stock rom is for the Moto E5 Play (James). Is this also the right one for Moto E5 (nora_row), because both phones have different specifications (according to GSM arena).
Otherwise, thanks for your help @Fersho.
artemis1102 said:
Hi, the ROM link for the stock rom is for the Moto E5 Play (James). Is this also the right one for Moto E5 (nora_row), because both phones have different specifications (according to GSM arena).
Otherwise, thanks for your help @Fersho.
Click to expand...
Click to collapse
My mistake, I didn't notice that I put the link for E5 Play Stock ROM, now is updated with the right one
Fersho said:
My mistake, I didn't notice that I put the link for E5 Play Stock ROM, now is updated with the right one
Click to expand...
Click to collapse
Seems like the right one now, thanks for your help. I'll give it a try.
Edit: I checked the page and there is no mention of the OPP27.91-72 build. Do you think the OPP27.91-25 will work or should I get the firmware from stock rom .net, which seems to have the correct one.
Thanks for updating the link anyways @Fersho
artemis1102 said:
Seems like the right one now, thanks for your help. I'll give it a try.
Edit: I checked the page and there is no mention of the OPP27.91-72 build. Do you think the OPP27.91-25 will work or should I get the firmware from stock rom .net, which seems to have the correct one.
Thanks for updating the link anyways @Fersho
Click to expand...
Click to collapse
The thread is not updated yet, so It will work because you only need the stock rom for your specific device, if it is updated or not, doesn't matter, I guesss that nora and hannah have got a security patch, but is not necessary, I mean still outdated, so don't take care about it
Hi
Have someone this firmware "XT1944-4 NORA_ROW_OPP27.91-146_cid50_subsidy-DEFAULT" for share ?
I would like to verify once magisk is I stalled and the manager is running and root works if we update will it still work. There are supposed exports who have said that if you update the magiks manager to the latest version 18+ or magiks 18+ versions that magics won't work anymore for the Moto e5 play can any one vetify
daktras said:
I would like to verify once magisk is I stalled and the manager is running and root works if we update will it still work. There are supposed exports who have said that if you update the magiks manager to the latest version 18+ or magiks 18+ versions that magics won't work anymore for the Moto e5 play can any one vetify
Click to expand...
Click to collapse
running 18 on e5+ perfectly
It worked on my XT1944-2 but only with Stock-ROM. Until nowI have no solution to Root with Lineage 17.1 OS on it.
Mod was already available for the Pixel2.
If you don't know what Edge Sense Plus is, you can check it here: https://forum.xda-developers.com/pixel-2/themes/root-custom-active-edge-actions-edge-t3732368
Just curious but do we know it can be rooted?
krabman said:
Just curious but do we know it can be rooted?
Click to expand...
Click to collapse
@topjohnwu will take care about that.
Sent from my HTC U11 using Tapatalk
Will get pixel 3xl by November 8 9. I am willing to test it for you.
ill have mine by 18th or 19th ill help out if still needed.
Mine is supposed to arrive today. I am hoping that root will be as simple as unlocking the bootloader, patching stock boot.img and flashing. I suspect that it'll be a while before we have a custom recovery though.
j to the 4n said:
@topjohnwu will take care about that.
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
WisdomWolf said:
Mine is supposed to arrive today. I am hoping that root will be as simple as unlocking the bootloader, patching stock boot.img and flashing. I suspect that it'll be a while before we have a custom recovery though.
Click to expand...
Click to collapse
Doing this would be extremely unwise without a copy of the stock boot image. I would advise you to wait till the factory images come out. Which should be soon. If you bootloop, highly likely, you will have a unusable phone until the factory images get posted.
Well considering that I would need a copy of the stock boot.img to accomplish this process it seems like we are in arguegreement. [emoji6]
Sent from my Pixel 2 XL using Tapatalk
Has anyone unlocked the bootloader? That's all I care about (for now). Is it the same process as the Pixel 2 XL? I'm just curious if anything has changed with Titan being a part of the hardware now.
WisdomWolf said:
Well considering that I would need a copy of the stock boot.img to accomplish this process it seems like we are in arguegreement. [emoji6]
Click to expand...
Click to collapse
Your phone comes with a boot image.
You can patch the boot image with Magisk Manager. Which saves a copy of the patched boot image on your device. Then it needs too be transferred to a PC to be flashed in fastboot. My advice is still relevant. As soon as I have factory images, I will try and root.
I have mine. I'm willing to test whatever/whenever it's safe to do so.
I did enable the "OEM Unlocking" in the developer settings. It didn't come with a USB-C to USB -A cable, so I cannot connect it to a PC anyway.
I have phone in hand.
I would love to test, once the root situation has been figured out. Links to how to get phone rooted appreciated (I'm already aware of how to root it via Magisk (once factory image or standalone boot.img is released), and how to root via TWRP (once TWRP is released)).
Golf c said:
Your phone comes with a boot image.
Click to expand...
Click to collapse
Where is the standalone boot image? Did not come with my phone (no boot.img other than the boot.img that is in slots A and B).
lensgrabber said:
Has anyone unlocked the bootloader? That's all I care about (for now). Is it the same process as the Pixel 2 XL? I'm just curious if anything has changed with Titan being a part of the hardware now.
Click to expand...
Click to collapse
I just unlocked mine. It's the unlocked version, not the VZW version though. Same commands as the XL 2.
sd_matto said:
I have phone in hand.
I would love to test, once the root situation has been figured out. Links to how to get phone rooted appreciated (I'm already aware of how to root it via Magisk (once factory image or standalone boot.img is released), and how to root via TWRP (once TWRP is released)).
Where is the standalone boot image? Did not come with my phone (no boot.img other than the boot.img that is in slots A and B).
Click to expand...
Click to collapse
There is no "standalone" boot image yet. It comes with factory image. Which should be out soon. The boot image is in your device. You can patch the boot image with Magisk Manager or sideload the Magisk zip. I would not do either of those until you have the factory image. If you bootloop, your device will be useless without factory images
mattj949 said:
I just unlocked mine. It's the unlocked version, not the VZW version though. Same commands as the XL 2.
Click to expand...
Click to collapse
Did you use the "unlock_critical" version of the command or just "unlock"?
Golf c said:
You can patch the boot image with Magisk Manager.
Click to expand...
Click to collapse
To which boot image are you referring:
1. The boot image in the factory image (I know how to do this), or
2. The boot image already in the device (I would love to learn how to do this)?
sd_matto said:
To which boot image are you referring:
1. The boot image in the factory image (I know how to do this), or
2. The boot image already in the device (I would love to learn how to do this)?
Click to expand...
Click to collapse
No 2 the boot image in the device. Unlock bootloader.
Download Magisk Manager apk. Im about ready to unlock mine right now. In Magisk Manager select patch boot image file. It will save a copy to your device. Transfer to PC.
Fastboot flash boot image. You will bootloop im sure. AVB has changed with crosshatch.
DO NOT attempt this without factory image.
I will be doing this when factory image comes out.
nirenshah said:
Did you use the "unlock_critical" version of the command or just "unlock"?
Click to expand...
Click to collapse
Just "unlock" the other one is not valid for this one. Sorry, I should have mentioned that!
My apologies gentlemen. You do need a separate copy of the the boot image from the factory image to patch in Magisk Manager. Sorry for the wrong info. Actually it makes sense doesn't it.
Golf c said:
Your phone comes with a boot image.
You can patch the boot image with Magisk Manager. Which saves a copy of the patched boot image on your device. Then it needs too be transferred to a PC to be flashed in fastboot. My advice is still relevant. As soon as I have factory images, I will try and root.
Click to expand...
Click to collapse
I got my Pixel 3XL last night. Excited to get things going on the Pixel 3XL, coming from a Nexus 6P.
I was sad that the factory image isn't immediately available on google's site for this phone, and I don't want to brick it trying to install Magisk without a factory image to fall back onto.
In any case, woot, woot! Phone looks great and I'm going to transfer over my line today.
Cheers,
B.D.
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device
vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group
vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.
kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted
vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.
FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant
I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.
kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.
I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work
This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.
Hey y'all,
I'm switching back to Android after 3 years on iOS and I'm a bit stuck on some changes.
First off, battery life on OOS was terrible and they ended support for OP7Pro this year, with no more major (or even security updates) so I decided to get a custom ROM, and I got this Pixel Experience ROM from here. I'm stuck with a few things:
Trying to root it, looks like the procedure is as simple as patch the boot image in that link with Magisk and flash it from the bootloader via "fastboot flash boot patched.img" but every time I do that and reboot, I get the 1+ splash screen and then nothing, black screen. If I boot back in bootloader and flash the original boot image via "fastboot flash boot original.img" it boots again. Same happens if I just run "fastboot boot patched.img", completely black until I reboot. Does anyone know what could be going wrong here?
Is there any way to install TWRP and make a NAND backup with this ROM? I've been out of the game for a while and I'm confused about why there's no recovery partition but there's A and B partitions, and I keep reading that TWRP can't decrypt data or something like that (I'm pretty sure it could 3 years ago tho)
Thanks!
I would never switch to an iphone for a personal phone because I can't stand it.
I have'nt had to root op7 pro till now because I had enough options. now with support ending I'm on 12.
If you have already upgraded to 12 like me you will probably have to downgrade to 11 first to unlock the bootloader if you haven't unlocked it already. I will not try till may when I get back from my vacation because I can't afford for the phone to go crazy right now. before you attempt to downgrade if you do make sure you back up everything to another spare phone or tablet and make sure you have a backup plan in case you soft brick before you attempt it. https://droidwin.com/downgrade-oneplus-7-7t-7t-pro-android-12-to-android-11-2-methods/ . Man if there is a new way to not have to first downgrade to android 11 someone please chime in, as it would reduce my headaches. Also I need someone to clarify if after I unlock the bootloader, I'll have to flash back to 12 via twrp and reformat the phone again to install Pixel experience?
dragancla said:
boot image in that link
Click to expand...
Click to collapse
That is probably where the problem is.
Which boot image to use depends on exactly which OS version you’re using, and the exact model number of your device.
A lot has changed in the Android world in the last 3 years.
TheMystic said:
That is probably where the problem is.
Which boot image to use depends on exactly which OS version you’re using, and the exact model number of your device.
A lot has changed in the Android world in the last 3 years.
Click to expand...
Click to collapse
Yeah, but that IS the boot image for that OS version and that device, that's why you can download both the ROM and the boot image for that ROM from the same link I posted. If I boot that specific image the device works fine. If I patch that same boot image and boot it, it doesn't work.
dragancla said:
Yeah, but that IS the boot image for that OS version and that device, that's why you can download both the ROM and the boot image for that ROM from the same link I posted. If I boot that specific image the device works fine. If I patch that same boot image and boot it, it doesn't work.
Click to expand...
Click to collapse
Then it means that the patching is not happening properly. Something is not right with the patched image, even if you don't get any errors. Search for this problem on Google. Also see if you can extract the boot image of your device yourself, instead of using the one you have in that link.
billperrotta said:
I would never switch to an iphone for a personal phone because I can't stand it.
I have'nt had to root op7 pro till now because I had enough options. now with support ending I'm on 12.
If you have already upgraded to 12 like me you will probably have to downgrade to 11 first to unlock the bootloader if you haven't unlocked it already. I will not try till may when I get back from my vacation because I can't afford for the phone to go crazy right now. before you attempt to downgrade if you do make sure you back up everything to another spare phone or tablet and make sure you have a backup plan in case you soft brick before you attempt it. https://droidwin.com/downgrade-oneplus-7-7t-7t-pro-android-12-to-android-11-2-methods/ . Man if there is a new way to not have to first downgrade to android 11 someone please chime in, as it would reduce my headaches. Also I need someone to clarify if after I unlock the bootloader, I'll have to flash back to 12 via twrp and reformat the phone again to install Pixel experience?
Click to expand...
Click to collapse
I already have Pixel Experience installed, so my bootloader is unlocked. Has been since I bought the phone 3 years ago
TheMystic said:
Then it means that the patching is not happening properly. Something is not right with the patched image, even if you don't get any errors. Search for this problem on Google. Also see if you can extract the boot image of your device yourself, instead of using the one you have in that link.
Click to expand...
Click to collapse
Google yielded no results, decided to post here to see if anyone else ran into this, I'll try to extract it myself somehow.
Coming out of left field but maybe you need to return to stock with bootloader unlocked. Flash 12 ota then rewipe for PE to get 12 latest firmware? https://www.xda-developers.com/oneplus-7-7t-end-of-life-final-update/
used to flash otas through TWRP when I had a rooted op5T with an unlocked bootloader. So Sad, Oxygen was so good till this last crummy update. Now they are forcing my hand to return to custom roms since OP insists on abandoning Support for the best phone they ever made.
Nothing worked, so I fixed it by wiping the phone and starting from scratch. Guess something bugged out.
thats usually the end all solution. but I have seen situations where you have to be on latest stock firmware to continue. I assume you don't have to copy any partitions because this software is already past Android 10 where treble was first introduced? I'm just asking as many questions as possible because I'm planning to overhaul in may. Did you use the pixel experience flashing instructions from pixel experience.org?
ill probably flash the ota back to twelve through twrp. then flash pixel experience recovery over that when I wipe and start over after the downgrade and bootloader unlock.
billperrotta said:
thats usually the end all solution. but I have seen situations where you have to be on latest stock firmware to continue. I assume you don't have to copy any partitions because this software is already past Android 10 where treble was first introduced? I'm just asking as many questions as possible because I'm planning to overhaul in may. Did you use the pixel experience flashing instructions from pixel experience.org?
Click to expand...
Click to collapse
I was on latest stock (12) before I started doing this. Had my bootloader unlocked since Android 9. Since it's impossible to do anything without unlocking it, that's your first step. I posted the link to PE website in my first post. Didn't copy any partitions. I just installed it and rooted it with a few commands from terminal (with the phone connected):
adb reboot bootloader
fastboot flash boot BOOT.img
fastboot reboot recovery
-- on the phone: wipe data, select install from sideload --
adb sideload ROM.zip
adb reboot
-- on the phone: wait for it to boot, enable developer options --
adb install MAGISK.apk
adb push BOOT.img sdcard/Download
-- on the phone: patch the boot image with Magisk --
adb pull sdcard/Download/magisk_patched-25200_xxxxx.img
adb reboot bootloader
fastboot flash boot magisk_patched-25200_xxxxx.img
fastboot reboot
That's it, installed and rooted. Stop at step 6 if you don't want root.