After flashing my new dual-sim XZ1 with Central Europe firmware in order to use the fingerprint sensor. (following this guide), I am having camera issues.
After googling around, I seem to have the symptoms of having erased the camera DRM keys from unlocking the bootloader (stock camera app does not take pictures, other apps result in solid green screen).
eg. https://forum.xda-developers.com/xperia-xz1/help/camera-doesnt-lock-bootloader-t3718051
However, the service menu shows that I did not 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"
}
What happened? Did the firmware just not install correctly?
Can I just try to re-flash the Central Europe firmware (and hope it fixes the camera while enabling fingerprint), the original NA firmware (fix camera but back to no fingerprint) or another region?
Or did the DRM keys really get deleted, meaning I am screwed with the camera? Thankfully, I still have a few days to return the phone.
dustygator said:
After flashing my new dual-sim XZ1 with Central Europe firmware in order to use the fingerprint sensor. (following this guide), I am having camera issues.
After googling around, I seem to have the symptoms of having erased the camera DRM keys from unlocking the bootloader (stock camera app does not take pictures, other apps result in solid green screen).
eg. https://forum.xda-developers.com/xperia-xz1/help/camera-doesnt-lock-bootloader-t3718051
However, the service menu shows that I did not unlock the bootloader.
What happened? Did the firmware just not install correctly?
Can I just try to re-flash the Central Europe firmware (and hope it fixes the camera while enabling fingerprint), the original NA firmware (fix camera but back to no fingerprint) or another region?
Or did the DRM keys really get deleted, meaning I am screwed with the camera? Thankfully, I still have a few days to return the phone.
Click to expand...
Click to collapse
Hi,
I currently running same device and quite the same update version without your issue.
My s1 boot version is 82 (yours is 78)
Custo version and active custo slightly differs too (in versionning).
Try to factory reset via computer (Sony companion).
If still no success, send it to repair workshop and claim warranty (software update pushed without success).
Keep us informed bro
I used Xperia companion to repair software and everything was fixed. (It automatically restored the CE firmware as I still have fingerprint)
Probably something went wrong in my initial firmware flash, maybe an important camera-related file in the wrong place or something. But it's good to know that the green camera is not solely a DRM-key issue.
Download the firmware with xperifirm and and try flashing with newflasher instead if you're using flashtool. After having the same issue on any firmware I tried this seemed to fix it.
Related
For some reason my last 2 posts have been closed
http://forum.xda-developers.com/showthread.php?t=1233502
Attempted 2.3.3 with 0.71 baseband, phone just goes in continuous boot_loop. Ive tried almost every available baseband with no results.
Here is what I have attempted so far:
1. Flash tool and forum instructions:
a) Device will take any 1.6 (branded or unbranded) firmware but wont allow to use any features of interface other then emergency calling
b) 2.1 firmware with different revisions/baselines have been attempted as well but device just wont boot at all.
c) after flashing with 2.3 firmware device goes in to constant boot_loop.
2. SEUS couldn't locate the new software as my phone has latest software available from the server. (however I'm still on 1.6 )
3. Same with SE Companion, it comes up with the message that software is not available for my phone yet.
brutus* said:
For some reason my last 2 posts have been closed
http://forum.xda-developers.com/showthread.php?t=1233502
Attempted 2.3.3 with 0.71 baseband, phone just goes in continuous boot_loop. Ive tried almost every available baseband with no results.
Here is what I have attempted so far:
1. Flash tool and forum instructions:
a) Device will take any 1.6 (branded or unbranded) firmware but wont allow to use any features of interface other then emergency calling
b) 2.1 firmware with different revisions/baselines have been attempted as well but device just wont boot at all.
c) after flashing with 2.3 firmware device goes in to constant boot_loop.
2. SEUS couldn't locate the new software as my phone has latest software available from the server. (however I'm still on 1.6 )
3. Same with SE Companion, it comes up with the message that software is not available for my phone yet.
Click to expand...
Click to collapse
U probelly doing something wrong
can you elaborate on this?
Hey take ur phone in flash mode after u see this screen in flash tool...
{
"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 sahibunlimited:
I'm not new_be to the flash process, did you read my initial post? Specifically->( Device will take any 1.6 (branded or unbranded) firmware but wont allow to use any features of interface other then emergency calling) I think this has to be resolved first before proceeding any farther....
Thanks
Folk, anyone? I need your help desperately....
Folks* sorry - TYPO
I held off updating my XZU to 4.3 until root was found, as I don't want to live without it (because of: Titanium backup, VPN software, full linux install on uSD card).
My XZU has an unlocked bootloader, too, as well as being rooted. I'd also modified /system/build.props too.
When I saw the OTA, I tried it and it failed without giving a reason, so I booted up Windows and used Sony PC Companion, and it too failed:
{
"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"
}
I've looked at many XZU update threads and none seem to mention this specific issue.
When the tool runs, it takes a minute to "prepare" (it seems to have kept stuff it downloaded the first time). The phone does stuff, screen goes blank. Then the update fails giving the above message. The phone is then dead, and I have to unplug the USB before I can turn it on.
I restored the standard build.props from a backup copy. Do I need to relock the bootloader? Remove SuperSU and unroot?
Laptop computer has lots of free disk space, and is running standard win7pro-x64, nothing special installed.
thanks for any ideas.
I think that it is the unlocked bootloader?
I just flashed the ce 290 ftf when I had some error in pcc. Might have been the same one.
Rooting is easy on 290 if you have an unlocked bootloader
it's not root, because I unrooted device, so I am guessing its the unlocked bootloader. I've never managed to get Barclays Bank mobile app to work as it complains about phone being rooted, still doesn't work, so it must be detecting the system modified flag (this is using the older version of the app which was happy to run on a fully p0wned Galaxy Note 2).
OK, it was the unlocked bootloader. OTA update now working.
thanks!
Hello,
After unrooted and re-locked (bootloader) my Nexus 9.
When i boot it, i got this:
{
"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"
}
"This is a development device not intended for production use"
After that, I have flashed the stock rom 6.0.1,so I'm 100% stock now, but I still get this message when the device boot
Is it a bug, or my seller sold me a tablet supposed to be not sold?
Do you think I can ask for a replacement? Because I would like to sell it and buy a other tablet... But with this weird message at the boot, I can't expect a lot from it...
Thanks
Strange. I am interested and want to know more.
The warning only recently appeared?
dmantilal said:
Strange. I am interested and want to know more.
The warning only recently appeared?
Click to expand...
Click to collapse
Just after re-locked my device. So i have unlocked it again to flash the last 6.0.1 stock rom, locked the bootloader, and the red message is still here. But I have seen that, if I unclock the bootloader, the message disappears, and if I lock it, the message appear... Strange.
One other thing, (with bootloader locked), I have an ota update, 7,7mb, but when I update, it fail each time
So if I send it to HTC, I think they will change it with a new one, because even with a factory reset, flash stock rom, I don't know what more they can do.
And I have light bleed on the screen, so i really hope they will give me a new one!
That's strange. I don't know whether that red message appears even if you lock the bootloader with everything being stock, but you may try this method: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Edit: If OTA update fails, your device may not be completely stock. Try troubleshooting by consulting the recovery log, or use the "flash-all.bat" to flash stock ROM again.
LeoYL said:
That's strange. I don't know whether that red message appears even if you lock the bootloader with everything being stock, but you may try this method: http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Edit: If OTA update fails, your device may not be completely stock. Try troubleshooting by consulting the recovery log, or use the "flash-all.bat" to flash stock ROM again.
Click to expand...
Click to collapse
Ok thanks for your help
I have send an email to HTC to ask for a replacement. I have seen that some people who got the same issue, (even without root or unlock bootloader) got a replacement :fingers-crossed: . And I have ugly light bleed on the screen, so I really hope I will got a replacement too
If the OTA fails then you aren't full stock..
DITTO to downloading the google stock image and flashing using the included flash-all.bat.
Greetings community I have a big problem with my Z5 Compact E5803.
A couple of months ago I unlocked the Bootloader, I rooted it and never had any problem (I did all this in the version of Android 6.0.1) until I decided to update it by Flashtool to the latest existing version of Nougat (I downloaded the firmware E5803_32. 4.A.1.54_Generic LAM, through XperiFirm).
The fact is that by mistake I included these options in the firmware flash:
{
"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"
}
Now the problem is that I can not flash any kernel to root my phone, since I always get the same message in both Flashtool and Fastboot mode; "FAILED (remote: command not allowed)", I can not unblock or block the bootloader again, my cell phone does not recognize the nano SIM, and the screen freezes when I enter the camera application.
I made several attempts to flash again the firmware I had before flashing Nougat, Marshmallow (32.2.A.0.224_R7C_Latin America Generic_1299-2789.ftf), I tried to block the bootloader by Flashtool and unlock it again, according to the program all right but when reviewing the phone keeps appearing "Rooting status: unknown".
Community, I do not know what else to do, I would be very grateful for a definitive solution, thank you :crying:
PD.: I had posted this before, but I think I did it in the wrong place
I will be attentive to your comments and suggestions community and if the photos are not published in the post I will gladly pass the link :good: where you can see them. Sorry for my bad english
I do not know what you can do now
but I know where you were wrong , you did not have to tick SIMLOCK
Flash lollipop?
mlleemiles said:
Flash lollipop?
Click to expand...
Click to collapse
Yesterday I tried and unfortunately it did not work
Well, flashtool should backup your previous TAs. Find them at C:/user/.flashTool/registeredDevices/serial number/rawta/date.fta
Backup
do not back up with Flashtool but I have a backup made with this tool:
https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
I have the file:
TA_E5803_XXXXXXXXXX_xxxxxxxx-xxx.img :victory:
perhaps this helps:
Restoring TA to factory state
https://forum.xda-developers.com/showpost.php?p=74041813&postcount=217
I cannot give any further advice, as I am not aware what the "Misc TA" options actually do. good luck
Device is a pretty much new LG V30 from verizon, running android 8.
I have done pretty much nothing with the device yet. No root, no tinkering, nothing. I accidentally accepted the software update request it showed me today, which I didn't want. I shut the device down but everytime I would turn it on it would start the update progress.
The only other option I had was booting into recovery, so I did that. I was presented with the following options:
{
"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 I went with factory reset. After that the phone won't boot anymore, and all I see is this screen:
What can I do now?
Again: No root. No unlocked bootloader. Nothing. I used LG's "require password on boot" feature though, which I assume is equal to android's full disk encryption. (?)
I talked to LG already since it's under warrenty (got it literally last week) - LG however told me the warrenty is void because there is a small crack on the back of the phone. WTF? Is that even true? I didn't drop the phone. I don't even know where the crack comes from. It's small. Shouldn't the warrenty cover that TOO instead of voiding the warrenty for everything else? Like jesus christ all I want is LG to fix my software why does a crack on the back matter?
From what I see my only option is to access fastboot and re-flash the ROM? The thing is: How do I access fastboot on this phone? Power and Vol- brings me into recovery (stock) everytime. Are there flashable images for the V30?
No one knows what I should try or what I could look into? This doesn't sound like it could be something overly complex to me.
Issue still persists. I had a talk with verzion at their store and they said I'd have to pay a $149 deductible. So what can I do now?
I'm assuming flashing a ROM via fastboot. Two questions:
1) Where can I get the ROM from?
2) How can I access fastboot on this phone? The method suggested everywhere puts me in LG's stock recovery, not in fastboot.