Related
hello, im just recently flashing FTF files to my z ultra, and its works fine until i left my phone idle for a while, and when checking back all sound input / output is gone. Totally gone, cant receive a call, no sound all only vibrate, mic also disabled, i must restart then the sound will back.
I already try to flash another FTF and it also having the same problem. Is it bug from 5.1.1 ? what should i do ? im not to advanced in android. Thanks
what FTF files that I used : C6802_Customized+TH_14.6.A.0.368.ftf and C6802_14.6.A.0.368_1275-8963_Customized-MEA.ftf
both of them sharing the same problem, randomly no sound after idle ( screen of for a while )
Do you wipe before/after you've flashed it/them? Also, I would probably have flashed an older FTF just to check that it's a software issue and not a hardware one (not that any hardware issue would do these things), but just to be sure. If the same issue happens on a lower firmware, then it's a little harder to determine what the issue might be.
Also, try to flash an FTF from your region or one that's fairly close. I flashed a Saudi Arabian .368 FTF the first time, and I had major issues with battery and other smaller bugs, but when I flashed one from my region (Europe), it solved itself. I just think you're having some bad luck, and it sounds like some software issues. Don't forget to wipe the system before or after you've flashed it.
Im flashing using flashtool, i suppose i already wipe, and im trying to find the stock version, but it seem i cant find a proper one, im trying to find the unmodifed / original one. but it seem all dead link, when i found one, i flash and it stuck at bootloop. So i just go back to the 5.1.1, which have the bug like that.
Anyway, the C6802 tft is limited, can i use another C6833 ftf ?
Shigeur said:
Im flashing using flashtool, i suppose i already wipe, and im trying to find the stock version, but it seem i cant find a proper one, im trying to find the unmodifed / original one. but it seem all dead link, when i found one, i flash and it stuck at bootloop. So i just go back to the 5.1.1, which have the bug like that.
Anyway, the C6802 tft is limited, can i use another C6833 ftf ?
Click to expand...
Click to collapse
Do you have the C6833? Or the C6802?
Klaos3000 said:
Do you have the C6833? Or the C6802?
Click to expand...
Click to collapse
i have the C6802
Shigeur said:
i have the C6802
Click to expand...
Click to collapse
Okay, I'm going to make an Indonesian C6802 FTF for you, so just hang tight for a little while and I'll have it for you soon (20-30 min).
Here you go: https://drive.google.com/file/d/0B_VjBcIjyoZDX3BFQ0hpeHJHbHM/view?usp=sharing
thanks, ill try, i hope its working...
Hello, im upping this thread...
its still not working, the sound still have same bug...
it seem something weird around bootloader stuff, i find my phone is unlocked bootloader.
is anyone know that unlocking bootloader can make sony xperia z ultra no sound bug like this ?
anywork around ?
i already try installing custom rom, but all my custom rom i try is stuck at bootloop, or just wont stick ( it detected as no OS and just keep on SONY logo )
any recommendation of custom rom that i should try ?
and im really newbie here, all recovery that i install is gone after i flash custom rom, so its really hard to flash rom, root, install recovery and install custom rom which is a dead end ( bootloop )
*its really weird bug...
sometime sony camera app also wont open ( app crash ) + no sound
after rebooting 2-3x its fix both of them, after screen go to sleep
sound is gone, and the camera still works fine until i reboot or no battery ( repeat reboot and it fix the camera and sound ( temporary )
>> relock bootloader, and restore with official software ( pc companion ) still not fix this bug.
You use Google play "soundabout" app .workaround. will restore sound
rockky said:
You use Google play "soundabout" app .workaround. will restore sound
Click to expand...
Click to collapse
im trying, ill post later... for now my phone is muted, i only use it for reading news only
Shigeur said:
im trying, ill post later... for now my phone is muted, i only use it for reading news only
Click to expand...
Click to collapse
it still cant, it seem something wrong with audio engine / system files. when i press 'play' button on walkman it didnt changed.
all sound app didnt work and saying something wrong
as for camera, i cant use sony default camera, but i can use other camera app, such as google camera. but as the audio all 3rd party app not working either directly crash or just stay still play button can be pressed.
up again...
trying installing custom rom ( resurection remix ) now it success, with xz dual recovery
but still no sound comming out, camera is working fine.
anyone experience the same problem ? sony rom and stock make camera app crashed and no sound
custom rom, still no sound.
the same error, when i press play button on any audio player, it just back to paused and the time still in 00:00
it seem something wrong in the system, but i just fresh install
The bug sounds very strange (haven't experienced it on C6802/HK or C6833/DE) but will give you some recommendations for flashing:
1. Download the TWRP recovery from this thread and flash it:
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-togari-t3197082
If you are on a stock based ROM, do step 1b. Otherwise flash a stock/based ROM first since it is necessary for extraction of those particular files.
1b. Before flashing anything, download Root Explorer or another file manager with root access and copy the files inside /Data/etc to the memory card. This is a way of avoiding the MAC address issue on some custom ROMs.
2. Download a ROM of choice. I would recommend BlissPop or Resurrection Remix but try the 20151007 build (the newer ones suffer from a WiFi issue).
2b. Check this thread for a fix for lost IMEI on C6802:
http://forum.xda-developers.com/xperia-z-ultra/general/guide-stock-to-custom-rom-t2901739
3. Boot into TWRP and wipe everything. Wipe system, data, cache, Dalvik cache and the internal storage.
4. Flash the ROM and the IMEI fix.
5. Wipe cache and Dalvik cache again.
6. Boot the ROM, let it settle for 5 minutes (after seeing the setup guide) and reboot, then do the setup.
7. Install a file explorer and copy the files from /Data/etc back into its place. You will notice that the folder is empty on a ROM such as BP so you will put the files back in place.
8. Reboot the device.
If the problem persists despite those steps, I would assume that something is corrupted and I would do a full wipe, flash a stock ROM and then repeat the steps again. I know that some root methods such as KingRoot can leave trash files which can interfere with ROM flashes and updates but doing a full wipe should clear those things out.
One option is a downgrade to a KitKat stock ROM such as 108 followed by rooting with Easy Root Tool and then making an update by flashing a new stock ROM with the /system partition excluded followed by reflashing of TWRP and flash of a custom ROM.
If nothing helps, then there is a possibility of some kind of hardware issue. I am supporting four Ultra's in total (one C6802 and three C6833s) and have never encountered such a problem. I have experienced BT dropouts on early LP ROMs and also phone FCs after kernel experimentation but everything has been cleared up by doing a clean flash with a full wipe.
A last long shot would be to try a different SIM card. Not that I suspect it but it has happened that some SIMs have been problematic thus causing strange behavior with the device. I don't think it is the SIM but it is just a way of excluding the possibility. Even far-stretched solutions can work when issues are very strange.
E90 Commie said:
The bug sounds very strange (haven't experienced it on C6802/HK or C6833/DE) but will give you some recommendations for flashing:
1. Download the TWRP recovery from this thread and flash it:
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-togari-t3197082
If you are on a stock based ROM, do step 1b. Otherwise flash a stock/based ROM first since it is necessary for extraction of those particular files.
1b. Before flashing anything, download Root Explorer or another file manager with root access and copy the files inside /Data/etc to the memory card. This is a way of avoiding the MAC address issue on some custom ROMs.
2. Download a ROM of choice. I would recommend BlissPop or Resurrection Remix but try the 20151007 build (the newer ones suffer from a WiFi issue).
2b. Check this thread for a fix for lost IMEI on C6802:
http://forum.xda-developers.com/xperia-z-ultra/general/guide-stock-to-custom-rom-t2901739
3. Boot into TWRP and wipe everything. Wipe system, data, cache, Dalvik cache and the internal storage.
4. Flash the ROM and the IMEI fix.
5. Wipe cache and Dalvik cache again.
6. Boot the ROM, let it settle for 5 minutes (after seeing the setup guide) and reboot, then do the setup.
7. Install a file explorer and copy the files from /Data/etc back into its place. You will notice that the folder is empty on a ROM such as BP so you will put the files back in place.
8. Reboot the device.
If the problem persists despite those steps, I would assume that something is corrupted and I would do a full wipe, flash a stock ROM and then repeat the steps again. I know that some root methods such as KingRoot can leave trash files which can interfere with ROM flashes and updates but doing a full wipe should clear those things out.
One option is a downgrade to a KitKat stock ROM such as 108 followed by rooting with Easy Root Tool and then making an update by flashing a new stock ROM with the /system partition excluded followed by reflashing of TWRP and flash of a custom ROM.
If nothing helps, then there is a possibility of some kind of hardware issue. I am supporting four Ultra's in total (one C6802 and three C6833s) and have never encountered such a problem. I have experienced BT dropouts on early LP ROMs and also phone FCs after kernel experimentation but everything has been cleared up by doing a clean flash with a full wipe.
A last long shot would be to try a different SIM card. Not that I suspect it but it has happened that some SIMs have been problematic thus causing strange behavior with the device. I don't think it is the SIM but it is just a way of excluding the possibility. Even far-stretched solutions can work when issues are very strange.
Click to expand...
Click to collapse
ill try, and will post the update, but maybe next month, i hope this work.
a bit busy this month preparing other stuff... thanks for helping
Shigeur said:
hello, im just recently flashing FTF files to my z ultra, and its works fine until i left my phone idle for a while, and when checking back all sound input / output is gone. Totally gone, cant receive a call, no sound all only vibrate, mic also disabled, i must restart then the sound will back.
I already try to flash another FTF and it also having the same problem. Is it bug from 5.1.1 ? what should i do ? im not to advanced in android. Thanks
what FTF files that I used : C6802_Customized+TH_14.6.A.0.368.ftf and C6802_14.6.A.0.368_1275-8963_Customized-MEA.ftf
both of them sharing the same problem, randomly no sound after idle ( screen of for a while )
Click to expand...
Click to collapse
Have you tried to flash the correct ftf? I don't have time to read through the thread.
Have you tried Sony repair tool?
What I would suggest is trying a different mixer path
Root directory>system>etc>mixer_paths.XML make a copy somewhere, delete the file and insert a new one.
I've owned a white 02 model and had similar issues I just ended selling it and getting a 06 model.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Shigeur said:
up again...
trying installing custom rom ( resurection remix ) now it success, with xz dual recovery
but still no sound comming out, camera is working fine.
anyone experience the same problem ? sony rom and stock make camera app crashed and no sound
custom rom, still no sound.
the same error, when i press play button on any audio player, it just back to paused and the time still in 00:00
it seem something wrong in the system, but i just fresh install
Click to expand...
Click to collapse
Ahh yes read your last part.
Try to switch out mixer path
My 02 had same issue but I was to impatient to bother.
RealityFails said:
Have you tried to flash the correct ftf? I don't have time to read through the thread.
Have you tried Sony repair tool?
What I would suggest is trying a different mixer path
Root directory>system>etc>mixer_paths.XML make a copy somewhere, delete the file and insert a new one.
I've owned a white 02 model and had similar issues I just ended selling it and getting a 06 model.
---------- Post added at 08:05 PM ---------- Previous post was at 08:02 PM ----------
Ahh yes read your last part.
Try to switch out mixer path
My 02 had same issue but I was to impatient to bother.
Click to expand...
Click to collapse
how to create a new mixer path ? just delete the old one ?
Shigeur said:
how to create a new mixer path ? just delete the old one ?
Click to expand...
Click to collapse
Make a back up, then delete it.
Once deleted add this one to the same location device>etc>mixer_path.XML
RealityFails said:
Make a back up, then delete it.
Once deleted add this one to the same location device>etc>mixer_path.XML
Click to expand...
Click to collapse
or it seem a hardware issue... just realised after doing a lot of fix..
if it shaked or pressed in some kind area of the screen the sound will gone for a while...
it seem the component are a bit loose inside.
you can see in video below
https://www.youtube.com/watch?v=kO8zN-v9b_w&feature=youtu.be
if someone can confirm this hardware issue, this thread can be closed, thanks a lot for those who help me
Merry Christmas !
Hi, my friends.
Great news . The new official update Leeco that has come in Indian web finally brings everything to their phones sold worldwide:
- Multilanguage. But, really. All are translated (I only tried Spanish, I assume that the other languages also). In Europe only translate to Spanish, English and French. The rest are Asian languages.
- Leeco Account. Integrated with Google account, as it should be. Leeco access to the entire EUI universe. Synchronization of our contacts, photos, etc.
- All active applications, including Leeco LIVE, Levidi, Leview ...
- Google for Works integrated with Gmail Exchange account, Play Music, Play Video, Google+, Yotube .
Only rest check battery perfomance, but ROM it´s smooth and powerful.
Download links:
Official: http://g3.letv.cn/209/7/47/letv-hdtv/0/upload/tmp/20160706171018829/LE_X2_X820-OS-OP-FGXOSOP5801507066S-5.8.015S.zip?b=123456&platid=5&splatid=500
Mega: https://mega.nz/#!wtplFRIQ!l5V9p8PtpmqEznqQjkm9vFNG6LCgM-KrpEDbTShiwn0
Enjoy ¡¡¡
yes, it's a good one. just installed no problems so far.
I had a problem with previous stock versions that 4G speed had some hickups....when I was downloading (for example from google store) it paused for 30 seconds..sometimes longer.
tried SIM in slot 2 and vice versa..but problem remains.
now it goes smoothly without pauses (so far)
also had the CM13 which is almost the best, apart from the sound bug...definitely one I want on this phone for a long time..if sound thingy is fixed.
thanks!
Recommendation Do Not Use India version
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
jim262 said:
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
Click to expand...
Click to collapse
Hmm..Ok! phone is encrypted indeed..do you know if there's as a way to decrypt or turn it off.?twrp is asking for a password when going onto recovery now...in previous roms the encrypt option was not greyed out.
or is only way to get in twrp and wipe everything.
Thanks !
jim262 said:
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
Click to expand...
Click to collapse
What is the way around the issue of encryption? So we can never install TWRP ever?
sanke1 said:
What is the way around the issue of encryption? So we can never install TWRP ever?
Click to expand...
Click to collapse
Under TWRP data it´s encrypted. But under Windows not. Copy to your computer all files that you need save (photos, music, etc.), and then format data in TWRP.
jim262 said:
This version apparently has data encryption enabled and will not show a viable data partition. This will cause TWRP to fail and subsequent attempts at root or installation of other roms.
Click to expand...
Click to collapse
Under windows DATA partition works properly, copy all your files (photos, music, etc.) into computer and then enter TWRP and format DATA.
This ROM it´s better that anyone, I think that worth trying. It´s awesome.
STEVE_MARS said:
Under windows DATA partition works properly, copy all your files (photos, music, etc.) into computer and then enter TWRP and format DATA.
This ROM it´s better that anyone, I think that worth trying. It´s awesome.
Click to expand...
Click to collapse
I wold'n say that his rom is better than others, here is still missing the multilingual support and so on. I'm atm with "Revolution 15s EUI 5.8 by TeaMSpaiN" alsolutely happy, just litte fine tuned and see my benchmark with over 143.000 points (first run). And yes the rom is smooth as hell.
Antutu proof pic:
http://www.pic-upload.de/view-31202011/Screenshot_20160714-071230.jpg.html
NU_User said:
I wold'n say that his rom is better than others, here is still missing the multilingual support and so on. I'm atm with "Revolution 15s EUI 5.8 by TeaMSpaiN" alsolutely happy, just litte fine tuned and see my benchmark with over 143.000 points (first run). And yes the rom is smooth as hell.
Antutu proof pic:
http://www.pic-upload.de/view-31202011/Screenshot_20160714-071230.jpg.html
Click to expand...
Click to collapse
:angel: yes, we developed Revolution series :good:. But I recommended you that try this Indian version .
STEVE_MARS said:
:angel: yes, we developed Revolution series :good:. But I recommended you that try this Indian version .
Click to expand...
Click to collapse
no
---------- Post added at 10:53 AM ---------- Previous post was at 10:25 AM ----------
@STEVE
if you want help you can try to fix the CM13 rom, THIS one, if would been fixed where of course the ultimare rom for our little beast.
STEVE_MARS said:
Under windows DATA partition works properly, copy all your files (photos, music, etc.) into computer and then enter TWRP and format DATA.
This ROM it´s better that anyone, I think that worth trying. It´s awesome.
Click to expand...
Click to collapse
You did not understand my question properly.
Right now, there is absolutely NO way to install TWRP on Indian X821 model. I cannot format DATA without installing TWRP.
All the TWRPs available on this forum give a BLOD (Blue Led of Death) The screen remains blank but powered on. The Blue LED light remains. There is another guy who is having the same problem and he has created a separate topic for it.
We can restart the phone normally but the installed TWRP gets overwritten with stock recovery.
atm here is no solution for your device, you need to wait until a developer create a TWRP compatible for your device.
sanke1 said:
You did not understand my question properly.
Right now, there is absolutely NO way to install TWRP on Indian X821 model. I cannot format DATA without installing TWRP.
All the TWRPs available on this forum give a BLOD (Blue Led of Death) The screen remains blank but powered on. The Blue LED light remains. There is another guy who is having the same problem and he has created a separate topic for it.
We can restart the phone normally but the installed TWRP gets overwritten with stock recovery.
Click to expand...
Click to collapse
What I did was to go into settings -> fingerprint -> -> other security options -> trusted credentials and disabled the credentials. You have to do this one by one as the clear all option is grayed out. From there I went into and fast boot and flashed TWRP recovery. I rebooted immediately to RECOVERY wiped everything on internal storage. I then transfered a ROM to storage and flashed normally. All is working again and TWRP and root are functioning.
WTF, ok it is a security related issue?
jim262 said:
What I did was to go into settings -> fingerprint -> -> other security options -> trusted credentials and disabled the credentials. You have to do this one by one as the clear all option is grayed out. From there I went into and fast boot and flashed TWRP recovery. I rebooted immediately to RECOVERY wiped everything on internal storage. I then transfered a ROM to storage and flashed normally. All is working again and TWRP and root are functioning.
Click to expand...
Click to collapse
I flashed old 14S Chinese ROM and then flashed recovery. My phone shows X820 now. I guess X820 and X821 may be just the same. It's the Chinese Roms show X820 and Indian Rom shows X821.
BTW I am on TeamSpain's CM Rom. Working good except charging.
If I used my Aukey QC 3.0 charger, the LED flashed like crazy and Ampere current measuring App showed 4680 mAh charging current and was climbing. (QC 3.0 shouldn't exceed 3000 mAh) So I immediately disconected it. Gave me a scare for a moment. Normal charging is slow but no LED blinking and feels safer.
NU_User said:
WTF, ok it is a security related issue?
Click to expand...
Click to collapse
Not a security. Just a way for Indian Dev's to prevent users from messing with their OS and to keep users on 100% stock.
STEVE_MARS said:
Hi, my friends.
Great news . The new official update Leeco that has come in Indian web finally brings everything to their phones sold worldwide:
Enjoy ¡¡¡
Click to expand...
Click to collapse
So can someone clarify if there's a way to clean install this ROM on a Chinese version of the phone and have a) TWRP b) ROOT working or is that impossible for now?
Exactly the same way as you install any other ROM. I have a Chinese phone and installed this ROM and uninstalled it because of its encrypted. Yes, the le-bloat is gone, but you will be unable to install TWRP or root because of the encryption.
jim262 said:
Exactly the same way as you install any other ROM. I have a Chinese phone and installed this ROM and uninstalled it because of its encrypted. Yes, the le-bloat is gone, but you will be unable to install TWRP or root because of the encryption.
Click to expand...
Click to collapse
Copy all your files (photos, videos, music, etc.) under Windows and enter TWRP, format DATA, reboot system, configure setupwizard, reboot TWRP again and copy supersu. zip and flash it.
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:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
First, you need to be on the latest stock firmware. Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
AOSiP was built from LineageOs.
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
50UND2 3NG1N33R said:
Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
Click to expand...
Click to collapse
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
50UND2 3NG1N33R said:
AOSiP was built from LineageOs.
Click to expand...
Click to collapse
Cool. I cant install neither.
50UND2 3NG1N33R said:
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
Click to expand...
Click to collapse
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
50UND2 3NG1N33R said:
All others might work, please do not ask in here how to up- or downgrade!
Click to expand...
Click to collapse
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
thegamerchunk1 said:
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
Cool. I cant install neither.
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
Click to expand...
Click to collapse
okay, sorry for not understanding you. You ain't a noob. So I should expect you did a clean install. Wiping Dalvik/ART Cache, Cache, Data, Internal Storage and System. this will give you a clean slate. And be on the latest TWRP which you already are in. If that fails, I can't help beyond that. VOLTE is Voice Over LTE. You are correct.
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...