As the title says the camera on my Z3 + does not work. Neither the back nor the front. I bought it today very economical, it is still submersible and the only problem that I indicated the previous owner was that the camera did not work since it updated to Nougat. I tried with Flashtool to upgrade to 7.1.1 and it did not do any good, the cameras do not work and the flash synonymous ideas?
Ju4n_ said:
As the title says the camera on my Z3 + does not work. Neither the back nor the front. I bought it today very economical, it is still submersible and the only problem that I indicated the previous owner was that the camera did not work since it updated to Nougat. I tried with Flashtool to upgrade to 7.1.1 and it did not do any good, the cameras do not work and the flash synonymous ideas?
Click to expand...
Click to collapse
As you mentioned it is having issues with Nougat, try flashing Marshmallow (Clean Flash). If you are flashing different version from the installed, it should be a clean flash, else so many issues will arise.
[email protected] said:
As you mentioned it is having issues with Nougat, try flashing Marshmallow (Clean Flash). If you are flashing different version from the installed, it should be a clean flash, else so many issues will arise.
Click to expand...
Click to collapse
I fix it changing the camera. Was hardware
Related
Hi guys! I have a Sony Xperia Z1 Compact phone. So my story begins when I installed a stock Android 5.1.1 on it, and I tried to install the original Xposed, but after booting it showed the SystemUI/everything fine for a sec, then it all got black. However, I could uninstall it, and install an unofficial Xposed by romracer. Anyway, that was a couple months ago, and now I saw it there is a version 79.1/80 and I'm asking that if his version worked with my phone, would this Samsung version one could work with mine? I can't find any Xposed frameworks by romracer anymore. I have v74 by the way (20150911).
So, what do you guys suggest?
Oh, and on android 5.0.2 the official Xposed worked fine. Maybe Sony changed some things since then...
And I don't know what was the problem with the original one, I couldn't do anything on my phone. (No logcat or anything.)
Or maybe the new original version would work?
Thanks in advance guys!
kornelkahh said:
Hi guys! I have a Sony Xperia Z1 Compact phone. So my story begins when I installed a stock Android 5.1.1 on it, and I tried to install the original Xposed, but after booting it showed the SystemUI/everything fine for a sec, then it all got black. However, I could uninstall it, and install an unofficial Xposed by romracer. Anyway, that was a couple months ago, and now I saw it there is a version 79.1/80 and I'm asking that if his version worked with my phone, would this Samsung version one could work with mine? I can't find any Xposed frameworks by romracer anymore. I have v74 by the way (20150911).
So, what do you guys suggest?
Oh, and on android 5.0.2 the official Xposed worked fine. Maybe Sony changed some things since then...
And I don't know what was the problem with the original one, I couldn't do anything on my phone. (No logcat or anything.)
Or maybe the new original version would work?
Thanks in advance guys!
Click to expand...
Click to collapse
Use the latest official Xposed version from rovo89 (v80, SDK22) instead of any romracer versions (which are outdated by now).
^yeah I know they're outdated. Then should I take the risk, and try to flash the original version? Like I said, my whole phone went black with the original one back in September (the screen was on though)
kornelkahh said:
^yeah I know they're outdated. Then should I take the risk, and try to flash the original version? Like I said, my whole phone went black with the original one back in September (the screen was on though)
Click to expand...
Click to collapse
Yeah, there have been lots of improvements since September. Make a complete backup in recovery, flash the latest official Xposed framework and wipe cache/dalvik afterwards.
orville87 said:
Yeah, there have been lots of improvements since September. Make a complete backup in recovery, flash the latest official Xposed framework and wipe cache/dalvik afterwards.
Click to expand...
Click to collapse
I'll try it then, and post the result here.
Dear XDA-developers,
Today I spend numerous hours in trying to root my xperia z3 compact.
I currently have MM 6.0.1 D5803 installed on it with 23.5.A.0.575 the netherlands T-Mobile version. I have tried the following: Kingroot, iroot, kingoroot etc but it is all not working. I also used adroid sdk and changed the fastboot driver. I am able to fast boot etc.
Could anybody help me out with rooting this device? Love to hear from you guys.
Kay
It is described here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343/page149
Basically you must downgrade to kitkat, run the rooting script and install recovery, and then install a prerooted marshmallow rom.
Similar issue in Switzerland
M1chiel said:
It is described here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343/page149
Basically you must downgrade to kitkat, run the rooting script and install recovery, and then install a prerooted marshmallow rom.
Click to expand...
Click to collapse
Hi, I actually have the same problem rooting my new Z3C in Switzerland. I know that I have to downgrade but when I flash the rom it just boot in the welcome page and the it crashes and go in bootloop.
I've tried with both:
"D5803_23.0.1.A.5.77 Android 4.4.4_Customized CE1 1288-7915.ftf"
"D5803_23.4.A.0.546 Android 5.1.1_Customized CH 1288-9528.ftf" (I know that is not the KK but I just wanted to try if it works, but no success at all even flashing a lollipop from CH)
Any ideas guys?
jassi0709 said:
Hi, I actually have the same problem rooting my new Z3C in Switzerland. I know that I have to downgrade but when I flash the rom it just boot in the welcome page and the it crashes and go in bootloop.
I've tried with both:
"D5803_23.0.1.A.5.77 Android 4.4.4_Customized CE1 1288-7915.ftf"
"D5803_23.4.A.0.546 Android 5.1.1_Customized CH 1288-9528.ftf" (I know that is not the KK but I just wanted to try if it works, but no success at all even flashing a lollipop from CH)
Any ideas guys?
Click to expand...
Click to collapse
You need to follow this guide here
To answer your question you need build 23.0.A.2.93 or older, to be able to use griefroot
Didgesteve said:
You need to follow this guide here
To answer your question you need build 23.0.A.2.93 or older, to be able to use griefroot
Click to expand...
Click to collapse
Thank you for you answer. I've actually just tried with this but I get stuck in the welcome screen and then it simply continues to reboots.
I've installed this: D5803_23.0.A.2.93_Generic GLOBAL.ftf
After having a look to the firmware that I had on the phone (original and working was the 6.0.1 GLOBAL version).
All my previous phone was rooted and now I feel like in prison without a rooted xperia! ahahah
jassi0709 said:
Thank you for you answer. I've actually just tried with this but I get stuck in the welcome screen and then it simply continues to reboots.
I've installed this: D5803_23.0.A.2.93_Generic GLOBAL.ftf
After having a look to the firmware that I had on the phone (original and working was the 6.0.1 GLOBAL version).
All my previous phone was rooted and now I feel like in prison without a rooted xperia! ahahah
Click to expand...
Click to collapse
Then you are doing something wrong with flashtool, I used that build yesterday, then used geifroot and dual recovery, before flashing Slim 2.
you need to tick all of the wipe boxes, and none of the exlcude, or it won't work. You can't keep your data flashing to a different firmware.
Didgesteve said:
Then you are doing something wrong with flashtool, I used that build yesterday, then used geifroot and dual recovery, before flashing Slim 2.
you need to tick all of the wipe boxes, and none of the exlcude, or it won't work. You can't keep your data flashing to a different firmware.
Click to expand...
Click to collapse
Ohhh nice, it was not mentioned that you have to check all the tick boxes! Thank you so much!
It seems to work now.
I think it would be better to emphasize this in the guide: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
I'm downloading the rom, what would you suggest me if I do really care about the battery life? Maybe the lollipop instead of Marsh-mellow because of the presence of Stamina mode in lollipop?
I guess I will just try to find the best...
jassi0709 said:
Ohhh nice, it was not mentioned that you have to check all the tick boxes! Thank you so much!
It seems to work now.
I think it would be better to emphasize this in the guide: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
I'm downloading the rom, what would you suggest me if I do really care about the battery life? Maybe the lollipop instead of Marsh-mellow because of the presence of Stamina mode in lollipop?
I guess I will just try to find the best...
Click to expand...
Click to collapse
There are only two good builds for the Z3c at the moment.
The Slim 5 which is lollipop
or the Slim 2 MM. I was sceptical about MM battery life and held back 5.1 for a long time, but now the latest roms is out, the doze function works as well or better than stamina mode. I am getting 4 days between charges now, something I could never do before
Didgesteve said:
There are only two good builds for the Z3c at the moment.
The Slim 5 which is lollipop
or the Slim 2 MM. I was sceptical about MM battery life and held back 5.1 for a long time, but now the latest roms is out, the doze function works as well or better than stamina mode. I am getting 4 days between charges now, something I could never do before
Click to expand...
Click to collapse
Thank you for your answer. Really useful! I've finally managed to room and install that I wanted!
If you have such permission, I would suggest to edit the guide in: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
by adding the following:
7. Just select the name of the fw you downloaded and click on "Flash". Note: select both wipes in case you are coming from different android version.
43. Open Flashtool and select the non-pre-rooted fw (this is 23.1.A.0.690), but DESELECT system: in "EXCLUDE" make sure you check the checkbox next to "SYSTEM", flash it.
I will put this comment on the relative guide too!
I don't want to abuse of you kindness but I am currently searching for some CPU+GPU clock and voltage changer. Is there any efficient application that you can suggest me?
I had camera in use issue after updating cm13. I decided to wipe and try computerfreak stock cleaned ROM. Camera and everything works now but I have a persistent notification to revert my motorola sensor services firmware to previous version.
What's up with this?
Is it safe to proceed?
Daught said:
I had camera in use issue after updating cm13. I decided to wipe and try computerfreak stock cleaned ROM. Camera and everything works now but I have a persistent notification to revert my motorola sensor services firmware to previous version.
What's up with this?
Is it safe to proceed?
Click to expand...
Click to collapse
Your good to go there is a firmware change between marshmallow and lollipop. You go back to lollipop from a marshmallow ROM you will have too. It only takes a couple minutes then your phone will restart and you will be good to go.
Done it. No issues.
So the other day I took the plunge and decided to flash cm14 on my H811. Everything went perfectly well. Camera worked, flashlight worked, calling worked. Then I decided to flash Gapps as is customary and when I booted up again I had perfect access to the play store and the Gapps that I wanted, but now the camera doesn't work (just shows a black screen and then crashes), the microphone doesn't work (tried in several different applications), the calling doesn't work and neither does the speaker. I returned to stock marshmallow kdz using lgup and the same problems happened on the stock software.
Any suggestions? Perhaps I wiped some important files the phone needs when I did a wipe in TWRP?
BreakingRAD said:
So the other day I took the plunge and decided to flash cm14 on my H811. Everything went perfectly well. Camera worked, flashlight worked, calling worked. Then I decided to flash Gapps as is customary and when I booted up again I had perfect access to the play store and the Gapps that I wanted, but now the camera doesn't work (just shows a black screen and then crashes), the microphone doesn't work (tried in several different applications), the calling doesn't work and neither does the speaker. I returned to stock marshmallow kdz using lgup and the same problems happened on the stock software.
Any suggestions? Perhaps I wiped some important files the phone needs when I did a wipe in TWRP?
Click to expand...
Click to collapse
what version were you running when you installed CM14 and wich version did you use for KDZ.?
raptorddd said:
what version were you running when you installed CM14 and wich version did you use for KDZ.?
Click to expand...
Click to collapse
I was running 20i when I flashed cm and for KDZ I used was also 20i
BreakingRAD said:
I was running 20i when I flashed cm and for KDZ I used was also 20i
Click to expand...
Click to collapse
do this cleaning procedure. and even after clean. do a KDZ make sure refurbished optin is ticked.
https://forum.xda-developers.com/tmobile-g4/development/turbo-cleaning-proceure-h811-t3417606
I went ahead and updated from 20i to 20o using the organic built in method from the phone. It worked wonders and I'm glad to say my G4 is now running CM 14 flawlessly!
So about 3 weeks ago my 2 year old 3T just stopped working out of nowhere. I debated on whether to upgrade for over a week, but eventually decided to replace it with the same, just to have the familiar ROM, & not to have to learn anything new or mess with anything else, since I'm going through a lot of personal stuff right now. Anyway, I got the phone over a week ago and I've tried everything since then to get it running something beside OOS to no avail. Every single time it goes to sleep in another ROM, once I wake it up, touch is no longer responsive. I can't for the life of me figure out why. I have tried so many different things, in so many different ways. I know it might sound ridiculous but at this point I'm just in tears... I really need a functional phone, and I never would have bought another OP3T if I knew I'd be stuck with OOS....
The process I went through as soon as I got it:
Unfortunately I don't remember the version of OOS that it came with
- Unlock bootloader
- Flash TWRP (twrp-3.0.4-1 due to a thread I came across and was confused by)
- Wipe everything
- Flash recommended firmware for my ROM (posted in the ROM's thread)
- Flash my favorite ROM (Unofficial RR)
- Flash Magisk
- Boot, everything seems fine, screen goes off, turn it back on, unable to use touchscreen anymore.
I then used the unbrick tool, and tried again. Same problem. Used unbrick tool, unlocked bootloader, this time tried to flash this unofficial Lineage . Booted. It went to sleep. Woke up. Touchscreen nonfunctional.
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS. I go through the entire process again, this time flashing TWRP 3.2.1.0, it's the same thing. I've tried going up to open beta and then flashing my roms. I've tried flashing the rom without firmware, without magisk. With gapps. Without gapps. I always format and wipe everything. I also tried this on the off chance it might work.... I have seriously done the process every way imaginable, over twenty times since I got the phone last week.... nothing ever works. I also just tried Cyanogenmod, but it wouldn't flash at all.
I don't know what to do anymore. I just want to have a phone that I don't hate. At this point, I am too tired and I've got too much going on to figure this out on my own anymore. I would be grateful to pay someone at this point just to help me get this working honestly.... so if there's anyone out there who knows how to fix this, please let me know
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Mizart said:
It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess).
Click to expand...
Click to collapse
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
SpaceOctopus said:
I shut it down. Unbrick tool. This time I let it update itself all the way up to the very latest version of OOS.
Click to expand...
Click to collapse
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Mizart said:
Did you buy a new unit from somewhere or did you get a second hand unit ? In the latter case, the person who owned the device before you might have replaced the display for whatever reason, replaced displays often run into these kind of issues.
Also, does this happen on all the ROMs ? It seems you're only flashing Nougat roms, It could be that the hardware is not falling in line with the older software (just a guess). Try flashing a newer, latest updated pie rom and see how that works out.
Click to expand...
Click to collapse
Brand new from ebay. Sealed in the box.
I did try flashing a more recent version of resurrection remix, but it failed. Any recommendations?
redpoint73 said:
What does that even mean? Sounds like you are just making stuff up.
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
At any point, did you flash a full OOS zip (over 1 GB) and not just update patches? That is where I would start, to make sure it's one a completely stock baseline (including firmware, etc.).
You can get the latest full update zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Click to expand...
Click to collapse
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case. Thank you.
hhp_211 said:
@SpaceOctopus
I would try a newer firmware like the
Stable5.0.8 Firmware+Modem_OnePlus3T.zip
I would also recommend the latest TWRP = twrp-3.3.0-1-oneplus3.img
if still not working definitely flash the flash a full OOS zip from the post above which is 5.0.8
else you should try making the jump to a 9.0 PIE ROM, I see an official and unofficial RR if that is your goto ROM, easy to locate in the [INDEX] ROMs, Kernels & Misc. for 3/3T thread
.
Click to expand...
Click to collapse
I did try that TWRP eventually. No change. I would probably have switched to pie a while ago, except one small thing. There's an xposed module I'm really attached to, and as far as I'm aware, xposed isn't available on pie? Or at least that's what I've heard/read. It's the xprivacy lua module that lets you control every type of data an app has access to. I think I've tried looking for an alternative and there aren't any, either. :'( You know, sometimes it's just that one small thing... lol
However, I did try to install the most recent version of RR yesterday, and it failed flashing. Don't know why. I'm going to try again after flashing the firmware. Maybe it'll work this time.
Anyway, I'm also going to try what you all have recommended and see what happens. Hopefully something happens. Thank you much for your help
Ok, well, this time it let me install Resurrection Remix latest version. It may not be exactly what I wanted, but it's pretty goddamn close, and it sure as hell isn't OOS! lol
Thanks for your help everyone! I really appreciate it. I do still really wish I knew wtf was happening honestly with it not properly running nougat ROM's, but hey, this works for me. It won't make me want to toss it in a dumpster and set it on fire every time I pick it up. :laugh: :laugh: :laugh:
Maybe I can get someone to figure it out in the future or something, I don't know. I sure wish someone would convert that xprivacy module to work with Magisk though! I'm surprised nobody has even made an alternative or an app or anything like it really.
SpaceOctopus said:
I mean, does using the unbrick tool count? I think it completely flashes everything back to stock. Granted it's a very old version of OOS, but either way I will try that next just in case.
Click to expand...
Click to collapse
I think the unbrick tool does flash the full OOS. But honestly not 100% sure, as I have never actually had to use the unbrick tool (knock on wood!). Which is one reason I decided to pose that as a question.
In any case, if the unbrick did flash an old OOS, best to replace with newer version (or at least the firmware). Updated firmware typically plays better with the current custom ROMs. And old firmware is often a culprit when random bugs occur after flashing a custom ROM. So again, flashing firmware and/or the full update zip (which also flashes the firmware) is best practice in such cases. And if you are in any doubt about the OOS version or corresponding firmware that was installed, it probably doesn't hurt to flash again.