Hello,
when buying my Axon 10 G first I unlocked the Bootloader. But because of lack of roms I never installed a custom rom. In the meantime I updated to v2.5 G-version and I want to relock the Bootloader. Is there a safe way, because I think I don't have anymore fastboot.
Regards, Martin
Mart Son said:
Hello,
when buying my Axon 10 G first I unlocked the Bootloader. But because of lack of roms I never installed a custom rom. In the meantime I updated to v2.5 G-version and I want to relock the Bootloader. Is there a safe way, because I think I don't have anymore fastboot.
Regards, Martin
Click to expand...
Click to collapse
you can safely close the bootloader
if you first import your backup
then boot into the fastboot mode and then fastboot " fastboot flashing lock "
after flash these files
fastboot flash abl_a abl.elf
fastboot flash abl_b abl.elf
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
greetz
Thank you for your advice, but the backup is from v1.6 or older. I am sure that I will brick my phone this way.
Related
I feel really sorry that I have to part with this device when I've only owned it for a couple of days. But I have to do it!
OK, I'll get straight to it:
1. I was on ICS 4.0.4 Stock,un-rooted and boot loader remained locked.
2. Then I decided to Unlock the Bootloader and flash the Twrp recovery and then I flashed the EOS Jelly Bean stable for MZ604 WiFi UK version.
3. I need to get it back to stock. As in, stock ICS, un-rooted and bootloader relocked (If that's possible).
4. Now I'm not that kind of guy that will ask a question before doing loads of research on a thing. So this is what I found out but just need some confirmation from some experienced Xoom users who have done this procedure before. First of all I've read through this Official Xoom website: http://developer.motorola.com/products/software/ And then I figured that I have to download this version:
Build H.6.2-24 for Retail Europe
MD5 Sum: cae470d91a6f6e1473f981bc06f452fd
Spain, Italy, Austria, Switzerland, UK, Sweden, Norway, Denmark, Netherlands 118 MB Jun. 2, 2011 MZ604 Product Specs Download
Since I do live in the UK. And then after that I would have to follow these instructions given by Motorola themselves:
INSTRUCTIONS TO FLASH & RE-LOCK YOUR MOTOROLA XOOM:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
And by this I'm guessing they mean, first download the Zip and then extract all of the files to the place where the file ADB and Fastboot reside. And then put your motorola xoom in fastboot mode by connecting it to the computer via the motorola usb cable that was provided in the box. And have usb debugging enabled. Then open command prompt and type in adb reboot bootloader. Which would then reboot to fastboot mode and then you'd have to type in these commands.
Also would I have to type these commands seperately right?
So first: Typing in command prompt: fastboot flash boot boot.img
Then after that has finished I do the next and the next and the next until it comes down to the "fastboot oem lock" which I guess should be the relocking part and the other parts were flashing the stock img and removing the recovery in order to put everything back the way it was before.
So now after following all those instructions, I'm guessing that everything should be back as it was before. As in, I could easily go and hand this in the store that I bought it from and they wouldn't notice a single thing. Right? And of course the tablet would be running stock ICS 4.0.4, unrooted and bootloader locked, right?
I would really appreciate anyone reading through these instructions and maybe confirming if they are right or if they are wrong, could you please show me the right way?
Thank you very much
With regards,
Beston94
This is all you should do,.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache..
an unlock bootloader still update..i never lock back mine..
tumpy said:
This is all you should do,.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache..
an unlock bootloader still update..i never lock back mine..
Click to expand...
Click to collapse
Perhaps you misunderstood me because I don't need to update but I need to return it as it was.
Hey,
So I've been searching for a few days now in the moto g section. I can't find any guides to restore my moto g GPE US version to stock. I found somewhat of walkthrough using the moto tool but I dont' have a windows machine to run that program. Is there another way to do this? Please let me know, also if I missed a post that shows this info please reply with the link.
Thank you!
If you don't have a Windows machine, it'd be good if we knew what you do have in order to guide you properly.
Flashing back to stock on Linux is quite easy once you've got the tools set up. I would assume MacOS X is similar provided you can get a suitable fastboot or mfastboot binary. (I recommend having them in a directeory listed in your $PATH variable with proper permissions for USB so that you don't need to sudo to use them.)
If you've got no computer, but can boot in a modified recovery, it should be possible to flash the entire stock ROM with that. You wouldn't be able to relock the bootloader though, if that's something you were aiming for.
killjoydreams said:
Hey,
So I've been searching for a few days now in the moto g section. I can't find any guides to restore my moto g GPE US version to stock. I found somewhat of walkthrough using the moto tool but I dont' have a windows machine to run that program. Is there another way to do this? Please let me know, also if I missed a post that shows this info please reply with the link.
Thank you!
Click to expand...
Click to collapse
If you are on MAC or linux I suppose you have fastboot installed! If not get it installed from here
Now To restore your phone to stock download this firmware.
After Downloading! Extract the firmware. cd to the directory of extraction.
Use the script in the attachement to restore your phone.
OR
Enter these commands manually
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
You will need the path to fastboot to be added in path variable!
OMG!!!! thank you, thank you, thank you!!!!!
Worked like a charm, I was flipping out trying to figure this out b4 I had to work, your a life saver!!! Btw is there any downside to this process, like can I re-lock the boot loader and is it still possible to get OTA updates?
OTA updates work regardless of whether your bootloader is unlocked or not.
It's root and other changes to the /system partition that'd prevent such updates from working.
killjoydreams said:
Worked like a charm, I was flipping out trying to figure this out b4 I had to work, your a life saver!!! Btw is there any downside to this process, like can I re-lock the boot loader and is it still possible to get OTA updates?
Click to expand...
Click to collapse
No no downsides
You can re-lock the bootloader
And you will get OTA updates as well, even if your bootloader is unlocked!
Just have stock recovery
3 days ago I got a lollipop ota update to my fe170cg. Everything is cool except rooting. I want to root this device like a used to do at kitkat.
But I couldn't find any solution to root this device. I also tried VampireFo's tethered CWM recovery but no luck with that it is not even flashing CWM because of the tigth locked asus lollipop bootloader. I also tried to downgrade to kitkat because of the lollipop recovery But I couldn't downgrade. Now I have no more chance to root this device. And no chance to downgrade to kitkat as well. So I decided to ask professionals like you. I really need help!!. Any help would be appreciated. Thanks from now for any response.
FreeAgentNBS said:
3 days ago I got a lollipop ota update to my fe170cg. Everything is cool except rooting. I want to root this device like a used to do at kitkat.
But I couldn't find any solution to root this device. I also tried VampireFo's tethered CWM recovery but no luck with that it is not even flashing CWM because of the tigth locked asus lollipop bootloader. I also tried to downgrade to kitkat because of the lollipop recovery But I couldn't downgrade. Now I have no more chance to root this device. And no chance to downgrade to kitkat as well. So I decided to ask professionals like you. I really need help!!. Any help would be appreciated. Thanks from now for any response.
Click to expand...
Click to collapse
Hey there!
Not sure this will help you or not..for me it just doing good. Try use fastboot
fastboot erase cache
fastboot erase system
fastboot erase userdata
Then you need you flash the a stock firmware. UL-K012-WW-11.2.3.33-user
Download the appropriate firmware from Asus website. There are three .img files in the firmware zip file (fastboot.img, boot.img, splashscreen.img).
Copy all these three files to the extracted folder. Now type the following command in the command window one by one:
fastboot flash fastboot fastboot.img
fastboot flash boot boot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
then you get your droidboot back.
user Temp CWM IntelAndroid-FBRL-05-16-2015-PTR to flash UL-K012-WW-11.2.3.33-user
so that you can downgrade to kitkat
BigBadWolf90 said:
Hey there!
Not sure this will help you or not..for me it just doing good. Try use fastboot
fastboot erase cache
fastboot erase system
fastboot erase userdata
Then you need you flash the a stock firmware. UL-K012-WW-11.2.3.33-user
Download the appropriate firmware from Asus website. There are three .img files in the firmware zip file (fastboot.img, boot.img, splashscreen.img).
Copy all these three files to the extracted folder. Now type the following command in the command window one by one:
fastboot flash fastboot fastboot.img
fastboot flash boot boot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
then you get your droidboot back.
user Temp CWM IntelAndroid-FBRL-05-16-2015-PTR to flash UL-K012-WW-11.2.3.33-user
so that you can downgrade to kitkat
Click to expand...
Click to collapse
Thanks a lot It worked :good:
thanx a lot it worked
It worked at-last ....
BigBadWolf90 said:
Hey there!
Not sure this will help you or not..for me it just doing good. Try use fastboot
fastboot erase cache
fastboot erase system
fastboot erase userdata
Then you need you flash the a stock firmware. UL-K012-WW-11.2.3.33-user
Download the appropriate firmware from Asus website. There are three .img files in the firmware zip file (fastboot.img, boot.img, splashscreen.img).
Copy all these three files to the extracted folder. Now type the following command in the command window one by one:
fastboot flash fastboot fastboot.img
fastboot flash boot boot.img
fastboot flash splashscreen splashscreen.img
fastboot reboot-bootloader
then you get your droidboot back.
user Temp CWM IntelAndroid-FBRL-05-16-2015-PTR to flash UL-K012-WW-11.2.3.33-user
so that you can downgrade to kitkat
Click to expand...
Click to collapse
:good::good::good: Thank you so much dude..:highfive: :victory: Now it is working ..
I was long time at MM sources.
Yesterday, Luis Gonzales created Resurrection Remix 5.8.5 working on Nougat baseband.
https://forum.xda-developers.com/mo...mix-v5-8-3-t3637204/post74686456#post74686456
So I updated my MXS to last N: 25.200-15-3
Before flashing custom I made DD backup of all needed partitions. I didn't try it but I think they are safe.
All can be flashed with fastboot.
System, boot, recovery with twrp too(flash from image).
All without root.
Kernel(boot) is untouched - without root - extracted from supersu backup.
https://mega.nz/#F!814XxZQK!g_INQT-O8ClpNttPc-wg6w
Flashing method:
fastboot oem fb_mode_set
fastboot flash logo logo.bin (unlocked BL warning!!!)
fastboot flash boot boot.img (rename downloaded file)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Only for phones with unlocked BL and N version of BL & gpt.
Fastboot should sparse system.img itself.
Modems only(MM&N):
https://mega.nz/#F!FlxxUZxQ!M9kqWei99LXatwc4LgJORw
Mirror and instructions with comments - post #25
https://forum.xda-developers.com/showpost.php?p=74993383&postcount=25
MM recovery tool post #28
https://forum.xda-developers.com/showpost.php?p=75001459&postcount=28
Big thanks to @Prazaar
valerio32 said:
Modem is EU?
Click to expand...
Click to collapse
"Stock xt 1572, RetEu, 7.0 DDumped files."
valerio32 said:
you can do the ota updates and the recovery is original or is twrp?
---------- Post added at 03:34 PM ---------- Previous post was at 03:16 PM ----------
is normal "Invalid sparse file format at header magi"?
:crying::crying::crying::crying:
Click to expand...
Click to collapse
I don't understand. Upload screenshots somewhere.
valerio32 said:
the phone works, but how can I block the bootloader?
thank you
:crying::crying::crying::crying:
Click to expand...
Click to collapse
You can't untill will be flashable original stock for fastboot.
The same version or upper.
OTA - I don't think will be any more. But If you have last BL version shouldn't be any problems.
Btw
Did you flashed all partitions I uploaded? Only modem, fsg?
CAN NOT.
Hi,brother.could you please backup the bootloader file?
zi_mo said:
Hi,brother.could you please backup the bootloader file?
Click to expand...
Click to collapse
Only with flashfire app(rpm, sbl1, aboot, utags).
Flashfire says - restoring is most dangerous.
Thanks for replying.
My friend has a broken xs_EU with blocked BL by flashing stock_7.0BR,I thought that it would be rescued by flashing you files with gpt of the ota_patches if we got the file bl.
so, we must wait for the stock_7.0EU.
Will this work if I flash these files on my recently debricked (from downgrade) XS on MM 6.01?
Bootloader is still unlocked from the initial install of a custom ROM. But then I bricked it after downgrading from N to stock MM and installing OTA updates.
So just flash these files in fastboot and it should be on Nougat again unbricked?
I don't know.
There isn't bootloader & gpt into these files.
If your BL & gpt are Nougat you can flash it and later install ota updates @Murugan78
BL and GPT should still be N after the downgrade no? It went from MM to N with OTA when I bought it. Last month I installed Lineage ROM but decided to go stock again (and got bricked due to the N bootloader and gpt?). I get the prevalidation error when flashing BL and GPT from the official MM ROM so these must still be N if I am correct. This is my first moto device and I have done some custom things in the past with my S1, S2 and my OPO but never had these issues.
The sparsechunks are not necessary for trying to upgrade?
BL, gpt should be N. @Murugan78
And I can flash the system.img as 1 file instead of all the chunks?
Yes
fastboot flash system system.img
Flashed the files and so far so good! Got an OTA update without problems. Tomorrow I'm gonna test if my SIM works and maybe remove the unlocked bootloader message.
Thanks a LOT!
dzidexx said:
I was long time at MM sources.
Yesterday, Luis Gonzales created Resurrection Remix 5.8.5 working on Nougat baseband.
https://forum.xda-developers.com/mo...mix-v5-8-3-t3637204/post74686456#post74686456
So I updated my MXS to last N: 25.200-15-3
Before flashing custom I made DD backup of all needed partitions. I didn't try it but I think they are safe.
All can be flashed with fastboot.
System, boot, recovery with twrp too(flash from image).
All without root.
Kernel(boot) is untouched - without root - extracted from supersu backup.
https://mega.nz/#F!814XxZQK!g_INQT-O8ClpNttPc-wg6w
Flashing method:
fastboot oem fb_mode_set
fastboot flash logo logo.bin (unlocked BL warning!!!)
fastboot flash boot boot.img (rename downloaded file)
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS.bin (Flash twice, if Prevalidation Error)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Only for phones with unlocked BL and N version of BL & gpt.
Fastboot should sparse system.img itself.
Modems only(MM&N):
https://mega.nz/#F!FlxxUZxQ!M9kqWei99LXatwc4LgJORw
Click to expand...
Click to collapse
If i flash all with fastboot, i turn back my phone to the lastest N stock version.
I guess that it format internal storage too.
thi3um said:
If i flash all with fastboot, i turn back my phone to the lastest N stock version.
I guess that it format internal storage too.
Click to expand...
Click to collapse
This will format:
fastboot erase cache
fastboot erase userdata
You need it if you was on another version - 6.x or 7.1.2.
mirror online: https://dl.prazaar.de/?dir=Android/Motorola/XT1572/Dumped_Files
edit: The gpt.bin can be easily pulled from an OTA file
and the single bootloader files in: Blur_Version.24.231.13.clark_reteu.reteu.en.EU.zip:
tz.mbn, sdi.mbn, sbl1.mbn, pmic.mbn, rpm.mbn, hyp.mbn, fsg.mbn (but it "about.mbn" is missing)
I working on a Recovery Tool for Moto X Style (EU) XT1572 from 7.0 back to 6.0.1 with working OTAs
No other factory img is needed anymore. you want to be up to date? only OTAs needet for this
bootloader after this up to date!
The Recovery Tool bring you up to 6.0.1 without restriction.
https://dl.prazaar.de/?dir=Android/Motorola/XT1572/Factory/Recovery-Tool / for news prazaar.de
Just a question, I already have my xt 1572 reteu with the build version NPHS 25.200-15-3 like this dumped files, but I miss the October update, can I just flash recovery and boot.img from the dumped files in order to install the security patch? Thanks!!
This CAN be done. Please note of course that I am NOT responsible for bricked devices.
I tried it on an XT2113-2 after finding this Moto G Power thread (kudos to the ever-informative @sd_shadow for giving my nerves a boost with his post):
How to downgrade Android 11 to 10
I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to...
forum.xda-developers.com
I successfully downgraded from Android 11 to 40-95-6. I did not have the last Android 10 version 40-95-9, so I had to fall back one more version. But it worked 100% fine, no snags at all.
Instructions for downgrading:
1. *** Bootloader MUST be UNLOCKED ***. Downgrading will NOT work on a locked bootloader, it will fail rollback protection. If you try and it fails, your current firmware is ilkely trashed and you'll have to reflash it.
2. Make sure you have a copy (uncompressed) of the firmware version you want to download to.
3. Copy all unzipped firmware files to your ADB folder, and open a command window.
4. Reboot to bootloader ("adb reboot bootloader" from system, or from power off, press Power + Volume-Down until bootloader screen shows).
5. "fastboot devices" in command window to check connection between phone and PC (I used Windows 7).
6. Manually run all fastboot commands listed below, or use a batch file, or maybe try RSDLite (run flashfile.xml in the firmware folder). RSDLite is old, but the last version of it (6.2.4) worked fine on a Moto G Stylus 2021 that I unlocked and rooted a year ago. It's a fairly simple tool that has aged well thus far.
7. Check that each flash command finished with an OKAY (actually 2 OKAYs). It ANY fail, you should start all over, or suspect that your firmware download is corrupt, or USB cable is bad . . .
8. If ALL files flashed OKAY, "fastboot reboot" or use the Volume and Power keys.
Commands (your firmware may be slightly different, possibly one extra sparsechunk file):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth btfm.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase ddr
fastboot erase userdata ... optional but advised (included in flashfile.xml but not in servicefile.xml)
fastboot oem fb_mode_clear
fastboot reboot
I posted this in the wrong section. I hope a diligant moderator will find and correct my mistake soon.
Moondroid said:
I posted this in the wrong section. I hope a diligant moderator will find and correct my mistake soon.
Click to expand...
Click to collapse
That’s what the report button is for
I've posted in the wrong section
sd_shadow said:
That’s what the report button is for
I've posted in the wrong section
Click to expand...
Click to collapse
I thought about trying that but was afraid it might set off a 3-alarm fire or something. Lol.
Badger50 got it fixed for me.