When I flash cm13 or mokee rom sim card doesn't get detected but after i get back to stock moto g3(2015) XT1550 rom(indian dual sim varient) it works fine...any solution?
did you format sd card as external ?? or internal ??
if you format as internal , then format as external .. then remove memory card and keep it again
i dont know if it works.. but its just a suggestion
nandakis4 said:
did you format sd card as external ?? or internal ??
if you format as internal , then format as external .. then remove memory card and keep it again
i dont know if it works.. but its just a suggestion
Click to expand...
Click to collapse
I tried everything, It didn't work in any way... I am not even able to flash to lollipop stock rom for moto g3. It shows <bootloader> prevalidation failed though i have allowed oem unlock and debugging. I dont want marshmallow, it has many bugs like scroll bugs and glitches.. And the bootloader is unlocked too...
akkisid23 said:
I am not even able to flash to lollipop stock rom for moto g3. It shows <bootloader> prevalidation failed though
Click to expand...
Click to collapse
If you are doing downgrade, you don't have to downgrade bootloader (and you musn't downgrade partition!). Just do:
fastboot oem fb_mode_set
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 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
Acetyloaceton said:
If you are doing downgrade, you don't have to downgrade bootloader (and you musn't downgrade partition!). Just do:
fastboot oem fb_mode_set
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 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
Click to expand...
Click to collapse
Oh cool, thank you so much and one more thing is when i flash any ROM on my moto g3 it doesn't detect sim card and when I get back to normal stock ROM its all well and fine..I even tried flashing the modem file(NON-HLOS.bin) that was in the stock ROM zip file but did not work...what do I do?
Related
You can grab your firmware from
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
or
https://github.com/motoxplay/stock
Originally Posted by bodivas
Flash with Wipe:
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 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 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 reboot
Without Wipe:
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18_cid7_subsidy-DEFAULT_CFC_V2.xml.zip
Is it final version of Marshmallow or the soak test version ? I already have Marshmallow ( via a TWRP backup : http://forum.xda-developers.com/showpost.php?p=64210076&postcount=104 ) but it's the soak test version.
Its the same and final
skdubg said:
Its the same and final
Click to expand...
Click to collapse
Do you mean that this TWRP backup ( http://forum.xda-developers.com/show...&postcount=104 ) is actually the final version ?
These 2:
fastboot erase customize
fastboot erase clogo
Arent really necessary, or?
Gesendet von meinem XT1562 mit Tapatalk
Is this file okay to flash for a rooted UK phone with TWRP?
@kyddox Maybe we can/should add the flash instructions to the README.md on github?
heisert said:
These 2:
fastboot erase customize
fastboot erase clogo
Arent really necessary, or?
Gesendet von meinem XT1562 mit Tapatalk
Click to expand...
Click to collapse
are not necessary, like if you want to erase userdata not erase the information from the sd
Enviado desde mi XT1563 mediante Tapatalk
These commands at first didn't work for my Moto X Play (1562) - until I added:
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
Marshmallow RETEU 6.0.1 Firmware!
You may also check my attached flashfile xml for all of the commands that are needed for this firmware.
Can also be found in the firmware package itself. :good:
Then the commands are (with wipe!)
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 system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
Check flash file of your firmware and all the sparsechunk files must be flashed .
I manually unlocked my bootloader and began the process of installing TWRP and then Cyanogenmod. After playing with Cyanogenmod I realized I wasn't missing much, so I tried to go back to Lollipop / Marshmallow only to discover that now every time I boot up my phone it immediately goes to the bootloader, requiring me to manually start my phone. If I try to factory reset it does the same thing. I can reinstall TWRP, but the resulting flash will not allow me to flash custom roms or do much more than click buttons that won't do anything. I cannot get TWRP to export my log to the SD card so I can share the issues. Here is what I have noticed:
1. I have no cache directory according to TWRP.
2. If I try to flash a custom rom, IE Cyanogenmod, it reboots recovery and I don't see an error until I attempt to go back and reflash. Again, I cannot export a log file that will open or allow me to copy it to a different directory.
3. No matter what operation I try to perform, rebooting the device always puts it back to the bootloader. I have to manually start my phone from the menu.
Is there something I should be doing differently? Should I try and flash down to Cyanogenmod 12.1 and then go back to Lollipop? Is the previous upgrade to Marshmallow screwing things up?
Hmm... can you try to flash firmware again? For now skip factory reset in recovery. You can do it later. Flash the latest Marshmallow firmware in bootloader mode:
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 system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
If you want to flash lollipop you must skip partition and bootloader. It might cause bootloop which you will not be able to fix:
fastboot oem fb_mode_set
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
If your phone goes to the bootloader mode every boot, then you didn't close fb_oem mode, when in the bootloader send the command "fastboot oem fb_mode_clear", you should get an OK. Reboot and you should be good to go.
Your phone reboot to system but every reboot it goes first to bootloader or only bootloader is loaded and you can't boot to system? If first then do what @acejavelin said. If system is not loaded then flash firmware again.
<bootloader/ has-slot:system: not found?
I can flash firmware again, but from there it's still acting up. I also cannot do fastboot oem lock.
Now I'm told the storage is in RAW format?
So I unlocked my boot loader, flashed lineage OS and TWRP onto my phone, which was working fine, till I installed a root checker.
It said my phone wasn't rooted and I figured it was because I didn't flash the SuperSu files(it kept boot looping every time I flashed it so I decided to skip it. I figured I'd un root and while re rooting, I'd flash SuperSu through the command prompt to see if it made a difference..Unfortunately I watched a video from some idiot whose method rarely worked(according to the comment section) many people faced the same problem and the video creator failed to answer...many other videos using the same method had the same comments but no one fixed the problem.
The problem is that while typing the following codes, they start to spit out failed messages from the 5th code till the last sparsechunk file(it shows only 6 but my phone stock ROM version has 8, so I add 6 7 and 8)
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
I'm now unable to flash any custom ROM to fix the problem or revert back to the stock ROM using alternate methods such as simply flashing the stock ROM zip...While flashing anything, it says unable to mount cache data and storage. the boot loader says device unlocked, status code 3 but the software status says official, even while I had lineage OS installed...please help and tell me if I need to share more information to find a fix.
In my defence, the last device I NEEDED to root was my Samsung galaxy tab 2
crazykid1234 said:
So I unlocked my boot loader, flashed lineage OS and TWRP onto my phone, which was working fine, till I installed a root checker.
It said my phone wasn't rooted and I figured it was because I didn't flash the SuperSu files(it kept boot looping every time I flashed it so I decided to skip it. I figured I'd un root and while re rooting, I'd flash SuperSu through the command prompt to see if it made a difference..Unfortunately I watched a video from some idiot whose method rarely worked(according to the comment section) many people faced the same problem and the video creator failed to answer...many other videos using the same method had the same comments but no one fixed the problem.
The problem is that while typing the following codes, they start to spit out failed messages from the 5th code till the last sparsechunk file(it shows only 6 but my phone stock ROM version has 8, so I add 6 7 and 8)
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
I'm now unable to flash any custom ROM to fix the problem or revert back to the stock ROM using alternate methods such as simply flashing the stock ROM zip...While flashing anything, it says unable to mount cache data and storage. the boot loader says device unlocked, status code 3 but the software status says official, even while I had lineage OS installed...please help and tell me if I need to share more information to find a fix.
In my defence, the last device I NEEDED to root was my Samsung galaxy tab 2
Click to expand...
Click to collapse
you need to be more specific if you need help, like what command you used in command prompt and what error you are getting in fastboot.
Rohi09 said:
you need to be more specific if you need help, like what command you used in command prompt and what error you are getting in fastboot.
Click to expand...
Click to collapse
As I said, the commands were
1)fastboot flash partition gpt.bin
2)fastboot flash bootloader bootloader.img
3)fastboot flash logo logo.bin
4)fastboot flash boot boot.img
5)fastboot flash recovery recovery.img
6)fastboot flash system system.img_sparsechunk.0
7)fastboot flash system system.img_sparsechunk.1
8)fastboot flash system system.img_sparsechunk.2
9)fastboot flash system system.img_sparsechunk.3
10)fastboot flash system system.img_sparsechunk.4
11)fastboot flash system system.img_sparsechunk.5
12)fastboot flash system system.img_sparsechunk.6
13)fastboot flash system system.img_sparsechunk.7
14)fastboot flash modem NON-HLOS.bin
15)fastboot erase modemst1
16)fastboot erase modemst2
17)fastboot flash fsg fsg.mbn
18)fastboot erase cache
19)fastboot erase userdata
20)fastboot oem lock
21)fastboot reboot
In that order
"(bootloader) preflash validation failed failed (remote failure)" is the error I get in command prompt for command 4 and 6-13
crazykid1234 said:
As I said, the commands were
1)fastboot flash partition gpt.bin
2)fastboot flash bootloader bootloader.img
3)fastboot flash logo logo.bin
4)fastboot flash boot boot.img
5)fastboot flash recovery recovery.img
6)fastboot flash system system.img_sparsechunk.0
7)fastboot flash system system.img_sparsechunk.1
8)fastboot flash system system.img_sparsechunk.2
9)fastboot flash system system.img_sparsechunk.3
10)fastboot flash system system.img_sparsechunk.4
11)fastboot flash system system.img_sparsechunk.5
12)fastboot flash system system.img_sparsechunk.6
13)fastboot flash system system.img_sparsechunk.7
14)fastboot flash modem NON-HLOS.bin
15)fastboot erase modemst1
16)fastboot erase modemst2
17)fastboot flash fsg fsg.mbn
18)fastboot erase cache
19)fastboot erase userdata
20)fastboot oem lock
21)fastboot reboot
In that order
"(bootloader) preflash validation failed failed (remote failure)" is the error I get in command prompt for command 4 and 6-13
Click to expand...
Click to collapse
Skip the bootloader and gpt.bin files. It should flash successfully​. Preflash validation failure occurs when you're flashing an older version of firmware on a newer one. Skip those two files and you should be good.
crazykid1234 said:
As I said, the commands were
1)fastboot flash partition gpt.bin
2)fastboot flash bootloader bootloader.img
3)fastboot flash logo logo.bin
4)fastboot flash boot boot.img
5)fastboot flash recovery recovery.img
6)fastboot flash system system.img_sparsechunk.0
7)fastboot flash system system.img_sparsechunk.1
8)fastboot flash system system.img_sparsechunk.2
9)fastboot flash system system.img_sparsechunk.3
10)fastboot flash system system.img_sparsechunk.4
11)fastboot flash system system.img_sparsechunk.5
12)fastboot flash system system.img_sparsechunk.6
13)fastboot flash system system.img_sparsechunk.7
14)fastboot flash modem NON-HLOS.bin
15)fastboot erase modemst1
16)fastboot erase modemst2
17)fastboot flash fsg fsg.mbn
18)fastboot erase cache
19)fastboot erase userdata
20)fastboot oem lock
21)fastboot reboot
In that order
"(bootloader) preflash validation failed failed (remote failure)" is the error I get in command prompt for command 4 and 6-13
Click to expand...
Click to collapse
no I asked about the command you used to install SuperSU. anyway if you are getting preflash validation failed error then just skip the first 2 lines of command, ie. gpt and bootloader, and use the rest. do a factory reset from twrp or stock recovery before flashing anyway.
.
I didn't use any command for SuperSu...before I got to that part, the phone bricked....
I'll try the methods you've mentioned and will get back soon!
Got it to work!!! but could you please explain why whenever I flash SuperSu, either through a ZIP or through the TWRP option when exiting the recovery, my phone bootloops?
It depends on the version of TWRP and superSU you are flashing ..... Use of latest twrp version and super su version does not results in bootloop if flashed properly ... If u want to root ur device again u can download the SuperSU zip file from attachment ...
Instructions to root via twrp recovery
First flash ur room and gapp ...
Reboot ur device ... Complete the setup
Then reboot to recovery ... Flash the super su zip file ... Wipe cache and dalvik cache ... And reboot u will succeed ??? Happy Flashing
Got it to work! Thanks a lot guys!
Hi guys!
I have got the XT1621 and i have a lot of lag when i flash a nougat firmware through fastboot
But when i install marshmallow (23.4) and i update by ota to nougat (-14) it is very smooth!!
The problem is that i updated by induced ota from -14 to -14-4 nougat
The real problem is that the bootloader updated to .05 version and i cant flash marshmallow and update by ota to -14 because it would end in hardbrick!!
What can i do to downgrade??
If i hardbricked my moto g4 with intention, could i flash the -14 bootloader blankflash file? It could be a way to downgrade the bootloader
Any other idea of what can i do?
I recall you can downgrade to MM if you wish, just do not flash the GPT and bootloader partitions. Leave them as they are. That way, you'll avoid a hard brick (but you'll need to flash the latest firmware to re-lock your device).
Of course, you'll need an unlocked bootloader for this to work, and the appropriate stock ROM (a copy is here https://mirrors.lolinet.com/firmware/moto/athene/official/RETAIL/) - I see XT1622 MPJ24.139-23.4 which matches what you had before (though I strongly recommend double checking it's the right firmware).
Then follow this guide to downgrade: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
If you're unable to download the script that's mentioned in the guide, you may try the following fastboot commands (note the absence of the locking, GPT and bootloader commands).
Code:
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 reboot
This procedure will wipe your device and should revert your device to an MM baseband and system. As always, back up your data, move it off your device until you're done flashing.
August 1 security update is out
RIVER_RETAIL_9.0_PPOS29.114-134-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
== Installation ==
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash partition 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 dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
If you don't want to clear your existing data, you can skip fastboot erase userdata
I used this method to update a couple days ago as i got sick of the update telling me it failed. No issues so far. Had to re-root with magisk after but... such is life.
I can also confirm this works
Stock boot img
I upgraded to 114 -134-4. I can't download the firmware file so I don't have a stock boot.img file to patch with Magisk. I cannot find a download link for 114-134-4. I don't know how to extract the boot img. If anybody could provide me with the stock boot img. For 114-134-4 I would really appreciate it.
fwr6236437 said:
I upgraded to 114 -134-4. I can't download the firmware file so I don't have a stock boot.img file to patch with Magisk. I cannot find a download link for 114-134-4. I don't know how to extract the boot img. If anybody could provide me with the stock boot img. For 114-134-4 I would really appreciate it.
Click to expand...
Click to collapse
from PPOS29.114-134-4
boot.img
Thank you so much! Works great!
Thanks for this write up and break down. It saved my sanity. I havent been with Android since the Nexus 5 and picked up the G7 on a BF sale and decided to try and root it and use custom ROMs. Quick story I jacked it up bad so just wanted to get it back to stock and even then was having issues. This worked. Much appreciated.
Clutch
This saved my life because this was my first time rooting and i got stuck in a bootloop trying to root my moto g7 with magisk. Im so glad i found this.