Related
if I have already upgraded to kit kat 4.4.2? I take it that since the 4.4.2 OTA hasn't been pushed for my Verizon Dev Ed device, that the factory images I have been given by Motorola are for 4.4.
But once the 4.4.2 OTA is pushed, the factory images I have now would be out of date because those are for 4.4., right? Then will Motorola release 4.4.2 factory images later?
Also, what does it mean when in bootloader mode it says Device is UNLOCKED. Status Code: 3. What is the status code 3?
Cozume said:
if I have already upgraded to kit kat 4.4.2? I take it that since the 4.4.2 OTA hasn't been pushed for my Verizon Dev Ed device, that the factory images I have been given by Motorola are for 4.4.
But once the 4.4.2 OTA is pushed, the factory images I have now would be out of date because those are for 4.4., right? Then will Motorola release 4.4.2 factory images later?
I have a verizon unlocked dev ed. Also, what does it mean when in bootloader mode it says Devide is UNLOCKED. Status Code: 3. What is the status code 3?
Click to expand...
Click to collapse
It gives you the stock recovery, the stock system image with all the applications, and the ability to update over the air (OTA). People re-flash the factory images either when they think they messed up their phone, or when they want the latest update via OTA instead of waiting for a SBF package. In short, it returns the phone to the default/non modded status.
I am fairly certain that a SBF will be made for 4.4.2, it just is taking a bit longer this time, maybe they are busy, especially since there is no new updates around the corner any time soon. Since you have already updated to 4.4.2 (like myself) there is no way to go back to stock unless you have made a recovery image in TWRP/CWM. Then all you have to do to update, is reflash the stock recovery image and then you can take a system OTA.
The bootloader on this phone cannot be downgraded, due to the eFuse system incorporated into it. If you attempt to load a lower bootloader in RSD Lite, it will simply fail to install and nothing else bad will happen, however, if you force the bootloader overwrite then you have a nice new paperweight (aka hard brick), because this trips the eFuse.
Status code 3 is basically the computer flag telling the future firmware updates that your bootloader has already been unlocked, so if you update using that same carrier/firmware, you don't lose your unlocked bootloader status. Another reason why you need to simply stick with your own firmware. As there have been reports that loading another regions/phones firmware can lock your bootloader again because the flag isn't there.
mastarifla said:
In short, it returns the phone to the default/non modded status.
Click to expand...
Click to collapse
It restores everything I modded? I erased the clogo.bin file and then I think I flashed with some other bin file to clogo and of course, didn't save a backup. Now I can't get the Kit Kat easter egg when I tap the build version so clearly it has something to do with the clogo file I messed with. I can live without the easter egg, but I don't want to brick my device. So I guess I should just flash the factory images and see what happens.
mastarifla said:
The bootloader on this phone cannot be downgraded, due to the eFuse system incorporated into it. If you attempt to load a lower bootloader in RSD Lite, it will simply fail to install and nothing else bad will happen, however, if you force the bootloader overwrite then you have a nice new paperweight (aka hard brick), because this trips the eFuse.
Click to expand...
Click to collapse
and even if your bootloader is unlocked, you have a hard brick and there is no way to correct that?
mastarifla said:
Status code 3 is basically the computer flag telling the future firmware updates that your bootloader has already been unlocked, so if you update using that same carrier/firmware, you don't lose your unlocked bootloader status. Another reason why you need to simply stick with your own firmware. As there have been reports that loading another regions/phones firmware can lock your bootloader again because the flag isn't there.
Click to expand...
Click to collapse
If my bootloader were to ever get locked again, can't I use the same 20 digit unlock key that Motorola emailed me to unlock it?
Many thanks again, and sorry I cannot hit the thanks button until tomorrow!
Cozume said:
It restores everything I modded? I erased the clogo.bin file and then I think I flashed with some other bin file to clogo and of course, didn't save a backup. Now I can't get the Kit Kat easter egg when I tap the build version so clearly it has something to do with the clogo file I messed with. I can live without the easter egg, but I don't want to brick my device. So I guess I should just flash the factory images and see what happens.
Click to expand...
Click to collapse
If you are already on 4.4.2 then you can flash the 4.4.2 "factory image" when it is released and it should be fine/back to normal.
Cozume said:
and even if your bootloader is unlocked, you have a hard brick and there is no way to correct that?
Click to expand...
Click to collapse
Correct, all the phones have the same eFuse system, even the developer phones. This "supposedly" prevents people from screwing up their phones more. (Personally I think it's silly, but I also have a Nexus, so it doesn't bother me).
Cozume said:
If my bootloader were to ever get locked again, can't I use the same 20 digit unlock key that Motorola emailed me to unlock it?
Many thanks again, and sorry I cannot hit the thanks button until tomorrow!
Click to expand...
Click to collapse
You should be able to (if you still have your IMEI), however there are reports that some people are losing their IMEI too, if this gets lost and there is no way to recover it then you are out of luck, because in order to unlock the bootloader it has to verify that the code works for your IMEI (which is carrier specific).
mastarifla said:
Correct, all the phones have the same eFuse system, even the developer phones. This "supposedly" prevents people from screwing up their phones more. (Personally I think it's silly, but I also have a Nexus, so it doesn't bother me).
Click to expand...
Click to collapse
It seems like the eFuse is the cause of people screwing up their phones. I suppose they do these sorts of things to satisfy potential corporate customers who want secure devices for their corporate communications.
mastarifla said:
You should be able to (if you still have your IMEI), however there are reports that some people are losing their IMEI too, if this gets lost and there is no way to recover it then you are out of luck, because in order to unlock the bootloader it has to verify that the code works for your IMEI (which is carrier specific).
Click to expand...
Click to collapse
Wow, that is awful but can't an IMEI be restored somehow if you know what it is? I not only have my box, Verizon has all my IMEI's stored on their system.
Cozume said:
It seems like the eFuse is the cause of people screwing up their phones. I suppose they do these sorts of things to satisfy potential corporate customers who want secure devices for their corporate communications.
Click to expand...
Click to collapse
Sadly corporate security is much less of a concern to them and actually something else entirely (see Samsung's encryption protocol for enterprise - SAFE). Motorola doesn't want to bother with supporting people on lower firmwares, and this prevents them from having to worry about it because they will always require you to be on the latest firmware for support, this eFuse system basically prevents people from using exploits in previous versions of the system (aka getting root on a non-unlocked phone, etc).
Cozume said:
Wow, that is awful but can't an IMEI be restored somehow if you know what it is? I not only have my box, Verizon has all my IMEI's stored on their system.
Click to expand...
Click to collapse
If you have your EFS files backed up then you are okay, you can just restore it and you are good to go again. However, the IMEI is a secure file, so you cant make a new one if its gone (nor can your cell company), this system in effect prevents people stealing phones and changing the IMEI in order to not be blacklisted. This system is in place for a very good reason, while not perfect (try selling a used phone to someone who understands this), its the best deterrent against theft currently available.
mastarifla said:
If you have your ESF files backed up then you are okay, you can just restore it and you are good to go again.
Click to expand...
Click to collapse
If I do a nandroid backup does it back those files up? if not, what can I use to back them up?
Also, I will have to come back tomorrow and the next day to hit the thanks button because I will use up all my thanks again tomorrow on you, lol!
Cozume said:
If I do a nandroid backup does it back those files up? if not, what can I use to back them up?
Also, I will have to come back tomorrow and the next day to hit the thanks button because I will use up all my thanks again tomorrow on you, lol!
Click to expand...
Click to collapse
There are tools available to backup your EFS partition in case a nandroid doesn't work correctly. Some CWM/TWRP versions do EFS partition backups, some don't, be sure to read through the threads and make sure. Asking a question goes a long way.
Hey folks. Got a Dev edition here, which as I understand is easy to unlock. Question is must I lose my data when doing so? And if yes, how can I backup before unlocking? If I had root, I would run titanium backup, but given that I can't get root until I unlock, this seems like a chicken and egg problem....
Sent from my XT1053 using XDA Free mobile app
Yes, doing the. Mfastboot oem unlock will factory reset the phone. You will lose apps and data. I am not familiar with a way (while not rooted) to back up everything and restore after unlocking such that everything is the same.
I may be wrong.....just going from memory of what I've read, but I think an app called helium can backup without root. Then you'd need to transfer the backup off the phone, cause everything is gone when you unlock. Pics too.
Hm. Can anyone confirm this happens for sure? On the Galaxy Nexus, people said the same thing but it turned out that if you just typed fastboot oem unlock without flashing any partitions that no data was actually erased. I just can't understand why unlocking would be linked to erasing.
Thanks!
Sent from my XT1053 using XDA Free mobile app
zAlbee said:
Hm. Can anyone confirm this happens for sure? On the Galaxy Nexus, people said the same thing but it turned out that if you just typed fastboot oem unlock without flashing any partitions that no data was actually erased. I just can't understand why unlocking would be linked to erasing.
Thanks!
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Unlocking erases everything. On any device I've owned. The x for sure.
Why? Dunno. Lol
Unlocking the bootloader will reset the phone back to factory fresh condition as stated. When I unlocked my Moto X it was factory reset. Same for when I unlocked the bootloader in my Nexus 10, Droid Razr M, Incredible and Eris. I think this is the normal behavior.
There are ways to back up your data and apps even without an unlocked or rooted phone. There is a toolkit in this forum somewhere for the Moto X that will do that as well as a market app (Helium?). I used the toolkit here:
http://forum.xda-developers.com/moto-x/development/tool-moto-x-toolkit-v1-2-1-t2477132
But I did that while at 4.4, before the OTA update to 4.4.2.
Any tool to recover files from a recently formatted device by unlocking the bootloader? thanks.
No. "Format" means "Blotto Everything". That's exactly what happens.
IMO seems to be a commercial "feature" more than a technical limitation. The simply want to discourage you to unlock the bootlader. All along the process, there is a warning message telling you that unlocking the bootloader will make the phone less secure. A subliminal message from Xiaomi : Blessed be the freely included uninstallable without root - and by extention unlocking the bootloader... D'oh!- bloatware package ! Or go to hell with your data if you dare to spit on it!
If you are able to install twrp, does that mean that the phone is already unlocked? I've already deleted my stock android and I couldn't see any options there at all of unlocking the oem directly in the settings, but I was able to install twrp itself (2.6).
Hello,
I recently lost my IMEI and just got my replacement phone from Motorola. I'm looking to unlock and root again but I don't want to lose the IMEI again! Is there a way to back it up? I've seen how to do it on other phones but nothing for the Moto X 2nd Gen yet.
Thanks.
You don't "lose" your IMEI as such. It won't not show up, in case you flash a wrong radio. Unlocking the boot loader and rooting your phone alone won't make your IMEI disappear. So go ahead and unlock, root you'll be fine
Yeah, what did you do besides rooting to get to where you were? I suspect you flashed an inappropriate modem somehow? Can you confirm?
CaptainMocha said:
Hello,
I recently lost my IMEI and just got my replacement phone from Motorola. I'm looking to unlock and root again but I don't want to lose the IMEI again! Is there a way to back it up? I've seen how to do it on other phones but nothing for the Moto X 2nd Gen yet.
Thanks.
Click to expand...
Click to collapse
Back up your /pds partition, in the sticky in this forum you can find a guide
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
http://forum.xda-developers.com/showthread.php?t=2972693 I don't know if this can help you or not I'm assuming you've already seen it
mikeboballen said:
http://forum.xda-developers.com/showthread.php?t=2972693 I don't know if this can help you or not I'm assuming you've already seen it
Click to expand...
Click to collapse
That was the guide I was following, which led to this somehow.
I'm thinking about re-locking and un-rooting now so I'll have a shot at the warranty claim.
Good luck man hope it all works out for you
ccarrionc said:
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
Click to expand...
Click to collapse
On this Nexus 6 thread some people had success flashing back to stock modems/baseband - these would be the commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
http://forum.xda-developers.com/nexus-6/help/imei-repair-t3000420
Then if that doesn't work then this:
http://forum.xda-developers.com/showthread.php?t=1960918
Then there is this:
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"
JulesJam said:
On this Nexus 6 thread some people had success flashing back to stock modems/baseband - these would be the commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
http://forum.xda-developers.com/nexus-6/help/imei-repair-t3000420
Then if that doesn't work then this:
http://forum.xda-developers.com/showthread.php?t=1960918
Then there is this:
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"
Click to expand...
Click to collapse
Thanks, but nothing worked. I'm starting to wonder if it might be a hardware issue...
ccarrionc said:
Thanks, but nothing worked. I'm starting to wonder if it might be a hardware issue...
Click to expand...
Click to collapse
Did you try this method using QPST?
http://forum.xda-developers.com/showthread.php?t=1960918
JulesJam said:
Did you try this method using QPST?
http://forum.xda-developers.com/showthread.php?t=1960918
Click to expand...
Click to collapse
I did, but I couldn't get the software to recognize my phone, it does seem kinda outdated (2012). Used QPST 2.7.
ccarrionc said:
I did, but I couldn't get the software to recognize my phone, it does seem kinda outdated (2012). Used QPST 2.7.
Click to expand...
Click to collapse
Sounds like you need to get a warranty replacement. It could be a hardware problem but even if it is not, they really need to make these phones less easy to eff up.
The IMEI is on the efs partition that we cannot even flash so I don't know how they can get messed up by the consumer but obviously they do. Someone on the N6 thread was saying it is a Qualcomm issue.
JulesJam said:
Sounds like you need to get a warranty replacement. It could be a hardware problem but even if it is not, they really need to make these phones less easy to eff up.
The IMEI is on the efs partition that we cannot even flash so I don't know how they can get messed up by the consumer but obviously they do. Someone on the N6 thread was saying it is a Qualcomm issue.
Click to expand...
Click to collapse
If I can't get the unlocked bootloader warning to go off, then I'm done for I think.
Unless people at the support center don't bother restarting it or anything... fingers crossed.
Plan B is to hardbrick it somehow so no one can turn it on and see my mess, haha.
ccarrionc said:
If I can't get the unlocked bootloader warning to go off, then I'm done for I think.
Click to expand...
Click to collapse
That is possible - there are plenty of threads on how to do that.
But even once you relock, your status code will be locked 2, not locked 0 so they can tell from the device. Also, you had to get an unlock code directly from them so if your device didn't qualify for bootloader unlock with maintaining your warranty, then they will know from that too.
Also, your qe will likely show 0/1 even though you unrooted. You can see the qe in stock recovery.
---------- Post added at 03:49 AM ---------- Previous post was at 03:46 AM ----------
ccarrionc said:
Unless people at the support center don't bother restarting it or anything... fingers crossed.
Click to expand...
Click to collapse
They will know b/c you got an unlock code to unlock it.
ccarrionc said:
Plan B is to hardbrick it somehow so no one can turn it on and see my mess, haha.
Click to expand...
Click to collapse
I would check the warranty status online. Even if the warranty is void, they may be able to repair the phone for a reasonable price if you don't hard brick it.
JulesJam said:
That is possible - there are plenty of threads on how to do that.
But even once you relock, your status code will be locked 2, not locked 0 so they can tell from the device. Also, you had to get an unlock code directly from them so if your device didn't qualify for bootloader unlock with maintaining your warranty, then they will know from that too.
Also, your qe will likely show 0/1 even though you unrooted. You can see the qe in stock recovery.
Click to expand...
Click to collapse
So the only way is getting the phone to not be able to turn on at all? Is there any known way to get off with it?
You need to flash an image from your original provider and it will work fine again. Right now you have an incompatible modem and as a result you will have no IMEI/mobile data or wifi as the radio portion of the phone is disabled.
ccarrionc said:
So the only way is getting the phone to not be able to turn on at all? Is there any known way to get off with it?
Click to expand...
Click to collapse
No, they have you in the database as having requested an unlock code.
ccarrionc said:
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
Click to expand...
Click to collapse
As someone post above. You need the stock modem of your phone model, but in your case any xt1097 will work just flash using the Fastboot mode steps and everything will be fine. I have a post on the general section "guide to convert 1097 to 1095" there you can find all the possible scenarios.
Good luck.
Steve-x said:
You need to flash an image from your original provider and it will work fine again. Right now you have an incompatible modem and as a result you will have no IMEI/mobile data or wifi as the radio portion of the phone is disabled.
Click to expand...
Click to collapse
That is what I said above but he said he tried it and it didn't work.
OP - you need to make sure you are flashing the right files - you need to flash the modem/baseband files for your device (XT1097).
JulesJam said:
That is what I said above but he said he tried it and it didn't work.
OP - you need to make sure you are flashing the right files - you need to flash the modem/baseband files for your device (XT1097).
Click to expand...
Click to collapse
I am 100% sure the files used were not the correct ones.
juliospinoza said:
As someone post above. You need the stock modem of your phone model, but in your case any xt1097 will work just flash using the Fastboot mode steps and everything will be fine. I have a post on the general section "guide to convert 1097 to 1095" there you can find all the possible scenarios.
Good luck.
Click to expand...
Click to collapse
I was following your guide, everything was fine until the OTA update came up. Is there anyway to get back to the xt1097 firmware I had before? It was 4.4.4 with Telcel.
ccarrionc said:
I was following your guide, everything was fine until the OTA update came up. Is there anyway to get back to the xt1097 firmware I had before? It was 4.4.4 with Telcel.
Click to expand...
Click to collapse
What was the exact version you had before? For future reference you shouldn't flash firmware from another provider unless you have original firmware to reflash if you experience an issue.
Steve-x said:
What was the exact version you had before? For future reference you shouldn't flash firmware from another provider unless you have original firmware to reflash if you experience an issue.
Click to expand...
Click to collapse
Found a firmware from my original provider, everything is back to normal (except now I have the different status code in the fastboot screen).
For future reference, I just installed the previous firmware through fastboot (with mfastboot, of course). IMEI was recognized again and baseband too.
I was trying to sim unlock bad IMEI (financed) all services refused to unlock I managed to sim unlock very easy
1 you need to convert to international version follow this thread By AnonymousTipster ( great thanks ) (https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 )
2 unlock bootloader
3 type this commands
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
thats all
you can also backup modemst1 and modemst2 files before this steps
you won't loose imei or have some problem phone works without any problem just tested
Congrats bro
Alright bro, I thought this was an early April fool's joke at first but it's apparently not. Congrats n sorry for the early doubts... I had just read your posts about trying a sim unlock thru some company and it being successful but the tmo app wasn't working so I figured that's where your sim got unlocked it had just carried over to the international version but apparently not. It's crazy that this is how easy it is to bootloader unlock & unlock your sim. Definitely backup your modemst with readback mode in msm
I can help you do what you need as I've done it before. pm me.
gigilie said:
No guide ends with the user deleting their modem. I mean come on man dont mess with people. You've been all over the forum last few days with a stolen phone with a bad imei trying to get it unlocked. U just said blowfish finally came thru n u got it unlocked. How r u gonna claim someone elses work tell everyone it does something it really doesn't do (which is sim unlock the device!) And then have them delete their modems and ask for a donation.... Too funny April fool's ISN'T for a week dude.
Click to expand...
Click to collapse
1 phone is not stolen its financed ordered from ebay as unlocked I was scammed was not able to return from oversies
2 you can backup your modems and then try deleting with this commands they are not deleting I tryed 2 times
3 after blowfish confirmed that phone was unlocked opened unlock app > permanent unlock was receiving same error delleted app data same error factory reset - same error reflashed firmware same error after that this commands worked
all unlock services included blowfish unlock cellunlocker few one from ebay . tyed many of them they refunded money (blowfish returned credits to account) main reason wan device was not active 40 days this services can unlock bad imei phones but if device was not active 40 days they can't more than month I was trying to unlock but only this commands worked if you think you will loose modems to backup try this method
Download & Open up Terminal Emulator on your phone
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.
Now enter these two commands:
Code:
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
Code:
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
Deleted doubting post #2 lol
gigilie said:
Bro ur funny we use magisk n we don't dd modems thru terminal to back anything up.... Tell me technically what sense would it make to delete your modem how would that unlock your sim? See if u really did unlock ur sim n bootloader for free by flashing to international and then deleting ur modems (lol) then you would have put twrp on and actually rooted upgraded to beta 7 or flashed an aosp (at least that's what I'd assume cause that's what we unlock the bootloader for) so post some screenshots of whatever ROM ur on or a video of the process with u proving ur not lying. Cause as far as I know absolutely no information regarding the devices unlocked sim state reside in the modem. Imei in Efs maybe or on the board in the phone but not on a piece of a stock rom that some of the best developers on here just overlooked but u magically figured it out.... Quit it dude go home
Click to expand...
Click to collapse
Yes bro I was very funny looking when this worked Im using non T-Mobile sim my number is not covered txt me for for instructions One guy from my country have same phone tmo locked I will take video for you
Hi, I believe you, and I want to try this method... but where are the source of your information? How did you know puting those comands will work?
Thank you!!!
robbie1104 said:
Hi, I believe you, and I want to try this method... but where are the source of your information? How did you know puting those comands will work?
Thank you!!!
Click to expand...
Click to collapse
40+ days I was trying everything Don't know how this phone survived
nika_bego said:
40+ days I was trying everything Don't know how this phone survived
Click to expand...
Click to collapse
Hi again, just one more question: How did you root the device (to make modem backup) with locked bootloader??
robbie1104 said:
Hi again, just one more question: How did you root the device (to make modem backup) with locked bootloader??
Click to expand...
Click to collapse
I didn't backup modems copied this first found instructions for annoying users ?
robbie1104 said:
Hi again, just one more question: How did you root the device (to make modem backup) with locked bootloader??
Click to expand...
Click to collapse
Before phone turned on I was searching modem files I was ready that phone doesn't turns on. But everything was good i don't lost my imei and phone is sim unlocked
nika_bego said:
Before phone turned on I was searching modem files I was ready that phone doesn't turns on. But everything was good i don't lost my imei and phone is sim unlocked
Click to expand...
Click to collapse
Some people I know discovered this work around in November if u make a modemst back up of both modems first, use msm readback to backup imei, then wipe modem, then sim unlocked, restore modem files and imei with msm readback mode. It's just very risky. So if u know how to use msm readback mode and smt mode then go for this, @nika_bego you are correct. For the haters, grow up man, u are incorrect, this man is correct. There are multiple ways to do things in android. I was part of the initial team that first achieved root with this phone with a locked bootloader via aging kernel. Which then led to wiping the modems..we had to keep it between ourselves or chaos would erupt on xda. Plus the mods get so upset if u talk about hacks, modded apps, imei anything and restoring stuff.
Thanks, good job man
fullofhell said:
Some people I know discovered this work around in November if u make a modemst back up of both modems first, use msm readback to backup imei, then wipe modem, then sim unlocked, restore modem files and imei with msm readback mode. It's just very risky. So if u know how to use msm readback mode and smt mode then go for this, @nika_bego you are correct. For the haters, grow up man, u are incorrect, this man is correct. There are multiple ways to do things in android. I was part of the initial team that first achieved root with this phone with a locked bootloader via aging kernel. Which then led to wiping the modems..we had to keep it between ourselves or chaos would erupt on xda. Plus the mods get so upset if u talk about hacks, modded apps, imei anything and restoring stuff.
Thanks, good job man
Click to expand...
Click to collapse
:good:
thanks
gigilie said:
No guide ends with the user deleting their modem. I mean come on man dont mess with people. You've been all over the forum last few days with a stolen phone with a bad imei trying to get it unlocked. U just said blowfish finally came thru n u got it unlocked. How r u gonna claim someone elses work tell everyone it does something it really doesn't do (which is sim unlock the device!) And then have them delete their modems and ask for a donation.... Too funny April fool's ISN'T for a week dude.
Click to expand...
Click to collapse
Modemst1 and 2 is settings, not modem.
fullofhell said:
Some people I know discovered this work around in November if u make a modemst back up of both modems first, use msm readback to backup imei, then wipe modem, then sim unlocked, restore modem files and imei with msm readback mode. It's just very risky. So if u know how to use msm readback mode and smt mode then go for this, @nika_bego you are correct. For the haters, grow up man, u are incorrect, this man is correct. There are multiple ways to do things in android. I was part of the initial team that first achieved root with this phone with a locked bootloader via aging kernel. Which then led to wiping the modems..we had to keep it between ourselves or chaos would erupt on xda. Plus the mods get so upset if u talk about hacks, modded apps, imei anything and restoring stuff.
Thanks, good job man
Click to expand...
Click to collapse
can confirm same.
robbie1104 said:
Hi again, just one more question: How did you root the device (to make modem backup) with locked bootloader??
Click to expand...
Click to collapse
I don't believe this guy either. However it is actually true that converting the TMO variant to the International using this: https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 will allow a simple
Code:
fastboot oem unlock
instead of having to go through OnePlus/TMO to get unlock.bin file.
Doing the conversion, then unlocking the bootloader, then rooting as normal. However I do not for one second believe that erasing the modem will unlock the SIM.
Edit: Looks like it might be possible to SIM unlock with this HOWEVER it requires MORE STEPS not only what is listed in the OP.
OP - Can you please update your post with a full, detailed list, of what to do?
nika_bego said:
I was trying to sim unlock bad IMEI (financed) all services refused to unlock I managed to sim unlock very easy
1 you need to convert to international version follow this thread By AnonymousTipster ( great thanks ) (https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 )
2 unlock bootloader
3 type this commands
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
thats all
you can also backup modemst1 and modemst2 files before this steps
you won't loose imei or have some problem phone works without any problem just tested
Click to expand...
Click to collapse
It is really necessary to unlock bootloader first?? I flashed 9.0.12 and OEM unlock under Developer settings is grayed and disabled... Do i have to flash 9.0.11 to unlock OEM?? In what version of OxygenOS did you make this procedure??
Thank you!!!
robbie1104 said:
It is really necessary to unlock bootloader first?? I flashed 9.0.12 and OEM unlock under Developer settings is grayed and disabled... Do i have to flash 9.0.11 to unlock OEM?? In what version of OxygenOS did you make this procedure??
Thank you!!!
Click to expand...
Click to collapse
I flashed 9.0.11 done this steps and then locked bootloader after updated to 9.0.12
sandix said:
I don't believe this guy either. However it is actually true that converting the TMO variant to the International using this: https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 will allow a simple instead of having to go through OnePlus/TMO to get unlock.bin file.
Doing the conversion, then unlocking the bootloader, then rooting as normal. However I do not for one second believe that erasing the modem will unlock the SIM.
Edit: Looks like it might be possible to SIM unlock with this HOWEVER it requires MORE STEPS not only what is listed in the OP.
OP - Can you please update your post with a full, detailed list, of what to do?
Click to expand...
Click to collapse
U gotta use readback mode on msm to back it up first. Then wipe smt wipe it then use it to restore the modemst. A and b and then u have to restore imei. A quick Google search will help u with that