[GUIDE][Osprey] Fastboot Flashing Factory Firmware Images

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,326
0
bro, my boot loader is unlocked , status code : 3 , software status : modified
These are Factory Firmware Images. They are not supposed to be used for downgrading. They are only meant to be used to upgrade phones. There is no guarantee downgrading will work at all, and can destroy your phone in the process.

If your Bootloader is already unlocked, then there is nothing you can do to make your phone accept the Firmware Image.
 

ASHLEY117

Senior Member
Jun 9, 2011
980
407
93
Someshire
These are Factory Firmware Images. They are not supposed to be used for downgrading. They are only meant to be used to upgrade phones. There is no guarantee downgrading will work at all, and can destroy your phone in the process.

If your Bootloader is already unlocked, then there is nothing you can do to make your phone accept the Firmware Image.
This may answer my question as well then.
Unlocked bootloader and when I flash 6.0.1 xt1541 following you're guide it will not boot or flash bootloader. Sticks in a loop between stock recovery "erasing" and bootloader unlocked warning.
Would relocking bootloader help?
 

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,326
0
This may answer my question as well then.
Unlocked bootloader and when I flash 6.0.1 xt1541 following you're guide it will not boot or flash bootloader. Sticks in a loop between stock recovery "erasing" and bootloader unlocked warning.
Would relocking bootloader help?
Are you doing a 'Factory data reset' in Stock Recovery prior to flashing? It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
 

ASHLEY117

Senior Member
Jun 9, 2011
980
407
93
Someshire
Are you doing a 'Factory data reset' in Stock Recovery prior to flashing? It would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
I flash stock recovery and full wipe prior to flashing and only happens when flashing 6.0.1.
I'll post screenshots and logs when I get home later.
 

russrn16

Member
Jul 12, 2015
16
3
0
I flash stock recovery and full wipe prior to flashing and only happens when flashing 6.0.1.
I'll post screenshots and logs when I get home later.
i Have the same problem as you. I just realised that, on lost101's guide there was no line for:
system.img_sparsechunk.7
just flash that and everything will work.

and also there is a file called :
"slcf_rev_b_default_v1.0.nvm"
i dunno if i should flash it.
 
Last edited:
  • Like
Reactions: lost101

lost101

Inactive Recognized Contributor
May 30, 2008
7,434
9,326
0
i Have the same problem as you. I just realised that, on lost101's guide there was no line for:
system.img_sparsechunk.7
just flash that and everything will work.
I've added two extra sparsechunk commands in OP to cover this in future.
 

ASHLEY117

Senior Member
Jun 9, 2011
980
407
93
Someshire
i Have the same problem as you. I just realised that, on lost101's guide there was no line for:
system.img_sparsechunk.7
just flash that and everything will work.

and also there is a file called :
"slcf_rev_b_default_v1.0.nvm"
i dunno if i should flash it.
I always check before flashing and flash all sparsechunks. Its only bootloader fail. Preflash check is OK and everything else flashes fine.
 

evnee

Senior Member
May 19, 2012
51
5
0
Łódź
mhm... got a question.
i bought this phone, with boot loop.
i reflashed the stock rom successfully
still bootloop
i cant get into recovery (nothing happens)
i cant unlock bootloader(allow oem unlock option wasnt turned on and i cant get into system)

what should i do now? i have time to wednesday to get my money back
 

ExaHamza

Senior Member
Jul 12, 2015
314
86
58
26
Maputo
Two questions
1.Why the bootloader is not relocked?
I have used this guide to flash firmwares on Windows, but on Ubuntu I'm facing a problem, when my smartphone is on is recognised, but on bootloader mode no.
On bootloader logs shows USB Connected, but no command is recognised.

Sorry for my bad English!:silly:
 

Tel864

