This phone doesn't have its own section in the forum yet, so I decided to put here a little guide for those who haven't figured out how to root it yet.
There is no twrp version for this Motorola yet, so I'm going to teach you how to root it without recovery.
This is how I rooted my Motorola One Macro:
Unlock your bootloader here.
Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
Download THE SAME VERSION of your compilation from here.
Extract from the zip the boot.img
Copy boot.img in a folder of your choice in your phone.
Install Magisk Manager apk in your phone (download here)
Open Magisk Manager and choose Install --> Install --> Patch file
Select boot.img and wait until it's patched
A new file would be created in the same folder you put the boot.img, named magisk_patched.img
Copy magisk_patched.img to your PC.
Reboot your phone to bootloader
Now replace the boot.img of your phone with the new one patched by magisk using the following commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
And now you are rooted. Enjoy
Pretinaverse said:
This phone doesn't have its own section in the forum yet, so I decided to put here a little guide for those who haven't figured out how to root it yet.
There is no twrp version for this Motorola yet, so I'm going to teach you how to root it without recovery.
This is how I rooted my Motorola One Macro:
Unlock your bootloader here.
Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
Download THE SAME VERSION of your compilation from here.
Extract from the zip the boot.img
Copy boot.img in a folder of your choice in your phone.
Install Magisk Manager apk in your phone (download here)
Open Magisk Manager and choose Install --> Install --> Patch file
Select boot.img and wait until it's patched
A new file would be created in the same folder you put the boot.img, named magisk_patched.img
Copy magisk_patched.img to your PC.
Reboot your phone to bootloader
Now replace the boot.img of your phone with the new one patched by magisk using the following commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
And now you are rooted. Enjoy
Click to expand...
Click to collapse
hi...
this guide works for me.
Motorola One Macro LatinAmerican version Telcel.
Pretinaverse said:
This phone doesn't have its own section in the forum yet, so I decided to put here a little guide for those who haven't figured out how to root it yet.
There is no twrp version for this Motorola yet, so I'm going to teach you how to root it without recovery.
This is how I rooted my Motorola One Macro:
Unlock your bootloader here.
Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
Download THE SAME VERSION of your compilation from here.
Extract from the zip the boot.img
Copy boot.img in a folder of your choice in your phone.
Install Magisk Manager apk in your phone (download here)
Open Magisk Manager and choose Install --> Install --> Patch file
Select boot.img and wait until it's patched
A new file would be created in the same folder you put the boot.img, named magisk_patched.img
Copy magisk_patched.img to your PC.
Reboot your phone to bootloader
Now replace the boot.img of your phone with the new one patched by magisk using the following commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
And now you are rooted. Enjoy
Click to expand...
Click to collapse
This worked for me too.
Hello! Thank you very much for the tutorial for the Moto One Macro. I was tired of looking for a tutorial for mine.
But one question remained: Because I am unable to install a Recovery, am I unable to flash a custom rom? Because I was trying to root the device just to install a Custom Rom of the Lineage OS type of Android 10, considering that as far as Motorola is concerned, the pro 10 update will not come anytime soon. But I still thank you for the tutorial.
Sent from my Motorola One Hyper using XDA Labs
Question
I have multiple questions I would like to ask.
1. Would this format the phone? Which partitions will get formatted?
2. Can you explain the namings of the folder in the link to the post? What do they mean? I've seen a compilation number close to mines in the 'retail' folder.
3. From where do people get these uploads? I've tried multiple times contacting Motorola for image uploads and they never sent anything. I am very interested in the origin of the files.
4. Is there anyway to recover from a failed patch?
The reason I want this is that I've tried patching the bootloader using an image from a fishy website and it soft-bricked my phone, I had to reformat the whole thing with a fresh image
Btw, thank you for contributing to the phone's community!
Update:
Installed successfully, magisk is enabled and root is functioning and whatnot. Problem is, sometimes on booting the phone hangs on the weird colorful animation. It's not consistent and I can't figure out why. I discovered force rebooting the phone multiple times boots the phone successfully but does not fix the problem. Boot times are slower, probably because of modules.
Screen mirroring Motorola one
Hello,
I have a root Motorola one Android 10, but I can't share my screen to my Samsung smart TV, i search a lot but I didn't have success, first I edited the build.prop lines,
persist.debug.wfd.enable=1 (before it was persist.debug.wfd.enable=0)
persist.hwc.enable_vds=0 (before it was persist.hwc.enable_vds=1)
I added this in the end
wlan.wfd.hdcp=disable
I added another line but I don't remember all because I erased it, i only remember the beginning
Persist.sys....
But it can't work, in my TV only show something like
"Screen mirroring: motorola is connecting" but then the signal is lost
Nothing that I tried work, only one thing is good and is that in my cellphone in the option of share screen after change this line: persist.debug.wfd.enable=1 (before it was persist.debug.wfd.enable=0) I could activate wireless screen and it let me TRY to connect with my TV but without success.
In other post show the last configuration with an extra thing, I should edit a file (wfdconfig.xml) and it supposed to stay in this direction system/etc/ wfdconfig.xml. But I search in all files and I didn't find.
Maybe someone can help me.
Thanks.
altffour said:
I have multiple questions I would like to ask.
1. Would this format the phone? Which partitions will get formatted?
2. Can you explain the namings of the folder in the link to the post? What do they mean? I've seen a compilation number close to mines in the 'retail' folder.
3. From where do people get these uploads? I've tried multiple times contacting Motorola for image uploads and they never sent anything. I am very interested in the origin of the files.
4. Is there anyway to recover from a failed patch?
The reason I want this is that I've tried patching the bootloader using an image from a fishy website and it soft-bricked my phone, I had to reformat the whole thing with a fresh image
Btw, thank you for contributing to the phone's community!
Update:
Installed successfully, magisk is enabled and root is functioning and whatnot. Problem is, sometimes on booting the phone hangs on the weird colorful animation. It's not consistent and I can't figure out why. I discovered force rebooting the phone multiple times boots the phone successfully but does not fix the problem. Boot times are slower, probably because of modules.
Click to expand...
Click to collapse
Motorola doesn't official share the firmware, but there has always been people with access to the firmware servers.
https://mirrors.lolinet.com/firmware/moto/ has lots of moto firmware
LMSA can also be used to get firmware for most moto devices
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Can't find build number
Pretinaverse said:
[*]Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
[*]Download THE SAME VERSION of your compilation from here.
Click to expand...
Click to collapse
Hi, I can't find my Build Number in there. Mine is PMDS29.70-81-3.
I see several PMDS29.70-81 but none of them have the -3 I need. Any suggestions?
lorenzzv said:
Hi, I can't find my Build Number in there. Mine is PMDS29.70-81-3.
I see several PMDS29.70-81 but none of them have the -3 I need. Any suggestions?
Click to expand...
Click to collapse
yeah me too, but I solved it, I just rooted mine just download and use Rescue and Smart Assistant to download your firmware and repeat the steps above and that's it, it took me about five minutes to root my phone.
Can any one please confirm, if after rooting this phone are you able to do call recording both side clearly ?
Not working
Help, I did this and now my phone is stuck on the Motorola logo, ¿is a way to undo this process? T_T
just download motorola smart assisstant on your laptop and plug your mobile to it and it will do the rest
atattooedgod said:
just download motorola smart assisstant on your laptop and plug your mobile to it and it will do the rest
Click to expand...
Click to collapse
That did the trick. MY ETERNAL GRATITUDE TO YOU, SIR. YOU ROCK.
HELP
atattooedgod said:
yeah me too, but I solved it, I just rooted mine just download and use Rescue and Smart Assistant to download your firmware and repeat the steps above and that's it, it took me about five minutes to root my phone.
Click to expand...
Click to collapse
Hey bro, im looking for this, can u upload? or give any link related? LMSA is coded by monkeys with cocaine in water and tells that my XT2016-2 is'nt compatible :\
Help!
I am from Brazil and I have a Motorola One Macro and the device does not appear in the list of supported devices for OEM unlocking on the Motorola website.
Do you have TWRP for XT2016-2 ?
mrmanson07 said:
I am from Brazil and I have a Motorola One Macro and the device does not appear in the list of supported devices for OEM unlocking on the Motorola website.
Click to expand...
Click to collapse
Ignore the list the list of never been complete.
The only way to know if the bootloader can be unlocked is to try to unlock it.
Sent from my Moto E (4) using Tapatalk
Nice
VD171 said:
Do you have TWRP for XT2016-2 ?
Click to expand...
Click to collapse
There is not, but i am working on developing one we'll see soon if i can complete it succesfully due actually there are a lot of problems with this one
TWRP would be a nice treat here. Keep the thread updated on any progress.
Related
Hello Everyone,
This is my first tutorial here.
So, any mistakes should be reminded in the thread.
==================================================
Guide for rooting with MAGISK==================================================
This guide is for those devices for which currently there is no custom recovery available. So, don't be sad instead have MAGISK Root for your device and and sleep well.:angel:
Note - USE THIS GUIDE ON YOUR OWN. I AM NOT RESPONSIBLE IF YOU END UP BRICKING YOUR DEVICES.
BETTER KNOW WHAT YOU ARE DOING AND ITS CONSEQUENCES.
==================================================
REQUIREMENTS -
1 - An Android 5.0+ device
2 - PC with working ADB
3 - Stock boot image (boot.img) of your device
4 - Magisk Manager app
5 - A good file browser like Mixplorer, Solid explorer etc..
6 - Active Internet connection
7 - Active mind and patience.
==================================================
Step 1: Patching the stock boot.img
- Install MagiskManager apk on your android device
- Copy the stock boot.img of your device to your phone's internal storage or SD card
- Launch Magisk Manager app
- If prompted to install Magisk, select NO THANKS
- If you are using a samsung device and wish to flash using Odin, then select Options > Settings > Update Settings > Patched Boot Output Format > img.tar )
- Select Install > Install > Patch Boot Image File >
Navigate to the location of the stock boot.img you copied earlier on, then Select it
-Magisk Manager should begin downloading the magisk zip file used for patching
-Once download is complete, MagiskManager will automatically patch the boot file and store it under SDcard/MagiskManager/patched_boot.img[.tar]
Step 2: Flashing the patched boot.img
You have a variety of options to flash the patched boot.img depending on your chipset (e.g Mediatek MTK, Spreadtrum SPD, Qualcomm QLM etc ), the resources you have and your skills. Note that some flashing methods might require you to rename the file to boot.img
- For those using MTK devices and have the specific scatter file for their device, you can flash the patched boot.img using SP flash tool or Miracle Box
-For those using SPD devices and have the PAC file for their device, you can flash the patched boot.img using Research download tool by replacing the stock boot.img with your patched boot.img
- For those using Samsung devices and then use ODIN to flash.
-You could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below
How to Flash patched_boot.img using Fastboot
-Setup adb and fastboot on your PC.
-Unlock the phone's Bootloader (if its not unlocked)
-Re-enable USB debugging on the phone
-Connect the phone to the PC via USB cord
-Boot into fastboot mode.
-Flash the patched_boot and reboot by typing in the commands below into adb CMD prompt window and hitting Enter after each line -
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
-Verify root using Root Checker
Credits goes to topjohnwu of XDA for Magisk
Also to X3non of Hovatek for original guide.
Does this work with lenovo vibe k4 note?
I think this thing would be risky to do.
Or what do you think?
Does the bootloader need to be unlocked still? I have a S6 Active (sm-g890a) that I would love to root with this method but I haven't wanted to try anything in fear of bricking. Sorry for the newb question but I'm a noob.
Sent from my SM-G900V using XDA Labs
2FrEsH99 said:
Does the bootloader need to be unlocked still? I have a S6 Active (sm-g890a) that I would love to root with this method but I haven't wanted to try anything in fear of bricking. Sorry for the newb question but I'm a noob.
Sent from my SM-G900V using XDA Labs
Click to expand...
Click to collapse
if the bootloader checks boot.img, it will fail since Magisk patches the boot.img and it will have an invalid signature.
This process is only useful for locked bootloaders that do not check boot.img or people who want stock or are stuck with stock recovery.
2FrEsH99 said:
Does the bootloader need to be unlocked still? I have a S6 Active (sm-g890a) that I would love to root with this method but I haven't wanted to try anything in fear of bricking. Sorry for the newb question but I'm a noob.
Sent from my SM-G900V using XDA Labs
Click to expand...
Click to collapse
Hi, the best way is to flash a custom recovery beforehand. But if you can't find you can go for this method but bootloader must be UNLOCKED. And also if anything goes wrong even if the bootloader is UNLOCKED , the phone will only be soft brick not hard brick. But the best thing will be a custom recovery method.
Cjoman said:
Does this work with lenovo vibe k4 note?
Click to expand...
Click to collapse
If your device bootloader is UNLOCKED, then you are good to go. But you should look for a custom recovery for your device and flash magisk.zip . Try this method only if you can't find one. Although every method is risky, you should play safe.
DE SEXIEST said:
I think this thing would be risky to do.
Or what do you think?
Click to expand...
Click to collapse
Of course this method is risky yet safe.
If you have a less secure device with UNLOCKED bootloader, you should try this.
But the best thing will be to find a custom recovery or try to port one.
This method should work on most devices.
Aquib132 said:
If your device bootloader is UNLOCKED, then you are good to go. But you should look for a custom recovery for your device and flash magisk.zip . Try this method only if you can't find one. Although every method is risky, you should play safe.
Click to expand...
Click to collapse
Okay thanks!
---------- Post added at 02:33 AM ---------- Previous post was at 02:03 AM ----------
Will this factory reset my phone?
does it work / may work with S9 plus G965U Qualcomm chipset?
as i didn't find any Oem unlock option in the developer menu.
A7 2017 (Android 8)
So i have an a7 2017 with android oreo or know as 8.0.0. So i want to flash the patched boot image with odin. How do i do that? Like i understand you need oem unlocked but where do you flash it specifically in odin?
Use ADB and the push command.. Be careful what you type.. This thing is a ***** to get the first time.. I wish you good luck
---------- Post added at 07:16 AM ---------- Previous post was at 07:10 AM ----------
Remember one other thing.. Sammy can not use Fastboot.. It's not that it's bad.. But it just won't in most cases.. Try CROM first to unlock the bootloader
Thanks, very helpful!
Well i tried to root my phone before with cf auto root and with twrp and it said device verification has failed or something. Will it happen for this device?
How do i copy the stock boot image onto my internal storage?
I'm having a question: does the new patched_boot.img file also contain my personal data? If not, then what's the best way to make a backup so that when I restore it my phone to be just like I didn't do anything to it(it should have all my apps, files,contacts, accounts etc untouched), but to be rooted? I have a Elephone a4 and I can't set up a custom recovery, that's why I want to follow this tutorial...
Pcarioca said:
I'm having a question: does the new patched_boot.img file also contain my personal data? If not, then what's the best way to make a backup so that when I restore it my phone to be just like I didn't do anything to it(it should have all my apps, files,contacts, accounts etc untouched), but to be rooted? I have a Elephone a4 and I can't set up a custom recovery, that's why I want to follow this tutorial...
Click to expand...
Click to collapse
Go to smart switch and create a backup.
Easy peezy
Works as advertised. One thing i would add to the guide is copying the patch boot img to where the command prompt window is opened. If i was using my noodle, it would be an unspoken, but i forgot and had to reboot once more. This would've saved me about 30 seconds, but i won't complain. I am on the moto z2 force sprint may 1 update with an unlocked bootloader
I think this thing would be risky to do.
emod0705 said:
Try CROM first to unlock the bootloader
Click to expand...
Click to collapse
Sir what is CROM?
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.
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?
Just a heads up to anyone who is wondering about root for this phone - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus model, and it worked. Obviously you need to have already unlocked the bootloader before doing any of this.
I got the stock boot.img from the firmware linked in this thread. I patched it using Magisk Manager (v8.0.7) then flashed it via fastboot. My installed Magisk version is 21.4 (21400).
-- A WORD OF CAUTION: --
As of now there is no TWRP or any other custom recovery for this phone that I am aware of, so if you mess something up due to root, your only option to fix it might be to reflash the stock firmware.
A note about mobile banking apps:
After I installed Magisk Manager, my banking app stopped working and SafetyNet check was failing. After flashing the patched boot.img and rebooting, the SafetyNet check passed but my banking app still wasn't working. I used Magisk Hide and checked off the banking app in the list, but that didn't help either. What I had to do was use the Hide Magisk Manager option where it reinstalls Magisk Manager under a different name. Now my banking app is working again.
DM.IDOL said:
... - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus model, and it worked. ...
Click to expand...
Click to collapse
It worked for me too. It was also easy for me because the only RETUS upload on the mirrors.lolinet site was my exact firmware version. Downloaded that, extracted and used that boot.img for magisk-patching.
The only issues I'm left with are:
1. Adaway isn't working (can't write to any of the canned hosts file paths) and I haven't figured out where I might be able to store a writable hosts file, and . . .
2. Titanium Backup (Pro) works to freeze almost every app that I wanted to disable. The one exception was Motorola Update Service. TiBu toasts that it was disabled and "invisible from the app drawer", but it actually wasn't disabled and still isn't. It still shows under System Applications. So I dunno . . . it's not a deal breaker as long as auto updating stays turned off.
Bootloader is unlocked and rooting via Magisk worked on my Stylus 2021, exactly as advertised.
Update: My solution for AdAway was here, AdAway 5.3 (newest version I believe).
Update2: Sans freezing Motorola Update Service, updates are of course frozen from actually running because of system changes by root & TWRP. So no big worries, just the nuisance of notifications.
cant the new maagisk be used as an alternative custom recovery? Something about renaming the apk to zip and then flashing zip file on recovery?
Mr.Morgan said:
cant the new maagisk be used as an alternative custom recovery? Something about renaming the apk to zip and then flashing zip file on recovery?
Click to expand...
Click to collapse
No, Magisk is not custom recovery.
There are two ways to install Magisk, using the .zip version, with a custom recovery like TWRP or
Using the magisk app to patch a boot.img then flash with fastboot.exe
sd_shadow said:
No, Magisk is not custom recovery.
There are two ways to install Magisk, using the .zip version, with a custom recovery like TWRP or
Using the magisk app to patch a boot.img then flash with fastboot.exe
Click to expand...
Click to collapse
I appreciate the knowledge, but perhaps you can shed some light on what the app means by " Custom Recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC. Check out the updated installation guide for more info"
Mr.Morgan said:
I appreciate the knowledge, but perhaps you can shed some light on what the app means by " Custom Recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC. Check out the updated installation guide for more info"
Click to expand...
Click to collapse
You are partly correct, there has been a big change with Magisk.
You can just change the Magisk.apk to Magisk.zip
But the zip does not replace a custom recovery.
It just eliminates the need for a separate manager.zip
In some custom recoveries, the installation may fail silently (it might look like success but in reality it bootloops). This is because the installer scripts cannot properly detect the correct device info or the recovery environment does not meet its expectation. If you face any issues, use the Patch Image method as it is guaranteed to work 100% of the time. Due to this reason, installing Magisk through custom recoveries on modern devices is no longer recommended. The custom recovery installation method exists purely for legacy support
Click to expand...
Click to collapse
Magisk in Recovery
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.
When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.
Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.
Click to expand...
Click to collapse
This does not replace the stock recovery, just patches the recovery.
I recently purchased this phone, Moto G Stylus 2021, from Amazon. When I enter the dev options menu, OEM Unlocking is greyed out. I did a bit of research and found another thread online where another two users had the same problem, for all of two days.
After two days, the option to enable OEM Unlocking was no longer greyed out for the both of them. Fascinating! I may return this phone before that time is up, but if I don't, I'll report back on any changes for sure.
EDIT: I've decided to return this phone and get a Galaxy Tab S7 instead; there's more room to draw and a better pen!
Can't find my firmware on lolinet (boost mobile qpc30.q4-31-93)
Tried lenovo's rescue tool to see if I could grab the firmware that way and it just kept giving me errors.
If anyone has some how acquired the appropriate firmware would you mind sending it to me?
I can't remember exactly where I seen someone else commenting on this topic but they had lost their cellular network after rooting ,
My problem / question is that I have also my lost my cellular network connection after rooting but not completley only to the original carrier I got t this phone with witch is boost, but if I try another carrier such as tmobile or sprint or even metro it will work because they are basically all 1 company now , but how do I fix this problem to get my phone to read my sim card as valid (I get the invalid sim msg) when I put my original sim in and I just went and got a brand new replacement sim from them to see if that would solve the issue.also going off reading the forums on here I went with the mask retus firmware for flashing because there isn't one on there anywhere for so any help would be hysteria l greatly appreciated. This is my only problem I'm having since rooting everything else is working perfectly fine.
BobbyBlunt said:
Can't find my firmware on lolinet (boost mobile qpc30.q4-31-93)
Tried lenovo's rescue tool to see if I could grab the firmware that way and it just kept giving me errors.
If anyone has some how acquired the appropriate firmware would you mind sending it to me?
Click to expand...
Click to collapse
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
riggin said:
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
Click to expand...
Click to collapse
I tried the lenovo recovery tool again and this time it was able to find the appropriate firmware. I was able to successfully root
Hey well i just installed latest magisk and patched boot img and moved it to my pc and went thru fast boot and just did fastboot flash boot patched.img and it works fine. I dunno if latest update fixed whatever was wrong on yours but if i installed the older one it would not even let me pick the boot img to patch *shrugs* but all working on mine now...we just need full device tree etc so we can get us a a recovery def want that before i go adding mods. If it helps any I have cricket same as ATT the person who lost cell may need to redo their apn or take sim card out and reapply it hope that works.
Moondroid said:
The one exception was Motorola Update Service. TiBu toasts that it was disabled and "invisible from the app drawer", but it actually wasn't disabled and still isn't. It still shows under System Applications.
Click to expand...
Click to collapse
I've been having the same problem trying to disable the update prompts. Titanium Backup doesn't work, nor can I disable it via terminal using pm. The system update screen will pop up multiple times a day, interrupting whatever I'm currently doing to tell me I have an update. It's really annoying that it can't be frozen.
Well after a few days of LTE connection my own unlock now works got root
riggin said:
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
Click to expand...
Click to collapse
hey was just wondering since im kinda in the same situation you were in with not being able to obtain exact firmware need at first for boost model if maybe you can proovide tthe brief steps you made to get the lmsa tool to recognize it and pull the corerct firmware....ty so much if u can
riggin said:
hey was just wondering since im kinda in the same situation you were in with not being able to obtain exact firmware need at first for boost model if maybe you can proovide tthe brief steps you made to get the lmsa tool to recognize it and pull the corerct firmware....ty so much if u can
Click to expand...
Click to collapse
Unfortunately, either LMSA determines the correct firmware or it doesn't, there isn't anything that can be done to fix it, except contacting Motorola.
For other options see
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Hey Guys, I'm continuing on this thread since I've gotten further. I used LMSA to download the firmware zip using the Resuce button. Afterwards I copy that zip (2+ gigs) to my download folder. I open up Magisk and select intall and select the firmware zip. I starts out successfully but then fails. I get this in the log folder.
- Device platform: arm64-v8a
- Installing: 23.0 (23000)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed
I even tried to resuce the phone using the firmware provided by the LMSA program which essentially wipes my phone and try again with a clean Magisk load and I'm getting the same. The only thing I'm thinking is I could be getting my Magisk from another source. I'm using version 23 from github.
steppinthrax said:
Hey Guys, I'm continuing on this thread since I've gotten further. I used LMSA to download the firmware zip using the Resuce button. Afterwards I copy that zip (2+ gigs) to my download folder. I open up Magisk and select intall and select the firmware zip. I starts out successfully but then fails. I get this in the log folder.
- Device platform: arm64-v8a
- Installing: 23.0 (23000)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed
I even tried to resuce the phone using the firmware provided by the LMSA program which essentially wipes my phone and try again with a clean Magisk load and I'm getting the same. The only thing I'm thinking is I could be getting my Magisk from another source. I'm using version 23 from github.
Click to expand...
Click to collapse
It isn't a zip file it's a folder or at least every firmware I have downloaded is automatically unzipped by LMSA.
You only need to copy the boot.img and maybe the recovery.img to the device.
sd_shadow said:
It isn't a zip file it's a folder or at least every firmware I have downloaded is automatically unzipped by LMSA.
You only need to copy the boot.img and maybe the recovery.img to the device.
Click to expand...
Click to collapse
Thanks I figured it out last night. I also figured out pretty quickly that once you root a phone certain applications will no longer function. I didn't deal with this before, but since I work from home I have to use some of those apps that create a "Work Profile". The one app "Intelligent Hub" removed itself and my work profile. When trying to re-install and authenticate with my work it literally said "Won't provision a compromised device".
Within Magsik I used the Magsik hide feature and tried selected that app and hiding all methods that it could detect root. I even then rebooted, removed/reinstall etc. Nothing worked. The app still kept detecting root. I know that the Xposed Framework modules may work in hiding root but I decided to go all the way back to normal since there's little benefit for me to root except for the ability for me to remove bloatware. This is a retail unlocked and there's little if any bloatware on the device.
I removed Magsik and any other junk, turned on OEM locking and rebooted and I'm back to mormal. Thank you everyone this was a leaning exp. I haven't rooted in like 5 years.
DM.IDOL said:
I've been having the same problem trying to disable the update prompts. Titanium Backup doesn't work, nor can I disable it via terminal using pm. The system update screen will pop up multiple times a day, interrupting whatever I'm currently doing to tell me I have an update. It's really annoying that it can't be frozen.
Click to expand...
Click to collapse
FYI, for posterity, instead of getting multiple notifs per day I just tap and let it try to update. It fails quickly and the notification is nixed for a while.
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Gregbmil1 said:
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Click to expand...
Click to collapse
Hey, thanks for your reply. I am really eager to root it. I almost just went for it. However, then I thought about it. If something went wrong I would not have any way to recover the phone since there is not a system image available yet. I have not given adb removal a try yet as I figure it would just be easier to go with rooting since it will help me with everything I am trying to achieve. If I cannot root it then I will go the adb route. Hopefully someone will come along and help me out. Fingers crossed
Let us know what you end up doing. Are you expected to send the phone back after the beta testing? If you are responsible for any damages done to it, I would not try it.
You could send it back bricked and say you have no idea what happened to it, lol. That or say you were "testing" the security of the device and that it passes
bigroc2223 said:
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
Click to expand...
Click to collapse
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
dladz said:
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
Click to expand...
Click to collapse
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
bigroc2223 said:
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
Click to expand...
Click to collapse
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
dladz said:
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
Click to expand...
Click to collapse
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
bigroc2223 said:
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
Click to expand...
Click to collapse
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
dladz said:
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
Click to expand...
Click to collapse
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
bigroc2223 said:
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
Click to expand...
Click to collapse
You're very welcome.
Chances of it not booting after doing that? Absolutely zero.
It's a copy not a cut, so you're fine.
The only problem you may encounter is the ability to access the device on that level.
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
I would advise against flashing it, just boot it.
dladz said:
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
Click to expand...
Click to collapse
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
jwoegerbauer said:
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
Click to expand...
Click to collapse
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
bigroc2223 said:
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
Click to expand...
Click to collapse
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It's a phone for testing which I am allowed to keep.
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It is a phone for testing which I am allowed to keep. Specs are Snapdragon 750g, Adreno 619, and 4gb of ram. Not too shabby for a free phone. It is a lot snappier than the moto e6 I was previously using.
dladz said:
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Click to expand...
Click to collapse
This method requires TWRP. So this will not work.
bigroc2223 said:
Nvm
Click to expand...
Click to collapse
dladz said:
Again!!!? What's your problem??
You're just trying to (for whatever reason) prove me wrong and yet again I wasn't being descriptive of an ADB pull!!!
You're pulling the boot.img off the device by whatever means.
To be clear for the final time, I'm not stating to use twrp, a script or anything else I said look it up / Google it!
Now if you've helped the chap then that's great, looking at what I said and attempting to put me straight when you clearly don't have to, is no help to you or the chap needing help it's just making you look like you're on a power trip.
Click to expand...
Click to collapse
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
bigroc2223 said:
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
Click to expand...
Click to collapse
Sorry I got the wrong end of the stick, I thought you was a second person posting..
Forget what I said