So what percentage of people here with ZU GPE have broken, malfunctioning camera after the 4.4.3 update?
Anybody find out the cause of failure?
What are the chances that the upcoming 4.4.4 will fix this issue?
It is comforting to know that I am not the only one with a broken camera, but it is so frustrating because there isn't much discussion going on this forum.
Cant add much except 4.4.4 won't fix the camera issue by it's self, it will need other patches above what's in 4.4.4
blueether said:
Cant add much except 4.4.4 won't fix the camera issue by it's self, it will need other patches above what's in 4.4.4
Click to expand...
Click to collapse
Do you know why camera works on 4.4.2 but gets broken in 4.4.3 for some users?
Fix camera http://forum.xda-developers.com/showpost.php?p=52696903&postcount=23
godraxe said:
Fix camera http://forum.xda-developers.com/showpost.php?p=52696903&postcount=23
Click to expand...
Click to collapse
Different camera issue
My camera is broken going from 4.4.2 - 4.4.3.
4.4.2 State
------------------
- Rooted, stock kernel.
- Unlocked boot loader
4.4.3 State
------------------
- Non-rooted, stock kernel.
- Unlocked boot loader.
Same here. Broken ass camera. My phone is basically a giant useless tablet.
I would love to know if people with locked bootloaders have the camera issue as well going into 4.4.3. Unlocking the boot loader normally wipes DRM keys and unless memory fails me, the xperia Z1's camera broke once the boot loader was unlocked. I am wondering if this may have something to do...
egzthunder1 said:
I would love to know if people with locked bootloaders have the camera issue as well going into 4.4.3. Unlocking the boot loader normally wipes DRM keys and unless memory fails me, the xperia Z1's camera broke once the boot loader was unlocked. I am wondering if this may have something to do...
Click to expand...
Click to collapse
If DRM keys being wiped were responsible for the camera breakage, then revering back to 4.4.2 should not bring camera back to life.
Now that the 4.4.4 OTA is released without the camera fix, I really wonder if this broken camera issue will ever be fixed.
I thought the main point of GPE devices were ease of unlocking bootloaders. Google and Sony have totally messed it up if unlocking bootloader killed the camera.
ddslee said:
If DRM keys being wiped were responsible for the camera breakage, then revering back to 4.4.2 should not bring camera back to life.
Now that the 4.4.4 OTA is released without the camera fix, I really wonder if this broken camera issue will ever be fixed.
I thought the main point of GPE devices were ease of unlocking bootloaders. Google and Sony have totally messed it up if unlocking bootloader killed the camera.
Click to expand...
Click to collapse
Have been in contact with Google support twice and their solution is to issue a replacement device.
https://support.google.com/playedition/topic/4397966?hl=en&ref_topic=3450794#contact=1&ts=4381330
adfurgerson said:
Have been in contact with Google support twice and their solution is to issue a replacement device.
https://support.google.com/playedition/topic/4397966?hl=en&ref_topic=3450794#contact=1&ts=4381330
Click to expand...
Click to collapse
Will Sony/Google issue a replacement device for a device with an unlocked bootloader?
Btw, have you tried going straight from 4.4.2 to 4.4.4? Will the camera stay functional?
Btw @adfurgerson thanks for your help. My wife just loves the phone. It is currently stuck at 4.4.2 and I have disabled notification for Google services framework and OTA update notification hasn't shown up for almost 5 days now.
egzthunder1 said:
I would love to know if people with locked bootloaders have the camera issue as well going into 4.4.3. Unlocking the boot loader normally wipes DRM keys and unless memory fails me, the xperia Z1's camera broke once the boot loader was unlocked. I am wondering if this may have something to do...
Click to expand...
Click to collapse
My wife and I each have a Z Ultra GPe, both upgraded to 4.4.3, both stock, not rooted, still locked boot loader. Both cameras function properly.
ddslee said:
Will Sony/Google issue a replacement device for a device with an unlocked bootloader?
Btw, have you tried going straight from 4.4.2 to 4.4.4? Will the camera stay functional?
Btw @adfurgerson thanks for your help. My wife just loves the phone. It is currently stuck at 4.4.2 and I have disabled notification for Google services framework and OTA update notification hasn't shown up for almost 5 days now.
Click to expand...
Click to collapse
I am going to relock with flashtool and hope for the best. I tried asking for a refund so I could order straight from Sony but they wouldn't go for that.
He5aid said:
My wife and I each have a Z Ultra GPe, both upgraded to 4.4.3, both stock, not rooted, still locked boot loader. Both cameras function properly.
Click to expand...
Click to collapse
Thanks. So, whatever it is, it is related to 4.4.3 and above looking for something missing due to the unlocked bootloader. Something that 4.4.2 is not looking for apparently.
And no, unlocked bootloader means no replacement unit...
You want me to put the hammer down?
egzthunder1 said:
Thanks. So, whatever it is, it is related to 4.4.3 and above looking for something missing due to the unlocked bootloader. Something that 4.4.2 is not looking for apparently.
And no, unlocked bootloader means no replacement unit...
You want me to put the hammer down?
Click to expand...
Click to collapse
So are you saying even if I relock they won't replace it?
Also I can't recall reading anywhere about drm keys on GPe.
Edit... There is a warning that you may loose DRM keys when unlocking boot loader, I had forgotten about it.
Well relocking bootloader and updating to 4.4.3 and 4.4.4 still leaves camera broken.
I have owned two GPE versions. The first one I unlocked bootloader and rooted straight away and updated to 4.4.3 after that my camera broke, the wireless display stopped working, and i couldn't use GPS while connected to bluetooth. I RMA'd that one and received a second unit, and i left it stock and didn't unlock bootloader and didn't root, it updated itself to 4.4.3 and everything functions. So I suspect that unlocking the bootloader is what screws with our phones. My problem is that i NEED root to use ARU (AppRadio Unchained lets me use my Pioneer in-car touchscreen to control my phone). Is there anyway to root without unlocking the bootloader? If we can replace our recovery without unlocking the bootloader i think we can achieve this.
llxxjinxxll said:
I have owned two GPE versions. The first one I unlocked bootloader and rooted straight away and updated to 4.4.3 after that my camera broke, the wireless display stopped working, and i couldn't use GPS while connected to bluetooth. I RMA'd that one and received a second unit, and i left it stock and didn't unlock bootloader and didn't root, it updated itself to 4.4.3 and everything functions. So I suspect that unlocking the bootloader is what screws with our phones. My problem is that i NEED root to use ARU (AppRadio Unchained lets me use my Pioneer in-car touchscreen to control my phone). Is there anyway to root without unlocking the bootloader? If we can replace our recovery without unlocking the bootloader i think we can achieve this.
Click to expand...
Click to collapse
You returned it to Google without issue? Towelroot reported working for GPe on 4.4.3 and if I understand correctly it works for locked bootloaders. See post #5 of this thread it was posted before the Sony specific tool was posted so I believe the standard apk was used.
http://forum.xda-developers.com/showthread.php?t=2783982
adfurgerson said:
So are you saying even if I relock they won't replace it?
Also I can't recall reading anywhere about drm keys on GPe.
Well relocking bootloader and updating to 4.4.3 and 4.4.4 still leaves camera broken.
Click to expand...
Click to collapse
Well, I am not saying it is the case, but drm keys being wiped and stuff stopping to work has been commonplace in the Z series ever since the Z was introduced. Also, if memory serves me well, I could have sworn that someone said that X-reality goes bye bye as soon as the bootloader is unlocked.
Having said that, these updates are looking for something that they find in locked bootloaders and that is obviously missing in unlocked ones. Hence, my suggestion for the Drm keys.
One other thought popped into my head yesterday. Back in my evo 3d days, we had an issue where if the correct hboot was not present, the Rom would simply not boot. Something else to consider.... I am leaning towards the drm being responsible though.
You want me to put the hammer down?
llxxjinxxll said:
I have owned two GPE versions. The first one I unlocked bootloader and rooted straight away and updated to 4.4.3 after that my camera broke, the wireless display stopped working, and i couldn't use GPS while connected to bluetooth. I RMA'd that one and received a second unit, and i left it stock and didn't unlock bootloader and didn't root, it updated itself to 4.4.3 and everything functions. So I suspect that unlocking the bootloader is what screws with our phones. My problem is that i NEED root to use ARU (AppRadio Unchained lets me use my Pioneer in-car touchscreen to control my phone). Is there anyway to root without unlocking the bootloader? If we can replace our recovery without unlocking the bootloader i think we can achieve this.
Click to expand...
Click to collapse
You can now root with towelroot - see the thread in the general ZU section, this will allow you to back up the TA as well now.
---------- Post added at 08:53 AM ---------- Previous post was at 08:46 AM ----------
egzthunder1 said:
Well, I am not saying it is the case, but drm keys being wiped and stuff stopping to work has been commonplace in the Z series ever since the Z was introduced. Also, if memory serves me well, I could have sworn that someone said that X-reality goes bye bye as soon as the bootloader is unlocked.
Having said that, these updates are looking for something that they find in locked bootloaders and that is obviously missing in unlocked ones. Hence, my suggestion for the Drm keys.
One other thought popped into my head yesterday. Back in my evo 3d days, we had an issue where if the correct hboot was not present, the Rom would simply not boot. Something else to consider.... I am leaning towards the drm being responsible though.
You want me to put the hammer down?
Click to expand...
Click to collapse
This is interesting... 4.4 on the zu kept x-reality working if the bootloader was unlocked on 4.4
In GPe I don't think x-reality ever stopped working when the BL was unlocked
The next test I guess is to use the new root method, back up TA/DRM keys and then unlock on 4.4.3 or 4.4.4 and see if the camera breaks, then restore the TA and see if that fixes the issue.
After the **** with the Z1 and the broken camera on unlocked BL you would think that they would't make the same mistake again
Has anybody ever been successful at resuscitating the dead camera once it started malfunctioning (besides downgrading to 4.4.2).
I have read a couple of people mentioning that their camera was fixed. @DooMLoRD and @MrSewerPickle.
Could you please share with us how it was done???
Related
How do I tell if my bootloader is unlocked?
I just got the pone and haven't done anything to it yet but I'm seeing options I wasn't expecting in a locked phone like the ability to enable USB debugging and the ability to instanll non-market apps. So could that mean my phone already has an unlocked bootloader? How do I check?
No - the phones all have that. These have nothing to do with unlocked B/L. The ADB connectivity doesn't function as root though.
Standard Android settings...
Thanks. Guess that means I still have root the phone sometime. At least I'm on 2.3.3 and not 2.3.4 so I should be able to avoid the battery issue.
No battery issue here...
There is no battery issue with 2.3.4 it only happens when you try downgrading to 2.3.2 I believe (which I am not going to test myself, there is already enough people who have fallen into this trap), you can still root 2.3.4 too with rootxperia, the only thing that's not possible (yet) is doomlords kernel for overclocking and that's it, everything else is good, and 2.3.4 is so much better over 2.3.3. quicker, panorama pictures, and lots more including swipe inbuilt into the firmware
I can only root with rootXperia if I have an unlocked bootloader. And to me the process for unlocking the bootloader looks trickier than the process for rooting. So yeah I meant the issue when downgrading to 2.3.2.
It's not too tricky, get alejandrissimo to help you out or you can try the offical sony way. but yeah, I forgot that you couldn't use rootxperia without a unlocked bootloader, my bad. it's worth doing though to be honest.
I don't think I can keep a stable enough connection to Mexico for Alejandrissimo to help me out. Also as far as I know SE hasn't made that site yet that they wanted to allow bootloader unlocking (and even if they did it was gonna be region based so my region most likely won't be supported till 2020 or something like that).
At this point however I'm not noticing much I'd like to have and don't that a root would provide me with. I don't want to try custom roms, I'm perfectly happy with stock and my need for a better battery icon is taken care of by a widget so that just leaves better backups (since to full back everything up these apps needs root access)...but the thing is I probably would only need a backup if I wanted to root or flash something in the first place.
Okay fair enough then, yeah I didn't think about the stable connection. well you don't need a real stable connection to get the IMEI code to sony to get the unlock code, the bootloader unlock is here for the neo -> http://unlockbootloader.sonyericsson.com/instructions I don't think it is based on regions, however if the phone is locked to a provider, (from experience) I don't think it will work, (is why I couldn't use this method) up to you if you want to give it a shot though. good luck.
Oh wow thanks. I didn't know about that all. Does the bootloader get relocked upon doing a PC Companion update just like the root is lost? Because I notice that says not to do an OTA update after the bootloader has been unlocked that way.
The BL will remain unlocked whatever you do. Only deliberately relocking using a specific flash regime (available on XDA) will work.
The OTA warning is because once the BL is unlocked, OTA updates may/can fail badly. PC C is fine.
BTW, all this information is already on this forum...
Yeah sorry. I admit I haven't looked around enough. But I thought it was slightly different for every phone.
Search is your friend mate, do a bit of research and enjoy using your phone.
Hello there!
i have been using my OneX+ for a few months now and i honestly hate it. selling my GNexus was the biggest mistake i've made. everything, apart from the internal storage is worse on this phone and i literally have had enough of it. I want to sell it and get either a Nexus 4 or GSIII.
I have been looking around for tutorials etc, but havent really found anything solid and related to this phone. im sure it's an easy thing to do, so if anyone out there knows how to do it, can you please spend a few moments and explain it to me, i will be very greatfull!
thanks in advance
I guess if u are trying to get rid of your one X+ u want to make it in somewhat original condition.
Then u need to relock your boatloader and then run the RUU to get you back to stock.
No one will know its been rooted except the boatloader will show relocked instaed of locked.
So search for RUU and relockong boatloader on the forums for the step by step.
Sent from my HTC One X+
Rularn, it is possible to return bootloader to LOCKED state from UNLOCKED by downgrade of stock ROM ?
Rularn said:
I guess if u are trying to get rid of your one X+ u want to make it in somewhat original condition.
Then u need to relock your boatloader and then run the RUU to get you back to stock.
No one will know its been rooted except the boatloader will show relocked instaed of locked.
So search for RUU and relockong boatloader on the forums for the step by step.
Sent from my HTC One X+
Click to expand...
Click to collapse
well i know how to relock the bootloader, it's quite simple, but problem is, i ran the RUU exe and it failed to revert my phone to stock rom etc. although i didnt relock the bootloader before doing it, would that be why it failed?
thanks
mjenabi2 said:
well i know how to relock the bootloader, it's quite simple, but problem is, i ran the RUU exe and it failed to revert my phone to stock rom etc. although i didnt relock the bootloader before doing it, would that be why it failed?
thanks
Click to expand...
Click to collapse
Yeap, u must FIRST relock than run RUU.
Check sticked threads in general question (U will have full tutorial how to back to stock) - however in bootloader there will be RELOCKED status not LOCKED, so it will be clear visible that u`ve previously unlocked Your device - may cause problem with warranty)
Krzysiec said:
Yeap, u must FIRST relock than run RUU.
Check sticked threads in general question (U will have full tutorial how to back to stock) - however in bootloader there will be RELOCKED status not LOCKED, so it will be clear visible that u`ve previously unlocked Your device - may cause problem with warranty)
Click to expand...
Click to collapse
thanks. im not worried about the warranty thing. i will sell it on ebay without it... and i believe HTC will still honor your warranty if the problem is not software related.
As far as I know u cannot return to LOCKED status after unlocking.
Sent from my HTC One X+
Rularn said:
As far as I know u cannot return to LOCKED status after unlocking.
Sent from my HTC One X+
Click to expand...
Click to collapse
If the device says relocked and i need to send it in for a warranty will it be an issue
The Camera on my HOX+ is terrible, tried the MOD but doesn't help
HTC say i must send it in but don't want in case there's issues
Thanks
camera is poor, change them doesnt help realy.
bootloader lock status has nothing to do with warranty
skdubg said:
camera is poor, change them doesnt help realy.
bootloader lock status has nothing to do with warranty
Click to expand...
Click to collapse
Ok thanks Skdubg
Only reason i thought there was an issue was i've compared photos to an stock standard HTC one x and they much better than my plus when viewed on a pc screen or HDTV
When viewed at actually size the photos are terrible, even video recording stutters a bit, video isn't smooth
Sorry wrong thread to go on about the photo and video quality
But just wanted to know if i factory reset and make stock standard and return bootloader to relocked if HTC will still honor the warranty
Thanks
My understanding is that unlock bootloader = void warranty. It wouldn't matter what you did after that. What a stupid policy - I just got my phone and now I'm afraid to root it. I desperately want to apply the BT call quality fix!
ashamir said:
My understanding is that unlock bootloader = void warranty. It wouldn't matter what you did after that. What a stupid policy - I just got my phone and now I'm afraid to root it. I desperately want to apply the BT call quality fix!
Click to expand...
Click to collapse
That's not my understanding of the terms from http://htcdev.com/bootloader/ :
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
Click to expand...
Click to collapse
and
We strongly suggest that you do not unlock the bootloader unless you are confident that you understand the risks involved. This is a technical procedure and the side effects could possibly necessitate repairs to your device not covered under warranty. If you are still interested in unlocking the bootloader, and you understand the consequences both to your device and to your warranty, then you may refer to the following pages where we have provided the unlocking instructions.
Click to expand...
Click to collapse
Sounds like a pretty good deal given the mobile industries general state of affairs.
No revert; just a flash, flash, flash, restore type thing.
Sent from my HTC One X+
I recently unlocked my bootloader and rooted my phone. I installed TWRP and flashed a couple of custom roms ( GPE & Revolution HD ) I decided i want to go back to stock. I understand so far i gotta unroot, flash stock rom and re lock bootloader. I read something about RUU files. Any one have suggestion or help how i go about this? Again, i have AT&T varient, currently on Revolution HD Rom
Famous22 said:
I recently unlocked my bootloader and rooted my phone. I installed TWRP and flashed a couple of custom roms ( GPE & Revolution HD ) I decided i want to go back to stock. I understand so far i gotta unroot, flash stock rom and re lock bootloader. I read something about RUU files. Any one have suggestion or help how i go about this? Again, i have AT&T varient, currently on Revolution HD Rom
Click to expand...
Click to collapse
There is currently no RUU available as of right now. I think the best you can do for now is to a TWRP restore. There is a stock rooted TWRP in the Android Dev forum. Although this won't un-root you, its closest to stock that you will get. For the future, always make a backup before you root and then you won't have to worry
TheEmpyre said:
There is currently no RUU available as of right now. I think the best you can do for now is to a TWRP restore. There is a stock rooted TWRP in the Android Dev forum. Although this won't un-root you, its closest to stock that you will get. For the future, always make a backup before you root and then you won't have to worry
Click to expand...
Click to collapse
I just ordered my device and still waiting on it to be delivered. I'm already debating on whether or not to root as I've never owned an android phone that i didn't root. From what i understand, the bootloader needs to be unlocked, then s-off, flash recovery and then root. Now, if i'm to do a nandroid of the stock ROM before I root, will I be able to lock the bootloader again, nandroid and s-on in case I need to utilize the warranty? Also, will any warranty bits show up or a tampered flag or any other problem arise that'll indicate it's been farked with? Is there a way to undo those flags? Thanks in advance to TheEmpyre or whomever else can shed some light on this.
EDIT: If the s-off is the only step that will trip the flag, is it possible to leave S, er, ON?
brianray14 said:
I just ordered my device and still waiting on it to be delivered. I'm already debating on whether or not to root as I've never owned an android phone that i didn't root. From what i understand, the bootloader needs to be unlocked, then s-off, flash recovery and then root. Now, if i'm to do a nandroid of the stock ROM before I root, will I be able to lock the bootloader again, nandroid and s-on in case I need to utilize the warranty? Also, will any warranty bits show up or a tampered flag or any other problem arise that'll indicate it's been farked with? Is there a way to undo those flags? Thanks in advance to TheEmpyre or whomever else can shed some light on this.
EDIT: If the s-off is the only step that will trip the flag, is it possible to leave S, er, ON?
Click to expand...
Click to collapse
Unlocking the bootloader trips a flag. When you relock it gets rid of one flag but trips the relocked flag. Soff can get rid of all flags but you have to leave it soff. Turning it back on throws a security flag.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
If you are current AT&T customer, and can go through them for warranty, they do not care in the least whether you are bootloader unlocked, rooted, s-off, etc.
I know AT&T written policy says otherwise (they have the right refuse warranty on modded phones) but in reality they cherish you paying that nice monthly bill every month over the modest cost of a refurb phone.
I've come over from the One X (EVITA) forum, and there were many (possibly dozens) of report from XDA users successfully returning their devices for warranty with bootloader RELOCKED, UNLOCKED, and in some cases even with custom ROMs installed! And I haven't seen any reports otherwise (AT&T denying warranty due to modded phone).
If you are not a current AT&T customer, and have to go through HTC, that is a different story.
But if you are an AT&T customer, my personal opinion is that you do not need to care about being able to return to stock, tripping flags, etc. Just mod away.
redpoint73 said:
If you are current AT&T customer, and can go through them for warranty, they do not care in the least whether you are bootloader unlocked, rooted, s-off, etc.
I know AT&T written policy says otherwise (they have the right refuse warranty on modded phones) but in reality they cherish you paying that nice monthly bill every month over the modest cost of a refurb phone.
I've come over from the One X (EVITA) forum, and there were many (possibly dozens) of report from XDA users successfully returning their devices for warranty with bootloader RELOCKED, UNLOCKED, and in some cases even with custom ROMs installed! And I haven't seen any reports otherwise (AT&T denying warranty due to modded phone).
If you are not a current AT&T customer, and have to go through HTC, that is a different story.
But if you are an AT&T customer, my personal opinion is that you do not need to care about being able to return to stock, tripping flags, etc. Just mod away.
Click to expand...
Click to collapse
I can second this. I just had to replace my m8 because the speakers were crackling like crazy, my bootloader showed relocked and they told me straight up that they didn't care about that as long as it was a hardware problem and not a software problem and replaced it on the spot.
I was under the impression that if you were in your first year of owning the device that faulty hardware would be covered under HTC's factory warranty and not AT&T?
brianray14 said:
I was under the impression that if you were in your first year of owning the device that faulty hardware would be covered under HTC's factory warranty and not AT&T?
Click to expand...
Click to collapse
Looking at the return info, I can see where the confusion might come from. It says "Return directly to manufacturer" for 15 days or more:
http://www.att.com/shop/wireless/returnpolicy.html#fbid=KMGdewZyG_f
But AFAIK, all warranty returns go to AT&T when you work through their warranty department. You send them your defective phone, and they send you a refurb. I haven't had to go through this process myself, but this is what has been reported many times on XDA and other forums.
Any update on this how to lock bootloader for HTC M8 AT&T with 4.4.3 InsertCoin 4.1.1 Rom S-On of course.
How do I lock the bootloader in order to upgrade to stock 4.4.4?
im2c0ol said:
Any update on this how to lock bootloader for HTC M8 AT&T with 4.4.3 InsertCoin 4.1.1 Rom S-On of course.
How do I lock the bootloader in order to upgrade to stock 4.4.4?
Click to expand...
Click to collapse
No "update" on this issue is required. The process has been the same for a couple years or more. Further, you've posted the same/similar question to multiple places, and its been answered already in multiple places.
Connect phone to computer in fastboot mode.
Open command prompt, and type: fastboot OEM lock
From there, you can run the RUU.
Got a stupid question and can't find the stupid question section on this forum for the M8 as in the M7 section. But, I have a new phone which I have upgraded to . I am not new to the rooting and switching roms I have done it since the One X, but , can I flash a custom recovery without unlocking the bootloader? Reason is , I use a app called Privacy Star for call blocking and just discovered by means of me having two identical phones except for the color . One has all the OTA's up to Android version 5.0.2 HTC Sense 6.0 the other is straight ouf the box and no updates, software Android 4.4.2 Sense 6.0. The app seems to work fine with 4.4.2 but the app makes the phone ringer silent after a blocked call and it has to be put in recovery and recovered or reboot the phone to get the ringer back. I know that flashing a custom recovery removes the ability to take OTA's and want to keep the phones at 4.4.2 , at least for a day or two. So can I flash a custom recovery such as TWRP without rooting? and RUU the one phone with the updates back to 4.4.2? Make sense? I hope so.
leesumm said:
Got a stupid question and can't find the stupid question section on this forum for the M8 as in the M7 section.
can I flash a custom recovery without unlocking the bootloader? I know that flashing a custom recovery removes the ability to take OTA's and want to keep the phones at 4.4.2 , at least for a day or two. So can I flash a custom recovery such as TWRP without rooting?
and RUU the one phone with the updates back to 4.4.2? Make sense?
Click to expand...
Click to collapse
I think someone did a "stupid question" thread for this section at one point, long ago. But nobody really used it, it didn't get stickied, and quickly became buried among the other threads.
No, you can't install custom recovery without unlocking the bootloader. But you can restore to stock recovery when/if you want to install an OTA.
You can RUU back to 4.4.2 if you use sunshine ($25) to s-off the phone; which removes the version check, and allows you to "downgrade".
redpoint73 said:
I think someone did a "stupid question" thread for this section at one point, long ago. But nobody really used it, it didn't get stickied, and quickly became buried among the other threads.
No, you can't install custom recovery without unlocking the bootloader. But you can restore to stock recovery when/if you want to install an OTA.
You can RUU back to 4.4.2 if you use sunshine ($25) to s-off the phone; which removes the version check, and allows you to "downgrade".
Click to expand...
Click to collapse
Thanks, wasn't sure and its been a long time since I have messed with a stock phone . I really didn't want to void the warranty just yet as the phone isn't much over 24 old so far and wanted to let it "settle" in before doing any mods on it.
leesumm said:
Thanks, wasn't sure and its been a long time since I have messed with a stock phone . I really didn't want to void the warranty just yet as the phone isn't much over 24 old so far and wanted to let it "settle" in before doing any mods on it.
Click to expand...
Click to collapse
If you want, since the phone has older software (4.4.2) you should be able to temp root and s-off with sunshine ($25) which can also unlock the bootloader without using HTCDev.com. And HTC will therefore not have a record of you unlocking the bootloader. And with s-off, all can be returned to full stock (LOCKED bootloader, s-on, etc.) so HTC would never be any the wiser.
But also note that if you purchased the phone through AT&T, modifying the phone by unlocking the bootloader (root, etc.) does not actually void your warranty. AT&T actually changed their warranty terms a year or 2 ago. The only thing that voids the warranty are physical damage and water damage. There have been numerous reports of folks that successfully got warranty service from AT&T with unlocked bootloaders. But that is just through AT&T. HTC is a whole other story.
redpoint73 said:
If you want, since the phone has older software (4.4.2) you should be able to temp root and s-off with sunshine ($25) which can also unlock the bootloader without using HTCDev.com. And HTC will therefore not have a record of you unlocking the bootloader. And with s-off, all can be returned to full stock (LOCKED bootloader, s-on, etc.) so HTC would never be any the wiser.
But also note that if you purchased the phone through AT&T, modifying the phone by unlocking the bootloader (root, etc.) does not actually void your warranty. AT&T actually changed their warranty terms a year or 2 ago. The only thing that voids the warranty are physical damage and water damage. There have been numerous reports of folks that successfully got warranty service from AT&T with unlocked bootloaders. But that is just through AT&T. HTC is a whole other story.
Click to expand...
Click to collapse
One phone has 4.4.2 software and the other has 5.0.2 software, I didn't catch the newest one soon enough and my wife did the OTA without me knowing it. The only reason I wanted the older software was the fact the app I like has a glitch in it with the newer software update and it silences the ringer . The app works fine on the phone with the 4.4.2 software I just wanted to make sure it didn't update itself
How To Fix Camera Problem Of Z5C?
How To Enable Software Update For Rooted Users?
Hi Friends,
After unlocking bootloader/rooting some of you might be experiencing problems with z5c camera such as Green lines on camera interface, Video freezing, Error in focus etc.... This is a problem with DRM keys associated with z5c bootloader.
According to me this problem happens for those who unlocked their bootloader and re-locked the same for software updates.
The only way that i found to fix this issue is to unlock the re-locked bootloader. As soon as you unlock the bootloader your camera will start working perfectly. By doing the same you will not be able to have official software updates (OTA) from Sony. In order to get software update you no longer need to Re-Lock the bootloader. Install a custom recovery and flash SuperSu. After flashing SuperSu go to its settings and scroll down until you find an option called "Enable Pro" Activate the option (If you want to support the developer of SuperSu please do not hesitate to purchase its pro/donation package from playstore) . This will spoof Sony Update Server and you will start receiving updates. Note: A reboot may be required .
Done
Hope this will resolve your problems.
Feel free to write me if you experience any trouble.
Thank You!
Arun Gopinath
[email protected]
heptyle said:
How To Fix Camera Problem Of Z5C?
How To Enable Software Update For Rooted Users?
Hi Friends,
After unlocking bootloader/rooting some of you might be experiencing problems with z5c camera such as Green lines on camera interface, Video freezing, Error in focus etc.... This is a problem with DRM keys associated with z5c bootloader.
According to me this problem happens for those who unlocked their bootloader and re-locked the same for software updates.
The only way that i found to fix this issue is to unlock the re-locked bootloader. As soon as you unlock the bootloader your camera will start working perfectly. By doing the same you will not be able to have official software updates (OTA) from Sony. In order to get software update you no longer need to Re-Lock the bootloader. Install a custom recovery and flash SuperSu. After flashing SuperSu go to its settings and scroll down until you find an option called "Enable Pro" Activate the option (If you want to support the developer of SuperSu please do not hesitate to purchase its pro/donation package from playstore) . This will spoof Sony Update Server and you will start receiving updates. Note: A reboot may be required .
Done
Hope this will resolve your problems.
Feel free to write me if you experience any trouble.
Thank You!
Arun Gopinath
[email protected]
Click to expand...
Click to collapse
what are you doing for ta keys. are you using the drm fix or your backed up ta keys?
Thanks man, really needed this.
MattyCurrann said:
Thanks man, really needed this.
Click to expand...
Click to collapse
Always Welcome!
I'm selling my Xperia Z5 Compact. Will I sell it with the bootloader unlocked so the next person to have it doesnt experience problems with the camera?
many thanks
MattyCurrann said:
I'm selling my Xperia Z5 Compact. Will I sell it with the bootloader unlocked so the next person to have it doesnt experience problems with the camera?
many thanks
Click to expand...
Click to collapse
If Unlocked Bootloader there won't be any problem for Camera. So Go ahead!
heptyle said:
If Unlocked Bootloader there won't be any problem for Camera. So Go ahead!
Click to expand...
Click to collapse
Does this mean they wont be able to receive the latest updates though? How do I get it so I reset it and the camera is fine and they can receive OTA updates?
MattyCurrann said:
Does this mean they wont be able to receive the latest updates though? How do I get it so I reset it and the camera is fine and they can receive OTA updates?
Click to expand...
Click to collapse
The only way that i know to fix this issue is by rooting and installing SuperSu Pro. Let the reciever do the same and they might be able to use Camera and Software update without any problem.
heptyle said:
The only way that i know to fix this issue is by rooting and installing SuperSu Pro. Let the reciever do the same and they might be able to use Camera and Software update without any problem.
Click to expand...
Click to collapse
Dammit. I need it to be normal so I can sell it haha.
I'll just update it to the latest version, unlock the bootloader and sell it so they have a functioning camera.
civicsr2cool said:
what are you doing for ta keys. are you using the drm fix or your backed up ta keys?
Click to expand...
Click to collapse
I haven't made a backup of ta keys.
If i had i would have fixed both software update and camera problem.
MattyCurrann said:
Dammit. I need it to be normal so I can sell it haha.
I'll just update it to the latest version, unlock the bootloader and sell it so they have a functioning camera.
Click to expand...
Click to collapse
Very sorry. If i find a way i will definitely pass it to you. Thank You
heptyle said:
I haven't made a backup of ta keys.
If i had i would have fixed both software update and camera problem.
Click to expand...
Click to collapse
Well technically you did come up with a way to fix the camera and OTA updates, just not when you reset the device.
Thanks anyway man, helped me a lot!
heptyle said:
I haven't made a backup of ta keys.
If i had i would have fixed both software update and camera problem.
Click to expand...
Click to collapse
I'm not tracking the flow of this very well.
You're unlocking the bootloader loosing ta partition, not applying DRM fix, then re locking the bootloader and able to use x reality and 23mp features? How? What shows up in the *#*#7378423#*#* menu?
civicsr2cool said:
I'm not tracking the flow of this very well.
You're unlocking the bootloader loosing ta partition, not applying DRM fix, then re locking the bootloader and able to use x reality and 23mp features? How? What shows up in the *#*#7378423#*#* menu?
Click to expand...
Click to collapse
I don't know very well about ta keys. I have not made any ta backup. By relocking the bootloader iam experienceing problems with video,focus etc...
heptyle said:
I don't know very well about ta keys. I have not made any ta backup. By relocking the bootloader iam experienceing problems with video,focus etc...
Click to expand...
Click to collapse
You may have missed a few steps in the root and unlock bootloader process then. You need to apply the DRM fix to obtain features lost in the unlock bootloader process.
civicsr2cool said:
You may have missed a few steps in the root and unlock bootloader process then. You need to apply the DRM fix to obtain features lost in the unlock bootloader process.
Click to expand...
Click to collapse
Oops. My phone restrict me from applying drm fix. If applied drm fix the camera problem persist.