Senior Member
Nov 22, 2011
3,011
1,093
253
Greenville
Two questions
1.Why the bootloader is not relocked?
I have used this guide to flash firmwares on Windows, but on Ubuntu I'm facing a problem, when my smartphone is on is recognised, but on bootloader mode no.
On bootloader logs shows USB Connected, but no command is recognised.

Sorry for my bad English!:silly:
Try '"fastboot devices" again after you get into bootloader. Sometimes that works or run fastboot as root/sudo

Sent from my SM-T530NU using XDA-Developers mobile app
 

acejavelin

Recognized Contributor
Sep 3, 2009
6,835
3,318
0
Lincoln, ND
Two questions
1.Why the bootloader is not relocked?
I have used this guide to flash firmwares on Windows, but on Ubuntu I'm facing a problem, when my smartphone is on is recognised, but on bootloader mode no.
On bootloader logs shows USB Connected, but no command is recognised.

Sorry for my bad English!:silly:
The bootloader cannot be relocked, there is no need to anyway.

Use 'sudo fastboot xxxx' for the commands or 'sudo su' prior to issuing fastboot commands.

Also, if you are using the Ubuntu repository package for fastboot, it's an older version... Try updating to the current one.

Sent from my MotoG3 using Tapatalk
 

ExaHamza

Senior Member
Jul 12, 2015
314
86
58
26
Maputo
Try '"fastboot devices" again after you get into bootloader. Sometimes that works or run fastboot as root/sudo
Solved by running as root!
Now why we are not able to relock bootloader?
Is there anything wrong with bootloader?
A few months back, I'm no longer user root, I'm satisfied with Stock ROM, and I don't need any tricks more, that's why I want to relock, but I just can't do it!!
 

Tel864

Senior Member
Nov 22, 2011
3,011
1,093
253
Greenville
Solved by running as root!
Now why we are not able to relock bootloader?
Is there anything wrong with bootloader?
A few months back, I'm no longer user root, I'm satisfied with Stock ROM, and I don't need any tricks more, that's why I want to relock, but I just can't do it!!
That's just the way it is. Once you unlock a Moto, it sets that status and it can't be undone. You will always be unlocked.

Sent from my SM-T530NU using XDA-Developers mobile app
 

qwertyiapine

Member
May 14, 2016
16
4
0
XT1541 boot loop?

Hello all at XDA, this is a very helpful community that I am hoping can provide some advice to enable my XT1541 8Gb 1Gb with locked bootloader to boot again.
I spent in excess of 12 hours on it yesterday meticulously reading every page of this thread, and the first seven of 100+ pages of the stock rom page trying and retrying the helpful suggestions offered to others with similar problems.
I will provide as many details of what I have tried as I can remember, but first the history, which is mostly unknown and may be the reason why nothing has worked.
I bought the phone from ebay, listed as being stuck in a boot loop after having a replacement screen fitted. Not much to work with, not even being clear as to whether or not the boot loop first appeared immediately after the replacement, or later on.
There were posts in this thread from somebody who said his phone looped after replacing the screen, but was never solved due to possibly damaging the ribbon afterwards.
The screen on mine is likely to be one of these compatible screens, rather than oem and wonder if this may be part of the problem? drivers?

