Database Info

Relock the Bootloader

Hi,
I want to give my unlocked Moto G to a family member - and I'd like to relock the bootloader again, for security reasons.(I don't care about the warranty)
is there a way to do that?

RazorHail said:
Hi,
I want to give my unlocked Moto G to a family member - and I'd like to relock the bootloader again, for security reasons.(I don't care about the warranty)
is there a way to do that?
Click to expand...
Click to collapse
open FAQ
ctrl+f : "relock"

matmutant said:
open FAQ
ctrl+f : "relock"
Click to expand...
Click to collapse
thanks,
I've already tried that.
But when I enter "fastboot oem lock", I get:
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
Click to expand...
Click to collapse
when I enter the suggested "fastboot oem lock begin", I get:
(bootloader) Ready to flash signed images
Click to expand...
Click to collapse
I'm not sure what that's suppose to mean.....I already downloaded the official firmware images and flashed those immediately after I get this message........but it still says that the bootloader is unlocked.
And immediately returning back to the bootloader and typing in "fastboot oem lock" still won't work - same message as before...
am I missing something?

RazorHail said:
thanks,
I've already tried that.
But when I enter "fastboot oem lock", I get:
when I enter the suggested "fastboot oem lock begin", I get:
I'm not sure what that's suppose to mean.....I already downloaded the official firmware images and flashed those immediately after I get this message........but it still says that the bootloader is unlocked.
And immediately returning back to the bootloader and typing in "fastboot oem lock" still won't work - same message as before...
am I missing something?
Click to expand...
Click to collapse
Yup, this "unlock-relock" is WIP yet ..

i done a relock last week and this works for me.use adb command "fastboot oem lock begin" go through the routine to flash factory firmware image and use "fastboot oem lock" command to finish after you flashed factory firmware.

akaygee said:
i done a relock last week and this works for me.use adb command "fastboot oem lock begin" go through the routine to flash factory firmware image and use "fastboot oem lock" command to finish after you flashed factory firmware.
Click to expand...
Click to collapse
So, steps are these:
1: fastboot oem lock begin
2: flash stock firmware
3: fastboot oem lock
And BL will be locked again. Correct me if i'm wrong.
Problem is that for "unlocked" we need always of a code by motorola atm.

denzel09 said:
So, steps are these:
1: fastboot oem lock begin
2: flash stock firmware
3: fastboot oem lock
And BL will be locked again. Correct me if i'm wrong..
Click to expand...
Click to collapse
thats how it works on most motorola android phones i have used ,it works fine on my moto g so yes that is right.
like so
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock

akaygee said:
thats how it works on most motorola android phones i have used ,it works fine on my moto g so yes that is right.
like so
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Click to expand...
Click to collapse
for me not working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

danger2u said:
for me not working
Click to expand...
Click to collapse
you didn't flash factory firmware in between

akaygee said:
you didn't flash factory firmware in between
Click to expand...
Click to collapse
i have some problem when i try to flash the system img

this is just a quick howto am at work....
the files you need and will use are in moto g section of this forum.
firmware's here
http://forum.xda-developers.com/showthread.php?t=2546251
relock bootloader
=============
keep in mind this will remove any and all personal files and settings
like any self respecting android user you have made backups right....!!!! GOOD
download adb and fastboot extract or place into a directory.
now download the factory firmware image of your phone extract zip/rar and place into the same directory.
download "relock bootloader.txt" rename to "relock bootloader.bat" place this in the same directory as the files and double click it ,this would save you typing in all the commands from below in by hand and does it all for you.recap....if you did download and run relock bootloader.bat you dont need to type anything form below
open a command prompt as administrator ,navigate to the directory where you placed all the files we are working with and type as follows giving time for each command to finish.
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock

When we ask the motorola unlock code, this does not imply that we actually unlock the bootloader.
I mean, i can ask to motorola to unlock code but i can decide to unlock also after sometimes, who stops me.
So, i think that when we relock bootloader, also if previously we asked an unlock code, we are ok, for what i writed above. How can they to be sure that bootloader has been really unlocked in case of brick or hardware failure ?

