Related
Hi Everyone i got a Quite new Nexus 4.
Im tired of waiting for the OTA and decided to move on to flash in the Factory Images.
As ive been reading on alot of places it says it ruins my warranty. but according to the EU Directives it does not ruin my Hardware Warranty.
So what would you do? would you open the bootloader flash in 4.4 and lock the bootloader. is there anyway the Serviceman can see that only the bootloader been opened if i lock it directly afterwards?
best regards.
Not sure what you mean about the bootloader. Yes u can unlock and lock the bootloader. After you lock it back; no there is not to tell if it was unlocked. If you want to upgrade to 4.4; follow this guide.
badboy47 said:
Not sure what you mean about the bootloader. Yes u can unlock and lock the bootloader. After you lock it back; no there is not to tell if it was unlocked. If you want to upgrade to 4.4; follow this guide.
Click to expand...
Click to collapse
I mean People have had trouble when they have been at a Official Servicecenter.
Apparently the servicecenter said that the customer have had a open bootloader then locked it before going to repair, so the Servicecenter refused to repair the phone.
I dont know if its a myth or not?
so its 100 % secure not damaging any hardware just unlocking the bootloader with nexus toolkit.
Eastliin said:
Hi Everyone i got a Quite new Nexus 4.
Im tired of waiting for the OTA and decided to move on to flash in the Factory Images.
As ive been reading on alot of places it says it ruins my warranty. but according to the EU Directives it does not ruin my Hardware Warranty.
So what would you do? would you open the bootloader flash in 4.4 and lock the bootloader. is there anyway the Serviceman can see that only the bootloader been opened if i lock it directly afterwards?
best regards.
Click to expand...
Click to collapse
I don't know a damn thing about EU Directives. But, I've never heard of google refusing to honor a warranty on a Nexus because the bootloader was unlocked. That's kind of expected on a Nexus, and that's why google makes it so easy to do. It's not like other phones that need to utilize some exploit to do it. There is very little that can go wrong. And it can almost always be fixed by flashing another factory image again.
If it was me, I would have unlocked the bootloader the day I bought it, because unlocking it will wipe your data now. There is no way around that. But if I were you, yes I would unlock it and install whatever you want to. Locking it up again is an option. But if you want to unlock again later, you will have to wipe data, again.
iowabeakster said:
I don't know a damn thing about EU Directives. But, I've never heard of google refusing to honor a warranty on a Nexus because the bootloader was unlocked. That's kind of expected on a Nexus, and that's why google makes it so easy to do. It's not like other phones that need to utilize some exploit to do it. There is very little that can go wrong. And it can almost always be fixed by flashing another factory image again.
If it was me, I would have unlocked the bootloader the day I bought it, because unlocking it will wipe your data now. There is no way around that. But if I were you, yes I would unlock it and install whatever you want to. Locking it up again is an option. But if you want to unlock again later, you will have to wipe data when you unlock in the future.
Click to expand...
Click to collapse
here is a link to the directive im talking about.
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
I do wipes from time to time to keep the phone fresh so thats noo worries at all for me.
so for me its just getting toolkit, open bootloader, flash 4.4 then lock the bootloader no harm done?
Eastliin said:
here is a link to the directive im talking about.
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
I do wipes from time to time to keep the phone fresh so thats noo worries at all for me.
so for me its just getting toolkit, open bootloader, flash 4.4 then lock the bootloader no harm done?
Click to expand...
Click to collapse
I also don't know anything about toolkits, I use linux and adb/fastboot (nerd).
But yes, unlock booloader, flash the new factory images, and relock it again if you want. Like I said, unlocking a Nexus is not some taboo process to google. Simply unlocking it won't void your warranty.
They only way you can void your warranty is abuse (dropping it, getting it wet, etc) , or installing BAD software that causes the hardware to malfunction. If you are installing google's factory images, you have nothing to worry about.
iowabeakster said:
I also don't know anything about toolkits, I use linux and adb/fastboot (nerd).
But yes, unlock booloader, flash the new factory images, and relock it again if you want. Like I said, unlocking a Nexus is not some taboo process to google. Simply unlocking it won't void your warranty.
They only way you can void your warranty is abuse (dropping it, getting it wet, etc) , or installing BAD software that causes the hardware to malfunction. If you are installing google's factory images, you have nothing to worry about.
Click to expand...
Click to collapse
ye i will follow a guide,
i know its ok to unlock bootloader by google, but LG that does the repair in sweden screams NONO haha
Eastliin said:
ye i will follow a guide,
i know its ok to unlock bootloader by google, but LG that does the repair in sweden screams NONO haha
Click to expand...
Click to collapse
actualy google says to unlock,flash and then relock for"security purposes".
opssemnik said:
actualy google says to unlock,flash and then relock for"security purposes".
Click to expand...
Click to collapse
Thats fun haha, you got a link of where they state that?
Eastliin said:
Thats fun haha, you got a link of where they state that?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images?hl=pt-BR
"After restoring a factory image,lock the bootloader for security reasons." almost at bottom of page, after all the images. on instructions part.
opssemnik said:
https://developers.google.com/android/nexus/images?hl=pt-BR
"After restoring a factory image,lock the bootloader for security reasons." almost at bottom of page, after all the images. on instructions part.
Click to expand...
Click to collapse
so with that link LG cant screw me at all! when it comes to repairing a phone.
Thx alot!
Eastliin said:
so with that link LG cant screw me at all! when it comes to repairing a phone.
Thx alot!
Click to expand...
Click to collapse
^, they tried to screw with me, but as i know lg here in brasil, i carried a book of "consumers defense code", i showed them the link,and the guy from the service center had to get my n4 and fix for no fee (my screen was broken, and no touch, but the screen broke because of overheating).
Is it possible to re-lock and unlocked bootloader?
I know updating should get rid of an unlocked bootloader, but I still get the warning screen on bootup.
Reason I ask is because I had it unlocked, got an OTA update from Verizon for kitkat, and soft bricked my phone. Got stuck in a boot loop with the unlocked bootloader warning message.
I just flashed back to 4.0.4 using RDS Lite 6.1.4. Id like to reset the boot loader to locked before updating to kitkat again.
It's not possible to re-lock. I've updated to KK and can confirm that the BL is, in fact, still unlocked.
I have read somewhere that when you unlock the bootloader, it actually physically blows some kind of physical fuse. or maybe I miusread it.
Someone had made a special logo.img you can flash to get rid of that message.
Although if you really want a locked BL phone, I'd be more than happy to trade you.
MxPhenom 216 said:
I know updating should get rid of an unlocked bootloader, but I still get the warning screen on bootup.
Click to expand...
Click to collapse
Not that it helps, but in Australia, we do not get the nasty warning message after unlocking the bootloader. And I think that the phones are actually sold with an unlocked bootloader.
GnatGoSplat said:
Although if you really want a locked BL phone, I'd be more than happy to trade you.
Click to expand...
Click to collapse
:laugh:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Why would you want to do this?
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Is there any way to remove the Bootloader unlock warning ⚠ without relocking bootloader?
Sent from my XT1572 using Tapatalk
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Theres no reason really to relock it. Once its unlocked, the bootloader will show that it was unlocked regardless if you relock it.
atishey23 said:
Is there any way to remove the Bootloader unlock warning without relocking bootloader?
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
Yes
Pyramid Head said:
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Click to expand...
Click to collapse
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
psandeepn said:
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
Click to expand...
Click to collapse
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
jason2678 said:
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
Click to expand...
Click to collapse
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
The answer is maybe... it depends what you have changed and what this OTA updater script actually checks for.
We know that a stock bootloader (which can be unlocked, that is not relevant), stock recovery, and stock system image are required to take an OTA. If the system image has been modified it can fail, and we know the updater has the ability to see if /system has EVER been mounted R/W and can fail for that condition although so far it doesn't seem Moto is going that extreme.
We do know a modified logo does not affect an OTA, in fact, you can even relock the bootloader with a modified logo so it must not be a significant check.
jason2678 said:
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
Click to expand...
Click to collapse
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
iks8 said:
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
Click to expand...
Click to collapse
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
acejavelin said:
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
Click to expand...
Click to collapse
You're right sorry
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
.G33K said:
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
Click to expand...
Click to collapse
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Heisenberg said:
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Click to expand...
Click to collapse
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
.G33K said:
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
Click to expand...
Click to collapse
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Heisenberg said:
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Click to expand...
Click to collapse
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
.G33K said:
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
Click to expand...
Click to collapse
Did you format userdata? It's worth a try.
Heisenberg said:
Did you format userdata? It's worth a try.
Click to expand...
Click to collapse
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
.G33K said:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
Click to expand...
Click to collapse
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.
So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that
I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.
Hi There,
Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.
However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?
Meanwhile, all my fastboot commands are working with no issues at all.
EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
TemplesOfSyrinx said:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
Click to expand...
Click to collapse
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
This happened to my wife's phone, sent back to Bell. Will see what happens.
TemplesOfSyrinx said:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?
TemplesOfSyrinx said:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
Click to expand...
Click to collapse
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.
Hi.
I just bought myself a used nexus 6p and im thinking of rooting it to get some more customization done
Before i only used Samsung phones which had this flash counter thing and then knox that kept the number of flashes to void the warranty and all. Is there this kind of measure on 6p or it's just the same as it was before {no triangles or anything) when i flash stock and lock the bootloader after i change my mind?
McXred said:
Hi.
I just bought myself a used nexus 6p and im thinking of rooting it to get some more customization done
Before i only used Samsung phones which had this flash counter thing and then knox that kept the number of flashes to void the warranty and all. Is there this kind of measure on 6p or it's just the same as it was before {no triangles or anything) when i flash stock and lock the bootloader after i change my mind?
Click to expand...
Click to collapse
No, only samjunk does stupid **** like that.
If your BL is unlocked which it should be if you are on anything other than stock, you will see a warning message each time you boot the phone. And before you act like you have ocd or something, NO that message can not be removed.
Lawlrus said:
No, only samjunk does stupid **** like that.
If your BL is unlocked which it should be if you are on anything other than stock, you will see a warning message each time you boot the phone. And before you act like you have ocd or something, NO that message can not be removed.
Click to expand...
Click to collapse
I haven't unlocked the bl yet as there was no point since I didn't want to root before I got the answer from you. I know how to read tutorials and I'm very familiar with flashing so that's no probs for me. Doesn't the message disappear after you lock the bootloader? (Just assume that I went to custom ROM didn't like it got back to stock ROM and locked the bl) will the message still be there? Because I think it says 'your phone can't be checked for corruption" but it says so only if the bl is unlocked not all the time after it's been unlocked doesn't it?
McXred said:
I haven't unlocked the bl yet as there was no point since I didn't want to root before I got the answer from you. I know how to read tutorials and I'm very familiar with flashing so that's no probs for me. Doesn't the message disappear after you lock the bootloader? (Just assume that I went to custom ROM didn't like it got back to stock ROM and locked the bl) will the message still be there? Because I think it says 'your phone can't be checked for corruption" but it says so only if the bl is unlocked not all the time after it's been unlocked doesn't it?
Click to expand...
Click to collapse
Right, it shows that message when the BL is unlocked, once you relock your BL that *should* go away, never tried it because I don't plan on even being back on stock with no root.
If you do any modifications to the device even root, or using a stock custom ROM like we have, it is suggested to NOT relock your BL, while on it. Keep that in mind.
You want to go back to full stock to lock it, then reflash the factory image