Hi people:
I bought a Xperia X Compact 2 weeks ago. It seems to be a "journalist and commercial" terminal, as it came with version 6.0.1 of Android and did not allow updates via OTA.
I've used FlashTool to put another version of Firmware, the 7.1.1, and everything looks perfect, until I'm going to make a photo.
In the screen is observed to make the photo and I see the "picture" to take, but the touch button of the screen is not working. From that moment, the mobile starts to spend a lot of battery and the photo is not done. If you force the camera to front, a photo comes out completely in green.
I've put ROM 6.0.1 (Journalist and Commercial) back in, but the camera no longer works.
I have not done root.
EDITED:
Sorry. I lost DRM and the problem solved when I install patched Kernel. Problem is solved and I have 7.1.1 "with" DRM.
Thank you for your help
I have the same problem now , anyone know how to repair it
I might be having exactly the same problem. How did you get (and install) the patched kernel?
Thanks.
Related
During an update, (PASSIMG.zip) in hboot I selected yes (to install) then about a second later, my screen
turned black and now, the only thing I can do is to boot in the installed stock rom (FRG33).
My english is not perfect, i'm sorry for that.
1. I Removed my battery after a while. (about 10 minutes)
2. Inserted the battery back in his place
3. Power down + vol down and I'm stock, I can navigate in
the menu but I can't see anything...
Anyone know how I can get my screen back ? OLED vs SLCD ?
Note: I can boot in my rom, the rom is unrooted, my phone is unlocked.
(And yes, I tried to flash recovery and another rom without success. And I can't
find a way to flash hboot again (bad signature)
I'm using the last version of hboot and radio.
If anyone have an idea of how I can fix this, this will be really appreciated.
Thanks.
I'm starting to think than my /dev/mtd/mtd0 is screwed up.
Anyone know where I can get/or generate a image of a normal mtd0 ?
At the moment I'm running debian sid dand SuperOneClick seem to freeze
after trying to chmod rageagainstthecage or psneu..
Note: Yes my screen work when the boot is completed. (but not in hboot/recovery)
bad spl ?
fblodroid
Ok, sorry for the noise, I was able to perform an update via 766a101ae02c.signed-passion-ota-60505.766a101a.zip (renamed to update.zip) and I powered off my phone.
Removed the battery to be sure there is no power at all.
and using some screenshot found on the web.
I was able to perform the update (blindly, this word exist ?) and the phone rebooted
and asked me if I want to update again (google update) I selected yes, the phone rebooted
and, VOILA, I can see again the crappy X logo with an open lock at the bottom.
Thanks again (ok for nothing, but if than can help some people...)
Yes, shame on my english again.
fblodroid
My guess is that you have an SLCD Nexus One, and the passimg installed the .33 HBOOT which doesn't work for them.
I had the same problem when flashing the MIUI-AU rom, screen went black,removed battery and replaced but the phone was dead,I was already thinking which phone to buy then when I connected the N1 to my laptop miraculously the X logo appeared and the rom launched ok
At the moment my phone is working again but I'm still having a camera issue.
About a 1 1/2 month ago I experienced this problem, no flash, no camera, just
a black screen when I try to run anything than use the camera.
Then a day, I was walking on the street and I checked to see if the flashlight was
working and obscured magic occured, the flash was working again but not the camera,
I wiped my phone again, repartitionned my SD card and installed a new rom and the
camera was back to normal.
Now, about a month later, (the problem started yesterday) i'm having the same issue.
I'm persuaded than this problem is related to a firmware problem, something related to
my /dev/mtd/mtd0 (hboot, perpaps ?) I don't know exactly where the camera firmware
is writed in the phone memory (nand)
I wiped and flashed again and again a lot of rom last night and today and the problem
still exist.
No camera/flash at all.
I'm thinking about returning the phone for warranty issue but like I said before, the
phone is unlocked... perpaps I will try to black the screen again and send the phone for
warranty... this way they cannot see (without fastboot) if the phone is locked or not.
If anyone have an idea of what I can do... a rom to recommend ?
Today I tryed to revert hboot without success...
EDIT: At the moment I'm running a rooted rom based on FRG83G.
fblodroid...
Related to my camera/flash problem:
Hum, I think I found the problem, this is hardware related, something seem to be
badly connected in the phone, I tryed too apply some force on the right border of the
phone with the flashlight ON (I previously looked on the web to see where the "contacts/plugs"
are located on the pcb (teardown pictures) and after applying some pressure, the light came ON
and now I can open and stop the "flashlight" mode.
teardown on the way ? I'm thinking about it... but i'll try to flash another rom again to see
if my camera is back.. (like in the past)
EDIT: No camera for the moment and the flashlight app light on the LED only if I select
the option "High Brightnes", ON/OFF are working with this option selected.
fblodroid
FIXED
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
http://img121.imageshack.us/i/icedqlubgg4zzbv2huge.jpg/ (in the red circles, the two pink dots)
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Hi, I have a HTC Desire GSM PVT4 (HTC__203), with the exact same issue as what is described in the original post. When I boot in hboot or recovery the screen is completely black. When I boot in the normal rom the screen works fine. I reflashed a number of RUU's successfully, but the problem remains.
The misc partition is not part of the RUU images, and I did re-flash the misc partition in an attempt to downgrade. Any idea where I can get an image for the misc partition for my device, or where I can generate one?
Thanks,
Hans
fblodroid said:
After a complete teardown of my phone, and a lots of cigarettes..
I found two cables not correctly connected to her pin.
I made a picture, hum, an ugly picture of which cables.
/link/
And yep, now my camera/flash are working perfectly.
NOTE: the phone is not easily to dismantle, this is at your risk and peril. (time: about ~25 min)
Thanks again and please, ignore my english. I'm thinking about starting a thread
related to this problem. Should I ?
fblodroid
Click to expand...
Click to collapse
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
soylapinta said:
Hey. I have the same issue you had with the camera, black screen and forced to close when running it. My flashlight works perfectly thoug.
I tried wiping and reflashing diferent ROMs, stock and Cyanogen with no luck. I also followed your lead and disassembled the phone to check all the connectors but the problem persists.
Any idea for me to try? Thanks for your posts anyway.
Click to expand...
Click to collapse
Did you managed to fix it ? Be sure to check all the plugs, at best unplug everythings
and disassemble the phone entirely.
Mine is still working perfectly after two years.
fb
Hi everyone.
I have encountered a problem on my phone's rear camera with the latest ROM upgrade, which upgraded my android version fom 4.2.2 to 4.3:
I9505XXUEMJ7_I9505BTUEMJ8_BTU
The problem is that I get a dark display (black screen, see the attached screenshot) and the whole phone gets stucked and its performance is slowed down due to that. After about a minute or to of freezing phone I Finally get a warning - Camera Failed.
I tried to wipe twice (both cache partition and user data), prior to and after flashing, and also tried to reflash the same rom again. Didn't work out for me, or at least works once right after wiping and then fails again. Seems like a heavy bug in 4.3, unstables the camera due to the new firmware.
Has anyone had that same problem or reported on it or it's just me? What should I do now?
Thanks.
When you open the camera, did you get a camera firmware update?
Crauze said:
When you open the camera, did you get a camera firmware update?
Click to expand...
Click to collapse
Yes, that was in the first time that opened the built-in camera app after flashing the newest firmware. I proceeded with the update and then all that mess started. But since then I have reflashed and didn't get that message once more to confirm/approve.
Is there a way to downgrade the camera's firmware to the one used in 4.2.2? It really worked really well for me prior to that so called "upgrade"...
Another question: When (roughly) should I9505 models recieve the 4.3.1 update? Is it scheduled to be soon?
Having the same issue (also with other Camera apps like Barcode Scanner, Paper Camera & Optical Reader). If I wait I end up with a "camera fail" message.
UPDATE: Just upgraded to MK8 version using Kies - and the problem persists!
This month's (november) update implies that Samsung are yet to resolve this bug. Does someone know how should I report them about the problem? Is there a website or a social network page that they actually check up on a regular basis?
Thank you.
So, it just popped up while my phone was idle, without anyone calling it in here first, YotaPhone finally decided to give us EU users the RU124 firmware! It looks from the changelog to be the exact EU equivalent to its RU counterpart, including YotaTravel, the return of the YotaStore and other stuff. It's been so long that I don't even remember, but I should be fine flashing this and then reflashing SuperSU and Xposed without losing anything, correct?
If you have stock recovery it will install fine. If not you should be able to grab the update zip from /cache and side load. Then reflash what you want.
Sent from my iPhone using Tapatalk
Yep I'm still on the stock recovery (I just boot TWRP every time I need it). Gotcha, then I'm just dumping my Titanium Backup folder onto my PC as a precaution, and then I'll update and report back on SU\Xposed.
Looks like whatever Yota pushed at 117MB was the wrong thing - a failed update attempt and a reboot later, it's now 0.94 GB. Seems like it's the correct size in ftp://fw.ydevices.com/YotaPhone2/Firmwares/EU/ so now it should work.
Update from RU1.1.112 to RU1.1.124 issue
https://r.tapatalk.com/shareLink?ur...share_tid=3436224&share_fid=3793&share_type=t
Sent from my iPhone using Tapatalk
Just as expected the 0.94 GB update file worked, I reflashed SuperSU and Xposed and the phone is working great on 1.124b.
What version were you coming from?
Sent from my iPhone using Tapatalk
EU1.87. I wanted to go to the RU version but never could get a KitKat RU firmware to boot on my device, so I just gave up and went back to the latest EU firmware.
Ah OK that makes sense. Glad you got it working.
Sent from my iPhone using Tapatalk
Go mine today (1.1.44HK)
Updated to EU 1.1.124b with official yotaflasher.
No Su nor any hack.
So far no bug, it's a great device.
Hi there!
I'm waiting for my yotaphone 2 from this new wave from chinese shops. I ordered the International version. Is it safe to flash the EU version firmware over the "international" version?
And please, can anyone provide an alternative downolad link for the yota flasher?
The one from offcial website:
https://yotaphone.com/us-en/ypflasher/
is a corrupted zip file.
Thanks!
Edit:
I could get it from here:
ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/
Seems there's a bug.
Almost each time i try to unlock phone (with power button) from EDP the pin keyboard isn't showing up, i must tap all over the EDP screen, way it's relocking then i can have the keyboard again.
Solved by using gesture instead of pincode
satsuki_yatoshi said:
Solved by using gesture instead of pincode
Click to expand...
Click to collapse
Gutted they removed the Instagram Cover instead of fixing it!
Rarelyamson said:
Gutted they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
they removed the Instagram Cover instead of fixing it!
Click to expand...
Click to collapse
Instagram restricted access to its API, so none of 3rd party apps now work properly. Thats why Instagram Cover was removed.
Hello
I deployed this great update a few days ago, and it clearly brings numerous improvements and fixes.
One visibly new bug annoys me a lot anyway, and that's why I am posting :
When I type a SMS on the EPD, lots of freezes occur. And today, I found a simple pattern. I type a word, and then I back-delete one or a few letters of it. Then I add new letters, and that frequently freezes the EPD for a long moment.
It's not 100%, lots of times it freezes under these conditions, few other times it does not.
I setup 3 languages to choose from (thanks to the update !) and the auto correction is ON.
Does someone else experience the same issue ? Any workaround or fix ?
Thanks
Appens to me 2 times, each time i needed to look/unlook the edp screen to solve
My problem is that with the latest update I need to restart my phone until it starts charging. Otherwise it will not charge ... does this happen to anybody else? Probably I should try to reset ...
no charge bug here
No charge bug here neither. Quite the opposite in fact, I would even say that autonomy obviously improved since this update.
And I confirm I have the same bug with the PIN keyboard not showing up on the EPD when using the Powa button. It happens very often after using the other screen, but unlocking by tapping twice is an easy and efficient workaround.
Surprising obvious bugs anyway, I hope the Yotagods watch us and intend to fix them.
I just bought a XT1687 and rooted it. Somehow I lost my camera and flashlight. No matter what camera app or apk I download, nothing picks the camera up. I have wiped and factory reset but still no camera. I'm on november patch 137-94. And yes, I'm definitely a rookie. I just watch YouTube videos... Can anyone lend me a hand please.
A Fix
I doubt any one cares, but for those of you here in 2018 that still have this broken camera issue after using that Moto G5 Toolkit and wiping out your camera, here is what I did, after 3 days of this trial and error crap.
1. Even though one of the experts suggested it isn't wise, installed RSD Lite from a YouTube video (Yes, I guess RSD Lite is dead and gone but it worked).
2. I then took a shot and downloaded a update that was sliiiiiightly different then what my phone was running. (POTTER_NPN25.137-92_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml). I got it from a google search for my stock. I have a XT1687 and that patch goes to a XT1686 but at this point I had nothing to lose.
3. I used RSD Lite to install the zip and BINGO. I have my camera back and everything else seems to work.
I would go more in detail but I think I'm talking to myself LOL. Anybody needs help with it I will try to help. I'm definitely a novice but I have put this one to bed
Looks like the stock camera software is screwed.. you'll have to manually flash a new OTA when it comes out (dangerous, you can brick your device) or just flash a new ROM.. unless it's hardware but as you described i don't think so
Hello, My phone's (main)camera is not being registered by the stock camera app , neither by Gcam. But it shows up in apps like instagram and snapchat and works just fine, no crashes or such. I tried resetting my phone through settings and the ****ty bootloader you get with a locked H870DS (un rootable) model and it didn't seem to work.
What I am thinking is, there's something wrong with the camera ID allocations of the camera but still confused as to why even after resetting, it won't work. Any way that I can erase the system and other partitions and do a fresh stock os installation? UGH it was so easy with root. Lg made a great device ****ty by locking it down for me.
Update: So I forgot to add how I came to the conclusion of camera ID being allocated wrongly. When I try to open the stock camera app by long pressing and selecting 'Selfie cam' , it opens up the wide angle rear camera. Either the front cam is done for or my device is.
So everyone's in quarintine but no one wants to help?
Hey,
today i tried to recreate your problem, and i got your problem.
Problem came when i flashed Pixel Experience Android 10 ROM against branded stock Android 9 (branded by Polish Play).
How to solve it? After many trial and errors, problem dissapeared when i flashed stock Android 8 (branded by Polish Play in my case), and did FOTA update.
I hope i helped.