Related
Hello All,
I am looking for some assistance on how to restore my bricked Droid Bionic, I updated to .893 and was trying to roll back to .886 so I can do the 4ever root hack before updating again to .893 however while trying to use rsd lite my device went into a soft brick state.
I have searched this forum and other places and tried the following however nothing seems to work, it keeps failed at flashing boot:
http://briefmobile.com/droid-bionic-receives-fastboot-recovery-files
http://rootzwiki.com/topic/5484-r3l3as3droot-and-43v3r-root-for-the-bionic-v21/page__st__630
http://www.mydroidworld.com/forums/...-your-phone-back-upgrade-path.html#post106072
http://forum.xda-developers.com/showthread.php?t=1262540
RSD lite 5.5/6
bionic_minimal_fxz.tar\bionic_minimal_fxz\default_flash_targa.xml and full
Any hope or is my device bricked for good.
Thank you.
i am on the same boat ahah now that my batter is low status, I was able to do the USB hack to get it to charge in AP Fastboot mode..still screwed at bootloader
So does that mean we are in need of a new phone from verizon?
have no fear! read this
http://forum.xda-developers.com/showthread.php?t=1412339&page=2
It does seem like it. I think I screwed up pretty bad. I am stuck at AP loop..
Currently at AP Fastboot (Boot Failured)
Invalid CG (CG:Boot)
Tried to fastboot stock or even FXZ, it starts and failed and screwed me over to
AP Flash Failed Mode...
---------- Post added at 09:01 PM ---------- Previous post was at 09:00 PM ----------
idivorceyou said:
http://forum.xda-developers.com/showthread.php?t=1412339&page=2
Click to expand...
Click to collapse
Funny you wrote that, i was going through the exact same process in at the moment. Already McGyver the USB cable
Dude I went through all that. Try my recipe. Click my link, download the zip from my dropbox. Follow instructions. Should work!
I tried something like that but not in the same order so I will give that try and report back.
idivorceyou said:
Dude I went through all that. Try my recipe. Click my link, download the zip from my dropbox. Follow instructions. Should work!
Click to expand...
Click to collapse
No dice for me
failed at flashing Web Top Frfs.img
Load_file: could not allocate xxxx
Pass preinstall.img
Failed system.img
Writing system .... INFOPreflash Validation Failure
FAILED (remote: )
@idivorceyou DUDE YOU R THE MAN!!!!
If we ever cross paths in NYC and I know its you I will buy you a few beers, it WORKED. Now I am back to where I was before, now I need to try and get root on .893 which was not possible that's why I started this whole thing in the first place of trying to downgrade to .886 to apply the 4ever root.
smilepak said:
No dice for me
failed at flashing Web Top Frfs.img
Load_file: could not allocate xxxx
Pass preinstall.img
Failed system.img
Writing system .... INFOPreflash Validation Failure
FAILED (remote: )
Click to expand...
Click to collapse
I failed with that earlier in the night and I tried this
[mydroidworld.com/forums/droid-bionic-forum/10577-bionic-path-saver-1-click-method as well as the fastboot_fix file. Here is what the file does:
fastboot flash devtree device_tree.bin
fastboot reboot
Click to expand...
Click to collapse
infolookup said:
I failed with that earlier in the night and I tried this
[mydroidworld.com/forums/droid-bionic-forum/10577-bionic-path-saver-1-click-method as well as the fastboot_fix file. Here is what the file does:
fastboot flash devtree device_tree.bin
fastboot reboot
Click to expand...
Click to collapse
did that 20 times today too..it fixed that part and advance me one step further..and some else failed and bring me back to square one.
So far, the only thing that stick is the mini FXZ 901 at the bottom of this post
http://rootzwiki.com/topic/4603-fxz-fastboot-recovery/page__st__138
but now different error on boot failed. hahaha
crap
---------- Post added 28th December 2011 at 12:21 AM ---------- Previous post was 27th December 2011 at 11:55 PM ----------
Finally...this got me at least being able to boot into android for once
Extract the files below from there respective fxz file and try the commands listed. You must use the updated moto-fastboot.exe app. I just have it renamed to fastboot.exe.
files from 5.5.893 tar.gz file posted above (credit to realbbb):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
files from stock 5.5.866 fxz file:
fastboot flash system system.img
fastboot flash preinstall preinstall.img
fastboot flash radio radio.img
fastboot flash webtop grfs.img (might not be necessary, but I did it)
Boot the phone into fastboot mode. I put all of the files in the same folder and flashed them one after the other. Then "fastboot reboot". I booted up fine and shortly thereafter had a notificaton of an available update. I then used R3L3AS3D to root and 4ever root and allowed the update. So far everything is working great and I'm on the OTA path again.
Click to expand...
Click to collapse
infolookup said:
@idivorceyou DUDE YOU R THE MAN!!!!
If we ever cross paths in NYC and I know its you I will buy you a few beers, it WORKED. Now I am back to where I was before, now I need to try and get root on .893 which was not possible that's why I started this whole thing in the first place of trying to downgrade to .886 to apply the 4ever root.
Click to expand...
Click to collapse
So pleased I could help (sorry this didn't work for everyone)
There are so many well intentioned posts with solutions but none really works for the total bricked bionic. So I saved my steps and uploaded my files and swore to help anyone else avoid - as much as possible - what I went through.
Would love to have root again but with 901 installed, golauncher and some manic app restoring, the phone works great.
For now I am on 893, and since development was stopped on the KIN3TX rom which I was using I am now about to take a nandroid backup, and flash with the new http://rootzwiki.com/forum/343-eclipse/ Eclipse rom.
after my restore, I downloaded and flashed the "official" 901 update "Blur_version.5.5.893.xt875.verizon.en.us".
don't know if released root will get me rooted. Too nervous to try anything else right now!
I just don't have the patience to spend another night in front of the computer cursing at my failed fastboot efforts. It works now. Supposedly, due to .901, it is better. bloaty, but better.
waiting for the dev gurus to create an easy way to root .901 and for the roms that are made with it.
For some reason, when I navigate I get errors and I'm typing the path where the file is stored, the desktop. What am I doing wrong?
hi
i unlocked my bootloader and then i reflash thr original firmware and lock the bootloader succesfully
but the red warning of bootloader unlocked still is present every time i power on my moto x
some help?
thank u
( i tried with a original logo from Moto g but got a weird image with all blured lines)
There's a thread for this. It's not difficult to find.
nhizzat said:
There's a thread for this. It's not difficult to find.
Click to expand...
Click to collapse
/// solved
thank u
danger2u said:
/// solved
thank u
Click to expand...
Click to collapse
How did you solve it because no matter what I do the warning still there .... Thanks
aburyan1 said:
How did you solve it because no matter what I do the warning still there .... Thanks
Click to expand...
Click to collapse
put in fastbootmode
download this recovery
https://drive.google.com/file/d/0BwTULBGmnkwqYVlkODlva2hNbzA/edit?usp=sharing
make a folder and copy adb files and mfastboot
open a cmd or terminal in that folder
write in cmd the folowing comands
mfastboot devices
mfastboot flash recovery logo_nowarning-4.4.bin
mfastboot reboot
done
enjoy
aburyan1 said:
How did you solve it because no matter what I do the warning still there .... Thanks
Click to expand...
Click to collapse
Keep in mind the logo.bin (used if you unlocked your bootloader) has changed between versions, so 4.2.2 uses a different file from 4.4. You need to make sure you're using the right file for the ROM version on your phone.
And if you've seen the threads on using the clogo.bmp, that is for an locked bootloader that has never been unlocked.
Consider also reading this thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
danger2u said:
put in fastbootmode
download this recovery
https://drive.google.com/file/d/0BwTULBGmnkwqYVlkODlva2hNbzA/edit?usp=sharing
make a folder and copy adb files and mfastboot
open a cmd or terminal in that folder
write in cmd the folowing comands
mfastboot devices
mfastboot flash recovery logo_nowarning-4.4.bin
mfastboot reboot
done
enjoy
Click to expand...
Click to collapse
dude... your command "mfastboot flash recovery logo_nowarning-4.4.bin" is not correct. that would be trying to flash the logo.bin file over the recovery partition. you want to use "mfastboot flash logo logo_nowarning-4.4.bin" and this assumes the person is on 4.4 or 4.4.2.
---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------
I've posted this elsewhere....
for unlocked bootloader phone, or one that has been unlocked and relocked, it would be...
Code:
adb reboot bootloader
fastboot flash logo name.bin
(where name.bin is the name of your new logo file)
and these steps should be performed with phone normally booted, and USB Debugging enabled.
The first command mitigates the need to power off and try and mess with buttons while powering on
On a side note... For those interested in making your own LOGO.BIN...
There is already a thread discussing how to do that -> Moto X Boot Logos which includes a script by carock -> <HERE> to help make it easier. NOTE1: you might want to see THIS POST with tips on formatting the graphics you want to use with the script. NOTE2: The LOGO.BIN format was different between 4.2.2 and 4.4. This script does work with KitKat 4.4. I have not looked to see if the KitKat 4.4.2 logo.bin has changed or not.
For my contribution of sharing...
I took the 24 CLOGO's from -> HERE, converted them to logo.bin's using carock's script. And did one or two others I found that I liked. I put them in -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip (when you un-zip it, there will be two folders, one containing the original graphics so you can see them and choose without flashing, and one with the logo.bin's. NOTE: the originals can be used by those with locked booloaders looking to flash their clogo.bmp). These flash fine on my Verizon Moto X Developer Edition with unlocked bootloader and KitKat 4.4.
KidJoe said:
Keep in mind the logo.bin (used if you unlocked your bootloader) has changed between versions, so 4.2.2 uses a different file from 4.4. You need to make sure you're using the right file for the ROM version on your phone.
And if you've seen the threads on using the clogo.bmp, that is for an locked bootloader that has never been unlocked.
Consider also reading this thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
dude... your command "mfastboot flash recovery logo_nowarning-4.4.bin" is not correct. that would be trying to flash the logo.bin file over the recovery partition. you want to use "mfastboot flash logo logo_nowarning-4.4.bin" and this assumes the person is on 4.4 or 4.4.2.
---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------
I've posted this elsewhere....
for unlocked bootloader phone, or one that has been unlocked and relocked, it would be...
Code:
adb reboot bootloader
fastboot flash logo name.bin
(where name.bin is the name of your new logo file)
and these steps should be performed with phone normally booted, and USB Debugging enabled.
The first command mitigates the need to power off and try and mess with buttons while powering on
On a side note... For those interested in making your own LOGO.BIN...
There is already a thread discussing how to do that -> Moto X Boot Logos which includes a script by carock -> <HERE> to help make it easier. NOTE1: you might want to see THIS POST with tips on formatting the graphics you want to use with the script. NOTE2: The LOGO.BIN format was different between 4.2.2 and 4.4. This script does work with KitKat 4.4. I have not looked to see if the KitKat 4.4.2 logo.bin has changed or not.
For my contribution of sharing...
I took the 24 CLOGO's from -> HERE, converted them to logo.bin's using carock's script. And did one or two others I found that I liked. I put them in -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip (when you un-zip it, there will be two folders, one containing the original graphics so you can see them and choose without flashing, and one with the logo.bin's. NOTE: the originals can be used by those with locked booloaders looking to flash their clogo.bmp). These flash fine on my Verizon Moto X Developer Edition with unlocked bootloader and KitKat 4.4.
Click to expand...
Click to collapse
this was tested and working great on Moto x xt1053
is the same logo as before the unlocked bootloader
i just want to help
if my thread is not helping u can close it
Hi there
That's my first post, so please be understanding. Bought a Motorola phone as it is (no water damage) which comes to booting logo and after few minutes keep restarting and trying to booting with no results. I've started red some posts, already but i'm stuck. Reset doesn't work (Power button+volume control down), but when i press power button +camera button and plug in with computer, it shows black screen and green led. Already installed MEDFIELD drivers, RSD Lite and xFSTK-DLDR. tried already RSD Lite with no luck (i've downloaded CFC_signed_customer_8.7.1I-110_IFW-DE-31_RTEU.xml and CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml)
Can get to AP Fastboot Flash Mode, but when i tried to do Factory or Recovery gets:
Failed to enter Factory/Recovery mode. error code -18
No more error code, only some kind of "GETVAR" failed
Read here
http://forum.xda-developers.com/showthread.php?t=2166646
CWMR or TWRP install easy 19-Sep-13
Install and try again
Enviado desde mi GT-I8190L
jacbarahona72 said:
Read here
http://forum.xda-developers.com/showthread.php?t=2166646
CWMR or TWRP install easy 19-Sep-13
Install and try again
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
I'll give it go and let U know.
Thanks
Got such a message:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder and fastboot file(s) created.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
-----------------------------------.
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
How can i connect with Motorola, at the minute is on AP FASTBOOT
This time i paste .img files into Fastboot Commander folder nad gets:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 0x2025.
Radio version: failed.
Main software version: failed.
cid: 7.
cpld: failed.
product: smi.
getvar:mid failed (remote failure).
getvar:security failed (remote failure).
getvar:build-mode failed (remote failure).
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?
On phone i got Getvar build-mode
Fastboot command failed
If you came down those 2 firmware must know that one is ICS (8.7), the other JB (9.8) and if you wanted to install the ICS tending JB you've done a hardbrick, so I recommend you search for the thread "Unbrick for downgrading"
Sorry for my bad English
Enviado desde mi GT-I8190L
---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------
asgaard76 said:
I'll give it go and let U know.
Thanks
Click to expand...
Click to collapse
You bootloader is locked?
Only make if you have unlocked
Enviado desde mi GT-I8190L
---------- Post added at 08:31 AM ---------- Previous post was at 08:25 AM ----------
Read here for getvar problem
http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company
Enviado desde mi GT-I8190L
jacbarahona72 said:
If you came down those 2 firmware must know that one is ICS (8.7), the other JB (9.8) and if you wanted to install the ICS tending JB you've done a hardbrick, so I recommend you search for the thread "Unbrick for downgrading"
Sorry for my bad English
Enviado desde mi GT-I8190L
---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------
You bootloader is locked?
Only make if you have unlocked
Enviado desde mi GT-I8190L
---------- Post added at 08:31 AM ---------- Previous post was at 08:25 AM ----------
Read here forma getvar problem
http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
I don't know if it's unlocked as i bought when it won't pass booting screen
Quick update:
When i tried using Recovery.img through Fastboot commander got such a message (picture)
and on phone mostly gets Fastboot command failed
Invalid image size for partition recovery
asgaard76 said:
I don't know if it's unlocked as i bought when it won't pass booting screen
Quick update:
When i tried using Recovery.img through Fastboot commander got such a message (picture)
and on phone mostly gets Fastboot command failed
Invalid image size for partition recovery
Click to expand...
Click to collapse
SURELY NOT HAVE THE BOOTLOADER UNLOCKED
IMPORTANT
AS YOU AND I flashed HAS MARKED ERROR, YOU MUST CORRECTLY FASTBOOT FLASH FOR SOMETHING AS BOOT IMAGE ( LOGO_SIGNED ) , EXTRACT OF THE SAME FIRMWARE (ZIP )
1 - . DOWNLOAD ONE FASBOOT.EXE OF THE THREADS XDA
2 - . PLACE THE IMAGE FILE ( LOGO_SIGNED ) WITH THE FASTBOOT EXE FILE IN ONE FOLDER IN THE ROOT FOR EXAMPLE C:\ANDROID\ <---- YOU CREATE
3. - OPEN COMMAND WINDOW IN THE FOLDER FILES YOU HAVE MENTIONED IN THE PREVIOUS ITEM
4 - . RAZR I CONNECTED TO PC BY USB CABLE AND BE IN FASTBOOT MODE SCREEN
5 - . INDICATE THE FOLLOWING COMMAND " FASTBOOT FLASH LOGO LOGO_SIGNED "
IF YOU ARE FLASHING OK FOLLOW YOU'VE INDICATED BELOW
CASE 1
1 - . USE A FIRMWARE JB (9.8 )
2 - . DECOMPRESS , EDIT THE FILE WITH EXTENSION XML, and eliminate GETVAR LINES INDICATED IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company)
3 - . USE RSD LITE VERSION 6.14 MINIMUM TO FLASH THE STOCK XML EDITED ( WHICH YOU HAVE CLEARED THE LINES GETVAR )
CASE 2
1 - . UNLOCK YOUR BOOTLOADER
2 - . INSTALLING A CUSTOM RECOVERY VIA FASTBOOT COMMANDER
3. - INSTALL AN " AS CUSTOM ROM OF OMAR AVELAR " IN THE RECOVERY
FOLLOW THE INSTRUCTIONS IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company) IN THIS THREAD AS INDICATED UNLOCK BOOTLOADER ,
ALSO, THE RECOVERY IS TO INSTALL A CUSTOM ROM FOR EXAMPLE OF OMAR AVELAR AND YOU SHOULD HAVE UNLOCKED BOOTLOADER FOR THAT
jacbarahona72 said:
SURELY NOT HAVE THE BOOTLOADER UNLOCKED
IMPORTANT
AS YOU AND I flashed HAS MARKED DEFECTIVE, YOU MUST CORRECTLY FASTBOOT FLASH FOR SOMETHING AS BOOT IMAGE ( LOGO_SIGNED ) , extract SAME FIRMWARE (ZIP )
1 - . DOWNLOAD ONE OF THE THREADS FASBOOT.EXE XDA
2 - . PLACE THE IMAGE FILE ( LOGO_SIGNED ) FASTBOOT WITH THE EXE FILE
3. - OPEN COMMAND WINDOW IN THE FOLDER archvos YOU HAVE MENTIONED IN THE PREVIOUS ITEM
4 - . RAZR I CONNECTED TO PC BY USB CABLE AND BE IN FASTBOOT MODE SCREEN
5 - . INDICATE THE FOLLOWING COMMAND " FASTBOOT FLASH LOGO LOGO_SIGNED "
IF YOU ARE FLASHING OK FOLLOW YOU'VE INDICATED BELOW
CASE 1
1 - . USE A FIRMWARE JB (9.8 )
2 - . DECOMPRESS , EDIT THE FILE WITH EXTENSION XML, and eliminate GETVAR LINES INDICATED IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company)
3 - . USE RSD LITE VERSION 6.14 MINIMUM TO FLASH THE STOCK XML EDITED ( WHICH YOU HAVE CLEARED THE LINES GETVAR )
CASE 2
1 - . UNLOCK YOUR BOOTLOADER
2 - . INSTALLING A CUSTOM RECOVERY VIA FASTBOOT COMMANDER
3. - INSTALL AN " AS CUSTOM ROM OF OMAR AVELAR " FOR RECOVERY
FOLLOW THE INSTRUCTIONS IN THE THREAD (http://forum.xda-developers.com/showthread.php?p=38595619
Telcel Razr I liberate and use in another company) IN THIS THREAD AS INDICATED UNLOCK BOOTLOADER ,
ALSO, THE RECOVERY IS TO INSTALL A CUSTOM ROM AVELAR AS OF OMAR AND YOU SHOULD HAVE UNLOCKED BOOTLOADER
Click to expand...
Click to collapse
Will give it go and keep U inform. Thanks
Once again:
1. I have to download Fastboot.exe (is it fasboot commander?)
2. Image file (do i have it?? which one is it?)
3. command window?? I'm lost
4.
asgaard76 said:
Will give it go and keep U inform. Thanks
Once again:
1. I have to download Fastboot.exe (is it fasboot commander?)
2. Image file (do i have it?? which one is it?)
3. command window?? I'm lost
4.
Click to expand...
Click to collapse
1. - Fastboot.exe
2. - logo_signed (must be obtained from the firmware, exploring the zip file) NO DOWNLOAD, draw your own "firmware ZIP (CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip <-- for example)"
sorry for my bad English
Donwload files
http://db.tt/tak1LsuU
note: NO DOWNLOAD logo_signed file is of the firmware: Brasil.en.BR (IS "ICS" NO WORK, YOU DAMAGED YOUR PHONE)
Procedure
1. - Put the downloaded files in a folder in the root "C" on your pc, (I call this folder "Android" for example)
2.- Put the phone in fastboot mode (power button and Vol - squeezing them a few seconds until the screen fastboot mode) and connect with USB the phone to pc
3.- Opening a cmd screen, we stand there, I'm in cmd C:\Android\
4. - cheking with command fastboot devices
5. - Performed the command fastboot flash logo logo_signed
6. - Conducted after ending command fastboot reboot and that's it
7.- enjoy
Warning: only share what I see written on a forum and I served, so I do not take responsibility for any damage this may cause to your phone
---------- Post added at 05:14 PM ---------- Previous post was at 04:56 PM ----------
AND YOU CAN NOT COME TO RECOVERY BECAUSE ERASED PARTITION,
AS YOUR PICTURE
WHERE RECEIVED INSTRUCTIONS TO CLEAR YOUR RECOVERY?
NO YOU ACCESS IT, TO RECOVERY BECAUSE YOU HAVE NO
AND YOU MUST FLASH THE STOCK RECOVERY FIRST TO SEE IF YOU ACCESS TO RECOVERY.
ALSO THAT WHAT TO DO WITH FASTBOOT COMMANDER
what was your firmware that you had installed before this happened to you?
As per picture
It looks like image was installed, what next steps should be done?
Yes, that's my fault. I've tried program and thought that it won't make any effects, because i got messages failed, so unfortunately i erase Recovery partition. Is there anything else what we can do?
Thanks
How can i flash stock Recovery and would it help?
jacbarahona72 said:
what was your firmware that you had installed before this happened to you?
Click to expand...
Click to collapse
I don't know as i bought that phone from someone who sell it cheap (already not working) and probably that person have no clue what version/name of Android was it there?
Ok, try this, it has nothing to do with the logo u just flashed
i dunno if u already done this. But we are gonna install the stock recovery again and see what happens. Installing a recovery cant kill your device
If by this methode u cant install the recovery, fastboot gives an error, your bootloader is locked.
1. In this thread, download the 1.6 zip version of the recovery flasher. (the flasher is an automated proces, but we do it manually)
2. Open de zip file and extract the "stock.img" to the folder with the fastboot.exe
3. now, reboot the device in fastboot mode (power and volume down) and linked with usb to your pc obviously
4. use the command "fastboot devices" and u get a list of attached devices. If ur device is one of them we are good.
5. use the command "fastboot flash recovery stock.img" to flash the stock recovery. If it works, your device has an unlocked bootlaoder. If it doesn't its locked.
If it is locked, we go through the next step with rsd lite and install the latest JB 4.1.2 image to your device.
Hazou
Hazou said:
Ok, try this, it has nothing to do with the logo u just flashed
i dunno if u already done this. But we are gonna install the stock recovery again and see what happens. Installing a recovery cant kill your device
If by this methode u cant install the recovery, fastboot gives an error, your bootloader is locked.
1. In this thread, download the 1.6 zip version of the recovery flasher. (the flasher is an automated proces, but we do it manually)
2. Open de zip file and extract the "stock.img" to the folder with the fastboot.exe
3. now, reboot the device in fastboot mode (power and volume down) and linked with usb to your pc obviously
4. use the command "fastboot devices" and u get a list of attached devices. If ur device is one of them we are good.
5. use the command "fastboot flash recovery stock.img" to flash the stock recovery. If it works, your device has an unlocked bootlaoder. If it doesn't its locked.
If it is locked, we go through the next step with rsd lite and install the latest JB 4.1.2 image to your device.
Hazou
Click to expand...
Click to collapse
had to make a correct flash because if you stay with an "incorrect flash", RSD LITE not work, and in many cases say error, reading the context, "directed to make a flash of SOMETHING" and that would be correct, then with RSD LITE flash the firmware and must not indicated error like before.
to the stock recovery you can flash with the same program that he used wrong
I do not have much that I left the Razr I but I've explained what ... . somewhere in all that I have written must match with you Master.
Sorry for my bad English
Enviado desde mi GT-I8190L
jacbarahona72 said:
had to make a correct flash because if you stay with an "incorrect flash", RSD LITE not work, and in many cases say error, reading the context, "directed to make a flash of SOMETHING" and that would be correct, then with RSD LITE flash the firmware and must not indicated error like before.
to the stock recovery you can flash with the same program that he used wrong
I do not have much that I left the Razr I but I've explained what ... . somewhere in all that I have written must match with you Master.
Sorry for my bad English
Enviado desde mi GT-I8190L
Click to expand...
Click to collapse
Don't get me wrong, if I gave you that idea, wasn't my purpose
U did great in presenting a solution for the problem, the only problem is that in my opinion your post wasn't very easy to read for a new guy with a problem. With all the lines/codes that were produces and not set in a container (/code) and with the big red lines that were in the post it wasn't very understandable.
Your English is fine, it is understandable, just the formatting of the post was in my opinion not very good. The solution is good though, maybe with a small sideway, but good.
Just keep it up and help those guys when ever u can. We need those folks like u that help others out!! :thumbsup:
Hazou
Verstuurd van mijn GT-P5110
Hazou said:
Don't get me wrong, if I gave you that idea, wasn't my purpose
U did great in presenting a solution for the problem, the only problem is that in my opinion your post wasn't very easy to read for a new guy with a problem. With all the lines/codes that were produces and not set in a container (/code) and with the big red lines that were in the post it wasn't very understandable.
Your English is fine, it is understandable, just the formatting of the post was in my opinion not very good. The solution is good though, maybe with a small sideway, but good.
Just keep it up and help those guys when ever u can. We need those folks like u that help others out!! :thumbsup:
Hazou
Verstuurd van mijn GT-P5110
Click to expand...
Click to collapse
Will post any update 2night.
OK. Folks short update
Friend of mine who's also on xda forum gave me few tips which i tried, but no luck. Will post them here:
1. CMD: fastboot oem get_unlock_data
fastboot oem get_unlock_data
...
(bootloader) 3A25150915586129#54413233373034
(bootloader) 48354100000000000000000000#1ACF
(bootloader) 4FDA6DCEE30F10CACA1F7FC1CBD39CB
(bootloader) 08BBF#DFF3ABAE76852954D805ED6EF
(bootloader) 3FA0000
OKAY [ 0.290s]
finished. total time: 0.290s
2. fastboot oem unlock PJYERHAJMZMPVYSRKIXN
fastboot oem unlock PJYERHAJMZMPVYSRKIXN
...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 8.390s
In Motorola phone it says
Unlock
Fastboot command failed
He said that partition table is faulty. It can be done only in Linux or JTAG.
Any advice on this?
We tried this as well:
CMD: fastboot format data
(bootloader) Variable not supported!
formatting 'data' partition...
(bootloader) Variable not supported!
FAILED (remote failure)
FAILED (remote failure)
finished. total time: 0.342s
He said that emmc is faulty that's why fastboot won't work.
Had that problem too... it was due to bad Emmc. Sorry for your loss bro.
It could be indeed an emmc problem, in that case a repair at motorola can only fix it, or u will need to replace the motherboard, that will set u back another 150 dollars.
But, u successfully flashed the logo, so a part of the emmc is still working correctly i assume. btw, my knowledge about emmc problems stops here..
The next steps i should take is the following, we will reformat/partition your device, as far as it goes. But I never done this, didn't need to i only know it is possible. Everything that happens now is on your own responsibility!!
1. Download your correct firmware, must be jellybean 4.1.2 from here(firmware)
2. Extract it content in a folder like "STOCKROM"
3. Download new fastboot files from here (mfastboot,xda)
4. Extract the new mfastboot files in the folder "STOCKROM" if u named it like that.
5. Connect your device with your pc, make sure all drivers are correctly installed, and boot in fastboot mode (power + volume down)
6. Flash each of the partitions in sequence using mfastboot (is like fastboot, but can install files larger then 100mb), you need to enter the following commands one-by-one checking that each one returns an [OKAY]. If it doesnt work, i am out of ideas. sry, but report anyway what happend
7.
Code:
mfastboot flash gpt gpt_signed
mfastboot flash motoboot motoboot
mfastboot flash boot boot_signed
mfastboot flash recovery recovery_signed
mfastboot flash motobp motobp
mfastboot flash system system_signed
mfastboot flash cdrom cdrom_signed
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Good luck with it, i will hear from you.
Hazou
btw, erasing 'data' is impossible, fastboot doesn't know 'data', only 'userdata'
Hazou said:
It could be indeed an emmc problem, in that case a repair at motorola can only fix it, or u will need to replace the motherboard, that will set u back another 150 dollars.
But, u successfully flashed the logo, so a part of the emmc is still working correctly i assume. btw, my knowledge about emmc problems stops here..
The next steps i should take is the following, we will reformat/partition your device, as far as it goes. But I never done this, didn't need to i only know it is possible. Everything that happens now is on your own responsibility!!
1. Download your correct firmware, must be jellybean 4.1.2 from here(firmware)
2. Extract it content in a folder like "STOCKROM"
3. Download new fastboot files from here (mfastboot,xda)
4. Extract the new mfastboot files in the folder "STOCKROM" if u named it like that.
5. Connect your device with your pc, make sure all drivers are correctly installed, and boot in fastboot mode (power + volume down)
6. Flash each of the partitions in sequence using mfastboot (is like fastboot, but can install files larger then 100mb), you need to enter the following commands one-by-one checking that each one returns an [OKAY]. If it doesnt work, i am out of ideas. sry, but report anyway what happend
7.
Code:
mfastboot flash gpt gpt_signed
mfastboot flash motoboot motoboot
mfastboot flash boot boot_signed
mfastboot flash recovery recovery_signed
mfastboot flash motobp motobp
mfastboot flash system system_signed
mfastboot flash cdrom cdrom_signed
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Good luck with it, i will hear from you.
Hazou
btw, erasing 'data' is impossible, fastboot doesn't know 'data', only 'userdata'
Click to expand...
Click to collapse
None of them are working. Anyway i was in few repair shops in Dublin and none of them can fixed as they stated Motorola isn't popular in Ireland. Mostly i heard "i have no clue" or "You have to send to manufacturer". One of them tried fixed (it takes roughly 3 hours), but also gave up. He said that it's nearly same story with chip which Samsung S3 had. Don't ask me what does it mean, cuz have no idea. Friend of mine who's also user on that forum will fix it as he stated, but don't know if i gonna send it to Poland. At this stage i have to stop any more tests with Motorola as i don't know what i have to do.
Thanks for all support and will keep You inform if something turn up.
Btw. one of Chinese "call him tech-e" broked back cover of Motorola (beside camera, cracked glass), but i noticed it when i left his repair centre.
Thanks
Okey, best of luck!
Hazou
Verstuurd van mijn XT890
So, is there a way to flash the update to 5.0.1? I'm unlocked, rooted, and still encrypted. I want to stay encrypted. Sorry, just my own paranoia I guess. But is there a way to do it as an update without wiping the device and having to restore a backup? I have had too many backups fail in the past, and I'm kinda lazy. Plus its been a long time since I played with flashing an Android. since my old EVO 4G. LOL Thanks all. Oh yeah, if it matters, I'm on a T-Mobile Nexus 6.
scothern99 said:
So, is there a way to flash the update to 5.0.1? I'm unlocked, rooted, and still encrypted. I want to stay encrypted. Sorry, just my own paranoia I guess. But is there a way to do it as an update without wiping the device and having to restore a backup? I have had too many backups fail in the past, and I'm kinda lazy. Plus its been a long time since I played with flashing an Android. since my old EVO 4G. LOL Thanks all. Oh yeah, if it matters, I'm on a T-Mobile Nexus 6.
Click to expand...
Click to collapse
The flash-all.bat script doesn't work anyway, so don't use it. Just use fastboot and flash:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
---------- Post added at 02:12 PM ---------- Previous post was at 02:02 PM ----------
You can turn that into a simple bat file to use if you like. Just copy and past the following (in between dashes) into notepad and save as something like nexus-flash.bat:
--------------------------
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
echo Press any key to exit...
pause >nul
exit
---------------------------------------
If you have named the twrp recovery something other than what it downloads as, be sure to adjust the file name in the script.
This assumes that all the files are in the same folder including the platform tools. So you would need to extract everything into the same folder.
livinginkaos said:
The flash-all.bat script doesn't work anyway, so don't use it. Just use fastboot and flash:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
(wait for reboot)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
---------- Post added at 02:12 PM ---------- Previous post was at 02:02 PM ----------
You can turn that into a simple bat file to use if you like. Just copy and past the following (in between dashes) into notepad and save as something like nexus-flash.bat:
--------------------------
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
echo Press any key to exit...
pause >nul
exit
---------------------------------------
If you have named the twrp recovery something other than what it downloads as, be sure to adjust the file name in the script.
This assumes that all the files are in the same folder including the platform tools. So you would need to extract everything into the same folder.
Click to expand...
Click to collapse
Ok, so not to be a noob, where do I get the image files to flash?
Nexus images are all posted here - https://developers.google.com/android/nexus/images
Ok, so I used the toolkit to unlock/root, I'm assuming then that to use this script you posted, I would need to download the actual ADB/Fastboot files separately?
Sorry for the stupid questions, I'm learning all over again, and this is my first Nexus device.
EDIT: So it looks like I can use the toolkit to individually flash the system image and then the radio. Will that work doing it in that order?
scothern99 said:
Ok, so I used the toolkit to unlock/root, I'm assuming then that to use this script you posted, I would need to download the actual ADB/Fastboot files separately?
Sorry for the stupid questions, I'm learning all over again, and this is my first Nexus device.
EDIT: So it looks like I can use the toolkit to individually flash the system image and then the radio. Will that work doing it in that order?
Click to expand...
Click to collapse
Does anyone know if this is correct?
What I did to upgrade without wiping, i was on stock with elementalx kernel, root and twrp.
Only flashed radio and system img.
1. Downloaded images, extracted zip of the images.
2. Reboot to bootloader
3. Fastboot commands
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
4. Reboot to bootloader again
Run chainfire autoroot script.
5. Done
Remember to read read read if you don't know what are you doing, nobody here is responsible if things go wrong.
With my past phones, there was always a stock rom posted shortly after the update came out. I would just flash that over what I had already to update. Is there some reason why no one has posted any stock roms for the nexus 6?
lion1750 said:
With my past phones, there was always a stock rom posted shortly after the update came out. I would just flash that over what I had already to update. Is there some reason why no one has posted any stock roms for the nexus 6?
Click to expand...
Click to collapse
I'm wondering the same. Usually it was out right away and I would do the same as you. Seems crazy to me that we would have to unroot update and reroot agaain.
Usually I would flash a stock rom with the update that the dev would also throw root into.
livinginkaos said:
Then, I like to boot directly into twrp and flash supersu.zip to reroot (I don't flash twrp on, just boot into it)
fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
Click to expand...
Click to collapse
Can you do this as opposed to using the CF-Auto-Root-shamu-shamu-nexus6.zip to root for the very first time as well?
GMoGoody said:
Can you do this as opposed to using the CF-Auto-Root-shamu-shamu-nexus6.zip to root for the very first time as well?
Click to expand...
Click to collapse
You bet. You can be sure to have the most recent SuperSU that way as well. CF-Auto isn't always updated as quickly.
http://download.chainfire.eu/supersu
livinginkaos said:
You bet. You can be sure to have the most recent SuperSU that way as well. CF-Auto isn't always updated as quickly.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
That su 2.4zip is for all devices? Not just for the n7 fhd? Thx
Via my NeXus™ 7FHD on XDA Premium app
So today I got an update for a new firmware, it was a small 125 mb patch, no big deal. I downloaded it and installed it a couple of hours later, I leave it to install and when I'm back my phone is frozen on the Motorola logo and the "Powered by android" text written below, but it won't get past that. I left it for almost an hour and it won't boot, I tried forcing a reboot and it gets me back to the same screen.
Is there any way I could fix it, preferably while keeping my data? Especially the what's app gallery.
Thanks a lot guys, I'm kinda panicking here.
Ps. I'm not rooted, everything is completely stock.
it's Stuck on Moto Boto logo ?
Yes. I tried doing a factory reset and that doesn't work either, it sends me right back to the boot logo.
Sorry to not have any solutions but my girlfriends phone has probably had the exact same thing happen. At about 10PM tonight she got an update notification and told it to install. almost two hours later she checked the phone again to see it stuck on the boot logo and incredibly hot. She restarted it and same thing, stuck on the boot logo. Same as you, completely stock phone. Never been modified in anyway.
I had her go into recovery and wipe cache, no change at all. I've now had her do a factory reset twice as some similar problems mentioned that as a solution. No change, still just gets stuck on the boot screen.
My assumption at this point is that this update has completely trashed the phone and it's completely unrecoverable on the device at least.
I'm willing to learn how to install a new rom from scratch if that would help, preferably a stock one. The problem is that Motorola doesn't have any stores where I live, I ordered my phone off amazon.
So is there any method to fix it? You can instruct me if you could or at least tell me what to look for on google.
Thanks a lot man.
darthlawl said:
I'm willing to learn how to install a new rom from scratch if that would help, preferably a stock one. The problem is that Motorola doesn't have any stores where I live, I ordered my phone off amazon.
So is there any method to fix it? You can instruct me if you could or at least tell me what to look for on google.
Thanks a lot man.
Click to expand...
Click to collapse
I didn't think that you have any way to install urself stock without voiding warranty so u have 2 choices u can go for service or unlock and install any rom u want
vaisakmct said:
I didn't think that you have any way to install urself stock without voiding warranty so u have 2 choices u can go for service or unlock and install any rom u want
Click to expand...
Click to collapse
My warranty is already over, I just want stock because I like it.
Are you sure a rom installation would work?
Ps. I can't unlock the bootloader since I can't access the OS
Unlock boot loader does not acess to os it is simple
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
Just go to fastboot mode and unlocking can done from pc and install twrp then u can flash roms
vaisakmct said:
Unlock boot loader does not acess to os it is simple
---------- Post added at 01:25 AM ---------- Previous post was at 01:23 AM ----------
Just go to fastboot mode and unlocking can done from pc and install twrp then u can flash roms
Click to expand...
Click to collapse
What do you mean?
I'm a total beginner when it comes to android, I'm more of a windows guy. Can you walk me through the steps?
It´s not that easy to guide someone through all the steps. First thing you have to do is unlock your bootloader,described here: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728. Read all the steps,it´s not that difficult.
You need all the drivers,by motorola and android, linked in the tutorial. I recomend Minimal ADB and Fastboot instead of Android SDK, it´s easier. Install it in the root of your windows partition,like C:\Minimal ADB and Fastboot. So if you open a command prompt the path is short and you know it.
After the unlock process you´ll need to flash a custom recovery, you can read how to do that here: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818.
There´s a part called Flashing TWRP Recovery . You don´t need to do that with Flashify (you surely can if you want but I think this way is easier to do), just download the custom recovery TWRP from here: https://dl.twrp.me/titan/.
Place the .img file in the Minimal ADB and Fastboot folder and connect the phone to the PC. After that you open a command prompt again from the Minmal ADB and fastboot folder (open the folder and hold Shift and right click and press "open command window here".
Now type the command
Code:
adb reboot bootloader
When the phone has booted to bootloader type
Code:
fastboot devices
A string of numbers should appear,that means your phone is connected.
Now type
fastboot flash recovery "name of the downloaded TWRP .img file", in your case that should be
Code:
fastboot flash recovery twrp-2.8.6.0-titan.img
Now everytime when you boot to recovery you´ll see a menu with a lot of features like install,wipe,backup,restore etc.
From here you can flash any rom you like, a stock rom, a stock based rom or any other like cyanogen or AOSP.
If you want to flash stock again you´ll need to know the name of your firmware,it differs from country and version. You can search for it here: http://forum.xda-developers.com/moto-g-2014/development/original-motorola-firmware-collection-t3153533.
It´s late now here, if you are at this point and have decided what rom to flash post again or pm me.
I hope my exclamation is understandable and I´ve made no faults, everyone else please correct me then!
Wolfcity said:
It´s not that easy to guide someone through all the steps. First thing you have to do is unlock your bootloader,described here: http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728. Read all the steps,it´s not that difficult.
You need all the drivers,by motorola and android, linked in the tutorial. I recomend Minimal ADB and Fastboot instead of Android SDK, it´s easier. Install it in the root of your windows partition,like C:\Minimal ADB and Fastboot. So if you open a command prompt the path is short and you know it.
After the unlock process you´ll need to flash a custom recovery, you can read how to do that here: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818.
There´s a part called Flashing TWRP Recovery . You don´t need to do that with Flashify (you surely can if you want but I think this way is easier to do), just download the custom recovery TWRP from here: https://dl.twrp.me/titan/.
Place the .img file in the Minimal ADB and Fastboot folder and connect the phone to the PC. After that you open a command prompt again from the Minmal ADB and fastboot folder (open the folder and hold Shift and right click and press "open command window here".
Now type the command
Code:
adb reboot bootloader
When the phone has booted to bootloader type
Code:
fastboot devices
A string of numbers should appear,that means your phone is connected.
Now type
fastboot flash recovery "name of the downloaded TWRP .img file", in your case that should be
Code:
fastboot flash recovery twrp-2.8.6.0-titan.img
Now everytime when you boot to recovery you´ll see a menu with a lot of features like install,wipe,backup,restore etc.
From here you can flash any rom you like, a stock rom, a stock based rom or any other like cyanogen or AOSP.
If you want to flash stock again you´ll need to know the name of your firmware,it differs from country and version. You can search for it here: http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533.
It´s late now here, if you are at this point and have decided what rom to flash post again or pm me.
I hope my exclamation is understandable and I´ve made no faults, everyone else please correct me then!
Click to expand...
Click to collapse
Its good guide follow these steps
If you want to go stock, I recommend you to go with the mfastboot method . . .
because it doesn't even need unlocked bootloader or any recovery,
The following link is having a mfastboot folder, in which, Moto G 2014(XT1068) stock 5.0.2 factory firmware is stored and, you just have to extract the folder and open it then pressing & holding shift + RMB and select "Open Command Window Here".
(Now press Power + Volume Down simultaneously, and you should go to the bootloader mode, if you don't know that )
Now in the command window, check your phone is connected with USB and type below code and press Enter.
Code:
fastboot devices
if any code(like for eg. ZDMJK2312) is shown, you're connected,
if not, try reconnecting the USB and try again.
Once properly connected, now you can flash the follwing commands one by one, to get your device to life.
Code:
Moto G 2014 Stock 5.0.2 Restore Script
------------------------------------------------------------------|
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash system system.img_sparsechunk.4
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
mfastboot.exe reboot
------------------------------------------------------------------|
BTW this happened to me 6 months back and the same helped me.
mfastboot
Note : The above method is for only the model XT1068, because the firmware in the folder is for that model only, so plz make sure your model before proceeding.
And plz follow each and every step properly.
Thanks . . .
Alright thanks people! I'll try ArtRahul's method since it's easier and i was quite satisfied with stock. If that doesn't work I'll try Wolfcity's method.
Alright, so this is an update. ArtRahul's method works great and it's really easy. If anyone looks for a solution and finds this thread, just make sure you find the exact model of your phone and google the firmware. Here's where I found mine
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
It has links to other versions too. Good luck!
darthlawl said:
What do you mean?
Click to expand...
Click to collapse
if ur phone is going to fastboot mode u can install twrp, no os is needed for doing this
darthlawl said:
Ps. I can't unlock the bootloader since I can't access the OS
Click to expand...
Click to collapse
darthlawl said:
What do you mean?
Click to expand...
Click to collapse
you don't have to access to os in order to unlock the bootloader, go to android development section on this forum for moto g 2014 & follow any thread that guides about unlocking bootloader.
darthlawl said:
Alright, so this is an update. ArtRahul's method works great and it's really easy. If anyone looks for a solution and finds this thread, just make sure you find the exact model of your phone and google the firmware. Here's where I found mine
http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
It has links to other versions too. Good luck!
Click to expand...
Click to collapse
did anything work?
my moto g2 was rooted .i got notification that update 5.1.1 is available .but after update it is stuck in bootloop::crying:
---------- Post added at 03:17 AM ---------- Previous post was at 03:03 AM ----------
it is giving me failed to validate system image error after first command mfastboot.exe oem lock begin