When I received the phone, the first thing I did was connect it to a wall charger. The screen lit up to the Motorola splash screen (non animated), then briefly showed an empty battery icon before the screen going blank, followed by the same boot screen, over and over.
I thought that perhaps there was not enough power to boot the OS (like the issue previous Moto G's had) so left it for a while to try and charge. I swapped the charger over for a 2A to provide as much power as I could but nothing changed apart from the dead battery icon no longer showing before the next loop. It was unclear though if the screen constantly lighting up was draining out any useful charge being put in thus never being able to complete the boot like previous models suffered with.

I then held down VOL- and the phone entered fastboot. I connected to phone to a usb port on my pc, information showed that usb was connected, battery went from red low (charging) to green ok (charging) so I again left it to try and charge the battery even though the screen was lit.

I then tried the different options available. Start, Recovery, Factory etc. All of these options resulted in the splash screen looping. No red exclamation mark when trying to enter recovery. The only option that works is barcode.

Running Ubuntu
Code:
lsusb
showed the Motorola was connected, so I confirmed with
Code:
sudo fastboot devices
which showed the serial number of the phone.
I again tried to select recovery which failed.

Searching for stock firmware brought me to Moto G (3rd Gen) Factory Firmware Images, and to this guide linked at the top of it.
I did some reading to select which firmware to download, not knowing what was installed already, and the associated problems of attempting to downgrade, so I chose the only 6.0.1 1GB image available which would hopefully be a match, or an upgrade.

I immediately had a problem because the first step was to perform a factory reset which I could only attempt by
Code:
sudo fastboot erase cache
and
Code:
sudo fasboot erase userdata
which reading suggests does not work, and a reset should either be performed from within Android, or via recovery. Neither of which I have access to so all I can do is try.

I downloaded and flashed XT1541_OSPREY_RETEU_6.0.1_MPI24.107-55_cid7 performing each command one line at a time, and flashed all 7 sparsechunks.
Everything reported ok with no errors using all the commands listed in the how to.
Result was the same boot loop. I tried two more times, no errors, but still looping.

I read suggestions to try 6.0, or 5.1..1, the exact details and order are now unclear but there were different errors at each attempt, so after each failure I would reflash 6.0.1, try it, and then another firmware, or suggestion as I came to them in this thread.
However further into the thread, but not mentioned earlier on whilst attempting to downgrade I read that I should not attempt to flash the bootloader, but too late as I had already followed instructions that omitted that line. Also do not try and flash gpt.bin which was another error I had, so I would try again armed with the new information which would fail, followed by me reflashing 6.0.1 again.

I read that unlocking the bootloader helps, so I got the unlock code from Motorola but could not unlock the bootloader as I cannot check the enable oem unlock box in developer options.
Various attempts to try various commands all failed due to the locked bootloader, I cannot think now, but just about everything in these previous pages.
Cannot load TWRP instead of installing, flashing stock recovery, then rebooting into recovery all fail.

Next I reboot into Win7 and try everything again using mfastboot instead of fastboot. I also installed RSDlite 6.2.4 and tried even more images.
Nothing has worked.

By this time the phone has been connected via usb for hours so I presume that the battery now has sufficient power to boot, but cannot know for certain.
My other concern is this screen, could it be the culprit?

I know I have not listed everything that I have tried because now it is all a blur, but I would appreciate any help that anybody has to offer.
Not knowing the full history could mean that somebody has bricked it beyond rescue but there may be things still to try?

If anybody can do this, it will be somebody from here.
I shall wait impatiently and hope for any further tips to try. Thanks in advance......
 

Gravemind2015

Senior Member
Dec 1, 2015
1,846
861
143
Hello all at XDA, this is a very helpful community that I am hoping can provide some advice to enable my XT1541 8Gb 1Gb with locked bootloader to boot again.
I spent in excess of 12 hours on it yesterday meticulously reading every page of this thread, and the first seven of 100+ pages of the stock rom page trying and retrying the helpful suggestions offered to others with similar problems.
I will provide as many details of what I have tried as I can remember, but first the history, which is mostly unknown and may be the reason why nothing has worked.
I bought the phone from ebay, listed as being stuck in a boot loop after having a replacement screen fitted. Not much to work with, not even being clear as to whether or not the boot loop first appeared immediately after the replacement, or later on.
There were posts in this thread from somebody who said his phone looped after replacing the screen, but was never solved due to possibly damaging the ribbon afterwards.
The screen on mine is likely to be one of these compatible screens, rather than oem and wonder if this may be part of the problem? drivers?

When I received the phone, the first thing I did was connect it to a wall charger. The screen lit up to the Motorola splash screen (non animated), then briefly showed an empty battery icon before the screen going blank, followed by the same boot screen, over and over.
I thought that perhaps there was not enough power to boot the OS (like the issue previous Moto G's had) so left it for a while to try and charge. I swapped the charger over for a 2A to provide as much power as I could but nothing changed apart from the dead battery icon no longer showing before the next loop. It was unclear though if the screen constantly lighting up was draining out any useful charge being put in thus never being able to complete the boot like previous models suffered with.

I then held down VOL- and the phone entered fastboot. I connected to phone to a usb port on my pc, information showed that usb was connected, battery went from red low (charging) to green ok (charging) so I again left it to try and charge the battery even though the screen was lit.

I then tried the different options available. Start, Recovery, Factory etc. All of these options resulted in the splash screen looping. No red exclamation mark when trying to enter recovery. The only option that works is barcode.

Running Ubuntu
Code:
lsusb
showed the Motorola was connected, so I confirmed with
Code:
sudo fastboot devices
which showed the serial number of the phone.
I again tried to select recovery which failed.

Searching for stock firmware brought me to Moto G (3rd Gen) Factory Firmware Images, and to this guide linked at the top of it.
I did some reading to select which firmware to download, not knowing what was installed already, and the associated problems of attempting to downgrade, so I chose the only 6.0.1 1GB image available which would hopefully be a match, or an upgrade.

I immediately had a problem because the first step was to perform a factory reset which I could only attempt by
Code:
sudo fastboot erase cache
and
Code:
sudo fasboot erase userdata
which reading suggests does not work, and a reset should either be performed from within Android, or via recovery. Neither of which I have access to so all I can do is try.

I downloaded and flashed XT1541_OSPREY_RETEU_6.0.1_MPI24.107-55_cid7 performing each command one line at a time, and flashed all 7 sparsechunks.
Everything reported ok with no errors using all the commands listed in the how to.
Result was the same boot loop. I tried two more times, no errors, but still looping.

I read suggestions to try 6.0, or 5.1..1, the exact details and order are now unclear but there were different errors at each attempt, so after each failure I would reflash 6.0.1, try it, and then another firmware, or suggestion as I came to them in this thread.
However further into the thread, but not mentioned earlier on whilst attempting to downgrade I read that I should not attempt to flash the bootloader, but too late as I had already followed instructions that omitted that line. Also do not try and flash gpt.bin which was another error I had, so I would try again armed with the new information which would fail, followed by me reflashing 6.0.1 again.

I read that unlocking the bootloader helps, so I got the unlock code from Motorola but could not unlock the bootloader as I cannot check the enable oem unlock box in developer options.
Various attempts to try various commands all failed due to the locked bootloader, I cannot think now, but just about everything in these previous pages.
Cannot load TWRP instead of installing, flashing stock recovery, then rebooting into recovery all fail.

Next I reboot into Win7 and try everything again using mfastboot instead of fastboot. I also installed RSDlite 6.2.4 and tried even more images.
Nothing has worked.

By this time the phone has been connected via usb for hours so I presume that the battery now has sufficient power to boot, but cannot know for certain.
My other concern is this screen, could it be the culprit?

I know I have not listed everything that I have tried because now it is all a blur, but I would appreciate any help that anybody has to offer.
Not knowing the full history could mean that somebody has bricked it beyond rescue but there may be things still to try?

If anybody can do this, it will be somebody from here.
I shall wait impatiently and hope for any further tips to try. Thanks in advance......
Probably the screen is the culprit. Many have reported boot loop with these outsider-made-screens.You can try finding an original oem one,at least to boot into android to enable oem unlock and subsequently unlock it, then reflash everything. I can't guaranty it will work with present screen. Can the phone be returned back? If so, it would be a good idea if you are seriously investing in the phone.

Broadcasted from Zeta Reticuli
 
  • Like
Reactions: qwertyiapine
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone