Help needed - Black Camera after restore - Xperia Z3 Compact Q&A, Help & Troubleshooting

It's the LTE-A version of Z3C (D5803), which shows the following issue:
What I've done so far:
Open Bootloader on all of our 5 Z3C.
Installed this ROM:
http://forum.xda-developers.com/showpost.php?p=58363452&postcount=336
Rooted phone
Installed recovery and SuperSU
Then configured installed and configured all apps on NO1-"prototype" where everything works fine up to now.
Then entered recovery and did complete backup onto SD1.
Entered recovery on all other 4 Z3C and did a complete restore.
On all 4 copies the camera app will open but only with total black screen while the original (first one) works normally. Tried to get rid of this issue by changing settings, delete all camera data and even transfer the camera apps via Titanium Backup separately from the working prototype to one of the copies - unfortunately without any success.
How can I resolve this problem?

Hello I have the same problem. Ich have 2 Xperia Z3 Compact. From my first one my screen dispensed. So I made a TWRP BackUp of the Data Partition and restored it on the second phone. Everything seems to work, except the camera. The user interface features seem to work but there is no image coming through the camera.
I still have a locked bootloader and the latest firmware installed available.
Any idea, which (configuration) file to delete, so my camera will work again?

Related

[Q] Recovery Help - CM10_LINARO_20130118_ODEX_IRX120, DemonsBlood v8

Okay, I did a ton of research on this, but when I flashed the ROM, I ended up with some major problems. I hope someone can help. Here's the deal:
Started with the stock ROM (Gingerbread 2.3.6), no overclocking
Backed up apps & data with Titanium Backup
Backed up contents of both internal and external SD card to my PC
Backed up phone to external SD card using CWM 6.0.1.2
Performed ROMwipe
Flashed odexed build, CM10_LINARO_20130118_ODEX_IRX120
Flashed DemonsBlood v8
Flashed Gapps
Rebooted
Now, the new ROM was working, but I started having trouble navigating and certain apps would force close, or I'd get messages that certain things had stopped working. Also, I could not figure out how to set up my home screens and wallpapers and settings and such the way I wanted. So I decided to go back to my stock ROM. But when I flashed my backup, the phone now acts as if it's been factory reset (although I can still boot back into CWM recovery). Also, when I download Titanium Backup, Facebook, and other apps, they force close upon launch.
I have wiped the ROM, fixed permissions, and tried again, with no success. I've copied the files I backed up to my PC back to the phone, but no joy there, either.
Ideally, I'd love to get my phone back to where it was before I attempted this - or, as a second choice, go forward and use the new ROM & Kernel, because I was pretty excited about trying it out. But I feel like I've lost a ton and now it's not working properly at all.
Can someone help me restore this? And tell me where I went wrong?
UPDATE: In CWM Recovery, I selected flash image from external SD card and selected CM10_LINARO_20130118_ODEX_IRX120, then rebooted. Now it gets stuck at the boot screen (Samsung Galaxy Exhibit 4G, Exclusively from T-Mobile). I tried booting into recovery, but no luck - same result, stuck at the boot screen. So I booted into HBOOT (vol down + power), got a warning about a custom ROM with a choice to reboot or proceed. Since I figured rebooting would just put me back at the boot screen, I chose to proceed. It is now showing the following:
ODIN MODE
PRODUCT NAME: SGH-T679
CUSTOM BINARY DOWNLOAD: NO
CURRENT KERNEL: SAMSUNG !!
Then there's the android icon and underneath it says:
Downloading...
Do not turn off target!!
Sigh. Help.
Okay, I got out of ODIN mode and managed to reboot into CWM recovery. Progress! I wiped the ROM, flashed CM10_LINARO_20130118_ODEX_IRX120, SpeedyGonzalez_OC_1.5.5, and Gapps, and rebooted.
So now I'm running CM10 Linaro, Odexed, with SGK. Okay. **deep breath** The first thing I see after the boot screen is "Welcome, choose your language" and then "Unfortunately, Google Search has stopped."
OK.
Signing in with Gmail . . . (screen does not auto-rotate at this point)
Contacting Google, then again "Unfortunately, Google Search has stopped."
Completed setup, then again "Unfortunately, Google Search has stopped."
Going to Play Store to get Titanium Backup. And a few more apps.
Auto-rotate now works.
Into Titanium Backup and I get this warning: "This device's Android ID has changed. This normally happens after a device replacement or factory reset. The Android ID is the most common way for apps to identify the device. Any app that relies on it for security/licensing purposes may stop working (or need to be reconfigured) unless you restore the previous Android ID now." with a choice: Keep the new one, or restore the old one (I only have the free version, so this choice is not available).
Should I get my apps back from Play Store or Titanium Backup or both? (I now know to restore the "app only" from Titanium Backup.)
I'm going to keep plugging away at this. Any suggestions for my next steps?
DarthJosef said:
Okay, I got out of ODIN mode and managed to reboot into CWM recovery. Progress! I wiped the ROM, flashed CM10_LINARO_20130118_ODEX_IRX120, SpeedyGonzalez_OC_1.5.5, and Gapps, and rebooted.
So now I'm running CM10 Linaro, Odexed, with SGK. Okay. **deep breath** The first thing I see after the boot screen is "Welcome, choose your language" and then "Unfortunately, Google Search has stopped."
OK.
Signing in with Gmail . . . (screen does not auto-rotate at this point)
Contacting Google, then again "Unfortunately, Google Search has stopped."
Completed setup, then again "Unfortunately, Google Search has stopped."
Going to Play Store to get Titanium Backup. And a few more apps.
Auto-rotate now works.
Into Titanium Backup and I get this warning: "This device's Android ID has changed. This normally happens after a device replacement or factory reset. The Android ID is the most common way for apps to identify the device. Any app that relies on it for security/licensing purposes may stop working (or need to be reconfigured) unless you restore the previous Android ID now." with a choice: Keep the new one, or restore the old one (I only have the free version, so this choice is not available).
Should I get my apps back from Play Store or Titanium Backup or both? (I now know to restore the "app only" from Titanium Backup.)
I'm going to keep plugging away at this. Any suggestions for my next steps?
Click to expand...
Click to collapse
i would suggest using TWRP recovery, backing up your internal, wipe cache 2x , wipe dalvik 2x , factory reset 2x, wipe rom 2x, and wipe internal 2x. then flash rom and gapps

What good are backups if I can't restore?

I have MOTO X 1053, unlocked bootloader. Runs Android 4.2.2 and this is where I want to stay (perfectly compatible with my car Bluetooth; I am not missing any features from later Android versions and don't want to deal with problems that come with them and potential incompatibility with my car after an upgrade considering downgrade is not possible).
Recently I noticed that phone is never in 4G LTE anymore - only in 4G. Before it was in LTE mode all the time. I downloaded an app from the market to force it into LTE and it worked but as soon as I reboot the phone is back in 4G (HSPA) mode.
I suspect the reason it was no longer in 4G was that I messed too much with Xposed toggle that toggles between 2G / 2G or 3G / 3G only but I am not sure.
So I made a TWRP backup (and a separate backup for Contacts, good thing that I did) and then tried to restore the backup from a year ago. Result: boot loop.
Tried to restore latest backup - same result, boot loop.
I then copied all I could (sdcard, /system, /data, /data/data) from the phone via ADB and returned to stock Android 4.2.2 using instructions from here: http://mark.cdmaforums.com/MotoX-ReturnToStock.html (option 5 using mfastboot)
After initial setup phone immediately connected to 4G LTE, so I flashed TWRP recovery (newer version than I had before), rooted and spent a day setting the phone up the way it used to be.
Nowhere near done I decided to see if TWRP restore will work now. So I take a backup and guess what? The same result. Restore (with MD5 verification) completes without any errors but then I am stuck in bootloop again.
I then booted into recovery, did factory reset from recovery and it worked - after reboot phone starts initial setup.
Can anyone suggest what I may be doing wrong? Why does restore always cause the boot loop?

SM-G800F rooted stuck in bootscreen (got TWRP access)

I wanted to try and hopefully learn little about rooting. Have been reading forumposts and tutorials for hours before I started.
Then I got this problem that I have been trying to solve for hours. But my conclusion is I need help solving it.
Tested on this phone that just were collecting dust.
Samsung Galaxy S5 Mini (SM-G800F) and I think it was running 4.4.2. (this is all I remember off the top of my head)
Problem / What happend (long version):
Rooted phone. Downloaded SuperSU and Flashify and installed TWRP 3.0.0 (http://forum.xda-developers.com/galaxy-s5-mini/orig-development/recovery-twrp-3-0-0-t3313775). I had no SD-card so I skipped doing a backup. Everything worked fine (for a normal user). Downladed a Root Uninstaller app also Debloater-setup-v3.90.exe (http://forum.xda-developers.com/devdb/project/dl/?id=12623). Did not freeze or uninstall anything before checking in this forum that it was OK. But after a while I could not access my homescreen it just turned up blank but I could still use other functions/apps. Rebooted the phone in order to get it to work but got stuck at the bootscreen. Tried to fix it via TWRP but the program freezes after a while or just reboots the phone back into Samsung bootscreen.
Problem / What happend (short version):
Rooted - got Flashify and SuperSU
TWRP 3.0.0 installed (no backup made)
Debloater-setup-v3.90.exe and some Root Uninstaller app used (searched on this forum before doing any changes)
Homescreen just blank, other functions/apps worked
Rebooted the phone and got stuck at Samsung bootscreen
TWRP access but the program freezes/reboot after short time
I did try "Factory reset". But the screen froze and the phone slowly started to heat up.
Later on I searched about it and it might have something to do with KNOX?
Any solution is fine since I don't have anything thats need to be saved. I can try any working stock/custom ROM (just not sure how to get it into the phone, yet).
Yes I am a novice so the simplest thing might even work.
Have you tried to flash stock ROM for your device using Odin? If it fails you may want to check this:
http://forum.xda-developers.com/galaxy-s5-mini/help/g800f-failed-odin-firmware-upgrade-fail-t3131782
If it doesn't fix your phone you may have a hardware problem.

K50-T5 Several Problems (Settings, System Update)

ive used the xda tool for k50 to root and flash touch recovery, taken a backup and flashed xposed. there was no chance to recover after bootloop cause for whatever reason, it wasnt saved.. even rom flash wont work in recovery and a backup ive found is to big to load with bad connection (google storage has no resume feature). as the phone staid in this state some hours, it surprisingly fixed itself, coming up with stock but system updates arent working. no problem until yet. but now the settings app closes instantly without a message - any ideas?

stock rom lockscreen problems

Hi, this is my first post and im having problems with my A6.
I tried to install TWRP wich mostly worked fine, but i didnt follow the tutorial correctly wich left my device boot looping at the boot-logo (i didnt install the zip files needed),
so i thought i soft-bricked my device and i downloaded correct stock rom versions from [cant post outside link because im new, but it would go here]
and installed it with Odin3.
This has worked fine and i restored it again, but for some reason if i set the lockscreen protection (like PIN or Fingerprint) it first wont work (but it shows changed in settings)
and when you reboot the device it soft-bricks at the lockscreen and keeps showing the samsung logo then lockscreen for 1 second and samsung again etc. (this wont brick if i dont set any protection)
I have tried a lot of things like installing TWRP again and clearing cache but none seem to fix the problem (other than doing a factory reset).
so im asking here if someone has a clue to what is happening?
EDIT: i will try to install a older version and try to update it with the official updater and i will report back shortly
Results: It did fix my problem with the lockscreen but if i flash TWRP and install Magisk it wont work again
EDIT2: apparently if i wait long enough at the lockscreen-bootloop(atleast couple of minutes) it will grant me access but the protection still doesnt work
EDIT3: Im using Android 9 and i noticed that this is probably the cause, but i didnt find a updated version

Categories

Resources