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.
Related
I can't find anything definitive about whether it's rootable or not
Same here i tried every root app possible and failed.
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
No need to flash TWRP: Booting into it is sufficient.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
How did you unlock the bootloader?
sCriptKittY1987 said:
How did you unlock the bootloader?
Click to expand...
Click to collapse
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
Where did you find a tarp img for the LG k51?
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
tarp image????? just follow the tutorial.
I meant TWRP recovery . After you've unlocked the bootloader where did you get a custom recovery to flash for the LG k51. From what I saw on Team Wins website, there isn't one.
Bhanu8082 said:
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Click to expand...
Click to collapse
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
sCriptKittY1987 said:
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
Click to expand...
Click to collapse
I doubt that's going to work, but let me know if it does. Carriers and manufacturers use a variety of sophisticated security schemes like requiring lengthy codes that only they can provide, etc to purposely make it very difficult to unlock bootloaders. Tmobile gave me a K51 for free. They apparently feel the have to pay for it by spying on me. I bought a moto g7 plus unlocked for $117 directly from Moto and put Lineage on it, no gapps Would love to use thie k51 though if anyone figures it out because it's more waterproof and bigger battery.
mgsgta3 said:
I can't find anything definitive about whether it's rootable or not
Click to expand...
Click to collapse
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
and let me guess my doofus luck im guessing no way to unlock it with out a P.C. like nuttin at all?
Absolutely no of the crap above works at all in any capacity especially sprint. Generic postings like hold volume down and power also doesn't work to go into fastboot so if you guys are following the advice of some of these guys don't because you'll drop more money on a new phone then you will unlocking it some variants verizon is one I think you have to call LG I know I spent 6 hrs on the phone with "tech support" aka "jokes with a screen to read from" to FINALLY get into touch with an engineer who told me the only way "NOW" to unlocked the bootloader is in his office which means it has to be depot to be unlocked which as of this moment lg is not doing that WILL change in the future that was 12/03/2020. Even running external adb with kali linux to hack it broke the bootloader and sends you into an infinite reboot loop
jwoegerbauer said:
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
This returns no value on a locked bootloader because even with Dev. Opt. Enables its still read only until bootloader is unlocked this is verified on two carriers k51's sprint and att. However it is unlockable we haven't found it and/or LG has not added this service to their site which is where you will get the info needed for the unlocked.
Oh my. You know you need to do all this from a computer, right? Can't do it in an Android terminal because fastboot commands are only valid in a phone's bootloader environment. And if you didnt know that then rooting and all of the dangers that come with it just isnt for you. But yes, it's rootable. So here you go anyway.
Reboot the phone to download mode.
Install LG's K51 usb drivers, and install adb and fastboot, on your computer.
Open a command prompt and type: fastboot oem unlock
If it does anything other than pat you on the back and tell you it's proud of you and how well you follow instructions, then go back and follow the effing instructions.
Otherwise, type: fastboot reboot.
Download magisk manager.
Do the magisk manager.
Use the LG flash tool on your computer to flash what you just did when you did the magisk manager.
And presto, you're rooted. Or I successfully left out enough info and you dont know how to use Google, leaving your device still not rooted. And thank god for that.
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Kenwoodquality69 said:
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Click to expand...
Click to collapse
Yo Ken,
So your K51 rooted?
If so, maybe you could provide a step by step?
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
TexasPride said:
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
Click to expand...
Click to collapse
O lord i hope this isnt true
so, i was following the guide for the bootloader unlocking process and succeeded. rooting process is what bricked my phone, unfortunately.
i loaded the patched magisk image in to boot_a like it said, and hoping that everything would have went well, it did not.
now phone will not boot. recovery modeis broken. adb does not recognize my device, and i have no clue how to get to edl mode from there.
as far as im aware, there is no kdz for the lg v50 sprint variant. (v450) unfortunately.
can anyone help me?
i feel like im SOL
It's not my main phone, but I really like the cameras on it. Was just looking to rid it of lgs software.
Which abl you used to unlock?The one provides for LG G8 is untested for sprint V50,it's highly you missed something,you need get into the abl's fastboot mode to flash back the original kernel
@Vortex said:
Which abl you used to unlock?The one provides for LG G8 is untested for sprint V50,it's highly you missed something,you need get into the abl's fastboot mode to flash back the original kernel
Click to expand...
Click to collapse
It boots into fastboot as soon as it boots up. So there's hope. Adb just doesn't recognize my phone. The thread said it worked, and everyone else who had the sprint v50 said it worked. So I don't know what went wrong
I didn't use the file for the g8.
Beefybeardedbear said:
It boots into fastboot as soon as it boots up. So there's hope. Adb just doesn't recognize my phone. The thread said it worked, and everyone else who had the sprint v50 said it worked. So I don't know what went wrong
Click to expand...
Click to collapse
Where is the thread?I didn't see any talked about V50,only G8's,the adb will not recognize because it's fastboot mode,you need the fastboot.exe to do further operations,not the adb
@Vortex said:
Where is the thread?I didn't see any talked about V50,only G8's,the adb will not recognize because it's fastboot mode,you need the fastboot.exe to do further operations,not the adb
Click to expand...
Click to collapse
,
Ah, I see. I have the fastboot.exe in my platform tools folder.
The link is https://forum.xda-developers.com/t/...YteGJNSWxEZlhydFpfWm9telNEbUhFZ1pFQlJ6amZORlg.
Beefybeardedbear said:
,
Ah, I see. I have the fastboot.exe in my platform tools folder.
The link is https://forum.xda-developers.com/t/...YteGJNSWxEZlhydFpfWm9telNEbUhFZ1pFQlJ6amZORlg.
Click to expand...
Click to collapse
Good it seems using the rencently appeared lge programmer with G8X ES abl,are you get original phone from sprint ?It's unlocked someway more violent before for sprint model.Have you flashed the abl back?I suggest you follow the bootloader unlock section carefully https://bbs.lge.fun/thread-121.htm
@Vortex said:
Good it seems using the rencently appeared lge programmer with G8X ES abl,are you get original phone from sprint ?It's unlocked someway more violent before for sprint model.Have you flashed the abl back?I suggest you follow the bootloader unlock section carefully https://bbs.lge.fun/thread-121.htm
Click to expand...
Click to collapse
I haven't as I am at work, currently. I will try once I am back home. I mean, it seems as easy as just flashing stock boot_a.bin to the boot partition, right? Or am I wrong?
Beefybeardedbear said:
I haven't as I am at work, currently. I will try once I am back home. I mean, it seems as easy as just flashing stock boot_a.bin to the boot partition, right? Or am I wrong?
Click to expand...
Click to collapse
Yes,just patched the ramdisk file is not enough,you have to deal with dmverity or something else,the root aquirement on android had became much more complex than the early days because the damn google always try to block this routine,even the SuperSu had gave up fighting
@Vortex said:
Yes,just patched the ramdisk file is not enough,you have to deal with dmverity or something else,the root aquirement on android had became much more complex than the early days because the damn google always try to block this routine,even the SuperSu had gave up fighting
Click to expand...
Click to collapse
yeah, i know. back in the old days, there were even apps like king root to give you root permission. damn google acts like we cant just have freedom. they are starting to act like apple now
Beefybeardedbear said:
yeah, i know. back in the old days, there were even apps like king root to give you root permission. damn google acts like we cant just have freedom. they are starting to act like apple now
Click to expand...
Click to collapse
I sincerely suggest you buying some Chinese ODM 5G phones instead of these hell-like phones,It's all carrier unlocked and free to flash with the same Snapdragon Platform like oneplus Xiaomi.
@Vortex said:
I sincerely suggest you buying some Chinese ODM 5G phones instead of these hell-like phones,It's all carrier unlocked and free to flash with the same Snapdragon Platform like oneplus Xiaomi.
Click to expand...
Click to collapse
well xiaomi and all those other brands are banned. i have a oneplus 6t for when i want to flash and customize.
Beefybeardedbear said:
well xiaomi and all those other brands are banned. i have a oneplus 6t for when i want to flash and customize.
Click to expand...
Click to collapse
i also have oneplus 8. but bootloader is locked unless i get my phone sim unlocked. but thats after i pay off the phone
You just need to find a V50 Sprint device from another user or your friend, then backup all partitions, back them up, then flash to your device.
Note: ignore imei partitions
How would I flash it? Through fastboot and adb? I've already found one.
hello?
You flash them through fastboot by giving the following command:
fasboot [file name i.e abl_a] [file location]
Alternatively if you can go back to EDL/QFIL/9008 mode, you can load through the software
Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?
geee0h said:
Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?
Click to expand...
Click to collapse
Unfortunately, I haven't even tried. And I've given up. Going to chinese brands now. They are way easier to root and rom. Like oneplus and xiaomi. You could try the method above that a member mentioned.
geee0h said:
Just bricked my LG v50 450pm. following the unlock guide, im a potato and missed a step in my haste. phone only boots into bootloader, no recovery, and i am not sure if adb is recognizing the phone... any magic tricks to help ?
Click to expand...
Click to collapse
Get KDZ Tools
unzip the kdz
look for abl_a.img abl_b.img laf_a.img laf_b.img xbl_a.img xbl_b.img xbl_config_a.img xbl_config_b.img
flash it on fastboot. If you have follow the guide to unlock, you should have backed up all these files.
hope this helps.
Hello,
I am trying to convert Tmobile OP9 to Global version and I am stuck at a basic step of getting the oem unlock code when trying to unlock the bootloader.
Details:
1. got my network unlocked from mobbdeep couple of weeks back.
2. Under Settings > "Network Unlock" status shows as unlocked
3. Installed the latest SDK as I am following the guide here to get the bootloader unlocked. When I boot in fastmode and run the oem command it stays at "waiting for device" and returns nothing.
Code:
fastboot oem get_unlock_code
When I run this, device list shows empty
Code:
adb devices
- Enabled USB debugging and stay awake options is checked from what I read on few posts
- When I restart the phone normally and then run "adb devices" it shows my phone listed
- Working on windows machine
What am I doing wrong here ?
TIA !!
PS: attached image shows the device state as Locked
If your phone is SIM unlocked, follow the instructions to convert from T-Mo to global.
Then you'll have the normal OEM unlock in dev options. Then you can just do the fastboot oem unlock and call it good.
Much easier and you don't have to deal with the token. It worked well for me.
I have the global version, not TMobile, so this might not apply
But I had a similar issue with fastboot not recognizing my device, the solution is disabling driver signing in windows and manually updating the driver in device manager
Check the "root OnePlus9" thread.. on page 8 at the bottom there's a guide on how to do it
Superguy said:
If your phone is SIM unlocked, follow the instructions to convert from T-Mo to global.
Then you'll have the normal OEM unlock in dev options. Then you can just do the fastboot oem unlock and call it good.
Much easier and you don't have to deal with the token. It worked well for me.
Click to expand...
Click to collapse
Thanks for your response.
I tried that earlier assuming the same but it asked me to first flash the unlock token for which I am following the steps
I was however able to get the device listed after manually uninstalling/installing adb drivers
avid_droid said:
Check in device manager. If you have the yellow triangle on your phone in device manager just download android composite driver and update it through device manager/browse computer/ select unzipped folder and click OK.
Might be the issue
Click to expand...
Click to collapse
That was indeed the issue. I manually uninstalled and installed the drivers which helped and I can now see the device listed and also got the oem unlock code successfully.
I have submitted the form with Tmobile for the unlock token, hopefully that should do it.
Thanks !
This thread was helpful as well. Thanks !
cass89 said:
I have the global version, not TMobile, so this might not apply
But I had a similar issue with fastboot not recognizing my device, the solution is disabling driver signing in windows and manually updating the driver in device manager
Check the "root OnePlus9" thread.. on page 8 at the bottom there's a guide on how to do it
Click to expand...
Click to collapse
This thread was helpful as well. Thanks !
avid_droid said:
If going for root and conversion,don't forget to use partitions manager to back up persist.img and modemst1,modemst2.
Can't stress that enough. This is my second oneplus device messed up in a 3 week time period
Click to expand...
Click to collapse
I will definitely.
I remember doing the same process for OP6T. Some users had mentioned about the issues surfacing and that helped o go back to stock
That reminds, like 6T are there any known issues post converting ?
I remember play services weren't functioning fine as well as there was no google pay. My corporate apps also didnt install due to missing security certificates.
Same applies for OP9 as well ?
FRNK8 said:
I will definitely.
I remember doing the same process for OP6T. Some users had mentioned about the issues surfacing and that helped o go back to stock
That reminds, like 6T are there any known issues post converting ?
I remember play services weren't functioning fine as well as there was no google pay. My corporate apps also didnt install due to missing security certificates.
Same applies for OP9 as well ?
Click to expand...
Click to collapse
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
craznazn said:
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
Click to expand...
Click to collapse
Hey thanks for the heads up. I will
Would infact first go through the conversion steps to go back to Tmo just incase things go south.
avid_droid said:
If going for root and conversion,don't forget to use partitions manager to back up persist.img and modemst1,modemst2.
Can't stress that enough. This is my second oneplus device messed up in a 3 week time period
Click to expand...
Click to collapse
craznazn said:
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
Click to expand...
Click to collapse
Following the guide here, I just performed the bootloader unlock successfully. Per your suggestion, I want to backup the modem files before I proceed any further.
I cant seem to recollect how do I backup the modem files when I did the same conversion for OP6T. Can you please guide me here before I proceed with the next steps.
I tried installing the partitions backup but it wont allow me without root. I vaguely remember that I hadn't rooted my device the last time while backing up these files or is root needed ?
TIA !
You need to root. Rooting is fine and won't affect your modem. While you are there, back up persist, modemst1, modemst2, modem_a, and modem_b. _a and _b should be different versions and you can pick and choose which one you might want to use (or stick with AA)
craznazn said:
You need to root. Rooting is fine and won't affect your modem. While you are there, back up persist, modemst1, modemst2, modem_a, and modem_b. _a and _b should be different versions and you can pick and choose which one you might want to use (or stick with AA)
Click to expand...
Click to collapse
Can you help me with the steps to root ? Just want to be careful while doing so.
I saw some posts but that was related to the Tmobile OP9Pro(in my case its its Tmo Op9). The boot images were different so I didnt try to play around.
Thanks !
Just try to fastboot boot a magisk patched img and see if it works.
Try https://forum.xda-developers.com/t/root-oneplus-9.4253651/
Don't flash anything, just go to fastboot
Code:
fastboot boot patched_boot.img
craznazn said:
Just try to fastboot boot a magisk patched img and see if it works.
Try https://forum.xda-developers.com/t/root-oneplus-9.4253651/
Don't flash anything, just go to fastboot
Code:
fastboot boot patched_boot.img
Click to expand...
Click to collapse
Okay did this step.
Downloaded an copied stock image and the boot_patched image provided on the link and copied to my phones internal storage
Also as next step said, rebooted the phone
- went to Magisk app > install > selected boot_patched.img from internal storage
- phone restarted
- When I open the partitions backup app it still shows "device is not rooted" warning
What step did I miss ?
FRNK8 said:
That was indeed the issue. I manually uninstalled and installed the drivers which helped and I can now see the device listed and also got the oem unlock code successfully.
I have submitted the form with Tmobile for the unlock token, hopefully that should do it.
Thanks !
Click to expand...
Click to collapse
do you have a link for the driver I'm having the same problem
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/
Ive looked for hours for a way to do this myself and i keep coming up short. Ive tried using fastboot method and it wont work. Its got a qualcomm chipset. A couple guides that i did find used using fastboot commands but they didnt work and i cant find anything else so far. The tablet is carrier unlocked to the best of my knowledge. Please guys if anyone could point me in the right direction i have no problem with doing the work i just need a nudge or even a possible solution if anyone can help. Thanks in advance for your time and attention to hear me out and for any help you could give.
ronnieshane1 said:
Ive looked for hours for a way to do this myself and i keep coming up short. Ive tried using fastboot method and it wont work. Its got a qualcomm chipset. A couple guides that i did find used using fastboot commands but they didnt work and i cant find anything else so far. The tablet is carrier unlocked to the best of my knowledge. Please guys if anyone could point me in the right direction i have no problem with doing the work i just need a nudge or even a possible solution if anyone can help. Thanks in advance for your time and attention to hear me out and for any help you could give.
Click to expand...
Click to collapse
First of all you have to mention the information about your device like device name,android version then we can help your
the_arxyn said:
First of all you have to mention the information about your device like device name,android version then we can help your
Click to expand...
Click to collapse
I thought I did when I created the post.im not used to posting on here and must have done it wrong sorry. It's a Blu M8L 2002 tablet running M0220WW firmware on Android 11. It has a Qualcomm chipset and I believe it is unlocked USA version
ronnieshane1 said:
I thought I did when I created the post.im not used to posting on here and must have done it wrong sorry. It's a Blu M8L 2002 tablet running M0220WW firmware on Android 11. It has a Qualcomm chipset and I believe it is unlocked USA version
Click to expand...
Click to collapse
Sorry my mistake not noticed in the title
You can follow this website https://www.google.com/url?sa=t&sou...oQFnoECA4QAQ&usg=AOvVaw2D0-geZL-AyAdYhvITs7nj
If it doesn't work show the error message
the_arxyn said:
Sorry my mistake not noticed in the title
You can follow this website https://www.google.com/url?sa=t&sou...oQFnoECA4QAQ&usg=AOvVaw2D0-geZL-AyAdYhvITs7nj
If it doesn't work show the error message
Click to expand...
Click to collapse
That's one of the guides that I mentioned that I tried. After using both unlock commands the response was FAILED (remote: unknown cmd.) I tried to use the fastboot OEM device-info command and got the same response
Tablet's OS is Android 11 GO, it got released 2020.
Is "OEM Unlock" option provided in Developer Settings? if so have you turned it on and afterwards rebooted the tablet?
Have you installed the Fastboot driver that's suitable to tablet?
If Fastboot returns "FAILED: (remote: unknown cmd.) " then Fastboot is obviously not supported.
the_arxyn said:
Sorry my mistake not noticed in the title
You can follow this website https://www.google.com/url?sa=t&sou...oQFnoECA4QAQ&usg=AOvVaw2D0-geZL-AyAdYhvITs7nj
If it doesn't work show the error message
Click to expand...
Click to collapse
That's one of the guides that I mentioned that I tried. After using both unlock commands the response was FAILED (remote: unknown cmd.) I tried to use the fastboot OEM device.
jwoegerbauer said:
Tablet's OS is Android 11 GO, it got released 2020.
Is "OEM Unlock" option provided in Developer Settings? if so have you turned it on and afterwards rebooted the tablet?
Have you installed the Fastboot driver that's suitable to tablet?
If Fastboot returns "FAILED: (remote: unknown cmd.) " then Fastboot is obviously not supported.
Click to expand...
Click to collapse
I realized i had my command line in the wrong place and i corrected it and now the commands are recognized but they are still failing. I do have the oem unlock option turned to unlock and im using the adb and fastboot quick setup from xda to use on my computer. I honestly cant figure out where im going wrong this time. Ive used adb and fastboot commands before. Im no expert but im not totally green either. Still thank you guys for attempting to help me out. It really is appreciated
jwoegerbauer said:
Tablet's OS is Android 11 GO, it got released 2020.
Is "OEM Unlock" option provided in Developer Settings? if so have you turned it on and afterwards rebooted the tablet?
Have you installed the Fastboot driver that's suitable to tablet?
If Fastboot returns "FAILED: (remote: unknown cmd.) " then Fastboot is obviously not supported.
Click to expand...
Click to collapse
I may have the wrong driver. As soon as i get back home ill try the one from the link you gave me and post my result. Thanks again
@ronnieshane1 Did you ever figure this out, I'm about to dive in and figured I'd see if there is an update before so?
No I finally just gave up. Sorry
Jacob_dillon said:
@ronnieshane1 Did you ever figure this out, I'm about to dive in and figured I'd see if there is an update before so?
Click to expand...
Click to collapse
Are you talking about the M8L 2022? I've unlocked the bootloader but can't get it back to recovery and its FRP locked so i can't use ADB. ugh.
Also, its a Unisoc chip I think.
You have to use a modified fastboot and get the identifier token.
r1pp3d2 said:
You have to use a modified fastboot and get the identifier token.
Click to expand...
Click to collapse
How do you do that?
Damonkg1 said:
How do you do that?
Click to expand...
Click to collapse
Look up modified fastboot for spreadrum devices. There is also a guide on hovatek forum.
For anyone and everyone who has had any trouble locating the firmware files (.pac) for the 2022 BLU M8L tablet, I FINALLY, after more than a month of searching found them on needrom.
Link is: https://www.needrom.com/download/blu-m8l-2022-m0220w/
Since idk if the link will be redacted or edited out, you can also google needrom and M0220WW
Be carefull when downloading the fireware for the M8L and pay close attention to the version your needing. From all that I gathered, there are mutiple versions...M0170WW, M0171WW, M0173WW, M0174WW, and the one I have that I have yet to find anywhere on the net. Its the most recent ..the M0176UU. If anyone happens to have this version, please make a full backup image and post it here. Thank you