Hello guys! After experiencing all custom ROMS including Xiaomi.EU, figured out that every single one has some small inconvenience for me and planning to return to stock, eventually using only Magisk and potentially a custom Kernel.
Managed to install every single version of Global Developer ROM, everything works well except the FaceUnlock that was gone, (the phone remained stucked in China region) and I am not able to access the fingerprint section, after few tries it brings me an error message.
Tried also using MIFlash , but the Fastboot ROM writting took 3 sec to write and stopped as successfully, then nothing but bootlooping.
Currently is the phone is functional, but as mentioned before not able to setup new fingerprints (using cache and data from old recovery and those work) neither Face Unlock.
Tried to Google any kind of solution, but unfortunately nothing worked.
Any suggestion is appreciated.
I see that nobody is interested to support, so I continuously researched and figured out that doing a full wipe and following these steps from this post will solve my problem:
https://forum.xda-developers.com/mi-8/help/chinese-mi8-to-global-instructions-t3839665
From I don't know which reason I was blocked on China region without the possibility to changing it.
Related
Hi guys,
this is gonna be a long story, but I'm at end of my wits.
So my phone (HTC One M7_UL Vodafone DE) got water damaged (it was submerged in water for at least a minute). I tested it again last weekend and it seemed to work in terms of hardware. I managed to test the speakers, the charge jack, the headphones jack, wifi, gsm, both cameras, etc. it all seems to work fine, and it's not about that anyways. I kept getting a "com.htc.htcdialer" issue, saying the process had unexpectedly crashed and then a few minutes later the phone would reboot. I tried finding out what this error was and how to fix it but I couldnt find anything. Also its weird that I got a software error.
So I unlocked the bootloader (via htcdev.com), flashed the latest recovery (I tried both cwm and twrp), which was also fine. I managed to install the latest Android Revolutions HD (53.0) and thats where the problems started again: I would get to the lock screen but as soon as I would swipe up to unlock it I would the white screen with the HTC letters on it. I tried wiiping all the cache and partitions i could find and reinstalled that rom, but the problem remained the same. Tried a different recovery (twrp) repeated all the steps and still no more luck than before.
So I decided to give a different rom a try and just flashed the latest stable cyanogenmod rom on it, and that boots fine, but eventually without error message reboots as well.
Then I tried flashing the latest viper rom, but there I have the same issue as at the beginning, that I get as far as the lock screen and then it just wont let me unlock it.
And that's where Im at the end of my wits. I cant imagine its a hardware related issue, but i might be wrong.
Ideally I would love to get my hands on a nandroid backup to restore the phone to stock, a stock rom ruu, but I cant find any of those either.
I'd really appreciate your help.
Let me know if you need specific details of installations, versions, decide numbers, etc
I bought new Mi5 and I still didn't put Sim card inside wanted to configure and see what phone can but when I entered configuration menu after 1st power up I manage to choose language and few things more and phone rebooted, then I manage to almost finish configuration then freeze and reboot again, after few tries I finished configuration but freeze (usually only last few seconds) and reboot happen again. Then phone offered me update software which I manage to reach from 3rd time and successfully update only with Mi PC Suite, not from phone update app. Interesting, all flashing proces with Mi PC Suite always is going as should be, without reboots etc... Crap happen only in OS. Now I got latest China stable (I bought phone in China) which has same problem with rebooting. Then I wiped all I can, factory reset etc...nothing helps.
-Still didn't unlock phone in case I need to return it.
-Didn't try global Rom because I can't flash it
I was reading forums and found a lot people have same problem but didn't find what they done on the end to make phone work.
If anyone have some solution, let me know. Returning phone from EU to China is not 1 day Or does someone know if someone in EU can service this if needed?
thanks in advance
huh,
I solved (for now) problem with installing this, developer version of miui 8 from here
http://xiaomiadvices.com/download-miui-8-6616-china-developer-rom-recoveryfastboot/
Downloaded it and installed with English version of MI PC Suite. Developer rom is Chinese (as my default software version in phone) over latest Chinese 7.3.10 miui
With original software phone was restarting, freezing randomly every 30 seconds or 1 minute of usage.
Now need to wait to unlock phone so I can use Global version of rom to get play store etc...
Hello,
I had the intention to install CM13 on my newly purchased Mi5 (that came with "MIUI 7.3.4.0 Global stable"), so after unlocking, I tried to install TWRP on it at first. Because of the technical problems this currently still involves, looking for a solution, I stupidly flashed an incorrect boot.img on my device (originating from this thread that was about another MI5 ROM version). Now the device still works again after a factory reset, but without any Wifi features (Wifi connection, thethering).
Does anyone know how to fix this? I couldn't find any resource linking to another boot.img (I guess I'd need one for 7.3.4 Global) so far and I'm not familiar with Xiaomi phones enough to help myself otherwise.
thanks, r.
Hello,
So my Moto X (1st gen, 2013, XT1058) used to work fine on KitKat but after it auto-updated to Lollipop it started messing up more and more every day. The phone is fully stock and locked. Here's a brief list of problems:
random freezes and crashes of apps and the OS itself
random screen freezes (doesn't respond to touches) or completely blank screen apart from the notification bar, often times nothing help but a reboot
random reboots, "optimizing apps" every so often on boot, especially when on charger
flaky and unreliable WiFi, not connecting when it should or disconnecting at random including when screen goes off (despite having "always on" selected)
GPS would sometimes have difficulty acquiring lock and would lose lock randomly (worked just fine before)
I'm not quite sure what to do at this point. It's the AT&T variant which means the bootloader is not unlockable. It is also updated to the latest OTA (build LPAS23.12-21.7-1) which means no rooting method works, or at least I haven't been able to find any. So I can't get even a temproot. I tried everything I could find, nothing worked and I'm running out of options. I love this phone and I'd like to get it back to working order. I'm wholeheartedly hoping someone here will have some good advice or some resource I haven't tried.
Here's what I tried so far:
multiple factory resets, both from system settings and through recovery
didn't help, works for a while but all the issues reappear soon after
rooting with KingRoot
failed, rooting method not available
rooting using this method
failed (not surprising, it does mention it doesn't work on OTA)
unlocking BL via Moto's official unlock service
device not supported
installing moforoot
failed, mofoverify just quits silently and the phone shows a message about some missing fastboot var
unlocking BL using Sunshine
says the device should be supported but then fails acquiring temproot, the phone just reboots
reflashing stock KitKat from here (file: ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip) via fastboot
failed, OS/BL downgrade not allowed
reflashing stock Lollipop from here (file: ATT_XT1058_5.1.0_LPAS23.12-21.7-1_cid1_CFC.xml.zip) via fastboot
partial success, managed to flash a few parts, however it fails on all relevant partitions (gpt, boot, system), reports "downgrade not allowed" just like with KitKat which is surprising, this version/build should be exactly the same as what's currently on the phone
wiping userdata and cache via fastboot
didn't help
I might have tried some other things/methods too, this is just what I could remember right now.
Again, I'd very much appreciate if someone could help me revive this phone. I enjoyed using it while it was working well and I'd like to get it back to that state. Any help is very much appreciated.
Cheers!
I'm having exactly the same issues on my wife's moto x. The only thing I've been able to do for a temporary fix is to enter stock recovery and clear cache. Is there really no root/custom rom method for this device?
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I'm sure there are several possibilities that could be software related. However, I've had this issue on a couple of my older phones and it just turned out that the power button was sticking. Just had to pull the phone apart and clean it.
If nothing else seems to work for you, it wouldn't hurt to check this.
PS: I have 4 boys who like to play on the devices with sticky fingers.