Related
oepete.com/n1update.htm
This has been discussed in other threads -- The problem here, however is that you still have to unlock the bootloader, so you are no longer left with a "stock" N1 and warranty is voided.
The easier 'equivalent' method is just to unlock the bootloader, install the custom recovery menu and then install the Modaco rooted 2.2. update.zip.
people keep saying this but warrantly is NOT voided.. you cannot void the warranty for s/w changes.. if there is a hardware issue htc has said and has honored their warranty.. now if you get the phone all fubared because of some software issue and cannot figure out how to recover or reinstall kernal, radio etc. then yes they may not cover it.
lgkahn, what do you base your statement on? Documentation clearly states that unlocking the bootloader will void your warranty. Once warranty is voided, it is really up to HTC to decide if they want to honour your no longer existing hardware warranty or not. There are people here that have successfully negotiated hardware repairs even after unlocking the bootloaders, but others who have not been able to if, I understand things correctly.
If you have any solid contrary information, please let us know. Thank you
Not to mention one of the latest posts is a guy trying to clean out the dust from behind his screen because HTC will not honor his warranty.
not true at all if you read the dust issue post it is because he knows he will bet another refurb if he warranties it.. not because they will not honor it.
gotta love spam
lgkahn said:
people keep saying this but warrantly is NOT voided.. you cannot void the warranty for s/w changes.. if there is a hardware issue htc has said and has honored their warranty.. now if you get the phone all fubared because of some software issue and cannot figure out how to recover or reinstall kernal, radio etc. then yes they may not cover it.
Click to expand...
Click to collapse
There has been a lot of discussion here of people who had their warrantied devices returned to them untouched because their bootloader was unlocked. Not all the time, but it may happen if you do that. The guide above is misleading because it does mention that your device will no longer remain stock.
Closing this thread as the original poster has already posted this in another thread... no need to start a brand new one.
In this thread I intend to give some basic insight about these two concepts, which are closely entwined with our phone's experience. I'm not a tech guy, but I think this little summary might clear some doubts for people who are new to this kind of issues (people who come from other non-Android phones especially). All feedback is welcome, in particular the one of people who can expand the topic with their knowledge.
"Root" is the common way to refer to the fact to the user account which has superuser rights on the device. Superuser rights imply full control over your phone's capacities, which are determined by the software and the hardware of the device. Non-superuser accounts have limitations, usually established for the sake of software security (for example, not allowing a user to disable critical functions such as phone or GPS), hardware safety (not allowing to change the processor's frequency speed, aka overclocking the CPU) or, in some cases, for someone's profit (disabling wi-fi tethering is a typical one as users are forced to buy data plans in order to use their devices to tether). In Android's case, Superuser is composed of an app* and a set of instructions to give this app root rights.
The bootloader is a program which accesses the internal storage and, basically, controls the loading of the programs and data necessary to initiate the sequence of launching the OS (aka booting, thus the name bootloader). We say that a bootloader is locked when it is programmed in such a way that it won't allow to load the device if it detects data from third-party sources. Unlocked bootloaders do allow these data and will load what these data contain, which will be usually a modified version of the phone's firmware, known as "Custom ROM".
As we can see, there was the fear that one would need to have unlocked bootloaders (i.e the ability to load third-party data in the booting sequence) in order to gain root rights. This would have been terribly inconvenient because only a minority of users will have unlocked bootloaders, since the phones with unlocked bootloaders by default are the ones sold carrier-unlocked. Said carrier-free phones will be a minority as the phone is pretty expensive: most Xperia Plays will be sold using carrier subsidies.
However, our fellow member Chainfire found an exploit (a programming loophole) in Gingerbread which allows said app and instructions to be loaded without the need of touching the bootloaders. Basically, his Gingerbreak program allows the user to have root rights without loading any bootloader-sensitive data. This widens the possibilities for the majority of users who will buy this phone with a subsidy.
*edit 3* Later on, it has become possible to unlock the bootloader even for SIM-locked devices, thanks to different unlockers like Alejandrissimo and Jinx13. This means that, provided that you pay what they charge, you can have your device set up without the bothers of having to buy a SIM-free phone. What's better: their method of unlocking the bootloader SIM-unlocks the phone as well.
I think this is more or less a succint framework of ideas which allows us to define "root" and "unlocked bootloaders" properly. As they say, knowing is half the battle, so I hope this nugget of information allows users to deal with their phones with more confidence.
*edit* as of version 2.3.3, this information has changed. Gingerbreak doesn't work with 2.3.3 anymore, and it seems now that the only way to root with locked bootloaders is to flash a 2.3.2 rom with FlashTool and update through OTA.
*edit2* note that this explanations pertains mostly to the Xperia Play. Other devices are NAND-locked, which means for us that they need unlocked bootloaders to even get root access.
*Note that Android is built in such a way that every app is a user account with limited rights (the ones specified before you download it). Thus, Superuser is a user account as any other app and the set of instructions is meant to give this user account root rights.
Thank you! This was very helpful in clarifying some things.
"As we can see, there was the fear that one would need to have unlocked bootloaders (i.e the ability to load third-party data in the booting sequence) in order to gain root rights. This would have been terribly inconvenient because only a minority of users will have unlocked bootloaders, since the phones with unlocked bootloaders by default are the ones sold carrier-unlocked. Said carrier-free phones will be a minority as the phone is pretty expensive: most Xperia Plays will be sold using carrier subsidies"
by carrier unlocked do you mean sim unlocked? sorry 4 noob question
Indeed, that is what I mean.
Logseman said:
Indeed, that is what I mean.
Click to expand...
Click to collapse
Alright, I asked this question and it was answered, but I want to make sure before I try anything.
I just found out from SE that my phone is the Rogers version. It's obviously been unlocked because I'm using it on AT&T.
What I don't know, though, is whether the bootloader is unlocked. Another member recommended that I check TrackID to see if it worked because it depends on the manufacturer DRM's that are wiped in unlocking the bootloader. It did work, so I assume it's still locked, but I wanted to confirm because of being carrier unlocked.
Sent from my R800a using XDA App
If TrackID works, your bootloader is locked, regardless of simlock.
I have a Sim-Unlocked Xperia Play from Rogers that I am using on ATT's network. My phone is boot-locked. When powered off, if I hold the search key while plugging in the USB cable, I do not get a blue light.
I was able to flash the firmware by holding the back key while plugging in the usb cable (with the phone off). I get a green light when I do this. Using flashtool, I was able get 2.3.3 rooted by loading the 2.3.2 firmware, rooting, and then updating OTA.
I bricked my phone several times while loading the firmware and each time I was able to fix it with flashtool or Sony Ericsson's Upgrade Utility. I found that you need a good USB cable, and even then it failed sometimes. I just kept trying and eventually it worked.
We wanted to provide an update on HTC’s progress with bringing bootloader unlocking to our newest phones. We know how excited some of you are for this capability, and we’ve put significant resources behind making this change as soon as possible. While we wish we could flip a simple switch and unlock all bootloaders across our device portfolio, this is actually a complex challenge that requires a new software build and extensive testing to deliver the best possible customer experience.
We’re thrilled to announce today that software updates to support bootloader unlocking will begin rolling out in August for the global HTC Sensation, followed by the HTC Sensation 4G on T-Mobile USA and the HTC EVO 3D on Sprint. We’re in the testing phase for the unlocking capability now, and we expect it to be fully operational by early September for devices that have received the software updates. We'll continue rolling out the unlocking capability over time to other devices as part of maintenance releases and new shipments.
HTC continues its commitment to unlocking bootloaders and supporting the developer community. Because of the importance of this community to us, please expect an update on this about every few weeks as we make progress toward launch. Thank you for your patience and continued support!
(they claim it will come to only two devices for starters the EVO 3D and the Sensation 4G and then it will slowly rollout to other devices that already have 2.3 or enough internal memory on them, this will all start in last August an early September for the first two droids listed... and others will soon follow suit, the only question is do you want you bootloader to come unlocked stock? Or will you buy it locked and be able to sit around and wait for your device to get an update to do so?? LOL
thats why my phone couldnt flash back to 2.3.2..(?)
I live in singapore.. phones are not carrier specific.. so does that mean my BL was unlocked even before I used gingerbreak?
I know this doesnt pertain to the play per se, but maybe you should add that, with nand locked devices, an unlocked bootloader is required to acheive full root, just incase someone with another device googles this question and ends up here
pros and cons of unlocked bootloader
Pros/Cons of rooting WITHOUT unlocking bootloader?
Since being interested in rooting my N1 I've been googling a lot but it's still somewhat confusing. One of the things that's making me hesitent is the idea of permanently (as of the date of this post) unlocking the phone and thus clearly/visibly voiding the warranty.
I've recently stumbled upon instructions for rooting without unlocking the bootloader? Am I correct in assuming this would make the phone appear (no unlock icon) to be unmodified? Also, does this mean one could fully reverse the rooting process and go back to fully stock google signed roms with OTA updates etc (essentially reverting it back as if it were never modified)?
It would seem this would be preferable to any method involving the unlocking of the bootloader. Are there any disadvantages of this? Any increased risks by NOT unlocking the bootloader? Is there a reason why most people have gone the rout of unlocking the bootloader?
My plan is simply to have root access to run setcpu on the stock FRF91 rom. As of now, I'm not interested in other ROMs (baby steps).
tommyinhi27 said:
Pros/Cons of rooting WITHOUT unlocking bootloader?
Since being interested in rooting my N1 I've been googling a lot but it's still somewhat confusing. One of the things that's making me hesitent is the idea of permanently (as of the date of this post) unlocking the phone and thus clearly/visibly voiding the warranty.
I've recently stumbled upon instructions for rooting without unlocking the bootloader? Am I correct in assuming this would make the phone appear (no unlock icon) to be unmodified? Also, does this mean one could fully reverse the rooting process and go back to fully stock google signed roms with OTA updates etc (essentially reverting it back as if it were never modified)?
It would seem this would be preferable to any method involving the unlocking of the bootloader. Are there any disadvantages of this? Any increased risks by NOT unlocking the bootloader? Is there a reason why most people have gone the rout of unlocking the bootloader?
My plan is simply to have root access to run setcpu on the stock FRF91 rom. As of now, I'm not interested in other ROMs (baby steps).
Click to expand...
Click to collapse
The N1 is made by HTC, generaly with htc devices, flashing a stock rom, will re-lock the bootloader, If you decide just to root, you will need a custom kernel before you can O/C All that unlocking the bootloader does is 2 things, It will security unlock the nand (on nand locked devices) allowing r/w access to read only partitions, and it allows you to issue fastboot commands to your device, the main reason alot of play owners went down the unlocking the bootloader path, is that atm it is the only way to flash custom roms other devices, have found sneaky ways to push a custom recovery without unlocking bootloaders, and thus do not need one to flash a custom rom
AndroHero said:
I know this doesnt pertain to the play per se, but maybe you should add that, with nand locked devices, an unlocked bootloader is required to acheive full root, just incase someone with another device googles this question and ends up here
Click to expand...
Click to collapse
I'm not too knowledgeable about the whole Nand thing, so I think you could give a much better explanation about it. I'll include it then
whoa whoa whoa!!!! i achieved root on 2.3.3 with no prob using superoneclick v2.3.3. it works beautifully!
Yes, but you're replying to a thread that's 8 months out of date too!
Sent from my R800x using XDA
Lol. I know, but I've been trolling the site, and I think it may need a bit of new info so someone doesn't follow the steps here now that a better method has been found.
Sent from my R800at using XDA
isavegas said:
Lol. I know, but I've been trolling the site, and I think it may need a bit of new info so someone doesn't follow the steps here now that a better method has been found.
Sent from my R800at using XDA
Click to expand...
Click to collapse
why not just stop bumping heavily old threads? then they can rest in piece
and nobody would care
the information thatit's outdated is alreada given in 1st post.
u also could ask a mod to close this as its outdated...
Hey, this thread may be outdated, but it's not my fault if someone necros old threads. Just let it die.
question
can i flash custom roms in a locked bootloader?
yes
big txmer said:
can i flash custom roms in a locked bootloader?
Click to expand...
Click to collapse
only stock gb ones nothing else
My phone, the Motorola Razr HD LTE is out already since November 2012, with not as much development options as other phones.
Compare to SG3 or the Nexus 4 (newly released), it leave us with very little options when it comes to custom ROMS or functional improvements.
Some of the uncertainty is coming from the lack of communication, between the developers and the community of users, on ongoing technical issues with no solution insight (example: the Rogers issue versions 492002 vs. 49003)
The best available custom ROM is currently uncompleted, and again no communication or reassurance on the work progression.
The truth to matter is that we are lagging behind other phones when it comes to development & improvements.
Figure out a way to unlock the bootloader and you will probably see more development on this phone.
You are not your iPhone 5
#tylerdurden
I agree. I holding back doing anything because of losing the warranty.
I have to say though my XT925 is one of the first Android phones that came to me stock without the bloat I've found on Sony, LG and Samsung devices. I'm still very happy with my stock Razr HD.
SFG said:
Figure out a way to unlock the bootloader and you will probably see more development on this phone.
You are not your iPhone 5
#tylerdurden
Click to expand...
Click to collapse
There already is a bootloader unlock. You can use the motorola bootloader unlock tool. I don't have a developer edition and it worked perfect for me. Other users in the forum also have their bootloaders unlocked.
itzik_man said:
My phone, the Motorola Razr HD LTE is out already since November 2012, with not as much development options as other phones.
Compare to SG3 or the Nexus 4 (newly released), it leave us with very little options when it comes to custom ROMS or functional improvements.
Some of the uncertainty is coming from the lack of communication, between the developers and the community of users, on ongoing technical issues with no solution insight (example: the Rogers issue versions 492002 vs. 49003)
The best available custom ROM is currently uncompleted, and again no communication or reassurance on the work progression.
The truth to matter is that we are lagging behind other phones when it comes to development & improvements.
Click to expand...
Click to collapse
I understand how frustrated you are itzak_man because of the lack of official Rogers firmware and that you almost felt lied to by the whole XDA community over the Rogers firmware scandal. Please remember, this is a risk that you take by modifying your phone outside of the manufacturers intended usage. This its the reason why this its the first phone that I haven't modified.
That being said, I am working directly with the firmware team to try to procure an official version of the Rogers firmware. There are some server issues with the fastboot servers, so please give us a couple more weeks. I want official firmware for everyone here as well, and the ability to modify my phone in the future with the ability to return to official stock.
Sent from my XT925 using Tapatalk 2
alexv305 said:
There already is a bootloader unlock. You can use the motorola bootloader unlock tool. I don't have a developer edition and it worked perfect for me. Other users in the forum also have their bootloaders unlocked.
Click to expand...
Click to collapse
I think that the bootloader unlock that SFG is referring to is a non-Motorola warranty-voiding unlock. It's nice the Motorola supports the unlocking but it really means that they control who gets unlocked and removes any future warranty claims.
waiting for your update. Thanks for checking with the firmware team.
---------- Post added at 12:51 PM ---------- Previous post was at 12:48 PM ----------
danifunker said:
I understand how frustrated you are itzak_man because of the lack of official Rogers firmware and that you almost felt lied to by the whole XDA community over the Rogers firmware scandal. Please remember, this is a risk that you take by modifying your phone outside of the manufacturers intended usage. This its the reason why this its the first phone that I haven't modified.
That being said, I am working directly with the firmware team to try to procure an official version of the Rogers firmware. There are some server issues with the fastboot servers, so please give us a couple more weeks. I want official firmware for everyone here as well, and the ability to modify my phone in the future with the ability to return to official stock.
Sent from my XT925 using Tapatalk 2
Click to expand...
Click to collapse
waiting for your update. Thanks for checking with the firmware team.
I think that the bootloader unlock that SFG is referring to is a non-Motorola warranty-voiding unlock. It's nice the Motorola supports the unlocking but it really means that they control who gets unlocked and removes any future warranty claims.
Click to expand...
Click to collapse
Reporting after a long talk to Motorola Canada services:
The JB upgrade (which is controlled by Motorola) checks your IMEI, android version & the country code.
When I mentioned the 2 versions (492002 & 49003) no body had a clue what I am talking about !
If you bootloader is unlock by Motorola, regardless which version you got, your phone becomes an orphan; No more upgradable !
When I said that there message on line is misleading: Losing the warranty only but nothing about losing any upgrade privileges !
They agree it's wrong & "promise" to fix the worming message (after the fact).
Now I am not sure that there is or was a second version (the 49003) in Motorola arsenal. My guess is that the Boot loader unlock process does more to the phone then just unlock. Possible changing the version system...?
So,our only option is waiting & hopping that we get a full JB version upgradable by RDS.
itzik_man said:
Reporting after a long talk to Motorola Canada services:
The JB upgrade (which is controlled by Motorola) checks your IMEI, android version & the country code.
When I mentioned the 2 versions (492002 & 49003) no body had a clue what I am talking about !
If you bootloader is unlock by Motorola, regardless which version you got, your phone becomes an orphan; No more upgradable !
When I said that there message on line is misleading: Losing the warranty only but nothing about losing any upgrade privileges !
They agree it's wrong & "promise" to fix the worming message (after the fact).
Now I am not sure that there is or was a second version (the 49003) in Motorola arsenal. My guess is that the Boot loader unlock process does more to the phone then just unlock. Possible changing the version system...?
So,our only option is waiting & hopping that we get a full JB version upgradable by RDS.
Click to expand...
Click to collapse
I have a feeling they don't know what they are talking about. There are reports of a number of users who were rooted but still got the upgrade. I've reached out to a couple of them and hopefully we will get a full JB XML restore soon.
Don't forget the date and version differences between 49003 and 492002.
Unlocking the bootloader changes some of the encryption keys used, but definitely not the system version.
Sent from my XT925 using Tapatalk 2
I can understand your frustration but development takes time and requires opportunity. With a locked bootloader & lack of kexec, there simply isn't much developers can do right now. With time, good things may eventually come. But Motorola development will never match that of other popular phones.
I have a feeling they don't know what they are talking about. There are reports of a number of users who were rooted but still got the upgrade. I've reached out to a couple of them and hopefully we will get a full JB XML restore soon.
Click to expand...
Click to collapse
Rooted will get you the OTA, not bootloader unlocked. Once you unlock using your IMEI, your phone info is deleted from Motorola databank.
We need to consolidate the information & comments on the Rogers ICS to JB upgrade to one topic & one location.
The subject is all over in this forum & it creates a great deal of difficulty to trace & follow the objective which is; how to fix the issue of compatibility of versions..
danifunker said:
That being said, I am working directly with the firmware team to try to procure an official version of the Rogers firmware. There are some server issues with the fastboot servers, so please give us a couple more weeks. I want official firmware for everyone here as well, and the ability to modify my phone in the future with the ability to return to official stock.
Click to expand...
Click to collapse
Hi danifunker, for your efforts, thank you.
Out of curiosity:
- what causes the "delay" in you getting official firmware from rogers?
- which version(s) are you planning to get: 2002 and/or JB?
thanks!
I have uploaded Rogers ICS firmware for RAZR HD back in November: http://sbf.droid-developers.org/vanquish_u/list.php
There is no JB for it right now as I'm aware.
Skrilax_CZ said:
I have uploaded Rogers ICS firmware for RAZR HD back in November: http://sbf.droid-developers.org/vanquish_u/list.php
There is no JB for it right now as I'm aware.
Click to expand...
Click to collapse
The version available doesn't allow for OTA update to JB it's the wrong version
Sent from my XT925
10/16/2015:
*CAUTION ADVISED*
Individuals have reported fastboot problems impacting their devices after attempting an official unlock. Review thread and proceed at your own risk.
----------
Official unlock!
Just noticed this on the official Asus site under 'Utilities':
Unlock Device App: Unlock boot loader
Notice:
1. Update your software image to V2.20.40.59 or latest version
2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.https://www.asus.com/us/support/Down...Ulh0Ph49Hl/32/
Update: Date stamp on the APK of 7/23/2015 is interesting. Ran on my unlocked ZE551ML and after accepting the terms of use, it complained that my model was not supported.
Oh crap nice find... Now if I use this I cannot or can do ota updates?
Worked here perfectly fine! Thanks!! Make sure you are on a stock ROM when you try
this is a great step!! thank you!!!
i checked: there is also for ZE550ML !!!
It's announced now
Khanger posted the announcement on reddit about an hour ago in /r/zenfone2/
Took 7 months but it's finally here haha.
Is there a difference between the official unlock and the previously known method of unofficial unlock? Unlocked bootloader is the same either way, correct?
Reddit thread says you will not get OTA after using this file.
onurd said:
Is there a difference between the official unlock and the previously known method of unofficial unlock? Unlocked bootloader is the same either way, correct?
Click to expand...
Click to collapse
Would like to know this as well.
Sad it does only concern 551ml version.
A, Does this unlock automatically give root?
B, And lets say I use this BUT I remain with stock, will I still be barred from OTA?
550 - direct download (source page, look under "Utilities"), mirror: mega
551 - direct download (source page, look under "Utilities"), mirror: mega
gontie said:
Sad it does only concern 551ml version.
Click to expand...
Click to collapse
nope
also for 550ml version
https://www.asus.com/Phone/ZenFone_2_ZE550ML/HelpDesk_Download/
under utilities
sumean said:
A, Does this unlock automatically give root?
B, And lets say I use this BUT I remain with stock, will I still be barred from OTA?
Click to expand...
Click to collapse
A) why would it? Root access and unlocking bootloader are completely different things.
B) if you unlock via official method, your warranty is void and your phone is barred from receiving OTAs.
I understand it voids the warranty but what I don't understand is why no updates? If you take an OTA and it hoses your out of warranty phone its on you.
hope someone discover relock method
Druboo666 said:
hope someone discover relock method
Click to expand...
Click to collapse
From the official unlock, there likely will never be a way to relock and get back OTA functionality. That being said, adb sideloading OTA files should still work. Reasoning as such:
* Unlocking your device using the official APK sends a notification to ASUS that your device is now unlocked, out of warranty, and will not have OTAs pushed to it.
* Whether or not you can manually grab OTAs using the system app has yet to be seen, as we haven't received a new update since the official bootloader unlock method has been released. Personally, I believe our SSIDs will be blocked from getting anything from the OTA server based on the verbage in the disclaimer.
* adb sideloading a ZIP file should have no reliance on the bootloader status. As long as you're flashing the right file, it should work because adb sideload has no internet functionality so it can't call home to check on your ability to flash things. It would be a very poor decision to actively bar users who do the unlock from using official firmware updates on their own terms.
Anyways, I'm adventurous so I've taken the plunge of my own accord. I don't plan to put TWRP on or flash CM12.1 until the majority of the CM bugs have been resolved. When the next OTA comes out, I'll post my experience in obtaining and flashing it so that others can know if they want to unlock the bootloader officially as well.
I will comment specifically that Motorola bootloader unlocks did not bar their users from getting official OTAs after the fact. It is an assumed risk to unlock the bootloader and it's a bit salty to basically say "well, you did this, you don't deserve to automatically get what we're baking for you now". The fact that we got an official unlock at all is scores above what most other manufacturers have done, though. Hopefully, ASUS backs off of the no-OTA thing at some point as it is a bit unnecessary. At worst case, I'm trusting us all here at XDA to work your magic if we end up in a corner somehow.
my question is: if their unlocking method brick my phone???? warranty is expired and they don't take him ???
this method is a weird thing.
MatteXperiaU said:
my question is: if their unlocking method brick my phone???? warranty is expired and they don't take him ???
this method is a weird thing.
Click to expand...
Click to collapse
Attempting to unlock your phone is the same this as actually unlocking your phone: you're taking it's life in your hands. If you brick it trying to unlock it, it's not covered. If something happens to it after it's been unlocked, it's not covered. This does not necessarily mean that they won't repair it, it means that:
a) any repairs cost money out of pocket and
b) they have the right to say a device is unrepairable and send it back to you with no obligation to fix it or compensate you in any way.
Them's the breaks for being a tinkerer!
Level99 said:
Attempting to unlock your phone is the same this as actually unlocking your phone: you're taking it's life in your hands. If you brick it trying to unlock it, it's not covered. If something happens to it after it's been unlocked, it's not covered. This does not necessarily mean that they won't repair it, it means that:
a) any repairs cost money out of pocket and
b) they have the right to say a device is unrepairable and send it back to you with no obligation to fix it or compensate you in any way.
Them's the breaks for being a tinkerer!
Click to expand...
Click to collapse
yeah, i think there are no phones with unlocked bootloader and warranty ok..
the only way is relock bootloader..no news for that now..
you said it is not possible..are you sure? i think unlock bootloader is an offline method?
Guys, i apologize in advance for this, but I am still a bit confused as to the whole QFuse debacle. I searched but found various contradicting statements and hence started another thread in the hopes of solving my confusion as well as that of others. My doubts are -
1) Does the QFuse change irreversibly once you unlock the bootloader?
2) In case that it does not, will the QFuse return to original state upon relocking the bootloader or never change despite an unlocked bootloader?
3) Given that it changes with an unlocked bootloader and reverts to original state on relocking it, will the manufacturers warranty be hinged on the QFuse state? (I am asking this because I need to make sure if you can get a replacement for a hardware fault in case you run into one while on a custom ROM. In such a case you will be stuck with a hardware issue and you cant flash factory, like the infamous nexus 5 power button issue. I have previously been able to get a nexus 5 replaced while being rooted and on a custom ROM due to a hardware defect)
Thanks for any answers and hope this helps others as well. :laugh:
Looks like you haven't searched enough. No debacle. seriously am not worried.
Sent from my iPhone using Tapatalk