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'
Related
Hello,
I have been googling and reading all threads about this issue for over a month now, so it's problably something quite special. Every time I try to use an app using a camera or flashlight, it reports with "Can't connect to camera" message. This first happened while trying to flash a Kitkat rom (Artas's CM11) with wrong recovery. So it was not working, I got back to system, flashed the correct recovery via flashify, got back to it and finally flashed the rom. Ever since that the camera has not been working, with one exception - now this is the interesting thing that makes me think it's not a hw problem - while trying to do all kinds of unbricks and resets I know of (flashing all kinds of different roms, CM based, AOSP, of course all kinds of original roms) I decided to go for KDZ - so I got the original bin I found on this forum and got back to v10i and the camera worked! So I was happy that it's solved and decided to stick with stock rom. It updated to JB (the official way) and ever since, it has not been working. I have tried to flash persist images, to mess with permisions and I can't really think of any other way. (Of course I have tried to flash KDZ again the same way, but it did not work, not even on ICS).
Thanks for every idea!
Hello friends,
In a moment of a severe mental handicap, I appear to have flashed a Mi4(cancro) ROM in EDL mode when I was trying to unlock my bootloader.
(The reason was that the guide I was using had a broken download link, so I searched for the filename and downloaded from one of the mirrors I found. I did not realize I was now downloading a file with a different device prefix (cancro instead of kenzo.).
So after the unavoidable brick, I was able to recover by flashing a proper Kenzo MIUI rom with disabled device checks (Since the phone now thought it was a Mi4, I guess).
MIUI is booting, but most of the functions are broken:
- No camera
- No SIM/Service
- Can't adjust brightness
- No rotation
Maybe there's more stuff broken, but I did not check every corner.
I moved on to try CM13, but that won't boot up at all (just sits there at the boot animation).
So far everything I've tried to get the phone back into a working state has failed, but I'm still getting used to this phone's specifics, so I may have missed something.
Please tell me there is something I can do.
if you can get to the recovery then WIPE everything out (system, cache,etc) then install the stock MIUI for your note3, if it booted up then you can move on to any other Rom...
Abd121 said:
if you can get to the recovery then WIPE everything out (system, cache,etc) then install the stock MIUI for your note3, if it booted up then you can move on to any other Rom...
Click to expand...
Click to collapse
Thank you. I can indeed get to recovery, but I always end up without sim card and camera when I flash an official rom.
I just tried to go back to the shop rom from geekbuying, that at least made brightness and rotation work, but still no signal/camera. I feel there's some firmware missing or was overwritten by my stupid action and now there does not seem to be a simple way to get it back up.
EDIT: So I just found out that my IMEI is gone. I will try to use a guide to re-set it. Hopefully, that will get mobile service running again. Dunno about camera, though
The last weeks I had my fair share of geek awesomeness with my shiny brand new POCO F1 and, in my own right, installed many (a dozen) custom-roms and another bunch of vendor and firmware versions, all of them specifically for the Poco F1.
I was using Havoc OS 2.5 and did an OTA update to version 2.6. Everything normal, ok, but I decided to get back to MIUI because two camera related APPs didn't work well with any of the custom roms I've installed and "ok, I'll get back to MIUI, is not bad afterall and the screenrecorder is WAY better than any of the others I tried".
Recovery, wipe, format, flashed MIUI 10.3.4 no problems or error messages like always, reboot, recovery, magisk, reboot, let the system do its stuff, Miui account, google account, the whole thing is ok, play store recovering my cloud backup, ok. Everything works really ok until the first reboot. After the reboot the "Find my device" halts repeteadly, running the system inoperable. "Find my device has crashed and bla bla bla" forever. As long as i use the system first boot, is ok, but eventually, I need to reboot and after that, "find my device has crashed". I've got back to Havoc OS 2.6 and is, like always, running like a charm.
I've tried to get back to MIUI 10.2.2 (whice came pre-installed) to try an OTA update to 10.3.4, but in 10.2.2 also the find my device crashes every time.
What kind of sorcery is happening here? Any thoughts?
Flash fastboot room
Flash fastboot rom
always flash miui with mi flasher
[SOLVED]
alfarhaannizam said:
Flash fastboot rom
Click to expand...
Click to collapse
Worked like a charm. Downloaded MIUI 10.2.3 fastboot rom and flashed using Xiaomi Adb/Fastboot Tools. And then updated to MIUI 10.3.4 via system updater.
Thanks for the heads up. It was really helpful.
mendax99 said:
always flash miui with mi flasher
Click to expand...
Click to collapse
Mi Flasher don't work allright in my computer, since I only have USB 3.0 on my windows device and it seems MI Flasher doesn't work with USB 3.0
I'm using, usually command line abd and fastboot on windows. Today I've downloaded Xiaomi ADb/Fastboot Tolls and it was very useful.
I can't post links yet since I'm new on the forum. But search for Xiaomi ADB/Fastboot Tools GitHub. it is powerful.
otaodofino said:
The last weeks I had my fair share of geek awesomeness with my shiny brand new POCO F1 and, in my own right, installed many (a dozen) custom-roms and another bunch of vendor and firmware versions, all of them specifically for the Poco F1.
I was using Havoc OS 2.5 and did an OTA update to version 2.6. Everything normal, ok, but I decided to get back to MIUI because two camera related APPs didn't work well with any of the custom roms I've installed and "ok, I'll get back to MIUI, is not bad afterall and the screenrecorder is WAY better than any of the others I tried".
Recovery, wipe, format, flashed MIUI 10.3.4 no problems or error messages like always, reboot, recovery, magisk, reboot, let the system do its stuff, Miui account, google account, the whole thing is ok, play store recovering my cloud backup, ok. Everything works really ok until the first reboot. After the reboot the "Find my device" halts repeteadly, running the system inoperable. "Find my device has crashed and bla bla bla" forever. As long as i use the system first boot, is ok, but eventually, I need to reboot and after that, "find my device has crashed". I've got back to Havoc OS 2.6 and is, like always, running like a charm.
I've tried to get back to MIUI 10.2.2 (whice came pre-installed) to try an OTA update to 10.3.4, but in 10.2.2 also the find my device crashes every time.
What kind of sorcery is happening here? Any thoughts?
Click to expand...
Click to collapse
Why just not just freeze the app/ service ? That's what I did.
MasterFURQAN said:
Why just not just freeze the app/ service ? That's what I did.
Click to expand...
Click to collapse
Because the service was broken. Yes, maybe I could adb and freeze the service, but the service would still be broken, probably due to many different firmware/vendor versions installed on the last couple weeks.
The fastboot rom is more comprehensive in terms of background images (cust/dsp/persist) and flashing it totally nailed the error.
otaodofino said:
Because the service was broken. Yes, maybe I could adb and freeze the service, but the service would still be broken, probably due to many different firmware/vendor versions installed on the last couple weeks.
The fastboot rom is more comprehensive in terms of background images (cust/dsp/persist) and flashing it totally nailed the error.
Click to expand...
Click to collapse
Yeah. I know that flashing a fastboot ROM is the best way to repair corrupt partitions but it also resets the phone and I'm too lazy to restore everything back. Lol.
Hi,
last week I bought myself a Huawei P20 Lite as this one seems to be good comprise between size, speed and price and all together I find this device quite nice.
However I'm not a big fan of this ROMs, it's bloated and you have to confirm on each and everyhting, so I tried to reduce this dramatically and I began a long journey....
Unlock the bootloader
When I bought the device I wasn't aware about the issues that I may face (Downgrad, additional 4 Euro to spend) but OK, I thought it would be worth....
Installing Recovery
..but I couldn't be more wrong. It seems that there's no working TWRP for this device out there. I tried a lot, both on 8.0 and 9.1 but each time I tried to
wipe cache/dalvik the whole system got stucked and wasn't able to show the boot animation. So, assuming that there's really no working recovery out there, I continued to
directly flash different ROMs and try out my luck.
Rooting
This wasn't as hard as I though first, at least, as long as the ROM I've used had an advanced Reboot-Menu with the possibilty to boot to recovery, otherwise you end up somewhere in the desert and
may not be able to restart with boot.
The problem is, that this device required to patch the RECOVERY_RAMDISK partition, so in order to have Magisk booted, you required to use the Recovery. No big deal: just Power up
using VolUp and Power until the Huawei logo appears... normally.. It didnt work in more than 50% of the times...
Gapps (or Magisk)
OK, as I already indicated, I tried lots of them, but to be honest, none of them really convinced me (all was done on EMUI9.1 "AB" and not EMUI8 "A only")
GSI Phh Treble: nice, but this is one of thinks I did not checked in depth, as almost all (?) are based on this one...
OmniRom from OpenKirin: works perfectly out of the box, SafeteNet is working, Magisk can be installed, but no advanced boot menu and I find it a little bit overloaded...
MicroG ufOffical: I would go with it, everyhting worked, it's slim BUT I couldn't get my Banking-App working, not even after appliying multiple MagiskHide Prop-Settings...
Descendant: This one was by far my favorite... Really slim, advanced reboot-menu, but I couldn't flash Gapps. OK, so I tried MicroG: this can be installed using Magisk. After some trouble (e.g. you have to install DroidGuardHelper so that the OS recognizes an "Update") I got MicroG working, but I coulnd't get it with my Banking-App. In this ROM I couldn't even apply any MagiskProp Hide-Settings. Only Post-FS worked. OK, as I'Ve failed using this approach, I thought: maybe I can use Gapps with this image.... but as I stated at the beginning: I do not have any working Recovery.
So my questions:
Is there any working Recovery out there? TWRP 3.3.x supports to be flashed in RECOVERY_RAMDISK (and there's also offical support for P20 Pro) As of now I wouldn't even care about decrypted data, but at least be able to wipe and do a factory reset....
Or: Is it possible to install Gapps from a running (rooted) system?
Or: can I patch system.img with Gapps before flashing it to the phone?
But perfectly: did anyone get Descendant running with MagiskHideProp? Maybe even got MicroG running on it?
I'm currently out of ideas, did someone else had such a trouble with that device?
Best regards,
Peter
Well, yes. Kinda the same as you but I didn't try that many roms. I tried a fair bunch of twrp versions though. And I managed to use twrp to flash roms and if I remember well even do a dalvik/cache wipe with one of them - but I might be imagining that one. It is worth noting that you can actually use some twrp versions for other huawei devices on the p20 lite. Try at your own risk. There is a lot more development going on for the p8 lite (2017) for example. I tried the lineageos version that was posted herefor that device and it worked quite well.
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
iJaviXR said:
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
Click to expand...
Click to collapse
Check my POCO F1 Ultimate Collection & Guides. Try to Clean Install Pixel Experience for example, according my guide (u need to format data also). Let me know how it goes.
Tried Android 10 and 11 Pixel Experience, tried with stock and NG Kernels. Still stays forever in the first load of the SO.
Just got the properties file from XiaomiADBFastbootTools. Maybe someone can see something wrong on it.