Related
DO NOT LOCK THE BOOTLOADER WHILE ROOTED!
When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader.
Locking the bootloader will not fix most issues. It will allow you to use apps that check for an unlocked bootloader without the need for any additional modification. That is the ONLY benefit.
If you still want to lock your bootloader, make sure you can say yes to each of the following:
1. Have you restored the stock boot.img / vendor_boot.img and the phone functions normally?
Spoiler: Restore Stock Boot
Boot / DTBO Images [Root / Stock] - 5 / Pro / Ultimate (NOT S)
These images are NOT built from source. These are the stock images from the firmware provided by Asus that are extracted with payload dumper and uploaded without modification. 18.0840.2202.231 18.0840.2201.226 18.0840.2112.211...
forum.xda-developers.com
Follow the instructions in the thread above.
Use only the boot and vendor_boot images.
Do NOT flash any images that end with "-magisk.img"
2. Have you made a backup of everything you do not want to lose when wiping the phone?
Spoiler: Make a Backup
The sdcard is part of the internal storage and is cleared by a factory reset
Copy everything you want to keep to a computer or USB-C storage device
Apps and settings can be backed up by enabling the Google Backup option
Open Settings
Select Google
Select Backup
Select Back up now
Wait for the backup to complete
3. Have you flashed raw firmware and made sure the phone and updates function normally?
Spoiler: Flash Raw Firmware
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Follow the instructions in the thread above.
If you perform a wipe, you may skip step 4.
4. Have you performed a factory reset and made sure the phone functions normally?
Spoiler: Factory Reset
Open Settings
Select System
Select Reset options
Select Erase all data (factory reset)
Follow the instructions
Once you have verified all of the above requirements, you are now ready to lock the bootloader.
Spoiler: Lock Bootloader
From the bootloader (volume up + power):
Code:
fastboot oem asus-csc_lk
Reserved for QA information
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
falhumai96 said:
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
Click to expand...
Click to collapse
Based on new information, it does seem possible to repair the issues caused by converting.
That said, this guide is still quite relevant. After all, most of the issues people were having were caused by unlocking the bootloader, converting, rooting, and locking the bootloader. The warning for possibility of not being able to unlock have been removed, but the info about restoring to stock before locking has been left.
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
chairman011 said:
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
Click to expand...
Click to collapse
@chairman011 what variant of the phone it is (e.g. CN or WW or US, ...etc.)? Also, when they returned it to you and you were able to unlock it again, was it on the original firmware (or any version in its lineage (i.e. not a ROM that's not original))?
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
nexusnerdgeek said:
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
Click to expand...
Click to collapse
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
falhumai96 said:
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
Click to expand...
Click to collapse
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
twistedumbrella said:
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
Click to expand...
Click to collapse
So, basically the bootloader unlock for tencent devices will always locked unless asus uodate their unlock app or has their been another way around it yet?
The unlock app should unlock the bootloader at least once. Unlocking it a second time has mixed results.
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
0v3rkill said:
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
Click to expand...
Click to collapse
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Andrologic said:
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Click to expand...
Click to collapse
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
0v3rkill said:
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
Click to expand...
Click to collapse
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Andrologic said:
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi there, I did follow and did the raw setup it did got me through the boot loop. However, its stuck on the system start up updating screen and stays in 0%.
Darn i thought im already dead! i didn't even know how i fixed it hahahaha! but its working now successfully downgraded to android 11 because its the only firmware i found and managed to make it work again combination of alot of research in google and here xda. working 100% imei two of them, finger print and sn are all intact. thanks guys
For these few reasons I have to give up root & lock the boot-loader: 1. Financial apps stop working from time to time causing much grief; 2. I've used root functionality precisely for nothing for a year I've had it; 3. It was getting all too complicated to keep up with it all.
(The original intention for unlocking/rooting was to get some sort of unofficial VoLTE and VoWiFi for the mobile operator of my choice; however, it didn't help. Then a newer firmware implemented VoLTE and VoWiFi! So my impatience, admittedly couldn't be known at that point in time, backfired.)
I've nothing to preserve on the phone, due to having a Moto G 5G backup phone. I only had it working with adb & fastboot in my Linux laptop (up to date Fedora 36). I had no working Windows laptop then. But I do now. However, adb on Windows says the device is "unauthorised" (as expected); fastboot in it doesn't list the device. So I might be limited to my Linux laptop only. The phone was previously working on the last A11 WW firmware fine.
I've tried to follow the steps from the original post of this thread. First one worked with vendor_boot, dtbo & boot images (used only 18.0840.2202.231 versions of them). Second N/A. With third step, flash_raw_and_wipe_data.sh fails by core dumping.
Right now, the phone boots to fastbootd & not further. Any help is much appreciated.
(I think I'm inching towards fully bricking this phone. I'm not there yet, but getting closer . It'd be nice to get it working again without root & with locked boot loader. Any help is much appreciated.)
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
nexusnerdgeek said:
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
Click to expand...
Click to collapse
Confirm that you can send fastboot commands to the device. It's a prerequisite for flashing the original boot img back or doing a RAW flash if boot looped. That's the very first step you need sorted and confirmed. Sounds like you may not be in the right Fastboot mode. The RAW version doesn't matter too much as long as it's in line with your device version, you just need it to get back up and can upgrade normally to other versions.
I just wanna learn how to begin the rooting don't know what driver how to get a sdk what app nothing?
I'm looking at the A13 as well since the GS5 is now blocked by AT&T.
I just spoke to Samsung, and they told me the A13 G5 unlocked version purchased directly from them comes with an unlocked bootloader.
I think I just wet myself.
MaddogK said:
I just spoke to Samsung, and they told me the A13 G5 unlocked version purchased directly from them comes with an unlocked bootloader.
I think I just wet myself.
Click to expand...
Click to collapse
What about flashable firmware?
Rularick5 said:
What about flashable firmware?
Click to expand...
Click to collapse
I don't think there's any yet, it's only been on the market for a few months. Aside from it's size it's pretty nice, I've had it 2 weeks and love the battery life.
MaddogK said:
I just spoke to Samsung, and they told me the A13 G5 unlocked version purchased directly from them comes with an unlocked bootloader.
I think I just wet myself.
Click to expand...
Click to collapse
This one dosnt
Samfirm should have the version of android you need for you're phone you need the Samsung flash tool su+twrp+magisk is optional good luck! Ps.always back up everything
I will be working on mine purchased from Metro PCS. Its OEM bootloader is locked at the moment. I will be using Magisk and flashing a TWRP. Utilizing an ADB wireless USB connection from PC. I will keep you posted if someone else doesnt beat me too it. Either way this thread is going so im sure together we can knock this out. Im going to do my LG Stylo 4 firsy. Its OEM came unlocked from Metro PCS...so i scored. Just havent had time. I just did my ZTE ZMax Pro Z981 from Metro PCS...it also was unlocked OEM. They will all need a PC usb connection and Magisck. You can find them in threads here. Good luck. Will post again when i get time. Hope this helps a little. Here you might not get an answer you want...but if you dig youll find what youre looking for...just got learn by doing...like they said...always backup... everything...first...dont forget to remove sd before you factory reset or you will wipe it. And your phone. If youre not sure...dont change things you dont know...you will brick your phone. Follow directions you find in threads...and you will be fine. I learned how to be a great chef from other chefs who told me the ingredients but never amounts of ingredients. Thats how you become a great chef and also become great developer...good luck guys. Im learning too. Share what you learn. FYI...the one click....dont bother...IJS...PC you will need for this....
GeekNout23 said:
I will be working on mine purchased from Metro PCS. Its OEM bootloader is locked at the moment. I will be using Magisk and flashing a TWRP.
Click to expand...
Click to collapse
How do you plan on flashing those if the bootloader is locked.....?
Sorry to break it to you, but it's a Samsung thing. It doesn't matter if it's a device from a carrier or carrier-free directly from Samsung, if you buy a U.S. Samsung phone you will not unlock bootloader freely.
ShaDisNX255 said:
Sorry to break it to you, but it's a Samsung thing. It doesn't matter if it's a device from a carrier or carrier-free directly from Samsung, if you buy a U.S. Samsung phone you will not unlock bootloader freely.
Click to expand...
Click to collapse
Correct
first you need oem unlock on that takes pluging in phone holding volume+/- (both) and power till it shutdown and restarts with the unlock option in recovery
Just bought this but the 5G version
Hi, I just rooted my Samsung Galaxy A13. Here's a quick tutorial of what worked for me:
Prerequisites:
Install Heimdall onto your computer. I used Manjaro Linux as my OS, and haven't tested anything else. Install any drivers if necessary.
Install Magisk onto your phone. I recommend using the F-Droid store/app, or Magisk's GitHub page.
Steps
Install any updates for your phone.
Unlock Bootloader
First of all you need to unlock the bootloader:
Enable Developer Mode by navigating: Settings > About Phone > Software information.
Tap Build number about 7 or 8 times until it says You're now a developer.
Allowing the bootloader to be unlocked:
Settings > Developer Options > Enable OEM unlocking.
Allow it to be enabled if prompted.
Turn off your device.
Turn on Download Mode by holding down Volume Up and Volume Down.
When you see a blue screen, hold Volume Up until it shows Unlock Bootloader screen.
Press Volume Up to confirm.
Flashing firmware
https://samfw.com/ is a good resource for downloading firmware. Be careful that you're downloading the correct firmware though. You can find information by navigating on your phone:
Settings > About Phone, and Settings > About Phone > Software information. If you call *#1234# it will show you the current firmware.
Extract the archive.
Extract the file staring with AP.
Extract the file boot.img.IZ4.
Move boot.img onto your phone.
Open Magisk. Click install. Locate and patch the file. Move the file back onto your computers.
Extract the file starting with CSC. Locate the pit file.
Open Heimdall.
Choose the pit file and the patched boot image.
Put your phone in Download Mode and connect via USB.
Flash your phone.
If it worked successfully, your phone will reboot. It will probably throw an error before starting. Choose to do a factory reset. This will delete all the user data, but the patched boot file will stay in place.
Download Magisk again. Follow the prompts.
To test if you have super user access, install Termux from the F-Droid store. type su into the terminal. You will get a pop up asking if you want to give super user permissions.
Congratulations! You're now the UNIX sysadmin of your own phone!
hello Everyone, a friend of mine from America bought an A13 5G, now we are in Europe and the phone is blocked.
exactly inserting a European sim says:
Phone locked. Please contact our customer service center to unlock your phone.
i tried to unlocked bootloader, but unfortunately i don't have OEM unlock present, no way i get it out!
there is a complicated procedure with Flashing a Combination Firmware, but it looks difficult!!! I haven't done it yet.
but would it be possible to only unlock the phone to use European sims?
many thanks
K
krellz said:
hello Everyone, a friend of mine from America bought an A13 5G, now we are in Europe and the phone is blocked.
exactly inserting a European sim says:
Phone locked. Please contact our customer service center to unlock your phone.
i tried to unlocked bootloader, but unfortunately i don't have OEM unlock present, no way i get it out!
there is a complicated procedure with Flashing a Combination Firmware, but it looks difficult!!! I haven't done it yet.
but would it be possible to only unlock the phone to use European sims?
many thanks
K
Click to expand...
Click to collapse
Unlocking the bootloader would not do anything for you in regards to network unlocking. Those are 2 totally separate and distinct procedures.
What's the Baseband Version on the device? You can find that under Settings-->About-->Software Information (and don't do any software updates to the device if it prompts you to)
Hello, the first thing would be to unlock the bootloader which is very easy in Samsung terminals, In all Samsung is the same, you can see the following video that I recommend. No PC needed, The video is in Spanish but it is only to follow the same steps:
The second thing would be to get root, the easiest would be with Magisk, I recommend you watch this video since it is not necessary to format the cell phone, the video is also in Spanish, but you still follow the same steps. In this case, a PC is necessary:
Soon I will make a post myself, teaching you how to root without losing data, the same way as in the video, in case you didn't understand the video.
There is no boot.img.IZ4 im my ap file
ok i found the boot.img I extracted the ap file with winrar before. some how it does not see the .img files but untarring on linux worked. i managed to re flash the ap fille with odin and i saw lot of .img files being flashed and the extracted foldersize by winrar was way smaler than the archive. so that made me look at the ap file and i got the boot.img patched by magisk and made an lz4 file out of it how do i get that boot.img.lz4 back in the archive?
also whats wrong with fast boot?
"fastboot devices" lists my device when its connected but like many here post it does not work with other commands it failes like thIs :
fastboot flash bootloader b.img
Sending 'bootloader' (32768 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
Tried other examples too but nothing works tried the fastboot included in android studio and one of the minimal adb/fastboot. the boot loader is unlocked (Not using fastboot) and odin works fine. my phone is in the "entertering fastboor mode" state .its a samsung galaxy a13 g5 and i flashed this firmware using odin
AP_A136BXXS2BWA1_A136BXXS2BWA1_MQB61124574_REV00_user_low_ship_MULTI_CERT_meta_OS13 now its stock again with no accounts.
fastboot reboot does work so some is right.
fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
i hope some one can point me in the right direction.
thx
Hans de Groot said:
i hope some one can point me in the right direction.
thx
Click to expand...
Click to collapse
Fastboot isn't functional on Samsung devices. Samsung replaces it with Download mode. Therefore, all flashing is done via Download mode using Odin, not via fastboot mode using command terminal
Hi, so I have a tmobile 8t sim unlocked and attempting to flash the international bootloader from the tmobile bootloader I have somehow gotten it stuck in edl mode, i can do a readback of the partitions using msm tool but cant flash any variant as I get a Get CID error or device image doesnt match, if i remember right i messed up the param.bin anywho when I first got the phone for situations such as this i have in the cloud a full F8 readback from rigjjt after i took it out of the box.... and when i use QFIL and open the partition manager the screen is empty. Any ideasa? I already sent it back to OP and have them fix it but in a total service meltdown they had my phone over a month and then sent it back marked repaired....Im totally stuck here
Check general discussion
There's a thread can convert T-Mobile version to EU, and you can unlock bootloader there if you want, and you can do local update back to global.
It can also fix your issue
saduncan084 said:
Hi, so I have a tmobile 8t sim unlocked and attempting to flash the international bootloader from the tmobile bootloader I have somehow gotten it stuck in edl mode, i can do a readback of the partitions using msm tool but cant flash any variant as I get a Get CID error or device image doesnt match, if i remember right i messed up the param.bin anywho when I first got the phone for situations such as this i have in the cloud a full F8 readback from rigjjt after i took it out of the box.... and when i use QFIL and open the partition manager the screen is empty. Any ideasa? I already sent it back to OP and have them fix it but in a total service meltdown they had my phone over a month and then sent it back marked repaired....Im totally stuck here
Click to expand...
Click to collapse
My friend i have the solution for u, dm me I went through the exact same thing
Hey guys so I have been having problems with my moto past couple months just not working right. Long story just a lil shorter come to find out I've been under atack on my home network with constant ddos attacks and arp spoofing. So in my mind maybe if my device is infected with something if I relocked the bootloader it would get rid of what's not supposed to be there and I could start fresh. NOPE not even a little bitas soon as I typed in the flashing lock command this screen popped up no valid operating system. Figures ok no biggie not my first rodeo. I can use moto flash tool or Lenovo assistant. NOPE strike 2 moto flash won't recognize because one, debugging not enabled nor is the oem toggle on in dev options and this will be first device the assistant could not flash either said something about only 1 partition availabled. So my question is how do I get debugging enabled oem toggled all while having no OS or recovery and because of BL being lockedi can't even boot into twrp to put recover. Oh and bootloader screen will load but not recognized by fastboot. All you devs on here are quiet brilliant most of the time I'm sure u guys have a way around these issues any help would be much appreciated
If you can't flash image the stock ROM your on if not you're in the same boat as me my bootloaders lock no OS and I turned off the OEM so I guess it's hard bricked there's no coming back for it unless you have your warranty and you could just swap it
m.mcneil99 said:
If you can't flash image the stock ROM your on if not you're in the same boat as me my bootloaders lock no OS and I turned off the OEM so I guess it's hard bricked there's no coming back for it unless you have your warranty and you could just swap it
Click to expand...
Click to collapse
damn appreciate the info. couple people were talking about testnpoints to get into edl. have you heard anything bout that?
yes...Start over blankflash it
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
paulb89 said:
damn appreciate the info. couple people were talking about testnpoints to get into edl. have you heard anything bout that?
Click to expand...
Click to collapse
maddog3030 said:
yes...Start over blankflash it
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
a
Click to expand...
Click to collapse
I've asked so many times in different forums and could never really get a straight answer what that is and what that accomplishes. Could you explain, and the process in which I need to follow to flash and possibly put some life back into my phone
paulb89 said:
asked so many times in different forums and could never really get a straight answer what that is and what that accomplishes. Could you explain, and the process in which I need to follow to flash and possibly put some life back into my phone
Click to expand...
Click to collapse
Here's an example
EDL test points and blank-flash boost mobile
Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
forum.xda-developers.com
But you need to use the correct blank flash file p
ok ima try it now ill let u know. i appreciate all your help
maddog3030 said:
Here's an example
EDL test points and blank-flash boost mobile
Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
forum.xda-developers.com
But you need to use the correct blank flash file p
Click to expand...
Click to collapse
Hey I know this thread is a bit old, but I have a Moto X2131-1 RETUS that boots into fastboot mode with the correct blankflash file, but it shows that the bootloader is still locked. Is there any way to still save this device without having to replace the motherboard?
Much appreciated!
cabinhead said:
Hey I know this thread is a bit old, but I have a Moto X2131-1 RETUS that boots into fastboot mode with the correct blankflash file, but it shows that the bootloader is still locked. Is there any way to still save this device without having to replace the motherboard?
Much appreciated!
Click to expand...
Click to collapse
Is it locked or re-locked?
Once these motherboards have been relocked it's very difficult to unlock them again.
You can always try flashing stock that matches the appropriate blankflash that used on it.
then reboot to the OS
set up developers make it unlockable then use the token you got from Motorola to unlock it.
maddog3030 said:
Is it locked or re-locked?
Once these motherboards have been relocked it's very difficult to unlock them again.
You can always try flashing stock that matches the appropriate blankflash that used on it.
then reboot to the OS
set up developers make it unlockable then use the token you got from Motorola to unlock it.
Click to expand...
Click to collapse
I re locked it because I was being dumb, and I can't unlock it because running "fastboot oem unlock <code>" complains that the android OEM unlock setting isn't enabled (I cannot get into android)
How would I flash the stock rom with the blankflash file? I have the stock rom I just dont know how to use it with the bootloader in this weird state
cabinhead said:
I re locked it because I was being dumb, and I can't unlock it because running "fastboot oem unlock <code>" complains that the android OEM unlock setting isn't enabled (I cannot get into android)
How would I flash the stock rom with the blankflash file? I have the stock rom I just dont know how to use it with the bootloader in this weird state
Click to expand...
Click to collapse
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
maddog3030 said:
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
When I use RSA after booting with blankflash it just says "RSA has detected that your device is flash locked." Is there perhaps a way to get the files for qfil and flash it that way?
cabinhead said:
When I use RSA after booting with blankflash it just says "RSA has detected that your device is flash locked." Is there perhaps a way to get the files for qfil and flash it that way?
Click to expand...
Click to collapse
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
cabinhead said:
When I use RSA after booting with blankflash it just says "RSA has detected that your device is flash locked." Is there perhaps a way to get the files for qfil and flash it that way?
Click to expand...
Click to collapse
Last ditch
lolinet channel
You can view and join @lolinetnews right away.
t.me
Look for ZAZ and ignore Valeriy
Okay guys so I bought an unlocked Moto G Stylus 5G 2022 a few weeks ago and I decided to unlock it via the instructions on Motorola's website and root it , which I did.
So after having done that, I decided to unroot it, mainly because of losing Widevine level 1 security , but also for other reasons.
After having done that I tried to flash the stock rom via adb fastboot, but it wouldn't do that (error: command failed).
Also tried using the Motorola LMSA repair tool, but no go either, Both ADB Fastboot and the LMSA recognzed my phone but neither would flash the stock rom.
Here are some pictures that may help.
Thanks guys.
classic757 said:
View attachment 5783383View attachment 5783385View attachment 5783387Okay guys so I bought an unlocked Moto G Stylus 5G 2022 a few weeks ago and I decided to unlock it via the instructions on Motorola's website and root it , which I did.
So after having done that, I decided to unroot it, mainly because of losing Widevine level 1 security , but also for other reasons.
After having done that I tried to flash the stock rom via adb fastboot, but it wouldn't do that (error: command failed).
Also tried using the Motorola LMSA repair tool, but no go either, Both ADB Fastboot and the LMSA recognzed my phone but neither would flash the stock rom.
Here are some pictures that may help.
Thanks guys.
Click to expand...
Click to collapse
First statement in circle doesn't make any sense.
Second statement tells me you've re-locked your bootloader...
Third issue I'm going to take a wild guess at when you unrooted did you restore the original boot image?
I'm going to assume you use magisk in which case it makes a backup fee of the original boot image.
And that might be why your phone is not being recognized.
Last is don't ever post your IMEI online, delete that first image if you can.
maddog3030 said:
First statement in circle doesn't make any sense.
Second statement tells me you've re-locked your bootloader...
Third issue I'm going to take a wild guess at when you unrooted did you restore the original boot image?
I'm going to assume you use magisk in which case it makes a backup fee of the original boot image.
And that might be why your phone is not being recognized.
Last is don't ever post your IMEI online, delete that first image if you can.
Click to expand...
Click to collapse
Thanks for responding to my question.
Okay so in the first statement I meant to say that I bought an unlocked G Stylus 5G 2022 and decided to unlock the bootloader.
Yes, I did re-lock the bootloader.
Yes when I unrooted I did restore the original boot image from the official stock rom.
Adb fastboot recognizes my device as well as the LMSA but neither will flash the stock rom. I even tried to set the active slot to a and b, to no avail.
Oh and I did delete the pics.
Thanks.
classic757 said:
Thanks for responding to my question.
Okay so in the first statement I meant to say that I bought an unlocked G Stylus 5G 2022 and decided to unlock the bootloader.
Yes, I did re-lock the bootloader.
Yes when I unrooted I did restore the original boot image from the official stock rom.
Adb fastboot recognizes my device as well as the LMSA but neither will flash the stock rom. I even tried to set the active slot to a and b, to no avail.
Oh and I did delete the pics.
Thanks.
Click to expand...
Click to collapse
get into bootloader and issue these 2 commands
fastboot getvar all
fastboot oem partition
sanitize both outputs of personal info, IMEI ect. and post them here in full
PS the command is
fastboot set_active a
or
fastboot set_active b
not
fastboot fastboot set_active a
maddog3030 said:
get into bootloader and issue these 2 commands
fastboot getvar all
fastboot oem partition
sanitize both outputs of personal info, IMEI ect. and post them here in full
PS the command is
fastboot set_active a
or
fastboot set_active b
not
fastboot fastboot set_active a
Click to expand...
Click to collapse
Okay thanks will do.
classic757 said:
Okay thanks will do.
Click to expand...
Click to collapse
Okay I posted the pics.
classic757 said:
Okay I posted the pics.
Click to expand...
Click to collapse
Try using Windows Snipping tool next time, for your screenshots, much cleaner
Got them, give me a few.
Preliminary it doesn't look good hope you're not attached to any of the information in the phone
classic757 said:
Okay I posted the pics.
Click to expand...
Click to collapse
classic757 said:
Okay guys so I bought an unlocked Moto G Stylus 5G 2022 a few weeks ago and I decided to unlock it via the instructions on Motorola's website and root it , which I did.
So after having done that, I decided to unroot it, mainly because of losing Widevine level 1 security , but also for other reasons.
After having done that I tried to flash the stock rom via adb fastboot, but it wouldn't do that (error: command failed).
Also tried using the Motorola LMSA repair tool, but no go either, Both ADB Fastboot and the LMSA recognzed my phone but neither would flash the stock rom.
Here are some pictures that may help.
Thanks guys.
Click to expand...
Click to collapse
Download File, Open and READ ALL First.
If all fails the BLANKFLASH, links included
maddog3030 said:
Got them, give me a few.
Preliminary it doesn't look good hope you're not attached to any of the information in the phone
Click to expand...
Click to collapse
Okay thank you.
maddog3030 said:
Download File, Open and READ ALL First.
If all fails the BLANKFLASH, links included
Click to expand...
Click to collapse
Okay great thanks!
I really appreciate your help.
I will let you know how it goes.
sd_shadow said:
Try using Windows Snipping tool next time, for your screenshots, much cleaner
Click to expand...
Click to collapse
Okay will do thanks.
maddog3030 said:
Download File, Open and READ ALL First.
If all fails the BLANKFLASH, links included
Click to expand...
Click to collapse
Okay so while in fastboot I could get nothing flashed because I would get a "command failed" error every time.
Tried to do the blankflash file but it stayed stuck on "waiting for device".
Idk what else to do.
There is someone on xda that posted they had a similar issue with their phone and they had someone fix it remotely. I think they are talking about a guy who did a YouTube video showing how he fixed someone's hard bricked device. I contacted that individual on WhatsApp and they said I need to fix the bootloader. I asked them what do I need to do and they didn't respond back. Idk.
classic757 said:
Okay so while in fastboot I could get nothing flashed because I would get a "command failed" error every time.
Tried to do the blankflash file but it stayed stuck on "waiting for device".
Idk what else to do.
There is someone on xda that posted they had a similar issue with their phone and they had someone fix it remotely. I think they are talking about a guy who did a YouTube video showing how he fixed someone's hard bricked device. I contacted that individual on WhatsApp and they said I need to fix the bootloader. I asked them what do I need to do and they didn't respond back. Idk.
Click to expand...
Click to collapse
sorry but mabey i did not go into "BLANKFLASH" enough, thought you might not need it, but
EDL test points and blank-flash boost mobile
Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
forum.xda-developers.com
this is an example of what needs to be done (this is not for your model).
you need to search for the EDL test point for your model .
DID YOU GET A Serial Number in response to the command "fastboot devices"?
https://t.me/motoblankflash ask for ZAZ
maddog3030 said:
sorry but mabey i did not go into "BLANKFLASH" enough, thought you might not need it, but
EDL test points and blank-flash boost mobile
Here are the edl (emergency download mode) test points for Motorola Moto G Stylus 5G XT2131.
forum.xda-developers.com
this is an example of what needs to be done (this is not for your model).
you need to search for the EDL test point for your model .
DID YOU GET A Serial Number in response to the command "fastboot devices"?
https://t.me/motoblankflash ask for ZAZ
Click to expand...
Click to collapse
Yes I get a serial number and imei number.
I can do the fastboot command getvar all but I cannot flash any part of stock firmware. I cannot set the active slot to a or b.
Fastboot recognizes my device and so does the LMSA tool but neither one will flash firmware.
classic757 said:
Yes I get a serial number and imei number.
I can do the fastboot command getvar all but I cannot flash any part of stock firmware. I cannot set the active slot to a or b.
Fastboot recognizes my device and so does the LMSA tool but neither one will flash firmware.
Click to expand...
Click to collapse
ok,
problem is 2 fold
3 states on this phone are
securestate: oem_locked
securestate: flashing_unlocked
securestate: flashing_locked
you are the last one, that flips the "OEM unlocking" to turm off.
and you system is corrupt (not booting ).
blankflash basically reformat the phone and returns "securestate: flashing_unlocked"
your current OS is MILANF_RETUS_12_S1SDS32.56-81-4
the newest blankflash out for your phone is milanf_retus_S1SD32.56-6
this is considered a downgrade and the phone wont allow it.
still hope!!
a blankflash cam be made from the image of XT2215-4_MILANF_RETUS_12_S1SDS32.56-81-4
but i dont have the rig to do it but "ZAZ" @ https://t.me/motoblankflash can.
last i checke he can generate one in 20-30 min and DID NOT charge for his help.
I hope this explained you problem, good luck.
maddog3030 said:
ok,
problem is 2 fold
3 states on this phone are
securestate: oem_locked
securestate: flashing_unlocked
securestate: flashing_locked
you are the last one, that flips the "OEM unlocking" to turm off.
and you system is corrupt (not booting ).
blankflash basically reformat the phone and returns "securestate: flashing_unlocked"
your current OS is MILANF_RETUS_12_S1SDS32.56-81-4
the newest blankflash out for your phone is milanf_retus_S1SD32.56-6
this is considered a downgrade and the phone wont allow it.
still hope!!
a blankflash cam be made from the image of XT2215-4_MILANF_RETUS_12_S1SDS32.56-81-4
but i dont have the rig to do it but "ZAZ" @ https://t.me/motoblankflash can.
last i checke he can generate one in 20-30 min and DID NOT charge for his help.
I hope this explained you problem, good luck.
Click to expand...
Click to collapse
Okay thanks. I'll try to contact him.
I appreciate all your help.