Related
I bought the rn3 couple of days ago and I was trying to unlock it with the unofficial method and I used the files included in this page
http://xiaomitips.com/guide/unlock-redmi-note-3-bootloader-without-official-permission/
After phone got unlocked I installed twrp and tried to flash 2 Roms but they both bootlooped so I tried to flash the stock firmware I got from the same page the phone booted but I noticed that WiFi and phone signal both don't work
Please point me to the right stock firmware that I can flash with edl mode because I'm not sure which version I got
I attached a picture of the box
I would really really really appreciate the help
First off all, going by your picture, you have a Special Edition "Kate" model and not a "Kenzo".
You probably need to flash an official rom again by EDL mode.
Recommend that you unlock the bootloader officially after doing the above. See the linked wiki for instructions.
Then read custom rom threads on the steps required to flash them on the "Kate" model.
corkiejp said:
First off all, going by your picture, you have a Special Edition "Kate" model and not a "Kenzo".
You probably need to flash an official rom again by EDL mode.
Recommend that you unlock the bootloader officially after doing the above. See the linked wiki for instructions.
Then read custom rom threads on the steps required to flash them on the "Kate" model.
Click to expand...
Click to collapse
Should I download the stable or developer version or is it not important?
It is easier to unlock the device on developer version, but both should work.
If you intend flashing a custom rom later, it doesn't really matter.
corkiejp said:
It is easier to unlock the device on developer version, but both should work.
If you intend flashing a custom rom later, it doesn't really matter.
Click to expand...
Click to collapse
Thank you very much I'll download the ROM and see what happens
corkiejp said:
It is easier to unlock the device on developer version, but both should work.
If you intend flashing a custom rom later, it doesn't really matter.
Click to expand...
Click to collapse
thank you very much for the help
I downloaded the special edition dev rom and it booted and everything is working correctly
I'm trying to unlock the bootloader the official way my account has permission but it keeps giving me "Couldn't verify device" at 50% I searched it and it seems to be a frequent issue do you have any idea how to fix it I logged in on my device using my phone number and did the same on the pc, I pinged my device using find my phone and I'm waiting till tomorrow to try again but I was just wondering if you know anything else?
thanks again
P.S. 2: If you failed to unlock, try only after 8-10 days, in other words don't keep trying and changing the handset's ROM.
Click to expand...
Click to collapse
Taken from this guide.
Also another guide: -
[Unlock BL] Tutorial for Successfully Unlocking Bootloader Stuck at 50% !
mshtob said:
thank you very much for the help
I downloaded the special edition dev rom and it booted and everything is working correctly
I'm trying to unlock the bootloader the official way my account has permission but it keeps giving me "Couldn't verify device" at 50% I searched it and it seems to be a frequent issue do you have any idea how to fix it I logged in on my device using my phone number and did the same on the pc, I pinged my device using find my phone and I'm waiting till tomorrow to try again but I was just wondering if you know anything else?
thanks again
Click to expand...
Click to collapse
After a failed unlock attempt, wait for atleast 3-4 days before giving another try. I also had the same issue and eventually figured this out. Do not attempt to unlock in between those 3-4 days.
jayaram95 said:
After a failed unlock attempt, wait for atleast 3-4 days before giving another try. I also had the same issue and eventually figured this out. Do not attempt to unlock in between those 3-4 days.
Click to expand...
Click to collapse
corkiejp said:
Taken from this guide.
Also another guide: -
[Unlock BL] Tutorial for Successfully Unlocking Bootloader Stuck at 50% !
Click to expand...
Click to collapse
10 days!!
is there at least a way to root the device meanwhile?
well at least there's hope
thanks a lot for the help
Looking to start a discussion on rooting the unlocked version.
I have tried the root for other variants for this phone and does not work
hi would love to see my k8+ rooted. i have the lmx210ulma version mtk and android 7.1.2.
There are recoveries for this phone and i have a full partition dump i nade today using salt on my ubuntu 18.04 machine. when i say full i mean something like 30-50 .img files pulled.
Any way. The problem on my end is booting into fastboot mode or rebooting to the bootloader. i have tried ADB, recovery and key combinations with out ever getting there. I can however get the phone to download into recovery download mode just fine.
any help would be appreciated
https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
Duhjoker said:
hi would love to see my k8+ rooted. i have the lmx210ulma version mtk and android 7.1.2.
There are recoveries for this phone and i have a full partition dump i nade today using salt on my ubuntu 18.04 machine. when i say full i mean something like 30-50 .img files pulled.
Any way. The problem on my end is booting into fastboot mode or rebooting to the bootloader. i have tried ADB, recovery and key combinations with out ever getting there. I can however get the phone to download into recovery download mode just fine.
any help would be appreciated
Click to expand...
Click to collapse
We are now in this forum. Why some dork mod moves these too early?
Why here, why not to the K8 forums instead?
The link I posted should work with your device...
Just got told to go to the k8 forums because im really just trying to get the bootloader unlocked. Temp root is nice but my plans involve a recovery and a fully rooted phone. Im trhing to develop a way to compile apps and operating systems completely on the device but i need full access.
Im looking for firmware for LG K8 2018 X210ULMG. Where can i find it ?
go to google and type in "LG K8 + LMX210ULM stock rom" you will get at least five pages or more.
Duhjoker said:
go to google and type in "LG K8 + LMX210ULM stock rom" you will get at least five pages or more.
Click to expand...
Click to collapse
I can't fin anywhere for X210ULMG. Try and when you will find paste here link because anywhere is this rom.
which android version do y0u have 9n your k8. I also need you to go to settings system software info and tell me the software versiion. And just for SandG no seriously, open up a terminal in terminal emulator and type getprop. im looking fir the value of
ro.lge.swversion_arb
to be of further assistance may i ask what exactly you are using it for? ie reflash stock fix brick or other. i can help you with the best plan of action and any other how to.
If you are still out there the ULMG and ULM are the same device. There is no ULMG stock rom. So you will need to flash your K8+ using the ULM firmware. If you are looking to roll back to get to the bootloader the lowest version you can find is a letter F version. None so far have an ARB value so happy flashing.
I myself own this device and its an easily rootable phone with bootloader unlock. Just flash the kdz with the lowest letter value then adb reboot bootloader and then in fastboot mode use fastboot oem unlock and your free to flash any cv1 device twrp recovery.img to the phone.
Just make sure to use either carliv image kitchen or android image studio to check and make sure that system, syatem.img, are both ext4 in recovery.fstab. System.img will probably be labled emmc which will cause failure to mount. Also cache and data as well. Firmware/modem should be labled as vfat. Just as if they were labled if you looked at original fstab.
To root just extract boot.img from kdz and patch using magisk and flash using fastboot flash boot boit.img then fastboot flash recovery recovery.img When booting into twrp first time flash no verity opt encrypt and make backup. Upon exiting make sure all parts are mounted or twrp loop will occur.
Duhjoker said:
If you are still out there the ULMG and ULM are the same device. There is no ULMG stock rom. So you will need to flash your K8+ using the ULM firmware. If you are looking to roll back to get to the bootloader the lowest version you can find is a letter F version. None so far have an ARB value so happy flashing.
I myself own this device and its an easily rootable phone with bootloader unlock. Just flash the kdz with the lowest letter value then adb reboot bootloader and then in fastboot mode use fastboot oem unlock and your free to flash any cv1 device twrp recovery.img to the phone.
Just make sure to use either carliv image kitchen or android image studio to check and make sure that system, syatem.img, are both ext4 in recovery.fstab. System.img will probably be labled emmc which will cause failure to mount. Also cache and data as well. Firmware/modem should be labled as vfat. Just as if they were labled if you looked at original fstab.
To root just extract boot.img from kdz and patch using magisk and flash using fastboot flash boot boit.img then fastboot flash recovery recovery.img When booting into twrp first time flash no verity opt encrypt and make backup. Upon exiting make sure all parts are mounted or twrp loop will occur.
Click to expand...
Click to collapse
I have problem because one month ago I flashed My K8 ULMG with kdz for Aristo 2 . I downloaded the software from Aristo 2 and made Brick through it.
Now it doesn't turn on, gives no sign of life, nothing. When connected to a laptop, the computer can only see Qualcomm HS-USB QDLoader 9008.
Do you know solution for it ?
There are two versions of the k8+ a qualcomm version and an mtk version. Did you read my post after your last reply. I was trying to help you determine that sort 0f thing.
As for a fix.... no as of currently there is no fix for either the qc or mtk versions once bricked. i am working on possible solutions but those are not going to be any time soon.
Your best bet at this point is to look for a used and damaged phone and replace the board in your phone with a different board. Find a k8+ lm-x210ulm or an aristo 2 board. They are cheap around $20 us and can be found with broken screens. They have no arb values so can be flashed and downgraded to get the boot loader unlocked and reflashed and upgraded after with guidance.
Dont feel to bad it happens. I have 4 boards that are trash but im still gonna try to unbrick them. But please what ever you do dont do it with out guidance. pm if you need and ill help.
Duhjoker said:
There are two versions of the k8+ a qualcomm version and an mtk version. Did you read my post after your last reply. I was trying to help you determine that sort 0f thing.
As for a fix.... no as of currently there is no fix for either the qc or mtk versions once bricked. i am working on possible solutions but those are not going to be any time soon.
Your best bet at this point is to look for a used and damaged phone and replace the board in your phone with a different board. Find a k8+ lm-x210ulm or an aristo 2 board. They are cheap around $20 us and can be found with broken screens. They have no arb values so can be flashed and downgraded to get the boot loader unlocked and reflashed and upgraded after with guidance.
Dont feel to bad it happens. I have 4 boards that are trash but im still gonna try to unbrick them. But please what ever you do dont do it with out guidance. pm if you need and ill help.
Click to expand...
Click to collapse
Did you found some method for unbrick this phone without motherboard change ?
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Arnys said:
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Click to expand...
Click to collapse
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
metalfangs said:
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
Click to expand...
Click to collapse
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that.
And more important, what was full build number for your phone, aka ane-lx3c779, something like that, can you find it? Then I maybe be able to help.
And ,wulda be great if you type down all you did with phone, what used, etc.
Arnys said:
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that..
Click to expand...
Click to collapse
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
metalfangs said:
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
Click to expand...
Click to collapse
Hm, did you tried erecovery method ? Maybe that can fix your problem
metalfangs said:
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Click to expand...
Click to collapse
Hello there brother. May I humbly ask how did you get your bootloader unlocked after downgrading? Can you share some steps please if you don't mind. Thank you
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system partition
Now my phone is stuck in fastboot and won't boot from an image, take a recovery image, etc. etc. it's kinda completely messed up and it's my fault for trying to tinker with commandline tools.
The problem is there is no MSM recovery for my phone, and even if there was virtualbox can't detect my phone's USB(I've already tried with just the nord MSM, I run linux and I was using a win10 VM)
Is there any hope? Do I have to go to a repair shop?
First post has a section specifically about the drivers you'll need to have your phone recognized in fastboot mode:
The Quest for a Bootloader Unlock (partial guide, T-Mobile variant, may work for MetroPCS/Metro variant)
OK, this process has been hell, but I'm gonna try and consolidate everything I've worked out so far in one place. This all applies only to the T-Mobile variant (ie. it comes preloaded with all the T-Mobile bloatware) of the N200 on the T-Mobile...
forum.xda-developers.com
That said, I'm pretty sure you're stuck until the MSM tool comes out (the MSM tool is different for each phone, DO NOT use one for a different OnePlus phone) to fix it yourself.
edale1 said:
First post has a section specifically about the drivers you'll need to have your phone recognized in fastboot mode:
The Quest for a Bootloader Unlock (partial guide, T-Mobile variant, may work for MetroPCS/Metro variant)
OK, this process has been hell, but I'm gonna try and consolidate everything I've worked out so far in one place. This all applies only to the T-Mobile variant (ie. it comes preloaded with all the T-Mobile bloatware) of the N200 on the T-Mobile...
forum.xda-developers.com
That said, I'm pretty sure you're stuck until the MSM tool comes out (the MSM tool is different for each phone, DO NOT use one for a different OnePlus phone) to fix it yourself.
Click to expand...
Click to collapse
Yeah I run linux, I don't need the drivers
It b what it b
Gip-Gip said:
Yeah I run linux, I don't need the drivers
It b what it b
Click to expand...
Click to collapse
Ah. Sadly, I have next to no experience with Linux outside of the tinkering I've done on my Raspberry Pis, so can't help you there.
Gip-Gip said:
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system partition
Now my phone is stuck in fastboot and won't boot from an image, take a recovery image, etc. etc. it's kinda completely messed up and it's my fault for trying to tinker with commandline tools.
The problem is there is no MSM recovery for my phone, and even if there was virtualbox can't detect my phone's USB(I've already tried with just the nord MSM, I run linux and I was using a win10 VM)
Is there any hope? Do I have to go to a repair shop?
Click to expand...
Click to collapse
My experience with USB passthrough on different hypervisors is that they all suck. I have to use Windows at work, so I use it for most of the tools including MSM tools.
That being said, I've never seen a real difference in adb / fastboot on Linux or Windows.
Have you tried calling OnePlus by chance?
SMcC2 said:
My experience with USB passthrough on different hypervisors is that they all suck. I have to use Windows at work, so I use it for most of the tools including MSM tools.
That being said, I've never seen a real difference in adb / fastboot on Linux or Windows.
Have you tried calling OnePlus by chance?
Click to expand...
Click to collapse
No, but there is a 100% chance that they'll just tell me to use their repair program. Which I'll be surprised if it's under $100 for me to mail it in, have some dude spend 5 minutes flashing it, and then mail it back
Gip-Gip said:
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system partition
Now my phone is stuck in fastboot and won't boot from an image, take a recovery image, etc. etc. it's kinda completely messed up and it's my fault for trying to tinker with commandline tools.
The problem is there is no MSM recovery for my phone, and even if there was virtualbox can't detect my phone's USB(I've already tried with just the nord MSM, I run linux and I was using a win10 VM)
Is there any hope? Do I have to go to a repair shop?
Click to expand...
Click to collapse
what exactly is messed up on your phone. i have metro ver rooted and can backup any partition img you need to flash from my stock rooted n200. do you need stock boot or recovery? if not then what do you need?
an is fastboot able to detect your phone?
PopCaps1996 said:
what exactly is messed up on your phone. i have metro ver rooted and can backup any partition img you need to flash from my stock rooted n200. do you need stock boot or recovery? if not then what do you need?
an is fastboot able to detect your phone?
Click to expand...
Click to collapse
i am not replying for the OP but i did the same thing .. fastboot sees the phone yet the bootloader is locked ... so OEM cant be unlocked using fastboot .. if i got this right .. only after oneplus releases the rom on their site this can be fixed .. Please correct me if i am wrong ...
Dimitrimem said:
i am not replying for the OP but i did the same thing .. fastboot sees the phone yet the bootloader is locked ... so OEM cant be unlocked using fastboot .. if i got this right .. only after oneplus releases the rom on their site this can be fixed .. Please correct me if i am wrong ...
Click to expand...
Click to collapse
do you have a unlock code from oneplus for you n200?
PopCaps1996 said:
do you have a unlock code from oneplus for you n200?
Click to expand...
Click to collapse
my phone was paid in full from oneplus store in US .. so i dont think i need a code
Dimitrimem said:
i am not replying for the OP but i did the same thing .. fastboot sees the phone yet the bootloader is locked ... so OEM cant be unlocked using fastboot .. if i got this right .. only after oneplus releases the rom on their site this can be fixed .. Please correct me if i am wrong ...
Click to expand...
Click to collapse
my bootloader is unlocked I just can't enter fastbootd, which is a problem
Hey there, so I managed to get a hold of the MSM tools this morning. Since I have to go out soon, I'll upload them later. Once I upload them, you should be able to unbrick your phone.
lzgmc said:
Hey there, so I managed to get a hold of the MSM tools this morning. Since I have to go out soon, I'll upload them later. Once I upload them, you should be able to unbrick your phone.
Click to expand...
Click to collapse
Excellent! This will be of so much help to many folks out here who have bricked their phones. Look forward to your sharing the tool.
Is the MSMDownload tool, that you got, for the Tmobile version or the unlocked version/retail or both?
jilebi said:
Excellent! This will be of so much help to many folks out here who have bricked their phones. Look forward to your sharing the tool.
Is the MSMDownload tool, that you got, for the Tmobile version or the unlocked version/retail or both?
Click to expand...
Click to collapse
It's for the T-Mobile version. Someone with a retail N200 will have to request a "remote session" with OP support in order to get the MSM tools for the retail version.
lzgmc said:
It's for the T-Mobile version. Someone with a retail N200 will have to request a "remote session" with OP support in order to get the MSM tools for the retail version.
Click to expand...
Click to collapse
@lzgmc, thanks.
How does this "remote session" with OP work? Does one report that the phone is bricked, and then they send you the tool which you execute? Or do they run the tool in real time using a remote desktop tool, but then one has to somehow capture their MSMDownlod tool using some other tool? Do they not try to delete the downloaded tool?
If you could share your detailed experience of this "remote session", and how to capture the MSMDownload tool, it would be of tremendous help. I don't own a retail/unlocked N200, but your experience can perhaps help those who have one, in getting the MSMDownload tool for the retail version. It would benefit the Tmobile users too, in finding a way to potentially convert Tmobile version to retail version. Thanks!
Can you upload the tool please mine is bricked after crash dump
nache2001 said:
Can you upload the tool please mine is bricked after crash dump
Click to expand...
Click to collapse
this might help..... https://forum.xda-developers.com/t/...ot-magisk-patched-boot-imgs-included.4323439/
PopCaps1996 said:
this might help..... https://forum.xda-developers.com/t/...ot-magisk-patched-boot-imgs-included.4323439/
Click to expand...
Click to collapse
Bootloader is locked i can't flash a patched rom, thanks anyway.
nache2001 said:
Bootloader is locked i can't flash a patched rom, thanks anyway.
Click to expand...
Click to collapse
That is a pity. The MSMDownload Tool seems to be the only way to fix this.
The good news is that the MSMDownload Tool is now available with Oneplus support, as of today e.g. until last week, folks out here posted that Oneplus support did not have the tool released to them. Perhaps you can contact Oneplus support and request a "remote session" to unbrick it similar to what @lzgmc did, and get your phone un-bricked sooner? If you do so, try to grab a copy of the MSMDownload Tool that they use in the session and share it with others out here. I am sure @lzgmc will post it soon, but no harm in having multiple copies available.
lzgmc said:
It's for the T-Mobile version.
Click to expand...
Click to collapse
@lzgmc Do you happen to recall which version of Oxygen OS the MSMDownlod tool is for? 11.0.1.4 or 11.0.1.5?
I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
I got it to fastboot mode, but there's no boot image for 11.0.0 available, right? Please help
Is it T-Mobile version or unlocked?
There's MSM tool for T-Mobile version and you can download full ROM for unlocked
If yours is unlocked and you can access recovery, use sideload
Code:
adb sideload
Press spacebar once and drag and drop the ROM onto command window and press enter
This can fix boot as well as making version update
bouyakasha said:
I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
Click to expand...
Click to collapse
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
amboyscout said:
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
Click to expand...
Click to collapse
wow .. please upload it to google drive or mega (dot) nz and post the link here .... honestly this gets me very excited ...
mingkee said:
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
Click to expand...
Click to collapse
my bootloader is locked .. thats why MSMDownload tool is a must
edale1 said:
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
Click to expand...
Click to collapse
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a maual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Dimitrimem said:
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
Click to expand...
Click to collapse
If you use the "+ Quote" button, rather than the reply button, it'll create a multiquote, letting you quote and reply to multiple posts all at once (it'll add a "insert quotes" button to the reply box). This eliminates double-posts, which most forums frown upon.
@Dimitrimem here ya go https://drive.google.com/drive/folders/1DzR0uEdyFeBeID4sVaT96z0Y88sMaomL?usp=sharing
Dimitrimem said:
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
Click to expand...
Click to collapse
Tried this today. Now waiting on OnePlus to respond.
bouyakasha said:
Tried this today. Now waiting on OnePlus to respond.
Click to expand...
Click to collapse
Don't wait to long for their reply .. if they don't answer call them on the phone.. it takes less than a minute to have them speak with you ... I dragged it for too long with them waiting 7 days to send me a shipping label than another 5 for another try at it .. another 4 to get the link for download ..after all that they said they don't have it... but this was a while back ... I'd be on that phone fast.. tell them you need your phone as it's the only one ... honestly if you can get the msm tool it would be amazing
mingkee said:
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a manual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Click to expand...
Click to collapse
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
darkghost568 said:
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
Click to expand...
Click to collapse
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
mingkee said:
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
Click to expand...
Click to collapse
Ok so now I'm stuck here as well (saw your comment in the other thread):
mingkee said:
I attempted to flash unlocked ROM on bootloader unlocked T-Mobile version phone
It stuck on products.img. The error stated "not enough space for the partition"
What happened?
Click to expand...
Click to collapse
Any luck getting past this?
darkghost568 said:
Ok so now I'm stuck here as well (saw your comment in the other thread):
Any luck getting past this?
Click to expand...
Click to collapse
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Towards the bottom of that post it talks about getting past that error.