Here it is most awaiting fastboot rom file...
https://drive.google.com/folderview?id=1NR--EZXzMCzbKT0GCBp3gKbp5TrU_ImE
POTTER_RETAIL_8.1.0_OPS28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
fastboot commands
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
if you ever played with your persist, its not fixing those persist who flashed other device persist to gain IMEI and VoLTE, safe for those who never played with their persist and for those who are having baseband with ending with capital R. Direct flashing via fastboot ending with no signals and also not imei if dont skip erase modemst1
erase modemst2.
Guide for those who are not on their own persist but with another persist able to use Signals with volte and using any custom or nougat or twrp rom
first take backup of your current working efs and persist on sd card or otg
Thn flash above rom via fastboot, dont skip anything, reboot system thn again go in fastboot menu
Flash twrp, thn in twrp only flash only FIRMWARE from SOAK Test 1 Aroma by @NZedPred ( https://www.androidfilehost.com/?fid=1322778262903990826 ), Thanks @NZedPred for his great work, now restore your efs and persist, roboot system.
If you want to lock bootloader thn follow these commands in fastboot
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash boot boot.img
fastboot oem lock
All of these worked for me as I was also not on my own persist.
everything working fine CAMERA, VOLTE, WIFI, FINGERPRINT, locked bootloader and unlocked also again with my key tht provided by moto, battery also charging faster, battery backup is also good.
Hey, will this work for hard bricked users? I've been using twrp flashable nougat stock ROMs since last year! Can't get back to full stock so!
irfanalinawaz said:
Here it is most awaiting fastboot rom file...
https://drive.google.com/folderview?id=1NR--EZXzMCzbKT0GCBp3gKbp5TrU_ImE
POTTER_RETAIL_8.1.0_OPS28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
fastboot commands
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
skip
fastboot erase modemst1
fastboot erase modemst2
if you ever played with your persist, its not fixing those persist who flashed other device persist to gain IMEI and VoLTE, safe for those who never played with there persist and for those who are having baseband with ending with capital R.
For those who played with their persist, there are IMEI but no network after restoring EFS and Persist backup with TWRP, so be careful.
Click to expand...
Click to collapse
With ota instalation my radio say is off....with the fastboot And jumping erase modems... Rádio Will work?
Same quesrion but nomore but to try anyways
LLegion said:
Same quesrion but nomore but to try anyways
Click to expand...
Click to collapse
Radio will work if your Persist is intact, and you never flashed others persist to gain imei and volte otherwise there are no signal. I have tried all the methods but stll working on it, let see...hope.
irfanalinawaz said:
Radio will work if your Persist is intact, and you never flashed others persist to gain imei and volte otherwise there are no signal. I have tried all the methods but stll working on it, let see...hope.
Click to expand...
Click to collapse
Tried put Oreo with one sim card only?
Another devices doing this work to get radio ?
david.gs.gm said:
Tried put Oreo with one sim card only?
Another devices doing this work to get radio ?
Click to expand...
Click to collapse
I have tried something different I was able to gain network with volte but signals are not stable they coming and going, anyways it will take time, nothing is impossible here, I am also one from those who messed up thier Persist, and I am working on it.
irfanalinawaz said:
Radio will work if your Persist is intact, and you never flashed others persist to gain imei and volte otherwise there are no signal. I have tried all the methods but stll working on it, let see...hope.
Click to expand...
Click to collapse
help me out with an issue about retail or my software channel is retin should this version is good for me to install my build number is NPNS25.137-92-14 and I already got OTA update but my persists is not mine what should I do
This means TWRP flashable is on its way.:good:
devvshukla said:
I got some errors while sending these two commands, device is working regardless of these errors.
Which are these command and whats they do? Also what issues I might be facing on future because of this?
Commands -
fastboot erase customize
fastboot erase clogo
Click to expand...
Click to collapse
These commands are not nessecery, ignore them and proceed. These commands will not affect any future ota or update.
livyansh said:
help me out with an issue about retail or my software channel is retin should this version is good for me to install my build number is NPNS25.137-92-14 and I already got OTA update but my persists is not mine what should I do
Click to expand...
Click to collapse
Bro you need to avoid this to flash, right now there is not any solution for those who are not on their persist, you will end up with no signals. So wait, I am still working on it.
rajeshkoshti said:
This means TWRP flashable is on its way.:good:
Click to expand...
Click to collapse
We already have that from beta. The latest beta was same as official release.
livyansh said:
help me out with an issue about retail or my software channel is retin should this version is good for me to install my build number is NPNS25.137-92-14 and I already got OTA update but my persists is not mine what should I do
Click to expand...
Click to collapse
After upgrading to oreo, download the Oreo flashable zip (Aroma) of SOAK1 and install only the firmware. And restore your efs after this step.
My phone is working perfectly with this, no network issues.
irfanalinawaz said:
Bro you need to avoid this to flash, right now there is not any solution for those who are not on their persist, you will end up with no signals. So wait, I am still working on it.
Click to expand...
Click to collapse
okay, bro, I am waiting just let me know whenever you find out any solution about VOLTE or no network issues
antojamez said:
After upgrading to oreo, download the Oreo flashable zip (Aroma) of SOAK1 and install only the firmware. And restore your efs after this step.
My phone is working perfectly with this, no network issues.
Click to expand...
Click to collapse
There are also many hidden issues after this method, wifi is getting slow while Bluetooth is active, if Bluetooth inactive thn also there are frequent wifi disconnection. Fingerprint also getting so slow while screen is off, I already tested it.
devvshukla said:
I got some errors while sending these two commands, device is working regardless of these errors.
Which are these command and whats they do? Also what issues I might be facing on future because of this?
Commands -
fastboot erase customize
fastboot erase clogo
Click to expand...
Click to collapse
Hey I also got that errors after few time my device got hard bricked.
riyan65 said:
Hey I also got that errors after few time my device got hard bricked.
Click to expand...
Click to collapse
These commands are not responsible for hard bricks, may be there are another reason for hard bricks.
Asking again...
Will this work for hard bricked users? I've been using twrp flashable nougat stock ROMs since last year! Can't get back to full stock so!
roydhritiman said:
Asking again...
Will this work for hard bricked users? I've been using twrp flashable nougat stock ROMs since last year! Can't get back to full stock so!
Click to expand...
Click to collapse
First post your fastboot getvar here, then tell me what is the condition of your persist, imei, volte etc. Also from fatboot menu take a pic and post them also, and describe how you recovered your hard bricked device, then we can explain you. Thanks.
irfanalinawaz said:
Bro you need to avoid this to flash, right now there is not any solution for those who are not on their persist, you will end up with no signals. So wait, I am still working on it.
Click to expand...
Click to collapse
but I got the OTA update on my phone to download and I did that but I am the little bit afraid to install it just because of VOLTE and IMEI
Related
hi, i have a big problem with my device, few day ago i installed twrp and root but then i needed to restore, for mistake did a wipe advance and root again and my devices bootloop, i did restore with the firmware stock but the version baseband show me something different, must be m8953_10208.08.04.47R but have m8953_10208.08.04.47e and my imei show "0".
i try flash with other firmware but all version baseband finish with the letter "e", i can´t call or send messages
i hope somebody can help me: (
Did you restore using commands similar to this?
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Milly7 said:
Did you restore using commands similar to this?
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
yes, i do but with all firmware show me the letter "e" 42R - 42e
Same error....
i just reflash firmware via RSD, when boot finished, it has no signal, imei shows 0 and the baseband replace the "R" letter with an "e" letter.
Before reflash firmware, i've make a backup of the EFS partition via TWRP. So i restore the backup, the devices boots with signal, shows IMEI but the baseband it's the same with letter "e"
Hardware info don't show the correct version. it shows "\x\x\x\x"
If erase the modemst1 and modemst2 via fastboot or when i reflash via RSD, it shows IMEI 0 again :crying:
I'm having the same problem but I didn't made a backup of the EFS.
My hardware info shows version "\x\x\x\x", same problem with the IMEI and baseband: M8953_1028.08.04.47e
Anyone was able to solve this problem? I'm looking for a solution for about 3 days now.
This all happened when I flashed a LATAM rom, booted with no singal, now I found my version (RETBR) and even flashing it I still boot with no signal.
same boat here lol
tried to restore EFS and nvram, fail, IMEI stay 0
I'm also having this issue due to willy-nilly flashing. I know what my IMEIs are supposed to be since they're written on the box, but I'm not sure how to get them into the phone again.
anyone could manage to fix this?
I'm still having this issue.
My brother bought another Moto Z Play exactly like mine and this is his info:
Baseband: M8953_10208.08.04.47R ADDISON_ROW_DSDS_CUST
Mine is: M8953_10208.08.04.47e ADDISON_ROW_CUST
I've got addison_row_cust. Any idea where I can find stock firmware so I can take the recent update? Bought the phone off Swappa and it came with TWRP with no backups :S
xxBrun0xx said:
I've got addison_row_cust. Any idea where I can find stock firmware so I can take the recent update? Bought the phone off Swappa and it came with TWRP with no backups :S
Click to expand...
Click to collapse
bro where you able to solve this did your bband change to letter r mine is motog5 plus i too had the same problem
Rakesh1b said:
bro where you able to solve this did your bband change to letter r mine is motog5 plus i too had the same problem
Click to expand...
Click to collapse
bro in this thread were you able to restore baseband finally.
mibonilla1103 said:
hi, i have a big problem with my device, few day ago i installed twrp and root but then i needed to restore, for mistake did a wipe advance and root again and my devices bootloop, i did restore with the firmware stock but the version baseband show me something different, must be m8953_10208.08.04.47R but have m8953_10208.08.04.47e and my imei show "0".
i try flash with other firmware but all version baseband finish with the letter "e", i can´t call or send messages
i hope somebody can help me: (
Click to expand...
Click to collapse
have you find the solution..?
if you have,please suggest that solution to us also.
i have this same problem with g5s plus. Waiting for suggest
AmNeZiS said:
i have this same problem with g5s plus. Waiting for suggest
Click to expand...
Click to collapse
Some1 fix this problem????? THx
There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.
I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.
uberano26 said:
I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.
Click to expand...
Click to collapse
I appreciate the reply. RSD doesn't detect, but ADB can. I can send fastboot commands via the bootloader, so I think drivers are OK. What got me in this mess was flashing the Chinese TWRP posted on the root guide here on XDA so I think the drivers are installed ok. I think it's a Windows thing.
I found that page you're referring to last night and read up on it. I found the retail US stock firmware image posted by another here on XDA and proceeded to go through the steps. After looking, the batch file immediately closed and did nothing. Then I went into the XML file and removed the m in mfastboot. After runnng manually, I found that it kept saying mfastboot.exe is not found. Then it went through every step as I've seen before, but every time a command was finished it would say "Image not signed or corrupt". I believe if I could somehow get RSD lite to work that I would be OK. I'd love to get this thing booting again.
uberano26 said:
I used the procedure here and it worked for me.
https://giveawaytricks.in/install-stock-rom-moto-z-play/
Also if RSD isnt detecting your phone, ADB might not either.
Click to expand...
Click to collapse
OK, I found mfastboot.exe located here (http://forum.xda-developers.com/gen...ng-mfastboot-exe-to-unbrick-motorola-t3203518) and had NO idea there was such a thing as mfastboot !
Unfortunately when running this, on all of these lines of mfastboot:
mfastboot flash gpt.bin partition
mfastboot flash bootloader.img bootloader
mfastoot flash NON-HLOS.bin modem
mfastboot flash fsg.bin fsg
mfastboot flash adspso.bin dsp
mfastboot flash logo.bin logo
I get "Image not signed or corrupt"
When I flash all of these, they go through OK:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
So I'm hoping this helps someone figure out what I'm doing wrong. Again, I'm just trying to get back to stock.
- You are restoring the firmware without wiping the device, i'd try fastboot erase userdata first before flashing the rest, could be worth a try.
- I get "Image not signed or corrupt" when flashing a modified kernel too, but it is flashed regardless.
- I got root with the chinese twrp, the others gave me bootloop.
Good luck.
I too have a freshly-bricked EU dual-SIM Z Play that gives "Image not signed or corrupt" errors when I try to flash recovery and boot. Seen by fastboot, but not by RSD.
edit: more of my saga is here http://forum.xda-developers.com/moto-z-play/help/identifying-firmware-required-phone-t3517360/
yeahhh, i manage to flash my moto z play back to stock, the rom was bad or something i downloaded from here.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETLA/
so happy
joesee said:
There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.
Click to expand...
Click to collapse
joesee said:
OK, I found mfastboot.exe located here (http://forum.xda-developers.com/gen...g-mfastboot-exe-to-unbrick-motorola-t3203518) and had NO idea there was such a thing as mfastboot !
Unfortunately when running this, on all of these lines of mfastboot:
mfastboot flash gpt.bin partition
mfastboot flash bootloader.img bootloader
mfastoot flash NON-HLOS.bin modem
mfastboot flash fsg.bin fsg
mfastboot flash adspso.bin dsp
mfastboot flash logo.bin logo
I get "Image not signed or corrupt"
When I flash all of these, they go through OK:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
So I'm hoping this helps someone figure out what I'm doing wrong. Again, I'm just trying to get back to stock.
Click to expand...
Click to collapse
The commands that aren't working aren't being given correctly. Should be like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
Milly7 said:
The commands that aren't working aren't being given correctly. Should be like this:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
Click to expand...
Click to collapse
You just saved my phone. Can I buy you a beer or something?
theodric said:
You just saved my phone. Can I buy you a beer or something?
Click to expand...
Click to collapse
It's all good. Just helping out. Glad it helped.
joesee said:
There isn't much on restoring this device at all. I'm really disappointed. I had high hopes. Anyway, the root situation is a mess, and after looking on here, I couldn't find a single set of instructions for properly flashing root. After digging around for a couple of hours, the only instructions I can find to revert to stock is:
1) Extract folder on PC.
2) Hold POWER and VOL DOWN on the phone to access the fastboot mode. Try to release the power button first before the VOL DOWN in case you trigger the system boot accidentally.
3) Connect USB cable to PC.
4) Flash in the following order:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash oem oem.img
Complete restore
WARNING: May wipe device, and has not been personally tested.
Before flashing the above, flash these first:
Code:
fastboot flash gpt.bin partition
fastboot flash bootloader.img bootloader
fastboot flash NON-HLOS.bin modem
fastboot flash fsg.bin fsg
fastboot flash adspso.bin dsp
fastboot flash logo.bin logo
BUT I cannot get this to work because I keep getting a "Image not signed or corrupt" error. I've confirmed I have the US retail single sim version (Addison).
I also cannot find a working version of RSD Lite that detects my phone. I've tried version 6.2.4.
Would anyone be able to help? I'd really appreciate it. I can get the bootloader up, but I cannot do anything else.
Click to expand...
Click to collapse
I had the complete restore section reversed when you saw it on my thread, someone pointed it out and it's been fixed now.
Edit: I see someone's done it here too.
You also don't need to restore fully, just do the restore for ota and it should be enough if you've not flashed over the other stuff.
well i forgot to boot and set up a pin before installing TWRP, soft bricked myself for hours, this thread helped me return to stock so i could set a pin so TWRP would work, THANK YOU!
also if anyone else ends up here, and is having trouble finding the US retail stock image, i used the one from https://mirrors.lolinet.com/firmware/moto/addison/official/RETUS/
Is that an official signed image?
Can i use it to relock bootloader?
Thanks!
dyonissos said:
Is that an official signed image?
Can i use it to relock bootloader?
Thanks!
Click to expand...
Click to collapse
None of the images are signed and won't relock the bootloader.
Would this allow me to return to Marshmallow after sideloading a Nougat OTA, given I unlock my bootloader? I flashed a build from a different region (I think retbr or something) onto my Canadian Z Play, but the build number doesn't match what everyone else is getting from. Just looking to revert to Marshmallow to perform a proper update instead of impatiently sideloading an OTA.
IncendiaryPyro said:
Would this allow me to return to Marshmallow after sideloading a Nougat OTA, given I unlock my bootloader? I flashed a build from a different region (I think retbr or something) onto my Canadian Z Play, but the build number doesn't match what everyone else is getting from. Just looking to revert to Marshmallow to perform a proper update instead of impatiently sideloading an OTA.
Click to expand...
Click to collapse
Yep if you have the right factory image for your device.
Leraeniesh said:
Yep if you have the right factory image for your device.
Click to expand...
Click to collapse
Thank you. I've never had issues doing stuff like this before, but for some reason it scares the hell out of me with this phone. Maybe because I haven't had it for very long, lol. Downgraded to Marshmallow successfully. Hopefully I don't run into any issues in the future that would require an RMA, but out of all the phones I've had over the years, I've only had to RMA a Nexus 5 due to a problem with the screen.
Hi everyone. Is this guide is okay for reteu dual sim? And please point me if there is a firmware for reteu nougat. I softbrick my device and my imei is 0. I want to restore it please guide me as i am a noob in fastboot commands and steps. Thanks in advance
Vitxlss said:
yeahhh, i manage to flash my moto z play back to stock, the rom was bad or something i downloaded from here.
https://mirrors.lolinet.com/firmware/moto/addison/official/RETLA/
so happy
Click to expand...
Click to collapse
do you have rooted device with twrp (maybe) ?
also, is the boot.img you got from Android 7 or 6.xx ?
Thanks
I use the DOWNGRADE script found here :
https://drive.google.com/file/d/0B134drJ4-Ed0MHQ5aE1wUmp5eFk/view
The original discussion here :
https://forum.xda-developers.com/moto-z-play/how-to/autoscript-install-firmware-downgrade-t3558118
Note that the original script is not ideal. The actual script came from @-=MoRpH=- on comment #4
Hello guys I've been trying out some different ROMs. Also tried the Oreo soak test but I'm now back on pixel experience but my finger print reader 4G and loud speaker is no longer working. It didn't work on aosp extended also.
How can I fix this please? I need 4G mainly...
Please help!
Thanks in advance.
junglebungle said:
Hello guys I've been trying out some different ROMs. Also tried the Oreo soak test but I'm now back on pixel experience but my finger print reader 4G and loud speaker is no longer working. It didn't work on aosp extended also.
How can I fix this please? I need 4G mainly...
Please help!
Thanks in advance.
Click to expand...
Click to collapse
Try flashing stock rom if you get 4g,speaker... Then try to come back to rom
riyan65 said:
Try flashing stock rom if you get 4g,speaker... Then try to come back to rom
Click to expand...
Click to collapse
Thanks for the reply. What is the stock ROM where can I find it? Is it safe to flash the older ROM?
junglebungle said:
Thanks for the reply. What is the stock ROM where can I find it? Is it safe to flash the older ROM?
Click to expand...
Click to collapse
The rom which came with your device is called stock rom. You can find it here
https://www.google.co.in/amp/s/foru...l-stock-moto-g5-cedric-firmware-t3733897/amp/
You can flash the old rom but you should not flash gpt and bootloader. If you flash bootloader and gpt your device will get hard bricked. So I suggest you to don't flash gpt and bootloader if you're having old stock rom. If you having latest stock rom then you can flash bootloader and gpt.
riyan65 said:
The rom which came with your device is called stock rom. You can find it here
https://www.google.co.in/amp/s/foru...l-stock-moto-g5-cedric-firmware-t3733897/amp/
You can flash the old rom but you should not flash gpt and bootloader. If you flash bootloader and gpt your device will get hard bricked. So I suggest you to don't flash gpt and bootloader if you're having old stock rom. If you having latest stock rom then you can flash bootloader and gpt.
Click to expand...
Click to collapse
Thanks I will try it, I am going to try it, I am from the UK so this link you give me is universal ROM and will work?
junglebungle said:
Thanks I will try it, I am going to try it, I am from the UK so this link you give me is universal ROM and will work?
Click to expand...
Click to collapse
It doesn't matter which country you live. All are same just different in receiving update time.
riyan65 said:
It doesn't matter which country you live. All are same just different in receiving update time.
Click to expand...
Click to collapse
Ok great, so because I am on the latest Pixel Experience ROM I just do the following commands to flash the november 2017 stock rom:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin - NO
fastboot flash bootloader bootloader.img - NO
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Right?
junglebungle said:
Ok great, so because I am on the latest Pixel Experience ROM I just do the following commands to flash:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin - NO
fastboot flash bootloader bootloader.img - NO
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Right?
Click to expand...
Click to collapse
Yes, right
riyan65 said:
Yes, right
Click to expand...
Click to collapse
Thanks for the help! I'll report back to see if 4G is working, does this fix the finger print reader too?
junglebungle said:
Thanks for the help! I'll report back to see if 4G is working, does this fix the finger print reader too?
Click to expand...
Click to collapse
When you flash stock rom there is possibility of losing imei. So take a backup of efs, if it efs didn't work then there a forum about how to recover imei with 4g. Wait for few minutes I send the link of the thread
---------- Post added at 02:30 PM ---------- Previous post was at 02:27 PM ----------
riyan65 said:
When you flash stock rom there is possibility of losing imei. So take a backup of efs, if it efs didn't work then there a forum about how to recover imei with 4g. Wait for few minutes I send the link of the thread
Click to expand...
Click to collapse
Here is the link
https://forum.xda-developers.com/g5/help/solution-0-imei-stock-t3801860
---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------
junglebungle said:
Thanks for the help! I'll report back to see if 4G is working, does this fix the finger print reader too?
Click to expand...
Click to collapse
Here is the link
https://forum.xda-developers.com/g5/help/solution-0-imei-stock-t3801860
---------- Post added at 02:40 PM ---------- Previous post was at 02:31 PM ----------
junglebungle said:
Thanks for the help! I'll report back to see if 4G is working, does this fix the finger print reader too?
Click to expand...
Click to collapse
Hey, I have forgotten to say that you can get 4g in Pixel rom also. But I don't know if it going to fix loudspeaker and finger scanner. The thread I have send you the link it is present there.
riyan65 said:
When you flash stock rom there is possibility of losing imei. So take a backup of efs, if it efs didn't work then there a forum about how to recover imei with 4g. Wait for few minutes I send the link of the thread
---------- Post added at 02:30 PM ---------- Previous post was at 02:27 PM ----------
Here is the link
https://forum.xda-developers.com/g5/help/solution-0-imei-stock-t3801860
---------- Post added at 02:31 PM ---------- Previous post was at 02:30 PM ----------
Here is the link
https://forum.xda-developers.com/g5/help/solution-0-imei-stock-t3801860
---------- Post added at 02:40 PM ---------- Previous post was at 02:31 PM ----------
Hey, I have forgotten to say that you can get 4g in Pixel rom also. But I don't know if it going to fix loudspeaker and finger scanner. The thread I have send you the link it is present there.
Click to expand...
Click to collapse
Ok I flashed the original stock ROM and I ended up getting 0 IMEI and no network. I followed your guide :
It seem like many of are not getting imei after doing this also.let me explain you in a clear way
Step1:-run on a custom rom such as lineage,aosp...
(Note:-if you have 4g/LTE in custom rom then skip step2)
Step2:-turn off your phone and get into bootloader and run the following commands
Fastboot erase modemst1
Fastboot erase modemst2
Step3:-make a back up of efs in Twrp 64x bits(save the efs in external memory so it will not get erased) and erase data,cache only
Step4:-now flash 32xbits Twrp then
Step5:-flash stock rom using following commands
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.o
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
fastboot oem fb_mode_clear
Step6:-now reboot your phone
Step7:-you will get the Imei and 4g/LTE
Step8:-don't use OTA, use adb you can download updates from here
https://drive.google.com/drive/mobil...Py?usp=sharing
Step9:-reboot to stock recovery and select apply update from adb
Step10:-run the following command to apply update
Adb sideload filename.zip
Step11:-In may security patch you may lose imei
Step12:-now install Twrp 64x bits and restore efs from it which you have make it before
Step13:-reboot your device.done
Now you will get the Imei,4g/LTE and latest update.
Let me know if it works for you.
--------------
This didn't work though, I have been messing around and finally got IMEI and 3G back again by reinstalling pixel experience ROM. But 4G doesn't even come up anymore when I select it in the Android network option, It just stays 3G when i select 4G, before it would say 4G with a X through it at the top of the home screen.
I have some questions, why do you need to flash 32bit TWRP because after you use the commands to flash stock it wipes thw TWRP anyway? also where can I get the 32bit as I can only find 64bit version.
Is that the reason why I got 0 IMEI because I didn't use 32 bit TWRP?
Finger print and loud speaker is now working but I REALLY need 4G back, please tell me how I can accomplish this?
I backed up my EFS AFTER I used the following commands:
fastboot erase modemst1
fastboot erase modemst2
But all that did was remove my IMEI.
I am lost how to get 4G back
Restoring EFS does nothing....
Thanks
junglebungle said:
Ok I flashed the original stock ROM and I ended up getting 0 IMEI and no network. I followed your guide :
It seem like many of are not getting imei after doing this also.let me explain you in a clear way
Step1:-run on a custom rom such as lineage,aosp...
(Note:-if you have 4g/LTE in custom rom then skip step2)
Step2:-turn off your phone and get into bootloader and run the following commands
Fastboot erase modemst1
Fastboot erase modemst2
Step3:-make a back up of efs in Twrp 64x bits(save the efs in external memory so it will not get erased) and erase data,cache only
Step4:-now flash 32xbits Twrp then
Step5:-flash stock rom using following commands
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.o
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
fastboot oem fb_mode_clear
Step6:-now reboot your phone
Step7:-you will get the Imei and 4g/LTE
Step8:-don't use OTA, use adb you can download updates from here
https://drive.google.com/drive/mobil...Py?usp=sharing
Step9:-reboot to stock recovery and select apply update from adb
Step10:-run the following command to apply update
Adb sideload filename.zip
Step11:-In may security patch you may lose imei
Step12:-now install Twrp 64x bits and restore efs from it which you have make it before
Step13:-reboot your device.done
Now you will get the Imei,4g/LTE and latest update.
Let me know if it works for you.
--------------
This didn't work though, I have been messing around and finally got IMEI and 3G back again by reinstalling pixel experience ROM. But 4G doesn't even come up anymore when I select it in the Android network option, It just stays 3G when i select 4G, before it would say 4G with a X through it at the top of the home screen.
I have some questions, why do you need to flash 32bit TWRP because after you use the commands to flash stock it wipes thw TWRP anyway? also where can I get the 32bit as I can only find 64bit version.
Is that the reason why I got 0 IMEI because I didn't use 32 bit TWRP?
Finger print and loud speaker is now working but I REALLY need 4G back, please tell me how I can accomplish this?
I backed up my EFS AFTER I used the following commands:
fastboot erase modemst1
fastboot erase modemst2
But all that did was remove my IMEI.
I am lost how to get 4G back
Restoring EFS does nothing....
Thanks
Click to expand...
Click to collapse
Now your in which rom stock or custom??? If you're on custom rom just use this command's
fastboot erase modemst1
fastboot erase modemst2
If you are in stock you need to go back to custom check if 4g is there if not use the above command and then come to stock without using this codes
fastboot erase modemst1
fastboot erase modemst2
And gpt, bootloader.
riyan65 said:
Now your in which rom stock or custom??? If you're on custom rom just use this command's
fastboot erase modemst1
fastboot erase modemst2
If you are in stock you need to go back to custom check if 4g is there if not use the above command and then come to stock without using this codes
fastboot erase modemst1
fastboot erase modemst2
And gpt, bootloader.
Click to expand...
Click to collapse
I am on pixel again, if I go back to stock it gives me 0 IMEI, and I don't want to risk it as I don't have the internet at home right now I am tethered via my phone. I did these commands
fastboot erase modemst1
fastboot erase modemst2
Before and it wiped my IMEI.
What do you mean "and gpt, bootloader" they need flashing too? for which ROM? I am so confused.
Why is 32bits TWRP needed?
I tried stock rom and the oreo rom and both gave me 0 IMEI but I am not sure what I did to get it working on pixel, I flashed pixel in TWRP and booted the phone and the IMEI and 3G was working again, but no 4G.
riyan65 said:
Now your in which rom stock or custom??? If you're on custom rom just use this command's
fastboot erase modemst1
fastboot erase modemst2
If you are in stock you need to go back to custom check if 4g is there if not use the above command and then come to stock without using this codes
fastboot erase modemst1
fastboot erase modemst2
And gpt, bootloader.
Click to expand...
Click to collapse
Any update? this is really stressing me out
even two guys in this thread: https://forum.xda-developers.com/g5/help/solution-0-imei-stock-t3801860/
Said that getting 4g back wasn't possible? and the post before my one that guy had issues too. I hear there is no fix to get 4G back....
junglebungle said:
I am on pixel again, if I go back to stock it gives me 0 IMEI, and I don't want to risk it as I don't have the internet at home right now I am tethered via my phone. I did these commands
fastboot erase modemst1
fastboot erase modemst2
Before and it wiped my IMEI.
What do you mean "and gpt, bootloader" they need flashing too? for which ROM? I am so confused.
Why is 32bits TWRP needed?
I tried stock rom and the oreo rom and both gave me 0 IMEI but I am not sure what I did to get it working on pixel, I flashed pixel in TWRP and booted the phone and the IMEI and 3G was working again, but no 4G.
Click to expand...
Click to collapse
If you on custom rom just use this command's in Pixel or other roms it don't wipe imei.
fastboot erase modemst1
fastboot erase modemst2
riyan65 said:
If you on custom rom just use this command's in Pixel or other roms it don't wipe imei.
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I am on Pixel rom with 3G only, no 4G, I just used those commands and rebooted the phone, it wiped my IMEI and gave me no signal..... so that doesn't work....
I then had to install stock rom again (without the above codes and gpt/bootloader it didn't give me imei stilI) So I wipe data, reinstall pixel custom rom and still no imei or 3g, I then installed Oreo soak test with all the commands (including fastboot erase modemst1/2 and gpt/bootloader) then flash pixel again to get my 3g back... I think I am doomed and 4g doesn't work anymore, many people are saying the same thing. Even on this guys video: https://www.youtube.com/watch?v=XmKg84IXEbo
I also can't restore my EFS file as when I try to it says some error about a partition?
Apprently the only way to fix it is install official android 8.0 that guy said? is this true?
riyan65 said:
If you on custom rom just use this command's in Pixel or other roms it don't wipe imei.
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
Hey man sorry to bug you but did you have any thing else I can try? it's driving me mad
junglebungle said:
Hey man sorry to bug you but did you have any thing else I can try? it's driving me mad
Click to expand...
Click to collapse
Hey did you try any rom of 32bit with 32 bit twrp.
riyan65 said:
Hey did you try any rom of 32bit with 32 bit twrp.
Click to expand...
Click to collapse
Not sure, I did use 32bit twrp for something I can't remember what though, it wasn't stock rom as I used the commands to flash stock rom.
Also tried this: https://forum.xda-developers.com/g5/how-to/how-to-recovery-4g-moto-g5-t3787208
But that didn't work either, using the erase modem commands just wipes my IMEI. I tried this on Pixel rom though not the DotOS, surely that doesn't make any difference?
junglebungle said:
Not sure, I did use 32bit twrp for something I can't remember what though, it wasn't stock rom as I used the commands to flash stock rom.
Also tried this: https://forum.xda-developers.com/g5/how-to/how-to-recovery-4g-moto-g5-t3787208
But that didn't work either, using the erase modem commands just wipes my IMEI. I tried this on Pixel rom though not the DotOS, surely that doesn't make any difference?
Click to expand...
Click to collapse
Try this commands on AOSP/lineage rom.
Hello. The phone is with my mom now and I haven't been here to know how rom development is going. She complains that camera doesn't work so I want to either return to stock or flash a pie build that has 100% camera functionality or a fix. Can you guys enlighten me?
Flash stock firmware via fastboot
https://mirrors.lolinet.com/firmware/moto/cedric/official/
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (don't flash this as may hard brick if incorrect)
fastboot flash bootloader bootloader.img (don't flash this as may hard brick if incorrect)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1 (don't erase this unless you have network issues)
fastboot erase modemst2 (don't erase this unless you have network issues)
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Flash the above with your phone in fastboot mode - I've edited which bits you shouldn't need to do
TheFixItMan said:
Flash stock firmware via fastboot
https://mirrors.lolinet.com/firmware/moto/cedric/official/
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (don't flash this as may hard brick if incorrect)
fastboot flash bootloader bootloader.img (don't flash this as may hard brick if incorrect)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1 (don't erase this unless you have network issues)
fastboot erase modemst2 (don't erase this unless you have network issues)
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Flash the above with your phone in fastboot mode - I've edited which bits you shouldn't need to do
Click to expand...
Click to collapse
So it doesn't matter if phone is on 64 bits or 32 bits?
diogofd8 said:
So it doesn't matter if phone is on 64 bits or 32 bits?
Click to expand...
Click to collapse
Why would it?
You are flashing stock firmware which will replace what ever is on your phone
Stock firmware for this device is only 32bit - it doesn't matter what rom you are currently using
Thanks a lot man, mom is happy!
I applied your method to my moto g5 and I confirm it works as advertised !
I only had to reflash TWRP and the boot logo and that was it. Thanks !
Why you need to reflash twrp and boot logo?
Sorry if it is a lame question. I am also thinking on reverting back to stock.
Oremusnix said:
I applied your method to my moto g5 and I confirm it works as advertised !
I only had to reflash TWRP and the boot logo and that was it. Thanks !
Click to expand...
Click to collapse
achintyakv said:
Why you need to reflash twrp and boot logo?
Sorry if it is a lame question. I am also thinking on reverting back to stock.
Click to expand...
Click to collapse
There is no lame question !
The guide provided by OP erases the TWRP recovery and replaces it with what was on stock (my guess because I did not check, actually). So I had to reflash TWRP to install Magisk, but this is not mandatory.
The logo was back to the "this device is not secure" warning wich is ugly. The unlocked state was not lost (which was fine by me). So I flashed one boot logo to replace that warning.
Okay now I understand. Thank you! ?
Oremusnix said:
There is no lame question !
The guide provided by OP erases the TWRP recovery and replaces it with what was on stock (my guess because I did not check, actually). So I had to reflash TWRP to install Magisk, but this is not mandatory.
The logo was back to the "this device is not secure" warning wich is ugly. The unlocked state was not lost (which was fine by me). So I flashed one boot logo to replace that warning.
Click to expand...
Click to collapse
Oremusnix said:
There is no lame question !
The guide provided by OP erases the TWRP recovery and replaces it with what was on stock (my guess because I did not check, actually). So I had to reflash TWRP to install Magisk, but this is not mandatory.
The logo was back to the "this device is not secure" warning wich is ugly. The unlocked state was not lost (which was fine by me). So I flashed one boot logo to replace that warning.
Click to expand...
Click to collapse
How cdo you flash the boot logo? And where can you find it? I also hate the "unlocked device" warning...
Thanks in advance,
J.
jpm92 said:
How cdo you flash the boot logo? And where can you find it? I also hate the "unlocked device" warning...
Thanks in advance,
J.
Click to expand...
Click to collapse
I used that one for the G5 plus and it worked fine : https://forum.xda-developers.com/g5-plus/how-to/logo-fix-g5-logo-bin-t3610456
Oremusnix said:
I used that one for the G5 plus and it worked fine : https://forum.xda-developers.com/g5-plus/how-to/logo-fix-g5-logo-bin-t3610456
Click to expand...
Click to collapse
But the bootlogo of the ROM will stay the same right? ? I like the LOS logo ?
I just want to remove the warning.
Thanks!
jpm92 said:
But the bootlogo of the ROM will stay the same right? I like the LOS logo
I just want to remove the warning.
Thanks!
Click to expand...
Click to collapse
Yes, the ROM starting screen stays the same.
Recently i install pie 9.0 on z2 play, to try to fix the fingerprint scanner and gestures but still doesnt work, i was reading that is a problem from oreo, so i want to Downgrade to oreo to nougat, it's posible?
Anything below Pie is vulnerable to the X-helper rootkit... we were just talking about it in another thread. It's a real nasty little bugger.
But its posible? I just want to get all the features back, even, i dont know what is that thing, if they have some to hack me i dont have to much to lose anyways, just want to downgrate to fix the fingerprint bug from oreo
Don't know. Hopefully someone with this device can help you.
iMaxwell said:
Recently i install pie 9.0 on z2 play, to try to fix the fingerprint scanner and gestures but still doesnt work, i was reading that is a problem from oreo, so i want to Downgrade to oreo to nougat, it's posible?
Click to expand...
Click to collapse
How exactly did you install it? FP not working is usually just that the fw is needed, but that's only if you are running a custom rom. What specific issue were you facing before and what OS were you running
marcost22 said:
How exactly did you install it? FP not working is usually just that the fw is needed, but that's only if you are running a custom rom. What specific issue were you facing before and what OS were you running
Click to expand...
Click to collapse
Install via "ota", just donwload 9.0 official motorola firmware, put it into internal storage, then go to settings - search for updates, then install.
The problems are, fingerprint doesnt work, but this is a problem from oreo. And i want to go back to nougat
iMaxwell said:
Install via "ota", just donwload 9.0 official motorola firmware, put it into internal storage, then go to settings - search for updates, then install.
The problems are, fingerprint doesnt work, but this is a problem from oreo. And i want to go back to nougat
Click to expand...
Click to collapse
that's probably the worst available way to do it. If your phone didn't originally receive it via OTA, then you are forcing it the wrong way.
If you want to go back to nougat all you need to do is download the official N firmware, then flash everything but bootloader and gpt
What is gpt? I need to unlock bootloader and flash whit wrp? I heard about losing imei or something like that
I follow the steps on this video
iMaxwell said:
I follow the steps on this video
Click to expand...
Click to collapse
Yeah that is just terrible
iMaxwell said:
What is gpt? I need to unlock bootloader and flash whit wrp? I heard about losing imei or something like that
Click to expand...
Click to collapse
Download the official N firmware from https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/albus/official/RETAIL/
Then, extract it and reboot your phone into fastboot (shut it down, hold down volume down and turn it on, you should arrive at fastboot that way)
Install minimal adb and fastboot if you dont have them installed ( https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/)
After that, you open a terminal where you extracted the firmware, run fastboot devices to check that A) fastboot is installed and that B) your phone is recognized and then you run
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
This WILL format your phone, but it should leave you with a booting N system(maybe, downgrading not always work and going P->N is really unusual)
I'm gonna be honest i do think all of your issues are caused by forcing an OTA where the phone wasn't supposed to have one, but it's your choice
marcost22 said:
Yeah that is just terrible
Download the official N firmware from https://mirrors-obs-2.lolinet.com/firmware/motorola/2017/albus/official/RETAIL/
Then, extract it and reboot your phone into fastboot (shut it down, hold down volume down and turn it on, you should arrive at fastboot that way)
Install minimal adb and fastboot if you dont have them installed ( https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/)
After that, you open a terminal where you extracted the firmware, run fastboot devices to check that A) fastboot is installed and that B) your phone is recognized and then you run
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
This WILL format your phone, but it should leave you with a booting N system(maybe, downgrading not always work and going P->N is really unusual)
I'm gonna be honest i do think all of your issues are caused by forcing an OTA where the phone wasn't supposed to have one, but it's your choice
Click to expand...
Click to collapse
The issues begin on official oreo, i upgrade nougat to oreo then, fingerprint option dissapear, then i upgrade to pie from oficial firmware but issues still remain
It really works? I didnt find any video or post about downgrade like that
Yes it does work, but it's not recommended, that's why you don't find much info
iMaxwell said:
It really works? I didnt find any video or post about downgrade like that
Click to expand...
Click to collapse