Related
Just a quick question. Hopefully someone knows the answer.
I bought an unlocked phone. If I flash the ROM to one of the ones from here, is the phone going to stay unlocked or do I have to unlock it again.
Thanks for your help.
marshj05 said:
Just a quick question. Hopefully someone knows the answer.
I bought an unlocked phone. If I flash the ROM to one of the ones from here, is the phone going to stay unlocked or do I have to unlock it again.
.
Click to expand...
Click to collapse
The phone will remain unlocked as in use any network but read flashing requirements as to spl/hspl or you will brick your phone
Great. Thanks for your response.
Query answered and covered before. Thread closed
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
You should check out the 'Chinese Middleman' thread. If you get the bootloader unlocked you should be able to fix anything.
I can't unlock the bootloader since this is not a Dev edition. Unless something has changed, I'll check it.
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Even though it's not a Dev edition?
Yes you should be able too.
Sent from my XT1053 using Tapatalk
danman421 said:
Even though it's not a Dev edition?
Click to expand...
Click to collapse
All XT1053s can be unlocked, yes. Additionally, if you follow my advice, you don't NEED to unlock. If one of the commands fails, simply skip to the next as I previously advised, and TRY flashing with RSD Lite after you have run the commands I listed.
If you want to check and make sure fastboot is working, type:
fastboot devices
if you see your phone and it's serial number listed, you fastboot IS properly communicating with your phone.
You do not need to unlock your BL to do any of this...but if you are interested in ROOTING, you will need to.
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
danman421 said:
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
Click to expand...
Click to collapse
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
danman421 said:
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
Click to expand...
Click to collapse
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
samwathegreat said:
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
Click to expand...
Click to collapse
So if I am reading this correctly, there is no way to keep all of my data and take the update?
danman421 said:
So if I am reading this correctly, there is no way to keep all of my data and take the update?
Click to expand...
Click to collapse
You can attempt to, by either editing the XML in the SBF and removing the line that says "erase userdata", or by skipping the erase userdata if you use the manual method, but either way CAN mess everything up.
You used an EXPLOIT previously. Any time you use an exploit, you should -expect- to have to wipe everything and re-install from scratch if you want to get back to stock in order to be able to take updates. Keep this in mind if you use any exploits in the future.
Hi! This hasn't seemed to spelled out yet..... But many Moto x's can be unlocked, not just dev editions. However, you stated in the opening post that you have a Verizon Non dev, which can not be unlocked. Only way is to pay the "China middleman" (See thread in general with that name).
And personally.... I would stay on 4.2.2 and do the Slapmymoto method to get root and write protection disabled. That is the best root scenario, aside from unlocking the bootloader.
If you update to 4.4.2 or higher, you will have write protection enabled always, and no root, or sorta root with towelroot and pie. But that will limit what you can do.
See the How do I root my phone sticky thread in general for your options.
I should have posted earlier. I ran RSDLite and put the newest version on. I am unrooted. My Moto X is a Sept '13 version the the middleman probably wont work anyways. Its not worth it with this phone, im tired of the rooting, I guess im at that point in my life... Thanks for all your help though guys!
danman421 said:
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
Click to expand...
Click to collapse
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
KidJoe said:
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
Click to expand...
Click to collapse
Good catch! ?
OP... Perhaps full disclosure of what you have done on the phone would help.
Or is that how it was?
If it's been downgraded to 4.2.2 after being on 4.4.2... As said above.... You could brick now... Especially if you OTA.
I'd tread lightly at this point.
danman421 said:
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
Click to expand...
Click to collapse
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Yes, that was a good catch. What I did was RSD Lite to 4.4.4 now which reset all my data.
KidJoe said:
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Click to expand...
Click to collapse
Correct, I do not need help anymore but thank you.
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
you can always use fastboot to go back to 5.0.1
stas333 said:
you can always use fastboot to go back to 5.0.1
Click to expand...
Click to collapse
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
simms22 said:
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
Click to expand...
Click to collapse
Hmm, I guess I am confused as to what is causing the bricks for those that downgraded? I'll go ahead and do that right now but... I've read direct quotes from others stating that downgrading a Motorola bootloader is an instant brick and others have said it has happened to them.
EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
gee2012 said:
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
Click to expand...
Click to collapse
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
EmperorX said:
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
Click to expand...
Click to collapse
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
EmperorX said:
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
Click to expand...
Click to collapse
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
Click to expand...
Click to collapse
I wasn't planning on it, just curious how all these people are bricking?
gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flashing anymore if an incident would occur.
Click to expand...
Click to collapse
Also, I will absolutely need to relock my bootloader per organizational policies.
EmperorX said:
I wasn't planning on it, just curious how all these people are bricking?
Click to expand...
Click to collapse
Most of them because they wiped their system and couldn`t flash a image anymore because oem-unlock wasn`t enabled as i heard.
Sweet, successful downgrade!
I saw it mentioned in another thread that now that I have successfully downgraded I may brick when I get the T-Mobile 5.1 OTA.
Is there any credence to this? I am back on 5.0.1 now, relocked my bootloader, etc. Just wanted to make sure. It doesn't seem as if that would be the case to me but... Just wanted to be safe rather than sorry.
Thanks!
Disregard! Got it handled. Thanks guys!
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
Click to expand...
Click to collapse
Couldn't agree with you more....specially on the sentence I highlighted in bold. Got into the same problem yesterday. I excitedly upgraded from LMY47D to LMY47E. Later realised it's a Verizon image. So, thought let me go down to 5.0.1 and get a OTA - the "proper" way to upgrade.
While flashing, it didn't let me downgrade my bootloader. Mistake #1.
Then continued to flash the remaining images (radio, recovery, cache, system, userdata).
Then I locked my bootloader, so that it continues to look like "fresh out of the box". Mistake #2.
Then when I rebooted, it was constantly giving the error that NFC has failed and the Phone has failed. I couldn't get past those errors. It was continuously giving me that error.
It wouldn't let me unlock the bootloader, as the new bootloader (5.1) needs the OEM unlocking enabled in Developer's options.
Then I realised that there was a slight gap of time between showing the NFC & Phone error and the next set of NFC & Phone error. Using that, with great difficulty, setup the phone - going through every tap using the gap that was available between 2 sets of errors. Then I unlocked the developer's options, then enabled the OEM unlocking and finally got my bootloader unlocked.
Torrid - Horrible task. Was scared I had bricked my phone....but through some hard work (and sleepless night - up until 6am), got this finished.
Guys - seriously suggesting you NOT to lock the bootloader, IF you have unlocked the bootloader. Speaking with experience. Learn from my mistakes.
EDIT: I realised what the problem was and why NFC & Phone were erroring out. It was because I forgot to flash the Boot image. So, Bootloader & Boot were 5.1 & the rest were 5.0.1
EmperorX said:
Sweet, successful downgrade!
Click to expand...
Click to collapse
How did you downgraded the bootloader??
Downgrade of bootloader is not possible.
Sent from my Nexus 6 using XDA Free mobile app
EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
How about you just leave it on D?
What do you think you will gain by changing to M?
Hi,
Few hours ago I used Nexus toolkit to return to stock rom + unrooting.
I think everything went smoothly bc's it booted succsesfuly into the fist stage of the set the language of the device.
I heard that people bricked thier devices after OTA updating - That b'cs something with the Bootloader...("Somthing" is bc's I dont know if it happened due to leaved it Unlocked or proceed the
"Relock Bootloader"(OEM Lock).
So, What should I do?
Leave unlocked OR excute "Relock Bootloader"(OEM Lock)
???
Thank you!
I've seen many comments in these forums from experienced members saying that unless you're really paranoid about security you should leave it unlocked so that you have at least the possibility to recover from bricking.
Thanks for the quick replay @dahawthorne
So...you think it someting that happened to some particularly users and NOT a comprehensively issue that happaned to many android users that unlocked the device before?
P.S: am using the Nexus Toolkit by WugFresh.
For relock the BL - Just push on "OEM Lock", right?
Thank you!!
shabydog said:
...
So, What should I do?!
Click to expand...
Click to collapse
Read the post #2 again. Search XDA for 'unlock bootloader'.
Wonder why so many XDA members will keep root access and unlocked bootloader.
shabydog said:
P.S: am using the Nexus Toolkit by WugFresh.
For relock the BL - Just push on "OEM Lock", right?
Click to expand...
Click to collapse
You do understand that I'm recommending leaving your device *unlocked*, right...?
@shabydog: For heaven's sake man, don't lock your bootloader as it's a lot easier to recover the device if the bootloader is unlocked. Google has made it easier to recover a bricked device by offering the full system in an OTA package, but despite that, you still shouldn't lock the bootloader.
@dahawthorne @Strephon Alkhalikoi @NLBeev
Conclusion: I must leave the bootloader LOCKED.
And as long I did not touched the "OEM Lock" under Relock bootloader ==> i'm safe, right?
Thank you all so much.
shabydog said:
@[email protected] [email protected]
Conclusion: I must leave the bootloader LOCKED.
Click to expand...
Click to collapse
Obviously I need to brush up on my communications skills.
YOU MUST LEAVE THE BOOTLOADER ***UNLOCKED***.
dahawthorne said:
.../ brush up on my communications skills.....
Click to expand...
Click to collapse
More power of a transmitter does not mean the receiver is fine tuned.
I love first world problems. So after another thread to ask about flashing a Nexus back to stock, he has to open a separate thread for locking the bootloader.
@shabydog If it gives you this much stress, don't do anything. You have it, as I understand, back to stock, it's working, just put it back in its box, and sell it, or keep it, I don't care, but you should really not touch it.
Sorryyyy...I messed up with all the info' and so on.
YOU MUST LEAVE THE BOOTLOADER ***UNLOCKED***.
Click to expand...
Click to collapse
So Yes - I did not touched at all with "OEM Lock" under Relock.
Sory, it's just "T-M-I" for me - and not only here - with any "unkown" instructions./tut's.
Just confusing with learmimg something that I dont know.
But I just love it so much!!!!!!!!
I know you'r familiar with - deeply into that.
I want to learn...sometimes it's hard for me so it takes time.
Hope you can understand
I bought a Xiaomi mi 8 in a Xiaomi Shop in Shanghai. If I try to relock the bootloader I always get stuck booting on the recovery mode. Besides, I can not flash anything (supersu, xposed...) because I always end in bootloop; in both cases it is a softbrick
Can anybody help me?
If you have a mi8 Chinese box you aren't allowed to flash global ROM and lock bootloader.
And is there any way to fix it? Writing to Xiaomi, waiting X time...?
Thanks for your reply!
There are literally, more than a few hundred threads about not relocking. You modified your phone without reading up, no sympathy here. Your phone is dead if it is not global version. Gone. Paperweight. All the best to you
achickennugget said:
There are literally, more than a few hundred threads about not relocking. You modified your phone without reading up, no sympathy here. Your phone is dead if it is not global version. Gone. Paperweight. All the best to you
Click to expand...
Click to collapse
Hey! Nice to meet you and thanks for your kind answer. This placer is better thanks to people like you.
By the way,my mobile works perfectly. I relocked the bootloader more than once and I just needed to unblocked to solve it. About reading the posts, If you had read you would have realized that what interests me is simply to know if I can re-block the bootloader.
Who taught you to help people in forums that have problems and is probably having a bad time? Hitler?
Bortex19 said:
Hey! Nice to meet you and thanks for your kind answer. This placer is better thanks to people like you.
By the way,my mobile works perfectly. I relocked the bootloader more than once and I just needed to unblocked to solve it. About reading the posts, If you had read you would have realized that what interests me is simply to know if I can re-block the bootloader.
Who taught you to help people in forums that have problems and is probably having a bad time? Hitler?
Click to expand...
Click to collapse
You are welcome for my help. There are posts all over. I suggest you learn the courtesy of posting in the right sections instead or even better (to read first), this belongs in Q&A: https://forum.xda-developers.com/mi-8/help/to-relock-bootloader-chinese-device-t3834937 where if you read you would have realized it is all over the place, including one i created: https://forum.xda-developers.com/mi-8/how-to/please-read-tweaking-mi-8-t3833454. Anyways, have a good day, leaving this here for anyone else before they create another thread to "unblock" their bootloader
Bortex19 said:
And is there any way to fix it? Writing to Xiaomi, waiting X time...?
Thanks for your reply!
Click to expand...
Click to collapse
You can check out official xiaomi forum to see a way. However the official way posted there including open up the device & tinkering with the EDL mode, which is really too much of a hassle :/
---------- Post added at 10:58 AM ---------- Previous post was at 10:57 AM ----------
Bortex19 said:
Hey! Nice to meet you and thanks for your kind answer. This placer is better thanks to people like you.
By the way,my mobile works perfectly. I relocked the bootloader more than once and I just needed to unblocked to solve it. About reading the posts, If you had read you would have realized that what interests me is simply to know if I can re-block the bootloader.
Who taught you to help people in forums that have problems and is probably having a bad time? Hitler?
Click to expand...
Click to collapse
Are you having a modern Xiaomi device? How can you relock bootloader without sending it to bootloop?
achickennugget said:
You are welcome for my help. There are posts all over. I suggest you learn the courtesy of posting in the right sections instead or even better (to read first), this belongs in Q&A: https://forum.xda-developers.com/mi-8/help/to-relock-bootloader-chinese-device-t3834937 where if you read you would have realized it is all over the place, including one i created: https://forum.xda-developers.com/mi-8/how-to/please-read-tweaking-mi-8-t3833454. Anyways, have a good day, leaving this here for anyone else before they create another thread to "unblock" their bootloader
Click to expand...
Click to collapse
Better now, at least you're helping to find the information. And you are right, I should read more before doing anything; in fact, I read a lot but you know, internet is so big and it's no difficult to get lost in that information sea (even more if you're a noob in the area). I'll do it better next time.
Have a good day.
TeeHoang said:
You can check out official xiaomi forum to see a way. However the official way posted there including open up the device & tinkering with the EDL mode, which is really too much of a hassle :/
---------- Post added at 10:58 AM ---------- Previous post was at 10:57 AM ----------
Are you having a modern Xiaomi device? How can you relock bootloader without sending it to bootloop?
Click to expand...
Click to collapse
I bought it a couple of weeks ago. And no, I cannot relock it without sending it to bootloop.
The thing went like that: I unlocked the bootloader, I flashed the global ROM, I relocked the bootloader and I fell into recovery bootloop. So I entered on fastboot mode, I unblocked the bootloader again (with the Xiaomi tool), I went to fastboot again and I reflashed the global ROM.
The bootloader have to be open to allow the global ROM work. I don't know why I have avoided the brick, but this is what I've done at least twice.
Bortex19 said:
I bought it a couple of weeks ago. And no, I cannot relock it without sending it to bootloop.
The thing went like that: I unlocked the bootloader, I flashed the global ROM, I relocked the bootloader and I fell into recovery bootloop. So I entered on fastboot mode, I unblocked the bootloader again (with the Xiaomi tool), I went to fastboot again and I reflashed the global ROM.
The bootloader have to be open to allow the global ROM work. I don't know why I have avoided the brick, but this is what I've done at least twice.
Click to expand...
Click to collapse
Well if it bootloops the first time after you relocked it, it'll bootloop again & again. Was there any time after relocking did your phone boot properly? If not, you didn't avoid anything. As far as I understand, boot loop = soft brick.
And this is what I found on MIUI official forum:
TUTORIAL FLASH MI 8 BOOTLOP (SOFTBRICK & BRICK) WITH TESTPOIN:http://en.miui.com/thread-3459005-1-1.html
Bortex19 said:
I bought it a couple of weeks ago. And no, I cannot relock it without sending it to bootloop.
The thing went like that: I unlocked the bootloader, I flashed the global ROM, I relocked the bootloader and I fell into recovery bootloop. So I entered on fastboot mode, I unblocked the bootloader again (with the Xiaomi tool), I went to fastboot again and I reflashed the global ROM.
The bootloader have to be open to allow the global ROM work. I don't know why I have avoided the brick, but this is what I've done at least twice.
Click to expand...
Click to collapse
If I read it right, your device goes into bootloop when installing a Global ROM version and trying to block the bootloader. Probably your device is a Chinese version, which should only have the bootloader locked running a China ROM.
Otherwise, it will be bootloop.
gugugrp said:
If I read it right, your device goes into bootloop when installing a Global ROM version and trying to block the bootloader. Probably your device is a Chinese version, which should only have the bootloader locked running a China ROM.
Otherwise, it will be bootloop.
Click to expand...
Click to collapse
True that. Any Chinese devices running global will get (soft)bricked
Yeah, I was asking is you know the way to lock a chinese phone in global rom. Maybe in the future or with MIUI 10
Is it possible to enter EDL mode via opening your device and connecting the dots to enter 9008 Mode and than use QFIL (Qualcomm_Flash_Image_Loader) to restore the software, instead of going with the MiFlashTool and a needed EDL authorized account?
Bortex19 said:
Yeah, I was asking is you know the way to lock a chinese phone in global rom. Maybe in the future or with MIUI 10
Click to expand...
Click to collapse
This is still too early to know, because development is still slow.
Wrong forum section.
Sigray said:
Wrong forum section.
Click to expand...
Click to collapse
I could not find the way to change it. Do you know how to do it?
achickennugget said:
There are literally, more than a few hundred threads about not relocking. You modified your phone without reading up, no sympathy here. Your phone is dead if it is not global version. Gone. Paperweight. All the best to you
Click to expand...
Click to collapse
Even if he posted in the wrong section he didn't deserve an answer like yours. Keep in mind the Android cooperate spirit and try not to be that rude. And if you had read better his post you had understood how great is the information he gave, go on reading below.
Bortex19 said:
The thing went like that: I unlocked the bootloader, I flashed the global ROM, I relocked the bootloader and I fell into recovery bootloop. So I entered on fastboot mode, I unblocked the bootloader again (with the Xiaomi tool), I went to fastboot again and I reflashed the global ROM.
The bootloader have to be open to allow the global ROM work. I don't know why I have avoided the brick, but this is what I've done at least twice.
Click to expand...
Click to collapse
Actually these are excellent news, I had never read about a case like this. We knew that if the bootloader was unlocked by the seller and you locked it flashing a global rom (being a Chinese phone) you would get a brick only repairable through testpoint and using an authorized account. But I had never read about doing the same whith the bootloader unlocked by the user and I didn't know if it would be possible to unlock it again. So now we know this :
- Chinese unlocked by the seller -> brick locking while flashing global -> impossible to unlock and edl needed
- Chinese unlocked by the owner -> brick locking while flashing global -> ability to re-unlock and flash normally
I had some questions now :
1.- Did you have to wait to unlock the bootloader the first time? (360hrs, 720hrs.. You know)
2.- Did you have to wait when unlocking after the brick or was it instantly unlocked?
Thanks in advance!
descarao81 said:
Even if he posted in the wrong section he didn't deserve an answer like yours. Keep in mind the Android cooperate spirit and try not to be that rude. And if you had read better his post you had understood how great is the information he gave, go on reading below.
Actually these are excellent news, I had never read about a case like this. We knew that if the bootloader was unlocked by the seller and you locked it flashing a global rom (being a Chinese phone) you would get a brick only repairable through testpoint and using an authorized account. But I had never read about doing the same whith the bootloader unlocked by the user and I didn't know if it would be possible to unlock it again. So now we know this :
- Chinese unlocked by the seller -> brick locking while flashing global -> impossible to unlock and edl needed
- Chinese unlocked by the owner -> brick locking while flashing global -> ability to re-unlock and flash normally
I had some questions now :
1.- Did you have to wait to unlock the bootloader the first time? (360hrs, 720hrs.. You know)
2.- Did you have to wait when unlocking after the brick or was it instantly unlocked?
Thanks in advance!
Click to expand...
Click to collapse
It seems to me that this is not so, as some members still manage. However, since they did not add their personal Account to the developer options, they were not able to unlock the device again because they did not have the account associated with the device. It seems to be something related to different cases.
What can be recommended is that the devices unlocked by the seller, return to Chinese ROM more stable, and have your bootloader blocked. By then, the user requests to unblock the bootloader regardless of the time they have to wait. Thus making everything safer, in the case of possible bricks in the future.
gugugrp said:
What can be recommended is that the devices unlocked by the seller, return to Chinese ROM more stable, and have your bootloader blocked. By then, the user requests to unblock the bootloader regardless of the time they have to wait. Thus making everything safer, in the case of possible bricks in the future.
Click to expand...
Click to collapse
Have you ever heard of read about somebody doing that? Because I think there's still the doubt about the unlocking method used by the sellers, whether they do a regular unlock with an account or they patch the boot in any way which could cause problems locking the bootloader.