denzel09 said:
When we ask the motorola unlock code, this does not imply that we actually unlock the bootloader.
I mean, i can ask to motorola to unlock code but i can decide to unlock also after sometimes, who stops me.
So, i think that when we relock bootloader, also if previously we asked an unlock code, we are ok, for what i writed above. How can they to be sure that bootloader has been really unlocked in case of brick or hardware failure ?
Click to expand...
Click to collapse
the boot loader has a status indicator.phone shops/retailers probably won't check it but motorola will.

akaygee said:
the boot loader has a status indicator.phone shops probably won't check it but motorola will.
Click to expand...
Click to collapse
Understood, i had read something in an other post, so to complete the "opera" we need to 'something' to reset that count/status? Like on samsung device, s2 et similia?

denzel09 said:
Understood, i had read something in an other post, so to complete the "opera" we need to 'something' to reset that count/status? Like on samsung device, s2 et similia?
Click to expand...
Click to collapse
yes that is right we would need to find out what file is responsible for storing the count or status of the boot loader as its not the boot loader its self that holds this information.even if you flash the whole system after relocking the bootloader the count is still there.

akaygee said:
yes that is right we would need to find out what file is responsible for storing the count or status of the boot loader as its not the boot loader its self that holds this information.even if you flash the whole system after relocking the bootloader the count is still there.
Click to expand...
Click to collapse
wth i just doing wrong???
the firmware is Blur_Version.14.91.11.falcon_umts.Retail.en.DE
he gives me this error and on the phone says failed to validate system image

akaygee said:
yes that is right we would need to find out what file is responsible for storing the count or status of the boot loader as its not the boot loader its self that holds this information.even if you flash the whole system after relocking the bootloader the count is still there.
Click to expand...
Click to collapse
Motorola talked about a fuse that is "burned" when unlocking, that's why they know, even after relocking
_________________________
i need to update FAQ about relocking (i never ever needed to relock a bootloader myself )
So for relocking, i would like to directly link your post @akaygee, please duplicate it in FAQ thread . then, i'll ask the current thread to be moved to Q&A.

@danger2u
interesting ,are you using a carrier branded phone.? that or the bootloader is locked
i used this method on a uk retail moto g and never run into any problems

akaygee said:
interesting ,are you using a carrier branded phone.?
i used this method on a uk retail moto g and never run into any problems.
Click to expand...
Click to collapse
no is not branded
i bought from italian retail store
now i will try to flash with uk firmware

matmutant said:
Motorola talked about a fuse that is "burned" when unlocking, that's why they know, even after relocking
_________________________
i need to update FAQ about relocking (i never ever needed to relock a bootloader myself )
So for relocking, i would like to directly link your post @akaygee, please duplicate it in FAQ thread . then, i'll ask the current thread to be moved to Q&A.
Click to expand...
Click to collapse
So it will be impossible to reset that status ?

problem ubgrading to kitkat 4.4.4 (MOTO G)

