I have a motog xt1033, and I'm trying to catch my android bricked, but after flashing each command as recommended, all give as "Failed <Remote Failure>" , I tried with various stocks and all give so if anyone can help me I will be very grateful !!
I was told it was because I have not unlocked bootloader, well, I try to unlock, but after flashing the command "fastboot oem get_unlock_data" the following error appears "(bootloader) Could Not get unlock".
device only starts in fastboot mode
Bootloadar: Blocked
make sure you flash:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Happened to me once did this got it to work
Related
Like an idiot i bought a GPE and didnt realize its not 4g, and has issues w/ tmobile. Then unlocked it soon as I got it.
How do I re-lock it? The command does not seem to work
I am always Given "Failed to validate system image"
Anyone? Beuller?
You'll have to first start by issuing the command 'fastboot oem lock begin' while booted to the bootloader.
Then find the procedure to flash the stock firmware to the GPE and do that.
Then after that is finished issuing the command "fastboot oem lock' and it will relock your bootloader.
However once the bootloader is unlocked it is not set back to 'locked' once relocked; It is set to 'relocked', so they could possibly still tell the difference if they are paying attention.
CodyF86 said:
You'll have to first start by issuing the command 'fastboot oem lock begin' while booted to the bootloader.
Then find the procedure to flash the stock firmware to the GPE and do that.
Then after that is finished issuing the command "fastboot oem lock' and it will relock your bootloader.
However once the bootloader is unlocked it is not set back to 'locked' once relocked; It is set to 'relocked', so they could possibly still tell the difference if they are paying attention.
Click to expand...
Click to collapse
I tried that, thats when I get the error I mentioned above.
You'll probably need to use mfastboot.exe instead of fastboot.exe. Which one are you using?
CodyF86 said:
You'll probably need to use mfastboot.exe instead of fastboot.exe. Which one are you using?
Click to expand...
Click to collapse
mfastboot.
Is it possible it has to do with the fact it got the 4.4.4 update?
Any help would be great. If not then I'll just try and resell it.
Someone must have something I can try.
WHen i to to restore I get this message on these files
mfastboot flash partition gpt.bin - Version downgraded for primary_gp
mfastboot flash motoboot motoboot.img - Version downgraded for tz
mfastboot flash boot boot.img - Version downgraded for boot
I'd love any input at all.
guess not
Hi had a moto g xt1039 on 4.4.4 yesterday finally got the official 5.0.1 update however my phone is rooted and the bootloader is unlocked. So I got the official stock from for my phone checked it and the cid number too. Followed the instructions on here to flash the rom back on. This all worked and a clean install was done. After a few apps updated the lollipop update message appeared again so downloaded and installed it however during the install it errored, restarted and once I was back on the phone dashboard it said an error occurred no changes made. The bootloader is still unlocked. Could this be the issue? If so how do you relock or what could cause the install error issue?
Many thanks
update so far while waiting for someone to help fix this current issue i have done some research on how to lock the boot loader. I found a guide on here to do so and the commands within mfastboot was as follows:
fastboot oem lock begin
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
So i executed this and now the problem is after restarting the phone the screen is stuck on the warning boot loader unlocked screen and wont move. Te phone still can boot into boot loader and communicates with the pc.
So i re flashed the firmware with the original guide ( without the fastboot oem lock) but still stuck on the boot loader unlock screen. Do i have to input a command to unlock the boot loader again?
Need this sorting asap as its my only phone for communication and i currently don't have a functioning phone.
Many Thanks
Unlocked Bootloader is not the reason for your original issue. I have never 'relocked.'
Download the XT1039 Fastboot Firmware image here:
http://forum.xda-developers.com/showpost.php?p=61445658&postcount=654​Use mfastboot to flash the files: https://www.androidfilehost.com/?fid=23578570567719065
TIP: Do not include the follow command for your own safety: mfastboot flash motoboot motoboot.img
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.
Hi, I'm trying to flash firmware on moto g3 but when I write command "fastboot flash partition gpt.bin" it tells me "error: cannot found 'gpt.bin' ". I have got all files thats are necessary. What is wrong with my phone? Some one had this problem? Someone can help me?
I actualy did it. I used Minimal ADB and fastboot program. But now, when I'm trying to lock bootloader, it saies "Please fully flash the signed build before locking phone!". I flashed system stepbystep with https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 ( without flashing gpt.bin because it saies "Preflash validation failed" ) Any ideas?
Theheero said:
I actualy did it. I used Minimal ADB and fastboot program. But now, when I'm trying to lock bootloader, it saies "Please fully flash the signed build before locking phone!". I flashed system stepbystep with https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 ( without flashing gpt.bin because it saies "Preflash validation failed" ) Any ideas?
Click to expand...
Click to collapse
You can't relock the bootloader using a version of firmware that is older than what you have... that is what you are trying to do.
Don't preface the flash with "oem lock begin", just start with like this:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
<rest of stuff>
fastboot oem fb_mode_clear
fastboot reboot
Without a version of official firmware that is the same or newer than what you have installed, you cannot relock the bootloader... and we don't have the current releases.
acejavelin said:
You can't relock the bootloader using a version of firmware that is older than what you have... that is what you are trying to do.
Don't preface the flash with "oem lock begin", just start with like this:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash partition gpt.bin
<rest of stuff>
fastboot oem fb_mode_clear
fastboot reboot
Without a version of official firmware that is the same or newer than what you have installed, you cannot relock the bootloader... and we don't have the current releases.
Click to expand...
Click to collapse
Any danger if I 'll use gpt.bin from other firmware of other version of phone which match?
Theheero said:
Any danger if I 'll use gpt.bin from other firmware of other version of phone which match?
Click to expand...
Click to collapse
Don't do it. Download the factory images for your specific device here https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639, and flash them.