Related
Hi,
I have quite a serious problem with my phone.
I used stable CM11 as my ROM lately, worked nice, seemed to be ok. Now, if I want to boot my phone, it suddenly crashes as soon as I want to enter unlock code. "Funny" thing is, performing a full backup via TWRP didn't help.
So I decided to wipe everything (even sdcard) and do everything from scratch, including flashing boot.img. After flashing the ROM zip, it's still the same.
After that, I flashed boot.img from AOSP 5.1 Unstable, installed this new, different ROM (which I had successfully tested on my device before) and STILL THE SAME?!
What's going on here? It sounds a bit like defective hardware, but I never experienced a crash when I was in Recovery mode, so that's quite unplausible.
My last idea is to flash stock ftf. Perhaps this will help...
Hi,
I am running RR 5.8.3, v. from 23-04-17.
I was forced to set fluencetype for the past few flashes to null or something, because otherwise I did not have sound during calls.
Right now the call quality is unbearably bad. It was not THAT bad on older ROMs, before I had to disable this fluence-thingie.
I want to upgrade the ROM, but what else am I supposed to improve the voice quality? I could not find a decent source.
Factory reset -> VoLTE patch -> RR ROM -> GAPPS?
Anything else? Some people wrote "updade your firmware" - how am I supposed to interpret it? Install MIUI Rom? So, like flash it from TWRP and replace it with RR 2 minutes later? I am alergic to MIUI.
This topic kind of explains it, but links are down and content might be outdated:
https://forum.xda-developers.com/redmi-note-3/how-to/android-n-permanent-volte-fix-10000-t3541922
Up
Up.
Right now I am stuck on a bootloop with rom's logo. I can access TWRP and flash stuff just fine, but I cannot load the system. Restoring from backup has failed.
I have installed 7.7.7 firmware - https://www.androidfilehost.com/?fid=673368273298969813
and booted to the system. It did not recognize my PIN and locked my card. Unlocked it with PUK on another device, but still the same.
Flashed newest RR with GAPPS and reflashed the firmware. Bootlooping begun.
Tried different ROMs, tried a different firmware - https://www.androidfilehost.com/?fid=673368273298969055
What should be the "next step"?
I was able to fix it, but man this was my last flash of this device. My next step was to brick the device, had to start from stratch after that. Never had so many different issues... I will rot on current ROM till Pixel 2 arrives.
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'
So this guide was written by @DeathByArmadillo who partly copied it from user "Danmue" from an old post. Anyway, it works.
Tested on Mi Note 10 with Global rom.
Just re-posted it in it's own thread because the information was a bit scattered among the threads.
What you will need:
- An unlocked phone (duh). It can take 3 days, a week, or more to get your phone unlocked. So I recommend starting the process as soon as you get the phone.
- A full backup of your phone as this will wipe it clean. Unlocking ALSO wipes your phone. You can use Google One (as far as I know) to backup most stuff. I usually use Super Backup & Restore to back up all contacts, calendars, etc. Then I copy over ALL my folders to my PC - except "Android" as it's just usually junk/data files for apps that I can't copy back anyway. Last I use Google One to also do a full backup. As far as I know - this is what you can do without root.
- OrangeFox recovery: https://forum.xda-developers.com/mi-note-10/how-to/twrp-orangefox-recovery-mi-note-10-cc9-t4008131
- Unoffiicial TWRP recovery by mauronofrio: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
- Xiaomi.EU stable OR dev branch: https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4008225 || https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4011409
- Fastboot/adb/Android SDK tools installation. https://developer.android.com/studio (Scroll down for "Command line tools").
Yes, you need the two recoveries. At least I needed both.
What we do, notes:
- I had issues with OrangeFox while I was using EEA firmware (EU). After flashing Global firmware on my phone the battery issues went away, and I was able to use OrangeFox after.
- TWRP can be a bit non-responsive, like for me it was at the unlock screen. For some reason after a few tries I managed to make my inputs work. Just kept touching the screen lol.
Steps:
- Boot your phone in fastboot mode. (Turn it off; Then hold VOLUME_DOWN and Power. it should display this weird looking thing with an ushanka saying FASTBOOT MODE.)
- Open command prompt and go to the Android SDK tools folder where you can find "fastboot.exe".
- Type the following:
Code:
fastboot boot twrp-3.3.1-0-tucana-mauronofrio.img
- TWRP will boot up now. Unlock your device as normal and it should show up in Windows as a drive.
Copy over the
Code:
OrangeFox-Unofficial-tucana-20191120.zip
file.
- Go into Install on your phone and pick the OrangeFox zip file you just copied over.
Once done, just go Back and Reboot and Recovery.
- OrangeFox should boot up. Unlock once again.
- Go into Partition management, tap Data, and tap Format. Not wipe, FORMAT.
(if you get an error reboot to recovery and try again)
- Go Back, Reboot, Recovery.
- Copy the Xiaomi.EU rom you want to the phone. I used Stable.
- Use Install within OrangeFox to install the rom.
- Go back. Reboot into Recovery. Once again.
- Format data partition. NOT wipe. Format.
- Finally, reboot to system.
Thanks for taking the time to order it, good job
Though NOW the issue is that the recovery (either TWRP or Orange Fox) won't work with touch, which is a bit of a pain.
DeathByArmadillo said:
Though NOW the issue is that the recovery (either TWRP or Orange Fox) won't work with touch, which is a bit of a pain.
Click to expand...
Click to collapse
Sorry my emails didn't arrive. Interesting, it works for me. Followed the steps 100%, using Mi Note 10 Global rom. I just booted up Orange Fox after turning off my phone and it works just fine. I seriously wonder what can kill recovery input... sounds like such a super weird bug.
I did boot TWRP (mauronofrio's) and then installed OrangeFox from there. Maybe that's the key.
h8Aramex said:
Sorry my emails didn't arrive. Interesting, it works for me. Followed the steps 100%, using Mi Note 10 Global rom. I just booted up Orange Fox after turning off my phone and it works just fine. I seriously wonder what can kill recovery input... sounds like such a super weird bug.
I did boot TWRP (mauronofrio's) and then installed OrangeFox from there. Maybe that's the key.
Click to expand...
Click to collapse
Yeah, possibly that, no clue. Don't get me wrong, it's not a biggie, as I always have an OTG mouse setup just in case that kind of stuff happens, just weird. On the whole that phone is a bit of an odd duck, not sure I'm going to stick to it, too much inconsistencies, both hardware and software.
DeathByArmadillo said:
Yeah, possibly that, no clue. Don't get me wrong, it's not a biggie, as I always have an OTG mouse setup just in case that kind of stuff happens, just weird. On the whole that phone is a bit of an odd duck, not sure I'm going to stick to it, too much inconsistencies, both hardware and software.
Click to expand...
Click to collapse
Yea I tried to find blobs today for 730g but there is nothing on the internet (yet?).
I mean, the phone works for me - if they just fix the missing "Ignore Do Not Disturb" option, I am golden...
flashed orangefox through twrp, touch doesnt work at all. But it worked on the first time, flashed MIROOM. Maybe it is related to the currently installed rom.
Edit: Flashed TWRP from fastboot and touch is working again. Just to be sure, reflashed orangefox and it didn't work again... I'll stick to TWRP, although I dont know if it is a problem with TWRP but i can't flash GSI roms
Hello,
Sorry for my Bad english.
with the stable rom 11.0.7, the orange fox touch works perfectly.
but with development roms, touch does not work. tested with 20.1.9 and 20.1.15.
Touch work with flashed twrp from fastboot
h8Aramex said:
So this guide was written by @DeathByArmadillo who partly copied it from user "Danmue" from an old post. Anyway, it works.
Tested on Mi Note 10 with Global rom.
Just re-posted it in it's own thread because the information was a bit scattered among the threads.
What you will need:
- An unlocked phone (duh). It can take 3 days, a week, or more to get your phone unlocked. So I recommend starting the process as soon as you get the phone.
- A full backup of your phone as this will wipe it clean. Unlocking ALSO wipes your phone. You can use Google One (as far as I know) to backup most stuff. I usually use Super Backup & Restore to back up all contacts, calendars, etc. Then I copy over ALL my folders to my PC - except "Android" as it's just usually junk/data files for apps that I can't copy back anyway. Last I use Google One to also do a full backup. As far as I know - this is what you can do without root.
- OrangeFox recovery: https://forum.xda-developers.com/mi-note-10/how-to/twrp-orangefox-recovery-mi-note-10-cc9-t4008131
- Unoffiicial TWRP recovery by mauronofrio: https://forum.xda-developers.com/mi...overy-unofficial-twrp-xiaomi-mi-note-t4015805
- Xiaomi.EU stable OR dev branch: https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4008225 || https://forum.xda-developers.com/mi-note-10/how-to/rom-miui-11-xiaomi-eu-t4011409
- Fastboot/adb/Android SDK tools installation. https://developer.android.com/studio (Scroll down for "Command line tools").
Yes, you need the two recoveries. At least I needed both.
What we do, notes:
- I had issues with OrangeFox while I was using EEA firmware (EU). After flashing Global firmware on my phone the battery issues went away, and I was able to use OrangeFox after.
- TWRP can be a bit non-responsive, like for me it was at the unlock screen. For some reason after a few tries I managed to make my inputs work. Just kept touching the screen lol.
Steps:
- Boot your phone in fastboot mode. (Turn it off; Then hold VOLUME_DOWN and Power. it should display this weird looking thing with an ushanka saying FASTBOOT MODE.)
- Open command prompt and go to the Android SDK tools folder where you can find "fastboot.exe".
- Type the following:
- TWRP will boot up now. Unlock your device as normal and it should show up in Windows as a drive.
Copy over the file.
- Go into Install on your phone and pick the OrangeFox zip file you just copied over.
Once done, just go Back and Reboot and Recovery.
- OrangeFox should boot up. Unlock once again.
- Go into Partition management, tap Data, and tap Format. Not wipe, FORMAT.
(if you get an error reboot to recovery and try again)
- Go Back, Reboot, Recovery.
- Copy the Xiaomi.EU rom you want to the phone. I used Stable.
- Use Install within OrangeFox to install the rom.
- Go back. Reboot into Recovery. Once again.
- Format data partition. NOT wipe. Format.
- Finally, reboot to system.
Click to expand...
Click to collapse
Hi bro...i have some annoying Issues on my mi note 10 ,so i want to try install xiaomi.eu and see if Issues can be fixed...i'm a newbie on flashing roms so can i have a very detailled guide for a guy like me : i mean images of the guide or for exemple
Sorry for my english,i'm french-speaking
ronademe said:
Hi bro...i have some annoying Issues on my mi note 10 ,so i want to try install xiaomi.eu and see if Issues can be fixed...i'm a newbie on flashing roms so can i have a very detailled guide for a guy like me : i mean images of the guide or for exemple
Sorry for my english,i'm french-speaking
Click to expand...
Click to collapse
Well, what's the question? What did you try? Where are you stuck?
You can use Google Translate...
h8Aramex said:
Well, what's the question? What did you try? Where are you stuck?
You can use Google Translate...
Click to expand...
Click to collapse
Don't worry bro my english is good enough to unserstand the guide ?...but i need to know for exemple words or expressions liké" boot to recovery" etc... How to do that ? What touches to use on Windows
You know what i mean ? I need images or pictures step by step if possible ?????
Can we just install Global Rom in the update option under settings ?
I mean, without needing to unlock the bootloader ?
Must the bootloader (OEM Unlock) remain enabled forever after following this guide?
Checking for updates
how long does it take to cheking for updates i stuck ? Thank you.
anyone with this rom experiencing huge battery drain ?
sigma119 said:
anyone with this rom experiencing huge battery drain ?
Click to expand...
Click to collapse
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
H-Emmanuel said:
Must the bootloader (OEM Unlock) remain enabled forever after following this guide?
Click to expand...
Click to collapse
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
WaldenGaming said:
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
Click to expand...
Click to collapse
There is a MIUI Global 11.0.13? The latest I see is 1.0.7?
I'm looking to update for improved camera speed etc.
First timer on Global Rom, now o EU Beta. Followed instructions, nothing else needed. Thanks a lot! (also, having an usb mouse just in case paid off)
WaldenGaming said:
I get big battery drain on official MIUI Global 11.0.13. Are you running Miui EU or global rom?
Miui.EU (Based on china rom) https://xiaomi.eu/community/threads/miui-11-0-stable-release.52628/
Some reported that their battery issue went away after flashing miui.eu
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
For flashing recoveries as twrp, I think the bootloader always needs to be unlocked.
Click to expand...
Click to collapse
I am using one from xiaomi.eu. Also ive experienced this rom to shutting down randomly. For a week period it happened twice.
sigma119 said:
I am using one from xiaomi.eu. Also ive experienced this rom to shutting down randomly. For a week period it happened twice.
Click to expand...
Click to collapse
Well, that's better than battery drain I hope android 10 with miui will be flawless:fingers-crossed:
HI to all
Strange behaviour with my phone. As title says, I cannot add PIN or fingerprint.
I have unlocked bootloader, flashed TWRP and rooted with Magisk 23. On Dev Settings OEM lock is enabled but I can switch it off if I want. It is not dimmed as it should be. I have checked bootloader unlock status via Fastboot - "fastboot getvar all" and it says (bootloader) unlocked: yes
Has anyone any idea why PIN or fingerprint cannot be added?
I have to say that I am bit frustrated with this phone, always something is not working as it should. Never know what tomorrow happens.
This my second One Plus Nord 2. First one I had 2 months, during that period of time it was 3 times at service. Once motherboard was changed. What they did other (2) times I do not know. And now this new one, which I got as replacement bec older sucks , is starting to suck too
Is metadata responsible for PIN or fingerprint? It holds keys for security, so maybe if I flash new metadata would it help/fix problems or is it device specific?
Any ideas, thank you
I had this exact same issue as well, and it seems to be linked to the way TWRP restores/saves the data partition in my case. My fix was to boot into recovery and wipe/reformat all data.
After a fresh wipe, my issues were resolved, but i had to manually redownload and setup all apps again. I did multiple tests and the issue would always come if i restored my data partition; whether i flashed it via TWRP or via fastboot. It's likely the way TWRP saves the data partition was my issue.
Zombnombs said:
I had this exact same issue as well, and it seems to be linked to the way TWRP restores/saves the data partition in my case. My fix was to boot into recovery and wipe/reformat all data.
After a fresh wipe, my issues were resolved, but i had to manually redownload and setup all apps again. I did multiple tests and the issue would always come if i restored my data partition; whether i flashed it via TWRP or via fastboot. It's likely the way TWRP saves the data partition was my issue.
Click to expand...
Click to collapse
HI and thank you for reply
Do you mean stock recovery? I have tried TWRP - format data, didn't help.
If you format data using TWRP my experience is that TWRP will uninstall itself in the process, so you'll boot into stock recovery after that anyway.
I would honestly suggest doing both. If you have TWRP, reformat and wipe using TWRP wipe. Next time you boot to recovery, it should be stock. Do another reformat+wipe on stock recovery. Should do the trick.
Never mind, I did not want to steal your topic. Open my own!
exis_tenz said:
Never mind, I did not want to steal your topic. Open my own!
Click to expand...
Click to collapse
hi. yes, we have different problem but i have to agree, always something strange happens with this phone. kinda sucks
I'm close to selling the device. My stock rom was re-flashed 5 times already (can't do anything once you're "well" bricked), got my mainboard changed and still the damn thing ain't doing what's it supposed to. I'm so fed up with this device before I actually start(ed) using it. Bah.
exis_tenz said:
I'm close to selling the device. My stock rom was re-flashed 5 times already (can't do anything once you're "well" bricked), got my mainboard changed and still the damn thing ain't doing what's it supposed to. I'm so fed up with this device before I actually start(ed) using it. Bah.
Click to expand...
Click to collapse
i had same too, 2 times service flashed stock back and 1 time change motherborad. now they gave me new one, but still prbs. am fed up too
exis_tenz said:
I'm close to selling the device. My stock rom was re-flashed 5 times already (can't do anything once you're "well" bricked), got my mainboard changed and still the damn thing ain't doing what's it supposed to. I'm so fed up with this device before I actually start(ed) using it. Bah.
Click to expand...
Click to collapse
jis251 said:
i had same too, 2 times service flashed stock back and 1 time change motherborad. now they gave me new one, but still prbs. am fed up too
Click to expand...
Click to collapse
Funnily enough, both of your issues are caused by TWRP not flashing partitions correctly, at least from my testing.
In Jis's case, (RE: Current thread) it's because TWRP does not flash the DATA partition correctly, and prevents the phone from being able to set a lockscreen password (and therefore the Data partition cannot be encrypted). And without a lockscreen, the stockOS does not allow you to set biometrics such as fingerprints/face unlock, though theoretically in this case, both sensors work perfectly, it's a simple software restriction.
In Exis's case,(RE: https://forum.xda-developers.com/t/cant-add-fingerprint-device-vibrates-like-hell.4389581/ ) it's because TWRP does not flash the PERSIST partition correctly. This messes up the sensor calibration data for the camera and fingerprint, which effectively makes both features completely unuseable.
Remember, @TheMalachite 's release of TWRP is an unofficial release and we're just glad to have it working at all. That said though, I wonder if TheMalachite is aware of these issues?
Zombnombs said:
In Exis's case,(RE: https://forum.xda-developers.com/t/cant-add-fingerprint-device-vibrates-like-hell.4389581/ ) it's because TWRP does not flash the PERSIST partition correctly. This messes up the sensor calibration data for the camera and fingerprint, which effectively makes both features completely unuseable.
Click to expand...
Click to collapse
Thing is: I didn't flash ANYTHING in TWRP. It's a clean recovered stock rom done by an official OnePlus servicecenter.
Zombnombs said:
Funnily enough, both of your issues are caused by TWRP not flashing partitions correctly, at least from my testing.
In Jis's case, (RE: Current thread) it's because TWRP does not flash the DATA partition correctly, and prevents the phone from being able to set a lockscreen password (and therefore the Data partition cannot be encrypted). And without a lockscreen, the stockOS does not allow you to set biometrics such as fingerprints/face unlock, though theoretically in this case, both sensors work perfectly, it's a simple software restriction.
In Exis's case,(RE: https://forum.xda-developers.com/t/cant-add-fingerprint-device-vibrates-like-hell.4389581/ ) it's because TWRP does not flash the PERSIST partition correctly. This messes up the sensor calibration data for the camera and fingerprint, which effectively makes both features completely unuseable.
Remember, @TheMalachite 's release of TWRP is an unofficial release and we're just glad to have it working at all. That said though, I wonder if TheMalachite is aware of these issues?
Click to expand...
Click to collapse
This is completely unrelated to TWRP itself. OxygenOS for Nord 2 use ColorOS base which is know to give such issues (Also happen with OPPO and Realme devices on ColorOS and RealmeUI)
exis_tenz said:
Thing is: I didn't flash ANYTHING in TWRP. It's a clean recovered stock rom done by an official OnePlus servicecenter.
Click to expand...
Click to collapse
Then they messed up your persist image and/or calibration data in some way or fashion. Take it back and complain they messed up your stuff. Probably some novice technicians who made a mistake would be my guess.
TheMalachite said:
This is completely unrelated to TWRP itself. OxygenOS for Nord 2 use ColorOS base which is know to give such issues (Also happen with OPPO and Realme devices on ColorOS and RealmeUI)
Click to expand...
Click to collapse
Ah, that's good to know. So it seems everything is the fault of ColorOS.
Camera works, fingerprint doesn't...