Hello everyone,
I'm experiencing a weird issue with a new F1: the camera flashlight icon is disabled and can't be activated.
Once out of the box, with stock ROM, it was initially working. Restoring the backup of my old F1 (LineageOS 16.0), I think that accidentally I should have restored/wiped something wrong.
After that I restored the stock ROM (beryllium_global_images_V12.0.3.0.QEJMIXM_20201227.0000.00_10.0_global) to fix it, but the flashlight works only if used in CIT mode, it doesn't in any another app.
Which could be the root cause? Wrong firmware?
Thanks in advance
SilverHawk.83 said:
Hello everyone,
I'm experiencing a weird issue with a new F1: the camera flashlight icon is disabled and can't be activated.
Once out of the box, with stock ROM, it was initially working. Restoring the backup of my old F1 (LineageOS 16.0), I think that accidentally I should have restored/wiped something wrong.
After that I restored the stock ROM (beryllium_global_images_V12.0.3.0.QEJMIXM_20201227.0000.00_10.0_global) to fix it, but the flashlight works only if used in CIT mode, it doesn't in any another app.
Which could be the root cause? Wrong firmware?
Thanks in advance
Click to expand...
Click to collapse
I would flash stock firmware and factory reset the device. Hopefully this will fix your issue.
Then you should be careful with flashing the custom rom you prefer ... maybe restoring the backup of your old devices is not the best idea.
It_ler said:
I would flash stock firmware and factory reset the device. Hopefully this will fix your issue.
Then you should be careful with flashing the custom rom you prefer ... maybe restoring the backup of your old devices is not the best idea.
Click to expand...
Click to collapse
I usually install LineageOS on every phone before to do everything else. We have three Poco F1, and I had no issue with the other two, only for this I think I did a mistake somewhere.
I already did a factory reset, restoring full stock ROM too. I suspect to have accidentally damaged another partition (i.e. persist).
Any other hint?
Related
I rooted my htc one and the camera stopped working. I didnt notice this until after i installed a custom kernel and when i unrooted, the kernel was still present and the camera still does not work. I also backed up my stuff on titanium backup because thats what everyone said to do if you were going to install kernals/roms. But when i saw the camera wasnt working, i tried reseting to factory and lost everything, including titanium backup.. so what im wondering is, is there any way to get back my stuff and is there any way to completely reset to factory settings as if it were day 1, including the kernel?
titanium backup application may have been lost , but the data might be present in your sd card
so if you install the app again you will find your data there .
to completely reset your phone as the way you got you will have to flash stock rom again then root it and restore apps by titanium
Sent from my GT-S5670 using xda premium
skiafolife said:
I rooted my htc one and the camera stopped working. I didnt notice this until after i installed a custom kernel and when i unrooted, the kernel was still present and the camera still does not work. I also backed up my stuff on titanium backup because thats what everyone said to do if you were going to install kernals/roms. But when i saw the camera wasnt working, i tried reseting to factory and lost everything, including titanium backup.. so what im wondering is, is there any way to get back my stuff and is there any way to completely reset to factory settings as if it were day 1, including the kernel?
Click to expand...
Click to collapse
you have to flash your firmware then it will be new as like 1st day.
Hello guys,
From the title, you might wonder what it has to do with the Z2 Tablet but I know for a fact it's the tablet and not the apps.
A few months back, I tried custom Roms; it all went fine until I tried CyanogenMod. The Rom itself was quite good but it messed up with the Recovery Partition, forcing the installation of the crappy Cyanogen Recovery (although the option to install it with updates was deactivated in the settings; I still don't understand how it got there). I had a hard time installing permanently another Recovery, it always got back to Cyanogen Recovery after a reboot.
A few issues also started to appear on non-Cyanogen ROMS : Adway wouldn't work. Titanium Backup sometimes couldn't find the backups. Youtube playback wouldn't work with the latest version. Gifs would never load on Relay for Reddit. It took me a while to realize that it was related to the ROM, until I actually tried Cyanogen again...where everything worked, sometimes using the same Titanium Backup for the apps !
I got fed up about this, so I decided to revert to full stock (latest 5.1) using the proper FTF.
And you know what ? Youtube Playback is not working, Gifs won't load in Relay. Can't speak for TiBu and Adaway as I didn't root but I'm sure they wouldn't work either. I'm also sure that other apps that I don't use have issues.
Do you have any idea what could be the source of these troubles ? Because if flashing a stock FTF still didn't fixed them, I think Cyanogen damaged my tablet more deeply than I thought...
Thanks !
Did you wipe data?
Not wiping data when going from cyanogen to stock causes problems very similar to yours. (only wiping cache isn't enough)
Sent from my SGP521 using XDA Premium HD app
I always wipe the datas when changing roms. And I did wipe the datas when I flashed the FTF as well...
OGYoutube won't work as well. If only I could identify the issue...
Ok, here's the solution : I forgot to relock my bootloader...
so.. that's so strange. how relocking the bootloader fixes the youtube problem? I've got the same problem with youtube, BUT only with original sony 5.0.. 5.1 firmware. with 4.4.2 or cyanogenmod doesn't happen.
I was using miui 8 the past month and wanted to try something new. So I flashed.a MM.Rom, CM13 from this forum. I did a system backup before. I am using twrp 3022.
After trying the Rom i decided to restore my miui backup, but when i try that I get an error saying:
extractTarFork() process ended with ERROR=255
I tried it several times but i always get this error after 85-87% of the restoring progress.
Is it because one rom is based on LP and one on MM? I never changed the twrp 3022.
I've read somewhere that it can be because of not having enough space but it's a system backup, so doesn't it mean, that it restores the whole system and data i had on that phone?
Please help
Edit
Restoring the cm backup works but the miui dies not work
Download and clean install Vova's AOSP rom first, let it boot, restart into recovery and try to restore your backup again. I've face this problem before, and this method works. Good luck mate ?
Jordan Jacob said:
Download and clean install Vova's AOSP rom first, let it boot, restart into recovery and try to restore your backup again. I've face this problem before, and this method works. Good luck mate
Click to expand...
Click to collapse
The Lollipop Rom?
Yups..
http://forum.xda-developers.com/redmi-note-2/development/cm-aicp-mokee-resurrection-bliss-t3383140
Jordan Jacob said:
Yups..
http://forum.xda-developers.com/redmi-note-2/development/cm-aicp-mokee-resurrection-bliss-t3383140
Click to expand...
Click to collapse
ok thanks i will try it
I still get the error 255 at 87%. I wiped the data and installed that aosp rom but it didn't help
gasperoni said:
I still get the error 255 at 87%. I wiped the data and installed that aosp rom but it didn't help
Click to expand...
Click to collapse
Did you wipe the data partition or did you format it? Try doing the latter ...
First i wiped cache+dalvik+data+system, everything but intern storage. I thought that must be enough. My last chance was wiping internal storage as well. I tried that and now it works. It really seems that it was a problem of space. I want to go back to a CM13 based Rom, when it's getting more stable.
Glad to hear your problem solved..
Jordan Jacob said:
Glad to hear your problem solved..
Click to expand...
Click to collapse
thanks bro, me too :good:
I've had this problem too - exact same error message, with the last two versions of TWRP.
I originally made a backup of my Nexus 7 2012 3G (Tilapia) with the modified KOT49H ROM installed, with TWRP (3.0.2.0, I think). I installed one of the Lollipop ROMs (I forget which) then restored that KOT49H based backup with no problem. Then I tried a different Lollipop ROM (Resurrection Remix, something) then tried to restore the same KOT49H based backup as before, and got this error.
I went from there to the Nougat ROM I'm currently using - an AOSP one by AndDiSa, and made a backup of that installation shortly after. After making some changes, I tried to restore that backup and got the same error (see OP).
I deleted as much stuff as I reasonably could, updated TWRP to 3.1.0.0 via fastboot and tried the restore again - same error. Also, my tablet then wouldn't boot, though that might be an unrelated problem. I took the battery out, which possibly I didn't need to, put it back, and noticed it was charging. It eventually booted, and seemed to have restored the backup, though I cant' be sure. Since it was the same ROM, it's possible all it restored was the data partition.
My main question is, if this is related to free storage, just how much is needed, to be able to restore a backup? I don't see wiping internal storage as much of a solution, on the Nexus 7, because there isn't a microSD slot, so that's the only place I can put the backup I'm trying to restore.
Hello. Can you please give me the twrp nvram backup or just the protect_f.img and protect_s. Thank you
Had same error, went back to old twrp ,all problems fixed
Steveromingagain said:
Had same error, went back to old twrp ,all problems fixed
Click to expand...
Click to collapse
what version TWRP to fixed problems ? i use TWRP version 3.0.2.2 always Error...
well after somehow breaking the miui stock cam when enabling the camera2apk, and being unable to fix it by replacing build.prop, i decided to restore the backup i made in twrp earlier.
restored backup: sticks at MI logo.
tried several times, cleared caches, wiped etc etc.. will not boot after restore.
so i downloaded the stock global rom, and flashed it in twrp: sticks at MI logo. will not boot
downloaded Ressurection Remix rom, flashed that.. works fine. but i want stock or as near as possible for now.
downloaded developer miui rom, flashed that in twrp: stuck at MI logo. will not boot.
tried stock stable rom again... same story, will not boot.
downloaded Miflash, and recommended TGZ archive of ROM. followed instructions and extracted to a folder and browsed to folder with Miflash. hit "refresh"
get error "length cannot be less than zero"
tried using the "mi recovery" method (renaming rom to "update.zip" and power/vol_up)
but for whatever reason, there is no "install update" option even present.
as you can see im having a very frustrating evening. i only wanted to enable the damn google camera.
flash it by edl mode
Sent from my [device_name] using XDA-Developers Legacy app
is there a decent guide for that anywhere? from what ive seen it still requires miflash to be working? which it, frankly, just isnt. but then, nothing is! dont think ive ever had an evening where so many things which are supposed to work all give problems together.
i mean, i could understand if the custom rom was problematic, but its the only thing that *did* work.
404 Not found
well i managed to get a stock rom installed by downloading an older version of miflash... that didnt give any errors and installed the global rom fine.
i would love to know what could be causing all my problems though. seems everthing ive tried should work.
the one that is bugging me more than anything now is that whenever i enable the camera2api, the miui stock camera stops working ( crash on hdr, panorarama mode) and stays broken even if i remove mod.
this should not happen it seems, since there are guides for enabling this and adding the pro features to the camera from higher models.
nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
robinlawrie said:
...nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
Click to expand...
Click to collapse
I dropped miui long ago, so it is difficult to comment. However, the problem would probably be found in the settings (and/or the drivers in the system). Reinstalling a stock system image and wiping /data (and formatting it, if necessary) should solve the problem. This is, of course, a drastic step - but I would be very surprised if the problem persisted after such a step.
you have to flash lazy flasher after every MIUI stock rom flashing to be able to boot the rom...
google it "lazy flasher'
long story short after full wipe, for the newest lineage os , ,gyroscope dosnt work anymore
ive tried with TWRP to go back to my last rom full backup (oldder lineage ver)
almost everything was there's (beside the gyroscope \screen rotation )
what can i do?
thanks
solve it (by flash stock ROM)
ok.. something weird.. after getback to any lineage still no gyro anymore
Superrman said:
ok.. something weird.. after getback to any lineage still no gyro anymore
Click to expand...
Click to collapse
Are you trying official or berni's?
Hi.
Have you found any solution? I am having quite the same problem.
All sensors (acceleration, compass, gyroscope, light, proximity) stopped working at my XZ5c.
Using Official LineageOS 14.1 latest version (14.1-20190207).
What I have tried:
Did an upgrade of LinOS, wiped dalvik and cache.
Even after a wipe of data all sensor are not working.
Tried something I found in the Xperia Z1 section
execute the following shell command (...):
kill $(pgrep sensors.qcom)
This kills the sensors.qcom process. ( It will restart automatically )
Click to expand...
Click to collapse
But it did not take any effect.
How do i know: Proximity sensor is not working when using telephone.app. Automatic screen brightness is not working. All other sensor readings only show up a "–" when reading out e.g. with SatStat.app.
Any ideas??
solve it (by flash stock ROM)
Click to expand...
Click to collapse
Did the same. Now sensors are working again.
Also see this Post.
Still: Someone knows how that happens? Would like to avoid all the flashing and restoring for the future if this is possible...
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
TheVan28 said:
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
Click to expand...
Click to collapse
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Son-Y said:
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Click to expand...
Click to collapse
My problem is that, even if i do a complete wipe, i still get the sensors issue
if i open an app like cpu-z they litterally don't exist, i get a blank page
I had the same problems and also persisting after a complete wipe.
My solution was:
Flashing Sony StockROM as descirbed in ( this post) .
This sorted my sensor issues. Check your sensors while in StockROM to make sure they are phyically OK
Then you can go back to whatever TWRP/CustomROM you like.
Hope that helps!
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Yep. I also cannot tell why it worked, could only tell you how...
Son-Y said:
Tried something I found in the Xperia Z1 section
But it did not take any effect.
Click to expand...
Click to collapse
I think pgrep no longer works on Nougat.
Code:
kill $(pidof sensors.qcom)
should work.
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
berbigou said:
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
Click to expand...
Click to collapse
Can you be more clear about the steps? how do you install stock kernel?