Hello.
First, sorry for my bad english, I hope you will understand what I say.
I bought a MotoG5 in France just after Chrismas, the retailer is Fnac.
He stays stuck with NPPS25.137-93-14 with Android 7.0 and with 1 july security patch.
He is really slow for booting, and YouTube playback is not smooth.
I'm pretty sure it comes from the fact that the ROM is not optimised, so I was searching for Oreo update but looks like it doesn't work with my firmware.
Can someone tell me if is it possible to change my ROM for having a smooth experience on this phone ?
Thanks, and have a nice day.
If I were you just wait until the oreo official ota rolls out (it's already started in some regions & obviously no one will know what you will get it)
Obviously you could flash specifically firmware & use the soak test ota but why bother - do it wrong you hard brick your device
Do it right you still may have issues updating it in the future
Just be patient if you want oero
If you want a custom rom use lineageos 14.1
elio612 said:
Hello.
First, sorry for my bad english, I hope you will understand what I say.
I bought a MotoG5 in France just after Chrismas, the retailer is Fnac.
He stays stuck with NPPS25.137-93-14 with Android 7.0 and with 1 july security patch.
He is really slow for booting, and YouTube playback is not smooth.
I'm pretty sure it comes from the fact that the ROM is not optimised, so I was searching for Oreo update but looks like it doesn't work with my firmware.
Can someone tell me if is it possible to change my ROM for having a smooth experience on this phone ?
Thanks, and have a nice day.
Click to expand...
Click to collapse
As long as you just flash boot, system (sparse chunk 0 thru 4), oem, non-hlos.bin, oem, fsg and dsp you should be all fine up/downgrading to any firmware version (when upgrading you may need to also flash bootloader).
People say all around here in XDA that's its "impossible to downgrade" Moto phones, this is all a myth.
I just downgrade my Cedric from stock Oreo to stock nougat. Only thing you need to know is:
1.NEVER downgrade bootloader... EVER... This will immediately hardbrick any motorola phone.
2.When you fastboot, there's no need to flash gpt.bin (at least on Cedric, I never do that, as I don't know what might happen).
3.erase Cedric's modemst1 and modemst2 and never see your imei again (I also don't understand why people say it's necessary to do this. When fastbooting a Motorola phone I always erase only cache and user data and never had problem)
4. You can downgrade to any firmware (since the newest bootloader will support the old firmwares) as long as you just flash system, fsg, dsp and oem and boot (it's not necessary to flash recovery, it will turn back to stock on the first boot.
5. To relock your bootloader.. You just need to flash the same files cited above.
freeZbies said:
People say all around here in XDA that's its "impossible to downgrade" Moto phones, this is all a myth.
Click to expand...
Click to collapse
It is impossible to fully downgrade. You can only partially downgrade, which doesn't allow to relock the bootloader on an older version. If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official, non-soak update comes out to be able to relock the bootloader because at that point you can't even go back to the latest fastboot flashable version of Nougat (though if you try to flash it, you won't hard brick the phone).
My recommendation would be to wait until the stable version of Oreo comes out and is flashable through fastboot.
freeZbies said:
When you fastboot, there's no need to flash gpt.bin (at least on Cedric, I never do that, as I don't know what might happen).
Click to expand...
Click to collapse
Flashing gpt.bin (re)creates partition scheme. If flash fails, partition scheme will mess up, which will end up in hardbrick.
fstabman said:
It is impossible to fully downgrade. You can only partially downgrade
Click to expand...
Click to collapse
True. I'm currently on stock Nougat but my bootloader is on B8.31, which is Oreo's BL version. As I can't Downgrade BL, once I downgraded the system
I didn't receive any OTA notifications anymore (due to mismatching BL version)
fstabman said:
If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official.
Click to expand...
Click to collapse
Also true. That's why after I downgraded from the official Oreo to Nougat I don't get any update notifications anymore(Oreo has already been out for a few weeks around here).
fstabman said:
which doesn't allow to relock the bootloader on an older version.
Click to expand...
Click to collapse
Not true AT ALL. I've relocked my bootloader after downgrading my phone and it's okay. Once you type "fastboot oem lock" twice on fastboot you just need to flash what fastboot demands you to, which is system, boot and oem. Recovery, dsp, modem and bootloader are not demanded, so you can theoretically relock any Motorola phone in any firmware version, using any firmware you want. I can't attest that for every device with the Motorola flag but I've already downgraded and relocked moto G2 and moto E5 - besides Cedric - using fastboot and never had any problems so far.
I think people come up with these stories in fear they might brick their devices but never try for themselves, so they come here and spread myths about the impossibility of relocking your device without ever paying attention to fastboot's own instrucrions on how to flash the device.
I really think that if the fastboot relock method didn't really accept downgrades it would make no sense for it to exist, since you'll presumably not always have a newer firmware version available to relock your device, because under the premise of unlocking your BL its assumed that you will move to an unnoficial OS and under the premise of relocking its assumed you'll have to downgrade/go back to stock. It's all logic. If fastboot didn't allow downgrades as a means of relocking bootloader, the relocking feature would not have a lot of sense unless it could be secured that every device would always have an updated firmware version available, one after the other, which is not only a false statement but also makes no sense.
In other words, this stories about not being able to downgrade/having to flash newer firmware to relock BL are all plain bull****. Relocking your bootloader never had anything to do with your firmware version afaik (I never had trouble doing it my self at least. Can't say for Others)
freeZbies said:
True. I'm currently on stock Nougat but my bootloader is on B8.31, which is Oreo's BL version. As I can't Downgrade BL, once I downgraded I didn't receive any OTA notifications anymore
Also true. That's why after I downgraded from the official Oreo to Nougat I don't get any update notifications anymore(Oreo has already been out for a few weeks around here).
Not true AT ALL. I've relocked my bootloader after downgrading my phone and it's okay. Once you type "fastboot oem lock" twice on fastboot you just need to flash what fastboot demands you to, which is system, boon and oem. Recovery, dsp, modem and bootloader are not demanded, so you can theoretically relock any Motorola phone in any firmware version, using any firmware you want. I can't attest that for every device with the Motorola flag but I've already downgraded and relocked moto G2 and moto E5 - besides Cedric - using fastboot and never had any problems so far.
I think people come up with these stories in fear they might brick their devices but never try for themselves, so they do here and spread myths about the impossibility of relocking your device but it makes no sense. I really think that if the fastboot relock method didn't really accept downgrades it would make no sense for it to exist, since you'll presumably not always have a newer firmware version available to relock your device if it was really as they say.
In other words, this is all plain bull****. Relocking your bootloader never had anything to do with your firmware version afaik (I never had trouble doing it my self at least. Can't say for Others)
Click to expand...
Click to collapse
So should I be "on safe side", if I lock bootloader with NPPS25.137-93-8 image but NPPS25.137-93-14 installed right now?
fstabman said:
It is impossible to fully downgrade. You can only partially downgrade, which doesn't allow to relock the bootloader on an older version. If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official, non-soak update comes out to be able to relock the bootloader because at that point you can't even go back to the latest fastboot flashable version of Nougat (though if you try to flash it, you won't hard brick the phone).
My recommendation would be to wait until the stable version of Oreo comes out and is flashable through fastboot.
Click to expand...
Click to collapse
Andrej_SK said:
So should I be "on safe side", if I lock bootloader with NPPS25.137-93-8 image but NPPS25.137-93-14 installed right now?
Click to expand...
Click to collapse
Yes. Take care of backing up your efs partition using twrp 64 bits first.
After that, download an official (signed) fastboot firmware and flash only system sparcechunks, oem and boot - in other words, do what fastboot tells you.
Dont "fastboot erase" anything but cache and user data and u should be fine. This command has been known for ages as being the cause of lost Imei (on moto g2 I think it broke if u erased the fsg partition, on Cedric its modem that breaks your Imei if erased).
If you for some reason have problems with signal/Sim cards not working, then u may flash the other partitions(fsg, dsp, and Non-hlos[modem])
I say these Because there may be incompatibilities related to The modem. For example, when downgrading from Oreo to NPPS25.137-93-2-5 using fastboot, everything went fine, but if I upgrade from npps25-137-93-2-5 to Oreo and don't flash modem And fsg, signal will not work. Also, if I downgrade from Oreo to Nougat using twrp and I don't flash fsg, fingerprint scanner wont work.
But in essence, as long as you don't "fastboot erase" anything unnecessary and don't touch bootloader (and seemingly gpt.bin, as someone mentioned above) , you should be safe.
freeZbies said:
Once you type "fastboot oem lock" twice on fastboot you just need to flash what fastboot demands you to, which is system, boot and oem.
Click to expand...
Click to collapse
The problem is, it fails at validating oem when trying to relock. At least on my end, after updating NPPS25.137-93-2-5 > First Oreo OTA > Second OTA > Back to NPPS25.137-93-2-5.
fstabman said:
It is impossible to fully downgrade. You can only partially downgrade, which doesn't allow to relock the bootloader on an older version. If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official, non-soak update comes out to be able to relock the bootloader because at that point you can't even go back to the latest fastboot flashable version of Nougat (though if you try to flash it, you won't hard brick the phone).
My recommendation would be to wait until the stable version of Oreo comes out and is flashable through fastboot.
Click to expand...
Click to collapse
fstabman said:
The problem is, it fails at validating oem when trying to relock. At least on my end, after updating NPPS25.137-93-2-5 > First Oreo OTA > Second OTA > Back to NPPS25.137-93-2-5.
Click to expand...
Click to collapse
Interesting.. Are you sure all files are signed? What error fastboot gives you?
I'll try making a video later today showing that it is possible to do it, so that u can see it.
freeZbies said:
Interesting.. Are you sure all files are signed? What error fastboot gives you?
I'll try making a video later today showing that it is possible to do it, so that u can see it.
Click to expand...
Click to collapse
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:oem: not found
target reported max download size of 536870912 bytes
sending 'oem' (188494 KB)...
OKAY [ 6.023s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.093s
I tried with 93-2-3 as well and get the same invalid signed image issue.
A question though, if the bootloader were to lock successfully after doing this (and since it still has some files from Oreo to prevent hard bricking), would it actually receive any OTAs?
fstabman said:
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:oem: not found
target reported max download size of 536870912 bytes
sending 'oem' (188494 KB)...
OKAY [ 6.023s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.093s
I tried with 93-2-3 as well and get the same invalid signed image issue.
A question though, if the bootloader were to lock successfully after doing this (and since it still has some files from Oreo to prevent hard bricking), would it actually receive any OTAs?
Click to expand...
Click to collapse
Really, the error you've been getting has to be related to you being unable to downgrade, since it attests the image is signed (error for unsigned I made says "unsigned or corrupt image).
Yep, seems like I was wrong, I might just have been lucky never to get an error like that before
Anyways, have you tried npps25-137-93-2-5 yet? It's the latest security patch (July) released in Brazil. I'm now somewhat confused lol.
Anyways, relocking your BL doesn't allow you to get otas, since some of the partitions will remain in the newest version, and that's long been known to render your phone unable to receive otas (I guess all partition's hashs are checked against stock ones before ota) and it will also not get your warranty back, so it's kind of useless unless you just want to test to see if u can downgrade OR if u want to go back to stock and never modify the device again.
EDIT: I was wrong, if you're on untouched stick you'll get OTA's, regardless of being unlocked or not.[/B] I thought I wouldn't receive OTA's anymore because it took me more than 2 weeks for me to get an OTA notification after it had already rolled out in Brazil, whereas for other updates I had gotten it really early By the way, I had other people confirm me that I wouldn't get it if I had modified my phone, but that's not true because when I got the OTA notification I had a rooted phone with lots of mosifixatiins. So I'm here to rectify this post and say that I was wrong: if you're on stock and there's an update rolling out, you should be getting it sooner or later regardless of your phone being rooted or not, but trying to apply the OTA in a modified phone will brick your device.
Anyways, I find it very strange that you're getting this error only when flashing the oem partition. You shouldn't be able to flash any of them.
If u want, I can send u the signed oem image I used to relock mine. I'm sure it won't cause any conflicts or glitches since this partition only contains some carrier bloat ware alongside some Motorola apks. I'm not sure if it will be Flash able alongside npp93-2-3 files during the same oem lock operation, due to mismatching firmware versions, but I think it'd be worth trying.
freeZbies said:
Anyways, have you tried npps25-137-93-2-5 yet? It's the latest security patch (July) released in Brazil. I'm now somewhat confused lol.
Click to expand...
Click to collapse
Yep, tried that one. I tried many different, older versions as well (got a hard brick or two as well, but I could restore it without issues). I can flash oem as long as it's not after I used the fastboot oem lock command twice. I do that and I am no longer able to do it.
Anyways I think I'll wait til Oreo stable comes out, all I was interested in was having the ability to take OTA updates again. Hopefully it will come out soon.
Well. If you wanted Official Oreo you wouldn't get it anyways.
But now that you said I'm curious to say how I managed to downgrade & relock without EVER getting that message.
To tell you the truth, I've seen many fastboot errors already, but this one is pretty new to me.
freeZbies said:
Well. If you wanted Official Oreo you wouldn't get it anyways.
But now that you said I'm curious to say how I managed to downgrade & relock without EVER getting that message.
To tell you the truth, I've seen many fastboot errors already, but this one is pretty new to me.
Click to expand...
Click to collapse
Did you downgrade from the first Oreo soak test or the second, more recent one?
fstabman said:
Yep, tried that one. I tried many different, older versions as well (got a hard brick or two as well, but I could restore it without issues). I can flash oem as long as it's not after I used the fastboot oem lock command twice. I do that and I am no longer able to do it.
Anyways I think I'll wait til Oreo stable comes out, all I was interested in was having the ability to take OTA updates again. Hopefully it will come out soon.
Click to expand...
Click to collapse
By the way could you tell me what exactly got your phone hard bricked?
freeZbies said:
By the way could you tell me what exactly got your phone hard bricked?
Click to expand...
Click to collapse
Doing a downgrade while flashing gpt.bin and bootloader with version B8.24.
Related
Krassermensch's Firmware Update Tool
My situation:
I'm too young to buy the Sunshine App to set my device S-Off but I want to update my device's firmware every time a firmware update's available. Since I compile ROMs and cannot do that via OTA updates the only acceptable way for me is to install signed firmwares in a locked bootloader. After doing that manually I thought I should write a tool that installs the right firmware for your device automatically. As I'm already running the latest firmware on my device after doing the procedure manually I cannot test if the flash part works correctly. Anyway, I achieved to read out the CID as well as the current firmware version and my tool reports that I'm running the latest firmware version I integrated for my device what's correct. So this part works well.
How the tool works:
The tool asks you if you've already installed the HTC USB drivers on your computer. If you haven't you can install it easily using my tool. After that the tool explains you how to set up your phone to be detected by the computer. Then it checks which device you have and checks which firmware's currently installed on it. Right after that the tool installs all the firmwares newer than the one that's currently installed on your phone one after another until the latest firmware my tool is shiped with runs on your device. The procedure doesn't wipe your data since signed firmware-updates are installed.
Requirements:
- An HTC 10
- A computer running windows
- An internet connection
- An unlocked bootloader
- An installed TWRP
Who is this tool for?
All the people who can't or don't want to set their device S-Off while running a non-stock ROM.
Why should I use this tool?
- It updates your firmware to the latest one available for your device automatically
- It doesn't wipe your storage
- You don't need to be S-Off
Download
https://www.androidfilehost.com/?fid=745425885120704223
When the file is downloaded just extract it on your Windows computer and run the batch file. Everything else will be explained.
Important to know
Your boot and recovery partitions will be replaced by the stock ones so after successfully updating your firmware you need to reflash TWRP as well as your Boot partition.
This process is performed automatically now. No need to do that manually.
Tools using ADB just like mine may interfere with other tools that also use ADB. Make sure all these tools are disabled.
Now I need your feedback to be able to optimize the tool! I'll add new firmwares from time to time. I'm looking forward to your reviews
GitLab
https://gitlab.com/Feulner/Firmware-Update-Tool-HTC10
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!
This works with unsigned firmware?
Good job, though irrelevant to me
xunholyx said:
This works with unsigned firmware?
Good job, though irrelevant to me
I would guess that you would have to have matching CID and MID of course.
Click to expand...
Click to collapse
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...
krassermensch said:
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...
Click to expand...
Click to collapse
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.
xunholyx said:
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.
Click to expand...
Click to collapse
Since when do you have to go back to stock to "fastboot flash zip some_firmware.zip" (as this tool does)?
--beaups
Hm sounds good, but i wont use it until we have some more information what it actually does.
As far as i know, theres no way to just update your firmware with signed zips without partly wiping your device. I had to reflash Viper10 (or restore a nandroid backup) the last time i updated my firmware, cause boot and recovery partitions got replaced. Not completely sure if this affects stock devices, it may work there, but not for devices which are modified with a custom ROM. For this you need a NoWipe firmware from sneakyghosts thread, but these cant be flashed while s-on.
So please explain in more details what your tool does, of course when youve got your sleep .
It most likely flashes firmware zips from OTA updates since those do not wipe the device. He already said it does that, he said if you're on a very old firmware it will keep updating your firmware progressively until you're on the latest version. So if you've never updated before, and there have been three updates since then, the tool will flash the firmware zip of each OTA one after the other.
Updated the main post, hopefully everything's clear now. I need your reviews now. I'm also thinking about an automatic bootloader lock with backup solution so you don't need to lock your bootloader manually and also don't lose your data partition.
Why it doesn't work with unlocked bootloader?
CroCop18 said:
Why it doesn't work with unlocked bootloader?
Click to expand...
Click to collapse
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com
xunholyx said:
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com
Click to expand...
Click to collapse
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently... And no, u don't need to be stock. This tool just requires a locked or relocked bootloader. U can use whatever ROM u like. U just need to have a locked bootloader and my tool installs the latest firmware I integrated for your HTC 10 model. I know what I do. You should just read my posts a bit more carefully to prevent yourself from contending wrong things...
krassermensch said:
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently...
Click to expand...
Click to collapse
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.
xunholyx said:
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.
Click to expand...
Click to collapse
Yeah, dude, I think I wouldn't be able to write a batch tool with fastboot and adb if I didn't know the whole stuff. My broken Nexus 4 has teached me a lot over the last 3½ years
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
You do not need this tool if you are Stock everything, unless you unlocked your bootloader.
Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
No, I could write a tool for manual OTA flashing, too, but I don't want to do that since OTAs are for stock devices which are notified about OTA updates automatically. If you want to flash OTAs quicker: there's a thread here on xda where OTA zips are shared with an explaination how to flash it manually... This tool can be used by stock device's owners but it wouldn't be necessary...
krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.
-Vulture- said:
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.
Click to expand...
Click to collapse
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?
krassermensch said:
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?
Click to expand...
Click to collapse
Thats what i did, bootloader was unlocked and flash successfully. I extracted the firmware.zip from an official OTA (TMOB-101) for my device and flashed it via ADB from my PC. Since the firmware.zip is signed, it can be flashed. Doesnt work with modified zips however, like the ones from sneakyghosts thread. He removed unnecessary stuff like the flash command for boot and recovery which my broke my phone initially. Thats why you need TWRP to restore them later.
As you already said with your tool, its also important here to get the right file to flash and not to skip a firmware update in between. You have to go from very old -> old -> current without skipping old.
I used the step-by-step instructions from here:
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520
Dear all
There are so many people looking for exactly samething that iam looking for but unfortunately there is not any proper tutorial available.
Could you confirm if there is anyway to install any other ROM on chinese moto z play ? i don't mind if i have to install each OTA manually.
If so could you please guide step by step guide how to perform this?
If there so no any ROM that can work with chinese variant is there any custom ROM that would and support Moto Mods?
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
freeman_g said:
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
Click to expand...
Click to collapse
Did you try editing build.prop?
jameelmemon said:
Did you try editing build.prop?
Click to expand...
Click to collapse
I see that you has not even tried to look through my thread (link was provided in previous post). Suggest to do that (espesially the very end) before further questions / discussion
I have gone through almost all threads including your befiore posting or asking you that question
you are referring to
2) target script is probably /device/company_name/device_name/init.device_name.usb.rc
3) there is a string in that script: write /sys/class/android_usb/android0/iProduct ${ro.product.model}
aactualy {ro.product.model} is variable in build.prop so that script (/device/company_name/device_name/init.device_name.usb.rc) from build.prop
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Finally i manage to install 7.1.1
My phone is addison after installing RETAIL version (7.0)
I installed RETAIL version then downloaded ota then installed 7.1.1 OTA from this thread https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
phone should not be locked/encrypted or protected at least i bricked it and it was not booting up.
Now need to change two things those are in bootloader (SKU and ro.carrier) fastboot getvar all
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Just found ro.carrier comes from kernel and will be taken from kernel each time devices boots up. so we need someone to customize the kernel and add retru or retus to kernel as ro.carrier.
sku i can not change as i am getting error of command is not allowed
can anyone help regarding this?
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
freeman_g said:
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Click to expand...
Click to collapse
freeman_g said:
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Click to expand...
Click to collapse
Just install fresh retail version then sideload first ota via adb then boot your phone do not complete setup.
then install 7.1.1 then do factory restore then you are good to go
and it have so many great features you can view them here specially camera app
freeman_g said:
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
Click to expand...
Click to collapse
Initally it didn't work and stuck on bootloader unlock warning but later it worked perfect and iam using 7.1.1 and now trying to figure out how we can change sku and channel to get official OTA.
Sku (XT1635-03) is in bootloader but i can't write is with Fastboot, channel (retcn) is in kernel.
Lucky you I still have the same problem
Yesterday I tried to start with flashing stock retail 7.0 (the link you have provided earlier) but due to fact I had already flashed image with April security patch I didn't manage to downgrade bootloader and gpt (security downgrade issue)
Despite this fact phone boots but small OTA with April security patch did not agree to flash for the same reason: wrong name "addison_retcn"
So I believe the problem is in bootliader and I will probably manage to fix it only with full 7.1.1 retail image.
Glad to see you guys are making some progress. I'll try flashing the retail version on my Chinese Z Play. I'm currently on Epsilon rom (stock rooted 7.0) with January patch. Can I flash retail and then the ota?
I woulf suggest the following:
1) At your current firmware install Aida64 and check if you have addison or addison_cn product name in System section. If you see only addison - then you may install retail firmware and OTAs
2) If you still have addison_cn here then try to install retail firmware provided above (bootloader can be upgraded) and then check product name in Aida64 again. If it changed to addison - you can sideload OTAs. If still addison_cn - then you can't
Thanks @freeman_g
Here is a screenshot of AIDA64 on my device: https://imgur.com/gallery/Or2JF
I guess I should be good to go, right?
Yes, should work
What I can't understand why I still with addison_retcn. Probably, will have to wait for full 7.1.1 retail image
Sorry for the noobie question, but how did you guys with XT1635-03 flash the XT1635-02 firmware? Did you use this script? Did you flash the full rom, including partition, fsg, and modem, no restrictions? I bought my device at Banggood. I know it will come with a shop rom and I would like to install the stock firmware. I want to be prepared when it arrives. Don't want to take the risk of brick it and would like to leave the custom roms for later.
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
freeman_g said:
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
Click to expand...
Click to collapse
Awesome, many thanks for sharing. Does this mean you'll receive future OTAs?
in brief
I have unlocked the botloder with commands in cmd, I have uploaded magisk, I expanded internal memory by sd card (my error). Unfortunately, after the upgrade to Android 9, the phone fail at receive any new updates (installation error of 30%). Subsequently, dumped magisk, did not help, , I uninstall sd card, now I did restore the factory data and the updates still do not work. November version of Andorida is badly bugged and there are problems even with the camera. So it looks like I'll have to send a phone for guarantees, a question now how to block a botloader or you have an idea how to fix ota update.
same here, but now you can download the full 10.0.3.0 rom to install with miflash. https://en.miui.com/download-354.html
fine but how to reblock a botloader ?
karenz88 said:
fine but how to reblock a botloader ?
Click to expand...
Click to collapse
use this on fastboot:
Code:
fastboot oem lock
Warning: this will wipe your data and if you have tampered with phone's partitions phone will hard brick. Make sure to have a backup. Other people have also experienced issues with January update. Locking the bootloader and booting the phone successfully doesn't mean that you will have January update for sure.
There's no point in locking the bootloader or returning the phone just because you failed to apply OTA update. Your phone is perfectly fine. Most of us had problems and bootloop while trying to apply Magisk OTA. This has been a frequent issue since the initial Pie update and the phone has nothing to do with it. It's either Google implemented stricter security policies or current version of Magisk are having Pie compatibility issues. If OTA is to important to you, just flash an official fastboot image and don't root your phone.
Ota does not have much meaning for me, but I have a problem with the camera and it annoys me already. I reblock a botloader and still cant update phone...
karenz88 said:
Ota does not have much meaning for me, but I have a problem with the camera and it annoys me already. I reblock a botloader and still cant update phone...
Click to expand...
Click to collapse
Fastboot image of 10.0.3 is already out. You could consider flashing your phone with "flash all" option to fix the errors. And i would recommend keeping the bootloader unlocked because many mi a2 owners got their phone bricked as a result of ota update with a locked bootloader in which case the only workaround is to disassemble the phone.
Basically forgot that I'd unlocked the bootloader and allowed the update, pretty stupid
Pretty sure that the next step from here is to flash the stock firmware, unless I'm mistaken?
Looking for any firmware for the XT1922-2 JETER model, which I think is an exclusively UK thing. Haven't been able to find any thus far which is both Jeter and XT1922-2, so would be intensely grateful if someone could help me!
Craventoby said:
Basically forgot that I'd unlocked the bootloader and allowed the update, pretty stupid
Pretty sure that the next step from here is to flash the stock firmware, unless I'm mistaken?
Looking for any firmware for the XT1922-2 JETER model, which I think is an exclusively UK thing. Haven't been able to find any thus far which is both Jeter and XT1922-2, so would be intensely grateful if someone could help me!
Click to expand...
Click to collapse
Yes just reflash latest stock firmware and you'll be good and what's your sw channel version? Like does it say reteu or something like that. There alot of models under the xt11922-2 device number.
ninjakira said:
Yes just reflash latest stock firmware and you'll be good and what's your sw channel version? Like does it say reteu or something like that. There alot of models under the xt11922-2 device number.
Click to expand...
Click to collapse
Unfortunately I've already tried flashing a few different firmware versions without success, so it just says the most recent version of that. Are there any models under the XT1922-2 called Jeter? I haven't been able to find any.
Craventoby said:
Unfortunately I've already tried flashing a few different firmware versions without success, so it just says the most recent version of that. Are there any models under the XT1922-2 called Jeter? I haven't been able to find any.
Click to expand...
Click to collapse
That's not Jeter. It's Aljeter. There's a bunch with that model number. But helps if know your original software channel.
madbat99 said:
That's not Jeter. It's Aljeter. There's a bunch with that model number. But helps if know your original software channel.
Click to expand...
Click to collapse
I dunno what to tell you, it says Jeter on the bootloader screen. Will have another go at flashing Aljeter software, but hasn't worked so far.
Craventoby said:
I dunno what to tell you, it says Jeter on the bootloader screen. Will have another go at flashing Aljeter software, but hasn't worked so far.
Click to expand...
Click to collapse
Some say Jeter in one line of props, then Aljeter in another. I know it's stupid. But all the ones with your model number (that I have seen anyways) are Aljeter. I could be wrong. But I don't think there is a Jeter with 3 GB of RAM
ninjakira said:
Yes just reflash latest stock firmware and you'll be good and what's your sw channel version? Like does it say reteu or something like that. There alot of models under the xt11922-2 device number.
Click to expand...
Click to collapse
Having some trouble, I get error messages when I try and flash both gpt.bin and bootloader.img - for both I get an error saying that the image failed validation/ preflash validation/ remote failure. Is there something I'm not doing?
Craventoby said:
Having some trouble, I get error messages when I try and flash both gpt.bin and bootloader.img - for both I get an error saying that the image failed validation/ preflash validation/ remote failure. Is there something I'm not doing?
Click to expand...
Click to collapse
You're likely trying to downgrade or have a locked bootloader, or both.
Craventoby said:
Having some trouble, I get error messages when I try and flash both gpt.bin and bootloader.img - for both I get an error saying that the image failed validation/ preflash validation/ remote failure. Is there something I'm not doing?
Click to expand...
Click to collapse
You can't downgrade if the gpt.bin has been updated which it has. Use the latest most recent firmware and everything should be fine. If the latest firmware has not been uploaded then I'm sorry to say your stuck with a bricked phone until the latest firmware is uploaded. Keep checking the link with the firmwares untill you see the latest one
ninjakira said:
You can't downgrade if the gpt.bin has been updated which it has. Use the latest most recent firmware and everything should be fine. If the latest firmware has not been uploaded then I'm sorry to say your stuck with a bricked phone until the latest firmware is uploaded. Keep checking the link with the firmwares untill you see the latest one
Click to expand...
Click to collapse
Actually, after trying the whole thing over a second time, flashing each command line by line, my phone is fixed. Have no idea how if what you're saying about it being impossible to downgrade is right, but certainly not complaining. In the end, the RETGB software for ALJETER was the one that worked.
Craventoby said:
Actually, after trying the whole thing over a second time, flashing each command line by line, my phone is fixed. Have no idea how if what you're saying about it being impossible to downgrade is right, but certainly not complaining. In the end, the RETGB software for ALJETER was the one that worked.
Click to expand...
Click to collapse
Hey as long as my guide helped you that all I care about In the end lol the biggest common issue most people have is not paying attention to the command lines lol. Glad your able to enjoy your phone. And it sounds exactly it sounds once the gpt.bin is updated you can't use a older firmware which in turn would be downgrading.
lol am I the only one who's been taking updates with unlocked bootloader having no problems?
blowingoff said:
lol am I the only one who's been taking updates with unlocked bootloader having no problems?
Click to expand...
Click to collapse
it seems the problem people are having is after they have already rooted their devices they're trying to take an ota update. Which you can't do. Having an unlocked bootloader doesn't affect that. the reason is because the stock recovery has been replaced by twrp. In order to install an ota update when your phone is rooted you must reflash either the stock firmware of the current version you're on or just flash the new stock firmware. Or in this case accidentally using the command lines wrong lol
ninjakira said:
it seems the problem people are having is after they have already rooted their devices they're trying to take an ota update. Which you can't do. Having an unlocked bootloader doesn't affect that. the reason is because the stock recovery has been replaced by twrp. In order to install an ota update when your phone is rooted you must reflash either the stock firmware of the current version you're on or just flash the new stock firmware. Or in this case accidentally using the command lines wrong lol
Click to expand...
Click to collapse
yes, just what I thought. unlocked bootloader doesnt change anyrhing, but having the phone system modified may do
ninjakira said:
it seems the problem people are having is after they have already rooted their devices they're trying to take an ota update. Which you can't do. Having an unlocked bootloader doesn't affect that. the reason is because the stock recovery has been replaced by twrp. In order to install an ota update when your phone is rooted you must reflash either the stock firmware of the current version you're on or just flash the new stock firmware. Or in this case accidentally using the command lines wrong lol
Click to expand...
Click to collapse
Also, people confusing 2 different issues regarding updates.
The only REAL issue I've heard is, after flashing firmware on an unlocked bootloader, they are no longer receiving OTA updates. Maybe changed their update channel or something.
madbat99 said:
Also, people confusing 2 different issues regarding updates.
The only REAL issue I've heard is, after flashing firmware on an unlocked bootloader, they are no longer receiving OTA updates. Maybe changed their update channel or something.
Click to expand...
Click to collapse
Yea that's why I've been starting to ask for sw channel version ? its been alot more helpful knowing that before anything lol. I haven't had any issue flashing stock firmware then taking an ota update its how I was able to take the latest security patch update as well as the other updates before they were uploaded on the firmware site ( I hate saying mirrors.lolinet because well darkweb has sites called that also unfortunately and there just not good lol) but that's just me lol
It have tried endless times trying to get root access via magisk by patching my retail Canada boot.img file. My phone has an unlocked bootloader and I definitely have the right boot image as I tried another boot image from another firmware and got a startup failure which I fixed by flashing the retail Canada boot.img. It patches okay and flashes okay (except for message "image signed with key bad key") but no root access and no installed Magisk. If anyone has a solution, has gained root access some other way or knows for a fact that magisk does not work with this model phone I would be very interested to know. This is the firmware I used the boot file from : XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-57
Thanks
Bad Key is normal after you unlock the boot loader. Have you tried side loading the Magisk apk along with a copy of the boot.img and have the app mod the boot.img? Then move the modded boot image back to your pc and fastboot it on to the phone. That's what I did with my G7Power.
Side loading
Not sure what side loading is but I did patch the boot file with Magisk manager, put it on my PC and fastbooted it to my phone with no results. The ROM for the G7 Play is different than older androids. I tried to create a makeshift recovery for it but my ROM does not have a recovery.img or other older android ROM files for that matter. I will have to wait for some kind of workaround for magisk or someone takes on the challenge to create a recovery for the different file system. I installed a recovery for my Moto G4 plus and rooted no problem. I should have researched more before I purchased the G7 Play and unlocked the bootloader so now I am at the mercy of development.
Thanks for your reply.
Nothing
I tried rooting the phone with the Magisk... Nothing.
I tried to relock the bootloader... Nothing.
What works on the other Moto G7s does not work on our G7 Play.
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
realsine said:
Hello,
relocking Moto G7 play:
* first reflash the 'boot.img' from the correct firmware file - 'fastboot flash boot boot.img' (in the Internet there are official images to the smartphone)
* then you can lock the bootloader again with 'fastboot oem lock'.
"bad key" is gone, SafetyNet test passed and OTA is working again.
Best regards
Click to expand...
Click to collapse
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Marcondes BR said:
Do you have a g7 play and did that? So show us because I could not.
When you use this command an error occurs because the "oem unlocking" option is not checked. And it is not checked because the system disables this option after we unlock the bootloader.
So, unless there is another way to check this option, it's not possible to relock the bootloader. That's what I think.
Click to expand...
Click to collapse
Yes, I have a Motorola Moto g7 play.
When I open the bootloader, I can't close it immediately. I get a "bad key" (or something like that). I have to flash the matching original boot.img first.
So in the bootloader:
* fastboot flash boot boot.img
And if that was successful, then afterwards (without restart)
* fastboot oem lock
Possibly the last command must be entered a second time, but this will be output when
If the command works, then the smartphone boots automatically at this point and the bootloader is closed again.
I assume that you have the correct boot.img and must flash.
I have performed this procedure several times successfully.
Information: at every LOCK and at every UNLOCK the data is reset (Factory reset?).
relock bootloader confirm
I can confirm this does work. I just relocked and unlocked my bootloader with those instructions. Again if anybody has successfully rooted this phone I would love to know.
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
thetesterman said:
Any update on this ? I would love to buy this phone but not till I know for sure that it can be rooted.. Any insight into this would be greatly appreciated !!
Click to expand...
Click to collapse
This device is definitely rootable -- there is no doubt as to proof of concept. It's just a matter of a viable root method being ironed out. The developer of Magisk (topjohnwu) has stated that the current difficulty with installing systemless root on the Moto G7 Play (via patched boot image) is due to the particular A/B partition index of the device. He is actually working on a universal resolution now. It also appears that TWRP custom recovery is being compiled by the guys over at TeamWin, not to mention unofficial builds being compiled by other dedicated devs (which will likely come first). I went ahead and bought a G7 Play and am just patiently waiting for the imminent resolution for root, TWRP, and hopefully, full-on ROM development. In other words, it's not a matter of if; it's just a matter of when.
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
avf90m said:
I expect the devs to release an unofficial version of twrp soon for g7 play. I already tried the same thing with patching my boot img and flashing in fastboot but still no dice. Just bought the the phone so I hope it gets released soon so we can finally root!
Click to expand...
Click to collapse
Amen to that.
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
LexusBrian400 said:
Root is all that this phone needs. It's amazing. I'm so happy with it. I can't believe what you get for the price. Why would you buy anything else?
Click to expand...
Click to collapse
Couldn't agree more, fantastic phone ( wish it had wireless charging though ) and all I need is root.
ninjakira said:
If someone can confirm the current root method for the g6 play could work with the g7 play id happily make a guide for y'all at least. If assuming this device also auto encrypts. Try just booting twrp first, press cancel, swipe right to allow system modifications, go to wipe, push the format button next to the advanced wipe button, type yes, go back into bootloader and flash twrp and internal storage should be readable from there adb push the encryption disabler then magisk. And just in case someone here trys to use the twrp for the g6 play I'm feeling you now it won't work in case that needs to be said. Try using magisk beta also if stable doesn't work I noticed we had to use beta for a little bit before we could use stable
Click to expand...
Click to collapse
The G6 Play root method will not work on the G7 Play. The G7 Play uses the A/B partition index. There are currently a few developers ironing out a viable root method and also working on a stable TWRP build. Many Moto G7 Play owners have hard bricked their devices by trying root strategies intended for devices with standard GPT partition tables.
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Viva La Android said:
I only recently bought my G7 Play and I am curious as to whether my firmware version is all the way up to date. I have the Boost Mobile variant (xt1952-4) and I'm on the PCY29.105-59 firmware build with a March 1, 2019 security patch level. According to my System Update check in Settings, this is the current build. However, it would seem that with a device so recently manufactured, there would be a more current firmware version available. Are there any Sprint, Virgin, or Boost variant owners who can clarify this? And I apologize if this is off topic.
Click to expand...
Click to collapse
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
GatoDeNieve said:
I'm on OPENMX channel and there is currently a June 1st update waiting to be installed. I'm reluctant to install it because I don't know if it will interfere with the root process down the line.
Click to expand...
Click to collapse
Ok thanks for the info. I would guess an OTA update for my variant is imminent within the next couple of weeks at least.
Motorola is not in the practice of patching root exploits via OTA updates. The company actually supports both OEM Unlocking and Android development. I don't think you would have any future issues with root by installing your pending OTA. But at the same time I don't blame you for holding off. When in doubt, don't update. Again, I do thank you for the info.
The xt1952-4 (Sprint, Boost, Virgin) variant is rolling out with PCY29.105-134 with June 1 security patches. I just got notification about ten minutes ago.