Related
Hi guys! How are you? I hope you are fine, because I'm not lol.
Well, I'm new in this things, but I can install CM9 and 7 in my old devices thanks to your guides and tutorials, I really apreciated!.
But now, I'm stucking with my new phone, because I flashed wrong and I don't know what to do.
Ok let's start to explain my problem:
My phone is stucked in the fastboot screen and no advance. When I press "pwr vol+-" and select Recovery, nothing happens, only showme the "Motorola Dual Core Technology logo" and returns to fastboot.
...........................................................................
AP FastBoot Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
FastBoot Reason: Sticky bit factory_fastboot
...........................................................................
Ok, and when try to enter to recovery screen "pwr, vol+-" it's show me:
...........................................................................
Invalid Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
...........................................................................
Sometimes, indicate "Batery Low"...its very frustrating because I love my ohine but I can't make work and I don't know what is happend...
I see some tutorials, specialy from @sleevydude, to unlock the bootloader, but the "fastboot.exe" appears and dissapears, and I can't acces to program tools...
Another big problem, I'm from Argentina, and my language is spanish, after all, my english is good, and I can understand 90% if you say something...sorry if that is offtopic or something.
I've tryed with the metod from TheMythTeam, but doesn't work...keep stucked...
Ok guys, I hope you help me...miss my phone so much
Well you can't open the fastboot.exe because it's not a regular program. You just open a command Window in the folder it's located in.
Sent from my PACMAN MATRIX HD MAXX
It looks to me like your device has a locked bootloader.
What rom did you try to flash? What did you use to flash it?
deeje00 said:
Well you can't open the fastboot.exe because it's not a regular program. You just open a command Window in the folder it's located in.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Thanks mate, I'm testing the commands, but maybe I'll look at the tutorials carefully!
Soon I will have them new, wishing luck! :good:
audit13 said:
It looks to me like your device has a locked bootloader.
What rom did you try to flash? What did you use to flash it?
Click to expand...
Click to collapse
Hi! this ROM..
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml
I've used RSD Lite...but I think the problem is the bootloader locked...like you said!
Ok, I trying again...let's see what I can do.
Thanks for answer :good:
Ok...I found a new problem, and suspect this is the big problem of all problems!
My computer can't recognize the device, I successfully installed Motorola USB drivers (2.3.9 version) and when I trying to unlock the bootloader ussing Motopocalypse by Dan, doesn't happens...shows the follow message:
Waiting for device...
* daemon not running. starting it now in port 5037 *
* daemon started successfully *
And then, nothings is happens!...not show anything more....
Any suggestions?
Please hel me! :crying:
What OS was originally on the phone? Without an unlocked bootloader, I don't think you can flash an earlier rom version if the original rom version was higher.
I think those zip files needs to flashed via cwm, but I'm not 100% sure. I think that's how I got the Mexico Retail onto my Atrix HD.
You could try this: http://forum.xda-developers.com/showthread.php?t=2299113 or http://forum.xda-developers.com/showthread.php?t=2259661
Stock roms: http://forum.xda-developers.com/showthread.php?t=2209660
audit13 said:
What OS was originally on the phone? Without an unlocked bootloader, I don't think you can flash an earlier rom version if the original rom version was higher.
I think those zip files needs to flashed via cwm, but I'm not 100% sure. I think that's how I got the Mexico Retail onto my Atrix HD.
You could try this: http://forum.xda-developers.com/showthread.php?t=2299113 or http://forum.xda-developers.com/showthread.php?t=2259661
Stock roms: http://forum.xda-developers.com/showthread.php?t=2209660
Click to expand...
Click to collapse
I try manually, but I keep getting the same errors as the automatic method, and not to do, should I throw it away and buy a new motherboard or buy on eBay?
As the phone is AT & T USA, I have no warranty here in Argentina ...
I'm really frustrated .....
Here are the errors:
> fastboot flash system system.img.ext4
sending 'system' (262144 KB) ...
OKAY [19.854s]
writing 'system' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 20.155s
> fastboot flash boot boot.img
sending 'boot' (10240 KB) ...
OKAY [0.865s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 1.137s
if anyone knows anything more, or want help clarify that this LOCKED BOOTLOADER
Wipe and Restore
Checkout my post on this thread. Just skip making a backup.
http://forum.xda-developers.com/showthread.php?t=2394238
PM me and click Thanks if I helped.
lucasantarella said:
Checkout my post on this thread. Just skip making a backup.
http://forum.xda-developers.com/showthread.php?t=2394238
PM me and click Thanks if I helped.
Click to expand...
Click to collapse
Thanks! I would try and let's see what happens!
**sorry for my bad english**
Reactorzero said:
I try manually, but I keep getting the same errors as the automatic method, and not to do, should I throw it away and buy a new motherboard or buy on eBay?
As the phone is AT & T USA, I have no warranty here in Argentina ...
I'm really frustrated .....
Here are the errors:
> fastboot flash system system.img.ext4
sending 'system' (262144 KB) ...
OKAY [19.854s]
writing 'system' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 20.155s
> fastboot flash boot boot.img
sending 'boot' (10240 KB) ...
OKAY [0.865s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
finished. Total time: 1.137s
if anyone knows anything more, or want help clarify that this LOCKED BOOTLOADER
Click to expand...
Click to collapse
Try using fastboot binaries from skeevy 's thread..
Sent from my MB886 using xda app-developers app
Reactorzero said:
Hi guys! How are you? I hope you are fine, because I'm not lol.
Well, I'm new in this things, but I can install CM9 and 7 in my old devices thanks to your guides and tutorials, I really apreciated!.
But now, I'm stucking with my new phone, because I flashed wrong and I don't know what to do.
Ok let's start to explain my problem:
My phone is stucked in the fastboot screen and no advance. When I press "pwr vol+-" and select Recovery, nothing happens, only showme the "Motorola Dual Core Technology logo" and returns to fastboot.
...........................................................................
AP FastBoot Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
FastBoot Reason: Sticky bit factory_fastboot
...........................................................................
Ok, and when try to enter to recovery screen "pwr, vol+-" it's show me:
...........................................................................
Invalid Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
...........................................................................
Sometimes, indicate "Batery Low"...its very frustrating because I love my ohine but I can't make work and I don't know what is happend...
I see some tutorials, specialy from @sleevydude, to unlock the bootloader, but the "fastboot.exe" appears and dissapears, and I can't acces to program tools...
Another big problem, I'm from Argentina, and my language is spanish, after all, my english is good, and I can understand 90% if you say something...sorry if that is offtopic or something.
I've tryed with the metod from TheMythTeam, but doesn't work...keep stucked...
Ok guys, I hope you help me...miss my phone so much
Click to expand...
Click to collapse
I just realized that your system image says ".ext4" Fastboot does not normally format a partition as ext4 by default, maybe never at all. Make sure you have the correct Fastboot files.
Best of luck!
---------- Post added at 10:40 AM ---------- Previous post was at 10:31 AM ----------
Reactorzero said:
Thanks! I would try and let's see what happens!
**sorry for my bad english**
Click to expand...
Click to collapse
Just to try, flash this Fastboot package with RSD Lite 6.1. I have a feeling this will work.
Package: http://sbfdownload.droid-developers..._FFW-20-27-release-keys-ATT-US_BuildA.xml.zip
** I take no responsibility for any damage done to your phone. **
---------- Post added at 10:49 AM ---------- Previous post was at 10:40 AM ----------
The reason I believe my blast post will work is because your error while trying to flash says
.................................................. .........................
Invalid Flash Mode (S)
10.98(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
.................................................. .........................
Click to expand...
Click to collapse
You are flashing a downgraded version of the boot image. If you came from 4.1.1 and are now trying to flash a 4.0.4 boot image, it will fail. Try to flash the package in my last post
lucasantarella said:
I just realized that your system image says ".ext4" Fastboot does not normally format a partition as ext4 by default, maybe never at all. Make sure you have the correct Fastboot files.
Best of luck!
---------- Post added at 10:40 AM ---------- Previous post was at 10:31 AM ----------
Just to try, flash this Fastboot package with RSD Lite 6.1. I have a feeling this will work.
Package: http://sbfdownload.droid-developers..._FFW-20-27-release-keys-ATT-US_BuildA.xml.zip
** I take no responsibility for any damage done to your phone. **
---------- Post added at 10:49 AM ---------- Previous post was at 10:40 AM ----------
The reason I believe my blast post will work is because your error while trying to flash says
You are flashing a downgraded version of the boot image. If you came from 4.1.1 and are now trying to flash a 4.0.4 boot image, it will fail. Try to flash the package in my last post
Click to expand...
Click to collapse
Hi mate, many thanks! I would try your way of flashing, I'm nothing to loose in this point...let's see what happens now and I tell you later, thanks again for your answer
Aingaran said:
Try using fastboot binaries from skeevy 's thread..
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
It doesn`t works in this case...flashing with snapdragon's fastboot :crying:
Did my RSD method work? Have you attempted it yet?
Sent from my Atrix HD
Hello
I have the same problem...
The bootloader is locked, the phone not rooted. I try to flash with RSD lite and Mexico Retail rom, but RSD give an error.
And the message is:
Partition (Boot) Security Version Downgraded
Fastboot Reason: Boot Failure
Thank your for help!
First try and get to stock. Then get Mexican retail.
Sent from my GT-P3110 using xda app-developers app
lucasantarella said:
First try and get to stock. Then get Mexican retail.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
When I try go back to stock, the phone (and RSD) get a message:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
RSD:
"Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL.
tomchy said:
When I try go back to stock, the phone (and RSD) get a message:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
RSD:
"Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL.
Click to expand...
Click to collapse
Make sure you are using the 4.1.1 fastboot package for RSD Lite. Also make sure you are using RSD Lite 6.1.
tomchy said:
When I try go back to stock, the phone (and RSD) get a message:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
RSD:
"Failed flashing process. 1/23 flash partition "gpt_main0.bin" -> Phone returned FAIL.
Click to expand...
Click to collapse
Unzip the rom zip and open .xml file and remove the line having flash partition gpt_main0.bin and save it, zip again using red, you will be able to flash now..
Hello xda community, I'd like to start with saying all the work done on this forum for open-source, freeware, and general android tweaks is awesome! Thank you.
So awesome in fact that I got a little bit ahead of myself with my new "Sprint HTC One". I followed this guide http://forum.xda-developers.com/showthread.php?t=2244060 to Unlock the bootloader, and root my phone. I then went a step further and wanted to flash a custom Rom. I followed this video, but strayed a little bit (whoops!). I went into twrp recovery, and flashed the "Beanstalk" super custom 4.3 (9/24/2013), along with smw6180_superwipe, and 4.3 gapps.
This actually was working for about 4 days, but now it won't connect to the mobile network even when toggling on and off airplane mode (A temp fix for the ROM). I went ahead and looked for solutions, namely to just get back to stock to see if the problem is bigger than just custom ROM. I relocked my bootloader, following http://www.youtube.com/watch?v=0WWNZpaQBh8&list=PLE395F615E026133D&index=11 Thus running into my current issue of Error 140 when trying to flash the RUU.
I'm asking anyone that could help, to offer suggestions on getting my phone back to stock. I would also like a couple suggestions for more stable ROM's (again, i knew what i getting into; ie disclaimers) that offer cool customization!
did you put the stock recovery back on before you locked the bootloader? Also are you super cid?
olorolo said:
did you put the stock recovery back on before you locked the bootloader? Also are you super cid?
Click to expand...
Click to collapse
No i don't believe so, Well now its not even going into twrp recovery. It displays tampered relocked security warning, s-on, hboot 1.44.0000 and This is the only screen i have for fastboot and the bootloader
I've seen this issue before let me take a quick look I think your ok
Sent from my HTCONE using Tapatalk 4
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
You caught me in the middle of flashing the s-off firmware myself
Sent from my HTCONE using Tapatalk 4
Good to hear! Thank you for your time sir
get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
---------- Post added at 07:28 PM ---------- Previous post was at 07:18 PM ----------
once you have twrp back flash the s-off firmware http://forum.xda-developers.com/showthread.php?t=2467607 then the 4.3 rom of your choice
olorolo said:
get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
Click to expand...
Click to collapse
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.
Pug4567 said:
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.
Click to expand...
Click to collapse
twrp has to be renamed to recovery.zip try fastboot flash then type flash recovery then the name of the zip which is recovery.zip then fastboot reboot
I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582
Pug4567 said:
I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
try hassoons all in one toolbox
I got twrp back by unlocking my phone again. Should i proceed with the 3.04.651.2 firmwre? beanstalk is now hanging on splash screen.
The phone isn't being recognized on my computer it seems, it shows as m7wls under device manager, when in twrp 2.6.3. When in bootloader it shows as One device, but neither is accessible.
Also tried flashing the s-off firmware, but got 'error cannot load firmware.zip'
Any more help would be appreciated, almost thinking of taking it back to sprint, i have a protection plan. But i would like to avoid that, im currently going to buy an otg-usb cable as well.
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error. I cannot even go into recovery I am stuck anyone please help!.
I am getting Failed to erase partition error when i try to flash anything!.
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error. I cannot even go into recovery I am stuck anyone please help!.
I am getting Failed to erase partition error when i try to flash anything!.
Click to expand...
Click to collapse
If you are in bootloader mode you should be able to get into recovery. Just hit volume down to scroll to recovery and then volume up to select recovery.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked.
Click to expand...
Click to collapse
Just remember - you cannot downgrade the bootloader or the partition table!!
JulesJam said:
If you are in bootloader mode you should be able to get into recovery. Just hit volume down to scroll to recovery and then volume up to select recovery.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Just remember - you cannot downgrade the bootloader or the partition table!!
Click to expand...
Click to collapse
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
vignesh245 said:
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
Click to expand...
Click to collapse
What should I do now!! to get my phone back working!
vignesh245 said:
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
Click to expand...
Click to collapse
well the last guy who got that error had to format his data partition but he had an unlocked bootloader with TWRP and could get into TWRP.
What happens when you connect your phone in bootloader mode to your PC, open a command shell and type:
fastboot devices
Does it return your device's serial number?
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
vignesh245 said:
What should I do now!! to get my phone back working!
Click to expand...
Click to collapse
You should not be trying to flash a lower version of the partition table!!!!
You may have to do a factory reset.
---------- Post added at 07:18 PM ---------- Previous post was at 07:16 PM ----------
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error.
Click to expand...
Click to collapse
gpt.bin is the partition table. If you were trying to flash a lower version partition table than your bootloader version, you cannot do that!!!
What is your bootloader version?
JulesJam said:
well the last guy who got that error had to format his data partition but he had an unlocked bootloader with TWRP and could get into TWRP.
What happens when you connect your phone in bootloader mode to your PC, open a command shell and type:
fastboot devices
Does it return your device's serial number?
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
You should not be trying to flash a lower version of the partition table!!!!
You may have to do a factory reset.
Click to expand...
Click to collapse
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
vignesh245 said:
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
Click to expand...
Click to collapse
Is Motorola Device Manager installed on your computer? If not, install it:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Then connect your phone in fastboot mode to your computer and run MDM and see if MDM can repair your phone.
Also - are you using version 2 of mfastboot to flash?
vignesh245 said:
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
Click to expand...
Click to collapse
its 60.11
vignesh245 said:
its 60.11
Click to expand...
Click to collapse
I am using normal fastboot ! and I have MDM install will try to repair using MDM !!
vignesh245 said:
its 60.11
Click to expand...
Click to collapse
That is the lollipop 5.0 bootloader. What version of stock were you trying to flash? Kit Kat 4.4.4? If so, that is what happened here - you tried to downgrade the partition table. You cannot downgrade the partition table once you upgrade the bootloader.
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
vignesh245 said:
I am using normal fastboot ! and I have MDM install will try to repair using MDM !!
Click to expand...
Click to collapse
OK let me know how it goes.
JulesJam said:
That is the lollipop 5.0 bootloader. What version of stock were you trying to flash? Kit Kat 4.4.4? If so, that is what happened here - you tried to downgrade the partition table. You cannot downgrade the partition table once you upgrade the bootloader.
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
OK let me know how it goes.
Click to expand...
Click to collapse
Thanks for the clarity in reply!!
Where can i get the stock rom and Files for lolipop 5.0 ?? So I can get back to my stock recovery!
vignesh245 said:
Thanks for the clarity in reply!!
Where can i get the stock rom and Files for lolipop 5.0 ?? So I can get back to my stock recovery!
Click to expand...
Click to collapse
Did MDM not fix your phone? Are you on the XT1095?
http://www.graffixnyc.com/motox.php#
Also, I don't know what build you are, there looks to be more than 1 build for 5.0. Check out the support thread that the link above links too.
JulesJam said:
Did MDM not fix your phone? Are you on the XT1095?
http://www.graffixnyc.com/motox.php#
Also, I don't know what build you are, there looks to be more than 1 build for 5.0. Check out the support thread that the link above links too.
Click to expand...
Click to collapse
MDM did not fix my phone yes I am on Xt1095.
Thanks will try it and let you know
vignesh245 said:
MDM did not fix my phone yes I am on Xt1095.
Click to expand...
Click to collapse
OK, it is probably the custom recovery.
JulesJam said:
OK, it is probably the custom recovery.
Click to expand...
Click to collapse
I am getting Preflash validation failed and I found I have 22.21.11 version installed using MDM. and it says in pink color error in phone as failed to downgrade primary_apt.
Can you help me with this now??
vignesh245 said:
I am getting Preflash validation failed and I found I have 22.21.11 version installed using MDM. and it says in pink color error in phone as failed to downgrade primary_apt.
Can you help me with this now??
Click to expand...
Click to collapse
I would not mess around with the partition table. See if you can do
fastboot format data
fastboot format cache
To wipe your data and cache partitions.
JulesJam said:
I would not mess around with the partition table. See if you can do
fastboot format data
fastboot format cache
To wipe your data and cache partitions.
Click to expand...
Click to collapse
I cannot do that it says the error as in the attached screenshot!
When I select recovery using volume up it says ||boot up failed||
Can Motorola help my situation Mine is a pure edition?
||version downgraded for primary_gpt||
vignesh245 said:
Can Motorola help my situation Mine is a pure edition?|
Click to expand...
Click to collapse
Yes. It is still under warranty. I would get a warranty replacement. If you can't flash anything in BL mode and can't get into recovery and MDM can't repair your phone, idk what else to do.
Motorola should let everyone who unlocks their bootloader know you can't downgrade the bootloader or partition table. They should release the factory images of every version of Android for a device and let people know they have to stick to the version for their bootloader
Quite frankly, this is Motorola's fault for not doing that.
JulesJam said:
Yes. It is still under warranty. I would get a warranty replacement. If you can't flash anything in BL mode and can't get into recovery and MDM can't repair your phone, idk what else to do.
Motorola should let everyone who unlocks their bootloader know you can't downgrade the bootloader or partition table. They should release the factory images of every version of Android for a device and let people know they have to stick to the version for their bootloader
Quite frankly, this is Motorola's fault for not doing that.
Click to expand...
Click to collapse
Thanks a lot will contact motorola get my device replaced !.
vignesh245 said:
I cannot do that it says the error as in the attached screenshot!
When I select recovery using volume up it says ||boot up failed||
Can Motorola help my situation Mine is a pure edition?
||version downgraded for primary_gpt||
Click to expand...
Click to collapse
try using the "erase" command instead of format, I've found on my PC format works, but on Mac I need to use erase.
Although having an unlocked bootloader is useful in many ways like flashing firmware (factory images), installing TWRP and getting root, but it can also lead to blocked services on your device due to security reasons and hence you you might want to relock bootloader to avail those services.
How to Relock Moto G5s Plus Bootloader
Things you need
Minimal ADB Size: 628.5KB
Moto G5s Plus Stock Rom Size: 1.7GB
Steps
Download Moto G5s Plus Stock Firmware from below (in download section).
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
Code:
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
Then it will restart your Device. And You Will Get Locked Bootloader.
After locking bootloader, flash full Rom to get OTA. Follow this guide to flash stock firmware - Flash official Firmware Moto G5s Plus
Extra Guides:
[ROOT][TWRP][BOOTLOADER UNLOCK] Moto G5s Plus [sanders]
Remove Unlocked Bootloader Message Moto G5S Plus, G5S
Flash official firmware Moto G5s Plus [sanders]
Appreciate my work?
It is a very hard task to work over mobile data. Please consider making a donation If this guide helped you.
Bank Transfer: Name- Shubham Mishra, A/C no. 8756149523, IFSC code. AIRP0000001
Paypal https://paypal.me/shubhmishra
You are doing a great job bro......:good::fingers-crossed:
shu006 said:
Although having an unlocked bootloader is useful in many ways like flashing firmware (factory images), installing TWRP and getting root, but it can also lead to blocked services on your device due to security reasons and hence you you might want to relock bootloader to avail those services.
How to Relock Moto G5s Plus Bootloader
Things you need
Minimal ADB Size: 628.5KB
Moto G5s Plus Stock Rom Size: 1.7GB
Steps
Download Moto G5s Plus Stock Firmware from below (in download section).
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
Code:
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
Then it will restart your Device. And You Will Get Locked Bootloader.
After locking bootloader, flash full Rom to get OTA. Follow this guide to flash stock firmware - Flash official Firmware Moto G5s Plus
Extra Guides:
[ROOT][TWRP][BOOTLOADER UNLOCK] Moto G5s Plus [sanders]
Remove Unlocked Bootloader Message Moto G5S Plus, G5S
Flash official firmware Moto G5s Plus [sanders]
Appreciate my work?
It is a very hard task to work over mobile data. Please consider making a donation If this guide helped you.
Bank Transfer: Name- Shubham Mishra, A/C no. 8756149523, IFSC code. AIRP0000001
Paypal https://paypal.me/shubhmishra
Click to expand...
Click to collapse
didn't work
saying to allow oem unlocking but it is disabled by saying already unlocked
Its also not work here. Need a signed firmware and this is not signed from Motorola.
Gesendet von meinem Moto G (5S) Plus mit Tapatalk
flashing boot.img error
Image signed with key bad key
Working ????
is the method working ????
Please wait 2 days. I am busy due to sister's engagement. I'll fix all issues asap.
Not Worked
Hey man it didnt work !!!it said wrong key/bad key and was stuck on bootlogo had to flash stock rom again
Yes this just creates a bootloop unfortunately
We need a signed rom from Motorola.
I was able to block Bootloader :fingers-crossed:
Laercio_lalau said:
I was able to block Bootloader :fingers-crossed:
Click to expand...
Click to collapse
How did you get past the unsigned error?
katienugget said:
How did you get past the unsigned error?
Click to expand...
Click to collapse
I'll post it soon as I did.
any update with this. I would love to relock my device considering everything else i have tried doesnt work well.
You put 4 steps on sparsechunk, but the rom has 5 sparechunk steps.
is correct to flash till step four only?
Anyway I got this message:
Shu006>mfastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.016s]
finished. total time: 0.016s
jefpcbr said:
You put 4 steps on sparsechunk, but the rom has 5 sparechunk steps.
is correct to flash till step four only?
Anyway I got this message:
Shu006>mfastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
Yup I got that I want to relock my bootloader but stuck at this.
????...help me out anyone please
---------- Post added at 07:10 PM ---------- Previous post was at 07:09 PM ----------
Laercio_lalau said:
I'll post it soon as I did.
Click to expand...
Click to collapse
please post it soon ..many days has passed but you still didn't Posted,???
maaze790 said:
Yup I got that I want to relock my bootloader but stuck at this.
????...help me out anyone please
---------- Post added at 07:10 PM ---------- Previous post was at 07:09 PM ----------
please post it soon ..many days has passed but you still didn't Posted,???
Click to expand...
Click to collapse
Already forgotten ... take this file. bat and place next to Firmware extracted from 2 click on the .bat file and wait for the procedure to finish, if it fails to start the system, reinstall the Firmware again.
Sorry for bad English.
Link:https://mega.nz/#!hgFHTQIb!KWggcvjA0mk8e-M0dPLX0psiiwE4ikcLS4at6mzsZGw
---------- Post added at 07:34 PM ---------- Previous post was at 07:30 PM ----------
Laercio_lalau said:
Already forgotten ... take this file. bat and place next to Firmware extracted from 2 click on the .bat file and wait for the procedure to finish, if it fails to start the system, reinstall the Firmware again.
Sorry for bad English.
Link:https://mega.nz/#!hgFHTQIb!KWggcvjA0mk8e-M0dPLX0psiiwE4ikcLS4at6mzsZGw
Click to expand...
Click to collapse
Bootloader is Blocked, but Software appears modified, this I could not solve ,,, if someone has the solution, it would be good
Lol this bat is not for g5s plus. G5s have 5 sparsechunk and not 4.
Laercio_lalau said:
Already forgotten ... take this file. bat and place next to Firmware extracted from 2 click on the .bat file and wait for the procedure to finish, if it fails to start the system, reinstall the Firmware again.
Sorry for bad English.
Link:https://mega.nz/#!hgFHTQIb!KWggcvjA0mk8e-M0dPLX0psiiwE4ikcLS4at6mzsZGw
---------- Post added at 07:34 PM ---------- Previous post was at 07:30 PM ----------
Bootloader is Blocked, but Software appears modified, this I could not solve ,,, if someone has the solution, it would be good
Click to expand...
Click to collapse
How you relocked bootloader will you please tell me
---------- Post added at 07:58 PM ---------- Previous post was at 07:49 PM ----------
Laercio_lalau said:
Already forgotten ... take this file. bat and place next to Firmware extracted from 2 click on the .bat file and wait for the procedure to finish, if it fails to start the system, reinstall the Firmware again.
Sorry for bad English.
Link:https://mega.nz/#!hgFHTQIb!KWggcvjA0mk8e-M0dPLX0psiiwE4ikcLS4at6mzsZGw
---------- Post added at 07:34 PM ---------- Previous post was at 07:30 PM ----------
Bootloader is Blocked, but Software appears modified, this I could not solve ,,, if someone has the solution, it would be good
Click to expand...
Click to collapse
Are you sure that helped you to relock your bootloader
maaze790 said:
How you relocked bootloader will you please tell me
---------- Post added at 07:58 PM ---------- Previous post was at 07:49 PM ----------
Are you sure that helped you to relock your bootloader
Click to expand...
Click to collapse
Yes, you can edit the .bat file and put line 5, I did not do it because I'm using root ...
Hello friends!
After i tried to find a way to bypass LeEco login on the install of stock based ROM , i have bricked my phone (not really bricked, but i will tell you). On the first boot i cant complete the setup, because X527 dont detect my sim cards and shows no wifi networks (So i cant go to developer options and can not use a dial code).
After i have read a lot, im sure it was a problem with the efs or nvram (The last working boot shows no serial and no bootloader). But now im on Stock ROM and Stock Recovery and need an option to repair efs/nvram over fastboot or stock recovery, without changing anything in the phone itself.
Hope you guys can help me...
i recommend you to install twrp and flash official stock rom it has stock recovery too so it will came back to original state. we have the original stock rom here so dont afraid to install twrp.
anjel05 said:
i recommend you to install twrp and flash official stock rom it has stock recovery too so it will came back to original state. we have the original stock rom here so dont afraid to install twrp.
Click to expand...
Click to collapse
I can't install TWRP because i have to go to the developer options, but my phone can not start....
quasimodo88 said:
I can't install TWRP because i have to go to the developer options, but my phone can not start....
Click to expand...
Click to collapse
What you need in developers option? Oem unlocking and usb debugging? I thnk in our device theyre already on default
anjel05 said:
What you need in developers option? Oem unlocking and usb debugging? I thnk in our device theyre already on default
Click to expand...
Click to collapse
Yes. If i want to install twrp in fastboot mode i get this error:
PS C:\adb> fastboot flash recovery twrp-3.1.1-1-s2.img
target reported max download size of 536870912 bytes
sending 'recovery' (17244 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.578s
quasimodo88 said:
Yes. If i want to install twrp in fastboot mode i get this error:
PS C:\adb> fastboot flash recovery twrp-3.1.1-1-s2.img
target reported max download size of 536870912 bytes
sending 'recovery' (17244 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.578s
Click to expand...
Click to collapse
You have to do
U need to unlock first dude
DarknessKiller said:
You have to do
U need to unlock first dude
Click to expand...
Click to collapse
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
quasimodo88 said:
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
Did you install the drivers you need?
anjel05 said:
Did you install the drivers you need?
Click to expand...
Click to collapse
Yes i did. My phone is shown under fastboot devices.
quasimodo88 said:
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
I think you are ****ed. Why oh why didn't you enable oem unlocking b4 flashing roms?
You can try
Fastboot erase modemst1
Fastboot erase modemst2
But it probably won't work cus your bootloader is locked
You can also try
Fastboot boot <insert name of your twrp img here>
But again doubt it'll work
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
Try googling for an alternative way to unlock your bootloader
---------- Post added at 08:40 PM ---------- Previous post was at 08:31 PM ----------
Also if you can find a way to transfer files to your phone, try downloading eui 19s rom, edit the update script as needed(especially if you are downgrading), then send it to your phone /sdcard as update.zip and try to flash it through stock recovery.
Dudeonyx said:
I think you are ****ed. Why oh why didn't you enable oem unlocking b4 flashing roms?
You can try
Fastboot erase modemst1
Fastboot erase modemst2
But it probably won't work cus your bootloader is locked
You can also try
Fastboot boot <insert name of your twrp img here>
But again doubt it'll work
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
Try googling for an alternative way to unlock your bootloader
---------- Post added at 08:40 PM ---------- Previous post was at 08:31 PM ----------
Also if you can find a way to transfer files to your phone, try downloading eui 19s rom, edit the update script as needed(especially if you are downgrading), then send it to your phone /sdcard as update.zip and try to flash it through stock recovery.
Click to expand...
Click to collapse
Fastboot erase... and fastboot boot... i have already tried.
Fastboot sideload... i have tried too, but im not sure if i do it right. I think my last chance is to try it over an otg cable, right?
quasimodo88 said:
Fastboot erase... and fastboot boot... i have already tried.
Fastboot sideload... i have tried too, but im not sure if i do it right. I think my last chance is to try it over an otg cable, right?
Click to expand...
Click to collapse
Any luck on googling a way to enable oem unlocking without access to developer options?
Or you can treat your phone as if it was bricked. Try downloading the sparse or Qfil file (not sure which is used for unbricking) for your model. And flashing through flashone or Qfil. Google or search xda for steps on how to unbrick this particular phone or Qualcomm phones in general. I believe it involves a step where you hold vol+, vol- & power key.
Anyway goodluck.
Dudeonyx said:
Any luck on googling a way to enable oem unlocking without access to developer options?
Or you can treat your phone as if it was bricked. Try downloading the sparse or Qfil file (not sure which is used for unbricking) for your model. And flashing through flashone or Qfil. Google or search xda for steps on how to unbrick this particular phone or Qualcomm phones in general. I believe it involves a step where you hold vol+, vol- & power key.
Anyway goodluck.
Click to expand...
Click to collapse
I dont find a way to unlock the bootloader. Flashing the qfil i have already tried, but it doesnt repair the issue. I think efs or nvram is broken.
quasimodo88 said:
I dont find a way to unlock the bootloader. Flashing the qfil i have already tried, but it doesnt repair the issue. I think efs or nvram is broken.
Click to expand...
Click to collapse
What version did you flash with Qfil? 19s usually doesn't ask for leeco login so try that. If you can bypass the leeco login I can walk you through the steps to repair your efs, I even have qcn files for x526 and x522 you can edit to fix it.
Don't know if these three options are possible, because I'm not sure what the qfil files contain but
1. with your current qfil if you can find a way to delete the letvaccount apk from the system image and reflash, that should bypass the login issues. Though dm verify might prevent the phone from booting past the splash screen, so you'll need to replace the kernel(boot) img with any custom one like illusion or overload
2. replace the system, data and kernel(boot) image with ones from miui 9 rom. This will flash miui instead and voila, no login issue
3. Replace Qfil recovery image with renamed twrp
Dudeonyx said:
What version did you flash with Qfil? 19s usually doesn't ask for leeco login so try that. If you can bypass the leeco login I can walk you through the steps to repair your efs, I even have qcn files for x526 and x522 you can edit to fix it.
Don't know if these three options are possible, because I'm not sure what the qfil files contain but
1. with your current qfil if you can find a way to delete the letvaccount apk from the system image and reflash, that should bypass the login issues. Though dm verify might prevent the phone from booting past the splash screen, so you'll need to replace the kernel(boot) img with any custom one like illusion or overload
2. replace the system, data and kernel(boot) image with ones from miui 9 rom. This will flash miui instead and voila, no login issue
3. Replace Qfil recovery image with renamed twrp
Click to expand...
Click to collapse
Thank's dude, that sounds good! I have to bypass the leeco setup, what i have to do? Can you give me an instruction, please? You can find the file on this site:
http://www.gsmhelpful.com/2017/08/how-to-flash-letv-le-2-x526-with-qfil-flash-tool.html
quasimodo88 said:
Thank's dude, that sounds good! I have to bypass the leeco setup, what i have to do? Can you give me an instruction, please? You can find the file on this site:
http://www.gsmhelpful.com/2017/08/how-to-flash-letv-le-2-x526-with-qfil-flash-tool.html
Click to expand...
Click to collapse
Have you flashed this? If so did it remove the leeco login or at least make it skipable?
Send a pic of the login screen
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
Also unzip the sparse file and send me pics of its contents. Because I can't download the file right now
Dudeonyx said:
Have you flashed this? If so did it remove the leeco login or at least make it skipable?
Send a pic of the login screen
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
Also unzip the sparse file and send me pics of its contents. Because I can't download the file right now
Click to expand...
Click to collapse
Yes, i have install it 2 times, but same issue. Can you give me an email address for the pictures, please?
quasimodo88 said:
Yes, i have install it 2 times, but same issue. Can you give me an email address for the pictures, please?
Click to expand...
Click to collapse
I've seen the pics, the system file is in parts so replacing it is very very difficult as I cant be sure how it was split.
But good news, I noticed a file named recovery
So move that file somewhere else.
Then rename your twrp file to recovery and copy it to that folder.
Then try flashing it, if successful this should give you custom recovery and I can work with that
Dudeonyx said:
I've seen the pics, the system file is in parts so replacing it is very very difficult as I cant be sure how it was split.
But good news, I noticed a file named recovery
So move that file somewhere else.
Then rename your twrp file to recovery and copy it to that folder.
Then try flashing it, if successful this should give you custom recovery and I can work with that
Click to expand...
Click to collapse
Ok, i will try it now. Don't run away :fingers-crossed:
quasimodo88 said:
Ok, i will try it now. Don't run away :fingers-crossed:
Click to expand...
Click to collapse
Good luck, also I noticed that your issue isn't leeco account login but rather Google's factory reset protection. So if this fails you can search for ways to bypass google factory reset protection.