Hello Brothers ,
i have a moto G (with android kitkat 4.4.2 rooted with unlocked bootloader Model XT1032) today i want to upgrade to 4.4.4 kitkat version
i made all the steps (i downloaded the 4.4.4 version using motorola OTA- i waited for the installation complet but on the last step when the phone reboot it's stay on warning bootloader screen )
It's stay here and bug here on this screen :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So ,Please Help me
and Greatest to All XDA-Devlopers members and developers

Waiting for developers .......

wahson said:
Waiting for developers .......
Click to expand...
Click to collapse
Can you please state all the steps you took?

TyCaliburEX said:
Can you please state all the steps you took?
Click to expand...
Click to collapse
okay ,
the steps are :
my phone was on 4.4.2 android version (rooted + bootloader unlocked)
when i turned on wifi i receive message that there are a new version of android 4.4.4 if you want to upgrade your android click yes i'am in
i clicked yes i'am in
the android 4.4.4 was downloaded and installed but when my phone reboot it's bug on the warning bootloader unlocked
i think it's damaged
THE ONLY THING WORKS ON THIS PHONE NOW ARE FASTBOOT
IF THE ARE ANY WAY TO REINSTALL ANDROID 4.4.2 MANUALY FROM FASTBOOT
PLEASE HELP ME
I FOLLOWED THIS STEPS HERE BUT NO WAY :
http://forum.xda-developers.com/showthread.php?t=2585242

wahson said:
okay ,
the steps are :
My phone was on 4.4.2 android version (rooted + bootloader unlocked)
when i turned on wifi i receive message that there are a new version of android 4.4.4 if you want to upgrade your android click yes i'am in
i clicked yes i'am in
the android 4.4.4 was downloaded and installed but when my phone reboot it's bug on the warning bootloader unlocked
i think it's damaged
the only thing works on this phone now are fastboot
if the are any way to reinstall android 4.4.2 manualy from fastboot
please help me
i followed this steps here but no way :
http://forum.xda-developers.com/showthread.php?t=2585242
Click to expand...
Click to collapse
i resolved problem thanks for your helps brothers

wahson said:
i resolved problem thanks for your help brothers
Click to expand...
Click to collapse
Can you say how you solved the problem? So other people can solve this problem without asking again.
I assume the problem was the root so you needed to go back to stock 4.4.2 with only bootloader unlocked and nothing else, then upgrade to 4.4.4 OTA and then reinstall the custom recovery and the root right?

rep
Nesquick_xD said:
Can you say how you solved the problem? So other people can solve this problem without asking again.
I assume the problem was the root so you needed to go back to stock 4.4.2 with only bootloader unlocked and nothing else, then upgrade to 4.4.4 OTA and then reinstall the custom recovery and the root right?
Click to expand...
Click to collapse
Yes i backed to 4.4.2
steps :
1- you have to download your special motorola firmware from
PHP:
sbf.droid-developers.org/phone.php?device=14
2- you have to rename : system.img_sparsechunk.0 to system.img_sparsechunk1 & system.img_sparsechunk.1 to system.img_sparsechunk2
& system.img_sparsechunk.2 to system.img_sparsechunk3
3- you have to enter to fastboot mode on your phone
4- after downloading fastboot package you have to open a command and write the commands bellow :
PHP:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
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 flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
AND BOOM IT WORKS ..

[Firmware] 8.1 official Moto Z3 Play [BECKHAM]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO Z3 Play
Download Moto Z3 Play 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:
adb fastboot
fastboot flash partition gpt.bin ( not mandatory )
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.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 system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot erase modemst1 ( not mandatory )
fastboot erase modemst2 ( not mandatory )
fastboot reboot
Click to expand...
Click to collapse
Thanks to Motorola firmwares.
Password:
MotorolaFirmwaresLB
BECKHAM_OPW28.70-22_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
-DRIVE
-AFH

Will this work on the Amazon version?

Hello, it should work

I would be VERY careful about trying to use the image provided here.
I picked up the Z3 today hoping to be able to build TWRP recovery with this image. Using the kernel from this image resulted in a permanently bricked device. It would no longer turn on. At all.
Second Z3, using the provided image's boot.img and only booting boot.img from fastboot... hung the device.
This tells me the linked image here is very likely to be incompatible with many Z3 Play devices.
The version I've tested it with is the US retus software channel version.
As far as I've been able to tell, this image is for French devices only. DO NOT use this image if you cannot confirm it will work by testing the boot image first.
Extract boot.img from the archive and put your phone into fastboot mode. Test it by typing "fastboot boot boot.img" - If your phone hangs at the motorola logo, this firmware WILL BRICK YOUR PHONE.
The Z3 Play has NO FIRMWARE candidates on https://firmware.center - So, I repeat, the firmware linked here is likely NOT compatible with your device.

twelfth said:
I would be VERY careful about trying to use the image provided here.
I picked up the Z3 today hoping to be able to build TWRP recovery with this image. Using the kernel from this image resulted in a permanently bricked device. It would no longer turn on. At all.
Second Z3, using the provided image's boot.img and only booting boot.img from fastboot... hung the device.
This tells me the linked image here is very likely to be incompatible with many Z3 Play devices.
The version I've tested it with is the US retus software channel version.
As far as I've been able to tell, this image is for French devices only. DO NOT use this image if you cannot confirm it will work by testing the boot image first.
Extract boot.img from the archive and put your phone into fastboot mode. Test it by typing "fastboot boot boot.img" - If your phone hangs at the motorola logo, this firmware WILL BRICK YOUR PHONE.
The Z3 Play has NO FIRMWARE candidates on https://firmware.center - So, I repeat, the firmware linked here is likely NOT compatible with your device.
Click to expand...
Click to collapse
This firmware is for XT1929-4 and no mention is made in the topic....

GuzXT said:
This firmware is for XT1929-4 and no mention is made in the topic....
Click to expand...
Click to collapse
The XT1929-4 is what I have and the firmware definitely did not work for me. I tried to build TWRP for the Z3 Play as I have for other devices and it definitely wasn't going to happen with these files. Even if you 'fastboot boot boot.img', it's supposed to boot like normal using the rest of the what is stored on your phone. Instead it only hangs.

there is this https://forum.xda-developers.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039
we just have to wait for OTA i guess
also there is this if you google beckham_opw28.70-25_subsidy-default_regulatory-default_cfc.xml.zip but they ask for money
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=19944
search for 1929- on https://firmware.gem-flash.com/index.php?a=browse&b=category&id=2634

Here in free access all the same))
https://mirrors.lolinet.com/firmware/moto/beckham/official/

