TWRP DIRTY PORT FOR G7 PLAY
My friend was looking to get a G7 Play, so I wanted to whip something up for him really quick. I managed to make a dirty port of TWRP for the G7 Play, taken from the G7 TWRP image since they're the same SDM632 chipset. Until you guys get a real, proper build of TWRP done with the proper source code, consider this a stop gap to at least be able to flash things! It's not perfect obviously but hopefully it's good enough for now!
AS ALWAYS, I DO NOT TAKE RESPONSIBILITY IF FLASHING THIS BRICKS YOUR PHONE. WHAT YOU CHOOSE TO DO TO YOUR PHONE IS ON YOU!!!
WHAT WORKS:
It boots! As you can see here, the G7 Play is in fact running this recovery image just fine
Not sure, don't have the phone to test for myself
WHAT DOESNT WORK:
Because this is a dirty port, the recovery will think this is a G7, when as we all know this is in fact a G7 Play. There is nothing I can really do about this, this is the nature of dirty ports
Not sure, don't have the phone to test for myself
DOWNLOAD:
DOWNLOAD LINK HERE
I cannot provide any source code since this was a dirty port, so no actual source was used. The only things I used to make this were a G7 TWRP image, a G7 Play boot image, and carliv's image kitchen
HOW TO USE:
Reboot to fastboot
Flash the dtbo with fastboot flash dtbo dtbo.img
After that boot from the recovery with fastboot boot recoveryname.img
THANKS TO:
@Alberto97 for the G7 TWRP image I dirty ported from
The G7 Play Telegram group for testing out the image I made, since I don't have a G7 Play to test this on myself. Specifically @noslen7 for testing the image and figuring out how to get it to run (need to flash the dtbo first) and for sending me the image I used above to show it's working and bootable
Carliv for that Carliv Image Kitchen he made, that tool rocks!
I can't test it anymore but if it's uses the same things as the one I built which was inspired by Alberto, do not try to install the TWRP unless you have already flashed the second bank.
fastboot boot recovery.img indeed won't harm so you can try that.
Any idea what works more then the one I built?
Which dtbo.img are we supposed to flash - the one from the stock ROM, or something else?
Great work!
First of all thanks for your hard work. I was really happy to see your post. I have followed the instructions exactly and I got "Failed (too many links)" when it attempted to boot my phone into recovery.
I am using XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-5
Any ideas why it might have failed?
Thanks
jwreidmoto said:
First of all thanks for your hard work. I was really happy to see your post. I have followed the instructions exactly and I got "Failed (too many links)" when it attempted to boot my phone into recovery.
I am using XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-5
Any ideas why it might have failed?
Thanks
Click to expand...
Click to collapse
That's the same one I'm trying to use, tried the dtbo from the same firmware got the same results. Possible EU/Canada firmware as the screenshot of the phone that was shared is in celcius
This is how i boot this recovery successfully
daftshanks said:
That's the same one I'm trying to use, tried the dtbo from the same firmware got the same results. Possible EU/Canada firmware as the screenshot of the phone that was shared is in celcius
Click to expand...
Click to collapse
step 1 fastboot flash dtbo dtbo.img
s000.tinyupload. com/download.php?file_id=26286860633744490329&t=2628686063374449032989765
step 2
fastboot boot "recovery above"
s000.tinyupload. com/download.php?file_id=24332259722784445351&t=2433225972278444535138860
noslen7 said:
step 1 fastboot flash dtbo dtbo.img
s000.tinyupload. com/download.php?file_id=26286860633744490329&t=2628686063374449032989765
step 2
fastboot boot "recovery above"
s000.tinyupload. com/download.php?file_id=24332259722784445351&t=2433225972278444535138860
Click to expand...
Click to collapse
I appreciate your reply on this. However the dtbo filebyou provided is about 3/5ths of the dtbo from my stock firmware, normally they would be at least close to the same file size. Can I ask you what firmware you are on? And were you able to permanently install TWRP? Possible root?
Downloaded dbto.img got same result
I downloaded the above dbto.img and flashed it instead of my own stock dbto.img and got the same result when I tried to boot from recovery - Failed ( too many links). I think the recovery IMG is not working for our Canadian ROM edition.
anybody with XT1952-1 RETEU reading this here, you can help!
https://forum.xda-developers.com/showpost.php?p=79655902&postcount=5
Which dtbo.img to use? In the download area you only have the image of recovery
HOW TO USE:
Reboot to fastboot
Flash the dtbo with fastboot flash dtbo dtbo.img
After that boot from the recovery with fastboot boot recoveryname.img
dbto.img
That was in response to another query. I used my own dbto.img from my stock ROM. That part flashes fine it's the recovery.img that comes back with " failed( too many links) I have a Canadian phone.
Flashing dtbo.img will erase the smartphone data? Will I lose app data?
thank you
it worked for me fine it did give me some problems when i tried booting direct so i flashed to boot then went to recovery mode thru bootloader menu and it worked once in twrp i installed the original boot.img and im good.
Yo I'm coming from the g6 play forum with a quick question. Does this by chance work with the same current root method for the g6 play which is booting in twrp and formatting data to decrypt it then flashing twrp and flashing through twrp the encryption disabler zip then flashing magisk. If someone is able to confirm that I can possibly try to make a decent guide for you guys. We don't have a offical twrp that decrypts on its own and the twrp we have ain't a dirty port so I know there may be some differences when it comes to twrp related issues but it's better than nothing lol
ninjakira said:
Yo I'm coming from the g6 play forum with a quick question. Does this by chance work with the same current root method for the g6 play which is booting in twrp and formatting data to decrypt it then flashing twrp and flashing through twrp the encryption disabler zip then flashing magisk. If someone is able to confirm that I can possibly try to make a decent guide for you guys. We don't have a offical twrp that decrypts on its own and the twrp we have ain't a dirty port so I know there may be some differences when it comes to twrp related issues but it's better than nothing lol
Click to expand...
Click to collapse
There is one significant difference (as it regards rooting) between the Moto G6 Play and the Moto G7 Play. The G7 Play uses the A/B partition index while the G6 Play uses a standard GPT index. The current dilemma with root for the G7 Play involves the A/B partition config. Developer topjohnwu has been notified of this issue on the Magisk support thread, and has stated that he is working on a resolution at present.
Viva La Android said:
There is one significant difference (as it regards rooting) between the Moto G6 Play and the Moto G7 Play. The G7 Play uses the A/B partition index while the G6 Play uses a standard GPT index. The current dilemma with root for the G7 Play involves the A/B partition config. Developer topjohnwu has been notified of this issue on the Magisk support thread, and has stated that he is working on a resolution at present.
Click to expand...
Click to collapse
There has to be more to it than this. There are plenty of devices using A/B partitioning that can be rooted with Magisk. As far as I know, Magisk has supported A/B since version 17.1. Reading through the threads it sounds like more a TWRP problem than a Magisk one.
Has anyone tried patching boot_a and boot_b with Magisk and flashing both at once?
Spaceminer said:
There has to be more to it than this. There are plenty of devices using A/B partitioning that can be rooted with Magisk. As far as I know, Magisk has supported A/B since version 17.1. Reading through the threads it sounds like more a TWRP problem than a Magisk one.
Has anyone tried patching boot_a and boot_b with Magisk and flashing both at once?
Click to expand...
Click to collapse
You try and let's us know
Fdraco10 said:
You try and let's us know
Click to expand...
Click to collapse
I don't have the device otherwise I would. That's why I'm asking if anyone has tried it yet.
Spaceminer said:
I don't have the device otherwise I would. That's why I'm asking if anyone has tried it yet.
Click to expand...
Click to collapse
Yes. I patched both boot_a and boot_b with Magisk v19.3. My device booted into the OS with no problems at all, yet Magisk Manager indicates that root is not installed. Topjohnwu has been notified of the root issue with the Moto G7 Play, and has stated on the Magisk support thread that he is looking into a resolution. It's not a TWRP issue at this point because there is no unofficial or official TWRP for the G7 Play as of yet. Like you, I fully agree this is a bizarre issue. Root strategies which are working on the Moto G7, G7 Power & G7 Plus are not working on the G7 Play. Although Magisk has certainly supported A/B devices for some time now, no universal root method is completely infallible. There are many devices -- both A/B and standard GPT -- that encounter problems with Magisk from time to time. Luckily for the Android community, topjohnwu works hard on resolving any known issues like the one at hand.
Viva La Android said:
Yes. I patched both boot_a and boot_b with Magisk v19.3. My device booted into the OS with no problems at all, yet Magisk Manager indicates that root is not installed. Topjohnwu has been notified of the root issue with the Moto G7 Play, and has stated on the Magisk support thread that he is looking into a resolution. It's not a TWRP issue at this point because there is no unofficial or official TWRP for the G7 Play as of yet. Like you, I fully agree this is a bizarre issue. Root strategies which are working on the Moto G7, G7 Power & G7 Plus are not working on the G7 Play. Although Magisk has certainly supported A/B devices for some time now, no universal root method is completely infallible. There are many devices -- both A/B and standard GPT -- that encounter problems with Magisk from time to time. Luckily for the Android community, topjohnwu works hard on resolving any known issues like the one at hand.
Click to expand...
Click to collapse
I read the responses in his thread about that, and it seems like you guys aren't getting root without a working TWRP. The problem that was laid out, is that fastboot can't patch existing files, it can only overwrite them. Without a custom bootloader, Magisk would never be able to patch existing files through fastboot.
Personally, I think that's a very sh*tty position to be in, and I want to help you guys out. If you or anyone else wants to upload your most recent boot.img, it'll save me some time. I'm not too familiar with the A/B partition setup, but I am very familiar with TWRP. I think that I can get it working for you folks. I will make this happen or break my brain trying. No phone with an unlockable bootloader should go unrooted! Thank you for answering my question by the way. That's one less thing to troubleshoot.
I just want to confirm a few things before I get to work.
Is your base model number xt1952?
Is your code name Channel?
Where is the current TWRP hacked from? (Moto G7, G7 Power, G7 Plus?) - Moto G7. I found it in the OP.
And are you guys arm32 or arm64?
Related
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
What are you talking about? Before unlocking have you checked OEM unlocking from Developer tools? After this you need to flash Twrp, boot into it directly from bootloader and flash SUPERSU. That should be the minimal steps in order to keep the custom recovery in place.
HaiKaiDo said:
So I just got my nexus 5x and it looks like I cant just do the simple fastboot oem unlock and then flash twrp image, which makes me sad (I thought unlocking your phone was pretty much a red flag for "im going to do things to you" so why all the new "security" measures?). Since I'm on the latest update MHC19J, and it seems a modified boot image is not available (unless Im just overlooking it) am I just kinda stuck at the moment until said image is available? (sans the "yeah you could just modify one yourself" comment).
Click to expand...
Click to collapse
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
You do need some knowledge so take a look at the howto conversation http://forum.xda-developers.com/showthread.php?t=3206930
, this is my go to tool since my Nexus 4 http://forum.xda-developers.com/showthread.php?t=3258492
Darke5tShad0w said:
There is a guide and a sticky roll up that have had a lot of time spent writing up with all this info in them.
Supersu modifies the image itself.
Click to expand...
Click to collapse
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
HaiKaiDo said:
I should have included in my post that Im only seeking help after reading everything I could find and still being at a loss. Perhaps i misunderstood the directions, or maybe the fact that Im not looking to root my device, only flash twrp and move to a custom rom right away, that Ive overlooked a step as ive ignored all the rooting steps.
So this guide says to just unlock your device (i have) and then just run fastboot flash recovery twrp.img (also did this) and I should be good (it didnt work, it gave me that warning screen).
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This guide looks slightly different:
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
1]Unlock bootloader- fastboot oem unlock [select yes by pressing volume up and then power button to confirm]
2] Reboot & skip everything in setup as we data will be wiped again!
3] Reboot into bootloader & flash the modified boot image- fastboot flash boot boot.img (This is the part that im asking about as there doesnt appear to be a modified image for me to flash)
4] Reboot into system to make sure it's booting properly! [May not be necessary!]
5] Reboot into bootloader again & flash twrp- fastboot flash recovery "recovery name".img
This is really what I want to achieve. Disabling Encryption and flashing TWRP so I can flash a custom rom. Not interested in the slightest about rooting a stock rom.
So thats where im stuck,no worries, I did attempt to RTFM :]
Click to expand...
Click to collapse
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
wtoj34 said:
You're not following the right guide. You don't have to bother with encryption, just use the latest twrp after unlocking the bootloader and flash that IMG file in fastboot. Twrp works with encryption now you don't have to decrypt
Use this guide and follow steps one and two http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
HaiKaiDo said:
Thanks for the reply. I wonder what went wrong the first time though. Cause i did unlock the bootloader, rebooted and let android load, rebooted into bootloader and flashed twrp 3.0.0.0 and it gave me a weird "cannot be verified" message when I tried to boot into recovery.
Click to expand...
Click to collapse
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
wtoj34 said:
That happens on Nexus phones. Just give it a second and it'll boot up. It's just a warning telling that you unlocked the bootloader. Make sure you're using the very latest version of twrp available in the site, it ends in a 1 I believe
Click to expand...
Click to collapse
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Well i went and redid everything the same way I did the first time and it worked! I must done something stupid the first time. Guess this thread was for nothing! xD Thanks for clarifying some things for me though guys.
HaiKaiDo said:
Ahh ok, thanks for info. I think ill run the flash back to stock and give it a fresh try. Is there any plus to being un-encrypted btw?
Thanks again!
Click to expand...
Click to collapse
Disabling encryption does give you a speed increase. It may or may not be noticeable for your use but the majority can see the difference.
So you have to decide between security and a snappier phone.
Just remember to back all your data up as this requires wiping your data and possibly a clean flash and either switching from the stock rom to another rom(Most have the forced encryption disabled) or when on stock rom either flash another kernel or flash supersu in systemless mode.
Hotspot need it Help! Nexus 5x
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Varsismaname said:
Ok, so I have a Nexus 5 and a Nexus 5X. I want to keep the Nexus 5x because has more features, but I cannot share the data from my provider cricket wireless (AT&T).
I have the option to return it or find a solution. I am pretty stubborn which means FIX IT. I have the March 1 2016 Update and this MHC19J shows up in the build version... I am under linux, last time I did this was well long time since 2013 for the nexus 5. Can some one help me with a guide for linux.
THANKS A LOT!!!
Click to expand...
Click to collapse
You need to go and start your own thread in the q&a section, its not polite to high jack someone else's.
Hi,
Everybody is looking for official stock roms for Moto G4/G4 Plus *AWAY* from Motorola support, which looked to me like kind of weird but I now know why: people are looking for stock roms that will allow them over the air upgrades. If you have a developer edition or a moto with unlocked bootloader, Moto's own roms are flashable and *COMPLETELY WORKING*
motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Go to above URL, quick login using G+, follow instructions to get to the download list. The listed download for XT1625 will also work just fine for XT1642.
Or, you can just use this direct link: motorola-global-portal.custhelp.com/cc/ajaxCustom/getBootFile/fileName/ib65qpz53y
may also require login.
******** VERY IMPORTANT ************
Everybody lists fastboot utility commands with which you restore a Moto stock rom. They do not tell these severe warnings:
- Never flash a gpt.bin file unless you really absolutely ultimately intentionally and knowingly NEED TO. Why? in 99.9% of the cases it is useless to your phone and your needs and all it will do is deprive you the ability to downgrade to an earlier version or flash an older boot file, system file, ...etc. You get the picture. BTW, gpt.bin is only a partition image containing Moto's partition table scheme, with versioning for downgrade prevention. Keep away from it. It is pure EVIL.
IF YOU SEE gpt.bin FILE, DELETE IT WITHOUT HESITATION.
- Our second vanity: bootloader.img or bootloader.bin or anything that spells BOOTLOADER. EVIL. DELETE IT. It will 99.9% only mess up your cellular capability and render your phone without voice calls, with out SMS and without 2G/3G/4G; no data whatsoever. It will convert your phone into a 5.5 inch SIM-less tablet. It will KILL YOUR SIM SLOTS.
Instruction are on the first link, but anyway, here we go:
To flash, put the phone in fastboot mode:
1. Power OFF your device
2. Then Power ON + Volume Down Alternatively, you can reboot into fastboot mode if you have adb...
adb reboot bootloader.
Next flash the images using fastboot:
Code:
"DELETED COMMAND HERE WAS SUPPOSED TO FLASH THE GPT.BIN. NEVER DO IT"
"DELETED COMMAND HERE WAS SUPPOSED TO FLASH THE BOOTLOADER. NEVER DO IT"
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
enjoy
****removed****
MK+2017 said:
****removed****
Click to expand...
Click to collapse
I would like back to MM from Nougat on XT1642. This firmware comes from a trusted source, but have you tried this firmware, no problems after flashing? Do I have to have an unlocked bootloader ?
kkamelot said:
I would like back to MM from Nougat on XT1642. This firmware comes from a trusted source, but have you tried this firmware, no problems after flashing? Do I have to have an unlocked bootloader ?
Click to expand...
Click to collapse
if you have not unlocked boot-loader you are covered by warranty and I advise you keep it that way. Motorola is a BI***.
if you really can't live without older stock, go to moto service and ask them to do it for you. should not cost you much, if any.
if what you hate is stock firmware, you can unlock bootloader, get warranty off, and flash LinageOS. Stable enough although still in nightly builds (successor of CyanogenMod)
hope that helps.
PS1: what you would fear the most is lose your SIM slot, happens a lot. Be safe!
PS2: asking if I tried it yes, I did. it worked. but I was on 6.0.1 at the time. do not take risk.
PS3: Motorola is a *****. DON'T MESS WITH IT.
MK+2017 said:
if you have not unlocked boot-loader you are covered by warranty and I advise you keep it that way. Motorola is a BI***.
if you really can't live without older stock, go to moto service and ask them to do it for you. should not cost you much, if any.
if what you hate is stock firmware, you can unlock bootloader, get warranty off, and flash LinageOS. Stable enough although still in nightly builds (successor of CyanogenMod)
hope that helps.
PS1: what you would fear the most is lose your SIM slot, happens a lot. Be safe!
PS2: asking if I tried it yes, I did. it worked. but I was on 6.0.1 at the time. do not take risk.
PS3: Motorola is a *****. DON'T MESS WITH IT.
Click to expand...
Click to collapse
Thank you for your answer !
I have one more question, is there way (like in nexus) to back to original software (Nougat can be) after changing OS or make a modifications?
kkamelot said:
Thank you for your answer !
I have one more question, is there way (like in nexus) to back to original software (Nougat can be) after changing OS or make a modifications?
Click to expand...
Click to collapse
There is, but if you are not good with command line, think twice. Check here: https://forum.xda-developers.com/moto-g4-plus/help/complete-partition-backup-script-xt1644-t3608408
you would typically use that alongside full TWRP backup.
I can assure you nothing will go wrong if you jump straight to LineageOS, it might only go wrong if you take the bad decision of going back to stock. The dd images would give you solid backup, though.
In case you lose your sim slot, you can use help from here: https://forum.xda-developers.com/showpost.php?p=72343095&postcount=101
I intuitively contributed to that solution Giving is taking!
Thank you @m.sawastik and @givitago
MK+2017 said:
There is, but if you are not good with command line, think twice. Check here: https://forum.xda-developers.com/moto-g4-plus/help/complete-partition-backup-script-xt1644-t3608408
you would typically use that alongside full TWRP backup.
I can assure you nothing will go wrong if you jump straight to LineageOS, it might only go wrong if you take the bad decision of going back to stock. The dd images would give you solid backup, though.
In case you lose your sim slot, you can use help from here: https://forum.xda-developers.com/showpost.php?p=72343095&postcount=101
I intuitively contributed to that solution 😊Giving is taking!
Thank you @m.sawastik and @givitago
Click to expand...
Click to collapse
I would also be happy to assist you if you want to jump to LineageOS. I won't assist you with dd backup, just because you need to take that responsibility on your own
My XT1625 is already on Lineage OS Andriod N. However, I feel like the cellular reception and thus battery life has been worse versus stock.
I wanted to flash only the latest baseband from the latest stock Andriod N but your Moto link only has 6.0.1 for XT1625.
What gives- I thought Motorola already updated the G4 to 7.0?
Will OTAs work with this?
Will OTAs work with these?
If I just want to upgrade my modem/baseband and then go back to LOS, do I just need to type "fastboot flash modem NON-HLOS.bin" or do I need to make a full install?
it works for moto g4 t1625 amazon version?? compilation number npj25.93-14.5 ?????? i answer this because in the web site motorola its appear the moto g4 rom xt1625 build MPJ24.139-64
Works!
I just want to say that I had a Moto G4 Plus (XT1642) that had no SIM recognition, no IMEI, no Wifi, and thanks to the instructions at the top of this thread, I now have it all.
I spent the whole day trying all sorts of things. Now it finally works!
Thanks!
How do I flash?
Hi friend, sorry but my English is not good.
My phone will receive nougat via OTA?
Something has broken my sound notifications
When I try this procedure I get a lot of these errors against some of the commands
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) will fail: flash:aboot
FAILED (remote failure)
And now sounds that accompany any notifications from any applications fail to make any sound. Vibrate does initiate.
I am trying to find a way to enable hotspot on my ATT Moto G4 plus, if I flash this rom can anyone confirm it will unlock this feature? Torn between flashing or just going in to kernel and make change for this feature, any advice appreciated..
how to restore the sim slot after flash( i have no service)
i had frp, and after remove it with 3rd party tool i flash new rom.
now i have no service(but it detect the sim), there is any way to restore the sim slot?
i flashed the original rom from motorola site and it didnt help.
i flash the lineage OS and it didnt helped.
thanks
ggc201 said:
there is any way to restore the sim slot?
Click to expand...
Click to collapse
I've been searching for a fix for a few months now, whenever I get free time. Most threads about the subject die and aren't revisited. Someone will inevitably come to this page on a Google search wondering like us. I haven't found anything that will help and so I'm calling it quits. This phone is so outdated it would be better suited to find a deal somewhere else.
Thanks... can't find the button.
I have the xt1625 amz channel version and the: XT1625-XT1644_ATHENE-RETUS_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip > provided enhanced LTE whereas the official OS did not support. I can actually do sh** on my phone without hanging up.
I want you and yours to be blessed forever and great post.
Bootloader is unlocked but somehow it is stuck between root and no root. Will figure it out....
Again... thanks... this is a big deal for me. :good:
non-developer edition?
If you have a developer edition or a moto with unlocked bootloader, Moto's own roms are flashable and *COMPLETELY WORKING*
Click to expand...
Click to collapse
Can anyone attest to having successfully flashed an unlocked non-developer edition G4 with this ROM? Motorola clearly warns against doing this:
IMPORTANT! Do not use these images/packages on non-developer edition devices or on devices with a locked bootloader.
Click to expand...
Click to collapse
(sorry, I'm a new member so I'm not allowed to include a link)
Hi, i like to know the prevention for Moto g5.so I can't able to brick my device again. thanks in advance
Don't flash recoveries, kernels or ROMs that are not suitable for your phone. However, in some cases mentioned above, phone will start. This is also related to other Android phones, not just Moto G5. An exception is if your device support Treble (Moto G5 does since today). Then, you can flash any ROM WITH TREBLE SUPPORT AND PARTITIONING CORESPONDING TO YOUR DEVICE - A ONLY or A/B.
Don't even try to flash stock firmware with older security patch than you have currently installed - everything except gpt and/or bootloader will flash because of preflash validations. Corrupted or missing gpt/bootloader will end up in hardbricked device.
Even, there's already a tutorial for fixing hardbricked G5 (by booting off from sdcard), it may, but also may not work for you. Always be careful of what you are flashing to avoid situations that are difficult to fix.
Andrej_SK said:
Don't flash recoveries, kernels or ROMs that are not suitable for your phone. However, in some cases mentioned above, phone will start. This is also related to other Android phones, not just Moto G5. An exception is if your device support Treble (Moto G5 does since today). Then, you can flash any ROM WITH TREBLE SUPPORT AND PARTITIONING CORESPONDING TO YOUR DEVICE - A ONLY or A/B.
Don't even try to flash stock firmware with older security patch than you have currently installed - everything except gpt and/or bootloader will flash because of preflash validations. Corrupted or missing gpt/bootloader will end up in hardbricked device.
Even, there's already a tutorial for fixing hardbricked G5 (by booting off from sdcard), it may, but also may not work for you. Always be careful of what you are flashing to avoid situations that are difficult to fix.
Click to expand...
Click to collapse
Thans for replying. If I flash the device without using gpt/or bootloader codes (in case of using old firmware).then my device will not get bricked.is it right.
riyan65 said:
Thans for replying. If I flash the device without using gpt/or bootloader codes (in case of using old firmware).then my device will not get bricked.is it right.
Click to expand...
Click to collapse
It won't get hard bricked because you are not changing the boot partitions or bootloader so you will be able to access fastboot
Your phone may not boot (for example if a kernel requires a certain bootloader version) but it won't be hard bricked
TheFixItMan said:
Your phone may not boot (for example if a kernel requires a certain bootloader version) but it won't be hard bricked
Click to expand...
Click to collapse
Or for example if ROM needs certain kernel... still remember how much I was scared when I've softbricked my old Xperia X8 for the first time.
Andrej_SK said:
Or for example if ROM needs certain kernel... still remember how much I was scared when I've softbricked my old Xperia X8 for the first time.
Click to expand...
Click to collapse
Thanks for help.
My piece of advice:
DON'T ATTEMPT TO DOWNGRADE USING FASTBOOT.
More specifically: don't flash gpt/bootloader files with fastboot. When you flash an older bootloader through Fastboot or RSD Lite, you end up with a brick and you will need a blankflash file or an image dump on a Micro SD card.
Just backup everything you can and be very cautious of what you flash, better safe than sorry.
This wil be a list of firmware sources and a bit of explanation in different firmware versions and builds. This information has been gathered over the past few weeks, mainly by helping others to find the proper stock roms.
First of all, there seem to be multiple regions that have different firmware’s, and there seem to be different software channels per region or per region per provider. ( for instance vfeu vs reteu )
The phone model is XT2041-X where the X can stand for 1 to 4
The development name / moto name is called: Sofiar ( XT2041-1/3)
the development name for the US name is: Sofia ( xt2041-4 )
The easiest way to find the proper firmware would be via the Lenovo rescue and smart assistant ( LMSA)
you can download it from here: https://download.lenovo.com/consumer/mobiles/rescue_and_smart_v5.0.0.25_setup.exe
Since a few days support has been added to rescue the g8 power
you can download the current firmware for your device via the rescue page.
Manual selection of firmware sources:
So far, every source on the internet points to the lolinet mirror
see https://mirrors.lolinet.com/firmware/moto/sofiar/official/
US version: https://mirrors.lolinet.com/firmware/moto/sofia/official/
a 2nd source would be the moto updates tracker, but I expect that everything you find here Will appear on lolinet
US: https://t.me/s/MotoUpdatesTracker?q=#sofia
The rest of the world: https://t.me/s/MotoUpdatesTracker?q=#sofiar
so far I have not been able to find any other sources. I hope this helps a bit in downloading / finding the stock firmware for your phone.
If you find any other / better source, please let me know, I'll add it to this first post.
Thanks
I successfully updated mine and regained root.
I will post manual update guide later.
A side note: the following must be flashed in fastbootd (fastboot reboot fastbootd or adb reboot fastboot)
boot.img, recovery.img, vbmeta.img, super, dtbo.img
@mingkee Pls can you share manual update guide? THX
endva3 said:
@mingkee Pls can you share manual update guide? THX
Click to expand...
Click to collapse
There's a simple method using LMSA rescue method, but make sure you backup your phone because your phone will be wiped during the process.
Hi, I'm running into a little problem. I used the lolinet link to download the factory ROM for my Moto G Power (Best Buy unlocked, on Verizon). I downloaded the sofia VZW factory ROM first (thinking because I'm on Verizon). I used Magisk to patch the boot.img and fastbooted it. After reboot, I lost the touch screen and cell service -- could not unlock the phone. So I thought no big deal, I'll just reflash the unpatched boot.img from the sofia retus ROM this time. However, I still do not have touch screen. Does anyone have the factory boot.img for QPM30.80.50-1 that originally came with this G Power? Thanks in advance.
quangtran1 said:
Hi, I'm running into a little problem. I used the lolinet link to download the factory ROM for my Moto G Power (Best Buy unlocked, on Verizon). I downloaded the sofia VZW factory ROM first (thinking because I'm on Verizon). I used Magisk to patch the boot.img and fastbooted it. After reboot, I lost the touch screen and cell service -- could not unlock the phone. So I thought no big deal, I'll just reflash the unpatched boot.img from the sofia retus ROM this time. However, I still do not have touch screen. Does anyone have the factory boot.img for QPM30.80.50-1 that originally came with this G Power? Thanks in advance.
Click to expand...
Click to collapse
You may have patched unmatched build number.
Solution: flash full ROM
LMSA rescue is the simplest method but it will wipe the phone
Thanks! That was what I ended up doing.
Is it possible to change fw xt2041-3 (PAHF0004PL) to XT2041-3 (PAHF0006GB)? I'm on the PL version (andoid security January 2020) and the GB version is May 2020. If possible, the bootloader must be unlocked? Can it be changed via any tool (mototool) or via adb commands?
Anyone have the boot.img for QPMS30.80-51-3?
I cant download the latest May update from their server. Some reason the link to download expired a few days after. So if anyone has another link or can just hook it up with the boot.img please
I couldnt get it with the rescue app either it was a lower version.
EDIT
Found it here
https://forum.xda-developers.com/showpost.php?p=82865201&postcount=73
Some lessons learned
pjottrr said:
The easiest way to find the proper firmware would be via the Lenovo rescue and smart assistant ( LMSA)
you can download it from here: https://download.lenovo.com/consumer/mobiles/rescue_and_smart_v5.0.0.25_setup.exe
Since a few days support has been added to rescue the g8 power
you can download the current firmware for your device via the rescue page.
Click to expand...
Click to collapse
In my case, you in fact cannot exactly download the "current" firmware via the rescue page - the phone's updater app thinks QPM30.80-51-3 is the latest version, but the rescue app installs the newer QPM30.80-109. Both are 5/1/2020 security patch level, but the boot.img files are most certainly not interchangeable.
I ended up in a bootloop which I had to rescue the phone to escape. I'd advise anyone wanting to root this phone to just rescue it first.
Also it's essential that you install the Motorola Device Manager/USB drivers in addition to LRSA, otherwise LRSA will incorrectly insist your phone is not in fastboot flash mode if you have to resort to rescuing from fastboot mode.
Finally, the rescue process will not work from a Windows VM under KVM, whether you have the USB device redirected or shared with the host. You need Windows running on bare metal.
Hope this saves someone the hours of annoyance I just went through trying to unbrick the damn thing.
Can jump from a carrier Rom to a unlocked version? And if yes, what's the unlocked phone rom? Cause I only see carrier versions.
Mikael1013 said:
Can jump from a carrier Rom to a unlocked version? And if yes, what's the unlocked phone rom? Cause I only see carrier versions.
Click to expand...
Click to collapse
Switching from a carrier rom to an unlocked version won't SIM unlock a phone (at least not to my knowledge), if that's your objective. But if you're looking to switch the retail flavor rom, try RETUS, specifically XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
rlrevell said:
In my case, you in fact cannot exactly download the "current" firmware via the rescue page - the phone's updater app thinks QPM30.80-51-3 is the latest version, but the rescue app installs the newer QPM30.80-109. Both are 5/1/2020 security patch level, but the boot.img files are most certainly not interchangeable.
I ended up in a bootloop which I had to rescue the phone to escape. I'd advise anyone wanting to root this phone to just rescue it first.
Also it's essential that you install the Motorola Device Manager/USB drivers in addition to LRSA, otherwise LRSA will incorrectly insist your phone is not in fastboot flash mode if you have to resort to rescuing from fastboot mode.
Finally, the rescue process will not work from a Windows VM under KVM, whether you have the USB device redirected or shared with the host. You need Windows running on bare metal.
Hope this saves someone the hours of annoyance I just went through trying to unbrick the damn thing.
Click to expand...
Click to collapse
Also a good word of advice before flashing a boot.bin
run the command
fastboot boot boot.bin
or whatever your boot.bin is called
Then you can test your patched file before patching it. Also even better once you get into Android you can open MAGISK and use direct install
TNS201 said:
Also a good word of advice before flashing a boot.bin
run the command
fastboot boot boot.bin
or whatever your boot.bin is called
Then you can test your patched file before patching it. Also even better once you get into Android you can open MAGISK and use direct install
Click to expand...
Click to collapse
I've never actually had this work on any device I've tried to root. Command not implemented or some such error was always the result. Does it work for you on this device?
The download link for the latest Google Fi firmware works again if anyone wants to grab it before it expires...again heh.
SOFIA_RETAIL_QPMS30.80-51-3
CodyF86 said:
The download link for the latest Google Fi firmware works again if anyone wants to grab it before it expires...again heh.
SOFIA_RETAIL_QPMS30.80-51-3
Click to expand...
Click to collapse
Do you have stock boot IMG by any chance? Thx in advance
freddienuxx said:
Do you have stock boot IMG by any chance? Thx in advance
Click to expand...
Click to collapse
sofia_80-51-3boot.img
CodyF86 said:
sofia_80-51-3boot.img
Click to expand...
Click to collapse
Thx man
rlrevell said:
I've never actually had this work on any device I've tried to root. Command not implemented or some such error was always the result. Does it work for you on this device?
Click to expand...
Click to collapse
yea when you are in bootloader with phone attached to the PC it should work
It worked on my pixel 2 xl and this phone
Does anybody have this file available? (Sorry for the spaces, I can't post a link...). The download link has expired.
t.me /motoupdatestracker/ 2752
filename: SOFIA_RETAIL_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
What's the difference between that and RETUS on lolinet? Is there any? Reason I'm asking is that I don't have any radios after that OTA (Google Fi) and flashing the boot.img from RETUS QPMS-30.80-51-5.
I think I understand the idea behind the device-specific Treble system, and the device-agnostic GIS images, which can work on any phone that has Treble. The app "Treble Check" says that the Sony Xperia 10 III is fully supported.
Here's my questions / educated guesses, please tell me if they're wrong or right:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
wirespot said:
1. This phone already comes with a Treble-compliant hardware layer (kernel+drivers) and GSI-compliant user-facing ROM, directly from Sony.
Click to expand...
Click to collapse
Yes.
wirespot said:
2. I can install any other GSI ROM (or from XDA) as long as it's an A/B arm64 ROM, and the hardware should work perfectly.
Click to expand...
Click to collapse
In theory. In practice it still depends on how the GSI ROM was implemented, there can still be issues.
wirespot said:
3. Can the phone still get OTA vendor updates for the hardware stuff after I unlock bootloader/install 3rd party GIS, or do I have to get the new images and flash them manually? Or do I get cut off from them altogether?
Click to expand...
Click to collapse
Not totally sure about this one. I think you don't get to install OTA updates anymore. You can probably download a new firmware with XperiFirm and flash pieces of it but no idea how that would work or what would happen.
wirespot said:
4. The original bootloader can take commands from the standard fastboot util in the Android SDK Platform Tools.
Click to expand...
Click to collapse
Yes. Sony did a great job going for standard things.
wirespot said:
5. I understand I need to unlock the bootloader in order to be able to flash anything, but why is it necessary to overwrite the vbmeta partition?
Click to expand...
Click to collapse
The original vbmeta partition contains a mechanism that checks for the other partitions to not be modified. The image downloaded from Google disables that mechanism, so you can put whatever you want on any partition.
wirespot said:
6. Is the procedure to get Magisk working still patching the bootloader, regardless what GSI ROM I install?
Click to expand...
Click to collapse
Yes, it's for the best. A large amount of what Magisk does is based on it being "hidden" from the regular system. Not just for hiding from SafetyNet, since you may not care about that with a 3rd party GSI ROM, but because keeping system modifications separate and keeping the original ROM is a very, very good practice.
wirespot said:
7. Did anybody pass Safety Net with Magisk and a 3rd-party GIS ROM? Can it be passed anymore after unlocking bootloader?
Click to expand...
Click to collapse
You can pass SafetyNet on the stock ROM, with unlocked bootloader and boot image patched to load Magisk. See my how to guide. I don't know about 3rd party GIS ROMs.
wirespot said:
8. I see there's no TWRP recovery for this device. Does it matter? Are there alternatives? In theory, if I have Magisk->root I can do pretty much anything so it doesn't sound like a big deal.
Click to expand...
Click to collapse
I've looked into this some more. The biggest downsides seem to be inability to restore backups of the userdata, and inability to disable problematic Magisk modules. There are modules such as Magisk Bootloop Protector which will disable all modules if it detects a bootloop, but if the problem is not a bootloop and still prevents your access you're out of luck...
Please feel free to add more info.