Camera not working in stock rom - Xiaomi Redmi Note 6 Pro Questions & Answers

Hi,
i wanted to install pixel. But i got bootlooped, so i went back to the Stock Firmware and Stock rom "miui_HMNote6ProGlobal_V10.3.3.0.PEKMIXM_2f80798173_9.0" when i dont recover my apps from google the camera is working, when i do recover my apps the cam is not working anymore.
So i wanted to install the google camera
But 2 problems occur: 1st i have to reflash the recovery to get into twrp each time i want to go into recovery
2nd When i m in recovery i have to "decrypt" the phone by wiping the data partion, which i dont want to, i just want to install the lets call it "googlecamera".zip
So is there a way to a) get twrp as standard recovery for volume up and powerbutton? mine is always the useless Xiaomi 3.0 recovery
b) have the data always encrypted
c) get the bloody camera working again
EDIT: Camera is working again, its been the launcher, deinstalled evie, reinstalled it all fine. But still got question 1 and 2

Related

I finally made it, Soft-Brick in another Way... -.-

Yeah, i finally made it. I bought a TMO-DE One S (With S4 Processor) 5 Days ago, unlocked the Bootloader (HBoot 1.09), rooted and SuperCID´d it, installed CWM Touch and installed TrickDriod V8.0 incl. its Tweak Package. After that i installed another Radio and everything was fine. It could have been SO easy, but i just HAD to do more, and now its soft-bricked.
At all TrickDroid is a really good ROM, but i hated the thingy that it shows G symbol instead of H when getting HSPA speeds. So i decided to dump it and go for a 4.0.4 / Sense 4.1 Stock Rom without branding instead until a JB / Sense Rom comes out. And thats were the trouble started. i flashed the stock rom with CWM, installed the boot.img that came shipped with it and booted it up. I did a full wipe before flashing. It booted up, Sense Stock Background Image came on and it showed "Unfortunately Wiper App is closed" at the "Preparing phone storage" stage. After OK´ing that another Screen came up about some system service wouldnt respond (dont know the exact Text anymore) wich i could close or wait for it. No matter what i do, or if i do nothing, after ~20 seconds the phone crashes and restarts. After the first restart the phone only boots into a black screen but with the Android bar at the top is working with time, battery-charging and a warning smybol. But the Phone wont react to anything i do except for lockscreen button. When its "online" i can push files via adb to the internal SDCard so i thought it wouldnt be a big problem. i pushed ONE MaximuS V2.5 ROM to the SD Card, booted into CWM and installed it. then flashed the boot.img of it via fastboot and booted it up. but nothing happens. still black screen with bar on top and not reacting phone that reboots every 20 seconds. i allready tried full wipe, cache wipe, dalvik cache wipe and i dont really know what to do now.
A broken SD Partion cant be since i can push files via ADB to it and install them with CWM. But whatever i try to install every ROM boots only in this blackscreen. its clearly not hanging in bootloader, but in android itself. I dont really know what to do, and returning to my dealer is no option since Rooting, SuperCID´ing and flashing another ROM. You maybe have a Idea what to do now?
Peace
TK
PS: Sorry for my bad english, hope you can understand it
Edit: Okey, i got something. i formatted everything i could in CWM, and now (as its now supposed) it hangs in bootloader since no system is there for booting. The good thing is in CWM i get ADB Connection so i can still push files to the SDCard. Im now trying installing a ROM again. So at least i have a starting Point if it fails again
Edit 2: Okey, found it. The "Stock" ROM is broken, not my Phones Fault. and MaximuS just doesnt install right so nothing was changed. Installed TrickDroid again for testing and everything is fine again. Close this one...

[Q] Help with samsung galaxy s3!!!!!!!! metro pcs.

