Question Motorola Edge (2021) - Motorola Edge (2021)

Hello, Can any smart person because I'm slow lol help me get the Recovery or the Boot.img for a Motorola Edge 2021, My version is 12 (S1RMS32.48-18-11-2-3). Thanks

You can download a factory image straight from Motorola themselves, using the Lenovo "Rescue and Smart Assistant" (Lenovo RSA).
I personally used this excellent guide from another user right on this very form, that also mentions grabbing the image(s).
Root Edge 2021 with Magisk
I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted. Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled. You should have...
forum.xda-developers.com

ruq said:
You can download a factory image straight from Motorola themselves, using the Lenovo "Rescue and Smart Assistant" (Lenovo RSA).
I personally used this excellent guide from another user right on this very form, that also mentions grabbing the image(s).
Root Edge 2021 with Magisk
I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted. Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled. You should have...
forum.xda-developers.com
Click to expand...
Click to collapse
I understand that yes but my problem is that I don't have a laptop or PC to run the program so I'm trying to find another way to get the firmware for my Edge 2021, And if I can't do that is there any custom ROM compatible with this device that I could use to patch it with magisk?

So far I have not seen any custom ROMs supporting this device (I think it should come eventually; the last gen has support).
This post includes a download link for an up to date Android 11 ROM. I haven't used it yet though. I'm a little nervous about downloading ROMs from random links, but since I used the guide from the same user (last post you replied to), it feels trustworthy. But use at your own risk.
Edge 2021 (unlocked) special flashing guide
You can manually update to latest Android 11 (April patch) Bootloader unlock may be required. Download the ROM...
forum.xda-developers.com

oh forgive me for forgetting to mention this...
but I'm 99% sure you REQUIRE a PC to flash images onto a phone, since you use the adb debug tool to manipulate the phone while it's in fastboot mode.

ruq said:
oh forgive me for forgetting to mention this...
but I'm 99% sure you REQUIRE a PC to flash images onto a phone, since you use the adb debug tool to manipulate the phone while it's in fastboot mode.
Click to expand...
Click to collapse
I already solved that problem I use another phone to flash the images

ruq said:
So far I have not seen any custom ROMs supporting this device (I think it should come eventually; the last gen has support).
This post includes a download link for an up to date Android 11 ROM. I haven't used it yet though. I'm a little nervous about downloading ROMs from random links, but since I used the guide from the same user (last post you replied to), it feels trustworthy. But use at your own risk.
Edge 2021 (unlocked) special flashing guide
You can manually update to latest Android 11 (April patch) Bootloader unlock may be required. Download the ROM...
forum.xda-developers.com
Click to expand...
Click to collapse
My firmware is android 12 so would it be alright if I install this android 11 image?

Imparel said:
My firmware is android 12 so would it be alright if I install this android 11 image?
Click to expand...
Click to collapse
An android DOWNGRADE might cause issues...

ruq said:
An android DOWNGRADE might cause issues...
Click to expand...
Click to collapse
Okay I understand, I'll just take my chances and hopefully I don't brick my device...

ruq said:
An android DOWNGRADE might cause issues...
Click to expand...
Click to collapse
I did try it but instead of fully flashing the img I just did fastboot boot so that it would only boot into it one time and it didn't work at all so my only chance of rooting my device is using a PC to get the firmware of my phone, And thanks for the help.

Related

Inquiry about OPPO R7plusf update!

