Related
I'd like to start this thread as a "what to not do to brick your device" discussion. I've noticed a lot of people bricking randomly with the 5.1 update and not a lot of people talking about what causes it. Is it random? Did you flash certain files from a certain ROM or Google? Did you mix 5.0.1 boot/radio with a 5.1 ROM? Can we find a solution to fix bricked devices?
Any insight here to help others avoid this problem will be appreciated!
read carefully and follow instructions, and all will be fine.
I bricked mine by flashing older CM 12 ZIP which flashed 5.0.1 bootloader over 5.1 one, so I think that's the cause - the bootloader doesn't like being downgraded. Might even be a "security feature", now that I think about it - because "fastboot flash bootloader" won't even let you flash older bootloader than you already have.
simms22 said:
read carefully and follow instructions, and all will be fine.
Click to expand...
Click to collapse
That's rather deceiving, don't you think?
Tasssadar said:
I bricked mine by flashing older CM 12 ZIP which flashed 5.0.1 bootloader over 5.1 one, so I think that's the cause - the bootloader doesn't like being downgraded. Might even be a "security feature", now that I think about it - because "fastboot flash bootloader" won't even let you flash older bootloader than you already have.
That's rather deceiving, don't you think?
Click to expand...
Click to collapse
whats deceiving? that somethings are messing things up in cm? what can i tell you, stay away from cm. i do. just because cm is messing things up? cm isnt android in general, its cm. they do things differently than aosp or stock android. i personally decided to stay as far away from cm years ago. anyways, i flashed 5.1, then reflashed 5.0.2, then flashed 5.1 again, all on the old bootloader, no issues. as long as you read about whats going on, and follow instructions properly, all will be alright.
adoublearonn said:
I'd like to start this thread as a "what to not do to brick your device" discussion. I've noticed a lot of people bricking randomly with the 5.1 update and not a lot of people talking about what causes it. Is it random? Did you flash certain files from a certain ROM or Google? Did you mix 5.0.1 boot/radio with a 5.1 ROM? Can we find a solution to fix bricked devices?
Any insight here to help others avoid this problem will be appreciated!
Click to expand...
Click to collapse
When you upgrade to 5.1 the OEM Unlock (under dev options) automatically gets switched off (due to new security which prevents stealing a device and just flashing it bypass the security code). Where people are running into trouble is they are upgrading to 5.1 and the latest radio having OEM Unlock unchecked and then flashing CM which includes the old radio and bootloader, at this point you are stuck. Can't flash a custom recovery because your bootloader is locked, can't unlock the bootloader because you have to boot into an os and check the OEM Unlock, and you can't do a system restore because you cannot access recovery.
Sent from my Nexus 6 using XDA Free mobile app
For me. I came from a 5.0.2 ROM. Flashed the newest radio and boot for 5.1 and flashed a 5.1 ROM. I DO SHOW an unchecked OEM unlock. So am I to assume if I wished to flash a 5.0.2 ROM to check OEM unlock? I don't think I will "downgrade"...but just curious. Thank you.
Sent from my Nexus 6 using XDA Free mobile app
Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance
Flashed 5.1 BL and Modem on euphoria 5.0.2, then flashed back to stock 5.0.1, then flashed euphoria again, the same build upon which i flashed the 5.1 BL and Modem.
I didn't flash CM, still bricked my phone . And i don't know why. Coz after flashing it worked for a while and next morning it was bricked.
pallefar said:
Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance
Click to expand...
Click to collapse
Most of the others relocked their bootloader after flashing the full 5.1 image and ended up in a bootloop. Not the end of the world but now the "enable OEM unlock" unsets every time you boot so if you lock the bootloader and end up in a bootloop, you cannot unlock the bootloader which means you cannot flash anything to recover.
Dont relock your bootloader?
So would you say that if you have unlocked the bottloader then dont relock it untill a fix for the brick has been found?
Also if you update to 5.1, the stay with 5.1 Roms to be on the safe side?
Thanks in advance, just want to help pthers with same questions
pallefar said:
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Click to expand...
Click to collapse
I think people are bricking b/c they are attempting to downgrade the bootloader and/or the partition table. In general, you should never do that with a Motorola phone. There are some examples when it could be done in the past, but those are few and far between.
The best advice is to know what you are flashing before you flash and make sure you never attempt to downgrade the bootloader or partition table. And never take an OTA until you revert back to stock.
Also, always enable OEM lock and USB debugging. If that makes your phone too insecure for you b/c you keep trade secrets, classified information or pictures of your private parts on your phone, then you shouldn't be unlocking and rooting your phone to begin with.
So based on what has helped avoid bricks on the Moto X:
1) ensure your bootloader is unlocked before you flash anything to your phone;
2) do not attempt to downgrade the bootloader or partition table*;
3) know what you are flashing and make sure whatever it is does not include files that would attempt to downgrade your bootloader or partition table*;
4) make sure OEM unlock and USB debugging are enabled each time you flash;
5) never take an OTA unless you have reverted back to stock completely;
6) never upgrade the bootloader w/o also upgrading the partition table* and vice-versa; and
7) use mfastboot for flashing**.
* there is apparently no partition table on a Nexus
** this may or may not be necessary on the Nexus 6
Now the above is a bit overkill - for instance, there may be situations in which you can take an OTA w/o reverting completely back to stock or there may be situations in which you can downgrade your bootloaders. But if you follow those rules above you should be safe from bricking your device.
As long as your bootloader is unlocked and you can get into bootloader mode and you have the factory images, you aren't bricked.
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
randy6644 said:
Flashed 5.1 BL and Modem on euphoria 5.0.2, then flashed back to stock 5.0.1, then flashed euphoria again, the same build upon which i flashed the 5.1 BL and Modem.
I didn't flash CM, still bricked my phone . And i don't know why. Coz after flashing it worked for a while and next morning it was bricked.
Click to expand...
Click to collapse
Did you flash the 5.1 partition table when you flashed the 5.1 bootloader? I would never have a mismatch of versions b/t the bootloader and the partition table.
Once you upgraded the bootloader to 5.1, do you know if any of the subsequent flashes you did included earlier versions of the bootloader or the partition table?
pallefar said:
So would you say that if you have unlocked the bottloader then dont relock it untill a fix for the brick has been found?
Click to expand...
Click to collapse
I personally.
I'm not on 5.1 yet so I cant say if the "Enable OEM lock" is controlled by the bootloader at boot or the Kernel / OS..
Better be safe then sorry
JulesJam said:
I think people are bricking b/c they are downgrading the bootloader and/or the partition table. In general, you should never do that with a Motorola phone. There are some examples when it could be done, but those are few and far between.
The best advice is to know what you are flashing before you flash and make sure you never attempt to downgrade the bootloader or partition table. And never take an OTA until you revert back to stock.
Also, always enable OEM lock and USB debugging. If that makes your phone too insecure for you b/c you keep trade secrets, classified information or pictures of your private parts on your phone, then you shouldn't be unlocking and rooting your phone to begin with.
So:
1) ensure your bootloader is unlocked before you flash anything to your phone;
2) do not attempt to downgrade the bootloader or partition table;
3) know what you are flashing and make sure whatever it is does not include files that would attempt to downgrade your bootloader or partition table;
4) make sure OEM unlock and USB debugging are enabled each time you flash; and
5) never take an OTA unless you have reverted back to stock completely.
Now the above is a bit overkill - for instance, there may be situations in which you can take an OTA w/o reverting completely back to stock or there may be situations in which you can downgrade your bootloaders. But if you follow those rules above you should be safe from bricking your device.
As long as your bootloader is unlocked and you can get into bootloader mode and you have the factory images, you aren't bricked.
Click to expand...
Click to collapse
Thanks mate, I think for now it is better to be dafe then sorry and follow your steps above
i believe it would be controlled by the kernel/OS...and thats how it gets disabled upon boot of 5.1
pallefar said:
Thanks mate, I think for now it is better to be dafe then sorry and follow your steps above
Click to expand...
Click to collapse
I think I would add to that not to do anything to cause a version mismatch b/t the bootloader and the partition table. And since you shouldn't be downgrading those, what that means is never upgrade the bootloader w/o also upgrading the partition table and vice-versa.
Again, maybe you can get away with upgrading the bootloader w/o upgrading the partition table but I can't think of any reason not to have those both be on the same version.
One more thing - use mfastboot not fastboot to flash. mfastboot may only be needed for the larger files like system.img but I just use mfastboot all of the time and then I don't have to worry about it.
benefit of mfastboot
What is the benefit of mfastboot compared to normal fastboot flashing? just want to make sure everyhitng is covered
thanks in advance
pallefar said:
What is the benefit of mfastboot compared to normal fastboot flashing? just want to make sure everyhitng is covered
thanks in advance
Click to expand...
Click to collapse
http://mark.cdmaforums.com/MotoX-mFastboot.htm
pallefar said:
Hi
I have been flashing for many years, but I think for the first time in 7 years, I am not feeling safe to flash on the Nexus 6.
I upgraded the stock to 5.1, and had a hard time figuring out what people did, other then flashing the CM 12 5.01 to brick thier phone.
Could someone Help compile a list of what not to do on the Nexus 6 and upgraded to stock 5.1?
What should I and others do in stead to insure we can unlock teh bootloader, flash recovery and flash custom rom safely
Thanks in advance
Click to expand...
Click to collapse
The issue with bricking is that after updating to 5.1 people flashed CM which for some reason includes a bootloader. (no rom should include a BL and radio) When they flashed CM it tried to load an older bootloader which caused bricks. This will be seen by any roms that pretty much is just a renamed CM rom. My advise would be to know what your flashing by always inspecting the zip file before you flash it.
Is the nexus locking its bootloader itself now...I unlocked mine and never have knowing locked it back....So on every flash or after every reboot always turn OEM unlock on?
Sent from my Nexus 6 using Tapatalk
safe side
So basicly to be on the safe side, stay away or evestigate any Rom which is using the CM 12 source.
I guess AOSP is a safer bet at the moment? like Chroma rom
pallefar said:
So basicly to be on the safe side, stay away or evestigate any Rom which is using the CM 12 source.
I guess AOSP is a safer bet at the moment? like Chroma rom
Click to expand...
Click to collapse
Pretty much. Many claim to be based off of AOSP but most are just using CM sources. I know Slim and DU are based off of AOSP. DU uses the theme engine from CM but thats about it. Slim doesnt use anything from CM last I knew. Many are moving away from using anything CM related so there may be more.
zelendel said:
Pretty much. Many claim to be based off of AOSP but most are just using CM sources. I know Slim and DU are based off of AOSP. DU uses the theme engine from CM but thats about it. Slim doesnt use anything from CM last I knew. Many are moving away from using anything CM related so there may be more.
Click to expand...
Click to collapse
Yep. I think @zephiK chroma is aosp no-cm.
awesome thanks guys, I think this thread will guide people to not brick thier phones
kenbrownstone said:
Is the nexus locking its bootloader itself now...I unlocked mine and never have knowing locked it back....So on every flash or after every reboot always turn OEM unlock on?
Click to expand...
Click to collapse
No it doesn't relock itself but lots of people who are on these forums don't really understand what they are doing/flashing and so to be extra safe, I put that in there for people always to double check that OEM unlock is enabled.
People may think they have unlocked when they haven't or may not realize they relocked. I know that seems hard to do but I have never seen so many bricked nexi in my life before.
Just trying to help the less experienced from bricking. If you know what you are doing you don't need to take advice from me.
---------- Post added at 10:37 PM ---------- Previous post was at 10:32 PM ----------
zelendel said:
The issue with bricking is that after updating to 5.1 people flashed CM which for some reason includes a bootloader. (no rom should include a BL and radio) When they flashed CM it tried to load an older bootloader which caused bricks.
Click to expand...
Click to collapse
Yep, that will do it - downgrading the bootloader is a no-no on a motorola phone except in rare cases when it was possible.
zelendel said:
My advise would be to know what your flashing by always inspecting the zip file before you flash it.
Click to expand...
Click to collapse
Always!
Great write up! Saved my a$$ for sure. I updated my bootloader and radio the day it was available and I'm running a 5.0.1 CM12 based ROM. Here's where sometimes you get lucky, I was on v8.7 of this ROM, after I did the 5.1 bootloader and radio flash, an update came out to 8.8, I'm usually flash happy, but I figured why bother if I can wait for the 5.1 integration! I did unzip the update and no bootloader.img to be found, so I suppose the dev was wise enough not to put it in, but still.
I was curious about why most are moving away from CM? Because of these types of oversights? Their"interesting" business model?
JulesJam said:
I think people are bricking b/c they are attempting to downgrade the bootloader and/or the partition table. In general, you should never do that with a Motorola phone. There are some examples when it could be done in the past, but those are few and far between.
The best advice is to know what you are flashing before you flash and make sure you never attempt to downgrade the bootloader or partition table. And never take an OTA until you revert back to stock.
Also, always enable OEM lock and USB debugging. If that makes your phone too insecure for you b/c you keep trade secrets, classified information or pictures of your private parts on your phone, then you shouldn't be unlocking and rooting your phone to begin with.
So:
1) ensure your bootloader is unlocked before you flash anything to your phone;
2) do not attempt to downgrade the bootloader or partition table;
3) know what you are flashing and make sure whatever it is does not include files that would attempt to downgrade your bootloader or partition table;
4) make sure OEM unlock and USB debugging are enabled each time you flash;
5) never take an OTA unless you have reverted back to stock completely;
6) never upgrade the bootloader w/o also upgrading the partition table and vice-versa; and
7) use mfastboot for flashing.
Now the above is a bit overkill - for instance, there may be situations in which you can take an OTA w/o reverting completely back to stock or there may be situations in which you can downgrade your bootloaders. But if you follow those rules above you should be safe from bricking your device.
As long as your bootloader is unlocked and you can get into bootloader mode and you have the factory images, you aren't bricked.
---------- Post added at 05:07 PM ---------- Previous post was at 04:57 PM ----------
Did you flash the 5.1 partition table when you flashed the 5.1 bootloader? I would never have a mismatch of versions b/t the bootloader and the partition table.
Once you upgraded the bootloader to 5.1, do you know if any of the subsequent flashes you did included earlier versions of the bootloader or the partition table?
Click to expand...
Click to collapse
Does nexus have a partition table to flash? I've never heard of that from a nexus forum. I just flashed the 5.1 BL and went back to 5.0 stock rom ,then flashed euphoria. I believe that you flash via Fastboot if your bootloade is mismatched, that you can't acutally flash it. Not unless you use dd command. I'm not sure about this, though. I'm no way a dev or someone with knowledge in this field. But for nexus devices i owned, i never saw any nexus could be bricked this easy. Yes, they're made by motorola, but it's still a nexus . LG makes nexus 4 and 5, doesn't mean LG locked their bootloader as well. I don't think it's a fault of Motorola or has anything to do with its manufacturer. It's a nexus.
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. I would also like the bootloader to be locked again as well, I'm not sure whether or not flashing stock firmware would do this. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Ladyslayer said:
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Click to expand...
Click to collapse
this is not quite a normal request.
any and all changes done to your phone are done at your own risk, no guarantee that the process will be "safe". and no guarantee the end result will be as expected.
I can upload stock system, boot, and recovery images.
download them, unzip the file. put the 3 .img files to the phone.
reboot phone to twrp.
select install, browse to the folder you loaded files to, you should not see the file yet. Select flash image in lower part of screen. Now select system.img, on next screen select system and swipe to confirm.
when done do same for boot.img to boot
then recovery to recovery
when all three are done do a wipe(factory reset)
this should bring you back to prime v6.1
be advised that re-locking the boot loader has potential of bricking the pone so it is not advised to do it.
also on all the early versions there are reports that after ota update with unlocked bootloader it caused a bootloop most times it was recoverable by performing "oem unlock" again.
once booted to v6.1 I suspect there will be proper update notice. but if not here is a list of the official update download links.
6.1 to 6.4
http://hwfotadown.mayitek.com/ota/r....4_GENERIC_6.0_20160710-00151468612925207.zip
6.4 to 6.5
http://hwfotadown.mayitek.com/ota/r....5_GENERIC_6.0_20160729-21551470255454500.zip
6.5 to 6.6
http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip
7.4.2 to 8.4
http://hwfotadown.mayitek.com/ota/r..._V8.4_GENERIC_6.0_20170505-18551493981392.zip
17 to 21
http://hwfotadown.mayitek.com/ota/r...RIC_6.0_20170505-17451495815395129/update.zip
==>>V6.1 images.zip
.
.
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
well you can go back to locked but it is tricky. Think of it like this.
unlocking , allows anything you put on phone to try and load.
when you re-lock it only properly signed images are allowed to load.
so you can potentially lock yourself out of allowing phone to boot up, so the warning is more relevant when trying to go back to a locked state.
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
Sorry guys I have yet to try it out, I don't have a lot of time and am a little nervous to bite the bullet. @kfn, did you follow the guidelines in the above post to restore to original condition or a different set of instructions from somewhere else? Btw any suggestions on how to back up pretty much everything? Sorry Noob here obviously.
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Which version update was it?
I can't be certain about the 8.4 or 21 updates, but older ones when that happened you needed to boot into fastboot mode and do oem unlock again.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Did you re-lock the bootloader or was this because of an unlocked bootloader?
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
kfn said:
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
Click to expand...
Click to collapse
Do you still have the phone? Have you done the OTA updates since then with an unlocked bootloader?
did not try another OTA, put back modified ROM and disabled OTA.
Here post #312 with similar unanswered question about relocking bootloader, it is unclear for me if another OTA would properly relock it without bricking.
https://forum.xda-developers.com/r1...tock-rom-6-5-flashed-via-twrp-t3455532/page32
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Ladyslayer said:
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Click to expand...
Click to collapse
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
mrmazak said:
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
Click to expand...
Click to collapse
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Ladyslayer said:
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Click to expand...
Click to collapse
I do not know for sure. And there fore cannot recommend to do it. In the event something goes wrong and bootloader is locked, you cannot use fastboot to flash a repair, there fore MY opinion is the same "DO NOT relock bootloader". If something goes wrong it will be a brick.
Run stock version un modified all you want but if you unlocked I do not think you should relock. My opinion, do as you want.
Okay folks, took forever to find, but we finally have it, the T-Mobile OnePlus 6T MSMDownloadTool, your brick savior, bootloader relocker, among other things, I will include a basic faq at the end.
Requirements:
1. Windows PC
2. OnePlus 6T - T-Mobile Version ONLY (It will fail otherwise).
3. Zip linked below, unzip and keep all files within the same folder.
Steps to restore are as follows:
1. Open up your working folder and run MsmDownloadTool V4.0.exe
2. Power off the device, unplugged from the working pc.
3. Holding Volume up and down together, plug the device into the working pc (device should now show up in the tool, if it doesn't you may need the qualcomm usb drivers)
4. Once your device shows up, hit start and sit tight, device will reboot upon completion.
MSMDownloadTool 9.0v2: DOWNLOAD LINK
MSMDownloadTool 9.0v1: DOWNLOAD LINK
MSMDownloadTool 9.0.13: DOWNLOAD LINK
USB Drivers can be found here: https://androidfilehost.com/?fid=11410963190603879743
FAQ:
Q. Will this restore hw/sw mismatch?
A. If you can get into qusb mode it can.
Q. Will this relock my bootloader?
A. Yes
Q. Can I take OTA updates after using this?
A. Yes, it will return you to complete factory condition.
Q. Can this fix my soft/hard brick?
A. Yes.
Q. What OS version is this going to flash to my device?
A. Launch firmware - 9.0 V1
Q. If I relock my bootloader with this, do I need a new token?
A. No, you can use your old token to unlock again.
Q. Will this wipe my data?
A. Yes.
Q. Does my bootloader have to be locked or unlocked?
A. Works on either.
Q. Will this work when I updated to 10.0?
A. Yes, it will work regardless, but will bring you back to 9.0 v1.
Huge Thanks to:
@BIGWORM
@hartleyshc for providing info/support
@strictlyphat for the same
@mauronofrio and @OzzieSan for providing v2.
Thanks to @themustached for decryption and @Some_Random_Username for the tool, version 9.0.13
For those wondering about this, this will recover from pretty much any software error. It will not recover hardware failure. The Qualcomm EDL partition is part of the SoC and is not writable. If you cannot boot into it by holding all three buttons, then you have a hardware failure. Either with your buttons, or with your board.
Hooray!!
Will be using this very soon!
Thanks for this!!
Might want to add to the post what version this brings you back to. The original 9.0, or 9.0 v2. (Whatever the build date is, I think 11/6?)
Edit: looked at the zip. Looks to be the original 9.0, which is perfect.
@Haz3 get in here!!! good luck brah
Thank you???
Youre the real hero
Seriously, where do people get a hold of these tools? From OnePlus? Or T-Mobile? Was it leaked internally? Genuinely asking.
Second question: What if my phone is originally a T-Mobile phone that was flashed to the 9.0.5 update to make it international. All went successful. Then a few days later I screwed up and updated via OTA (a partial OTA) and brick the device. Would I use this TMobile msm tool, or the international one?
lemonspeakers said:
Seriously, where do people get a hold of these tools? From OnePlus? Or T-Mobile? Was it leaked internally? Genuinely asking.
Second question: What if my phone is originally a T-Mobile phone that was flashed to the 9.0.5 update to make it international. All went successful. Then a few days later I screwed up and updated via OTA (a partial OTA) and brick the device. Would I use this TMobile msm tool, or the international one?
Click to expand...
Click to collapse
dont ask such questions lol. be grateful
use tmobile tool.
CONFIRMED: WORKING
So if your bootloader relocks do we open with same token?
headcreepz said:
So if your bootloader relocks do we open with same token?
Click to expand...
Click to collapse
Yes
This is by far the holy grail for TMO variant users!
lemonspeakers said:
Seriously, where do people get a hold of these tools? From OnePlus? Or T-Mobile? Was it leaked internally? Genuinely asking.
Click to expand...
Click to collapse
Its genuinely not a good idea to ask questions like that. Just be thankful..
I saved like 6 copies of this. Super redundant backups lol!
wow, restored tmo rom, relocked loader, installing ota now, ota did fail twice then started installing after 2nd fail
at first I was skeptical but couldn't resist, glad it works, great tool!!!!!!!!!!!!
Alright, what was @Haz3 plan on doing once the TMO variant got out in the wild!?
Fixed a hw/build mismatch?????
Quick question, I have now 9.0 V2 installed from the OTA but my Bootloader is unlocked, yes It installs new updates when the BL is unlocked but only without any modifications to the ROM or anywhere, anyways back to my question, I wanna re-lock the BL, using this tool I'll be downgrade to 9.0 V1 and I guess it will re-lock the BL, but will I be able to update right away back to 9.0 V2? Will it probably install and the device will be like brand new out of the box? Or the tool will fail on me since I have a newer version? Or the tool will work the OTA after it will fail to install? Also this tool will definitely wipe the phone data, right?
SmileBigNow said:
Quick question, I have now 9.0 V2 installed from the OTA but my Bootloader is unlocked, yes It installs new updates when the BL is unlocked but only without any modifications to the ROM or anywhere, anyways back to my question, I wanna re-lock the BL, using this tool I'll be downgrade to 9.0 V1 and I guess it will re-lock the BL, but will I be able to update right away back to 9.0 V2? Will it probably install and the device will be like brand new out of the box? Or the tool will fail on me since I have a newer version? Or the tool will work the OTA after it will fail to install? Also this tool will definitely wipe the phone data, right?
Click to expand...
Click to collapse
My bootloader was unlocked, with random tmo 9.0 V1 rom installed, it would fail tmo ota Everytime. I had it rooted also, i unrooted. flashed back to international 9.0.5. ran tool, tool restored 9.0 V1 and locked the bootloader. Rebooted took ota after a couple fails now on 9.0 V2.
Just seems more snapier to me with the bootloader locked with 9.0 V2 as compared to 9.0.5
KMHartford said:
My bootloader was unlocked, with tmo rom installed, it would fail tmo ota Everytime. I flashed back to international 9.0.5. ran tool, tool restored 9.0 V1 and locked the bootloader. Rebooted took ota after a couple fails now on 9.0 V2.
Just seems more snapier to me with the bootloader locked with 9.0 V2 as compared to 9.0.5
Click to expand...
Click to collapse
Hey, nice meeting you here now..lol this wasn't my questions! Sorry but I asked if it's possible to rub this tool if I'm already on 9.0 V2, #2 if the OTA will work after the tool is done, which you answered as a affirmative, thanks, #3 if it will wipe my device clean, #4 if this tool will make my device act as a brand new phone like out of the box.
Again I never flashed any ROMs or anything, just Bootloader unlocked and I got the OTA and it's installed now but my BL is unlocked and I wanna lock it
SmileBigNow said:
Hey, nice meeting you here now..lol this wasn't my questions! Sorry but I asked if it's possible to rub this tool if I'm already on 9.0 V2, #2 if the OTA will work after the tool is done, which you answered as a affirmative, thanks, #3 if it will wipe my device clean, #4 if this tool will make my device act as a brand new phone like out of the box.
Again I never flashed any ROMs or anything, just Bootloader unlocked and I got the OTA and it's installed now but my BL is unlocked and I wanna lock it
Click to expand...
Click to collapse
Pretty sure it'll work just about to matter what your on, as long as it's the t mobile phone.
SmileBigNow said:
Quick question, I have now 9.0 V2 installed from the OTA but my Bootloader is unlocked, yes It installs new updates when the BL is unlocked but only without any modifications to the ROM or anywhere, anyways back to my question, I wanna re-lock the BL, using this tool I'll be downgrade to 9.0 V1 and I guess it will re-lock the BL, but will I be able to update right away back to 9.0 V2? Will it probably install and the device will be like brand new out of the box? Or the tool will fail on me since I have a newer version? Or the tool will work the OTA after it will fail to install? Also this tool will definitely wipe the phone data, right?
Click to expand...
Click to collapse
SmileBigNow said:
Hey, nice meeting you here now..lol this wasn't my questions! Sorry but I asked if it's possible to rub this tool if I'm already on 9.0 V2, #2 if the OTA will work after the tool is done, which you answered as a affirmative, thanks, #3 if it will wipe my device clean, #4 if this tool will make my device act as a brand new phone like out of the box.
Again I never flashed any ROMs or anything, just Bootloader unlocked and I got the OTA and it's installed now but my BL is unlocked and I wanna lock it
Click to expand...
Click to collapse
Tool did it for me. Brought my op6t to clean wiped out of box experience. 9.0 v1.0 Also eventually took the ota and now on 9.0 V2.0 locked bootloader. No warnings complaining about unlocked bootloader when rebooted
Thank you Dark Nightmare
I have the Rom from Vodafone which however does not receive updates. Would it be possible to install the standard European ROM RKDEUXM without unlocking the bootloader and without losing the phone configuration?
I have the full rom file for fastboot installation 12.5.19.0.
Really thanks
Unfortunately, no, without losing configuration and data, you wont be able to flash any other version roms.
goodsale said:
I have the Rom from Vodafone which however does not receive updates. Would it be possible to install the standard European ROM RKDEUXM without unlocking the bootloader and without losing the phone configuration?
I have the full rom file for fastboot installation 12.5.19.0.
Really thanks
Click to expand...
Click to collapse
1. It's impossible to flash different rom without unlocking bootloader.
2. It's impossible to unlock bootloader without wiping the phone.
I see that is possible for Xiaomi phone using XiaomiTool V2 via ADB (debug usb enable).
You loose data but you don't have to unlock bootloader.
I don't know if it works with 11t pro...
I'd say DON'T DO IT. Switching ROM like that without unlocking the bootloader is a very bad idea. If something goes wrong your recovery options will be very limited. For sure though if you don't format data after flashing a different region ROM the device will end up soft bricked. Either a bootloop or perma fastboot mode. Adb doesn't work with stock recovery and stock recovery doesn't offer the "format data" option anymore just "wipe" which is not the same and won't fix anything. So unlock bootloader first.
Thanks!
But is it possible to re-lock after rom installed and is it possible to have ota regular updates?
goodsale said:
Thanks!
But is it possible to re-lock after rom installed and is it possible to have ota regular updates?
Click to expand...
Click to collapse
You can only relock bootloader when the rom installed in your phone is the stock ROM came with your phone or else you'll brick it and have to reflash in EDL mode using test point.
Now I'm with RKDEUXM Rom...no brand Vodafone.
I've closed bootloader After flash and small test.
All work fine, no brick and Ota updates downloaded and installed.
Thanks!!!
goodsale said:
Now I'm with RKDEUXM Rom...no brand Vodafone.
I've closed bootloader After flash and small test.
All work fine, no brick and Ota updates downloaded and installed.
Thanks!!!
Click to expand...
Click to collapse
Care to share the process so others can learn as well?
Yes look here
Lock bootloader on change ROM from Vodafone to EEA
Hello dears! A pleasure to be here. I recently got a Xiaomi 11T Pro from Vodafone (MIUI Global 12.5.6 Estable RKDEUVF) and I want to change it to the global one (I have read that operator roms does not work properly good) so If Im not wrong It...
forum.xda-developers.com