Reason for edit: Change title so more users can find this method since for now TWRP is working but not to root
Click to expand...
Click to collapse
Hello fellow XDA users,
On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
I've been following all threads here on XDA and for the last few days its like a boom of new information, yesterday a Senior Member provided me with the Unlock Key generated with my IMEI1 and the phone's bootloader is now unlocked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now the next logical part I would be installing TWRP to flash the magisk flashable zip to the phone, but there is no TWRP built to our phones (old information, there is now an official TWRP build)..
To my surprise there is this thread that offers boot images already patched with root ( @nummerok are they patched under magisk?), I tried flashing first with:
Code:
fastboot boot NB1-0-484A-00WW-boot.img
But it did not worked, no matter what the installed Magisk Manager would not find the Magisk Module on the system.
Then I found out that some users were getting root but with the problem of losing wifi connectivity, that was found to be the fault of the phone having the March Security Patch (00WW_4_84A_SP01) while flashing the boot image of the phone with the February Security Patch (00WW_4_84A).
As of this new A-B partition scheme on Android, when your boot image does not pass dm-verity it restores the older version automatically (Am I right on this point?? can please someone confirm?!)
Since my phone WAS on the march patch I saw no other option but to wait someone to grab the march boot image to patch it Magisk Manager and get root.
Buut since my generation doesn't like to sit and wait I found that there was a way to roll back to the previous firmware!
What I did was, run this code below on adb to know which slot my phone was:
Code:
adb shell getprop ro.boot.slot_suffix
Then take note of the slot and run:
Code:
adb reboot bootloader
After the device starts up in Download Mode you need to switch to the other boot slot. Just run:
Code:
If you are currently on slot A, type this: [B][I]fastboot --set-active=_b[/I][/B]
Or on slot B type this: [B][I]fastboot --set-active=_a[/I][/B]
You should see something like this:
Code:
Setting current slot to 'a'... OKAY [ 0.046s] finished. total time: 0.046s
Now run the code below and cross your fingers!
Code:
fastboot reboot
Once the phone has booted, check in Settings/System/About Phone if your Android security patch level has downgraded to the February one and proceed to the next step.
I've downloaded the full NB1-484A-0-00WW-B03.nb0 firmware from @blackpanther0582 thread under the google drive link and extracted the boot image using the tool made by @heineken78 available over here (be sure to have lots of ram available for the unpack process :fingers-crossed.
With the file NB1-0-484A-00WW-boot.img at hand I've copied it to the Nokia 8 internal storage and ran Magisk Manager to patch it, follow instructions here under Via Magisk Manager (Only support v14.0+) part.
Now grab the patched_boot.img file provided by Magisk from the phone and save it (adb pull or whatever) to your pc and run these commands:
Code:
adb reboot bootloader
After the phone boots up in Download Mode run:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
With that done, after the boot you can open Magisk Manager to see it fully installed and later on install some root checker app just to be sure of the sucess of your rooting:
Split-screen to the rescue lol
This Nokia 8 is officially rooted but with the previous February patch and I'm itching to install the March OTA provided by @2WildFirE here, any thoughts on that? What about the official system update that still lists the 2018-03 security patch? Would any of which work?
And that is all for now folks!
I would like to thank @the_laser @heineken78 @topjohnwu @blackpanther0582 @nummerok and many others in this invaluable path to learning more about this phone and the Android system in general!
Good Luck!!
Reserved
Nice, this will help some people to understand.
Powered by Nokia 8 with open bootloader
2WildFirE said:
Nice, this will help some people to understand.
Click to expand...
Click to collapse
That's the idea @2WildFirE !
btw just to make things clear, the official system update is running for like 10 hours and it seems it's not going anywhere.. would I get success by doing the march update thru the zip you've found?
Yep was working fine here, to bring my wifi back, but lost root [emoji6] what we Really need is twrp and or a method to extract the boot.img from the *. Bin file included in the update zip.
Powered by Nokia 8 with open bootloader
I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?
contrahelix said:
I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?
Click to expand...
Click to collapse
It should work only if you have your bootloader unlocked @contrahelix
You might get it unlocked officially by Nokia or wait for an alternative method.
Also you should update your adb/fastboot tools, then you would get the right error message telling you about the still locked bootloader!
On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
Click to expand...
Click to collapse
I have a TA-1012 i assume it won't work for me?
For everyone with unlocked bootloader, this is the method to root without TWRP !
Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...
Raithlin said:
Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...
Click to expand...
Click to collapse
Still have to rollback to official image.. you cannot upgrade with patched img unfortunately
As u have unlocked bootloader and installed magisk i have a question .
Is it worth to unlock bootloader and install magisk.......?
And one more any custom rom available for nokia8 ta1004.......?
شرا
Related
Starmobile Up Prime
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SOME INFO:
MT6737/M (they seem to be the same thing)
Antutu Score: 30052 [source]
As of Jan 6 2018, latest official firmware is v13 06292017.
A. Root
Disclaimer: YOU ARE DOING THIS AT YOUR OWN RISK. I will not assume any responsibility for your own actions on your phone. Follow the instructions carefully, and ask questions if you're unsure.
Tested way: Magisk Manager patched boot method
Other option: SRS Root reports to root the v12 firmware, though I didn't use this method so I don't know if it works.
Magisk Manager Patched Boot Method
1. Unlock your bootloader (Note: this will factory reset your phone and you will lose all your personal data) To do this:
Enable bootloader unlock inside developer options, accessed by pressing build number 7 times in settings. Thanks @Nao Tomori !
Install adb and fastboot on a computer (Search it, it's available)
Reboot to fastboot mode (Switch off phone, press power and volume up simultaneously. Choose fastboot mode from the menu that appears)
Connect to computer by USB Cable provided
Open a command prompt or terminal and check if fastboot detects your device by typing
Code:
fastboot devices
A device number should appear. If nothing appears, it's a most likely driver problem. Click this button to know more.
Linux doesn't need drivers so try using fastboot in linux. If you really want to do it in windows, try PDANET drivers while connected in fastboot mode. No guarantees. I'm using a linux machine to specifically avoid this hassle
We're now gonna unlock your bootloader. Type
Code:
fastboot oem unlock
and confirm unlock by clicking volume up on your phone.
Reboot and go through all the necessary set-up.2. Download Magisk Manager from here and install the APK.
Make sure you download the latest apk version provided.
Note it says that Magisk itself is not yet installed.
We've only installed the helper app.
3. Flash Patched Boot Image
At this point you have two options: extract and patch your own boot image, or just use my patched boot image. I will assume you pick the second but this REQUIRES that you are on the same v13 06292017 official firmware. PM me if you want to do the first one. Download my patched boot image.
Download
Move the file to a known location that's easy to type (home directory or C Drive)
Reboot to fastboot mode, same as before
Flash with fastboot then reboot
Code:
fastboot flash boot /path/to/patched_boot.img
Code:
fastboot reboot
CONGRATS! Magisk should now be installed and along with it, Magisk's Superuser
Press thanks if it helped you! And/or leave feedback if it worked for you, and if your setup differed from mine. Thanks
MODS
B. Mods
1. Xposed Framework (systemless)
Install Xposed framework from within Magisk. Install API24.
Then reboot. This first boot takes really long. I pulled out my battery once, then the next time it successfully booted after a while.
Install topjohnwu's Xposed apk from his systemless Xposed thread.
It will tell you that Xposed is installed but not active yet.
Reboot one last time
2. Dolby Atmos (systemless)
Install from within Magisk. Confirmed working!
RECOVERY
Reserved
If you get fail operation
If you get
Code:
FAILED (remote:
Unlock operation is not allowed
)
Just go to Developer Settings > OEM Unlocking and enable it.
I used PDAnet for Windows and it worked
Nao Tomori said:
If you get
Code:
FAILED (remote:
Unlock operation is not allowed
)
Just go to Developer Settings > OEM Unlocking and enable it.
I used PDAnet for Windows and it worked
Click to expand...
Click to collapse
Oh yes, I forgot about that! Thanks. Will add and credit you
hi there bro. i just want to know, is there a custom rom that we can use for this phone? i have the same exact phone but i cannot find any articles about any other custom roms that has been used on this phone. hoping to hear from you. thanks.
And another thing, can we use TWRP for this phone?
Hello. Is there anyone here who has a clean stock rom for Starmobile UP Prime? The phone keeps popping up ads and redirecting to chrome/google play. Contact names sometimes disappear too. I ran the malwarebytes app and it said that "Settings" app is the malware. I downloaded and flashed another rom before (I forgot from what website), but same experience. Hoping for helpful response.
The only command prompt that seems to be working is fastboot flash boot twrp.img but when I type fastboot flash recovery the flash fails. I use Minimal ADB and Fastboot command prompt. The latest version too. I downgraded my android 11 to 10 successfully. I have no problems rooting magisk through ADB but why can't TWRP permenantly stick? How can I force it to stick as my main recovery no matter what rom I flash?
Crap. I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10. Sorry for the confusion. Any tips of how to retain twrp? Having problems with my unlocked pixel 4a.
This guide shows you how to get TWRP to stick:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
P4a doesn't have a recovery partition anymore, recovery is part of the boot.img. That's why the fastboot cmd fails.
UltimateGamer83 said:
Crap. I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10. Sorry for the confusion. Any tips of how to retain twrp? Having problems with my unlocked pixel 4a.
Click to expand...
Click to collapse
You can't flash recovery on this phone. It's part of boot.img. Put the TWRP.img file in your internal storage of your phone. Flash the TWRP temporarily first. Fastboot boot TWRP.img. When TWRP boots, click install, then select install image. Choose your TWRP file and select install Ramdisk. Swipe to flash. TWRP will then be installed permanently. You must also be using a custom kernel with TWRP compression support because the partition is not big enough and must be compressed otherwise you will run into issues like TWRP freezing or touch screen issues.
I tried that and twrp still wont stick even after a OTA update flash. I installed ram disk twrp even after the update. What gives?
I fixed it. My mistake was flashing magisk boot img after the ramdisk installation and two kenel. I just flashed magisk.zip instead and got things working.
UltimateGamer83 said:
I fixed it. My mistake was flashing magisk boot img after the ramdisk installation and two kenel. I just flashed magisk.zip instead and got things working.
Click to expand...
Click to collapse
Yes, if you flash magisk boot img it will replace TWRP. Flashing the zip is the way to go. Glad you got it working.
UltimateGamer83 said:
I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10.
Click to expand...
Click to collapse
I've move your thread out of development, for which it doesn't qualify.
And I assumed your consent and edited the thread title.
In order to edit a title, click the "Edit" button of your OP and you'll see the title at the very top, which you're able to edit:
Spoiler: Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Regards
Oswald Boelcke
Senior Moderator
UltimateGamer83 said:
I tried that and twrp still wont stick even after a OTA update flash. I installed ram disk twrp even after the update. What gives?
Click to expand...
Click to collapse
I'm curious....you said you are on Android 10, but then you mentioned above installing an OTA update.....I thought all the currently available OTA updates are only for android 11?
My 10 cents worth. Magisk kills fastboot and adb in MY armor x5 mt6765, in 10_Q, so had no choice but to load boot-debug.img just to 'test'.
Try an android 9 bootloader designed for them 'super' .img's, this is the only way I could LOAD magisk, only to find what I read here.
Also note, in 10_Q, the gsi ability found in dev options dissapears when magisk is flashed, so I cant flash gsi, never mind use fastboot or adb.
Thank you.
Introduction
This is a guide for updating from Android 12 (rooted) to Android 13, maintaining root and keeping data. I followed this method with success after having a difficult time finding clear instructions. Hopefully it helps someone.
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
Notes
Method uses Pixel Flasher
Updates both slots to Android 13 as suggested by V0latyle
One caveat with flashing patched boot.img directly (this method) is that you won't be able to revert back to take OTA updates.
To work around this, you could either follow this tutorial or boot the patched boot.img first and do a direct install in the Magisk app.
These two methods would replace the method that this post covers.
Process
Make sure you have the most up to date version of Pixel Flasher, Platform Tools, and Google USB Driver
Download factory image of Android 13
Flash using Pixel Flasher following these steps and screenshot (see corresponding numbers in screenshot)
Browse to your platform tools folder
Reload adb connected devices
Select your device from dropdown
Browse to Android 13 factory image zip file
Click to process factory image (gets boot file from image)
Select factory boot image
Patch factory boot image
Select patched boot image
Select keep data
Select flash to both spots
Push 'flash pixel phone' button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wait for process to complete. it will take some time since it has to flash both slots. your phone will reboot to Android 13 as normal once it’s complete
Enjoy A13
Troubleshooting
Only issue I ran into was Pixel Flasher couldn't detect my device when in bootloader-fastboot mode. ADB commands were registering fine.
To fix this,
Plugged in my phone
Booted to the bootloader screen
Opened device manager in windows 10
Updated the driver for the android device/pixel 6a/unknown device using the latest google usb driver
Future OTA Updates
To take future OTAs without an original boot.img, you can either follow this tutorial to force the original boot.img into the system and take the OTA directly, or this tutorial to sideload a downloaded OTA and re-apply root with Magisk.
Thanks
topjohnwu for Magisk
badabing2003 for Pixel Flasher
psychedel!k for help with OTA update info
Thank you for the tutorial!
I have a doubt... Currently I'm already on A13 with root but I'm not very clear about the steps to follow when the next update comes out and I want to flash it already with root through pixel flasher...
- Should I follow these same steps except check that I update both slots?
- Should I check both "disable" boxes? (What are these two options for?)
- After selecting the rom and hitting "Patch" I would install the new rom with magisk and I would not lose the modules or anything like that?
Thank you again!
dannyzamora said:
- Should I follow these same steps except check that I update both slots?
Click to expand...
Click to collapse
I don't believe you need to update both slots if you've already done that when moving to Android 13. If you didn't, it would probably be good to update both slots like i show in my screenshot
dannyzamora said:
- Should I check both "disable" boxes? (What are these two options for?)
Click to expand...
Click to collapse
i would recommend reading about these two. i'm not an expert and can't provide much info without doing research myself. I chose to go with the defaults and recommendations i saw while researching the process.
dannyzamora said:
- After selecting the rom and hitting "Patch" I would install the new rom with magisk and I would not lose the modules or anything like that?
Thank you again!
Click to expand...
Click to collapse
after you click the patch button, Pixel Flasher will do the installation. you don't need to install the factory image with magisk afterward. all magisk modules should persist through the update.
happy to help the best i can.
Excellent write-up. One caveat with flashing patched boot.img directly is that you won't be able to revert back to take OTA. To work around you could either follow this tutorial or boot the patched boot.img first and do a direct install in the Magisk app
psychedel!k said:
Excellent write-up. One caveat with flashing patched boot.img directly is that you won't be able to revert back to take OTA. To work around you could either follow this tutorial or boot the patched boot.img first and do a direct install in the Magisk app
Click to expand...
Click to collapse
Ahh, i see. Thank you for sharing this. I will update my post to include this information, but to be sure i fully understand first, the work around you mention would need to be done instead of doing the process i outline, correct?
For myself who followed the process I shared, what are my options for updating once an new OTA becomes available?
R.Suave said:
Ahh, i see. Thank you for sharing this. I will update my post to include this information, but to be sure i fully understand first, the work around you mention would need to be done instead of doing the process i outline, correct?
For myself who followed the process I shared, what are my options for updating once an new OTA becomes available?
Click to expand...
Click to collapse
correct and to take OTAs without an original boot.img you could either follow this tutorial to force the original boot.img into the system and take the OTA directly, or this tutorial to sideload a downloaded OTA and re-apply root
just wanted to say thank you for this guide and detailed instructions. amazing!!
Questions
1. When I try to run APT 34 it says it won't work, so I have to use 33?
2. I have the roms in a folder but it will not find any images.
3. Do I need to reboot to bootloader and use magisk? It's greyed out.
I attempted to root my Pixel 4a with Android 12 using Magisk. While executing commands, I received an error stating the partition was not found. I dont have the latest version of Andriod. My phone debugger mode is checked.
XZNZI said:
I attempted to root my Pixel 4a with Android 12 using Magisk. While executing commands, I received an error stating the partition was not found. I dont have the latest version of Andriod. My phone debugger mode is checked.
Click to expand...
Click to collapse
Not a lot to go on from you description,, So is this what's been done? Bootloader unlocked, oem unlocking toggled, magisk installed,,, magisk patched boot.img available and the adb command sent "fastboot flash boot patchedboot.img" ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
What version of ADB Platform Tools are you using?
Are you absolutely sure you're using the right firmware?
Why did you downgrade?
Are you following one of the several guides? If not, you should be.
XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
Maybe some of the steps on this page might help you:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
EngineerMind said:
Maybe some of the steps on this page might help you:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
Click to expand...
Click to collapse
That guide is very out of date.
V0latyle said:
That guide is very out of date.
Click to expand...
Click to collapse
It is, but since he mentioned Android 10, some of it might help him with his issue because it relates to Andorid 10
XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
You could make sure your platform tools are upto date from here https://developer.android.com/studio/releases/platform-tools then try again, you could also try Pixel Flasher, it works great, slight learning curve but all in all pretty easy,
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
hammered58 said:
You could make sure your platform tools are upto date from here https://developer.android.com/studio/releases/platform-tools then try again, you could also try Pixel Flasher, it works great, slight learning curve but all in all pretty easy,
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
Click to expand...
Click to collapse
I download a mini version of the andriod tools and rooted my phone. I attempted to flash TWRP 3.5 for Android 10 for Pixel which failed. Error: Not allowed to flash to recovery. Debugging on Unlocked and rooted..
Hi all new here glad to be a member
anyway i just unlocked the bootloader and rooted with magisk through BOOT.img patching.... my Question is, are there any custom roms or anything out yet for this phone? Android 12 .thank you so much
Thats amazing. From my own research i understand this phone is so new that people have yet the get their hands on it to work on it also the fact that it uses a mediatek instead of a snapdragon is a sticking point for a lot of developers even though its basically the same phone as the g power 22 and g play 21
Hi sam9566
Yeah I broke my other phone cheap . So I looked for an unlocked carrier phone close to me and Walmart had like 7 maybe. But they were in lockup couldn't find it. So I asked the guy in the back he looked around and took his key out and went into this metal cage that you couldn't see into and pulled one out and sold it to me really quickly . Then I had to wait 9 days for the OEM UNLOCK to be UN-greyed in dev options. But in those 9 days I waited for an email from moto for my unlock code but never showed. So I got on live site chat and within 2 minutes the person gave me the 20 digit code . And after 9 days I unlocked the bootloader, then I used the Lenovo software to get the factory Rom extracted the boot.img used magisk to patch then flashed.. lol been debloating the crap out this phone.. it uses 51% storage after setup is completed
nice lets try to actually keep this thread alive so maybe we can get a lineage rom for this phone eventually???
well got rid of all the preinstalled apps and moto junk lol got down to 39% storage used. now what lol im bored
Yeah im still completely lost on how you did this could you possibly post a step by step guide???
lol ill try
1: download https://www.motorola.com/us/rescue-and-smart-assistant/p MOTOROLA SITE please be patient the program is slow just a warning if anyone thinks its hung..
2: Download magisk from GITHUB on your phone and install it.
3: download ADB_Fastboot
4: open rescue and smart assistant program and do the steps it says to do, then once it finds the ROM it MIGHT say already have latest... Say download anyway..
5: now once its done downloading dont do anything else. go to the download location and open the file and copy the BOOT.IMG to desktop or where ever you want it..
6: Now copy the BOOT.IMG to your phone's internal storage Download folder.
7:Run magisk and click top install then select and patch a file. locate the boot.img on your phone and patch it.
8: once done copy the patched file back to the PC i put it in ADB FASTBOOT folder. rename it too BOOT.IMG open CMD with admin rights or it wont work.
9: type (adb reboot-bootloader), should reboot into bootloader. now do this command (fastboot devices) make sure it see's the device.. then type ( fastboot flash boot boot.img ) -BOOT.IMG is what ever name you make it but for simple measures i did boot.img. let it finish reboot device with ( fastboot reboot ).. now open magisk and let it finish what its got to do...
10: ENJOY hope this helps someone out.. i never wrote a guide before as you can tell hahaha.. let me know if there is any QUESTIONS
Gonna have to dig out my windows pc ugh
lol what device do you have?
sam9566 said:
Gonna have to dig out my windows pc ugh
Click to expand...
Click to collapse
My main rig is a mac running os 10.15 so idk if ill be able to run your tutorial step my step i do have adb tools installed but the paths etc are different because of the operating system
sam9566 said:
My main rig is a mac running os 10.15 so idk if ill be able to run your tutorial step my step i do have adb tools installed but the paths etc are different because of the operating system
Click to expand...
Click to collapse
my bad i meant your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
samtron6 said:
my bad i meant your phone.
Click to expand...
Click to collapse
So what do i do next on my pc in still lost
sam9566 said:
So what do i do next on my pc in still lost
Click to expand...
Click to collapse
do you have bootloader in dev option enabled?
Yes
samtron6 said:
well got rid of all the preinstalled apps and moto junk lol got down to 39% storage used. now what lol im bored
Click to expand...
Click to collapse
Same here. Unloaded all the "Junk",and this little pistol is much faster-- however, still looking for a custom ROM.
dcluvsme said:
Same here. Unloaded all the "Junk",and this little pistol is much faster-- however, still looking for a custom ROM.
Click to expand...
Click to collapse
same.
I was struggling to get my boot partition to flash (not found error). Ultimately I had to flash boot_a and boot_b as described here.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
hmm i didnt have to flash the boot a or boot b.. i just did the flashboot boot.img command. maybe i didnt do something right lol now im going to try this when i get time today.. thanks
Yes, you must flash boot_a and boot_b