Please Help!!!!! I have a rooted Samsung Galaxy S3 that I have a problem with. I was going through my phone trying to get java to work on the phone and I noticed you had to copy a file into the lib folder, so when I tried to start all over to see if I had done something wrong I deleted the lib folder and right when I did that the phone kept saying touchwiz has stopped working, so i turned it off and turned it on and then it wouldnt get passed the white samsung logo and then went straight to Android update recovory and if i put reboot now it just keeps taking back to the recovery state, I also did wipe data and factory reset but that didnt work either. I have tried to flash a custom firmware that i flashed on it to get it rooted but the problem stays the same is there anyway i can fix this and get my phone back?
thehusk said:
Please Help!!!!! I have a rooted Samsung Galaxy S3 that I have a problem with. I was going through my phone trying to get java to work on the phone and I noticed you had to copy a file into the lib folder, so when I tried to start all over to see if I had done something wrong I deleted the lib folder and right when I did that the phone kept saying touchwiz has stopped working, so i turned it off and turned it on and then it wouldnt get passed the white samsung logo and then went straight to Android update recovory and if i put reboot now it just keeps taking back to the recovery state, I also did wipe data and factory reset but that didnt work either. I have tried to flash a custom firmware that i flashed on it to get it rooted but the problem stays the same is there anyway i can fix this and get my phone back?
Click to expand...
Click to collapse
Which recovery are you running (stock, CWM,TWRP,Philz etc) ?
As I see it, you've got 2 options:
1- Flash back to stock rom using Odin (see S3 thread FAQ)
2- Download other custom rom (I suggest the one i'm using), copy it into your device (you can mount your device SD in recovery mode),
perform wipe data + cache wipe + delvik wipe, and flash the rom.

[Q] How do I restore Soft bricked SCH1535 from CM unofficial 4.4.2

I rooted my SCH 1535 and installed CM Version 11-20140215-UNOFFICIAL-d2vzw. Android 4.4.2 (Baseband: l535VRBLMD3) (Kernel:3.4.80-cm
It was working OK except in order to see my WiFi I had to reboot every time WiFi was turned off.
Plus I was having trouble updating ROMs with ROM Manager.
I had both TWRP & CM installed, although the phone defaulted to TWRP in recovery.
I downloaded seveeral CM ROMs via the CM updater in Settings > About Phone & wasn't able to flash.
So, I (stupidly) WIPED with TWRP
Now, I still have the CM KitKat ROM on my phone but when I try Play Store it starts & immediately closes.
Android Keyboard stops as soon as I boot up, so i can't log even into my Google account.
I'm pretty sure I'm no longer rooted & there's no recovery - in fact the Return, Menu & Volume buttons don't seem to work.
Most of my apps are gone except for Google & Samsung, but I can't log in.
I did do a nandroid backup & have Internal & Card backups on my PC as well as Odin.
So, my question is Should I try to restore to stock and start over? (What's the best way to do that from my build?)
or do I go for a KItKat ROM? (any suggestions?)
I want to make sure I have the proper recovery, bootloader (SuperSU_Bootloader_FIXED.zip ?)
I am wide open to suggestions on the best way to proceed. I'm really hesitant to try the Factory Data Reset - since I've heard that can brick a phone completely.
Thanks!

MOTO G custom ROM weird bug/problem

Hello, so after I install a custom ROM, after 2-3 weeks of using it, my phone gets stuck, and then reboots. After the reboot, the phone acts weird: no notifications are shown, home/recents buttons not working, some apps not working and not locking and some options just reset.
Thank you in advance.
yakomi said:
Hello, so after I install a custom ROM, after 2-3 weeks of using it, my phone gets stuck, and then reboots. After the reboot, the phone acts weird: no notifications are shown, home/recents buttons not working, some apps not working and not locking and some options just reset.
Thank you in advance.
Click to expand...
Click to collapse
?? Yep i know this thing few symptoms were shown on my osprey so it happened to me bz i just to test many custom rom and many time there residue remain uncleaned even after many twrp formats (it weird but i think this happens) so try clearing your intenal storageand (no need to clean memory just remove it) even remove you sim crad and memory cards
flash a recovery from your current recovery if there is not update just reflash the current recovery and then just make it a reboot to recovery ( msg will pop up no os found but there will be no issue if you're rebooting directly to the recovery)
So after reboot put your memory card in phone where you will store your rom and gapps ( if memory not detected just reboot to recovery one more time) puff install things let your sim cards in enjoy your rom
If this thing failes go install stock firmware its an ultimate solution
i finally flashed the stock os, hopefully no issues now!
yakomi said:
Hello, so after I install a custom ROM, after 2-3 weeks of using it, my phone gets stuck, and then reboots. After the reboot, the phone acts weird: no notifications are shown, home/recents buttons not working, some apps not working and not locking and some options just reset.
Thank you in advance.
Click to expand...
Click to collapse
The same issue happened to me yesterday
So, now I am trying to clean flash the custom rom first
I've been running a Lineage OS PIE version on my Moto G3 2015(Osprey) XT 1541 for several months now and not a single problem.I think it's a Fantastic Custom rom that you might like to try,
http://www.droidthunder.com/android-9-0-pie-on-moto-g3/
Note:
Before installing any Custom rom do a,"Nandroid" backup and then a Factory Reset.
Then once the rom has installed and before setting the phone up do another,"Factory Reset".
I've found this the best way to make sure the install is really good and clean

How to flash persist.img in this phone?

Good evening guys.
For a couple of days the phone has been in bootloop and I have problems with the persist partition. It all started at the beginning of the year. For no apparent reason, the main camera stopped working (error: unable to connect to camera). The curious thing is that in the smartphone test menu, all the cameras are functional, except for the main one. The tests I did were:
Format the phone from the settings.
Reinstall the rom via fastboot.
Install other roms.
In the case of formatting and reinstalling, the camera app only worked if I held down the icon and chose to take a selfie. Using other roms, however, the pre-installed camera (camera go, for example), did not start. If instead I installed one of the various gcams for surya, these worked. But if I tried to load the config files briefly into the gcam, it also crashed and wouldn't open anymore.
In the end, I opted to keep the stock rom (rooted) and use a gcam with no setup. These days, the phone hasn't been used except to play online (only on wifi) and hasn't given any problems. Yesterday however, while I was playing, the gyroscope started moving by itself and/or getting stuck and not working.
At that point, I decided to do yet another fastboot flash. This time though, the phone didn't boot anymore, remaining in bootloop. I also tried to change version (from global to european), to flash again other roms (pixel os, miui.eu, pixel expiriece), but nothing to do. The only thing I noticed is that the recovery warns me that I can't mount /persist. I also tried recovering the persist.img from the original rom (I don't have a backup) and flashing from twrp. It seems to work fine, but then actually the same error comes back. I also tried from the terminal, always via twrp, but even there it says it has copied the data, but the error returns.
Could you help me?
Thank you.

Categories

Resources