Let's tell my experience.
I had my Moto G6 Play for near two months. I've unlocked the Bootloader and attempted to root it but unsuccessful. So, I've rolled back to my stock rom via Fastboot (using the stock ROM linked in this forum). It worked fine after that.
Some days ago, the official Android Pie update has been available, so, I installed it via OTA. However, it failed. After trying installing again, the phone gone down and never powered on again (even entering the Recovery mode, even charging all the night).
Therefore, I left the device to the technical service, knowing the bootloader unlock voids the warranty.
Does this happened to someone else? In what scenarios?
Thanks for commenting.
Amitie10g said:
Let's tell my experience.
I had my Moto G6 Play for near two months. I've unlocked the Bootloader and attempted to root it but unsuccessful. So, I've rolled back to my stock rom via Fastboot (using the stock ROM linked in this forum). It worked fine after that.
Some days ago, the official Android Pie update has been available, so, I installed it via OTA. However, it failed. After trying installing again, the phone gone down and never powered on again (even entering the Recovery mode, even charging all the night).
Therefore, I left the device to the technical service, knowing the bootloader unlock voids the warranty.
Does this happened to someone else? In what scenarios?
Thanks for commenting.
Click to expand...
Click to collapse
1. Unlocking your bootloader does not void your warranty.
2. That's a recovery loop. It doesn't look like it, but it is.
3. How to fix that crap. -Flash stock firmware, wipe data, cache, and DDR through fastboot, then issue the command fastboot reboot. Let it encrypt, then you can boot into recovery normally. If you don't let it encrypt right after flashing stock firmware then you'll loop again.
Spaceminer said:
1. Unlocking your bootloader does not void your warranty.
2. That's a recovery loop. It doesn't look like it, but it is.
3. How to fix that crap. -Flash stock firmware, wipe data, cache, and DDR through fastboot, then issue the command fastboot reboot. Let it encrypt, then you can boot into recovery normally. If you don't let it encrypt right after flashing stock firmware then you'll loop again.
Click to expand...
Click to collapse
1.- Maybe, depending the country. So, the agent who attended me told me the warranty is void just when unlocking the Bootloader. Motorola's technical service will give the last word about that, as I have re-installed the stock rom.
2.- As I told, the phone don't seems to power on and no charging light. I've connected to the computer and it never identifies as anything than a brick.
3.- Per above, Fastboot won't recognize the device and unable to send commands to the device in any way. In other words, the device seems to be completely dead.
The vendor where I purchased the device just told me they will replace the device under the warranty.
So, I'll apply the updates via OTA and tell you the results, but I'll not unlock the bootloader, but backup upload the ROM via Fastboot and TWRP, and upload it.
I've finally gone to the vendor to retire the replacement device.
However, they don't have the Moto G6 Play available anymore. Instead, they gave me the Moto G6 (better device except for the battery) for free, as the failure has been covered under the warranty.
Advices:
Ask your vendor the repair costs for failures caused by failed firmware updates. I assume Motorola didn't checked even if the bootloader is unlocked (as the device seems to be completely dead), they just decided to replace the device.
Don't send the device to the technical service if it powers on and Fastboot is working unless you're prepared to pay the repairs.
Don't try to install the Android Pie update with the bootloader unlocked and firmware altered.
acutally, updating with unlocked bootloader causes nothing. that might have been a hardware problem of some source, idk...
---------- Post added at 09:45 PM ---------- Previous post was at 09:44 PM ----------
but unlocking the bootloader does void your warranty tho
Indeed the warranty is void after unlocking the bootloader, but Motorola haven't noticed (and even checked it) as the device completely died.
¿So, where is actually stored the Bootloader? In the Flash or a separated ROM chip. As a previous flashing attempt may caused failed write to key partitions.
Amitie10g said:
Indeed the warranty is void after unlocking the bootloader, but Motorola haven't noticed (and even checked it) as the device completely died.
¿So, where is actually stored the Bootloader? In the Flash or a separated ROM chip. As a previous flashing attempt may caused failed write to key partitions.
Click to expand...
Click to collapse
Not true. My bootloader is unlocked, and Motorola is well aware of that since I had to ask them for the key. Unlocking it by itself doesn't void it. It's what you do afterwards that might void it. Like running an over volted kernel and frying something. Check the screen shot. My warranty is still good until Aug of this year. And if I really wanted to I could just relock the bootloader before sending it in, which blows that theory out of the water.
i replaced one under warranty with no issue. with an unlocked boot loader. twice.
Related
Hi everyone
I wanted to try going from the stock Android 4.3 to cm12.1.
My phone was bootloader locked but unlocking was allowed.
So I followed the process on the sony website and got the unlock code and entered it.
Phone then refused to restart, stuck on booting screen.
Eventually using Flashtool, I found a stock rom and reflashed that, still wouldn't boot. Then I relocked the bootloader and now it boots again.
However, it now says sim card is invalid and refuses to let me join the phone network (I'm in Malta, using the Go network).
Also, I'm now unable to reunlock the bootloader as it says failed when I try doing so using fastboot and says it cannot be officially unlocked when using flashtool. Worryingly for me, in settings it now says "no" for unlock allowed (it used to say "Yes").
So now, I've got a phone that otherwise works normally again except that it doesn't actually work as a mobile phone! Please help me someone as Sony have already refused to do anything to help, their customer (dis)service people simply point out that once you unlock the bootloader - even if that itself causes the problem - they will no longer help you. Cheers, thanks Sony, no way will I ever buy any product from you ever again!
What a crap day...
andrewh1973 said:
Hi everyone
I wanted to try going from the stock Android 4.3 to cm12.1.
My phone was bootloader locked but unlocking was allowed.
So I followed the process on the sony website and got the unlock code and entered it.
Phone then refused to restart, stuck on booting screen.
Eventually using Flashtool, I found a stock rom and reflashed that, still wouldn't boot. Then I relocked the bootloader and now it boots again.
However, it now says sim card is invalid and refuses to let me join the phone network (I'm in Malta, using the Go network).
Also, I'm now unable to reunlock the bootloader as it says failed when I try doing so using fastboot and says it cannot be officially unlocked when using flashtool. Worryingly for me, in settings it now says "no" for unlock allowed (it used to say "Yes").
So now, I've got a phone that otherwise works normally again except that it doesn't actually work as a mobile phone! Please help me someone as Sony have already refused to do anything to help, their customer (dis)service people simply point out that once you unlock the bootloader - even if that itself causes the problem - they will no longer help you. Cheers, thanks Sony, no way will I ever buy any product from you ever again!
What a crap day...
Click to expand...
Click to collapse
i think you have missing something after unlock bootloader, and you can't give any wrong or false to sony. because you're do this with your vault and you're is vault your warranty. and sony have give you a warn sign before do this, and you accepted because you do it.
so no any vendor problem if you fail or your device is bricked.
after unlock bootloader, you need to reflash your stock rom again and do a full wipe data and cache from flashtool before flash any rom. after wipe and flash you can check your device is boot up perfectly without any problem. you only missed that. try to reunlock if still can, but try to unlock your bootloader using flashtool too.
Nicklas Van Dam said:
i think you have missing something after unlock bootloader, and you can't give any wrong or false to sony. because you're do this with your vault and you're is vault your warranty. and sony have give you a warn sign before do this, and you accepted because you do it.
so no any vendor problem if you fail or your device is bricked.
after unlock bootloader, you need to reflash your stock rom again and do a full wipe data and cache from flashtool before flash any rom. after wipe and flash you can check your device is boot up perfectly without any problem. you only missed that. try to reunlock if still can, but try to unlock your bootloader using flashtool too.
Click to expand...
Click to collapse
Well on Sony's site it also says that any repair will be chargeable once you do unlock, so I would have expected them to have done something at a charge not to totally refuse to help at all. I accept what you say but I DID follow the instructions exactly, I unlocked the bootloader and rebooted it as instructed and from there it went wrong - refused to boot.
Anyway, I have tried several stock roms including even using the Sony tools and letting it do a "repair" reflash, all to no avail. "Sim Invalid" is what I'm left with and what I have noticed when flashing every stock rom with flashtool, what is missing from the "Wipe" list is cache, the only option there is "USERDATA". Is there something wrong with the flashtool perhaps?
Even when I relock the bootloader using flashtool (which I seem to need to do every time even after flashing a stock rom) it still seems to regard the phone as unlocked, or at least when you go the "BLU" screen it shows only the option to relock each time. Something has definitely screwed up here.
I got a UK stock rom via Xperifirm and used Flashtool to create the TFT from that. Still no joy. I'm assuming something is wrong with the sim lock, somehow, but how to fix this? I'm realising that reflashing stock roms doesn't totally return the phone to factory condition, so what am I missing here please? Is the phone totally stuffed now or is there still some way to repair it?
Ok so further to this, I just gone into service menu -> Sim lock and I see this:
[x] Network 0
[x] Network subset 0
[x] Service provider 0
[x] Corporate 0
[x] SIM 0
So is the phone locked or not? What does the x mean? The phone was previously fully sim unlocked as I bought it without a contract from Amazon. Is there a way to fix this please?
help me please
i have xperia m, after unlocking bootloader it stuck on bootlooping, i have not enable usb debugging...any way to fix it?
I unlocked my bootloader several months ago, but now my SIM card readers (both of them) have gone out. I have no idea how, no water damage or anything like that has happened. They just stopped working. So I went complete stock firmware, locked bootloader, everything but I am still unable to take OTA updates like a new phone would be able to. I think this is because they banned my device from OTAs which I believe they do if you have messed with the device. I need to RMA my device so my question is would it be better to say that I didn't tamper with the device and run the risk of them finding out I did, which is pretty likely seeing as how my device has been banned from OTA updates, or tell them that I did unlock it and all of that but that I have relocked it and I am back to stock? If any of you have had a similar issue how did ASUS handle that? Thanks!
E3AANG11E3 said:
I unlocked my bootloader several months ago, but now my SIM card readers (both of them) have gone out. I have no idea how, no water damage or anything like that has happened. They just stopped working. So I went complete stock firmware, locked bootloader, and all of that but that I have relocked it.
Click to expand...
Click to collapse
How to you relock bootloader?
mr_gourav2000 said:
How to you relock bootloader?
Click to expand...
Click to collapse
Since I am a new user I cannot post links. But Google "Zenfone 2 bootloader unlock" and I followed the instructions of Grekky's Blog.
there is no such thing as relocking the bootloader. only thing you can do it flash the stock image to make it look stock (since an unlocked bootloader has a white splash screen) but im sure asus knows of this and will still check and see that the bootloader is indeed unlocked and not warranty it.
This is just something we all accepted as a consequence of unlocking our bootloaders. hell i have a screen thats getting worse and worse with a yellow/brownish line coming from the top of the phone, but alas i have an unlocked phone too.
You can replace the white splash screen by flashing a black splash screen image to try and cover up unlocking your bootloader. http://forum.xda-developers.com/zenfone2/themes-apps/551-black-white-splashscreen-twrp-flash-t3141945 . If the reseller has no clue about custom recoveries and trying to flash a rom you'll be safe.
They fixed it, no questions asked. And yes, I was able to relock the bootloader.
I recently got a new motherboard installed to my Nexus 5X by LG due to the recent bootloop related to TWRP and Android N. My problem is that after unlocking bootloader, and doing the mandatory device wipe that comes with it, the bootloader gets reverted to locked state when I restart my device. I've tried multiple cables, USB ports, fastboot binaries, but nothing seems to make the device behave any differently. I am able to flash things in fastboot mode after unlocking the device as long as I don't restart the device. TWRP installs just fine, but obviously throws a bunch of errors because I cannot enter recovery mode without restaring (which gets the bootloader locked again). Is there any tricks I could try, or is it my NAND that is acting up as it seems to revert to previous state on power loss? As far as I can tell, the rest of the memory chip is working just fine, /sdcard does not lose any data when restarting etc. I was able to install Nougat on the device by flashing factory images.
I have not bought my device from Google and thus it is covered only by LG's limited warranty, which probably means that this is something they will not repair as unlocking the bootloader probably voids their warranty in any case. Am I just out of luck?
neree said:
I recently got a new motherboard installed to my Nexus 5X by LG due to the recent bootloop related to TWRP and Android N. My problem is that after unlocking bootloader, and doing the mandatory device wipe that comes with it, the bootloader gets reverted to locked state when I restart my device. I've tried multiple cables, USB ports, fastboot binaries, but nothing seems to make the device behave any differently. I am able to flash things in fastboot mode after unlocking the device as long as I don't restart the device. TWRP installs just fine, but obviously throws a bunch of errors because I cannot enter recovery mode without restaring (which gets the bootloader locked again). Is there any tricks I could try, or is it my NAND that is acting up as it seems to revert to previous state on power loss? As far as I can tell, the rest of the memory chip is working just fine, /sdcard does not lose any data when restarting etc. I was able to install Nougat on the device by flashing factory images.
I have not bought my device from Google and thus it is covered only by LG's limited warranty, which probably means that this is something they will not repair as unlocking the bootloader probably voids their warranty in any case. Am I just out of luck?
Click to expand...
Click to collapse
What TWRP errors are you getting? TWRP shouldn't care if your device is locked or not. It doesn't do its operations through the bootloader.
Also just as a sanity check, you enabled OEM unlocking under developer options and you did fastboot oem unlock (or equivalent) on the phone right?
sfhub said:
What TWRP errors are you getting? TWRP shouldn't care if your device is locked or not. It doesn't do its operations through the bootloader.
Also just as a sanity check, you enabled OEM unlocking under developer options and you did fastboot oem unlock (or equivalent) on the phone right?
Click to expand...
Click to collapse
For the TWRP errors I'll have to get back on when I get back home to my device. For the other part, yes I did enable the unlocking under dev options, and used fastboot flashing unlock (also tried fastboot oem unlock). They both do go through and wipe my device. The bootloader also stats that current state is unlocked after the wipe. However after restaring the device back to bootloader causes the state change back to locked.
Did you install the motherboard or did LG?
I think something didn't install correctly on your phone. There is probably somewhere on the phone where they store the persistent unlocked state of the bootloader and that isn't working.
If you are bold, you can try using LGUP and the TOT file to reinstall you phone (this is a more in-depth reinstall than just factory images)
However there is always the risk you make things worse on your phone than they currently are.
If you have 16GB then you need to install the Android N OTA afterwards to get the partition tables set correctly.
sfhub said:
Did you install the motherboard or did LG?
I think something didn't install correctly on your phone. There is probably somewhere on the phone where they store the persistent unlocked state of the bootloader and that isn't working.
If you are bold, you can try using LGUP and the TOT file to reinstall you phone (this is a more in-depth reinstall than just factory images)
However there is always the risk you make things worse on your phone than they currently are.
If you have 16GB then you need to install the Android N OTA afterwards to get the partition tables set correctly.
Click to expand...
Click to collapse
LG (or whatever company it is that does it for them here) installed the new board. I think I'll pass on doing the deeper installations for now as I'm currently trying to sell the device off to someone who wouldn't have any use to unlocked bootloader. Was just wondering if I completely missed something that might cause the device to do this so I could either use it again by myself or sell it as fully functioning Nexus device.
neree said:
I think I'll pass on doing the deeper installations for now as I'm currently trying to sell the device off to someone who wouldn't have any use to unlocked bootloader.
Click to expand...
Click to collapse
That's a good call. Actually I wouldn't mess around too much with the phone if you are going to sell it.
Just make sure you remove any pin/pattern/password from the phone and to be extra safe, remove your google account from the phone *PRIOR* to factory reset or you will run into Factory Reset Protection (FRP) where you will have to give the buyer your google account and password so they can do first install and switch to their own account.
Hi,
I have recently bought a T-mobile version of OP7T. Even though T-Mobile unlocked the network permanently, I still didn't like T-mobile branding at the start, plus I wanted Stock OxygenOs. So what did I do?
(No root and No TWRP)
1. I've Unlocked the bootloader via the method in this post. Stage-1
2. I have flashed the stock rom which I downloaded from this post. Stage-2
3. Phone loads up perfectly fine and now I have stock OOS. to make sure everything is fine, I also did a factory reset and re-flashed the stock rom to make sure there's no track of previous roms.
4. I then wanted to relock the bootloader in order to keep my device safe and enjoy having a normal device like any others without the ugly message at the startup.
5. So I put it in fastboot mode and executed "fastboot flashing lock" or "fastboot oem lock" and it gave me the options and I locked the bootloader.
6. after this, I can't do anything else. it keeps showing me the page where it says Your device is corrupt. It can't be trusted and will not boot and in order to get rid of I need to keep unlocking the devices relfashing everything and the rest of the story.
I've read all the accurate and inaccurate infos on forums where another guy claims when he did turn everything to stock (recovery + rom + factory reset) things go back to normal and he's done. in my case it doesn't work.
Please help me, how I can be able to relock the bootloader without running into Your device is corrupt. It can't be trusted and will not boot.
Thanks.
First I think no help is stupid, since that is the regular way of doing it. Second you should have read extensively before doing what you did. T-mobile is very specific device. What he probably didn't mention is that you need the original rom t-mobile branded, since you need original software to be able to relock bootloader. I would recommend use msm- tool to recover you device. Read carefully and next time just be sure that what you are doing is informed.
I have unlocked the device and installed everything. the phone works like a charm.
My only problem is that I can't re-lock the bootloader.
bahadorkh said:
I have unlocked the device and installed everything. the phone works like a charm.
My only problem is that I can't re-lock the bootloader.
Click to expand...
Click to collapse
That was my point in order to relock your device you must have the original firmware that the phone came with if it's t-mobile. Installed in both slots. Then you can relock you device.
Please try this thread
[OP7T T-MOBILE][OOS 11.0.1.5 HD63CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
After the first boot you must update via OTA, then after the 7T reboots you can go back into the bootloader and relock it. I'm typing this message out on my T-Mobile 7T running the Global OOS 11 version. _ANY_ modification to the system whatsoever will cause the "Device is Corrupt" error, due to a mismatch of the keys used by OnePlus to sign the firmware. I've attached a screenshot of my "About phone" section as proof of the conversion, however, I can't show proof of my bootloader's state because I don't have access to a PC at the moment and *#*#7378423#*#* didn't work, neither did *#*#7378423*#*#. If I remember to the next time I'm near a PC I'll add proof of that too.
For further reading see::
1.) https://source.android.com/security/verifiedboot/boot-flow#locked-devices-with-custom-key-set
And
2.) https://source.android.com/security/verifiedboot/dm-verity
P.s. I do realize that I'm almost a year late to this discussion, but I thought knowing would/could still be useful to someone.
A month ago I bricked my G40 fusion. It was in "flashing locked" state which meant I could not send any commands over fastboot.
EDL mode was of no use as there were no QFIL files available for the phone.
I paid a tech to bring my phone back to life but I do not know everything he did. I am posting what I know about the process. I understand that repair techs are dependent on income from these situations so understand that I am only posting about the limited things I know.
Process-
Phone was kept in fastboot mode(flashing locked)
MotoflashPro was used to gain information on device status.
Accessed MotounlockGsm.com through CMD(BAT file) and used usb over server to connect phone to it.
Thingamajingy happened and phone now entered "oem_locked" state.
used motoflashpro tool to flash stock rom
booted to recovery
hard reset phone
reboot.
Phone now works like before. No bootloader unlocked warnings on startup. Tech said custom roms should no longer be flashed and phone needs to be used as it is now.
My phone is Indian variant but Indian rom failed to flash. Global retail rom was flashed and works just fine.
vamsi53 said:
Tech said custom roms should no longer be flashed and phone needs to be used as it is now.
Click to expand...
Click to collapse
So, you can't able to unlock bootloader now?
HemanthJabalpuri said:
So, you can't able to unlock bootloader now?
Click to expand...
Click to collapse
Yes. He can't.