Related
Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ??
This methode work with So Flashtool ?
I'm going to make SPflashTool working. I have some issue
Riadh300 said:
Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ?
Click to expand...
Click to collapse
Thanks for your enthusiasm but my method does not Unlock the bootloader so you should change your thread title.
As I told you I will open a thread when the method is fully tested by a few advanced user's who are testing it now and you will be given full credit for all your help.
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.
bigrammy said:
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.
Click to expand...
Click to collapse
Thanks for this informations ! ?
Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
Actually, spflashtool bypasses the bootloader in this instance, so the bootloader is untouched and you still flash twrp
---------- Post added at 08:35 AM ---------- Previous post was at 08:02 AM ----------
bigrammy said:
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.
Click to expand...
Click to collapse
Not to be pessimistic, but you do realise that even with all your precautions,people will still not read properly and will still brick their phones, no matter how many precautions you take. Even if you had an app that requires you to click one button to do everything,there are still people who will do it wrong. That said I think I know of one or 2 people in this Nokia 3 forum who were able to recover their phones using spflashtool AFTER the phone couldn't even be detected by their pc, even OST flashing was not possible .
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD
redweaver said:
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD
Click to expand...
Click to collapse
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).
bigrammy said:
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).
Click to expand...
Click to collapse
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it
bigrammy said:
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it
Click to expand...
Click to collapse
So how did you get your phone back anyway?
redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
redweaver said:
So how did you get your phone back anyway?
Click to expand...
Click to collapse
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.
SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
OK, one thing though, before flashing the recovery you might want to do a backup of the stock recovery if you don't already have one. That's what I did, so after I got root, flashed back my stock recovery. Magisk is the root manager ,
---------- Post added at 12:17 PM ---------- Previous post was at 12:12 PM ----------
bigrammy said:
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.
Click to expand...
Click to collapse
oh you mean you went through hoops to get your phone back? I thought you would say you got a stock recovery somewhere and flashed using spflashtool or used the ost method. I didn't actually expect you to outline the steps you used. BTW, first time I flashed twrp AFTER unlocking bootloader, I got stuck in a recovery bootloop too. I had to flash my phone with OST then retry the process again.
One other thing, I think OST is actually a propriety software that is supposed to work for lots of phones, at least I know that users of other non mediatek Nokia phones also use it to recover their phones (with the corresponding stock images of course)
SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
Magisk hide allows you get OTA's see the Magisk thread and yes it will work on any android version.
@redweaver
I am glad you got out of the loop but your clearly a more advanced user hence why I ask you to test. :good:
The OST is very convoluted for use on MediaTek devices and is very unnecessary it also requires unnecessary FIH software to be installed on the phone to work properly.
They likely choose this method to work across different SoC's but it's not what MediaTek use SPFlashTool is MediaTeks own software.
EDIT: Sorry lost internet for a while then.
I continue: Good news is I do not think they will be able to remove SPFlashTool use as it's binary on device which lives on a none volatile area ram chip or radio chip and is loaded at the factory so I doubt it can be updated via a OTA. :fingers-crossed:
Sony actually replaced this and this is the only device I have been unable to recover and even Sony were replacing the boards of bricked devices but if they had left the Mediatek binary in there it would not of been a issue as SPFlashTool would of been able to recover them. :good:
guys, old thread, i know, different device, i know, but ive been in the dark and this is what most resembles my issue.
any hints would be appreciated, read all 2 pages, can you believe it? im a very average xda enthusiast.
worries out of the way, my sincere thanks beforehand follow.
issue
carrier doesnt get in the way
oem doesnt get in the way
oem unlock toggle, check, adb debugging, you and i know the drill, no driver/cable issues
cannot for the life of me unlock bootloader, this one would take the newer command, however i tried them all ive come accross to no avail
output encourages me to unlock first, howwever not a clue is given as to how to accomplish it. this isnt the flash a file type of unlocking, either, at least not oem provided. going nuts.
go ahead and feel free to issue "advanced" directions (meaning, like your voicemail, instead of "for voicemail configurations press 8" and just "configurations 8"
spreatrum, not mtk
x120c
came with oreo go, treble enabled per getprop
i dont know what else, please
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
boxof said:
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
Click to expand...
Click to collapse
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Azev said:
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
Click to expand...
Click to collapse
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
Mackay53 said:
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Click to expand...
Click to collapse
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
boxof said:
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
Click to expand...
Click to collapse
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
Unless you have got unlock permission and linked phone to account you can't unlock.
Unlock like how you would normally - put the phone into fastboot, connect it to your PC, and run the mi unlock tool. For this to work, hopefully you have associated your device to a mi account and have met the unlock requirements ie. surpassed the waiting period. Otherwise you're out of luck as there is no other ways (that i know of) to register the device now as you can't get into the system.
As a last resort you can try opening up the back of the phone and flash new firmware using the test point if unlocking is not possible. I'm not sure how or where the testing point is located exactly, but it's a possible solution that i found while researching when my device was bricked. Good luck!
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
u say u can only access to fastboot..
How about pressing volume up and power button? can u enter in stock mi recovery with mi assistant options?
Hello, I have a Galaxy S7 G930P with what I believe is the v7 bootloader on Oreo.
I've only rooted a couple times before so I'm not super experienced but this phone is worth nothing to me so I will (and have been I think) risk bricking the phone. From what I understand this is a locked bootloader, so I cannot root it at all, or at least that's what I'm seeing. When I try flashing it with many different APs including engineering ones with multiple failures in Odin.
Depending on which files I'm attempting to flash, I either get and AUTH or a RQT CLOSE error in Odin.
The error on the phone says SW REV CHECK FAIL.
It's a little late in my timezone so my writing is probably horrendous, if you need anymore information I'll be back on in the morning to supply anything else. Thanks!
also please don't roast me, I'm new to this...
BertMcfallen said:
Hello, I have a Galaxy S7 G930A with what I believe is the v7 bootloader on Oreo.
The bootloader says "PRODUCT NAME: SM-G930P", although the marking on the back of the phone says SM-G930A.
I've only rooted a couple times before so I'm not super experienced but this phone is worth nothing to me so I will (and have been I think) risk bricking the phone. From what I understand this is a locked bootloader, so I cannot root it at all, or at least that's what I'm seeing. When I try flashing it with many different APs including engineering ones with multiple failures in Odin.
Depending on which files I'm attempting to flash, I either get and AUTH or a RQT CLOSE error in Odin.
The error on the phone says SW REV CHECK FAIL.
It's a little late in my timezone so my writing is probably horrendous, if you need anymore information I'll be back on in the morning to supply anything else. Thanks!
also please don't roast me, I'm new to this...
Click to expand...
Click to collapse
The solution to your issue would be patching your boot img in magisk in tar format and then flashing that img via odin
([emoji3590]09-09-18[emoji3590])
PoochyX said:
The solution to your issue would be patching your boot img in magisk in tar format and then flashing that img via odin
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Ah yes I've heard of magisk, I will start researching that right now. Thank you very much!
BertMcfallen said:
Ah yes I've heard of magisk, I will start researching that right now. Thank you very much!
Click to expand...
Click to collapse
Anytime
([emoji3590]09-09-18[emoji3590])
From what I've read, you can't get root on sprint and/or bootloader v7
https://forum.xda-developers.com/showpost.php?p=77655646&postcount=882
https://forum.xda-developers.com/showpost.php?p=77663944&postcount=901
https://forum.xda-developers.com/showpost.php?p=77665353&postcount=902
The only root methods for the snapdragon/USA models is by using engineering bootloaders, but you have to be on the right bootloader to flash over to the engineering bootloader, which there doesn't seem to be a v7 engineering bootloader out there
Beanvee7 said:
From what I've read, you can't get root on sprint and/or bootloader v7
https://forum.xda-developers.com/showpost.php?p=77655646&postcount=882
https://forum.xda-developers.com/showpost.php?p=77663944&postcount=901
https://forum.xda-developers.com/showpost.php?p=77665353&postcount=902
The only root methods for the snapdragon/USA models is by using engineering bootloaders, but you have to be on the right bootloader to flash over to the engineering bootloader, which there doesn't seem to be a v7 engineering bootloader out there
Click to expand...
Click to collapse
Yeah, unfortunately I am also seeing the same things elsewhere. Thanks for the help.
BertMcfallen said:
Yeah, unfortunately I am also seeing the same things elsewhere. Thanks for the help.
Click to expand...
Click to collapse
Someone with root can patch your img with magisk and you can flash it in odin and it wont work however due to the fact you have a locked bootloader i believe once you flash it in Odin you will get unauthorized binary alert and your phone won't boot
([emoji3590]09-09-18[emoji3590])
MOD Edit: check post #25#25 before you proceed.
craznazn said:
This thread was created before I made the MSM conversion, hence the confusion. Probably could be locked now.
And if the OP is still reading this, for your own good don't mess with modemst1/2/persist unless you really know what you're doing.
Click to expand...
Click to collapse
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/
Certain partitions need to be flashed from the bootloader fastboot, not fastbootd.
Either way, there is no going back to the T-Mobile firmware as there's no unbrick tool yet.
Don't do this.
lrod55 said:
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/
Click to expand...
Click to collapse
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.
inspron said:
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.
Click to expand...
Click to collapse
I should still have the boot.img I backed up from stock 11.2.2.2 (T-Mobile). I'll attach it here when I get off work
LLStarks said:
Certain partitions need to be flashed from the bootloader fastboot, not fastbootd.
Either way, there is no going back to the T-Mobile firmware as there's no unbrick tool yet.
Don't do this.
Click to expand...
Click to collapse
+1 . I myself love flashing things and have the unlocked op9. Just got in mail and unlocked and rooted this evening. I however will not be flashing anything but magisk updates till an msm tool is available for us to use.
inspron said:
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.
Click to expand...
Click to collapse
This should be the stock boot.img from the 11.2.2.2 T-Mobile build. Named it that way so as to not confuse it with stock boot image from 11.2.4.4 (EU)
boot(old).img (Google Drive link)
mattie_49 said:
+1 . I myself love flashing things and have the unlocked op9. Just got in mail and unlocked and rooted this evening. I however will not be flashing anything but magisk updates till an msm tool is available for us to use.
Click to expand...
Click to collapse
Will heed your guys' warnings. Just was super curious (and confused) as to how others were able to get it to work
Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.
jaed.43725 said:
Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.
Click to expand...
Click to collapse
You know the unlocked global version works with carrier sims. I'm on verizon . Bought the unlocked 9 popped the verizon sim in and everything works perfect. Vvm/5g everything. And unlocked to my liking
mattie_49 said:
You know the unlocked global version works with carrier sims. I'm on verizon . Bought the unlocked 9 popped the verizon sim in and everything works perfect. Vvm/5g everything. And unlocked to my liking
Click to expand...
Click to collapse
Yes, I am very aware of that. The issue is I have the T-Mobile version because I got if 1/2 off with a trade in. Will this warrant a trade after I pay it off? Maybe. But I would rather just put on Lineage OS if that becomes possible.
lrod55 said:
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/
Click to expand...
Click to collapse
you flash from bootloader (fastboot) or from fastbootd
FAILED (remote: 'Flashing is not allowed for Critical Partitions this is when you flash in fastboot
only fastbootd can flashh all partition
jaed.43725 said:
Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.
Click to expand...
Click to collapse
You know there's a specific option under the development settings called 'stay awake', right?
TheKnux said:
You know there's a specific option under the development settings called 'stay awake', right?
Click to expand...
Click to collapse
I can not select it. It is greyed out for some reason.
TheKnux said:
You know there's a specific option under the development settings called 'stay awake', right?
Click to expand...
Click to collapse
On the T-Mobile version it is not selectable.
jaed.43725 said:
On the T-Mobile version it is not selectable.
Click to expand...
Click to collapse
Yeah that's BS because I definitely selected it while I was backing up my data before I converted from T-Mobile firmware.
jaed.43725 said:
On the T-Mobile version it is not selectable.
Click to expand...
Click to collapse
I'm on t-mobile version i can select it as well. Pretty sure everything in developers options is selectable. Some don't stick for whatever reason.
Ya, I don't know what this things deal is. But as soon as I get the ability to flash to international I'm doing it.
Where is the guide for flashing a OnePlus 9 from T-Mobile to International?
Btw for everyone following this thread, its an easy to miss step, but if you follow the guides for converting, all you have to do is go into fastboot and then use command “fastboot reboot fastboot”. This apparently puts you in fastbootd (never had to use this before, I would just use commands and flash stuff from bootloader screen but whatever) where you can then flash the needed partitions. Also, no hate to the guy who posted the recent conversion thread but it is super unorganized and a little too easy to miss that step, as well as MAKE SURE you read through the .bat file they provided because it is NOT correct. They have some typos in there so it wasn’t working for me at first. It’s a pain in the ass but I highly recommend going through each command, copy/paste, and read it to make sure there’s no typos then hit enter or you will run into errors like I did. Good luck
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.