Related
*removed*
use it, install perfectly working on twrp.
this is my new rom daily rom , more fluid than aosp.
all working fine with my module xposed
thank you for your work
pixiebob said:
use it, install perfectly working on twrp.
this is my new rom daily rom , more fluid than aosp.
all working fine with my module xposed
thank you for your work
Click to expand...
Click to collapse
Do you have the US Retail version XT1527?
I'm interested to know whether this works on other moto e lte variants.
I updated the fxz to exclude the bootloader to prevent any potential bricks; so anyone with an unlocked bootloader can flash this and still be able to flash back to any 5.0.2 build without any issues.
Just be sure to have the fxz for your device standing by before trying.
Also renamed the other files, adding the prefix "surnia" to the title to avoid any potential confusion...
Q9Nap said:
Do you have the US Retail version XT1527?
I'm interested to know whether this works on other moto e lte variants.
Click to expand...
Click to collapse
my version is XT1524, europe retail LTE
Fastboot file now includes only logo, boot, and system.
Radio and bootloader can be installed using separate flashable zips.
It is recommended to flash radio and bootloader only on devices for which they were intended; logo, boot, and system are safe to flash on any unlocked hardware.
best rom is this stock 5.1 so far, more fluide and battery life
i like stock kernel, cpu is more able to stay at low frequencies, phone more able to stay cool.in CM/aosp it's not the case
Sadly, this phone doesn't have much development, but this is what I've been looking for, I think.
What I understand is that this works like any ROM, right? I can have a backup of my current ROM and flash this and if anything goes wrong I restore and that's it? This doesn't mess with the radio, recovery nor bootloader, so it doesn't matter that my phone is a Retla one with CID 12, as the ROM doesn't mess with that. I make several questions as I bricked my last phone by trying to flash 5.1 firmware with the bootloader unlocked, so I want to be careful. After all, if something goes really wrong, I'll always be able to flash stock firmware.
This is the best ROM I've used (XT1527) so far. I had to wipe the data and let google restore most of my apps to stop Gapps crashes, but it was worth it. I didn't install the radio, bootloader, or recovery zips and am having no problems at all. Re-rooting was easy and Xposed and its modules are working well. All the minor problems I had with AOSP are gone. This is my daily driver.
rster said:
This is the best ROM I've used (XT1527) so far. I had to wipe the data and let google restore most of my apps to stop Gapps crashes, but it was worth it. I didn't install the radio, bootloader, or recovery zips and am having no problems at all. Re-rooting was easy and Xposed and its modules are working well. All the minor problems I had with AOSP are gone. This is my daily driver.
Click to expand...
Click to collapse
What's your phone model? What do you mean, when you say you let Google restore your apps?
My phone is the Moto E 2015 LTE Retail US (XT1527). I'm using the google backup/reset in settings and it appears that it backs up non-system apps and restores them on installation if you let it. The associated passwords with the apps, however, had to be re-entered manually. What is restored is:
Google Calendar settings
Wi-Fi networks & passwords
Home screen wallpapers
Gmail settings
Apps installed through Google Play (backed up on the Play Store app)
Display settings (Brightness & Sleep)
Language & Input settings
Date & Time
Third-party app settings & data (varies by app)
Will this work for the xt1511 variant? I have it unlocked, but i'm having trouble getting a custom recovery on it to begin with, and it's not receiving and OTA to 5.1 which is annoying me.
ZeroAlphawolf said:
Will this work for the xt1511 variant? I have it unlocked, but i'm having trouble getting a custom recovery on it to begin with, and it's not receiving and OTA to 5.1 which is annoying me.
Click to expand...
Click to collapse
It's highly unlikely it will work and I wouldn't recommend trying it.
But if you're determined, make sure one of these works first so you can recover if necessary:
http://motofirmware.center/files/category/45-moto-e-2nd-generation/
Then flash only the main fastboot zip from the op which includes logo, boot, and system; do NOT flash bootloader, radio, or recovery zips.
on boost mobile version xt1526. flashed the main file but could not get data to work and the boost mobile file from the motofirmware page fails to install on twrp
Retail Fastboot from Carrier
Hi, I'd like to know if by getting this fastboot, being Retail and overriding what's currently installed (Carrier's) it would allow me to carrier unlocking it? Also; if I get this; would my updates come directly from Motorola instead of having to be approved and released by my carrier?
I do have a XT1527 that came directly from my carrier.
Thanks in advanced.
carlitosoe said:
Hi, I'd like to know if by getting this fastboot, being Retail and overriding what's currently installed (Carrier's) it would allow me to carrier unlocking it? Also; if I get this; would my updates come directly from Motorola instead of having to be approved and released by my carrier?
I do have a XT1527 that came directly from my carrier.
Thanks in advanced.
Click to expand...
Click to collapse
This fastboot requires an unlocked bootloader, and the carrier versions don't have unlockable bootloaders afaik.
Even if you are able to unlock your bootloader, flashing this fastboot will not remove carrier lock if it is present.
Ota is determined by sim, even on the retail version, afaik.
Works well on xt1524 eu.
So far the best voice quality, and the most stable firmware.
Just a heads up, I will be removing the op and the files soon.
Q9Nap said:
This fastboot requires an unlocked bootloader, and the carrier versions don't have unlockable bootloaders afaik.
Even if you are able to unlock your bootloader, flashing this fastboot will not remove carrier lock if it is present.
Ota is determined by sim, even on the retail version, afaik.
Click to expand...
Click to collapse
At&T/Cricket,verizon doesn't allow bootloader to be unlocked, which is really sad and there should be a law passed that prohibits them from doing that. Us consumers that pay good money for these phones should not have to be locked or prevented from doing what we want with them. I don't understand why it hasn't been illegal yet.
The sprint,Boost, and consumer cellular Models should have unlockable bootloaders and the Moto dev site should provide the codes
Hi. Could anyone point me at a working download link for this stock retail rom? OTA for 5.1 isn't yet available in Spain (xt1524) but i can't seem to find any copy of the ROM around XDA or anywhere else...I Know Q9Nap deleted it, but i hope someone uploaded it somewhere else.
Thanks
voland34 said:
Hi. Could anyone point me at a working download link for this stock retail rom? OTA for 5.1 isn't yet available in Spain (xt1524) but i can't seem to find any copy of the ROM around XDA or anywhere else...I Know Q9Nap deleted it, but i hope someone uploaded it somewhere else.
Thanks
Click to expand...
Click to collapse
Here is a working Link
https://mega.nz/#!c1N1AQCY!s9Gt-RDbMiDbxp3Wv7PPIRAbq5gxzd1xAah1aCMtt6w
Hi!
I come from the Galaxy S series (S4, S5, S7) phones and I m considering of buying a Google Pixel 3
I can find many decent options, all of which are carrier unlocked
My concern with the Pixel 3 is whether I ll be able to install Android vanilla (without any carrier-related bloatware)
For all of my Samsung's so far, I could easily pick the retail ROM (well not exactly 'vanilla'!) from sammobile and load it with Odin (without breaking the knox)
Can I do something similar in the Pixel 3 or are there any security mechanisms to prevent me? (I m talking about installing original ROM - not custom..)
Bonus question - does any of you know if the Pixel 3 from Verizon and US Cellular have branding [carrier logo(s)] on the device?
Thank you in advance!
Well, you will certainly avoid the Samsung bloatwear. I have a P3 from Google and got my son's P3 through T-mobile. It did not have any additional T-mobile bloat on it, but I don't know about the big V.
Note10.1Dude said:
Well, you will certainly avoid the Samsung bloatwear. I have a P3 from Google and got my son's P3 through T-mobile. It did not have any additional T-mobile bloat on it, but I don't know about the big V.
Click to expand...
Click to collapse
I can find it via Verizon and US Cellular - hopefully none of which have put logos on it..
I have one more - rather embarassing question: do you have to use a Google account in order to use the Pixel 3? For several other Android phones that I know of - it's optional. You can still skip this step and use the phone without having to tie the phone with Google. But can you do that on the P3?
Any more hints on that and my ROM-related queries would be really helpful! Thanks
jstoner said:
I can find it via Verizon and US Cellular - hopefully none of which have put logos on it..
I have one more - rather embarassing question: do you have to use a Google account in order to use the Pixel 3? For several other Android phones that I know of - it's optional. You can still skip this step and use the phone without having to tie the phone with Google. But can you do that on the P3?
Any more hints on that and my ROM-related queries would be really helpful! Thanks
Click to expand...
Click to collapse
Verizon branded Pixel 3s have locked bootloaders, which prevent rooting or custom ROMs (vanilla AOSP would be a custom ROM). According to the flashing instructions at https://developers.google.com/android/images, you also need to unlock the bootloader to flash a google factory image.
I'm not sure if you can skip the google account. If you really want to avoid google services, my recommendation would be to install LineageOS, with no gapps.
dcarvil said:
Verizon branded Pixel 3s have locked bootloaders, which prevent rooting or custom ROMs (vanilla AOSP would be a custom ROM). According to the flashing instructions at https://developers.google.com/android/images, you also need to unlock the bootloader to flash a google factory image.
I'm not sure if you can skip the google account. If you really want to avoid google services, my recommendation would be to install LineageOS, with no gapps.
Click to expand...
Click to collapse
Hmm...if the 3s has that, then the 3 will also have it :/
But I m confused...would I be able to unlock the bootloader?
I can see from this page: https://developers.google.com/android/images#blueline that 'blueline' is that vanilla AOSP version that corresponds to the P3 (right?)
The G account issue is less important. I just don't like 'syncing' stuff (accounts, photos etc). Worse case scenario, I ll create an empty profile, just for the logon
jstoner said:
Hmm...if the 3s has that, then the 3 will also have it :/
But I m confused...would I be able to unlock the bootloader?
I can see from this page: https://developers.google.com/android/images#blueline that 'blueline' is that vanilla AOSP version that corresponds to the P3 (right?)
The G account issue is less important. I just don't like 'syncing' stuff (accounts, photos etc). Worse case scenario, I ll create an empty profile, just for the logon
Click to expand...
Click to collapse
3s is not a model, it is the plural of 3. A Verizon Pixel 3 usually cannot be boot loader unlocked, but if you search this forum, you will find a few special cases where it has been done. One such case is at https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Vanilla AOSP generall refers to a ROM without any google services. See https://android.stackexchange.com/questions/53171/what-exactly-is-in-aosp for more info. Blueline is the Pixel 3 factory image, which has all the google services. It does not have any added carrier bloatware, but I wouldn't call it a vanilla AOSP.
You can turn off all the syncing stuff, and you may be able to skip the google account part. I just can't definitely say you can skip the google account because I have not tried it.
Another consideration with a locked bootloader is the end support date. Google support for the Pixel 3 ends in October, 4 months from now. There will be no security updates from Google after October. If you have an unlocked bootloader, you can switch to LineageOS and continue to receive security updates. That is what I plan to do.
dcarvil said:
3s is not a model, it is the plural of 3. A Verizon Pixel 3 usually cannot be boot loader unlocked, but if you search this forum, you will find a few special cases where it has been done. One such case is at https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Vanilla AOSP generall refers to a ROM without any google services. See https://android.stackexchange.com/questions/53171/what-exactly-is-in-aosp for more info. Blueline is the Pixel 3 factory image, which has all the google services. It does not have any added carrier bloatware, but I wouldn't call it a vanilla AOSP.
You can turn off all the syncing stuff, and you may be able to skip the google account part. I just can't definitely say you can skip the google account because I have not tried it.
Another consideration with a locked bootloader is the end support date. Google support for the Pixel 3 ends in October, 4 months from now. There will be no security updates from Google after October. If you have an unlocked bootloader, you can switch to LineageOS and continue to receive security updates. That is what I plan to do.
Click to expand...
Click to collapse
Clear!
I ll check on the resources you ve listed here
If the V-branded P3 is troublesome as it sounds, perhaps I should just go for the US Cellular carrier option. Bootloader may also be locked (but we know for sure that the V is..)
Interestingly, the US Cellular P3 is unlocked to all GSM carriers except Verizon, Boost, Virgin Mobile and Sprint
Is the carrier lock specified in the bootloader?
Btw, thanks for all the help!
jstoner said:
Clear!
I ll check on the resources you ve listed here
If the V-branded P3 is troublesome as it sounds, perhaps I should just go for the US Cellular carrier option. Bootloader may also be locked (but we know for sure that the V is..)
Interestingly, the US Cellular P3 is unlocked to all GSM carriers except Verizon, Boost, Virgin Mobile and Sprint
Is the carrier lock specified in the bootloader?
Btw, thanks for all the help!
Click to expand...
Click to collapse
SIM (carrier) unlock and bootloader unlock are separate, and not related. I have no idea if US Cellular is bootloader unlocked. Google sold a global model, which is the bootloader unlocked version, and the one I have. The IMEI/MEID number of the global variant begins with 990012 (don't know how many digits are significant). If I was buying it, I'd ask the seller to confirm it was bootloader unlocked.
Glad I could help.
dcarvil said:
SIM (carrier) unlock and bootloader unlock are separate, and not related. I have no idea if US Cellular is bootloader unlocked. Google sold a global model, which is the bootloader unlocked version, and the one I have. The IMEI/MEID number of the global variant begins with 990012 (don't know how many digits are significant). If I was buying it, I'd ask the seller to confirm it was bootloader unlocked.
Glad I could help.
Click to expand...
Click to collapse
The two P3 options I m considering (Verizon + US Cellular), both are sealed in their original box. According to that post, if the P3 hasn't ever being turned on, which is probably then when bootloader becomes locked
So I wonder if there is a SIM that comes with the phone already and that I have to remove that prior booting the phone. Not sure what he means with "VZW SIM". Is it a different type of SIM e.g. an eSIM??
I know for fact that these phones are CDMA-locked and only GSM is unlocked (but that's what I need anyways)
Does anyone here have any experience from an US Cellular P3 - is the bootloader locked? (the retailer of the phone doesn't seem to know much on such details..)
jstoner said:
The two P3 options I m considering (Verizon + US Cellular), both are sealed in their original box. According to that post, if the P3 hasn't ever being turned on, which is probably then when bootloader becomes locked
So I wonder if there is a SIM that comes with the phone already and that I have to remove that prior booting the phone. Not sure what he means with "VZW SIM". Is it a different type of SIM e.g. an eSIM??
I know for fact that these phones are CDMA-locked and only GSM is unlocked (but that's what I need anyways)
Does anyone here have any experience from an US Cellular P3 - is the bootloader locked? (the retailer of the phone doesn't seem to know much on such details..)
Click to expand...
Click to collapse
VZW SIM is just a Verizon SIM. It is probably the standard SIM card, not an eSIM. I would remove the SIM prior to booting, just to be safe. According to one of those posts, WiFi had to be connected before they could unlock the bootloader.
dcarvil said:
VZW SIM is just a Verizon SIM. It is probably the standard SIM card, not an eSIM. I would remove the SIM prior to booting, just to be safe. According to one of those posts, WiFi had to be connected before they could unlock the bootloader.
Click to expand...
Click to collapse
I ll find out soon, I ve ordered the P3 (US cellular stock)
Seller claims that it is sealed in original box. If that's really the case, then the carrier can't have put a SIM into it, right? But what about an eSIM? If they have the eSIM pre-programmed, then I can't possibly avoid booting the phone with it..
jstoner said:
I ll find out soon, I ve ordered the P3 (US cellular stock)
Seller claims that it is sealed in original box. If that's really the case, then the carrier can't have put a SIM into it, right? But what about an eSIM? If they have the eSIM pre-programmed, then I can't possibly avoid booting the phone with it..
Click to expand...
Click to collapse
Hmmm I think the way it works is that when the phone is produced, for a specific carrier, and the carrier wants it to have a sim, it's put in at the factory. So, I think, sealed with a sim in it, possible.
I don't think us cellular uses e-sims. Double check that but it doesn't look like one of the carriers that's capable of e-sims.
cheers, good luck. I have a vzw coming today, hoping it's new and can unlock as others have... we'll know soon.
Good news! Just got the phone and ... I ve managed to unlock the bootloader!
Exactly same case as described here. No SIM inserted, connected to WIFI, and in Dev Options, turned OEM unlocking to ON!
Then, on the instructions (link by opensense), I ve used adb and the bootloader is now unlocked! I m really chuffed about it
(btw the US Cellular supplied SIM was attached on the box (outside) with a sticker. Box was sealed.
Now, all is left is for me to pick that 'cleaner' Android option I always wanted!
But which one should it be? It's currently running blueline MP1.0(ROW)
Is there any clearer (official) Android ROM that I should switch to instead?
From G services, I would like to keep the Playstore and Maps...
jstoner said:
Good news! Just got the phone and ... I ve managed to unlock the bootloader!
Exactly same case as described here. No SIM inserted, connected to WIFI, and in Dev Options, turned OEM unlocking to ON!
Then, on the instructions (link by opensense), I ve used adb and the bootloader is now unlocked! I m really chuffed about it
(btw the US Cellular supplied SIM was attached on the box (outside) with a sticker. Box was sealed.
Now, all is left is for me to pick that 'cleaner' Android option I always wanted!
But which one should it be? It's currently running blueline MP1.0(ROW)
Is there any clearer (official) Android ROM that I should switch to instead?
From G services, I would like to keep the Playstore and Maps...
Click to expand...
Click to collapse
Congratulations. You'll have to define what you mean by the term "cleaner (official)" ROM. Blueline is the only official Google ROM for the Pixel 3. Anything else will be a custom ROM. I have no experience with any of the Pixel custom ROMs, so can't offer any advice on those.
You can disable most of the unwanted Google services in the blueline ROM. I'd recommend keeping the backup service, though.
Blueline MP1.0(ROW) is not a version listed at https://developers.google.com/android/images#blueline Go to Settings, About Phone, and tap Android Version. Check the "Android security update" date. Latest is June 5, 2021. I suspect yours is quite old.
If you want to update to the current blueline version, you have 2 options, OTA or flash a new factory image.
For OTA, go to Settings, System, System update, and follow instructions.
To flash a new factory image, follow the instructions at the link above. To prevent wiping your data when flashing, edit the flash-all.bat or flash-all.sh file, and remove the "-w" from the last line.
I you intend to change ROM's, I wouldn't bother updating.
Good luck.
dcarvil said:
Congratulations. You'll have to define what you mean by the term "cleaner (official)" ROM. Blueline is the only official Google ROM for the Pixel 3. Anything else will be a custom ROM. I have no experience with any of the Pixel custom ROMs, so can't offer any advice on those.
You can disable most of the unwanted Google services in the blueline ROM. I'd recommend keeping the backup service, though.
Blueline MP1.0(ROW) is not a version listed at https://developers.google.com/android/images#blueline Go to Settings, About Phone, and tap Android Version. Check the "Android security update" date. Latest is June 5, 2021. I suspect yours is quite old.
If you want to update to the current blueline version, you have 2 options, OTA or flash a new factory image.
For OTA, go to Settings, System, System update, and follow instructions.
To flash a new factory image, follow the instructions at the link above. To prevent wiping your data when flashing, edit the flash-all.bat or flash-all.sh file, and remove the "-w" from the last line.
I you intend to change ROM's, I wouldn't bother updating.
Good luck.
Click to expand...
Click to collapse
I think I ll probably stick with the official one then. My current is PQ1A.181105.017.A1 (which is very old as you guessed)
Which means I can jump to Android 10 or 11. From my experience, latest isn't always the best so I might have to keep reading, see if I should jump to a latest build of 10 instead. My emphasis is on stability/security - not new features...
And I want to ensure that the camera is at its best
jstoner said:
I think I ll probably stick with the official one then. My current is PQ1A.181105.017.A1 (which is very old as you guessed)
Which means I can jump to Android 10 or 11. From my experience, latest isn't always the best so I might have to keep reading, see if I should jump to a latest build of 10 instead. My emphasis is on stability/security - not new features...
And I want to ensure that the camera is at its best
Click to expand...
Click to collapse
If security is a concern, you'll want to go to Android 11. 10 has not been updated since August 2020, when Android 11 came out. Also, I believe there have been camera improvements since August 2020, which would not be in the latest Android 10 build.
I have not seen any reports of stability problems with the June 2021 Android 11 update, which has the latest security patches.
I don't know if you can do an OTA update to Android 11 from Android 9. You might have to go from 9 to 10 to 11. You can flash the Android 11 image without going to 10 first.
I intend to do via flashing (whichever version I decide in the end). Not a fan of OTA
I recently purchased a used Moto G7 Power (US version) and discovered after flashing Lineage OS that the phone was still locked to T-Mobile. The seller thought he had successfully unlocked it and contacted T-mobile on my behalf since he's still a current customer. They told him to complete the unlock he needed to complete the following command, "Settings > More Connection Settings > Network Unlock > Permanent Unlock" Since I'm currently running LOS on the phone, I no longer have these options.
So it seems like I'd need to flash back to the T-Mobile stock ROM to successfully unlock the phone. Is that correct?
If so, would the following guide accomplish this? I'm not experienced with flashing software so I wanted to get a 2nd opinion before I start mucking around and inadvertently brick the phone.
T-Mobile Motorola G7 Power Firmware | Stock ROM Guide
In this guide, we'll be sharing the easy steps to install the T-Mobile Motorola XT1955-5 (G7 Power) firmware flash file (codenamed Ocean). As an
www.getdroidtips.com
Any guidance is appreciated.
This thread has links to get stock firmware, and a guide to install it:
[GUIDE] Moto G7 Power/Supra [All Versions] Flash Back to Stock Firmware
Broke your G7 Power? No worries! As long as you can still get to fastboot, you can fix it. Note that this WILL wipe all data on the phone! First download the stock firmware for your model here...
forum.xda-developers.com
You probably want the TMO version.
The article has outdated links (404) to the firmware files, but both the article and the XDA thread are linking to the same website.
The XDA thread and the Article are listing slightly different "fastboot" commands, but either guide might work. I haven't tried it.
gemst10 said:
I recently purchased a used Moto G7 Power (US version) and discovered after flashing Lineage OS that the phone was still locked to T-Mobile. The seller thought he had successfully unlocked it and contacted T-mobile on my behalf since he's still a current customer. They told him to complete the unlock he needed to complete the following command, "Settings > More Connection Settings > Network Unlock > Permanent Unlock" Since I'm currently running LOS on the phone, I no longer have these options.
So it seems like I'd need to flash back to the T-Mobile stock ROM to successfully unlock the phone. Is that correct?
If so, would the following guide accomplish this? I'm not experienced with flashing software so I wanted to get a 2nd opinion before I start mucking around and inadvertently brick the phone.
T-Mobile Motorola G7 Power Firmware | Stock ROM Guide
In this guide, we'll be sharing the easy steps to install the T-Mobile Motorola XT1955-5 (G7 Power) firmware flash file (codenamed Ocean). As an
www.getdroidtips.com
Any guidance is appreciated.
Click to expand...
Click to collapse
Hi! I understand what u feel. And now there's a much easier way to restore your Motorola phone without much fear... Just put it in fastboot mode: Hold (Volume down+Power) While the phone is off. Let the software auto detect it... It will download the firmware version of the phone or the lastest one and Flash it for you. in just a few click . Oh you will need to register to the software that's all and it's all free..
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.
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.