Making a thread where common questions/FAQs are done here for the S-OFF made by beaups and Fuses.
Even I have a question haha:
Will this S-OFF require the need to unlock the bootloader from HTCDev first?
abzillard said:
Making a thread where common questions/FAQs are done here for the S-OFF made by beaups and Fuses.
Even I have a question haha:
Will this S-OFF require the need to unlock the bootloader from HTCDev first?
Click to expand...
Click to collapse
Well the last time I had a HTC device that had S-OFF I remember just using a tool that a developer created and ran it and my HTC had S-OFF without unlocking the bootloader. But it doesn't matter even if you have to unlock it because with S-OFF you can have it locked again (not relocked). And there will be no evidence that you have unlocked the BL.
You're probably talking about Revolutionary which was developed almost 2 years ago. I remember that because I used it for my HTC Wildfire but recent S-OFF tools require the need to unlock the bootloader such as the Droid DNA S-OFF tool so just curious because I don't want to S-OFF if I have to unlock the bootloader.
abzillard said:
You're probably talking about Revolutionary which was developed almost 2 years ago. I remember that because I used it for my HTC Wildfire but recent S-OFF tools require the need to unlock the bootloader such as the Droid DNA S-OFF tool so just curious because I don't want to S-OFF if I have to unlock the bootloader.
Click to expand...
Click to collapse
But like I said unlocking the bootloader won't matter because you can lock it again and it will not say "RELOCKED" either. That's why I'm waiting for S-OFF before I flash anything. That's what great about S-OFF because you can have the phone locked again without any trace of the BL being unlocked.
shadowboy23 said:
But like I said unlocking the bootloader won't matter because you can lock it again and it will not say "RELOCKED" either. That's why I'm waiting for S-OFF before I flash anything. That's what great about S-OFF because you can have the phone locked again without any trace of the BL being unlocked.
Click to expand...
Click to collapse
You dont think they have a database with all the unlocked devices and their imei? I´d be surprised if not
They may not have a database. The last part of the process to unlock is not on their website, so hard for them to be sure you performed 'fastboot oem unlock'
Sent from my HTC One using xda app-developers app
I'm excited to be able to change the what the bootloader says incase it breaks.
Sent from my HTC One using xda app-developers app
shox22 said:
You dont think they have a database with all the unlocked devices and their imei? I´d be surprised if not
Click to expand...
Click to collapse
There's no proof that you have unlocked your BL. Yes you got the key but whether you unlocked it or not is another matter.
shox22 said:
You dont think they have a database with all the unlocked devices and their imei? I´d be surprised if not
Click to expand...
Click to collapse
They have a database of phones REQUESTING for an unlock code, but not whether you used it or not.
They would definitely have a database my friend. The IMEI and the identifier tokens as well since they are unique for each device.
This thread is going off-topic. Only Q&A related to beaups and Fuses upcoming S-OFF for the HTC One please.
I will have S-OFF but i thinks is better wait a fix for aroma
Because my friend bricked him phone with a freeze of TWRP...
more info here in the droid DNA section http://forum.xda-developers.com/showthread.php?t=2293010
abzillard said:
They would definitely have a database my friend. The IMEI and the identifier tokens as well since they are unique for each device.
This thread is going off-topic. Only Q&A related to beaups and Fuses upcoming S-OFF for the HTC One please.
Click to expand...
Click to collapse
Yes they will have a database but they can't tell if you unlocked the BL. All they have are your IMEI number and the token. Even when you try to unlock the BL the phone gives you an option whether you want to go ahead and unlock it. See picture below (you can see you can choose "YES" or "NO" to unlock the bootloader):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So even if you get the token they can't tell if you went ahead and unlocked it. Because with S-OFF you can flash the original BL back and it will show that the BL is "LOCKED" and not "RELOCKED".
My friend, the moment you send you're identifier code as well as your IMEI of the device, the warranty is gone, dead, vamoosh.
abzillard said:
My friend, the moment you send you're identifier code as well as your IMEI of the device, the warranty is gone, dead, vamoosh.
Click to expand...
Click to collapse
What rubbish. That would be totally illegal for HTC to do that in the EU and probably in 99% of other countries as well. Even with a custom ROM installed HTC still have to honour hardware failures.
Stop spreading such ideas, they are false. The only thing HTC can refuse is to fix a bricked device and only then if the device was actually unlocked and flashed with custom software.
rovex said:
What rubbish. That would be totally illegal for HTC to do that in the EU and probably in 99% of other countries as well. Even with a custom ROM installed HTC still have to honour hardware failures.
Stop spreading such ideas, they are false. The only thing HTC can refuse is to fix a bricked device and only then if the device was actually unlocked and flashed with custom software.
Click to expand...
Click to collapse
I thought that was how it went. My apologies.
HTCs warranty goes slightly beyond the legal minimum, but only just, any hardware failure is still covered, whatever you do, unless HTC can prove the hardware was damaged by a customisation they have to repair it as required by EU law. So for example, if the screen goes faulty, they have to fix it, but if you flash custom software and it hard bricks, thats your problem.
HTC might initially refuse to fix it, sometimes they do try it on, but if you remind them of their legal responsibility they will ultimately have no choice if the software was not to blame.
abzillard said:
My friend, the moment you send you're identifier code as well as your IMEI of the device, the warranty is gone, dead, vamoosh.
Click to expand...
Click to collapse
Totally WRONG!!! rovex knows how it is.
abzillard said:
My friend, the moment you send you're identifier code as well as your IMEI of the device, the warranty is gone, dead, vamoosh.
Click to expand...
Click to collapse
Wrong. Just plain wrong...
Careful guys; HTC aren't obliged to do anything, consumer protection law is with the retailer, not the manufacturer.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey guys i updated my device to JB V20a but i cannot unlock bootloader.I'm not getting any error but when I run the command "adb reboot oem-unlock"y.phone reboots and asks me if i want to unlock bootloader.I choose yes and then it says "Download mode" with red colour letters.Then nothing.When I disconnect from cable the phone says factory reset............Please wait!
Its unlockable?Or i am doing something wrong?
If it's unlockable can I flash a .kdz rom from other country and achieve to unlock it?
Sent from my LG-P880 using xda app-developers app
GRG13 said:
Hey guys i updated my device to JB V20a but i cannot unlock bootloader.I'm not getting any error but when I run the command "adb reboot oem-unlock"y.phone reboots and asks me if i want to unlock bootloader.I choose yes and then it says "Download mode" with red colour letters.Then nothing.When I disconnect from cable the phone says factory reset............Please wait!
Its unlockable?Or i am doing something wrong?
If it's unlockable can I flash a .kdz rom from other country and achieve to unlock it?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
Make sure you have fastboot drivers installed, it was my problem. It will work when it goes from download mode to factory reset WITHOUT taking the cable out, try the unlock tool it has drivers packaged with it i believe
Otherwise?It means that its unlockable
Στάλθηκε από το LG-P880 μου χρησιμοποιώντας Tapatalk 2
GRG13 said:
Otherwise?It means that its unlockable
Στάλθηκε από το LG-P880 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Eur 4.1 firmware is unlockable, if it isnt i dont think reboot-oem-unlock would work
nevermind
About unlocking the bootloader
Quick question guys, I had a Atrix 4G. When I unlocked the bootloader at the boot logon it shown the message "unlocked'.
When I unlock the bootloader for my "still to come" (shipped) O4X it will display any message of unlocked bootloader?
Sorry for my bad english
Erus Tyrannus said:
Quick question guys, I had a Atrix 4G. When I unlocked the bootloader at the boot logon it shown the message "unlocked'.
When I unlock the bootloader for my "still to come" (shipped) O4X it will display any message of unlocked bootloader?
Sorry for my bad english
Click to expand...
Click to collapse
it will on S/W upgrade screen, not on boot logon afaik
JoinTheRealms said:
Make sure you have fastboot drivers installed, it was my problem. It will work when it goes from download mode to factory reset WITHOUT taking the cable out, try the unlock tool it has drivers packaged with it i believe
Click to expand...
Click to collapse
I have the packet from 17 post, now, i click at install and nothing happens, could you tell me how proceeds ??
Im allways getting the message above:
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 169.836s
Installed the Euro-XXX and in About Phone read:
P88020A-724-06
Any rom installed returns this code 724-06, till the 20B, i got this code.
Any help ??
I have some stupid Questions
1. Is it possible to Lock the Bootloader again if you get it unlocked by any means?
2. How does this effect yoour warranty on the phone?
3. Do you lose your warranty?
sPEADy said:
I have some stupid Questions
1. Is it possible to Lock the Bootloader again if you get it unlocked by any means?
2. How does this effect yoour warranty on the phone?
3. Do you lose your warranty?
Click to expand...
Click to collapse
1. No. It may or may not show as locked if you get back to ICS, but if you then go back to JB it shows as unlocked again.
2 and 3. Depends if you bought the phone in Europe or elsewhere.
For Europe, you might lose the warranty regarding software-related issues. Hardware-related issues should still be covered (due to a EU directive, read more about it here), although you might find resistance from some LG Support centers. If you do, just state it's your right as granted by Directive 1999/44/CE. If they still don't grant you, I believe there are legal ways you must follow.
If you bought it outside of Europe, it would depend on the legislation of your Country.
Also, a quick reminder that there's still only Nightlies on the CM 10 ROM, and no other Custom ROMs to speak of. So my general advice would be to read on about the way to unlock your phone, but only do it if you actually want to install a Custom ROM right away (which also implies you're ready to the possible buggy-ness of the available ROMs).
skryptus said:
1. No. It may or may not show as locked if you get back to ICS, but if you then go back to JB it shows as unlocked again.
2 and 3. Depends if you bought the phone in Europe or elsewhere.
For Europe, you might lose the warranty regarding software-related issues. Hardware-related issues should still be covered (due to a EU directive, read more about it here), although you might find resistance from some LG Support centers. If you do, just state it's your right as granted by Directive 1999/44/CE. If they still don't grant you, I believe there are legal ways you must follow.
If you bought it outside of Europe, it would depend on the legislation of your Country.
Also, a quick reminder that there's still only Nightlies on the CM 10 ROM, and no other Custom ROMs to speak of. So my general advice would be to read on about the way to unlock your phone, but only do it if you actually want to install a Custom ROM right away (which also implies you're ready to the possible buggy-ness of the available ROMs).
Click to expand...
Click to collapse
My phone is just 3 months old I am not going to do this any way I am very happy with the Stock Rom I will give it a try when I am over the Warranty Period. Thank you for your reply.
Have a nice Day/Eve.
So I just got the Google Play Edition and I can't seem to figure any tutorial thread out on how to unlock the bootloader then root my phone, then install a custom recovery, then install a rom :/ I need some help. So currently, I am at the htcdev part to unlock bootloader using this tutorial. When I get to step 11 it says to skip to step 8 which I can not do on the page (Guessing the guide is outdated?). So I go ahead and do step 5-7 and when I type "fastboot oem get_identifier_token" on step 5 it just stays stuck on "waiting for device" on the CMD prompt. What am I doing wrong?
PS. which I click fastboot as instructed on step 2 of htcdev it just send me back to the screen before.
EvoTheBoy said:
So I just got the Google Play Edition and I can't seem to figure any tutorial thread out on how to unlock the bootloader then root my phone, then install a custom recovery, then install a rom :/ I need some help. So currently, I am at the htcdev part to unlock bootloader using this tutorial. When I get to step 11 it says to skip to step 8 which I can not do on the page (Guessing the guide is outdated?). So I go ahead and do step 5-7 and when I type "fastboot oem get_identifier_token" on step 5 it just stays stuck on "waiting for device" on the CMD prompt. What am I doing wrong?
PS. which I click fastboot as instructed on step 2 of htcdev it just send me back to the screen before.
Click to expand...
Click to collapse
Stuck waiting for device mean your drivers are not installed preoperly, download HTC Sync manager install it and then remove HTC sync, you will see the driver package above it, leave that alone.
Also, your phone must be in the bootloader when trying to get ID token, not booted up. (just in case)
Instructions to unlock the bootloader are at HTCDev whilst your trying to actually unlock the bootloader, you will need to register: http://www.htcdev.com/bootloader unlocking is the easy part.
Seanie280672 said:
Stuck waiting for device mean your drivers are not installed preoperly, download HTC Sync manager install it and then remove HTC sync, you will see the driver package above it, leave that alone.
Also, your phone must be in the bootloader when trying to get ID token, not booted up. (just in case)
Instructions to unlock the bootloader are at HTCDev whilst your trying to actually unlock the bootloader, you will need to register: http://www.htcdev.com/bootloader unlocking is the easy part.
Click to expand...
Click to collapse
Thank you for the reply! I got as far as inputting "fastboot flash unlocktoken Unlock_code.bin" into the cmd prompt which says it was successful but doesn't show nor do anything on my phone like it says it should. Any ideas on how to fix that?
EvoTheBoy said:
Thank you for the reply! I got as far as inputting "fastboot flash unlocktoken Unlock_code.bin" into the cmd prompt which says it was successful but doesn't show nor do anything on my phone like it says it should. Any ideas on how to fix that?
Click to expand...
Click to collapse
Really sorry I didn't read your first post properly, you have a gpe device, different kettle of fish, the HTC dev way doesn't work for gpe, try this instead.
http://www.ibtimes.co.uk/htc-one-google-play-edition-how-unlock-bootloader-root-install-twrp-1429968
For the Google Play Edition just use fastbot oem unlock and you're done
However, bear in mind that you won't be able to use Sense-based ROMs as the partitions are different. You're limited to AOSP/CM-based ROMs (unless you can convert to a Sense M7, which I assume so as they're technically the same device)
Seanie280672 said:
Really sorry I didn't read your first post properly, you have a gpe device, different kettle of fish, the HTC dev way doesn't work for gpe, try this instead.
http://www.ibtimes.co.uk/htc-one-google-play-edition-how-unlock-bootloader-root-install-twrp-1429968
Click to expand...
Click to collapse
EddyOS said:
For the Google Play Edition just use fastbot oem unlock and you're done
However, bear in mind that you won't be able to use Sense-based ROMs as the partitions are different. You're limited to AOSP/CM-based ROMs (unless you can convert to a Sense M7, which I assume so as they're technically the same device)
Click to expand...
Click to collapse
I keep getting this error :/ Idk if this helps but it says s-on and hboot is 1.54 and my OS is 5.11.1700.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
EddyOS said:
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
Click to expand...
Click to collapse
It is weird. I googled it and came about people saying to downgrade (Which I have 0 knowledge of when it comes to HTC devices.. coming from LG as my device with experience). Idk. Thanks for the help hopefully someone can help me out about this.
The whole point of the GPe phones is that they're easy to unlock, like a Nexus, so it should just unlock with that command. The only thing I can think of is you're using outdated fastboot files so perhaps looks into updating them but failing that I'm at a loss
EddyOS said:
The whole point of the GPe phones is that they're easy to unlock, like a Nexus, so it should just unlock with that command. The only thing I can think of is you're using outdated fastboot files so perhaps looks into updating them but failing that I'm at a loss
Click to expand...
Click to collapse
Guess that isn't the problem :/ I triple checked to make sure I had the right fastboot and I kept getting the same error.
EddyOS said:
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
Click to expand...
Click to collapse
I've never seen that.. It's very odd.
graffixnyc said:
I've never seen that.. It's very odd.
Click to expand...
Click to collapse
I read online about it and saw some say to call google and they could help fix the problem cause it is a problem within the actual device. I called them and they didn't help lol. Anyways, my device is still under warranty and has the purple camera tint problem so I will try to send it in and hopefully get a new model back.
OT: if anyone has had this error before please say how you fixed it thanks
UPDATE: After some googling I found out that after 4.4.2 fastboot oem unlock does not work anymore with this devices (I am on 5.0.1)
I did "oem unlock" on my new Nexus 6, because i wanted to upgrade directly to the newest image of Android 6.
However after that, i discovered, that i had to "Enable OEM unlock" in developer settings, to "oem lock" and "oem unlock" the device.
But I didn't had to do this the first time.
So is this feature not implemented in the first firmware version of the Nexus 6, or is my "new" device not realy new?
Looks like it was already unlocked when you got it. Usually you get a few messages about unlocking the phone to warn you and tell you the device will be wiped aka factory reset.
JulianPascal said:
I did "oem unlock" on my new Nexus 6, because i wanted to upgrade directly to the newest image of Android 6.
However after that, i discovered, that i had to "Enable OEM unlock" in developer settings, to "oem lock" and "oem unlock" the device.
But I didn't had to do this the first time.
So is this feature not implemented in the first firmware version of the Nexus 6, or is my "new" device not realy new?
Click to expand...
Click to collapse
are the dev options in settings witthout you unlocking them? if yes, then your new phone isnt new.
simms22 said:
are the dev options in settings witthout you unlocking them? if yes, then your new phone isnt new.
Click to expand...
Click to collapse
No, the developer options were not enabled. I got into fastboot mode, made sudo fastboot oem unlock, clicked yes and it was unlocked. I flashed the Android 6 image manually and after that i couldn't relock it. I had then to activate the developer options to relock the device.
gee2012 said:
Looks like it was already unlocked when you got it. Usually you get a few messages about unlocking the phone to warn you and tell you the device will be wiped aka factory reset.
Click to expand...
Click to collapse
I got this warning, but i didn't have to activate “Enable OEM Unlock” in the developer options to unlock the device.
JulianPascal said:
I got this warning, but i didn't have to activate “Enable OEM Unlock” in the developer options to unlock the device.
Click to expand...
Click to collapse
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch ?
gee2012 said:
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch ?
Click to expand...
Click to collapse
i think ive read about two more phones that had that "glitch", but its not common for sure.
simms22 said:
i think ive read about two more phones that had that "glitch", but its not common for sure.
Click to expand...
Click to collapse
I`am glad there is still some magic left in this world
gee2012 said:
Hard to believe to be honest. But hey anything is possible, maybe some kind of magical glitch
Click to expand...
Click to collapse
i've got only 1 Warning the first time: "Unlock bootloader? - yes(may void waranty / no)"
after the upgrade i get: the red "Waring" and then "Unlock bootloader?" - yes(may void waranty / no)
JulianPascal said:
i've got only 1 Warning the first time: "Unlock bootloader? - yes(may void waranty / no)"
after the upgrade i get: the red "Waring" and then "Unlock bootloader?" - yes(may void waranty / no)
Click to expand...
Click to collapse
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?
simms22 said:
i think ive read about two more phones that had that "glitch", but its not common for sure.
Click to expand...
Click to collapse
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?
JulianPascal said:
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?
Click to expand...
Click to collapse
Thats probably it, had that on a N4 too once when i used CF Auto-Root (not wiped)
JulianPascal said:
Maybe this only happens with a old bootloader version, which dosen't support this feature yet? Which would explain, why i couldn't relock it after upgrading. Do you have a link?
Click to expand...
Click to collapse
na. it was there on the very first version of pre 5.0 that the phone came with. so it was there on all bootloader versions.
gee2012 said:
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?
Click to expand...
Click to collapse
I did a full wipe before flashing, so I'm not shure if the upgrade process itself reseted the device.
gee2012 said:
Oke, you`re one of the happy few where this happens. Was the device wiped/factory reset during the process?
Click to expand...
Click to collapse
simms22 said:
na. it was there on the very first version of pre 5.0 that the phone came with. so it was there on all bootloader versions.
Click to expand...
Click to collapse
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.
JulianPascal said:
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.
Click to expand...
Click to collapse
i ran the very first version of software on my n6, back in november of last year, and it had to be unlocked with hitting the oem unlock option first. calling people at motorola is just going to get you talking to people that dont know whats going on.
simms22 said:
i ran the very first version of software on my n6, back in november of last year, and it had to be unlocked with hitting the oem unlock option first. calling people at motorola is just going to get you talking to people that dont know whats going on.
Click to expand...
Click to collapse
Ok, this is strange, the Device was new and the package sealed. I mean, could realy someone have somehow re-sealed it? Someone at Nexus Help Forum suggested, maybe someone at Motorola made a mistake in the final preparation process, so there are just some devices affected.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/nexus/ZoVKdHn-cM4/xwaB-b8MAQAJ
So, do you think the Device is safe to use(regarding the devices firmware (bootloader etc.) isn't altered/ some sort of maleware embedded)? Or should I return it, if I can?
JulianPascal said:
Ok, this is strange, the Device was new and the package sealed. I mean, could realy someone have somehow re-sealed it? Someone at Nexus Help Forum suggested, maybe someone at Motorola made a mistake in the final preparation process, so there are just some devices affected.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/nexus/ZoVKdHn-cM4/xwaB-b8MAQAJ
So, do you think the Device is safe to use(regarding the devices firmware (bootloader etc.) isn't altered/ some sort of maleware embedded)? Or should I return it, if I can?
Click to expand...
Click to collapse
mistakes do happen. ive seen people buy a n6 from tmobile but receive an att version, with all the att trimings. if you want to check if locking it is possible, you probably should. but, i think it probably is safe to use.
Theoretically someone could have bought it, opened it, unlocked it and did what ever with it, somehow reasealed it and returned it to the retailer(you have the right to return something you bought online in a 14 day period in germany).
I noticed something there are two numbers which are each 11 digits long, one on the the bottom and one on the side of the packaging.
(I covered them on the pictures, but marked where they are)
The two numbers differ at my packaging, Is this normal or should the two numbers be the same?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JulianPascal said:
Motorola Support says, it's normal for older firmware versions, that they can be unlocked without activating this option.
Click to expand...
Click to collapse
I have read this as well.
Hello guys;
I bought just three days ago a new zuk Z1, it doesn't seem to have probblem and then I would start to mod it (root, custom rom ecc.).
but this will void the warranty.
there is a way to restore warranty for the zuk z1? (es. lock the bootloader, reset the flash counter, stock system and recovery ), if in the future the phone might have problems.
thank you
I just want to know if it is possible to restore warranty or is lost forever?
anyone?
use this link to get the official stock cyanogen flashable zip : http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS3OH-ham-signed.zip
or this one to be used with fastboot: http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS3OH-ham-signed-fastboot.zip
and ensure that developer mode is enabled : "go to settings >about click 5 times on the build number till it says you are no a developer" go to developer mode and ensure "Update Cyanogen" recovery is ticked.
tara you are back on fully stock like brand new out of the box
yacbos said:
use this link to get the official stock cyanogen flashable zip : http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS3OH-ham-signed.zip
or this one to be used with fastboot: http://builds.cyngn.com/factory/ham/cm-12.1-YOG4PAS3OH-ham-signed-fastboot.zip
and ensure that developer mode is enabled : "go to settings >about click 5 times on the build number till it says you are no a developer" go to developer mode and ensure "Update Cyanogen" recovery is ticked.
tara you are back on fully stock like brand new out of the box
Click to expand...
Click to collapse
But your bootloader will be unlocked still I guess.
Planet X said:
But your bootloader will be unlocked still I guess.
Click to expand...
Click to collapse
Code:
fastboot -i 0x2b4c oem lock-go
If i'm not wrong this is the method to lock it back
But you can't restore DRM Keys ....
olefou-zuk said:
But you can't restore DRM Keys ....
Click to expand...
Click to collapse
Is not a Sony Z device .
@tomdan95 warranty is not an issue, since there's none for this device : You won't be able to contact ZUK's after sale support whatsoever because it doesn't exist
So I advise you not to **** your device up like I did x')
I-Immortal said:
@tomdan95 warranty is not an issue, since there's none for this device : You won't be able to contact ZUK's after sale support whatsoever because it doesn't exist
So I advise you not to **** your device up like I did x')
Click to expand...
Click to collapse
no warranty? in europe you have it 2 years.
http://www.zuk-store.com/en/content/6-our-strengths
I-Immortal said:
@tomdan95 warranty is not an issue, since there's none for this device : You won't be able to contact ZUK's after sale support whatsoever because it doesn't exist
So I advise you not to **** your device up like I did x')
Click to expand...
Click to collapse
I have bought it from amazon so According to the laws in Europe i can send it to Them for the warranty
I-Immortal said:
@tomdan95 warranty is not an issue, since there's none for this device : You won't be able to contact ZUK's after sale support whatsoever because it doesn't exist
So I advise you not to **** your device up like I did x')
Click to expand...
Click to collapse
I know you're very annoyed because of what happened to your device but since you bought your ZUK from eBay..well..It's Amazon or an authorized reseller.
I live in Egypt and I bought mine from UniGroup which is an authorized reseller for ZUK. I have a one year warranty.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
zuk offcial reseller of italy
anyway thanks for all the answers
so ultimately , it is possibile to restore warranty, after unlock bootloader and root?
Guys, I live in Europe (France) and I bought it on eBay to TomTop which is an official and authorized seller (see on zuk.hk/onlineshop ) there was a 2 years warranty mentioned, but since ZUK has no after sale support, there's nothing they can do to repair the device so you'll have to hope the seller is kind enough to refund/exchange it (which was not the case with TomTop) or hope that you've bought it with PayPal :3
And @tomdan95 , it should be restored once you've unrooted and relocked the bootloader of the device
Planet X said:
But your bootloader will be unlocked still I guess.
Click to expand...
Click to collapse
i trust the only way to lock/unlock boot loader is via fast boot it cant be done via flashing or restoring.
yacbos said:
i trust the only way to lock/unlock boot loader is via fast boot it cant be done via flashing or restoring.
Click to expand...
Click to collapse
The easiest way is to use the toolkit of @mauronofrio http://forum.xda-developers.com/zuk-z1/orig-development/tool-toolzukz1eng0-0-3-mauronofrio-t3332563. This tool does eveything for you.
It is possible to clear flags and restore warranty state
Flags are stored in:
/dev/block/bootdevice/by-name/aboot
Unlock Bit Position - 0x001FFE10 Hex
Tamper Bit Position - 0x001FFE14 Hex
Link: http://forum.xda-developers.com/zuk-z1/help/guide-unlock-bootloader-zuk-z1-wiping-t3251801
as far as I remember, I had to flash twrp 3 and it allowed me to change aboot.img and clear all flags
Wasnt easy but it is doable
Chiminig in with some personal experience, I actually was able to get my ZUK Z1 fixed by warranty after unlocking then re-locking the bootloader.
So I bought my ZUK from a local reseller with 1 year warranty, unfortunately it seems I got a faulty unit since I had major battery problems - including the phone randomly turning off at times and often displaying wildly inaccurate battery percentages. I tried fixing the issue myself, and thinking it might be a software issue I factory-reset the phone... then later I also decided to try and see if CyanogenMod 13 fixes the issue (which was less smart, given the potential to screw up the warranty). Finally when none of it worked, I decided to take it back to the store for warranty service - so before that, I flashed back the stock Cyanogen OS factory image (links here then relocked the bootloader thru fastboot using the command "fastboot -i 0x2b4c oem lock-go". With the info command ("fastboot -i 0x2b4c oem device-info") it then shows:
Code:
(bootloader) Device tampered: [B]false[/B]
(bootloader) Device unlocked: [B]false[/B]
(Note that even when the bootloader was unlocked, it still said "Device tampered: false", but true on the latter).
Now I'm not sure if there are any other flags that could indicate I was messing with the device's software (which could have been a convenient thing for them to blame me for the battery troubles), I don't think there are but even if there were my warranty fixers did not notice them. I later got the device back with a new battery.
Tuberomix said:
Chiminig in with some personal experience, I actually was able to get my ZUK Z1 fixed by warranty after unlocking then re-locking the bootloader.
So I bought my ZUK from a local reseller with 1 year warranty, unfortunately it seems I got a faulty unit since I had major battery problems - including the phone randomly turning off at times and often displaying wildly inaccurate battery percentages. I tried fixing the issue myself, and thinking it might be a software issue I factory-reset the phone... then later I also decided to try and see if CyanogenMod 13 fixes the issue (which was less smart, given the potential to screw up the warranty). Finally when none of it worked, I decided to take it back to the store for warranty service - so before that, I flashed back the stock Cyanogen OS factory image (links here then relocked the bootloader thru fastboot using the command "fastboot -i 0x2b4c oem lock-go". With the info command ("fastboot -i 0x2b4c oem device-info") it then shows:
Code:
(bootloader) Device tampered: [B]false[/B]
(bootloader) Device unlocked: [B]false[/B]
(Note that even when the bootloader was unlocked, it still said "Device tampered: false", but true on the latter).
Now I'm not sure if there are any other flags that could indicate I was messing with the device's software (which could have been a convenient thing for them to blame me for the battery troubles), I don't think there are but even if there were my warranty fixers did not notice them. I later got the device back with a new battery.
Click to expand...
Click to collapse
Can u tell me how u flashed those images??
Is there no root on ?Verizon xt1254 without unlocking bootloader and sunshine on 5.1?
There is temp root that is relatively useless (the device acts up)
You can gain that for free with sunshine or kingroot.
But for permanent root you need an unlocked bootloader and for that sunshine ($25) is your only option.
The reason for this is proper write permissions can't be gained in system without it.
Sent from my DROID Turbo using XDA-Developers mobile app
cell2011 said:
Is there no root on ?Verizon xt1254 without unlocking bootloader and sunshine on 5.1?
Click to expand...
Click to collapse
I don't understand people's aversion to unlocking the bootloader. I did it on all my Nexus devices, and then rooted. And it's the first thing I did on my Quarks, and then rooted. I even did on on the LG phones I used before I had two Nexus phones.
In a development forum like XDA, unlocking the bootloader and rooting is like peanut butter + jelly. They just go together very well!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ChazzMatt said:
I don't understand people's aversion to unlocking the bootloader.
Click to expand...
Click to collapse
Besides paying the $25 fee to unlock the bootloader, I see one big reason not to unlock it - voiding the warranty.
On all my previous phones, I was able to root without the prospect of voiding warranty; I could always unroot and noone would be the wiser. Now, I personally decided it was worth it to void the warranty to unlock this phone and get root; but I can completely understand others being hesitant to do so, especially considering you're throwing away that 2 year screen replacement offer. I know had to think it over a while before I moved forward.
bigdav1178 said:
Besides paying the $25 fee to unlock the bootloader, I see one big reason not to unlock it - voiding the warranty.
On all my previous phones, I was able to root without the prospect of voiding warranty; I could always unroot and noone would be the wiser. Now, I personally decided it was worth it to void the warranty to unlock this phone and get root; but I can completely understand others being hesitant to do so, especially considering you're throwing away that 2 year screen replacement offer. I know had to think it over a while before I moved forward.
Click to expand...
Click to collapse
Well, this is XDA. Most ROM and kernel threads start off with "Your warranty is voided".
I don't even think about that. If you are here on XDA and you want to flash ROMs and kernels, you really don't have a warranty.
hi, I buy this phone form ebay. at the first start pup up a message it's unlocked .
it has 5.1 android and no root, a question if verizon release ota can i install ?
I want to unlock my xt1254 but i am unable to pay them 25$ because I dont have paypal account in Pakistan and I am kinna stuck in this problem, is there any other way to unlock? :fingers crossed:
bigdav1178 said:
Besides paying the $25 fee to unlock the bootloader, I see one big reason not to unlock it - voiding the warranty.
On all my previous phones, I was able to root without the prospect of voiding warranty; I could always unroot and noone would be the wiser. Now, I personally decided it was worth it to void the warranty to unlock this phone and get root; but I can completely understand others being hesitant to do so, especially considering you're throwing away that 2 year screen replacement offer. I know had to think it over a while before I moved forward.
Click to expand...
Click to collapse
I've talked to a few people who have turned in their unlocked phones under warranty to Verizon with no issues. I've personally returned a "system status: modified" phone to Motorola back in the moforoot days also without issues. I don't think it actually voids anyone's warranty and if it does, I guess the community is small enough that Verizon/Moto doesn't think it's worth training technicians to look for it.
TheSt33v said:
I've talked to a few people who have turned in their unlocked phones under warranty to Verizon with no issues. I've personally returned a "system status: modified" phone to Motorola back in the moforoot days also without issues. I don't think it actually voids anyone's warranty and if it does, I guess the community is small enough that Verizon/Moto doesn't think it's worth training technicians to look for it.
Click to expand...
Click to collapse
I'm already past my 1 year Motorola warranty coverage, but that's good to hear considering I'm still covered by the 2 year Verizon screen warranty. I hope to never find out whether they'll take mine unlocked without issue, but it's good to know others have been able to so. I think I may need to get rid of that unlocked bootloader message at boot just in case.
ChazzMatt said:
In a development forum like XDA, unlocking the bootloader and rooting is like peanut butter + jelly. They just go together very well!
Click to expand...
Click to collapse
will you please inform us ( pm ) about it ?
regards.
oralover2006 said:
will you please inform us ( pm ) about it ?
regards.
Click to expand...
Click to collapse
No reason for PM. The information is available throughout the forum.
[GUIDE] How to unlock your bootloader, install TWRP and gain root access
http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
Unless you took the recent (May 2016) OTA update SU4TL-49 which blocks bootloader unlock:
[PSA] DT Android SU4TL-49 5.1 + Updates patch SunShine Unlock, Unlock b4 updating
http://forum.xda-developers.com/droid-turbo/general/psa-droid-turbo-android-6-0-update-t3379894
IF you are on an XT1254 with firmware SU4TL-44 or lower, you can unlock your bootloader and root your XT1254 Droid Turbo. (If lower than SU4TL-44, then just flash SU4TL-44.)
However, if you took SU4TL-49 BEFORE unlocking your bootloader, you are out of luck and cannot unlock bootloader and root.
The other Quarks (XT1225, XT1250) do NOT need Sunshine to unlock bootloader. You can get the unlock code for free from Motorola.
ChazzMatt said:
No reason for PM. The information is available throughout the forum.
[GUIDE] How to unlock your bootloader, install TWRP and gain root access
http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
Unless you took the recent (May 2016) OTA update SU4TL-49 which blocks bootloader unlock:
[PSA] DT Android SU4TL-49 5.1 + Updates patch SunShine Unlock, Unlock b4 updating
http://forum.xda-developers.com/droid-turbo/general/psa-droid-turbo-android-6-0-update-t3379894
IF you are on an XT1254 with firmware SU4TL-44 or lower, you can unlock your bootloader and root your XT1254 Droid Turbo. (If lower than SU4TL-44, then just flash SU4TL-44.)
However, if you took SU4TL-49 BEFORE unlocking your bootloader, you are out of luck and cannot unlock bootloader and root.
The other Quarks (XT1225, XT1250) do NOT need Sunshine to unlock bootloader. You can get the unlock code for free from Motorola.
Click to expand...
Click to collapse
thanks for reply.
I had XT 1254, SU4TL-49, 5.1 and it is not unlocked... means it can't be unlocked and rooted, now i have to sell it and buy an older ver. ? ok then i will consider change it, i purchased some apps from play store like Greenify which require root work completely and now it require me to did the task manually.
what about if i use KingRoot like app to only root it to run those apps? will work as required by these apps?
thanks again for your reply and guide.
best regards
oralover2006 said:
thanks for reply.
I had XT 1254, SU4TL-49, 5.1 and it is not unlocked... means it can't be unlocked and rooted, now i have to sell it and buy an older ver. ? ok then i will consider change it, i purchased some apps from play store like Greenify which require root work completely and now it require me to did the task manually.
what about if i use KingRoot like app to only root it to run those apps? will work as required by these apps?
thanks again for your reply and guide.
best regards
Click to expand...
Click to collapse
I don't know of any temp root that works with SUTL-49 unless the bootloader is already unlocked.
If someone knows differently,v please chime in.
ChazzMatt said:
I don't know of any temp root that works with SUTL-49 unless the bootloader is already unlocked.
If someone knows differently,v please chime in.
Click to expand...
Click to collapse
The Sunshine team has removed the temproot functionality for all phones (bootloader locked or unlocked) on SU4TL-49. Jcase requested that I remove the temp root/flashify method for installing TWRP from my unlocking guide.
TheSt33v said:
The Sunshine team has removed the temproot functionality for all phones (bootloader locked or unlocked) on SU4TL-49
Click to expand...
Click to collapse
it means there is a chance Rooting SU4TL-49 which is my droid's build number... or i mis-understood
a very old question, my friend want to keep it without Root (we both bought together) and asking for how to remove limitation of SMS which allow to Create message not more than 160 characters, but can Receive and Forward bigger messages. tried GO SMS Pro Premium 6 but don't know why it didn't worked, any advise / suggestion please.
best regards
Federal Copyright Act states it is 100% legal to root a phone as long as the intentions are not to gain access to otherwise paid features without voiding a warranty. I would post a link but I don't think I can. Just Google it. So in other words, don't use a rooted phone in order to hack something to gain monetary value, physical or virtual, and it's still within our legal rights to do so. Whether or not the manufacturer of your device "lets" you do it or not is up to them.
Draven10785 said:
Whether or not the manufacturer of your device "lets" you do it or not is up to them.
Click to expand...
Click to collapse
In this case it's not the manufacturer, it's the carrier (Verizon) who demands the locked down bootloader which prevents full root.
Motorola specifically gives unlock code for free to all other Quarks (XT1225, XT1250), sold by at least a dozen carriers around the world. Only Verizon demands their Quark (XT1254) bootloader remain locked down.
Sunshine team found an exploit specific to Snapdragon 805 chipset, which worked on Verizon firmware SUTL-44, to unlock the bootloader in spite of Verizon. This was released in November 2015.
Six months later (May 2016), Verizon pushed out SUTL-49 which blocks that exploit. So, people had six months to unlock their bootloaders -- and still can as long as they don't have SUTL-49 (or higher).
I unlock my bootloader and root my phone to fully own my phone. I pay for all my phones in full, I've NEVER had a contract. So, the manufacturer/carrier has no control over the software on my phone.Unless your phone is rooted, the manufacturer/carrier really still owns your phone. They decide what bloatware to put on there, etc. I root my phone to block ads, control my own device for which I paid hundreds of dollars, and improve performance. It's MY property, not theirs.
I typically "bring my own phone". I've used AT&T since 2012, but have never had an AT&T branded phone. First, gen3 Galaxy Nexus, then gen5 LG Nexus 5, now Moto XT1225 (basically the gen6 Moto Nexus 6, but in a mainstream 5.2" display size).
For Verizon, there are now phones you can "bring" that can be rooted -- for instance the Moto XT1250, which is identical to the Droid Turbo XT1254, but has bootloader which can be unlocked. Or any of the newer Nexus phones.
Draven10785 said:
Federal Copyright Act states it is 100% legal to root a phone as long as the intentions are not to gain access to otherwise paid features without voiding a warranty. I would post a link but I don't think I can. Just Google it. So in other words, don't use a rooted phone in order to hack something to gain monetary value, physical or virtual, and it's still within our legal rights to do so. Whether or not the manufacturer of your device "lets" you do it or not is up to them.
Click to expand...
Click to collapse
I would love to see your reference for this, please. If you can't post it, please PM it to me, and I'll be happy to post it for you. I was not able to find it myself.
US government says it's now okay to jailbreak your tablet and smart TV
http://www.theverge.com/2015/10/27/...-smart-tvs-dmca-exemption-library-of-congress
This year the Library of Congress got together and established a handful of now well-known exemptions — like the ability to unlock your smartphone from its carrier — and a slew of new ones covering a range of devices.
Click to expand...
Click to collapse
They are using the term "jaibreak" because they are Apple fanbois, but it's rooting.
schwinn8 said:
I would love to see your reference for this, please. If you can't post it, please PM it to me, and I'll be happy to post it for you. I was not able to find it myself.
Click to expand...
Click to collapse
https://www.eff.org/document/library-congress-2015-dmca-1201-rules
Page 34 explains it. In short though, it says as long as you are rooting it (jailbreaking as they term it on paper) without the intention of doing something illegal, then it is legal as of 2015 still.
Edit: It also states that this is because of the many devices that you ARE able to unlock through the manufacturer directly, falling under fair-use for remaining devices. It continues about e-readers and tables as well (and as I don't own any of those I have not read) and they may still fall under illegal to root as it was in the past. That is until 3 more years (2018) I believe it is when they meet again for new proposals and such.