Related
IMP : You need to be on 5.x.x Rom
Download official CM12 firmware image files.
Link : http://builds.cyngn.com/cyanogen-os/tomato/12.0-YNG1TAS0W0-tomato/56deeca328/cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Download and install yureka drivers so that your pc can detect your phone.
Link : http://forum.xda-developers.com/yureka/help/fix-yureka-fastboot-detection-issues-t3014794
credits to @[email protected]
Download adb and mfastboot files.
Link : https://drive.google.com/folderview?id=0B05Crz57q4zgZE1aVW5FT1RsUUU&usp=sharing
Extract mfastboot files and factory images to a folder.
Open command prompt there.
Reboot your yureka into fastboot mode.
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
commands :
mfastboot -i 0x1ebf oem unlock
mfastboot -i 0x1ebf flash boot boot.img
mfastboot -i 0x1ebf flash system system.img
mfastboot -i 0x1ebf flash userdata userdata.img
mfastboot -i 0x1ebf flash recovery recovery.img
mfastboot -i 0x1ebf flash modem NON-HLOS.bin
mfastboot -i 0x1ebf flash rpm rpm.mbn
mfastboot -i 0x1ebf flash sbl1 sbl1.mbn
mfastboot -i 0x1ebf flash tz tz.mbn
mfastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
After successful execution, disconnect yureka from pc and reboot.
If every command you entered was successfully executed, your phone will reboot into stock CM12 firmware !
Please don't do this if your are on 4.4.x Rom. It will hard brick your device.
Hit thanks, if helped ! :good:
mfastboot is necessary for flashing Motorola firmwares; standard fastboot is sufficient for Yureka.
Thank you man!!! Great Help
you are a life saver.
Did all you mentioned and my device returned to normal stage
prince.d.emperor said:
IMP : You need to be on 5.x.x Rom
Download official CM12 firmware image files.
Link : http://builds.cyngn.com/cyanogen-os/tomato/12.0-YNG1TAS0W0-tomato/56deeca328/cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Download and install yureka drivers so that your pc can detect your phone.
Link : http://forum.xda-developers.com/yureka/help/fix-yureka-fastboot-detection-issues-t3014794
credits to @[email protected]
Download adb and mfastboot files.
Link : https://drive.google.com/folderview?id=0B05Crz57q4zgZE1aVW5FT1RsUUU&usp=sharing
Extract mfastboot files and factory images to a folder.
Open command prompt there.
Reboot your yureka into fastboot mode.
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
commands :
mfastboot -i 0x1ebf oem unlock
mfastboot -i 0x1ebf flash boot boot.img
mfastboot -i 0x1ebf flash system system.img
mfastboot -i 0x1ebf flash userdata userdata.img
mfastboot -i 0x1ebf flash recovery recovery.img
mfastboot -i 0x1ebf flash modem NON-HLOS.bin
mfastboot -i 0x1ebf flash rpm rpm.mbn
mfastboot -i 0x1ebf flash sbl1 sbl1.mbn
mfastboot -i 0x1ebf flash tz tz.mbn
mfastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
After successful execution, disconnect yureka from pc and reboot.
If every command you entered was successfully executed, your phone will reboot into stock CM12 firmware !
Please don't do this if your are on 4.4.x Rom. It will hard brick your device.
Hit thanks, if helped ! :good:
Click to expand...
Click to collapse
So by this restore we will go to kitkat 4.4.4??
kenil89 said:
So by this restore we will go to kitkat 4.4.4??
Click to expand...
Click to collapse
No, you will go to official CM12 !
prince.d.emperor said:
No, you will go to official CM12 !
Click to expand...
Click to collapse
Okie...
Does the following step will unbrick my soft brick yureka device??
Bob Parihar said:
Does the following step will unbrick my soft brick yureka device??
Click to expand...
Click to collapse
Only if you have officially or manually upgraded to CM12.
Please help sir
Will this method work if I have installed CM12 64BIT CUSTOM ROM? AND WILL WE GET OTA UPDATES AS NORMAL?
AND lastly can u say me why i always get "Android is starting" after every boot, when I was in CM 12 CUSTOM ROM WITH 64BIT MINIMAL GAPPS?
jogson said:
Will this method work if I have installed CM12 64BIT CUSTOM ROM? AND WILL WE GET OTA UPDATES AS NORMAL?
AND lastly can u say me why i always get "Android is starting" after every boot, when I was in CM 12 CUSTOM ROM WITH 64BIT MINIMAL GAPPS?
Click to expand...
Click to collapse
Follow this method only if you have officially/manually upgraded to CM12. This method requires updated bootloader. Flashing these on old bootloader may brick your device !
I'm on cm12.1 by varun chitre how can i get back to cm12.
not able to find system.imf file
prince.d.emperor said:
IMP : You need to be on 5.x.x Rom
Download official CM12 firmware image files.
Link : http://builds.cyngn.com/cyanogen-os/tomato/12.0-YNG1TAS0W0-tomato/56deeca328/cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Download and install yureka drivers so that your pc can detect your phone.
Link : http://forum.xda-developers.com/yureka/help/fix-yureka-fastboot-detection-issues-t3014794
credits to @[email protected]
Download adb and mfastboot files.
Link : https://drive.google.com/folderview?id=0B05Crz57q4zgZE1aVW5FT1RsUUU&usp=sharing
Extract mfastboot files and factory images to a folder.
Open command prompt there.
Reboot your yureka into fastboot mode.
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
commands :
mfastboot -i 0x1ebf oem unlock
mfastboot -i 0x1ebf flash boot boot.img
mfastboot -i 0x1ebf flash system system.img
mfastboot -i 0x1ebf flash userdata userdata.img
mfastboot -i 0x1ebf flash recovery recovery.img
mfastboot -i 0x1ebf flash modem NON-HLOS.bin
mfastboot -i 0x1ebf flash rpm rpm.mbn
mfastboot -i 0x1ebf flash sbl1 sbl1.mbn
mfastboot -i 0x1ebf flash tz tz.mbn
mfastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
After successful execution, disconnect yureka from pc and reboot.
If every command you entered was successfully executed, your phone will reboot into stock CM12 firmware !
Please don't do this if your are on 4.4.x Rom. It will hard brick your device.
Hit thanks, if helped ! :good:
Click to expand...
Click to collapse
not able to find system.img file
seshadri.1995 said:
I'm on cm12.1 by varun chitre how can i get back to cm12.
Click to expand...
Click to collapse
I was also on custom rom and I wanted to revert back to stock cm 12.........this method helped me and I have successfully reverted back.....thanks to prince.d.emperor
I've already done this method when my yureka was in bootloop after updating official cm12 by OTA. Prince.d.emperor suggested this method to me and it worked. Now I've flashed custom cm12.1 and i want to revert back. Somebody saying that we want to flash "stock recovery" then only we need to flash official cm12. Is it necessary to flash stock recovery ???
seshadri.1995 said:
I've already done this method when my yureka was in bootloop after updating official cm12 by OTA. Prince.d.emperor suggested this method to me and it worked. Now I've flashed custom cm12.1 and i want to revert back. Somebody saying that we want to flash "stock recovery" then only we need to flash official cm12. Is it necessary to flash stock recovery ???
Click to expand...
Click to collapse
Nope !
Just flash the stock firmware. It's enough.
prince.d.emperor said:
Nope !
Just flash the stock firmware. It's enough.
Click to expand...
Click to collapse
Thanks bro... It worked...:thumbup:
:fingers-crossed::fingers-crossed::fingers-crossed:Awesome...
all is done very well
Thank you...
EiiiiiiiYUUUUUUU...:good::good::good:
I reverted back to official firmware but unable install any custom recovery. If I flash cwm or twrp, the existing stock recovery also gets removed and none of the other gets installed. Plz help I need root so bad...
Sent from my AO5510 using XDA Free mobile app
I've done this method from cm11 . And my device was hard bricked. What can I do now...!!!! Please help me....
s333hacker said:
I've done this method from cm11 . And my device was hard bricked. What can I do now...!!!! Please help me....
Click to expand...
Click to collapse
Can't help u.
In the post, it is written that u need to be on 5.x.x ROM before doing those steps.
Perhaps this guide will help fellow YU's users who want to downgrade their YU from Lollipop to KitKat (OR FROM OTHER ROMs UNDER THE SAME PARTITION TABLE):
Download KitKat fastboot images from HERE.
Download fastboot.zip from HERE.
Extact all zips in ONE EMPTY FOLDER.
Open "Terminal Window" from the folder where you extracted all the zip files (right click your mouse and choose "Open command window here"):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Put your phone into fastboot mode (disconnect the phone from PC, turn off the phone, and connect the phone to PC WHILE PRESSING VOLUME UP BUTTON).
After the phone is connected go to the "Terminal Window" you have opened previously, type all the command below (ONE LINE AT A TIME) and make sure you get an "OKAY" feedback:
Code:
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf erase modem
fastboot -i 0x1ebf erase boot
fastboot -i 0x1ebf erase recovery
fastboot -i 0x1ebf erase aboot
fastboot -i 0x1ebf erase abootbak
fastboot -i 0x1ebf erase hyp
fastboot -i 0x1ebf erase hypbak
fastboot -i 0x1ebf erase rpm
fastboot -i 0x1ebf erase rpmbak
fastboot -i 0x1ebf erase sbl1
fastboot -i 0x1ebf erase sbl1bak
fastboot -i 0x1ebf erase tz
fastboot -i 0x1ebf erase tzbak
fastboot -i 0x1ebf format system
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf flash modem NON-HLOS.bin
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash sbl1bak sbl1.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash abootbak emmc_appsboot.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash rpmbak rpm.mbn
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash tzbak tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash hypbak hyp.mbn
fastboot -i 0x1ebf flash boot boot.img
fastboot -i 0x1ebf flash recovery recovery.img
fastboot -i 0x1ebf flash system system.img
fastboot -i 0x1ebf reboot-bootloader
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf reboot
Welcome back to KitKat, easy wasn't it.
Hi Quakze, could you post this procedure at YU's official forum website, as I don't have access there. I'm hopping that more YU's owner will help our mission in forcing official from YU Televentures to release all source code, include all Qualcomm signed mbn files.
------------------- Edit ----------------------
Since a lot YU's users in this thread have been insisting for a simple FLASH_ALL.bat file, so here is it. Extract it to the same folder you extracted fastboot.zip and KitKat fastboot images. However, please keep in mind that I don't recommend to use the bat file, and I am not responsible for bricked devices.
Does this really work?
rahulsingh616 said:
Does this really work?
Click to expand...
Click to collapse
Yes, of course, but please do the guide in order.
is bootloader unlock is mandatory??
Anybody tried that?!
will it hard brick the device??
i heard that infact i myself hard bricked before while downgrading from lollipop to kitakt..
jogson said:
i heard that infact i myself hard bricked before while downgrading from lollipop to kitakt..
Click to expand...
Click to collapse
Just tried it works perfect thanks bro @tirta.agung
Uh a few screenshots of this working would be better since most official mods of yuforums advise against using fastboot when upgrading from KitKat to lollipop and downgrading from lollipop to KitKat. If this works then it is really great work. Thank you. I can now try lollipop and go back to KitKat if not happy with it.
Sent from tomato using Tapatalk
baggu1984 said:
is bootloader unlock is mandatory??
Click to expand...
Click to collapse
Yes, you can't flash anything with a lock bootloader.
3andala said:
Just tried it works perfect thanks bro @tirta.agung
Click to expand...
Click to collapse
Thanks 3andala, I'm happy to help.
roy92 said:
Uh a few screenshots of this working would be better since most official mods of yuforums advise against using fastboot when upgrading from KitKat to lollipop and downgrading from lollipop to KitKat. If this works then it is really great work. Thank you. I can now try lollipop and go back to KitKat if not happy with it.
Click to expand...
Click to collapse
What kind of screenshota that you need? I'll be happy if I could help you.
tirta.agung said:
Thanks 3andala, I'm happy to help.
What kind of screenshota that you need? I'll be happy if I could help you.
Click to expand...
Click to collapse
It works for 3andala. I guess that is proof enough. Thank you for finding a clean way to revert to KitKat.
I guess you could upload desktop screenshot of the cmd window with executed commands. A photo of device first running on Lollipop and then on KitKat would be great.
Also did you try flashing cm 12 ota again after going back to KitKat?? Does it work??
Sent from tomato using Tapatalk
roy92 said:
It works for 3andala. I guess that is proof enough. Thank you for finding a clean way to revert to KitKat.
I guess you could upload desktop screenshot of the cmd window with executed commands. A photo of device first running on Lollipop and then on KitKat would be great.
Also did you try flashing cm 12 ota again after going back to KitKat?? Does it work??
Sent from tomato using Tapatalk
Click to expand...
Click to collapse
Hahahahahah, you won't believe this, but I'll post the screenshots tomorrow.
tirta.agung said:
Hahahahahah, you won't believe this, but I'll post the screenshots tomorrow.
Click to expand...
Click to collapse
Thank you[emoji5]
It's just that many bricked devices are floating around and not being able to properly revert back and forth to 32 bit builds and 64 bit builds is the only reason I haven't upgraded to lollipop yet.
KitKat is still the best with full xposed support and arm v7 is better supported by media players.
Sent from tomato using Tapatalk
Request
Can you make a file like flash-all.bat to do everything automatically other than typing the commands?
Help appreciated
onlyoneaamir said:
Can you make a file like flash-all.bat to do everything automatically other than typing the commands?
Help appreciated
Click to expand...
Click to collapse
It's very easy to do so. But not recommended. Read OP's post again. You need to get OK confirmation after every step before moving on to next. So suppose a command to erase system fails but the script proceeds to flash system image it might brick your device.
The chances of this happening are very very low. But it is important that you follow the step of commands exactly and also get OK confirmation that every command is successfully executed.
Edit: To quote the OP:
tirta.agung said:
[*]After the phone is connected go to the "Terminal Window" you have opened previously, type all the command below (ONE LINE AT A TIME) and make sure you get an "OKAY" feedback
Click to expand...
Click to collapse
Sent from tomato using Tapatalk
Points to remember?
I'm running official cm12 updated via ota with xposed . I have a nandroid backup . If something goes wrong can i restore using the backup. What are the chances of HARD bricking?
Many people have hard bricked the phone by downgrading ( the whole 64 bit, 34 bit confusion)
Awesome!
@tirta.agung
thanks man, works like a charm!! i dont think i'll be switching back until CM12 gets bug-ridden officially!
onlyoneaamir said:
Can you make a file like flash-all.bat to do everything automatically other than typing the commands?
Help appreciated
Click to expand...
Click to collapse
Nope, i don't think so. But, if you want to try it for yourself, just copy all commands to a text editor, for instance notepad or notepad++, and save it as flash-all.bat.
technowizard99 said:
I'm running official cm12 updated via ota with xposed . I have a nandroid backup . If something goes wrong can i restore using the backup. What are the chances of HARD bricking?
Click to expand...
Click to collapse
No, you can't use your CM12 (Lollipop) nand backup on CM 11 (kitkat), it will brick your YU.
technowizard99 said:
Many people have hard bricked the phone by downgrading ( the whole 64 bit, 34 bit confusion)
Click to expand...
Click to collapse
Just use my guide to downgrade your Lollipop back to Kitkat, but be sure to read carefully the guide and do the steps orderly. It works for me, and many others have also confirmed my method. By the way, I'm the OP of this THREAD, so I know what I'm doing.
kane111 said:
@tirta.agung
thanks man, works like a charm!! i dont think i'll be switching back until CM12 gets bug-ridden officially!
Click to expand...
Click to collapse
Thank you, glad that I could help.
Can I copy paste the commands?
I'm just being paranoid. But can i copy paste the commands?
technowizard99 said:
I'm just being paranoid. But can i copy paste the commands?
Click to expand...
Click to collapse
yes you can, i did the same!
Hello friends I have stock 7.1.1 fo mzp got from local service station it's around 3 GB data there
So how can I flash it and relock bootloader ? Is it possible ?
Yes. Just flash your official FW, go to fastboot in your phone, go to FW folder with ADB and run this step by step:
Code:
#!/bin/bash
set -e
# Block 1
fastboot getvar securestate #securestate: flashing_unlocked
fastboot getvar max-sparse-size #268435456
fastboot oem fb_mode_set
fastboot flash partition gpt.bin # исключить при даунгрейде
fastboot flash bootloader bootloader.img # исключить при даунгрейде
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 oem oem.img
fastboot erase carrier
fastboot erase DDR
# fastboot erase cache
# fastboot erase userdata
fastboot oem fb_mode_clear
# Block 2
fastboot reboot-bootloader
# Block 3
fastboot oem lock # This command erases all user data. Please re-run this command to continue.
fastboot oem lock # Flash valid Android images now. Then re-run this command to lock
# Still require signed boot.img
# Still require signed system.img and/or oem.img
fastboot flash boot boot.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 oem oem.img
# Let's finish it!
fastboot oem lock # Lock complete! Flash signed images after reboot if needed
fastboot reboot
Just look how many system.img_sparsechunk are in your FW.
Please - upload your FW - I`ll write manual for it )
Here are original manual (Russian)
You mean you got an official, signed image from Motorola? How do you get it?
What software channel is it?
Can you upload it?
Thanks!
Please share with us.. It will help a lot of members here with their phone.
dyonissos said:
You mean you got an official, signed image from Motorola? How do you get it?
What software channel is it?
Can you upload it?
Thanks!
Click to expand...
Click to collapse
Hello sir
I just attached the screenshot of my Data file
ROM_HUNTER said:
Please share with us.. It will help a lot of members here with their phone.
Click to expand...
Click to collapse
Hey
I am working on that with some senior member once it will succeed I share data link of mega
St.Noigel said:
Yes. Just flash your official FW, go to fastboot in your phone, go to FW folder with ADB and run this step by step:
Just look how many system.img_sparsechunk are in your FW.
Please - upload your FW - I`ll write manual for it )
Here are original manual (Russian)
Click to expand...
Click to collapse
That's the image of data files
Is there 12 img_sparsechunk
Hey Guys,
I recently had hardbricked my potter device.. Was unable to flash any rom, not even stock rom and I didnt find any thread in this forum which could have helped me.
I unbricked my device, flashed the stock rom and locked the bootloader,
The following steps will also get you unbrick your device... So, I would like to share the steps with all of you.
Note that this isnt only for unbricking, this can be done by any user who wants to flash stock rom and lock their bootloader.
Step 1: Download your potter rom from the following link: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
"POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" download the following zip file.
Step 2: Download Minimal adb and fastboot from the following link: https://androidfilehost.com/?fid=745425885120698566
Step 3: Install Minimal adb and fastboot and extract the downloaded rom to the same folder where you have installed Minimal And fastboot package.
Step 4: After extracting open command prompt in that folder (where you have extracted the rom/ the adb and fastboot folder)
Step 5: Now boot your phone into your bootloader by pressing volume down+ power button at the same time.
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
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 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
Step 8: This will completely wipe your data and install stock 7.0 OS on your potter device. Note that this does not lock your bootloader.
Step 9: Boot your device to check if it boots and if it works.... now if you want to lock your bootloader move to the next step.
Step 10: Reboot again into your bootloader.
Step 11: Again follow the step 4, step 5 and step 6.
Step 12: Now paste the following commands in the command prompt:
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
Step 13: Reboot your device...
In this way you will be able to move to stock rom and lock your bootloader..
Please do comment if this works for you too and if you find any issues...
Thank you!!
All the Best!!:fingers-crossed::fingers-crossed::good::good:
rishivg said:
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
Click to expand...
Click to collapse
The quoted lines are redundant (surely they gave you an error since they don't exist in the G5+ firmware)
Otherwise, pretty standard Moto stuff... interesting that in 5th gen stuff you can lock after only flashing system sparsechunks, almost all previous devices required a complete flash with wipe to relock. https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ is another good source for stock factory ROM's (it is the official repo of FirmwareTeam), and Minimal ADB and Fastboot has a lots of "hacks" out there, so it is best to only reference the original source: https://forum.xda-developers.com/showthread.php?t=2317790
I am extremely familiar with previous Moto device, but am curious on this device what is the bootloader status number after relocking with this method and do you still get the unlocked warning screen after relocking like on previous Moto devices?
Hi,
Great if this guide works (not tested by me). However, it sounds viable. :good:
In any case, I suggest to put the original device and retail versions witht the link of the firmware. For example:
- XT1680 & retus: "POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
This is necessary. For example my is XT1685 and RETEU, then this file is not for me!
Not working. Its says cant be downgrade.
No does not work with the XT 1685 and reteu
surjeet.vishwas said:
Not working. Its says cant be downgrade.
Click to expand...
Click to collapse
what is your model number?
rishivg said:
what is your model number?
Click to expand...
Click to collapse
Xt1686 but i download another stock rom
surjeet.vishwas said:
Xt1686 but i download another stock rom
Click to expand...
Click to collapse
okay that is why it gave you error, try with the file that is mentioned in the post
This only works if you are on a previous or the exact same build. If you have already installed the August ota atm you can't relock the bootloader.
Gingernut78 said:
This only works if you are on a previous or the exact same build. If you have already installed the August ota atm you can't relock the bootloader.
Click to expand...
Click to collapse
yes exactly! you ll need to flash the whole previous build again...
rishivg said:
yes exactly! you ll need to flash the whole previous build again...
Click to expand...
Click to collapse
You can flash a previous build but it won't lock the bootloader that is the problem.
Gingernut78 said:
You can flash a previous build but it won't lock the bootloader that is the problem.
Click to expand...
Click to collapse
it will
rishivg said:
it will
Click to expand...
Click to collapse
The firmware will only re-lock your bootloader in that case if it's of the same or newer patch level as your bootloader. Older firmwares, as Gingernut78 pointed out, will get you back to stock, but if you're on the August 2017 patch level (and your bootloader is at the August 2017 patch level as well), you need a August 2017 or later stock ROM to re-lock your bootloader.
rishivg said:
Hey Guys,
I recently had hardbricked my potter device.. Was unable to flash any rom, not even stock rom and I didnt find any thread in this forum which could have helped me.
I unbricked my device, flashed the stock rom and locked the bootloader,
The following steps will also get you unbrick your device... So, I would like to share the steps with all of you.
Note that this isnt only for unbricking, this can be done by any user who wants to flash stock rom and lock their bootloader.
Step 1: Download your potter rom from the following link: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
"POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" download the following zip file.
Step 2: Download Minimal adb and fastboot from the following link: https://androidfilehost.com/?fid=745425885120698566
Step 3: Install Minimal adb and fastboot and extract the downloaded rom to the same folder where you have installed Minimal And fastboot package.
Step 4: After extracting open command prompt in that folder (where you have extracted the rom/ the adb and fastboot folder)
Step 5: Now boot your phone into your bootloader by pressing volume down+ power button at the same time.
Step 6: Type the following in your command prompt: fastboot devices
If it detects your device move to the next step, if it does not then you will have to install drivers for your device.
Step 7: Now Copy the following code and paste it to your command prompt:
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 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
Step 8: This will completely wipe your data and install stock 7.0 OS on your potter device. Note that this does not lock your bootloader.
Step 9: Boot your device to check if it boots and if it works.... now if you want to lock your bootloader move to the next step.
Step 10: Reboot again into your bootloader.
Step 11: Again follow the step 4, step 5 and step 6.
Step 12: Now paste the following commands in the command prompt:
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
Step 13: Reboot your device...
In this way you will be able to move to stock rom and lock your bootloader..
Please do comment if this works for you too and if you find any issues...
Thank you!!
All the Best!!:fingers-crossed::fingers-crossed::good::good:
Click to expand...
Click to collapse
thank you so much you safe my life:good
rishivg said:
yes exactly! you ll need to flash the whole previous build again...
Click to expand...
Click to collapse
Please let me know how. I'm on August security patch. Xt1686 67 5 build indian version. I can flash only 67 5 build stock rom. When i try flashing older stock roms, it says bootloader version downgrade. Please please tell me how i can fully go back to stock.
ksvirdi105 said:
Please let me know how. I'm on August security patch. Xt1686 67 5 build indian version. I can flash only 67 5 build stock rom. When i try flashing older stock roms, it says bootloader version downgrade. Please please tell me how i can fully go back to stock.
Click to expand...
Click to collapse
dont flash the bootloader! ignore that command and report!:fingers-crossed:
rishivg said:
dont flash the bootloader! ignore that command and report!:fingers-crossed:
Click to expand...
Click to collapse
Are you sure it will work perfectly. No bricking and stuff?? which commands should i skip.
And once i flash it will i be able to get ota to august patch and relock?
ksvirdi105 said:
Are you sure it will work perfectly. No bricking and stuff??
Click to expand...
Click to collapse
it wont brick your device.. try it out:good:
rishivg said:
it wont brick your device.. try it out:good:
Click to expand...
Click to collapse
Once i flash it will i be able to get ota updates.
ksvirdi105 said:
Once i flash it will i be able to get ota updates.
Click to expand...
Click to collapse
lock your bootloader, you ll get updates but not security updates.. I dont know why? Need some help from developers
Can anybody provide with the flashing instruction for moto g5
yolomonkey said:
Can anybody provide with the flashing instruction for moto g5
Click to expand...
Click to collapse
Assuming you have fastboot installed on your pc
Download firmware and unzip to where you have fastboot
Open command prompt at fastboot location with firmware
type the following although I have marked lines that you should not use unless you have to as flashing wrong firmware can damage your device
Code:
fastboot oem fb_mode_set Only required if you wish to relock bootloader - if not skip it
fastboot flash partition gpt.bin Do not use unless you want to repartition your device - incorrect file will damage your phone
fastboot flash bootloader bootloader.img Do not use unless you want to replace the bootloader - flashing wrong file will hard brick
fastboot flash logo logo.bin No need to flash if you are going to flash a custom rom after and have already flashed a modded version
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 Will erase everything on internal storage but you need to do it
fastboot erase customize Not sure about this - might be for other device
fastboot erase clogo Not sure about this - might be for other device
fastboot oem fb_mode_clear Only required to relock bootloader if you used the very first command
fastboot reboot
NOt working
My device keeps booting to the recovery
even though i flashed my recovery. it boots to twrp
yolomonkey said:
My device keeps booting to the recovery
even though i flashed my recovery. it boots to twrp
Click to expand...
Click to collapse
have you read the FAQs on my twrp thread because the answer is there (assuming you have flashed a custom rom and can boot it through the bootloader by selecting start)
TheFixItMan said:
have you read the FAQs on my twrp thread because the answer is there (assuming you have flashed a custom rom and can boot it through the bootloader by selecting start)
Click to expand...
Click to collapse
could you please link it. I am so grateful for you replying this fast
yolomonkey said:
could you please link it. I am so grateful for you replying this fast
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
FAQs are on 2nd post