Has anyone been able to relock the bootloader in a way that passes safetynet. I noticed that phone boots with verity set at log only which fails CTS and I want to go back to stock until Magisk works properly.

driverdis said:
Has anyone been able to relock the bootloader in a way that passes safetynet. I noticed that phone boots with verity set at log only which fails CTS and I want to go back to stock until Magisk works properly.
Click to expand...
Click to collapse
magic works quite well if you patch the boot normally, with check marks.

Willy33 said:
magic works quite well if you patch the boot normally, with check marks.
Click to expand...
Click to collapse
Thanks, this did the trick. I was able to download use the boot.img from the lollinet mirror firmware zip. It does require both force encrypt and verity enabled before patching it or it will boot loop.

---REDACTED---

Will this work on the Moto Z3 (XT1929-17)?

wanb1i said:
Will this work on the Moto Z3 (XT1929-17)?
Click to expand...
Click to collapse
You need a firmware image for your specific device. Check the websites from this thread and see if you can find one specific to your device. Other images could brick your device.
The steps should be the same for every device as far as fastboot flashing goes. But don't use an image for another device

darkdaemon32 said:
You need a firmware image for your specific device. Check the websites from this thread and see if you can find one specific to your device. Other images could brick your device.
The steps should be the same for every device as far as fastboot flashing goes. But don't use an image for another device
Click to expand...
Click to collapse
Found the original vzw firmware on Moto's site.
Thanks!

