Hi guys, I have a problem with a perfectly working Mi4c and am looking for some help.
I bought the phone online and it worked perfectly except for the fact that it had a custom ROM (not official) with lots of bloatware. So what did I do? Installed the official stable rom from Xiaomi (this is my first Xiaomi phone, didn't know much about the bootloader thing).
The problem now is that after the update I lost my keyboard (it diessapeared and when in options you tap on keyboard settings, nothing happens). You know, apparently it is a common problem, you can't type anything. The apparent solution is a simple cache wipe on recovery. As you can guess where this is going... when I boot into recovery mode all I get is the "connect to computer via USB" picture, because my phone is locked (or so I read). So, no recovery. Can't wipe cache, can't use the phone without a keyboard. Everything else works fine.
My bootloader is locked now (because I installed the stable ROM) so I cannot flash TWRP, another recovery, another ROM, nothing, nada.
I applied for unlock and got permission (yey!), however the account in my phone is not the same as the one I used to ask for permission (my mistake). So, my phone doesn't get verified. I can't edit the account on the phone (log out, log in) because I don't have a keyboard. Thank god I didn't log out so an account is still open on the phone, so I applied again a second time with that account but that was just today, so I would have to wait again for a couple of weeks. Again. No working Mi4c for like a month total.
This is not my daily drive phone thankfully so I can just be patient but really... isn't there anything I can do? Suggestions? Something I might be missing?
TLR
Problem: I have no keyboard. Thus can't use phone. Phone works flawlessly though.
Solution: Wipe cache in recovery.
Problem: No access to recovery, just "USB connect" picture when booting.
Solution: Flash TWRP/Another recovery, even stock/ROM
Problem: Bootloader locked
Solution: Unlock
Problem: Different account when asked for permission, since no keyboard, can't edit account on phone.
Solution: Re apply for permission with correct phone account ** current status **
Problem: I don't want to wait anymore, can't I do anything? The phone works flawlessly bar the dissapeared keyboard issue! If no solution I have to wait again for a couple of weeks...
Just use this guide to unlock bootloader. U dont need permission from xiaomi or keyboard http://forum.xda-developers.com/showthread.php?t=3336779
Wysłane z mojego Mi-4c przy użyciu Tapatalka
Thanks for the answer! Believe it or not I already tried it but since my bootloader was locked I obvioucly couldn't downgrade to do that (fastboot? locked, updater? failed check or something like that). Still I already got Xiaomi's permission and unlocked and everything is fine now, thanks a lot!
Related
Hi All,
I just rooted with chainfire .img via fastboot and updated supersu to latest from google play. I unlocked the bootloader the second I bought the phone, decided to root now, so no wipe was involved (this is why I can compare with no root boot times). No custom rom installed. Stock rom, rooted and bootloader locked.
What I noticed is that all desktop widgets take 10-15 seconds to load after boot. Widgets are in a blank state for that period of time, like freezing.
Anyone else noticed this ? Is expected to see this after rooting ? Maybe supersu checking entire device after boot and slowing the device ?
Thanks in advance
I also noticed this on stock rom but also on custom rom.
I have to wait before using Power Toggles widget (but not with Poweramp). The same for some apps that should start at boot as Headset Control, Clipper, Tasker, LMT Launcher...
BTW if you used CF Auto Root your BL is unlocked.
Glad I an not the only one seeing this.
I have locked my bootloader after root using bootunlocker. This is why I said bootloader is locked. I would unroot and wipe to see if this is a root problem or not, but I am still not clear if I can backup and restore to EXACT same state I am now (apps, data, settings, widgets, etc.)
LE: apparently slow widgets after boot are caused in my case by sim pin check. If I disable the sim pin check on boot, all widgets load instantly first time after boot. Can anyone else test and confirm ?
Anyone else notice this?
Sent from my SPH-L900 using xda premium
I also noticed this problem, not sure if after root or not, as I rooted my phone immediately. Tested against Nex4 and although Nex5 lock-screen comes up 2 seconds earlier, the Nex4 widgets immediately loads, whereas my Nex5 take 30 seconds for widgets to load.
Ladduro said:
LE: apparently slow widgets after boot are caused in my case by sim pin check. If I disable the sim pin check on boot, all widgets load instantly first time after boot. Can anyone else test and confirm ?
Click to expand...
Click to collapse
Can you explain in more detail where this option is?
Settings > Security > Set Up SIM card lock > Lock SIM card on or off.
Put it to off and try again.
I flashed factory images and the widgets do the same thing, so I dont think it is root related.
I have the same problem
The widgets were running perfectly when the Nexus 5 was stock (unrooted, locked, stock rom). As soon as I unlocked, rooted but stock rom still, the widgets were slow to load -- 30 seconds. I then insalled DroidKang, and still -- Widgets are slow to load;
I did not, however, check if putting in ART runtime has anything to do with it (it could as I did this after unrooting my phone.)
Anybody has ideas ?
(I have tried to lock/unlock SIM card, and still same effect)
I also have this issue and I've never used a pin code on my device , It was working perfectly fine before I rooted it :crying:
Hi
Recently I've unlocked my Z5's bootloader and rooted it.
I installed Paranoid android from the thread in the forum, everything was working fine, even the fingerprint sensor was working quite ok.
after a day I wanted to switch the locking option. so i wouldn't use the fingerprint, and only swipe to unlock the phone.
After i changed the settings the app crashed (it changed successfully to swipe instead of using fingerprint)
Now the result is that every time I try to change this specific setting (Screen Lock) the app asks me for my pin, I type it and the settings app crash.
I tried to restart, Clean cheche and uninstalling some google apps. nothing helps
Thank you for the help! :angel:
RomSeeker said:
Hi
Recently I've unlocked my Z5's bootloader and rooted it.
I installed Paranoid android from the thread in the forum, everything was working fine, even the fingerprint sensor was working quite ok.
after a day I wanted to switch the locking option. so i wouldn't use the fingerprint, and only swipe to unlock the phone.
After i changed the settings the app crashed (it changed successfully to swipe instead of using fingerprint)
Now the result is that every time I try to change this specific setting (Screen Lock) the app asks me for my pin, I type it and the settings app crash.
I tried to restart, Clean cheche and uninstalling some google apps. nothing helps
Thank you for the help! :angel:
Click to expand...
Click to collapse
Probably its something from Rom which yoi installed and beacuse that happends.
Solution to try stock based custom rom or back to stock official.
Sent from my D6503
Allek84 said:
Probably its something from Rom which yoi installed and beacuse that happends.
Solution to try stock based custom rom or back to stock official.
Sent from my D6503
Click to expand...
Click to collapse
So obviously it happened because I am no longer stock, But as my experience goes, I know people may have stumbled upon the same problem in their past, and maybe know a solution that will work for me.
I do not want to go back to stock, Because Sony's Stock is ****, serious **** full for bloatware that you cannot remove and battery life that makes you cry.
Your message was not helpful, but thanks for trying
It most likely is a problem with the ROM installed on your device, as you already performed wipes and the problem persists. Try reporting the problem to the rom dev or if its that important, try a different rom for now
Good luck
Hi, I hope you guys can help. I have an OPO which is on Android 8 as per this link and it was all working fine (well, it's a bit buggy in places, but I can live with it!).
I have TWRP installed (3.2.3.0), and had no problems with it, was easy to access and install/backup with it; I have reasonably recent backups too (but wait for it....), and phone is rooted using Magisk.
Anyway, in a recent bout of paranoia, I encrypted my phone. It's a long story, but the company I work for recently employed an IT company to manage its systems and I didn't want them poking about where they shouldn't (they are not particularly good).
The encryption worked straight away, and clearly functions as it should; rebooting the phone requires a pattern unlock, and the phone is clearly marked as encrypted.
HOWEVER when I went to try and get into TWRP, I was faced with the same pattern unlock request - I tried it, and my pattern doesn't work. I have seen suggestions about disabling screen lock, or changing it to a PIN, but this doesn't affect the pattern unlock on TWRP. I reckon I can probably access the backups when unlocked via PC file transfer, so presumably can flash these via ADB, but I'm a bit loathe to in case something horrible happens.
So, is there a solution? do I:
try and reflash TWRP/different version of TWRP
flash the backup?
try and decrypt the phone
cry?
with regards decrypting, I can't see any way of reversing the encryption one it has happened - kinda wish I'd known that before I'd done it.
Help would be greatly appreciated. It isn't a major problem, phones working, it's just my modding is kinda curtailed....
Would this one work?
GitManMatt said:
Hi, I hope you guys can help. I have an OPO which is on Android 8 as per this link and it was all working fine (well, it's a bit buggy in places, but I can live with it!).
I have TWRP installed (3.2.3.0), and had no problems with it, was easy to access and install/backup with it; I have reasonably recent backups too (but wait for it....), and phone is rooted using Magisk.
Anyway, in a recent bout of paranoia, I encrypted my phone. It's a long story, but the company I work for recently employed an IT company to manage its systems and I didn't want them poking about where they shouldn't (they are not particularly good).
The encryption worked straight away, and clearly functions as it should; rebooting the phone requires a pattern unlock, and the phone is clearly marked as encrypted.
HOWEVER when I went to try and get into TWRP, I was faced with the same pattern unlock request - I tried it, and my pattern doesn't work. I have seen suggestions about disabling screen lock, or changing it to a PIN, but this doesn't affect the pattern unlock on TWRP. I reckon I can probably access the backups when unlocked via PC file transfer, so presumably can flash these via ADB, but I'm a bit loathe to in case something horrible happens.
So, is there a solution? do I:
try and reflash TWRP/different version of TWRP
flash the backup?
try and decrypt the phone
cry?
with regards decrypting, I can't see any way of reversing the encryption one it has happened - kinda wish I'd known that before I'd done it.
Help would be greatly appreciated. It isn't a major problem, phones working, it's just my modding is kinda curtailed....
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692
The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136
Taurus_XDA said:
The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136
Click to expand...
Click to collapse
Thanks for this, I'll give it a go now
Working again
Taurus_XDA said:
The developers of LOS have worked in and recommended this version:
https://androidfilehost.com/?fid=1395089523397886136
Click to expand...
Click to collapse
yep, that's awesome, fully up and running now. Just for anyone else experiencing this problem, I downloaded the TWRP version listed above, then flashed it via ADB (unlock USB debugging on your phone, connect it, open a powershell window where you keep your adb files, 'adb reboot bootloader' then 'ffastboot flash recovery [NAME].img' and it will reinstall TWRP with the new version).
Bit of a moment when I rebooted to recovery, as faced with the same decryption unlock window, but this time the decryption worked and was able to access TWRP fully.
Nice one.
Got this second hand google pixel 2 from a seller yesterday while setting up and connected to internet .until I started receiving a notification saying "Device managed by admin - Automatically resetting soon." When I tap on it, it gives me an error saying "Device setup keeps stopping". I checked the phone's IMEI but it doesn't classify as lost/stolen. If I try to factory reset the phone, it asks me for a "@google.com" adress. My question is, should I be worried? Is there any way to fix this?
You basically got a phone from a student who sold it to make some money and this is the property of a school. You could try to flash the whole OS again, but the choice is up to you
i can reflash the OS but i guess , the imei is saved in the portal of the school/company , so when i connect to internet it will again show the same message.
Just try it, maybe it's just a software solution
Ok thanks
Will clear the current image and install factory image
Hi I unlocked the boot loader and download the latest factory image how to clear the current system image from the phone in fastboot?
I forgot the command to wipe the system image.
Ztaker said:
I forgot the command to wipe the system image.
Click to expand...
Click to collapse
Do you solve anything?
Tudor M said:
Do you solve anything?
Click to expand...
Click to collapse
Device managed by admin — Automatically resetting soon — Google Pixel
Different stories from the internet for the same issue.
medium.com
solved it and published the article
I guess the shorter version is to just set it up offline and turn on usb debugging from the settings.
I don't think you even have how to proceed entering the work email by providing a simple gmail.
Anyhow,
This is what I've tried and done and it works great on Android 11 as long as there is no factory restet.
But this does not work on Android 12.
Do you have any solution for that?
Thank you!
Tudor M said:
I guess the shorter version is to just set it up offline and turn on usb debugging from the settings.
I don't think you even have how to proceed entering the work email by providing a simple gmail.
Anyhow,
This is what I've tried and done and it works great on Android 11 as long as there is no factory restet.
But this does not work on Android 12.
Do you have any solution for that?
Thank you!
Click to expand...
Click to collapse
the above solution worked for 11 and 12
normal Gmail account you can add quickly before the phone gives this error. Like within 1 minute after resetting the phone
I also got a pixel 3 XL phone with this issue as it accepted only google.com email and said it was managed by IT Admin, and I got this post and few others on this topic, followed the instructions given with my phone, I got a success on the last window. and my current android version is 12.
sannanthetraveller,I wanted to ask what should be followed now to setup the phone so to avoid this issue coming up again.
and any other suggestions while using the phone, whether to disable anything like auto update check or?
Please let know.
Hi,
I bought an X3 pro with a global rom, but as I really need a call recorder I have installed the xiaomi 12.5.1 rom. I'm really not an expert on phones but somehow I managed to do it. Also for whatever reasons I had the magisk manager installed as well which I have never really wanted to use.
I was pretty happy with the phone when on one day (ironically a day after I have just checked if my phone is rooted) my phone said I can't use NFC payments anymore. So I have decided to try some magic and fix the problem myself. Again, I'm not an expert but as far as I understood I have a problem with safety-net which I have managed to solve by installing magisk and setting up modules as I have seen on youtube.
Now my phone passes the safety-net check and my phone in the play app says its certified but I still can't pay with NFC and some of the banking apps are not working anymore which is pretty bad for me.
So the question I have in escence: how can I really restore my phone to the factory default 12.5.1 eu rom? I mean I dont need TWRP or anything unlocked, I'd just like to be a regular joe without superuser rights.
Thanks a lot for your help.
ps: not sure if that matters, but if I hit the update button or I'd like to perform a factory reset on my phone then it boots into TWRP.
Uninstall Magisk or Use Magiskhide also your Banking app hide it on the Magiskhide and playstore,
Just MiFlash stock ROM.
Thanks for responding. I have tried hiding Magisk, but that didnt help me with my banking apps. Then I have uninstalled it which made things even worse cause some other programs started to complain. As the phone was not rooted anymore (I guess) I thought it can't be anything except the unlocked bootloader so I had the genius idea to type something like 'adb oem lock' which immediately bricked my phone saying 'the system is destroyed'.
I was very lucky that I remembered that xiaomi unlocker tool which opened the bootloader and that magically still worked and my phone booted to TWRP. From there I just installed an EU ROM and now everything works perfectly fine.
So overall I spent about 20h with unlocking, intalling a new ROM, rooting etc and then another 10 with reinstalling the original ROM plus reinstalling my apps again! Kudos to me going back to square one