Hi guys,
I hope all of you are fine, now after more than one year of usage of OPPO R7Plusf which was really amazing, it seems like OPPO has no plans to upgrade our phones, when I purchased my device a ColorOS version 2.0 was installed already and recently, it was upgraded to ColorOS version 2.1.0i (based on 5.1.1 Android Lollipop). Nowadays, all of us heard about the Nougat upgrade when we still dreaming with Marshmallow!!
So please, any suggestions for a custom ROM (tested) to upgrade my OPPO phone to Nougat version with no usual known errors or bugs. I will be grateful.
Notice: I contacted both customer support (the local one and the international) and I received the usual formal disappointed answer: "we will inform you when the update is available", which I think it will not be.
So thanks
Anybody here!?
Depends what you like
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Meroslave said:
Anybody here!?
Click to expand...
Click to collapse
Lol, yeah. There is not much traffic here, but the R7Plusf is still awesome and up to date. Mainly due to good people at LineageOS keeping the device fresh.
I don't have serious issues with AICP on Nougat. No reboots. It is build "on top of" LineageOS, but have more features plus a working theming system. Latest build uploaded today.
Try RR, AICP and LineageOS and see what you like. Wait with Lineage untill the next release (current is Feb 14), if you want to avoid reboots.
ccrocks426 said:
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Click to expand...
Click to collapse
So, you recommend the CM13 in case it's available?
And what's the cons and pros?
teemo said:
Lol, yeah. There is not much traffic here, but the R7Plusf is still awesome and up to date. Mainly due to good people at LineageOS keeping the device fresh.
I don't have serious issues with AICP on Nougat. No reboots. It is build "on top of" LineageOS, but have more features plus a working theming system. Latest build uploaded today.
Try RR, AICP and LineageOS and see what you like. Wait with Lineage untill the next release (current is Feb 14), if you want to avoid reboots.
Click to expand...
Click to collapse
Sure I will try one of your recommendations, but all I was afraid of was the disappointed bugs after updat such as battery drain, camera errors, wifi issues ... etc. Of course my ColorOS became boring to me, but still stable with no errors
Any pros or cons for those above I will be great full
Meroslave said:
Sure I will try one of your recommendations, but all I was afraid of was the disappointed bugs after updat such as battery drain, camera errors, wifi issues ... etc. Of course my ColorOS became boring to me, but still stable with no errors
Any pros or cons for those above I will be great full
Click to expand...
Click to collapse
Battery drain on MM has improved compared to Lollipop and N has improved over MM. With 4 email accounts running (on Aqua Mail) and Location on "High accuracy", Viber messenger and other stuff running, I had not much drain on AICP 11 (MM). Drain during night with Location on "Device" was 0.5% per hour. On MM and especially N, you have many ways in settings you can fine tune battery drain. Many apps are automatically shut down when not in use. You can decide which to limit and which to keep running when phone is off. Without extra apps (as ColorOS has), you can limit what apps are allowed to do and see. All built into the system.
A final word on drain: With Googles and others services running all the time, tracking everything you do, some drain is expected. Luckily this can be turned off by you
The number one reason to upgrade in these hacker friendly times: N is updated with much improved security. Updated every month with the latest security patches.
For me, AICP 11 is error free. The latest MM builds are complete in features and practically error free. Features are still being merged one at the time on N, but is useable as is now with only some minor issues.
I have not tried RR. My guess is that it has more features than AICP, but also more issues.
Lineage is the mother of all, I expect it to be stable with a good set of features.
All the N builds have more or less issues with speaker-phone. It may or may not bother you (or the person in the other end). MM was not affected as much as N, for some unknown reason.
I use Resurrection Rom and very happy with this rom!
i am beginer
i have oppo r7 plus f. tried the auto root tool but ended up hard bricking my phone. i am a beginer and i do not have much knowledge .
want to install lineage os on my oppo r7 plus f please tell me some easy ways.
Meroslave said:
Hi guys,
I hope all of you are fine, now after more than one year of usage of OPPO R7Plusf which was really amazing, it seems like OPPO has no plans to upgrade our phones, when I purchased my device a ColorOS version 2.0 was installed already and recently, it was upgraded to ColorOS version 2.1.0i (based on 5.1.1 Android Lollipop). Nowadays, all of us heard about the Nougat upgrade when we still dreaming with Marshmallow!!
So please, any suggestions for a custom ROM (tested) to upgrade my OPPO phone to Nougat version with no usual known errors or bugs. I will be grateful.
Notice: I contacted both customer support (the local one and the international) and I received the usual formal disappointed answer: "we will inform you when the update is available", which I think it will not be.
So thanks
Click to expand...
Click to collapse
supriyo_rana said:
i have oppo r7 plus f. tried the auto root tool but ended up hard bricking my phone. i am a beginer and i do not have much knowledge .
want to install lineage os on my oppo r7 plus f please tell me some easy ways.
Click to expand...
Click to collapse
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
what to do next?
DooganAU said:
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
Click to expand...
Click to collapse
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
supriyo_rana said:
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
Click to expand...
Click to collapse
i have the same concern also. Can someone please provide a step by step instruction on how to downgrade the firmware to the old version?
supriyo_rana said:
thanks for your reply
yeah i went to the ofiicial service centre for the unbricking , noy it is working fine with letest firmware . now according to you i should downgrade the firmware . but how to do it ? should i do it via oppo stock recovery? or via the local update option of system updater in the menu?
Click to expand...
Click to collapse
bu11et said:
i have the same concern also. Can someone please provide a step by step instruction on how to downgrade the firmware to the old version?
Click to expand...
Click to collapse
Try here: https://forum.xda-developers.com/showpost.php?p=73786100&postcount=139
unlock bootloader still stuck..
Hi Guys..
First i don't know if i am posting this in right thread or not... but I need help... after lots of search i couldn't find anything to unlock my oppo R7 plus running r7plusEx_11_160922 on color os 2.1.o1 android 5.1.1.. As per my study the first thing I need to do it unlock bootloader, then do TWRP, then install any custom rom. (Please correct me if m wrong). Now please tell me how can i unlock my bootloader when I dont have access to fastboot by pressing power and Volume + key. Is there some other way. I have also tried the adb version 1.4.3 to get to the fastboot mode but it restarts my mobile to lock screen.
x_master1987 said:
Hi Guys..
First i don't know if i am posting this in right thread or not... but I need help... after lots of search i couldn't find anything to unlock my oppo R7 plus running r7plusEx_11_160922 on color os 2.1.o1 android 5.1.1.. As per my study the first thing I need to do it unlock bootloader, then do TWRP, then install any custom rom. (Please correct me if m wrong). Now please tell me how can i unlock my bootloader when I dont have access to fastboot by pressing power and Volume + key. Is there some other way. I have also tried the adb version 1.4.3 to get to the fastboot mode but it restarts my mobile to lock screen.
Click to expand...
Click to collapse
Download this rom https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0. Place it in your internal drive and flash it. It will install the ColorOS with an unlockable bootloader.
Even I'm facing the same issue. There are no such methods available on internet. I have ended bricking phone several times. Because since the last update oppo had limited tho access to bootloader. And the phone OPPO r7 plus f is quite old now so there's no people dealing with the issue. The only methods remain is to downgrade the firmware and repay the process again. Better look for some firmware version around mid 2015-2016early. I read somewhere that has access to bootloader. I haven't tried it personally but I hope the methods will work. Please let me know whatever the result is..
need your help badly
ccrocks426 said:
I currently use Resurrection remix on mine however there are some issues with apps force closing is my main one. Lineage OS also had issues for me with bluetooth causing the phone the reboot over and over. CM 13 was the best but I can't find any download links for it any more (rip CM) I think they both have updates coming outside but I recommend trying some out and then making a decision. Also if your phone is on one of the latest oppo updates (one of the 2016 updates) you'll have to downgrade to a 2015 software as they locked the bootloader so you won't be able to root! It's easy to do just find an old firmware from the internet (I would post links but I can't, also has to be a 2015 one) turn off the phone and turn it back on whilst holding down the volume down button and then go install and install the old firmware and then follow any guides on the internet for installing custom ROMs
Hope this helped
Click to expand...
Click to collapse
please pm me your email . i have an oppo r7 plus f (the international version ) and i do not have much knowledge about the rooting and installing custom recovery. and since oppo has closed the bootloader now please tell me which rom to download for downgrading( if possible please provide the link) and then how to flash the custom roms and which rom is best for oppo r7 plus? which one are you using?
DooganAU said:
Rana, first I'm sure you have been a good phone user and your Oppo R7 plus is upto date, unfortunately this is a problem. So first thing you need to do (Assuming you have unbricked your phone) is find a older version of the genuine R7+ firmware. Preferably some time between 2015- mid2016. The reason for this is OPPO locked the bootloader on later versions, these earlier versions are what the autoroot tool was designed to work on. Once you have this firmware, flash through recovery (provided you still have genuine OPPO recovery), if not you also need to flash this. Once you have the older firmware on your phone you should be able to proceed as usual steps to install lineage on your phone using typical walkthroughs.
Click to expand...
Click to collapse
Where can i find the 2015 firmware for oppo r7 plus f
Just check the link in my post above.
kishd said:
Just check the link in my post above.
Click to expand...
Click to collapse
Don't know why but the link is not working

KG state prenormal after 7 days no reboots

I have an SM-A530F and had no issues flashing roms and TWRP. I eventually tried Saboor OneUI from and my phone got completely encrypted and would only allow official binaries to be flashed. I flashed Binary 7 (Pie) to my device and tried to flash TWRP but had come across the error and after researching realised I'd have to wait 7 days with the phone continuously booted up. I have waited 7 days with nothing changed. I'm now on my 25th day and still have a prenormal KG state. But in developer options my OEM states that it is already unlocked and I can switch the toggle. I cannot flash TWRP or magisk though.
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash
Click to expand...
Click to collapse
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Zefpoes23 said:
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Click to expand...
Click to collapse
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
Click to expand...
Click to collapse
youdoofus said:
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
Click to expand...
Click to collapse
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Zefpoes23 said:
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Click to expand...
Click to collapse
youre not going to get the phone to think that TWRP is official. If that was possible, we would all have root and without so much as unlocking the bootloader for that matter
manifesto- posted on another thread-sorry for the dupe
A bit of history gives a bit more depth/ Just when you thought it was okay to go back in the water. I'm Canadian you can probably tell by my accent. My journey with phones has always been Samsung simply due to availability s6 s7 s8 s8+ most recently the a530w.
In order for you to understand my joy finding the A8 and my horror is that the S8 series. in North America S8 uses a Qualcomm Snapdragon chip. g950u is SD g950f is the rest of the world (exnyos) This is probably due to some kind of World Trade Organization antitrust treaty {although qualcom makes great chips} or whatnot I don't care.
i do care about is their bootloader lock policy (g950u and up) so it is impossible to unlock an encrypted Snapdragon bootloader. When I ran into the a530w exnyos, I was like a three-year-old at Christmas now you have to understand I'm not a coder I'm more of a mason I'm familiar with bricks. I'm sure we've all watch the AP file upload and Odin like we watch paint dry. So when I first got the a530w pi version April patch I was able to TWRP install I believe at the time was Pixel project or something else added magisk, xposed you get the idea.
Eventually a file got corrupt (much like @Zefpoes23) and I had to common sense restock it. I think my mistake what is going with the most current pie version (hadn't read this thread yet from @corsicanu) which is binary 7 knowing what I know now I would have probably had the ability to go a binary 4 or so. I haven't done the 7 day challenge simply not to waste my sanity. my bootloader unlock never vanished, it like it's a light switch with no bulb. I've tried to backdated front dated. I refuse to wait 7 days to find out that I'm still at the same place. . The problem is all the fixes are zip files which you need TWRP to flash. I agree, it's not @BlackMesa123 version. it's the prenormal. No I'm certainly not a developer and some of them are mobile gods. My questions maybe Elementary logical. Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort. think we're all about to become in the same boat. we could start a movement lie "#meprenormal2" In Time will tell. As or now "prenormal" is the new "normal" All I can to the devs: help me odin 3 canmodme. your my only hope
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
jthibault27 said:
Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort.
Click to expand...
Click to collapse
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
jthibault27 said:
I refuse to wait 7 days to find out that I'm still at the same place.
Click to expand...
Click to collapse
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
jthibault27 said:
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
Click to expand...
Click to collapse
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
@mchlbenner if you have a moment, could you lend a hand?
Youdoofus said:
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
Click to expand...
Click to collapse
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
jthibault27 said:
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
Click to expand...
Click to collapse
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
mchlbenner said:
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
Click to expand...
Click to collapse
there you are!! so, the A8 is now not rootable?
Youdoofus said:
there you are!! so, the A8 is now not rootable?
Click to expand...
Click to collapse
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
jthibault27 said:
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
Click to expand...
Click to collapse
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
mchlbenner said:
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
Click to expand...
Click to collapse
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Youdoofus said:
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Click to expand...
Click to collapse
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
jthibault27 said:
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
Click to expand...
Click to collapse
yes, from what ive gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before i got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Youdoofus said:
yes, from what I've gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before I got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Click to expand...
Click to collapse
If you ever come across a forum specific to this issue ({completely extrapolating the date by guess} July 1, 2019 9.0) but not necessarily specific to the A8, please share. as it stands now, my findings indicate isolated conversations in different forums on various models, sharing the same problem. We must unite! lol. truth be told, it's challenging searching for such a specific problem relating to a patch on many models.

Motog8 plus root

Does anyone know how to root? Till yet ?
Today IT was my Christmas.present
Thanks
Daniel
No source from motorola, nor updates yet.
Hello you can root your moto with magisk.
Mounib BOULAABI said:
Hello you can root your moto with magisk.
Click to expand...
Click to collapse
If you have a copy of the boot.img
Sent from my mata using XDA Labs
Thanks by the way. I found i way to root my Device.
Please do tell, how?
Danieldergrosse said:
Thanks by the way. I found i way to root my Device.
Click to expand...
Click to collapse
Would you mind sharing your way to root your device? Every piece of knowledge can help other users here on XDA.
Sent from my Moto G5 Plus using XDA Labs
http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method
Danieldergrosse said:
http://androidbiits.com/root-motorola-moto-g8-plus-xt2019-2-xt2019-1-easily/
This method
Click to expand...
Click to collapse
*
your link seems dead or not correct. - edit: link correct, was not working due to my vpn...
I assume he patched a G8+ boot.img with magisk manager.
boot image can be extracted from official Doha firmware found here: https://mirrors.lolinet.com/firmware/moto/doha/official/
manual on how to do this can be found on official magisk manager website.
be aware that when unlocking bootloader your phone will reset to factory settings.
This is what I did. Yes..
Worked great for my G8+. I guess people should just check which stock ROM file they get from lolinet to make sure it's the right one. I say that because, in my case, lolinet list had two files for the Brazilian stock ROM. I went to Settings / About / Version number and downloaded the matching file. Don't know whether the other file would work the same or not. Just didn't want to risk having any issue since G8+ is somewhat new and there's not much info on solving root problems on the Internet.
Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl
carl.13 said:
Hi,
Couple of questions
Does the Bootloader have to be Unlocked to flash the modified Boot image?
Or can I use update option?
Are Motorola releasing unlock numbers for Bootloader now?
Thanks, Carl
Click to expand...
Click to collapse
Hello, Carl. I guess it's not possible unless there's a flaw in the security. There are some articles on the Internet about that. Google "is-there-a-way-to-root-an-android-phone-without-unlocking-the-bootloader". I can't post URLs yet.
As for Motorola devices, I was able to unlock the bootloader without problems on my G8+, last week. The only caveat, I'm my case, is that I had to wait some days for the unlock bootloader option be available under developer options. It was disabled by default in my G8+. And, yes, they're releasing bootloader unlocking codes.
THANKS!
Have anybody with a rooted device tried to get wide angle camera working in gcam ports?
Thanks.
successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google
esrd43 said:
successfully rooted my Moto G8 Plus using the info in this thread
but for some reason I can't delete bloatware, even by deleting apps from root browsers or trying few solution I found on google
Click to expand...
Click to collapse
magisk module debloater and also sdmaid helped with most of the bloatware, the only thing I could not remove was google files but I just deactivated it.
a really weird thing happened with the April 1st update, basically the update started automatically and it failed at 3/6 so I tought I should restart my phone and test it again, but it got stuck in bootloop and I had to reflash a rom with fastboot cmd.
I think that's because I unlocked the bootloader and rooted my phone, cause u lose the right for updates after you do that, but for some reason lenovo/moto update system goes automatically the next second u connect to the internet and fails halfway thru so u have a higher chance to ruin your phone or something, instead of denying the update from the start
so the solution I found was to try and delete "moto update service" app that I can't force stop or disable but I couldnt find it in system/app or system/priv-app, that's because the app name is "3c_ota", so deleting that with SD Maid app worked and the "update system" option in settings is reverted to a sort of default android one that lets you check manually.
Had a similiar issue. I soft bricked my phone (bootloop) and installed a stock rom from an unofficial source. The funny thing is, this version did make like 3 or 4 system upgrades to PPSI.29.65-51 without any issue. But the 1st April updated failed to install. I then flashed the official 1st april stock image with the moto rescue and smart assistant. After that, the official ROM tells me my phone is not allowed to do updates because the security of this phone is compromised and I should contact lenovo support
Those upates are kinda annoying if they don't work, I guess I'll just completey flash the phone every 6-12 months with the moto assistant.
yeah you should always have a backup rom that you can download with moto assistant or from lolinet g8 roms (https://mirrors.lolinet.com/firmware/moto/doha/official/)
I also got the same message saying that my phone is compromised ( unlocked bootloader + rooted) and it won't receive any further updates, but I just deleted the "3c_ota" app (the moto update service) which is bad cause if forces automatic updates the second u connect to internet.
I'm not going to touch any further updates or security patches until android 10, which I will attempt to flash via moto assistant

Question T-mobile oneplus 9 (LE2117) has an unlocked bootloader now?

Hello all, after lurking here for a while, I found something that's making me post.
I have a carrier locked OP9. I just received the update to Android 12, and it has broken critical features. (Particularly not being able to stop apps from being closed accidentally!)
I have looked at Lineage OS in the past, and the process to get the LE2117's bootloader unlocked was... complicated.
However, while trying to fix other problems, rooting around in the developer options, I noticed that "unlock bootloader" was actually toggleable!
I think I have an unlocked bootloader now, but it's on android 12, and all the guides for rooting and installing a custom MOD for this phone say you must revert to android 11 before anything else.
So what now? Am I waiting for lineageOS 19 to come out, because that's the one based on android 12? I'm new to custom roms, and don't get the coding side of how all this works. (But I'm pretty determined to figure this out.)
Thanks for any help or advice you've got!
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
dark_sable said:
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
Click to expand...
Click to collapse
I am pretty sure there is root for 12. All you need to do is dump the payload from the 12 update OnePlus let's loose, and patch it with magisk and flash it via fastboot. Via bootloader it is easy I am using a TMobile OnePlus 9. All you need to do is revert back to 11 via a msm tool. There is a post here for that. After downgrading to unlock your bootloader is easy only takes time. There is a post for it I don't remember all the details but all you have to do is get you imei code and email OnePlus. Soon they will sent you a code to fastboot flash to unlock the bootloader. After that most of these 12 work for us on our model phone. I am using evolution x. It tells me every day I can go to 12 .
funkybear34 said:
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Click to expand...
Click to collapse
Yes yes they do.
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
JimmyL216 said:
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
Click to expand...
Click to collapse
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
EtherealRemnant said:
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
Click to expand...
Click to collapse
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
JimmyL216 said:
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
Click to expand...
Click to collapse
What worked for me was shutting the phone off, removing my case, holding both volume up and down, then plugging the phone in. The screen won't show anything, you have to look at the MSM Tool and see that it's connected to know you did it right. Both times I tried it worked perfectly.
You can also use adb reboot edl if you can get the thing to boot and have USB debugging turned on.

HELP ROOT MOTO ONE 5g ACE (XT2113-2) Android 10 from T-Mobile

Hello: I'm using the guide clintongsan made to root a usa moto one 5g ace android 10 purchased in april 2022 from a T-mobile store here in the south on the east side of the mississippi river.
My build number is QZKS30.Q4-40-95-9 The last build number on this link
( https://mirrors.lolinet.com/firmware/moto/kiev/official/TMO/ ) is QZKS30.Q4-40-95-6 with a
date of 02/11/2022. Will that work for me since I have 95-9 and that one is 95-6 There is a grayed out statement that there are 68 more subfolders but I don't know how to access it to see if my build is there. Also on the Motorola website for unlocking the bootloader, Get your device ID, there are examples for compacting the lines of code into a long string. The examples are for Windows and Mac. I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
vansteering said:
Hello: I'm using the guide clintongsan made to root a usa moto one 5g ace android 10 purchased in april 2022 from a T-mobile store here in the south on the east side of the mississippi river.
My build number is QZKS30.Q4-40-95-9 The last build number on this link
( https://mirrors.lolinet.com/firmware/moto/kiev/official/TMO/ ) is QZKS30.Q4-40-95-6 with a
date of 02/11/2022. Will that work for me since I have 95-9 and that one is 95-6 There is a grayed out statement that there are 68 more subfolders but I don't know how to access it to see if my build is there. Also on the Motorola website for unlocking the bootloader, Get your device ID, there are examples for compacting the lines of code into a long string. The examples are for Windows and Mac. I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
Click to expand...
Click to collapse
Honestly I've been trying to figure out the best way to go about this as well. My fiance is interested in having her phone rooted. I'm just trying to figure a well to where i can just access the boot image off the phone somehow so i can patch it using magisk. well obviously backing up the original image first, but i've heard twrp doesn't work and i tried using QFIL to see if i can access it but i don't think it has EDL. If you figured out a way to do it without flashing a older update to the phone. Please let me know. I'll do the same after I look into it a bit more. I feel like i'm just over complicating somehow lol I have a tendency of doing that.
vansteering said:
Hello: I'm using the guide clintongsan made to root a usa moto one 5g ace android 10 purchased in april 2022 from a T-mobile store here in the south on the east side of the mississippi river.
My build number is QZKS30.Q4-40-95-9 The last build number on this link
( https://mirrors.lolinet.com/firmware/moto/kiev/official/TMO/ ) is QZKS30.Q4-40-95-6 with a
date of 02/11/2022. Will that work for me since I have 95-9 and that one is 95-6 There is a grayed out statement that there are 68 more subfolders but I don't know how to access it to see if my build is there. Also on the Motorola website for unlocking the bootloader, Get your device ID, there are examples for compacting the lines of code into a long string. The examples are for Windows and Mac. I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
Click to expand...
Click to collapse
Just tried this and had no issues at all, Hope this helps
[RECOVERY][UNOFFICIAL] TWRP 3.5.2_10 for Moto G 5G (kiev)
DISCLAIMER: I'm not responsible if you brick or damage your phone in any way by using this recovery. It is always advisable to fully backup your phone before playing around with recoveries, custom roms and similar stuff. What has been tested and...
forum.xda-developers.com
InvisibleAOD said:
Just tried this and had no issues at all, Hope this helps
Click to expand...
Click to collapse
On Build number 95-9? Or a previous version? I'm asking because I couldn't even get the bootloader unlocked on a 95-9 phone (unlock "failed" after getting the code from Moto). I'm still trying to get an answer as to whether if the newest OTA is a problem.
vansteering said:
. . . I'm using a Linux laptop and no example exists. The Moto site gives a link to download SDK tools. Is there a site where I can download the minimum tools required? Probably more questions to follow for sure. Thank you
Click to expand...
Click to collapse
Is this what you're asking for?
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
As for 40-95-9 firmware, a sure way to get that firmware is Moto/Lenovo's "Rescue and Smart Assistant", aka "LMSA" (search, should be easy to find). Use the Rescue option and stop (EDIT/ADD: let the download finish), go to the folder where it was downloaded (make sure to get the download link shown in the utility) and find the firmware in the ".../ROMfiles" subfolder I think it is. That's the full firmware including boot.img. I used that subfolder to reflash the entire 95-9 firmware. EDIT/ADD: But this assumes Rescue and Smart Assistant on Windows, NOT Linux. I don't know if there is a Linux version for that, sorry. {--Or do you have a Windows emulator in your Linux that might solve this particular issue?--)
I DO NOT KNOW -- yet -- if 95-9 is rootable or even unlockable. Unlock failed for me on a 95-9 phone . . . although I did get an Unlock Code from Moto (on a Windows PC).
So this is a question back at you: HAVE YOU MANAGED TO UNLOCK THE BOOTLOADER on your 95-9 phone?
Moondroid said:
On Build number 95-9? Or a previous version? I'm asking because I couldn't even get the bootloader unlocked on a 95-9 phone (unlock "failed" after getting the code from Moto). I'm still trying to get an answer as to whether if the newest OTA is a problem.
Click to expand...
Click to collapse
Yeah it was on 95-9, just make sure to read through the thread cause I kind of messed up in the process but once you flash twrp and boot into it, flash the kiev file and magisk. I had to keep reading. I flashed to both partition a and b.
InvisibleAOD said:
Yeah it was on 95-9, just make sure to read through the thread cause I kind of messed up in the process . . .
Click to expand...
Click to collapse
I should've been more specific with my question, sorry. . . . Did you actually unlock your bootloader on 95-9, or was it unlocked prior to that OTA and then you ran the root process on 95-9?
@vansteering , I don't mean to hijack your thread.
Moondroid said:
I should've been more specific with my question, sorry. . . . Did you actually unlock your bootloader on 95-9, or was it unlocked prior to that OTA and then you ran the root process on 95-9?
@vansteering , I don't mean to hijack your thread.
Click to expand...
Click to collapse
Unlocked on 95-9
been away for awhile. Thanx Moondroid, and Invisible AOD, & everyone for all the info. I'll try a few things this weekend.
InvisibleAOD said:
Unlocked on 95-9
Click to expand...
Click to collapse
Moondroid said:
I should've been more specific with my question, sorry. . . . Did you actually unlock your bootloader on 95-9, or was it unlocked prior to that OTA and then you ran the root process on 95-9?
@vansteering , I don't mean to hijack your thread.
Click to expand...
Click to collapse
no hijacking here, just much needed info. More is better.

Categories

Resources