twelfth said:
The XT1929-4 is what I have and the firmware definitely did not work for me. I tried to build TWRP for the Z3 Play as I have for other devices and it definitely wasn't going to happen with these files. Even if you 'fastboot boot boot.img', it's supposed to boot like normal using the rest of the what is stored on your phone. Instead it only hangs.
Click to expand...
Click to collapse
So I have a Verizon Moto Z3 (Brand New XT1929-17, NO XDA Thread yet) I found the firmware off the Motorola site at this link https://androidfilehost.com/?w=files&flid=279604 (last file). I unzipped it, copied the boot.img to my adb folder and executed fastboot boot boot.img and this is the result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.622s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.633s
My goal here is to modify a boot.img so I can root with Magisk without unlocking the bootloader. (Verizon devices don't allow unlocking the bootloader)
Any help would be appreciated.

wanb1i said:
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
Your bootloader is locked. Being a Verizon device, it's likely not unlockable.
You have to have an unlocked bootloader before you can boot and flash in fastboot.
This is why people buy unlocked devices.

Xt-1929-4 opw 20.70-31
Hi, I have the Moto Z3 Play. This is the updated Firmware that I have on my device. I felt I should share it, just in case anyone else needs its. I also added a couple of simple batch files to the folder that I thought everyone might appreciate.
FlashRoot(Service) - Will automatically flash the phone with the patch_boot.img instead of boot.img. This will flash the rooted version of the boot image that was made with Magisk Manager. (Must be in Fastboot)
Flash - Stock --Will automatically flash the regular boot.img also with all the other stock files to the phone. (Must be in Fastboot)
Credit -
Magisk Manager
Google
Hi, I have the Moto Z3 Play. This is the updated Firmware that I have on my device. I felt I should share it, just in case anyone else needs its. I also added a couple of simple batch files to the folder that I thought everyone might appreciate.
FlashRoot(Service) - Will automatically flash the phone with the patch_boot.img instead of boot.img. This will flash the rooted version of the boot image that was made with Magisk Manager. (Must be in Fastboot)
Flash - Stock --Will automatically flash the regular boot.img also with all the other stock files to the phone. (Must be in Fastboot)
Credit -
Magisk Manager
Google
Android FileHost[https ://drive.google. com/open?id=1KAMijX1W2HQx69mDhZ294tp51vtAoo0E[/URL]

Can someone provide a system dump for Moto Z3 Play..
Edit: Done

Hi, my Z3 play has a Bootloop I tried with hard reset and still not working. It's XT1929-6 dual SIM, can someone help me ? Please

[ROM][12.1][PDX206] Ghost OS [AOSP][OFFICIAL][STOCK A12]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ghost OS for Xperia 5 II [PDX206]
What is this?
Ghost OS is a PE based ROM, with Google apps included and most Pixel goodies (icons, fonts, boot animation)
Our mission is to offer a rom that is fast while being secure, along with essential and useful features for the proper functioning of the device
Based on Android 12.1
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
NFC
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download Here
Stay tuned
Our Telegram channel​
Android OS version: 12.1
Security patch level: July 2022
Device Source code: https://github.com/XperiaBrickers
Kernel Source code: https://github.com/lolipuru/android_kernel_sony_sm8250
Source code: https://github.com/Ghost OS
​

This is based on ANDROID 12 TREES (thanks to hellobbn and lolipuru), SO FLASH LATEST STOCK A12 FIRST

Flashing Instructions
PLEASE READ CAREFULLY AS THEY HAVE CHANGED
Flash Instructions
//plug in USB while holding VOL+ during boot, make sure charge LED is blue
//reboot to fastbootd:
fastboot reboot fastboot
//flash the ROM:
fastboot set_active a
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata // only on first install, ignore on upgrading
fastboot delete-logical-partition product_a
fastboot delete-logical-partition system_a // so that fastboot won't complain about disk space
fastboot create-logical-partition product_a 0 // size is 0, will auto-resize during flash
fastboot flash product product.img
fastboot create-logical-partition system_a 0
fastboot flash system system.img
//erase userdata:
fastboot erase userdata // also only on first install
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash recovery recovery.img
//boot the ROM:
fastboot reboot

PE recovery is now working, so next uploads will be full rom zips that you dont have to unpack, you can just do
adb sideload <rom zip name>.zip
We also no longer rely on prebuilt kernels thanks to hellobbn and lolipuru

Bugs
Audio don't work
120hz

A very nice ROM. But unfortunately not suitable as a daily driver without sound.
Is there a chance to fix the sound problem quickly?

seneca said:
A very nice ROM. But unfortunately not suitable as a daily driver without sound.
Is there a chance to fix the sound problem quickly?
Click to expand...
Click to collapse
I've dropped the rom, but I'm working on sound

i thought when you mentioned this, it was a desktop os for rom building haha

owlery_hk said:
i thought when you mentioned this, it was a desktop os for rom building haha
Click to expand...
Click to collapse
no lol

King081 said:
PE recovery is now working, so next uploads will be full rom zips that you dont have to unpack, you can just do
adb sideload <rom zip name>.zip
We also no longer rely on prebuilt kernels thanks to hellobbn and lolipuru
Click to expand...
Click to collapse
Hey where can we find this pe recovery that works for A12?

born2bkilled said:
Hey where can we find this pe recovery that works for A12?
Click to expand...
Click to collapse
Just flash the recovery image from this rom.
Fastboot flash recovery recovery.img
I can confirm it works on stock a12

Hello, is there are lens shades in a raw images on this rom?
Looks like: https://community.sony.lt/t5/5-series/dng-file-defects-xperia5ii/m-p/3722952

legzd2010 said:
Just flash the recovery image from this rom.
Fastboot flash recovery recovery.img
I can confirm it works on stock a12
Click to expand...
Click to collapse
The recovery is TWRP or OrangeFox?
My Xperia 5 ii is under Sony stock A12.
If I just enter Fastboot flash recovery recovery.img, and then reboot my phone, it won't erase my userdata
Two very last questions:
• if the recovery is TWRP, how to disable certain Magisk modules from it, as I was able to do from OrangeFox under root Android 11?
• if I want to make a restorable system recovery, which boxes I have to check when I backup my system from TWRP?
Many thanks!
Yoannjap

Yoannjap said:
The recovery is TWRP or OrangeFox?
My Xperia 5 ii is under Sony stock A12.
If I just enter Fastboot flash recovery recovery.img, and then reboot my phone, it won't erase my userdata
Two very last questions:
• if the recovery is TWRP, how to disable certain Magisk modules from it, as I was able to do from OrangeFox under root Android 11?
• if I want to make a restorable system recovery, which boxes I have to check when I backup my system from TWRP?
Many thanks!
Yoannjap
Click to expand...
Click to collapse
its aosp recovery

King081 said:
its aosp recovery
Click to expand...
Click to collapse
Thanks for your reply.
You mean this one?
Then I already have it.
Still dreaming about an OrangeFox (or TWRP coming next)

Yoannjap said:
Thanks for your reply.
You mean this one?
View attachment 5680909
Then I already have it.
Still dreaming about an OrangeFox (or TWRP coming next)
Click to expand...
Click to collapse
no aosp one is different

King081 said:
no aosp one is different
Click to expand...
Click to collapse
Ok, thank you.
If anyone using this recovery has screenshots to show what more we can do with asop recovery compared to a normal one (can we backup and restore system as with TWRP?)

Yoannjap said:
Ok, thank you.
If anyone using this recovery has screenshots to show what more we can do with asop recovery compared to a normal one (can we backup and restore system as with TWRP?)
Click to expand...
Click to collapse
no just ADB enabling

Can moderators close this please

Question need a little information

Moto G stylus 5G Denver build I had TWRP installed and majisk installed I wanted to install a ROM during insallaion i was having issues and needed 2 set my device down for a few minutes and take care of like regular life problems. Anyways my kid get ahold of my phone and did god-knows-what but he had enough time to wipe everything but my external USB drive. i have the full stock file i downloaded to pach wih magisk i have the twrp file as well.i had my backup on my sd card which was erased. so my question is his, where do i go from here? how do i use files in the picture recover back to I guess a stock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. Version of Android
also doing all his thru bugjager and im sure more then one guide explaining what to do but i need o be at work in 2 hours and so alink in thr right direction would be awesome

tommy2tones1990 said:
also doing all his thru bugjager and im sure more then one guide explaining what to do but i need o be at work in 2 hours and so alink in thr right direction would be awesome
Click to expand...
Click to collapse
In my opinion I would just restore back to stock. Basically, using bugjager, make sure you have the stock rom downloaded and unzipped. Now you'll want to probably copy and paste these commands but you'll reboot your Stylus 5G into fastboot mode and once its connected to the second device with bugjager on it, start going down the list of flashing the partitions back... Here are commands you can copy and paste:
Code:
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 vbmeta_system vbmeta_system.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 vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.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 flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear

I basically spent a hour trying random things on bugjaegar I honestly have no ideal how I didn't brick this phone seriously but then I flashed vbmeta boot and vendor boot and restarted. It took a long time to start then a msg popped up for half a second and the phone rebooted and then I went thru the whole Google startup process and when I got there I rebooted back to bootloader and flashed the magisk patched img and so far everything seems to work
.. thanks for your help.. I'll probably go ahead and wipe everything and start over using your guide. Then go get everything back to how I had it before and and make multiple backups on at least 2 different micro sds then retry the to install ROM

No worries Just saw your post and figured I'd offer some help.. I personally love the bugjaeger app. I use it all the time... it definitely helps if I'm without a computer and got my tablet lol.. and my handy dandy USB-C to USB-C cable lol...