Related
Hello,
I am new to flashing roms, but today I tried flashing cm12(cm-12-20150224-NIGHTLY-falcon.zip) on my moto g XT1032. I installed clockworkmod recovery and made a backup of my stock rom. I then coppied the buckup to my computer and deleted it from my moto g, and that was a huge mistake. I then wipped the data, cache and the dalvik cache and installed the new rom. After 10 minutes it was still showing the cm logo so I waited an other 10 minutes but nothing changed. So I think it is in a boot loop. I can still boot into fastboot and recovery but I cant get my device to show up on my computer in ADB fastboot works fine. I really hope that you can help me.
I fixed it because of this:
I cant place links yet sorry
I updated my Moto G (XT1032) to the new Lollipop (5.0.1, I think). I left the phone plugged in to let it download and install, and when I came back to it after about a half hour, the phone was displaying the screen with 'Google' and an unlocked padlock on it. I left it for another 20 minutes or so, but it stayed on the same screen. I couldn't power it off at all, every time I tried to, the screen would turn off, but then come back on and vibrated once, only to go back to the padlock.
I ended up going through the Flashboot menu and cleared the Cache Partition, but that made no difference. Also tried a factory reset, but that seemed to make no difference. Currently, the phone is still sitting at the padlock screen.
The Flashboot menu says that the phone is unlocked, but I have no memory of doing this. Maybe it's something to do with the update failing?
Just wondering if anyone has some advice on how to proceed with this.
5.0-lollipop motorola
shareimprove this question
asked Dec 18 '14 at 5:02
thechunksalot
62
add a comment
1 Answer
active oldest votes
up vote 0 down vote
Well, there are two ways to fix this one out:
Requirements:
You need to have a custom recovery (CWM/TWRP) installed
You are going to require Stock firmware zip file for Moto G XT1028, XT1031, XT1032, XT1033 and XT1034 which can be downloaded over here
ADB and Fastboot
Method 1:
Boot your phone into custom recovery mode. Recovery will have adb on by default, so leave recovery as it is.
Connect your phone to your PC and open command prompt and issue the command: cd directory-with-adb.exe-and-fastboot.exe
Now, issue the command: adb devices. If Moto G drivers have installed properly, the phone will show up. If not, get it over here and install it over your device
Now, from recovery wipe /data and media
Open command prompt and execute: adb push rom.zip /sdcard/rom.zip It will take some time to install the ROM. If you face a not working SIM or WiFi, extract the downloaded ROM zip file and navigate to extracted firmware folder using cmd and issue:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Method 2:
Extract the downloaded firmware file to a folder.
Download and extract mfastboot and copy its content to the same folder where the extracted firmware files.
Reboot your Moto G into the Bootloader Mode. To do so, turn off your phone and then press and hold the Volume (-) and Power buttons simultaneously for a few seconds.
Connect your phone to your PC via USB cable.
Now, launch a command window from inside the firmware folder (click shift key, right click and select open command window here option).
In the command window, issue the following commands one by one:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Note: If firmware includes four ‘system.img_sparsechunk’ or you do not want to erase the userdata, you can modify the command. You have now successfully installed a fresh ROM on your Moto G and the phone the phone should work as usual.
This is a tangent to the issue I had Situated HERE. I am seriously giving up on hope and want help for the love of god. Semester is approaching and I need a functioning mobile
After "fixing" my isssue and being on Lolipop 5.0.2, I realised that my SU binary wasn't present, So I reboot into recovery to realise that CWM isn't present anymore.
Not a big issue, I plug it in and flash TWRP onto it using fasboot commands.
Now i go into recovery and Install Superuser.zip trough TWRP. Then I decide to make a backup of everything. Afterwards I rebooted
The boot logo (The logo in which it normally mentions that Bootloader is unlocked and blablabla) Apears. But then it closes. Apears again but then closes once more. It keep doing than until I boot it into bootloader and close it once arrived there.
If I try to get into TWRP again it closes and continue the cycle.
So I flashed in CWM recovery with the intention to Flash the Stock lolipop ZIP that I done before (which fixed it).
When I boot CWM however, I am presented with a bunch of command lines at the bottom saying
"E: can't mount cache/logs"
and other lines (If you want the exact command lines say so and I will go get them). I didn't flinched to it (sometimes weird **** happens like that and I got used to it) so I go into the install from sdcard. I get this amazing message:
E: cannot mount sdcard
And all gui is not even present. I close the phone and start panicking
################################################################
In other words I need help. I will be checking this thread all the time looking for any help. I am giving up. faced such a problem in my life. I am scared that I bricked the phone for good.
Here is all I know about said phone:
KITKAT MOTO G 4.4.4 from canada (obtained from WIND mobile) most likely XT1034 (Its a mono sim)
The bootloader is 41.18
I used TWRP 2.8.6.2 for xt1032 (This is probably why everything exploded. I didn't realised it was for xt1032)
And I used CWM touch 6.4.0.7 falcon
MORE INFO WILL BE COMING, But I am extremely stressed right now to the idea that I might killed it.
#######################################################################################
#######################################################################################
Here are the CWM error messages
ClockworkMod Recovery v6.0.4.7
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_Install
- Install ZIP
- Choose zip from /sdcard
E: can't mount /sdcard
-Choose zip from /sdcard
##CWM gui closes## only the command lines are showing.
################
Update 1. I calmed down. I searched the error message and found out that it could either be an issue with CWM being currupted. I will reflash it and bring details. If it doesn't work I will format cache (Wiping the cache seems to not work)
Formatting the cache seems to fix all the cache error messages. But the mounting of /sdcard still present an obstacle
################
Why not flash stock firmware?
motofirmware.center
Sent from my XT1031
#######################
Update 2
I did some research and found out that my sdcard might be on logical and not primary and a way to fix it is to use mini partition tool on it. I am hesitant to do this so I will search for other possible issues
############################################
ATTACK said:
Why not flash stock firmware?
motofirmware.center
Sent from my XT1031
Click to expand...
Click to collapse
Because I can't find it.
try to find a 4.4.4, xt1034 canada stock firmware, Not easy. I've look for around 3 hours without success.
I however found a flashable zip for it, so I need to make recovery work, Because to my knowledge you can't flash an entire zip from adb/fastboot
The site you provided doesn't contain the right firmware. I highly appreciate the help though.
####################################
update 3
I decided to try and sideload stock rom lolipop. Seems to be working. Will be updating the results.
Here are the result:
ON MOTO G
-Install zip from sideload
nothing unusual happens
ON ADB
- adb sideload "lolipop stock rom".zip
Loads.....
Sends.....
"*failed to write data 'protocolt fault <Coudn't read status: invalid argument'* "
BACK TO MOTO G
- cancel sideload
Restarting adbd....
status 0
finding update package.....
opening update package.....
E: Can't open /tmp/update.zip
(bad)
installation aborted.
Click to expand...
Click to collapse
So it doesn't work but I found that last bit interesting. I feel like things are clearing up even though no ones is helping me (except for ATTACK, thanks but I will need a lot more help than that ) So help is apreciated
######################################
What about this file? -> XT1034_FALCON-RETAIL-CA_5.0.2_LXB22.46-32_31_cid14_CFC_1FF.xml.zip
Taken from the factory image index thread. It's the full Retail Canadian 5.0.2 firmware for XT1034
Here are some links to the 4.4.4 firmware.
http://forum.xda-developers.com/showpost.php?p=54855457&postcount=354
EDIT: Here's another link that's probably faster then FileFactory.
http://yun.baidu.com/s/1eQ6iXR8
Sent from my XT1031
k-kuchen said:
What about this file? -> XT1034_FALCON-RETAIL-CA_5.0.2_LXB22.46-32_31_cid14_CFC_1FF.xml.zip
Taken from the factory image index thread. It's the full Retail Canadian 5.0.2 firmware for XT1034
Click to expand...
Click to collapse
If you look at the top of the thread you'll see a link pointing to the beggining of the file, The one who helped me told me to flash this exact file and made my moto to boot loop. Trust me, it's not the right one.
ATTACK said:
Here are some links to the 4.4.4 firmware.
http://forum.xda-developers.com/showpost.php?p=54855457&postcount=354
EDIT: Here's another link that's probably faster then FileFactory.
http://yun.baidu.com/s/1eQ6iXR8
Sent from my XT1031
Click to expand...
Click to collapse
YES, Omg I didn't knew lost posted Firmwares. Prase the mighty lost god. The first one is exactly it.
I don't mind waiting 1 or 2 hours. as long as I got it nicely set up for september 1 I'm a-ok
If it boots properly I owe you sir.
thegamerchunk1 said:
If you look at the top of the thread you'll see a link pointing to the beggining of the file, The one who helped me told me to flash this exact file and made my moto to boot loop. Trust me, it's not the right one.
Click to expand...
Click to collapse
The 4.4.4 is also in this thread
Edit: Hosted on AFH -> https://www.androidfilehost.com/?fid=24052804347795180
##############################
Update 4
I tried to restore stock firmware. Back to square 1.
Cache issues.... I fixed it
Can't mount /sdcard.... Can't fix it.
The logo is the only thing I see and whenever I try to close it by pressing the power button, it reboots into the logo screen.
The only way I can truly close it is by opening fastboot menu and closing it there.
WHY IS THIS HAPPENING IM LOOSING MY MIND
I beg someone, anyone, Help me...
######################################################################
##################################
Update 5 Final ****ing update ****
I wiped and formatted /sdcard with philz touch recovery.
It seems that I can mount the sdcard now but I can't flash any roms because it
"Failed to set up expected mounts for install"
I am seriously in the most depressed mood ever. I worked for 4 years in computer development and I never had this much trouble ever. I ****ing give up everything. If someone ever encounter this issue:
you are ****ed throw the moto g in the garbage its dead nada done.
If someone thinks the contrary tell me how I am supposed to fix this. I will check it in about 12 hours.
I will do anything that someone thinks is going to fix it.
So - after flashing stock firmware your device still won't boot?
How did you flash stock firmware?
Did you receive any errors while flashing stock firmware?
And you are able to flash a custom recovery (TWRP or similar)?
Sent from my XT1031
kinda urgent
@lost101 can you help him brother. He is in dire need.....
@thegamerchunk1 - You need to try to relax - you are making things more complicated than necessary.
It's an known issue that making a nandroid backup in certain versions of TWRP will cause all this. You need to start again.
Stop trying random fixes and fastboot flash the firmware image for your phone.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Provide a log of what happens when doing the fastboot commands.
ATTACK said:
So - after flashing stock firmware your device still won't boot?
How did you flash stock firmware?
Did you receive any errors while flashing stock firmware?
And you are able to flash a custom recovery (TWRP or similar)?
Sent from my XT1031
Click to expand...
Click to collapse
I flashed it using fastboot. here are the commands I used
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I recall seeing 3 errors. It was hours ago so I don't remember exactly where but it was before the system flashes. They were all similar error except for the end. Im gonna flash it again and see.
Yes I can flash custom recovery.
However I can't a right TWRP version for the phone. whenever I do flash it (TRWP 2.8.6.0 xt1032) and enter into recovery, the logo boots but closes right after
The only ones I could install were CWM and PHilz touch. But I can't install anything from sdcard because I either miss expected mounts (From formatting /sdcard/) or I can't mount /sdcard/.
lost101 said:
@thegamerchunk1 - You need to try to relax - you are making things more complicated than necessary.
It's an known issue that making a nandroid backup in certain versions of TWRP will cause all this. You need to start again.
Stop trying random fixes and fastboot flash the firmware image for your phone.
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Provide a log of what happens when doing the fastboot commands.
Click to expand...
Click to collapse
Sorry. It was 2 am where I was.
I know how to fastboot flash. I'll try myself again and report myself again.
Also I wasn't expecting to see lost here.
thegamerchunk1 said:
Sorry. It was 2 am where I was.
I know how to fastboot flash. I'll try myself again and report myself again.
Also I wasn't expecting to see lost here.
Click to expand...
Click to collapse
Make sure to include the command: fastboot erase userdata
thegamerchunk1 said:
I flashed it using fastboot. here are the commands I used
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I recall seeing 3 errors. It was hours ago so I don't remember exactly where but it was before the system flashes. They were all similar error except for the end. Im gonna flash it again and see.
Yes I can flash custom recovery.
However I can't a right TWRP version for the phone. whenever I do flash it (TRWP 2.8.6.0 xt1032) and enter into recovery, the logo boots but closes right after
The only ones I could install were CWM and PHilz touch. But I can't install anything from sdcard because I either miss expected mounts (From formatting /sdcard/) or I can't mount /sdcard/.
Click to expand...
Click to collapse
Ok - after you retry flashing, please post those errors. May want to try using mfastboot instead of fastboot as well.
Also you could 'adb push ROM.zip' with a custom recovery, bypassing the sd card altogether, but I think you should get your device to boot first.
Sent from my XT1031
After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
My bootloader is locked, so I tried to unlock it following the Motorola's guide. Got my device ID via fastboot, copy and paste on their site and requested the unlock key.
Then again, when I use "fastboot oem unlock CODE"
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
The problem is that I can't pass trough flash mode screen.
I've been reading some threads over here, and one guy which had his bootloader locked on XT1563 tried to flash the Canadian firmware and didn't get any error, then he was able to fully unlock his bootloader and after this he was able to flash the Brazilian firmware.
I didn't try to flash the Canadian firmware yet. How risky is this? There is another way to unlock the bootloader?
If you flash the right firmware for a locked phone (model and version), it won't give the prevalidation error. Then it can boot again and you can turn on the OEM unlock, and unlock the bootloader.
Try to use the right firmware for your phone.
TImMaia said:
After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
Click to expand...
Click to collapse
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?
MrTooPhone said:
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?
Click to expand...
Click to collapse
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:
TImMaia said:
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:
Click to expand...
Click to collapse
If you really want to root, you need to follow these instructions. Although you can use the latest version of TWRP, do not use any other version of Supersu except v2.62-3. Any other methods will most likely soft brick your phone.
Boys, is not difficult, not just fiddling around to fix it.
Motorola install drivers
Install ADB and fastboot
Looking for your stock rom here: " github dot com dash motoxplay dash stock dash releases " for example.
Saddled with fastboot Tooda the rom (eye, if downloaded from out there commands, you may be wanting to them upload any image rom, this drove me crazy to me all one day until I realized I was missing two sparsechunk).
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 system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
On the subject battery, the XT1563 charge the batt when it is in this mode, we just have to leave it connected to the charger and is loading very slowly.
On the bootloader issue, I have LOCK, and may do so without problems because they look the same version of rom that he had.
About not having DEPURACION USB, I did not have it on, and yet I could do it.
My stay in Fastboot mode I when installing the app Kingroot, and turned off the phone and start no more.
In this way it is solved, 100% sure I did not do myself. Do not try other methods like TWRP or things like that because with locked bootloader will hit the wall every time.
Anyone who needs a hand, ask or send mail.
Sorry if he had been resolved, but it was a big achievement for me, so I leave the info. I cost a lot to buy the cell phone and had ****ed the other day.
Regards!
(Sorry, its googletranslated, im from argentina)
Yeah, what ever @jonatandirocca1 said is right
i also once faced the problem of missing sparse file but after flashing every file you can make your Phone revoke
if you want to install STOCK FIRMWARE , you dont need to unlock bootloader, you just need your phone detected in ADB
Hi all,
I could really use some help on the following, and any advice would be greatly appreciated.
I wanted to root my Moto G (2014, 2nd gen, dual sim) in order to use the RAM more flexibly. Unlocking the device was no problem at all. However, when I initiated the rooting process, the trouble started. I first tried superboot, which did not work, but also did not destroy anything. Then, I switched to using TWRP and the supersu image (I found the info on here). TWRP worked fine, but after initiating the installation of the supersu image, the phone got stuck in a boot loop -- it stayed on the unlocking warning page and would not boot up anymore. I figured out a way to get back into fastboot (also by looking through the forum here, thanks to you all!) -- by pressing the power button until the screen switched off, and then pressing the Volume down button as well for a few seconds.
However, none of the recovery methods I found in other threads worked (I tried deleting the cache etc. through various methods, but the loop persisted). So, next, I attempted to use the method I found on droidviews.com to restore the phone to a working status (any working status would do at this point).
Since I was not able to access the debugging options anymore, I did everything except the initial 'adb reboot bootloader' command. Here is the list of commands:
mfastboot oem lock begin
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.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 modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
NB I am doing this on MacOS, so I used the osx-fastboot command instead of mfastboot. Up until 'flash boot boot.img', everything worked, but when I tried the 'osx-fastboot flash recovery recovery.img' command, I got the following error message in the Terminal window:
(bootloader) Preflash validation failed
FAILED (remote failure)
And the error message on my phone reads:
hab check failed for recovery
Failed to verify hab image recovery
What can I do at this point? Since I followed the instructions as closely as possible, I also used the 'osx-fastboot oem lock begin' command, and now my device indicates that it is locked. Did I wreck my phone or is there any way out of this at all?
As I said, I would be most grateful for any advice at all. If you need more information, I am happy to provide it.
Thanks!
-sleepingweather
I am still looking for ways to get the phone into any sort of working order. Do any of you have advice on this? Is it possible?
I ran Lollipop on it before it crashed, if that is helpful information.
Thanks
After connecting the device to a Windows 7 PC, I can confirm that the Windows system does not recognize the Moto at all, so it appears that the method in the main thread on unbricking & restoring Moto Gs back to 4.4.4 / 5.01 would not work either, right? Is there anything else that I can do?
If anybody were to give me even the most spurious bit of advice, or some feedback on how I should go about finding a solution on the forum (I am trying my best, but might not have observed all the etiquette etc. out of ignorance), I would be tremendously grateful.
Thanks
Here is the solution a very friendly user -- inFiniTyz_Z , many thanks!-- on here pointed me towards:
If a bootlocker is unlocked and then relocked, as was mine, it is entirely possible to unlock the bootloader again. One needs the unlocking key from Motorola and the command
fastboot oem unlock UNIQUE_KEY
With the bootloader unlocked, I was able to flash TWRP again, which of course helped tremendously.
After this, I managed to install a Brazilian stock ROM -- the German one I would need did not work, but I will look for ways to get the phone to work regardless. At the moment, Android is up and running, but it does not connect to the network (because of the Brazilian settings, I guess). I might switch to CyanogenMod anyways.
I figured that since the Motorola web site doesn't have the firmware for this yet I would post a link to my Dropbox so others have access to the firmware. This is for us cellular Moto g4 play xt1607 not sure if it will work for devices on a different carrier. If someone could make a backup of their current rom and test it out to let us all know if it does that would be great. Please hit the thanks button if this helps anyone. https://www.dropbox.com/s/i6jsafelq...y-DEFAULT_regulatory-DEFAULT_CFC.xml.zip?dl=0
This must be flashed with fastboot. If you do not know how to flash with fastboot there are tons of how to videos if you google it.
BACKUP YOUR DEVICE TO SD CARD OR PC BEFORE DOING ANYTHING!!!!!
DISCLAIMER: FLASHING ANYTHING TO YOUR PHONE HAS RISKS. IF YOU DO NOT KNOW WHAT YOU ARE DOING AND YOU HAVE JUST PURCHASED YOUR PHONE AND HAVE NOT UNLOCKED THE BOOTLOADER STOP!!!!! DO NOT CONTINUE. IM NOT SURE WHAT THE EFFECTS WILL BE IF YOU TRY FLASHING WITH A LOCKED BOOTLOADER, IT COULD BRICK YOUR DEVICE!!!!! I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED BY FLASHING THIS FIRMWARE. IF YOU DID SOMETHING WRONG AND DONT FOLLOW INSTRUCTIONS THAN THATS YOUR OWN T.S.
Just in case you can't use google, for some crazy reason, put phone into bootloader mode then on PC download and install minimal fastboot and adb then download firmware, unzip firmware to desktop then open that file and click on a blank spot then hold shift and right click on that blank spot then click open command window here. In that command window type
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 clog
fastboot oem fb_mode_clear
fastboot reboot
If you are running windows 10 you can copy all lines and paste to the command window and it will do all without having to type every line one by one, not sure if it works the same on windows 8.1, 8 or 7 but it does on 10 just remember to hit enter after it completes and you see fastboot reboot on the command window for some reason it doesn't do this for you. That's all there is to it it's very easy. After the device has rebooted you will be at 100% stock with a completely de-bloated rom! This should work on any xt1607, but please be safe and make a backup on sd card or PC before doing anything. If you are still having issues I will have my 4 year old come to your house to bring you to school. Happy flashing everyone and please hit the thanks button if this helps.
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
DanHutchins said:
Just in case you can't use google, for some crazy reason, put phone into bootloader mode then on PC download and install minimal fastboot and adb then unzip firmware to desktop then open that file and click on a blank spot then hold shift and right click on that blank spot then click open command window here. In that command window type
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 clog
fastboot oem fb_mode_clear
fastboot reboot
If you are running windows 10 you can copy all lines and paste to the command window and it will do all without having to type every line one by one, not sure if it works the same on windows 8.1, 8 or 7 but it does on 10 just remember to hit enter after it completes and you see fastboot reboot on the command window for some reason it doesn't do this for you. That's all there is to it it's very easy. After the device has rebooted you will be at 100% stock with a completely de-bloated rom! This should work on any xt1607, but please be safe and make a backup on sd card or PC before doing anything. If you are still having issues I will have my 4 year old come to your house to bring you to school. Happy flashing everyone and please hit the thanks button if this helps.
Click to expand...
Click to collapse
jestyr8 said:
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Is the bootloader unlocked?
jestyr8 said:
I have tried following your instructions so that i can restore my us cellular xt1607 back to stock but all i get are failed (data transfer failure (unknown error)) messages.not really sure what the issue is. I am using minimal fastboot and adb 1.4. Any help would be greatly appreciated.
Click to expand...
Click to collapse
What command gives the error?
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
DanHutchins said:
Is the bootloader unlocked?
Click to expand...
Click to collapse
jestyr8 said:
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
Click to expand...
Click to collapse
Not sure. Did you make sure USB debugging is active for file transfer?
jestyr8 said:
I am unlocked and root with twrp and su installed and working. Unfortunately, I forgot the cardinal rule of making a backup before rooting. phone is working but having some issues. As far as which command is giving me the issues.
fb_mode_set is fine. but after that I get.
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.008s
Click to expand...
Click to collapse
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
II seem to be going backwards.
Heres the steps i had been following..that now no longer seem to work. with phone running....plug in, run minimal adb...check for devices with adb devices command...device is listed...then use adb reboot bootloader. from there I started using your list of commands to flash the phone. however after the first command to set fastboot mode all I get are errors. now for some reason adb isn't even seeing my phone.
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse
jestyr8 said:
II seem to be going backwards.
Heres the steps i had been following..that now no longer seem to work. with phone running....plug in, run minimal adb...check for devices with adb devices command...device is listed...then use adb reboot bootloader. from there I started using your list of commands to flash the phone. however after the first command to set fastboot mode all I get are errors. now for some reason adb isn't even seeing my phone.
Click to expand...
Click to collapse
That's because if you unplug the phone from the PC then plug it back in it defaults the USB debugging to charge only. If you get into twrp you can still put a custom ROM in root of phone to flash in twrp. I would try that then try to install the stock again. Be sure to have debugging set to file transfer.
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse
jestyr8 said:
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
Click to expand...
Click to collapse
Please do as of now that's the best I can do. Everything worked fine for me. I have flashed the same file many times on my g4 play
jestyr8 said:
I've been doing that...I'll give squids CM13 rom a shot as it is the only rom out there and see if that works. Thanks for your help. I really wasn't expecting such a quick response on a Saturday morning..I'll let you know how it goes
Click to expand...
Click to collapse
Were you able to get back to stock?
DanHutchins said:
Were you able to get back to stock?
Click to expand...
Click to collapse
Haven't gotten back to stock yet, but did get cm13 running with no issues. I'm still playing with it to try and see what's up. Since I've gotten cm13 running I'm undecided on staying with it and upgrading to cm14 when it's ported or continue trying to go back to stock and getting nougat thru that way.
jestyr8 said:
Haven't gotten back to stock yet, but did get cm13 running with no issues. I'm still playing with it to try and see what's up. Since I've gotten cm13 running I'm undecided on staying with it and upgrading to cm14 when it's ported or continue trying to go back to stock and getting nougat thru that way.
Click to expand...
Click to collapse
I like cm13 there just aren't any real good themes for free. I don't mind donating to a dev. but if I can't test it out to see if I like it or not I don't want to pay.
I'm using the material glass theme along with stealth icons, i like it a lot
jestyr8 said:
I'm using the material glass theme along with stealth icons, i like it a lot
Click to expand...
Click to collapse
Looks cool.
DanHutchins said:
Looks cool.
Click to expand...
Click to collapse
So just further update. Got as far as fastboot partition gpt.bin. after that it just gives me transfer failed errors. So I guess I am just going to stick with cm13 since that is running good. at least until someone makes a flashable zip of the stock firmware. I have never tried any dev work with android, so while I know it is possible to make a flashable zip out of these files it is way beyond my skills and knowledge. Thanks Dan for your help and fast response time.
jestyr8 said:
So just further update. Got as far as fastboot partition gpt.bin. after that it just gives me transfer failed errors. So I guess I am just going to stick with cm13 since that is running good. at least until someone makes a flashable zip of the stock firmware. I have never tried any dev work with android, so while I know it is possible to make a flashable zip out of these files it is way beyond my skills and knowledge. Thanks Dan for your help and fast response time.
Click to expand...
Click to collapse
No problem, ask around for anyone able to make it flash able with twrp I'm sure someone can or at least give you instructions on how to do it.
USB debugging to file transfer
DanHutchins said:
Every time you unplug the phone from PC then plug it back in you must change debugging to file transfer.
Click to expand...
Click to collapse
Where/how to "change debugging to file transfer" on Win-7?
Thanks!
Until now, my only experience was flashing a recovery image to Moto E2 with command:
Code:
fastboot flash recovery twrp.img
Neither I have to change "USB debugging to file transfer", nor I needed to use command
Code:
fastboot oem fb_mode_set
Is that something new and specific to Moto G Play 4th Gen?
Edit:
I have just unlocked the bootloader of my new Moto G4 Play and flashed a new logo file with command:
Code:
fastboot flash logo logo.bin
Still puzzled by "change debugging to file transfer"