Yesterday I downloaded the April patch and updated it using the bootloader due to being rooted.
However, since then, the volte icon has stopped appearing.
I tried *#*#INFO#*#* but that shows VoLTE provisionijg enabled.
None of the Jio sims show VoLTE on my phone (which do on other phones).
I tried the swim swapping technique and the enhanced LTE mode is enabled as well.
Jio4G voice shows my phone as VoLTE compatible and thus only allows me to do video calls (which doesn't work either).
I tried the Magisk modules to enable and disable VoLTE but they don't work either.
Again, I'm on stock with EX Kernel 2.01, Magisk 16 and April 2018 security patch (retin).
Here's the screenshot of the *#*#INFO#*#*
Had to reset device just to enable VoLTE
kunalgupta1 said:
Had to reset device just to enable VoLTE
Click to expand...
Click to collapse
Bro I did the same thing as you did but still didn't work for me !!
I flashed the fastboot ROM directly coz I was rooted ... And then things didn't worked quite well as I lost my radio,fingerprint and the models changed to Moto(g4) !! So I followed everything as mentined in this link moto g4 plus repair
And then I got everything back working fine , until I installed jio sim in my mob..... Everything is working except volte ... I tried resetting the device .. but it didn't work !! Could u help me with that !!??
I'm using
Twrp 3.2.1
And I'm on stock ROM with April' 18 patch applied directly through flashing ROM via fastboot !
Vs1607 said:
Bro I did the same thing as you did but still didn't work for me !!
I flashed the fastboot ROM directly coz I was rooted ... And then things didn't worked quite well as I lost my radio,fingerprint and the models changed to Moto(g4) !! So I followed everything as mentined in this link moto g4 plus repair
And then I got everything back working fine , until I installed jio sim in my mob..... Everything is working except volte ... I tried resetting the device .. but it didn't work !! Could u help me with that !!??
I'm using
Twrp 3.2.1
And I'm on stock ROM with April' 18 patch applied directly through flashing ROM via fastboot !
Click to expand...
Click to collapse
Sorry but I don't have it anymore and went forward to buy an OP6, as it even started to shut down at 70% battery.
Motorola's Moto G4 Plus is the ****tiest phone I've ever seen, with the ****tiest quality and ****tiest concern-for-customer policy. It's better to buy a new one rather than this phone. Never buying Moto again.
Vs1607 said:
Bro I did the same thing as you did but still didn't work for me !!
I flashed the fastboot ROM directly coz I was rooted ... And then things didn't worked quite well as I lost my radio,fingerprint and the models changed to Moto(g4) !! So I followed everything as mentined in this link moto g4 plus repair
And then I got everything back working fine , until I installed jio sim in my mob..... Everything is working except volte ... I tried resetting the device .. but it didn't work !! Could u help me with that !!??
I'm using
Twrp 3.2.1
And I'm on stock ROM with April' 18 patch applied directly through flashing ROM via fastboot !
Click to expand...
Click to collapse
Did you try this script from the factory fastboot ROM? https://forum.xda-developers.com/showpost.php?p=76786219&postcount=12 (Don't flash the ROM, just use the script if possible).
Hmm, did you follow the posts that I mentioned in the note included in that folder? As I mentioned (I'm the uploader of those files), they were from my XT1642, with an EMEA (Europe) baseband, so they may not work for India VoLTE services. You may have to see if you can find an Indian modem variant if the above script fix doesn't work.
echo92 said:
Did you try this script from the factory fastboot ROM? https://forum.xda-developers.com/showpost.php?p=76786219&postcount=12 (Don't flash the ROM, just use the script if possible).
Hmm, did you follow the posts that I mentioned in the note included in that folder? As I mentioned (I'm the uploader of those files), they were from my XT1642, with an EMEA (Europe) baseband, so they may not work for India VoLTE services. You may have to see if you can find an Indian modem variant if the above script fix doesn't work.
Click to expand...
Click to collapse
Hello sir ... I followed the posts mentioned in your note... And did exactlly as explained ... But still negative .... although I haven't tried the script from the factory fast boot ROM ...... And honestly I didn't understand what exactly we've to do(the script flashing part).... So would you please help me with that ?? .... If everything fails then I guess I'm left with flashing the old ROM from Feb patch (npjs25.93-14_15).... :crying:
Vs1607 said:
Hello sir ... I followed the posts mentioned in your note... And did exactlly as explained ... But still negative .... although I haven't tried the script from the factory fast boot ROM ...... And honestly I didn't understand what exactly we've to do(the script flashing part).... So would you please help me with that ?? .... If everything fails then I guess I'm left with flashing the old ROM from Feb patch (npjs25.93-14_15).... :crying:
Click to expand...
Click to collapse
As far as I understand, the script should re-program your hw partition - this partition tells your device how to distinguish itself from a G4 and a G4 Plus. I recall you mentioned your device now reports as a G4, which this script may help with.
I've not used the script fully, so you may have to perform some troubleshooting, though try this:
1)Download the NPJ25.93-14 factory fastboot ROM as linked. Extract the factory ROM - it should ask for a password. The password is 'lenovo-forums.ru' without quotes. NOTE - this is a factory fastboot ROM, which is different from the usual fastboot ROMs we get leaked - the factory fastboot ROM appears to have most if not all the scripts for programming a G4/Plus.
2)Boot your device to the bootloader, don't connect it to your computer just yet.
3)Launch the programutags.bat script. It should ask you what region you want to program for. For your device, select APAC (Asia Pacific) with option 2, then select Retail India with option B.
4)Connect your device when it asks for fastboot enumeration (making sure you've programmed the right settings in 3), and follow the rest of the prompts.
Hopefully that should fix your device. Flashing the older firmware may not work, since the issue appears to be more extensive than flashing firmware. These partitions should normally not be touched, but we've seen previously that flashing firmware from another region in the past can lead to IMEI loss when flashing newer firmware (even if the newer firmware is correct for your region).
echo92 said:
As far as I understand, the script should re-program your hw partition - this partition tells your device how to distinguish itself from a G4 and a G4 Plus. I recall you mentioned your device now reports as a G4, which this script may help with.
I've not used the script fully, so you may have to perform some troubleshooting, though try this:
1)Download the NPJ25.93-14 factory fastboot ROM as linked. Extract the factory ROM - it should ask for a password. The password is 'lenovo-forums.ru' without quotes. NOTE - this is a factory fastboot ROM, which is different from the usual fastboot ROMs we get leaked - the factory fastboot ROM appears to have most if not all the scripts for programming a G4/Plus.
2)Boot your device to the bootloader, don't connect it to your computer just yet.
3)Launch the programutags.bat script. It should ask you what region you want to program for. For your device, select APAC (Asia Pacific) with option 2, then select Retail India with option B.
4)Connect your device when it asks for fastboot enumeration (making sure you've programmed the right settings in 3), and follow the rest of the prompts.
Hopefully that should fix your device. Flashing the older firmware may not work, since the issue appears to be more extensive than flashing firmware. These partitions should normally not be touched, but we've seen previously that flashing firmware from another region in the past can lead to IMEI loss when flashing newer firmware (even if the newer firmware is correct for your region).
Click to expand...
Click to collapse
Hello sir ,
Thanx for your valuable support . But sorry to say the script
Didn't work as well . Even though I followed the exact same instruction, the script ended up with the result in cmd as follows :
Code:
Motorola Mobility LatAm UTAG programming script
This script programs the following UTAGs: fsg-id and carrier
1 - LATAM
2 - APAC
3 - Canada
4 - US
5 - EMEA
6 - Quit
Please select Region:2
A - Retail APAC
B - Retail India
C - Quit
Please select Carrier: B
Waiting for fastboot enumeration...
Fastboot device is ready!!
Setting fsg-id...
Executing ".\Windows\fastboot.exe oem config fsg-id """
...
OKAY [ 0.004s]
finished. total time: 0.004s
Setting carrier...
Executing ".\Windows\fastboot.exe oem config carrier retin"
...
(bootloader) <UTAG name="carrier" type="str" protected="false">
(bootloader) <value>
(bootloader) retin
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see http://goo.gl/lojLh3
(bootloader) </description>
(bootloader) </UTAG>
OKAY [ 0.012s]
finished. total time: 0.012s
Erasing modemst1/modemst2...
Executing ".\Windows\fastboot.exe erase modemst1"
erasing 'modemst1'...
OKAY [ 0.029s]
finished. total time: 0.029s
Executing ".\Windows\fastboot.exe erase modemst2"
erasing 'modemst2'...
OKAY [ 0.028s]
finished. total time: 0.028s
All UTAGs programmed successfully!
Press any key to continue . . .
screenshot
I guess the that's all bcoz of flashing European modem !!
But as you mentioned , the script must have worked ... But didn't . So maybe I've to post in the thread asking modem for Indian variants and maybe that would work !!
Sir , if you could suggest anymore alternatives I would be grateful
Vs1607 said:
Hello sir ,
Thanx for your valuable support . But sorry to say the script
Didn't work as well . Even though I followed the exact same instruction, the script ended up with the result in cmd as follows :
Code:
Motorola Mobility LatAm UTAG programming script
This script programs the following UTAGs: fsg-id and carrier
1 - LATAM
2 - APAC
3 - Canada
4 - US
5 - EMEA
6 - Quit
Please select Region:2
A - Retail APAC
B - Retail India
C - Quit
Please select Carrier: B
Waiting for fastboot enumeration...
Fastboot device is ready!!
Setting fsg-id...
Executing ".\Windows\fastboot.exe oem config fsg-id """
...
OKAY [ 0.004s]
finished. total time: 0.004s
Setting carrier...
Executing ".\Windows\fastboot.exe oem config carrier retin"
...
(bootloader) <UTAG name="carrier" type="str" protected="false">
(bootloader) <value>
(bootloader) retin
(bootloader) </value>
(bootloader) <description>
(bootloader) Carrier IDs, see http://goo.gl/lojLh3
(bootloader) </description>
(bootloader) </UTAG>
OKAY [ 0.012s]
finished. total time: 0.012s
Erasing modemst1/modemst2...
Executing ".\Windows\fastboot.exe erase modemst1"
erasing 'modemst1'...
OKAY [ 0.029s]
finished. total time: 0.029s
Executing ".\Windows\fastboot.exe erase modemst2"
erasing 'modemst2'...
OKAY [ 0.028s]
finished. total time: 0.028s
All UTAGs programmed successfully!
Press any key to continue . . .
screenshot
I guess the that's all bcoz of flashing European modem !!
But as you mentioned , the script must have worked ... But didn't . So maybe I've to post in the thread asking modem for Indian variants and maybe that would work !!
Sir , if you could suggest anymore alternatives I would be grateful
Click to expand...
Click to collapse
Did you reflash the April 2018 fastboot ROM? On occasion, after trying to repair your IMEI you may have to reflash to fully attempt the repair. I did warn in those notes that the files are from an European device.
Other than that, I don't know what else to try, as this isn't my area of expertise. That factory fastboot ROM is the only one we have.
Also, I see you've posted in other threads, please review and remove the posts you quoted, in both cases you've quoted the entire opening post which is unnecessary, messy and risks us losing your message. You can keep your message.
Had same issue
Flash the December update via fastboot.... Volte will work
rex1435 said:
Flash the December update via fastboot.... Volte will work
Click to expand...
Click to collapse
Hi bro . I've flashed Npjs25.93-14-15 but didn't work .
But I'll definitely try with December patch and let u know..
Thanks btw
Vs1607 said:
Hi bro . I've flashed Npjs25.93-14-15 but didn't work .
But I'll definitely try with December patch and let u know..
Thanks btw
Click to expand...
Click to collapse
It will definitely work with the December patch
rex1435 said:
Flash the December update via fastboot.... Volte will work
Click to expand...
Click to collapse
Same problem on my moto g4 plus..how can i do this..plz explain... I'll try
sanjibkumarchini said:
Same problem on my moto g4 plus..how can i do this..plz explain... I'll try
Click to expand...
Click to collapse
Find the December or February stock rom ( not April one) from xda flash it via fastboot n ur volte will work.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
U can directly put above commands in cmd to flash stock
any other way other than reverting to december update? thx
Deleted, sorry I didn't check first
m8952_70030.25.03.62.02R
athene_emea_dsds_cust
Deleted. Sorry I didn't check first
but it's always emea xt1642 for me i'm not in india...
Related
Hello, I'm trying to help people who installed the soak test of Lollipop but is not enjoying the ROM with lots of bugs and want to go back to KK.
THIS IS ONLY FOR XT1225, BRAZILIAN FIRMWARE RETAIL UPDATED VIA OTA
YOU NEED TO HAVE YOUR BOOTLOADER UNLOCKED
It will work even if you have root on lollipop
Do it at your own risk!
So, this is the procedure:
DOWNLOADS
1 - Download the Stock ROM from here:
RETBR_XT1225_4.4.4_KXG21.50-9
2 - Download Motorola Drivers from HERE
3 - Download Moto Fastboot from HERE
* IT NEED TO BE MOTO FASTBOOT, known as "mfastboot" . Android Fastboot wont handle the system flash.
INSTRUCTIONS
1 - Backup your phone, otherwise you will lose everything on it
2 - Extract ROM files to a folder (I did on " C:\MAXX\ " )
3 - Extract Moto Fastboot files on same folder you extracted the ROM
4 - Shutdown your phone and put it on fastboot mode (when off, press Power Button + Volume down)
5 - Plug your phone on your PC
6 - Install Motorola Drivers NOW. (For me it only install the driver at this time. If you have the proper driver installed already, skip this step)
7 - Open a command prompt and go to the folder that you extracted the ROM and Moto fastboot
8 - Now, you need to type every line, pressing enter when is a new line and waiting the process to be sucessfully
Code:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
For me it worked, now your phone will reboot and boot right again on KK
I had tried to do with RSD Lite but it always fail on flash the partition.
So, this procedure above is tested by me and it works.
Well all i just did was to restore my twrp backup and then flash my radio.img and that's it didn't lose anything and my cell works like charm just like before flashing lollipop
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Gundabolu SC said:
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Click to expand...
Click to collapse
remember that this tutorial is ONLY FOR WHO UPDATES WITH OTA.
if u updated the phone with official OTA ,u can t downgrade to 4.4.4
or if the firmware img of 5.0.2 will go out and u will flash it U CAN T GO BACK TO 4.4.4 either.
always make a nandroid backup in twrp of 4.4.4 .it will be useful.
I've received a OTA without TWRP.... so, I did not could make a nandroid
Gundabolu SC said:
These downgrades are super dangerous the next time you accept an OTA which could possibly brick your device.... Happened loads of times on the Moto X... Hope it doesnt repeat here as well!
Click to expand...
Click to collapse
This was the case with the 2013 Moto X, there is no such problem with the 2014 model. It is unlikely to be a problem with the XT1225. Motorola learned from that mistake.
do you know how you can downgrade but for the mx firmware?, because i flash the br firmware and update to lollipop but i didnt like it very much and i want to go back, any ideas?
arcaneck said:
do you know how you can downgrade but for the mx firmware?, because i flash the br firmware and update to lollipop but i didnt like it very much and i want to go back, any ideas?
Click to expand...
Click to collapse
Did you install the lollipop via OTA after flashing brazilian firmware ?
yes i did
It's the same procedure but with the mx firmware
works fine thanks
Works for me too
do you have the mx ota?
Hi,
I have lock bootloader, trying this tutorial, and no work (of course).
When flash Boot.img, show message with failed "version downgraded for boot" and
C:\Maxx>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
anyone have any idea how to unbrick phone?
tnks!
I've installed the zip file of the soak test (I didn't receive it through OTA), will this procedure work for me? Really tired of the instability of 5.0.2
I have the same problem
megadu said:
Hi,
I have lock bootloader, trying this tutorial, and no work (of course).
When flash Boot.img, show message with failed "version downgraded for boot" and
C:\Maxx>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.538s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.797s
anyone have any idea how to unbrick phone?
tnks!
Click to expand...
Click to collapse
I have the same problem.
After the command "mfastboot flash boot boot.img ". Do not process more.
Can anyone help me? Please!
Have you unlocked the bootloader?
boot.img can never been be downgraded. If you downgrade from version 5.x to 4.4.4 you have to skip that file.
I update my motorola using this guide http://forum.xda-developers.com/droid-turbo/general/guideinstall-lollipop-ota-root-ur-moto-t3029690 , can i do the downgrade ?
Thanks!
im have the same question, im using now cm12 with twrp, bootloader unlocked. can i go back to stock 4.4.4 using this tutorial? its safe?
Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?
Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.
sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.
what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key
This guide will help you re lock the bootloader and fix the bootloader is damaged error download a stock rom for the cedric extract it into adb and fast boot . (Not into its own folder just all the files in adb ) link to stock roms :
Now copy these commands
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 boot boot.img
fastboot oem lock
If it worked there shouldn't be a bl warning and in fastboot it should say flashing-locked
Note any problems caused are not my fault I have tested on my device and on g5+ both are fine !
Thank you so much, my Bootloader is locked again.
̶C̶a̶n̶ ̶y̶o̶u̶ ̶p̶l̶e̶a̶s̶e̶ ̶g̶i̶v̶e̶ ̶u̶s̶ ̶f̶i̶r̶m̶w̶a̶r̶e̶ ̶f̶i̶l̶e̶ ̶t̶h̶a̶t̶ ̶y̶o̶u̶ ̶u̶s̶e̶d̶?̶
First its the command to relock de BL?
before the commands to flash system?
AlmapekeDj said:
First its the command to relock de BL?
before the commands to flash system?
Click to expand...
Click to collapse
You need to reflash system
With me didn't worked. It says "Not signed rom"
CypherPotato said:
With me didn't worked. It says "Not signed rom"
Click to expand...
Click to collapse
Redownload stock
CypherPotato said:
With me didn't worked. It says "Not signed rom"
Click to expand...
Click to collapse
Did you get it already? Still need it?
Anyway, if anyone else needs it https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
This is the only one that worked signed for me, XT1672
my imei is 0 already tried everything but I did not have any results help me please it's an xt1672
jonathars said:
my imei is 0 already tried everything but I did not have any results help me please it's an xt1672
Click to expand...
Click to collapse
Reflash stock rom
CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
I already did this and it did not work
---------- Post added at 02:36 AM ---------- Previous post was at 02:30 AM ----------
CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
I already did this and it did not work
infixremix said:
This guide will help you re lock the bootloader and fix the bootloader is damaged error download a stock rom for the cedric extract it into adb and fast boot . (Not into its own folder just all the files in adb ) link to stock roms :
Now copy these commands
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 boot boot.img
fastboot oem lock
If it worked there shouldn't be a bl warning and in fastboot it should say flashing-locked
Note any problems caused are not my fault I have tested on my device and on g5+ both are fine !
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------
You are amazing !!
Hi,
doesn't work for me. Tried from here:
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
Moto G5 - Jan 2017 firmware NPP25.137-15 and
Moto G5 - Nov 2017 firmware NPP25.137-93 (Moto G5 - Aug 2017 firmware NPP25.137-33/NPP25.137.33-10 not tested yet).
Error when flashing boot.img:
C:\g5\010117\platform-tools>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.583s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 1.035s
anyone an idea what's going wrong?
D.
CypherPotato said:
Reflash stock rom
Click to expand...
Click to collapse
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)
carlapazin said:
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)
Click to expand...
Click to collapse
Yes - via fastboot
I don't know why you would want to change though
You risk either not getting ota updates or potentially hard bricking your device if you flash a future ota update if you have flashed firmware that was not designed for your phones specific varient
Unless you have physically moved locations & the firmware you are using is not compatible with the countries mobile networks I see no benefits in changing firmware versions
TheFixItMan said:
Yes - via fastboot
I don't know why you would want to change though
You risk either not getting ota updates or potentially hard bricking your device if you flash a future ota update if you have flashed firmware that was not designed for your phones specific varient
Unless you have physically moved locations & the firmware you are using is not compatible with the countries mobile networks I see no benefits in changing firmware versions
Click to expand...
Click to collapse
thanx!!!
carlapazin said:
can I reflash stock ROM with locked bootloader?
how can do that? using adb fastboot or RSD lite?
i just want to change my channel (today is retin, but i've got a stock ROM with retbr and want to use that)
Click to expand...
Click to collapse
RSD Lite only emulates Fastboot inside the application.
Idk if you can flash the stock rom with an locked bootloader, if it is signed, you can, otherwise, no.
Hello! https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
I used that forum to re-lock bootloader and flash stock rom! WHOOHOO, but fastboot is still saying my software status is modified, and I can't tell if I'm receiving OTA updates? How do I check that? I went into settings > About phone > software updates > YOUR SOFTware is up to date.
So I'm wondering if since my fastboot says my firmware is modified, that i'm not receiving OTA. Can someone please confirm they're running un-touched moto g5 plus software, and confirm what latest buildnumber is? U.S. phones only please.
I really need help, I need to receive OTA updates, and I'd assume since it says my "software is up to date" that it is, but I want someone to confirm..
BUILD NUMBER NPNS25.137-33-11
if anyone knows anything about this PLEASE post I'm desparate.
OK flashed rom from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ from december
that should be the latest one,
NPN25.137-92
security patch nov 1 2017
HOWEVER, even though i may be on the latest rom it's still disturbing that i don't receive ota updates. any way to get around this?
beatlesfan5858 said:
OK flashed rom from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ from december
that should be the latest one,
NPN25.137-92
security patch nov 1 2017
HOWEVER, even though i may be on the latest rom it's still disturbing that i don't receive ota updates. any way to get around this?
Click to expand...
Click to collapse
I think once you leave stock, you won't receive OTA's again, even if you re-flash and lock bootloader. You will have to download the updated ROM and manually install it.
lol... You are a lot newer than mine (which I thought was current) and I have NPN25-137-83 (August 1, 2017) and I am completely stock with locked bootloader, never touched it. Are you sure you flashed the right software channel image for your device, retus?
There has only been a couple OTA updates for this device ever, your not missing anything. And BTW, your "modified" status is normal until you get your first OTA, it should then become official. Note that Bootloader Status will ALWAYS be a 2 and will never go back to 0, it isn't possible for anyone but Moto to do that.
beatlesfan5858 said:
Hello! https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
I used that forum to re-lock bootloader and flash stock rom! WHOOHOO, but fastboot is still saying my software status is modified, and I can't tell if I'm receiving OTA updates? How do I check that? I went into settings > About phone > software updates > YOUR SOFTware is up to date.
So I'm wondering if since my fastboot says my firmware is modified, that i'm not receiving OTA. Can someone please confirm they're running un-touched moto g5 plus software, and confirm what latest buildnumber is? U.S. phones only please.
I really need help, I need to receive OTA updates, and I'd assume since it says my "software is up to date" that it is, but I want someone to confirm..
BUILD NUMBER NPNS25.137-33-11
Click to expand...
Click to collapse
I flashed the stock ROM for RETUS (US variant of the G5 Plus), compared it with a with a friend who is on RETUS and on the latest version, and found out that the latest version is build number NPN25.137-83 with the August 1st security patch. When I flashed the stock ROM, my bootloader said I was on official software. If you want me to help you out, I can.
reCoded said:
I flashed the stock ROM for RETUS (US variant of the G5 Plus), compared it with a with a friend who is on RETUS and on the latest version, and found out that the latest version is build number NPN25.137-83 with the August 1st security patch. When I flashed the stock ROM, my bootloader said I was on official software. If you want me to help you out, I can.
Click to expand...
Click to collapse
OK where can I find the stock ROM NPN25.137-83? So the steps would be....
1. Download stock rom
2. oem lock device
3. Flash stock rom/ erase everything?
EDIT: to clarify where I'm at right now, I re-unlocked bd and rooted with Magisk, but have root access gives me nothing but trouble. I have a broken camera now since I've rooted, the app doesn't want to open. No doubt about it, I want to go back to the way everything was normally, receiving OTA updates and have official software. I never should've messed with anything.
OK I downloaded 137-83 from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL
Then tried oem locking and reflashing everything with this link https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
But it didn't want to oem lock, because it says it requires a "signed boot img"
So what should I do from here?
beatlesfan5858 said:
OK I downloaded 137-83 from this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL
Then tried oem locking and reflashing everything with this link https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
But it didn't want to oem lock, because it says it requires a "signed boot img"
So what should I do from here?
Click to expand...
Click to collapse
You'd likely have to wait for the next US retail firmware to be leaked to be able to lock your device.
Given that you've flashed the NPN25.137-92 firmware, you've likely still got the bootloader from that firmware, and so using an older NPN25.137-83 firmware won't permit you to re-lock your bootloader. You cannot downgrade bootloaders (and probably reports a security downgrade error if you try).
Also, now that you likely have a different system to your bootloader, I would caution against taking OTA updates until you've flashed the newer US firmware. I don't know if bootloaders for US firmware are different or the same as other region's firmware, and hopefully someone knows (or can compare firmwares), but mixing builds with different patch levels or regions could lead to a hard brick if taking OTA updates. Be careful.
Thanks I don't want to brick my device. So what should I flash right now? I want to delete everything (root) and go back to stock rom so my camera works! See above for what rom I'm on, it's December security patch. Should I just reflash that one? I won't try to downgrade now. How do I wipe twrp and restore stock recovery and stock everything? Show me the way Jedi master!
Please someone tell me! I really need my phone to be functional.
beatlesfan5858 said:
Thanks I don't want to brick my device. So what should I flash right now? I want to delete everything (root) and go back to stock rom so my camera works! See above for what rom I'm on, it's December security patch. Should I just reflash that one? I won't try to downgrade now. How do I wipe twrp and restore stock recovery and stock everything? Show me the way Jedi master!
Click to expand...
Click to collapse
You're on the December patch? What's your software channel? If it's not RETUS, you've screwed stuff up. The December patch isn't available to US G5 Pluses.
reCoded said:
You're on the December patch? What's your software channel? If it's not RETUS, you've screwed stuff up. The December patch isn't available to US G5 Pluses.
Click to expand...
Click to collapse
my bad! software channel retus android version 7.0 android security patch level nov 1 2017 baseband version m8953_37.46.07.47R Potter NA_Cust kernel version [email protected] #1 mon nov 20 09:32:29 CST 2017 build number NPN25.137-92 hope this helps
beatlesfan5858 said:
my bad! software channel retus android version 7.0 android security patch level nov 1 2017 baseband version m8953_37.46.07.47R Potter NA_Cust kernel version [email protected] #1 mon nov 20 09:32:29 CST 2017 build number NPN25.137-92 hope this helps
Click to expand...
Click to collapse
When your device starts up, does it say "ID: bad key" by chance?
reCoded said:
When your device starts up, does it say "ID: bad key" by chance?
Click to expand...
Click to collapse
edit it says ID:n/a just checked booting it up, that's on the unlocked bootloader screen by the way
beatlesfan5858 said:
edit it says ID:n/a just checked booting it up, that's on the unlocked bootloader screen by the way
Click to expand...
Click to collapse
Alright, you seem to have a similar situation to what I had. I cannot confirm that this will work but if you're willing, you can try it. Doing this fixed my device. My device software status is official and I pass SafetyNet. Again, I'm not sure if this will brick your device or not and I'm not responsible for anything that goes wrong.
First download the NPN25.137-83 firmware here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Now reboot your device to bootloader and type these commands ONE AT A TIME.
Code:
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 boot boot.img
fastboot oem lock
Now reboot and set up your device. After doing that, restart to bootloader and type these commands again, ONE AT A TIME.
Code:
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 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
Hopefully, you should be back to stock and able to receive software updates.
reCoded said:
Alright, you seem to have a similar situation to what I had. I cannot confirm that this will work but if you're willing, you can try it. Doing this fixed my device. My device software status is official and I pass SafetyNet. Again, I'm not sure if this will brick your device or not and I'm not responsible for anything that goes wrong.
First download the NPN25.137-83 firmware here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Now reboot your device to bootloader and type these commands ONE AT A TIME.
Code:
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 boot boot.img
fastboot oem lock
Now reboot and set up your device. After doing that, restart to bootloader and type these commands again, ONE AT A TIME.
Code:
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 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
Hopefully, you should be back to stock and able to receive software updates.
Click to expand...
Click to collapse
Alright i'm going to do everything exactly like you said. I'll be about 15 minutes, will report back. stick around please, and thanks so much for all your help.
Hey, isn't this what previous user warned about? I was on a higher up version of the software so he said I couldn't downgrade?
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (517383 KB)...
OKAY [ 17.424s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.531s
that's when i typed in flash oem and flash sparseimg 0, it's giving me those validation errors.
beatlesfan5858 said:
Hey, isn't this what previous user warned about? I was on a higher up version of the software so he said I couldn't downgrade?
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (517383 KB)...
OKAY [ 17.424s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.531s
that's when i typed in flash oem and flash sparseimg 0, it's giving me those validation errors.
Click to expand...
Click to collapse
It seems so. I was afraid this might of happened. That means that you'll have to wait for RETUS to get the November update or higher for you to relock. Did the commands relock your bootloader or is it still unlocked?
reCoded said:
It seems so. I was afraid this might of happened. That means that you'll have to wait for RETUS to get the November update or higher for you to relock. Did the commands relock your bootloader or is it still unlocked?
Click to expand...
Click to collapse
It wouldn't re-lock because it said the boot img wasn't signed. I know if I try with the current potter version I have, that it will relock, but I was afraid I wouldn't receive OTA updates if I did that.
edit: to clarify, I had downloaded 137-92 from the above link, and managed to relock it before on that version. However I was paranoid about ota updates so i re-unlocked, and re-rooted, which turned out to be a mistake. I'll try re-locking and flashing 137-92, which is the nov 1 2017 security update btw.
hello friends I have the motorola g5 plus xt1680 by telcel. I have the bootloader blocked and I also have many files in memory that I do not want to lose.
I got a security patch which I downloaded and installed correctly, after updating my mistake I let the cell phone completely discharge, reaching the battery at 0%, after this I can not turn on the device stays in the motorola logo.
I have already tried to flash firmwares using adb but I can not mark me error, errors similar to this one:
fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling
gpt.default.xml
FAILED (remote failure)
finished. total time: 0.066s
for more than download firmware images, all of them make me the same error and I can not find the solution on the internet.
I have been several days and can not find a solution, it is very important not to lose my files that I have on my cell phone.
Would any of you help me please?
Have u tried using the Moto Smart Assist to reflash the phone? It should automatically detect the correct firmware for you.
But if you want to flash one of the firmwares you have, leave out the "fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img" commands and the flash should work fine. Apparently the update you took updated the partition tables on your device so you either have to flash without downgrading or flash using the exact firmware that the gpt.bin file is using.
If you need to get your files off first, download TWRP here, and then copy it into the directory where you have fastboot and run
"fastboot flash recovery twrp-3.2.3-1-potter.img" and then scroll down with the vol keys until you get reboot to recovery. (If it doesn't flash correctly you may have to push vol key down to reboot bootloader and try flash again) After inside TWRP, you should be able to use your password to decrypt your data and then use a USB cable to get your things off the phone or take a TWRP backup of your data / internal storage partitions and restore those after a fresh flash.
Drkmatr1984 said:
Have u tried using the Moto Smart Assist to reflash the phone? It should automatically detect the correct firmware for you.
But if you want to flash one of the firmwares you have, leave out the "fastboot flash partition gpt.bin" and "fastboot flash bootloader bootloader.img" commands and the flash should work fine. Apparently the update you took updated the partition tables on your device so you either have to flash without downgrading or flash using the exact firmware that the gpt.bin file is using.
If you need to get your files off first, download TWRP here, and then copy it into the directory where you have fastboot and run
"fastboot flash recovery twrp-3.2.3-1-potter.img" and then scroll down with the vol keys until you get reboot to recovery. (If it doesn't flash correctly you may have to push vol key down to reboot bootloader and try flash again) After inside TWRP, you should be able to use your password to decrypt your data and then use a USB cable to get your things off the phone or take a TWRP backup of your data / internal storage partitions and restore those after a fresh flash.
Click to expand...
Click to collapse
thanks, I had already tried to revive my phone with moto smart assist but the software tells me that my phone is not compatible.
I can install twrp if I have the bootloader blocked or I need to open the bootloader to use twrp? but when I open the bootloader my phone restarts from the factory that will erase all my files
I think I've already got the most recent security patch that is updated, apparently this is:
https://mega.nz/#!jxUEXazJ!TVU8n458ZZwd5TfP12I_uEvslYgGc5vakyUaOeSqMOs
can I install that version on my cellphone without any risk ?
then I can flash it without losing my data by omitting the command fastboot erase userdata or is it more advisable to use the ocpion of twrp to recover my data as you explain my friend?
Thank you very much for the help
Well, if the bootloader is locked, then you can't flash TWRP until you unlock it, which you can't do because you can't get into the system to enable OEM unlocking from developer options. So you're pretty limited to what you can do...
I believe fastboot flashing everything using the exact same firmware as your most recent update, but omitting the gpt.bin, bootloader, and userdata commands would work.
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
july48 said:
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
Click to expand...
Click to collapse
Why don't use ADB pull command to pull the data from device and run the all command of flashing except bootloader and gpt.
riyan65 said:
Why don't use ADB pull command to pull the data from device and run the all command of flashing except bootloader and gpt.
Click to expand...
Click to collapse
I think the problem is he can't get past bootloader so no ADB commands for him to have access to, and his bootloader is locked and since his system won't boot he can't turn on OEM unlocking to unlock it to flash TWRP or something similar to give him ADB commands.
july48 said:
I tried to flash the last ota for the motorola g5 plus and now I can install almost everything but when it comes time to flash the following commands it marks me error:
fastboot erase customize
fastboot erase logo
and now how do I fix that I reboot the device and it keeps giving me boot on the motorola logo
c:\Herramientas ADB\platform-tools>fastboot erase customize
erasing 'customize'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.006s
c:\Herramientas ADB\platform-tools>fastboot erase clogo
erasing 'clogo'...
bootloader Permission denied
FAILED remote failure
finished. total time: 0.005s
and now how can I solve that someone help me
Click to expand...
Click to collapse
Your problems are not related to the errors for "customize" and "clogo". These entries are for customazions made by Moto Maker and it's normal that they fail if you don't have any of these.
If your device doesn't boot you may have downgraded your bootloader in the past.
I have already tried to omit the bootloader and gpt commands, and I still have the same problems only in that part of the code, having the bootloader blocked limits me a lot, I do not know if I have to wait for the firmware of my phone company Telcel to flash it by adb and see if only so I retrieve the phone.
I do not know what else to try if there is any other solution
july48 said:
I have already tried to omit the bootloader and gpt commands, and I still have the same problems only in that part of the code, having the bootloader blocked limits me a lot, I do not know if I have to wait for the firmware of my phone company Telcel to flash it by adb and see if only so I retrieve the phone.
I do not know what else to try if there is any other solution
Click to expand...
Click to collapse
If you have the most recent firmware you don't need to omit the bootloader and gpt commands, and the clogo and customize commands almost always fail, you don't even really need them.
If it's still not booting I'm not sure what else to tell you to try. Someone in another one of my posts suggested trying to boot with "fastboot boot boot.img" and then possibly you could switch on OEM unlocking from the developer options, then reboot, unlock bootloader, and flash again or flash TWRP and use recovery to recover from there.
But I'm not guaranteeing that will do anything other than be stuck at boot logo.