Hey All,
I was looking for a "Return to stock" guide but couldnt find any. Does anyone here know where I can find stock images perhaps?
Need to sent it back to the retailer and gotta have it stock.
Hope someone can help me.
Thanks!
nerotix said:
Hey All,
I was looking for a "Return to stock" guide but couldnt find any. Does anyone here know where I can find stock images perhaps?
Need to sent it back to the retailer and gotta have it stock.
Hope someone can help me.
Thanks!
Click to expand...
Click to collapse
What did you do to it that you can't manually undo?
_MetalHead_ said:
What did you do to it that you can't manually undo?
Click to expand...
Click to collapse
Nothing it all, I just unlocked bootloader like everyone else and rooted it. But now when I try to do it manualy I get 2 errors, I do this:
fastboot oem lock begin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
On the boot.img and recovery.img flash I get this error for both:
D:\android-sdk\sdk\platform-tools>mfastboot flash recovery recovery.img
sending 'recovery' (10280 KB)...
OKAY [ 0.370s]
writing 'recovery'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.596s
I also tried it with mfastboot, both didnt work.. and when I do fastboot oem lock I get :
D:\android-sdk\sdk\platform-tools>mfastboot oem lock
...
sst lock failure!
OKAY [ 0.026s]
finished. total time: 0.026s
If you didn't flash a custom recovery and kernel, there is no reason to try and flash recovery or boot. Just hit the unroot option in SuperSU, and relock the bootloader and you should be good to go.
_MetalHead_ said:
If you didn't flash a custom recovery and kernel, there is no reason to try and flash recovery or boot. Just hit the unroot option in SuperSU, and relock the bootloader and you should be good to go.
Click to expand...
Click to collapse
That's the thing.. if I type fastboot oem lock it says I must begin with fastboot oem lock begin and then start flashing signed files or something.
So I tried that but no luck.
Thx for your reply.
nerotix said:
That's the thing.. if I type fastboot oem lock it says I must begin with fastboot oem lock begin and then start flashing signed files or something.
So I tried that but no luck.
Thx for your reply.
Click to expand...
Click to collapse
That's weird, I've never heard of that before . It must be something unique to the X. Sounds like we need the stock boot and recovery images to relock the bootloader. Are the signed images even available to us yet? I have no clue...
nerotix said:
That's the thing.. if I type fastboot oem lock it says I must begin with fastboot oem lock begin and then start flashing signed files or something.
So I tried that but no luck.
Thx for your reply.
Click to expand...
Click to collapse
Sadly motorola hasn't put up any factory images on their website as far as i know. In their support forums they said they'll be coming up soon a month ago though. There's a tool posted on the Moto X dev forums which seemed to have a system.img and other images embedded, just read that up and see if it helps.
Alternatively, there's no real need for you to relock, most likely no one's gonna notice it. And if yours is not a pure edition they would know if they checked your imei if you have unlocked or not irrespective of you locking the bootloader or not. So the best and quick solution for you is to unroot, flash the logo.bin file posted on the Moto X dev forums so that you dont have any message showing up that you have unlocked the bootloader on starting up your device.
Related
Hello,
Forgive me for my bad English, I'm French, I unlock the bootloader via the Motorola site, it has to work perfectly, but I will wish to reset the lock the bootloader, how do I proceed? On the Motorola site there is not any procedure.
Pierre
If you are doing for warranty purposes it is still voided and they will charge for repair.
But if for some silly reason you need to lock it...
Code:
fastboot oem lock
Sent from my MB886 using Tapatalk 2
Using your code I get the following message appears:
FAIL: run fastboot oem lock Please begin first!
Click to expand...
Click to collapse
What to do?
Code:
C:\sdk\tools>cd..
C:\sdk>cd platform-tools
C:\sdk\platform-tools>fastboot oem lock
< waiting for device >
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.550s]
finished. total time: 0.550s
pierre144 said:
Using your code I get the following message appears:
What to do?
Code:
C:\sdk\tools>cd..
C:\sdk>cd platform-tools
C:\sdk\platform-tools>fastboot oem lock
< waiting for device >
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.550s]
finished. total time: 0.550s
Click to expand...
Click to collapse
That's how it was supposed to work... contact Motorola I guess. Why bother locking anyway..?
mattlgroff said:
That's how it was supposed to work... contact Motorola I guess. Why bother locking anyway..?
Click to expand...
Click to collapse
I will contact Motorola, I want to put the bootloader as before for security reasons.
pierre144 said:
I will contact Motorola, I want to put the bootloader as before for security reasons.
Click to expand...
Click to collapse
Won't change a thing in terms of security, except possibly for DRM content. Read what bootloader tells you. I believe the sequence is "fastboot oem lock begin", then firmware flash, then "fastboot oem lock".
Skrilax_CZ said:
Won't change a thing in terms of security, except possibly for DRM content. Read what bootloader tells you. I believe the sequence is "fastboot oem lock begin", then firmware flash, then "fastboot oem lock".
Click to expand...
Click to collapse
I wish to sell on my phone so i want to re-lock it to remove the bootloader warning. Unfortunately the above steps don't work for me either and I cant see any mention of how to lock the phone again on motorolas site?
f1ux said:
I wish to sell on my phone so i want to re-lock it to remove the bootloader warning. Unfortunately the above steps don't work for me either and I cant see any mention of how to lock the phone again on motorolas site?
Click to expand...
Click to collapse
Then can't you use fastboot to put the original boot logo back on instead of relock?
Sent from my rooted XT890 with unlocked bootloader using XDA premium
Past androids: HTC Hero - Sony X10 mini (rooted and running mini cyanogenmod) - Orange Stockholm (rooted to remove orange's skin and bloatware) :3
max choco found a way to relock! here you find the guide:
http://argendroid.com/topic-GUIA-Re...upera-tu-garantía-volver-al-estado-de-fabrica
mercurio. said:
max choco found a way to relock! here you find the guide:
http://argendroid.com/topic-GUIA-Re...upera-tu-garantía-volver-al-estado-de-fabrica
Click to expand...
Click to collapse
I tried following the guide.
I'm on the Retail EU firmware 4.1.2
When I try to flash the system, it shows some error about the file size (the 100MB limit?) and when I try to lock the bootloader without flashing system - but everything else - it tells me that something in my system is wrong...
What (if any) is the fastboot command to MultiFlash the system_signed manually?
Sayuuk said:
I tried following the guide.
I'm on the Retail EU firmware 4.1.2
When I try to flash the system, it shows some error about the file size (the 100MB limit?) and when I try to lock the bootloader without flashing system - but everything else - it tells me that something in my system is wrong...
What (if any) is the fastboot command to MultiFlash the system_signed manually?
Click to expand...
Click to collapse
I have that problem too... 100MB limit comes on screen.
I haven't found JB Retail British, only ICS Retail British. I want to be careful with flashing ... if you flash JB to ICS you will brick..
Any news about that?
mercurio. said:
max choco found a way to relock! here you find the guide:
http://argendroid.com/topic-GUIA-Re...upera-tu-garantía-volver-al-estado-de-fabrica
Click to expand...
Click to collapse
Does not work in "Razr HD" because we do not have the files "bos_signed, gpt_signed, motoboot and radio_signed" in firmware. If anyone can help, I really need. Grateful.
its not possible man
felipe_net said:
its not possible man
Click to expand...
Click to collapse
You tried it?
Enviado desde mi Moto HD
LOCK
fastboot oem lock begin
fastboot flash boot boot.img
mfastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot erase userdata
fastboot erase cache
fastboot oem lock
use this mfastboot View attachment mfastboot.zip for command - mfastboot flash system system.img
system.img must be solid file ! if not and you have multiple files, try renaming the last of them in system.img
Good Luck
borik88 said:
LOCK
fastboot oem lock begin
fastboot flash boot boot.img
mfastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot erase userdata
fastboot erase cache
fastboot oem lock
use this mfastboot View attachment 2546578 for command - mfastboot flash system system.img
system.img must be solid file ! if not and you have multiple files, try renaming the last of them in system.img
Good Luck
Click to expand...
Click to collapse
And all these files? where can i download that? (boot.img, system.img, recovery.img, logo.bin)
Thanks!
Finally, Re-Lock Failed
I am not getting download link of fastboot oem lock for razr i
I have decided to post a new thread as all the other threads on this are not for my phone.
I try to do what bootloader says which is 'fastboot oem lock begin' but I get stuck.
It says afterwards:
Code:
...
<bootloader> Ready to flash signed images
OKAY [ 0.476s ]
finished. total time: 0.479s
But what are the signed images?
So I skip flashing the 'signed images' and go ahead and type: 'fastboot oem lock' and it gives me this error:
Code:
...
<bootloader> Re-Lock Failure. See display.
OKAY [ 0.644s ]
finished. total time: 0.667s
So, I look at the display and it says:
Code:
Fastboot Reason: Reboot to bootloader
fastboot: max download size: 100MB
USB connected
Fastboot command failed
OEM lock
OEM lock begin
Getvar partition-type:recovery
Fastboot command failed
Getvar max-download-size
OEM lock
E:No valid PIV block in SP for cdrom
E:piv validation failed (cdrom)
E:Falied to validate piv objects
Re-lock failure
Somebody please help me!! I have been trying to search for my phone's stock rom for days without success! PLEASE HELPPP!!!!
If you only want to go back to stock-firmware, you don't have to relock your bootloader. You only have to flash the stockimage with RSD-Lite.
But if you really want to relock:
http://forum.xda-developers.com/showpost.php?p=44430691&postcount=4
Firmwares fro our Razr I:
http://sbf.droid-developers.org/phone.php?device=13
ICuaI said:
If you only want to go back to stock-firmware, you don't have to relock your bootloader. You only have to flash the stockimage with RSD-Lite.
But if you really want to relock:
http://forum.xda-developers.com/showpost.php?p=44430691&postcount=4
Firmwares fro our Razr I:
http://sbf.droid-developers.org/phone.php?device=13
Click to expand...
Click to collapse
Thank you. It did work but I want to know, how do you tell when it is locked?
Also, I have already tried to go back to stock firmware using RSD-Lite but I don't know where to find the needed file...If you can help with that, I would be very grateful.
Thank you,
GoldenPaul27
Do you have to change the downloaded file extension so it doesn't have the .zip on the end of it?
GoldenPaul27 said:
Do you have to change the downloaded file extension so it doesn't have the .zip on the end of it?
Click to expand...
Click to collapse
No, the is zipped. You have to unzip this file first.
HTML:
ICuaI said:
No, the is zipped. You have to unzip this file first.
Click to expand...
Click to collapse
OK. I shall try this. Thank you for your help so far.
nice
I wanted this 2, tks!!
Just another question:
How do you tell when the bootloader is relocked??
Unfortunately I loaded the leaked Lollipop build to my PE and it was working great, but I wanted to get on the soak test build. I downloaded the stock KK 4.4.4 system image from Motorola in order to restore before updated to soak test. All but one of the files flashes fine, the exception being motoboot.img. I get Preflash validation failed error for that file.
The phone boots and runs but the missing file means the update won't install. Does anyone have any thoughts on how to restore this file?
TMO_21.21.42.victara_tmo.tmo.en.US>mfastboot flash boot motoboot.img
target max-sparse-size: 256MB
sending 'boot' (2022 KB)...
OKAY [ 0.089s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.109s
samabuelsamid said:
Unfortunately I loaded the leaked Lollipop build to my PE and it was working great, but I wanted to get on the soak test build. I downloaded the stock KK 4.4.4 system image from Motorola in order to restore before updated to soak test. All but one of the files flashes fine, the exception being motoboot.img. I get Preflash validation failed error for that file.
The phone boots and runs but the missing file means the update won't install. Does anyone have any thoughts on how to restore this file?
TMO_21.21.42.victara_tmo.tmo.en.US>mfastboot flash boot motoboot.img
target max-sparse-size: 256MB
sending 'boot' (2022 KB)...
OKAY [ 0.089s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.109s
Click to expand...
Click to collapse
try:
Code:
mfastboot flash motoboot motoboot.img
holtenc said:
try:
Code:
mfastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Sorry, copy/paste error there.
I actually tried the motoboot motoboot.img too and get the same error.
well I'm not sure then man. I guess all I can suggest is follow THESE instructions to a T.
also if you have flashed any of the radios floating around these forums insert "fastboot flash modem radio.img" in there somewhere.
And of course make sure your bootloader is unlocked.
holtenc said:
well I'm not sure then man. I guess all I can suggest is follow THESE instructions to a T.
also if you have flashed any of the radios floating around these forums insert "fastboot flash modem radio.img" in there somewhere.
And of course make sure your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks, those are precisely the instructions I used. I haven't done anything with the radios. I flashed the leaked lollipop rom and then used the official image files to try to go back. The bootloader was initially not unlocked, I unlocked it only in an attempt to get the motoboot file to flash. Now I can't relock it because this part of the image is missing.
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
holtenc said:
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
Click to expand...
Click to collapse
Only thing I did with bootloader locked was the partition. As soon as I got to the motoboot and it failed, I figured I would need to unlock and did that. Since then, I've tried the whole process a couple of times with the same result. I will however, give it another shot.
You don't need motoboot to update. Go use the script and it will do everything for you.
tw1tch175 said:
You don't need motoboot to update. Go use the script and it will do everything for you.
Click to expand...
Click to collapse
Which script is that?
samabuelsamid said:
Which script is that?
Click to expand...
Click to collapse
My multitool in development section has stock restore included
holtenc said:
Have you tried re-doing all those instructions from the top with your bootloader unocked? instead of just trying to reflash motoboot?
I'm surprised it let your flash somethings while your bootloader was still locked.
Click to expand...
Click to collapse
bhp090808 said:
My multitool in development section has stock restore included
Click to expand...
Click to collapse
Downloading V4.1 now, thanks
bhp090808 said:
My multitool in development section has stock restore included
Click to expand...
Click to collapse
I flashed with the multitool and was able to get back where I started with the leaked PE lollipop version but something is still missing because I can't relock the bootloader.
Think I may be officially bricked ... tried to sideload the OTA this morning with no luck (looped at Google splash screen). So I flashed the 5.0.1 images and went about my day. Came home and flashed the 5.1 images and looped at the Google splash again ... continued to tinker and play. Long story short, in my idiocy I oem locked. Now I can't flash any .img files cause I am locked, can't unlock because I can't boot into Android and uncheck the stupid box in dev options and trying to sideload the ota .zip again yields: "/dev/block/platform/msm_sdcc.1/by-name/system has been removed R/W; reflash device to reenable OTA updates E:Error in sideload/package.zip (Status 7)" ...
At this point I think I am screwed!! Any suggestions would be GREATLY appreciated!
Can you not get into fastboot and try to OEM unlock that way?
Xaikar said:
Can you not get into fastboot and try to OEM unlock that way?
Click to expand...
Click to collapse
I can get into fastboot but get this when I try to unlock
C:\Android\sdk\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.000s
C:\Android\sdk\platform-tools>
And of course I cannot check that because I cannot boot into Android
So it currently says device locked?
Xaikar said:
So it currently says device locked?
Click to expand...
Click to collapse
10-4
I can get into stock recovery, but I don't know of anything to flash with the stock recovery and adb sideloading 5.1 isn't working
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
There's a thread about this over at the Nexus 9 help forum. Might want to check there.
Xaikar said:
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Click to expand...
Click to collapse
Can't flash the images while locked, thanks though
ChristianJay said:
There's a thread about this over at the Nexus 9 help forum. Might want to check there.
Click to expand...
Click to collapse
Ah, thanks! Any idea which section?
Edit: Found it!
YankInDaSouth said:
Ah, thanks! Any idea which section?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312
Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img
WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.
ajjames01 said:
Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img
Click to expand...
Click to collapse
Custom recovery isn't currently on the device ...
Dusty Rhodes said:
WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.
Click to expand...
Click to collapse
Tried that too ... but the .img's cannot be flashed while locked, keeps failing
If you have TWRP on the device can you adb push a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.
ajjames01 said:
If you have TWRP on the device can you a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.
Click to expand...
Click to collapse
I don't have TWRP, sorry that was a typo. It's stock recovery as I was trying to go fully stock 5.1 ...
@YankInDaSouth
Did you try booting twrp and not flashing it and go from there?
Fastboot boot recovery twrp.img
when Google decided to add the "OEM Lock" checkbox they should have committed to every Nexus device also having SD card capability, not only for the convenience that SD cards bring but also to be able to load the images that way in the event of a catastrophe.
But I guess forcing everyone into buying cloud storage is the new modus operandi.
Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot
efrant said:
Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot
Click to expand...
Click to collapse
Still get the message about checking the box in dev options ...
Not sleeping tonight huh bro? I know the feeling when this **** happens, it sucks. I think someone will come up with a work around, a lot of brains around here.
Sent from my Nexus 9 using XDA Free mobile app
How to unlock the OEM when I could not activate the developer options, because the device does not turn on?
It is not possible to flash a ROM because it says: flashing_locked
In short, the device only goes to Fastboot.
------------------
I manage to do the following. I did a temporary boot via Fastboot.
fastboot boot "Original ROM file or Boot.img Patched with Root"
More information I have I will be putting it here.
An application to use adb and fastboot without a computer.
Bugjaeger or Bugjaeger Premium
ps: requires otg support on the device you are going to control.
I'm out of results at the moment, I couldn't recover my Moto G7 Plus.
I've already lost almost 100% of the hopes that I can manage.
I think I will have to send it to a Motorola Official Technician or buy another device, as it is not worth me to have it fixed. because the stores are far from my city.
I was able to start the device, but I still can't activate oem unlock.
it is already a progress.
I used a modified boot.img and started the device using:
fastboot boot boot.img
the problem I have to use this command to turn on the device without...
if i get more news i will talk here.
Anrito Kun said:
if i get more news i will talk here.
Click to expand...
Click to collapse
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
------------------
I don't know how to send files here.
I have no new results, but I will try to send the boot.img that could connect the device.
wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img
I haven't been able to do anything new yet.
I think that only specialist technicians will know how to fix the device.
Anrito Kun said:
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img
Click to expand...
Click to collapse
------------------
After downloading use the command: fastboot boot file.img
This managed to start the device, but I couldn't get into Recovery ... At least I couldn't.
Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.
Anrito Kun said:
Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.
Click to expand...
Click to collapse
------------------
I think it may be possible to join TWRP with the system's Boot.img. As if it were a magched patched, only instead of magisk it is TWRP.
delete
delete
poog said:
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....tried 2 things that fail
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
(bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote failure)
finished. total time: 0.510s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s
Click to expand...
Click to collapse
------------------
You're using the Moto G7 plus, right?
the command has to be this to use the file:
fastboot boot "file name".img
poog said:
I can boot to fastboot, but I cannot flash anything. I cannot get a proper return with "fastboot devices"
I cannot get RSD LITE to recognize my device. (win 10). I have read to try win7
Device Manager (windows 10) can only show the device as "Motorola ADB Device". I have not figured out how to force it to show as Qualcom ..............if that will make a difference or not. qualcom drivers are installed.
Before I messed it up I was able to load the device as a qualcom device on the right port and blankflashed after I hardbricked with nothing on screen.
Ability to boot to fastboot but not flash anything seems it is effectively dead for now.
Click to expand...
Click to collapse
------------------
There is no point in trying Flash on the device when the device is Flashing Locked.
My phone is in the same situation after I tried to re-lock the bootloader. Please do follow up on your progress.
hey I have the same problem have you found a solution?
Unfortunately, no.