So I'm just warning you guys, be extremely careful when using stock DSU loader.
What happened: I went to developer settings, enabled "OEM Unlock" option (my plan was to root the device), but then I saw DSU option and decided to try it. In my mind that was pretty safe operation.
After the reboot I met a weird screen I never seen before:
QUALCOMM Crashdump Mode
Fatal exception
die
Now all I have is "your device is corrupt" message. It doesn't go to neither recovery nor fastboot (yes, I tried all possible keys combinations with and without USB connected), only EDL mode is available.
By the way, maybe someone knows if this situation meets warranty requirements, because in fact I did not root the device, did not unlock bootloader and did not flash anything onto it.
// I was on 11.2.7.7 global ROM
UPD: Ok, I lied, fastboot is available, I have to disconnect USB, try to turn the phone on (in a usual way), and then after I see phone-corrupt-message I have to hold all 3 buttons (and thats weird too, because it should go to the EDL). But: recovery is not available, fastbootd is not available, changing active slot is not available (because in lock state), fastboot fetch command isn't working. I think I may be able to unlock bootloader and flash something on this stage, but I will try to return the phone so not going deeper.
Some fastboot getvar output, idk, maybe it will be helpful for someone:
Code:
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:no
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:85f871a8
(bootloader) product:lahaina
(bootloader) snapshot-update-status:none
Msm will fix this issue and it's in the threads. Global op9 msm by Fizz.
Thread 'GLOBAL OnePlus 9 MSM TOOL' https://forum.xda-developers.com/t/global-oneplus-9-msm-tool.4284779/
mattie_49 said:
Msm will fix this issue and it's in the threads. Global op9 msm by Fizz.
Thread 'GLOBAL OnePlus 9 MSM TOOL' https://forum.xda-developers.com/t/global-oneplus-9-msm-tool.4284779/
Click to expand...
Click to collapse
Thanks, I know that, not doing that because I will try to return it to the store. I didn't like the phone in general, that was the last straw.
efogdev said:
Thanks, I know that, not doing that because I will try to return it to the store. I didn't like the phone in general, that was the last straw.
Click to expand...
Click to collapse
Yeah that's really crazy,btw what's dsu loader mode. I've never heard of this?
mattie_49 said:
Yeah that's really crazy,btw what's dsu loader mode. I've never heard of this?
Click to expand...
Click to collapse
https://developer.android.com/topic/dsu
Very underestimated feature of android 10/11. And yeah for some reason very few people knows about it. On any android 11+ you have an ability to try Android 12 using the built-in DSU loader.
Hi @efogdev , did you solve the problem? Because I saw that you have the chinese version of the op9 and for this the msm should not work. I have ecountered the same problem and did not get the phone back to work.
AxelM said:
Hi @efogdev , did you solve the problem? Because I saw that you have the chinese version of the op9 and for this the msm should not work. I have ecountered the same problem and did not get the phone back to work.
Click to expand...
Click to collapse
Yes, I successfully unbricked it with indian msm. However I succeded only after 5-6 reboots, driver reinstalls and also I replaced usb cable (used third-party high quality typeC-typeC).
I tried using the USB cable from my old OnePlus 5t. It does not work well, it will stay in fastboot for no reason, changed it to one from an OnePlus 6t and all problems where gone. I could reproduce the problem when I tried again. So be careful guys
noname122414 said:
I tried using the USB cable from my old OnePlus 5t. It does not work well, it will stay in fastboot for no reason, changed it to one from an OnePlus 6t and all problems where gone. I could reproduce the problem when I tried again. So be careful guys
Click to expand...
Click to collapse
Ive successfully been using the cord from my most recent device . The op8 with no issues. Even to oem unlock!
@efogdev : Thanks for this information. Did the original usb-c cable worked for you?
AxelM said:
@efogdev : Thanks for this information. Did the original usb-c cable worked for you?
Click to expand...
Click to collapse
No, I got it working right after cable switch. But maybe that is just a coincidence
@efogdev : Thanks, than I will try my cables again, when I got my phone from op repair service back...
AxelM said:
@efogdev : Thanks, than I will try my cables again, when I got my phone from op repair service back...
Click to expand...
Click to collapse
Feel free to PM or tag me if you fail, I'll try to help reproducing what I did
Bootloader has to be unlocked to load dsu images.. I'm not sure why they don't have a way to keep it greyed/non-selectable unless the BL has been unlocked on a device..
Shooter7889 said:
Bootloader has to be unlocked to load dsu images.. I'm not sure why they don't have a way to keep it greyed/non-selectable unless the BL has been unlocked on a device..
Click to expand...
Click to collapse
This makes perfect sense now. Def doesn't make sense why your able to switch it on and brick your device without oem unlock complete though..good job oneplus
Shooter7889 said:
Bootloader has to be unlocked to load dsu images.. I'm not sure why they don't have a way to keep it greyed/non-selectable unless the BL has been unlocked on a device..
Click to expand...
Click to collapse
The question is why does it keep DSU-loaded image after reboot. AFAIK it should load into another slot after reboot
Btw congrats me with my brand new OnePlus 8 Pro
efogdev said:
Btw congrats me with my brand new OnePlus 8 Pro
Click to expand...
Click to collapse
Op gave you this instead of the 9?
mattie_49 said:
Op gave you this instead of the 9?
Click to expand...
Click to collapse
Idk if you joking, but nah I returned 9 to the store and bought 8 pro. Feels much better
efogdev said:
Idk if you joking, but nah I returned 9 to the store and bought 8 pro. Feels much better
Click to expand...
Click to collapse
Some don't agree but I feel as if the addition of the hassleblad makes so much difference in the 9 series. And I'm a big cam buff. Take lots of pics.
Related
Is this variant to new for rebooting? XT2131-1 bought from bestbuy w/o activation so it's supposed to be unlocked for carrie
I was able to use it on metro/tmoble without issue but cannot seem to get the bootloader unlocked, grayed out
Errors on moto's site for unlocked, not eligible, is it because it's to new?
Eatspizza
eatspizza said:
Is this variant to new for rebooting? XT2131-1 bought from bestbuy w/o activation so it's supposed to be unlocked for carrie
I was able to use it on metro/tmoble without issue but cannot seem to get the bootloader unlocked, grayed out
Errors on moto's site for unlocked, not eligible, is it because it's to new?
Eatspizza
Click to expand...
Click to collapse
It may take 14 days for oem unlocking to be available.
Edit: It should only 3 days for oem unlock to be available after connecting wifi or carrier.
Thank you - I'll give it a go in 24hrs or so
Do you know if any roms off hand are available for my version of stylus? Seems to be different processor then other stylus
eatspizza said:
Thank you - I'll give it a go in 24hrs or so
Click to expand...
Click to collapse
Sorry, it usually only takes 72 hours for oem unlock to work, but the device needs to connect to wifi or carrier.
Which cid does the device have?
Code:
fastboot getvar all
Look for this line
Code:
(bootloader) cid:
sd_shadow said:
Sorry, it usually only takes 72 hours for oem unlock to work, but the device needs to connect to wifi or carrier.
Which did does the device have?
Code:
fastboot getvar all
Look for this line
Code:
(bootloader) cid:
Click to expand...
Click to collapse
Right now, It's on WiFi and I got it on MetroPCS network.
Not even 5hrs since I got it online through metro and my home wireless.
I'll check it in 72hrs and let you know if it doesn't work
It is a pretty nice phone for $400! Great internal storage, 256GB though I got 256GB sd card and 6gb ram, 2 more then my G7
sd_shadow said:
Sorry, it usually only takes 72 hours for oem unlock to work, but the device needs to connect to wifi or carrier.
Which cid does the device have?
Code:
fastboot getvar all
Look for this line
Code:
(bootloader) cid:
Click to expand...
Click to collapse
72 hours passed but still cannot unlock
Here is the cid from bootloader you mentioned in earlier post
(bootloader) cid: 0x0032
eatspizza said:
72 hours passed but still cannot unlock
Here is the cid from bootloader you mentioned in earlier post
(bootloader) cid: 0x0032
Click to expand...
Click to collapse
Cid should be good,
You could try a factory reset, and reconnect to internet.
Or contact Motorola
sd_shadow said:
Cid should be good,
You could try a factory reset, and reconnect to internet.
Or contact Motorola
Click to expand...
Click to collapse
Thanks - I've posted in there forum and will see what they say.
My G7 was also cid 32 and could unlock after 72hrs so we'll see about this one soon enough
sd_shadow said:
Cid should be good,
You could try a factory reset, and reconnect to internet.
Or contact Motorola
Click to expand...
Click to collapse
OEM Unlocked now - so to find some ROMs
eatspizza said:
OEM Unlocked now - so to find some ROMs
Click to expand...
Click to collapse
Good, did you factory reset?
sd_shadow said:
Good, did you factory reset?
Click to expand...
Click to collapse
I had not - I randomly checked the oem lock in developer options and it was available so i did the bootloader unlock.
Also got it rooted by getting the boot img file from LMSA and patching with magisk then running the patched boot in bootloader.
No ROMs seen at this moment to try/test.
Same boat, hopefully we get some roms soon.
This is the subsection for the 5G (XT2131-1, and probably a few more) version of the Moto G Stylus 2021, make sure to keep an eye in both subsections.
eatspizza said:
Is this variant to new for rebooting? XT2131-1 bought from bestbuy w/o activation so it's supposed to be unlocked for carrie
I was able to use it on metro/tmoble without issue but cannot seem to get the bootloader unlocked, grayed out
Errors on moto's site for unlocked, not eligible, is it because it's to new?
Eatspizza
Click to expand...
Click to collapse
I'm having the same issue
I wanted to help someone whose phone wouldn't boot into the system after bootloader locking back, phone hangs on a red warning. And in the process of experimenting myself got confused and got into the same situation. Unlocking the bootloader again is not working:
Code:
C:\adb>fastboot oem unlock AX4XQ...................
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
Such cases are frequent and I knew about it. But I got in this trouble myself.
Does anybody know what can be done in this situation?
I understand that it may be hopeless, but maybe there are some devices that can flash the phone in this situation?
ilia3367 said:
I wanted to help someone whose phone wouldn't boot into the system after bootloader locking back, phone hangs on a red warning. And in the process of experimenting myself got confused and got into the same situation. Unlocking the bootloader again is not working:
Code:
C:\adb>fastboot oem unlock UNIQUE_KEY
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
Such cases are frequent and I knew about it. But I got in this trouble myself.
Does anybody know what can be done in this situation?
I understand that it may be hopeless, but maybe there are some devices that can flash the phone in this situation?
Click to expand...
Click to collapse
What does getvar all say?
Remove the IMEI line before posting.
Code:
fastboot getvar all
Are you interested in this?
(bootloader) securestate: flashing_locked
ilia3367 said:
Edit: Removed by request
Click to expand...
Click to collapse
First thing I would do is try to unlock the bootloader.
If you still have the unlock code from Motorola, try it.
I have good news. My friend restored my phone!
ilia3367 said:
I have good news. My friend restored my phone!
Click to expand...
Click to collapse
How???
dfert said:
How???
Click to expand...
Click to collapse
Neehow!!!
ilia3367 said:
I have good news. My friend restored my phone!
Click to expand...
Click to collapse
Hello, how did it happen to you and how do I solve it? Can you tell it for future cases? Thanks a lot
Unfortunately, there is no way to restore this.
If the securestate= oem_locked then you can reflash the same firmware but
securestate= flashing_locked is a dead end
Hopefully you find a way.
psbhadola said:
Unfortunately, there is no way to restore this.
securestate: flashing_locked is a dead end...
Click to expand...
Click to collapse
It turned out that it was not! It is possible to make the device operable again, return it to securestate: oem_locked.
This requires someone who has access to Motorola's servers and has knowledge in these matters. Everything is done via remote access.
That's great news. Can you share the steps. Maybe your friend can assist.
I can't give you coordinates my comrade's without the his consent. If you really have such a situation, then we will have a substantive conversation.
At least those are not the topics to be discussed here.
We need paid and illegal tools and methods like XiaomiTool and qUnlock Tool.
Most people are not interested in such things.
PEACH-PIT said:
XiaomiTool and qUnlock Tool.
Click to expand...
Click to collapse
No such programs are needed. I wrote above how it was fixed.
I consider the issue closed.
ilia3367 said:
I can't give you coordinates my comrade's without the his consent. If you really have such a situation, then we will have a substantive conversation.
Click to expand...
Click to collapse
Yes. I have the same issue. My phone is flashing_locked and unusable.
ilia3367 said:
No such programs are needed. I wrote above how it was fixed.
I consider the issue closed.
Click to expand...
Click to collapse
Please do not close this issue, we, many people need the step by step method to resolve the lock-back problem.
Please consult with your friend and issue the step, thanks!
I informed my comrade of your requests. If he considers it possible, he will respond himself.
I can help you all, only after that re-unlocking the bootloader is not possible. but, after my actions, you will receive oem_lock and the ability to install any off-firmware on your device, regardless of the region. Write to private messages.
Please..help
I am trying to unlock my nord ce 2 bootloader but everytime I try to access bootloader mode, it says something like Unlock_Verify_device ok and then reboots
how can I unlock the bootloader? Same happens on my nord 2. Oem unlocking is enabled and I have no selection of advanched startup options. I have magisk boot.img to flash
Can't say I experienced that myself. The message you got looks promising. The 'unlock_verify_device ok' message means you're getting to fastboot. But I'm not sure why it's rebooting. Do you have enough time to run the command 'fastboot devices'?
Also, what version is your firmware?
Here is the guide I used when I was unlocking the bootloader: https://www.droidwin.com/how-to-unlock-bootloader-on-oneplus-nord-ce-2/
I am running android 12 beta on oxygenos
Edit: fastboot doesn´t even find the device
Oh, now it tells that serial is not match. what's going on?
so? Can anyone help? Phone keeps saying that serial is not match and then reboots. Is this phone just a joke or something? Gonna buy samsung if yes.
What model is your phone? I wasn't aware of the Android 12 beta being available for the Nord CE 2. Another thing to try is this tutorial to manually install the OnePlus drivers: https://www.droidwin.com/fix-android-device-not-showing-in-fastboot-mode/
Was looking on the nord ce 1 xda Forum. It's only recently that a few roms and twrp are starting to appear, so there is hope. IMO oneplus need to take £$50 off the price, more users = more chance of getting more development
mr_munch said:
Can't say I experienced that myself. The message you got looks promising. The 'unlock_verify_device ok' message means you're getting to fastboot. But I'm not sure why it's rebooting. Do you have enough time to run the command 'fastboot devices'?
Also, what version is your firmware?
Here is the guide I used when I was unlocking the bootloader: https://www.droidwin.com/how-to-unlock-bootloader-on-oneplus-nord-ce-2/
Click to expand...
Click to collapse
I don't have fastboot on my device Nord ce 2 ..when I type fastboot reboot bootloader then it directly reboot into my device ..Please somebody help me.Im on current Android 12.1 version
neilop7 said:
I don't have fastboot on my device Nord ce 2 ..when I type fastboot reboot bootloader then it directly reboot into my device ..Please somebody help me.Im on current Android 12.1 version
Click to expand...
Click to collapse
Fastboot is stuffed on this device. There's no longer a way to make fastboot work.
burningcreation said:
Fastboot is stuffed on this device. There's no longer a way to make fastboot work.
Click to expand...
Click to collapse
I wanna unlock bootloader..is there any way to unlock ?
neilop7 said:
I wanna unlock bootloader..is there any way to unlock ?
Click to expand...
Click to collapse
No unfortunately.
burningcreation said:
No unfortunately.
Click to expand...
Click to collapse
Did you able to unlock bootloader?
neilop7 said:
Did you able to unlock bootloader?
Click to expand...
Click to collapse
No I am not able to unlock the bootloader either. There is currently nothing we can do.
Hi everyone, any update on this? Did someone manage to unlock the bootloader?
If I'm not mistaken. You can rollback to android 11 to get it back.
I'm currently facing the same problem, so I tried rolling back and have downloaded over 20 rollback zips now, and extracted them. All won't work, it reboots in recovery. And it is like fastboot just doesn't exist. So yeah they probably messed it up.
I'm so sad, I switched from Iphone to Oneplus partly because of the rooting options. So sad
Can I do this trough adb or not?
NiekKamer0105 said:
I'm currently facing the same problem, so I tried rolling back and have downloaded over 20 rollback zips now, and extracted them. All won't work, it reboots in recovery. And it is like fastboot just doesn't exist. So yeah they probably messed it up.
I'm so sad, I switched from Iphone to Oneplus partly because of the rooting options. So sad
Can I do this trough adb or not?
Click to expand...
Click to collapse
You don't extract it though. You just rename it by removing the _Rollback at the end.
See here: https://droidwin.com/downgrade-oneplus-nord-ce-2-from-android-12-to-android-11/
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.
you guys knows what that means. I can't get it to do anything. Can't use any of the tools. Flash permission denied on everything. Even the Motorola rescue assistant tool doesn't support the device. Does anyone have any recommendations? All I can boot to is a locked Bootloader mode
Can you unlock the bootloader again?
V0latyle said:
Can you unlock the bootloader again?
Click to expand...
Click to collapse
Nope. OEM unlock is not turned on in settings. neither is USB debugging.
So you're saying you locked the bootloader on custom firmware, and while Android still runs, you can't unlock it again?
This is why you should NEVER lock the bootloader on custom firmware.
brd912 said:
Nope. OEM unlock is not turned on in settings. neither is USB debugging.
Click to expand...
Click to collapse
What possessed your faculties to make you lock your bootloader after the hassle it can be to get them to let you unlock in the first place?
V0latyle said:
So you're saying you locked the bootloader on custom firmware, and while Android still runs, you can't unlock it again?
This is why you should NEVER lock the bootloader on custom firmware.
Click to expand...
Click to collapse
Exactly what I'm saying. I was drinking. got angry at certain bugs it had after rooting and well here we are. I can't even find any info on test points for edl on this model. It's just a $40 phone but it's the ONLY phone I have.
brd912 said:
I was drinking.
Click to expand...
Click to collapse
'nuff said... i feel that pain
brd912 said:
Exactly what I'm saying. I was drinking. got angry at certain bugs it had after rooting and well here we are. I can't even find any info on test points for edl on this model. It's just a $40 phone but it's the ONLY phone I have.
Click to expand...
Click to collapse
Sorry to hear that. If you're unable to unlock the bootloader with fastboot commands, I don't think there's anything you can do. I assume you don't have root?
you try and EDL cable yet? if you don't have one you can make one by stripping back a bit of insulation and shorting the black and green together with the device off, then at the same time click all three buttons 3-4 times until you see the 9008 port show up in device monitor (WINDOWS)
if that fails and you're feeling brave (or you have really good anti-virus software) you could always give something like this a shot
Download Fastboot to Edl tool 2022 Android 11 – 12
Download Fastboot to Edl tool 2022 Android 11 - 12 Download Fastboot to Edl tool 2022 Android 11 - 12
vocdienthoai.com