Related
Hello Guys!
First of all I would like to thank every developer on xda for their hard work on developments.
I got atrix 4g about 3 weeks ago it was a korean version of SKTelecom. I wanted to remove the korean keyboard and stock apps so i decieded to unlock its bootloader and flash a custom rom. I used the international users sbf file to unlock its bootloader by using rsd lite. When i started the process rsd gave an error failed and my phone was stuck at a black screen. When i pull out the battery and rebooted it gave an error 1.3.8 something like that so i pulled out the battery and hold volume up button and the power it said starting fastboot so i unlocked the bootloader. Then the phone was booted up and there was no signal no 2g 3g data was working when i checked the imei of phone it said unknown and the phone keeps on rebooting no mateer how many services i stopped. So i decieded to flash a new rom and i installed a recovery i sucessfully installed neutrino rom but same problems appeared no data connection no imei phone keep on rebooting after 4 to 5 minuted. Now phone is at airplane mode while the wifi and bluetooth still works . Plz guys help me fix this problem.
Tried Global/China Stable/Developer fastboot roms but always stuck at 50%, it has been months since got permissions. So unlocked unofficially flashed custom roms but if i enter airplane mode then exit it i didnt get signal till i reboot, Found out cm13radios.zip flashing it solved airplane issue but now data connection keeps dissconnecting and reconnecting automatically. Miui has aux problem cant play songs using aux cable, even after i dissconnecting cable it still shows headphone icon in status bar -_-
People saying they got volte working in quallcomm aosp 6 rom but i didnt know how..
is there any way to use this device normally ?
Manu11 said:
Tried Global/China Stable/Developer fastboot roms but always stuck at 50%, it has been months since got permissions. So unlocked unofficially flashed custom roms but if i enter airplane mode then exit it i didnt get signal till i reboot, Found out cm13radios.zip flashing it solved airplane issue but now data connection keeps dissconnecting and reconnecting automatically. Miui has aux problem cant play songs using aux cable, even after i dissconnecting cable it still shows headphone icon in status bar -_-
People saying they got volte working in quallcomm aosp 6 rom but i didnt know how..
is there any way to use this device normally ?
Click to expand...
Click to collapse
Why use unofficial unlock?
Manu11 said:
Tried Global/China Stable/Developer fastboot roms but always stuck at 50%, it has been months since got permissions. So unlocked unofficially flashed custom roms but if i enter airplane mode then exit it i didnt get signal till i reboot, Found out cm13radios.zip flashing it solved airplane issue but now data connection keeps dissconnecting and reconnecting automatically. Miui has aux problem cant play songs using aux cable, even after i dissconnecting cable it still shows headphone icon in status bar -_-
People saying they got volte working in quallcomm aosp 6 rom but i didnt know how..
is there any way to use this device normally ?
Click to expand...
Click to collapse
Let me tell you. Go to " https://i.mi.com/ " first and log in with your mi account and see if it can find your phone. I was facing the same issue of getting stuck at 50% while unlocking and I tried this yesterday. From the site, a sms was sent to the registered phone number to verify device. After verification, I tried unlocking officially and it got unlocked!
Debanka said:
Let me tell you. Go to " https://i.mi.com/ " first and log in with your mi account and see if it can find your phone. I was facing the same issue of getting stuck at 50% while unlocking and I tried this yesterday. From the site, a sms was sent to the registered phone number to verify device. After verification, I tried unlocking officially and it got unlocked!
Click to expand...
Click to collapse
I tried everyting, this miui is **** as always
even tried with other account. in i.miui.com device is online and i can locate it
still stuck at 50%
Manu11 said:
I tried everyting, this miui is **** as always
even tried with other account. in i.miui.com device is online and i can locate it
still stuck at 50%
Click to expand...
Click to collapse
Sorry to hear that. It worked for me, I thought it might work for you too.
Sent from my Redmi Note 3 using Tapatalk
Try login mi account that you use for unlock, go to i.mi.com then find device, after your phone find than logout mi account from your device and go to fastboot, connect to PC try unlock with miunlock I hope this work
1yang said:
Try login mi account that you use for unlock, go to i.mi.com then find device, after your phone find than logout mi account from your device and go to fastboot, connect to PC try unlock with miunlock I hope this work
Click to expand...
Click to collapse
Can I try unlocking with beta Rom. I had permission months back. Now I'm in latest beta Rom. RN3SD.
Manu11 said:
I tried everyting, this miui is **** as always
even tried with other account. in i.miui.com device is online and i can locate it
still stuck at 50%
Click to expand...
Click to collapse
Sent from my Redmi Note 3 using XDA-Developers mobile app
mathi68 said:
Can I try unlocking with beta Rom. I had permission months back. Now I'm in latest beta Rom. RN3SD.
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Recommend dev rom/ beta rom and yes you can use your permission months back
I've unlocked the phone but of no use. Can't switch Rom, fast boot and recovery reboot are same as locked. Horrible. What's the use of unlocking with permission and so on?
Sent from my Redmi Note 3 using XDA-Developers mobile app
What is the exact and complete error message when you attempt the unlocking process?
If you put your phone into flashboot mode and use ADB, do you get anything from the command "Fastboot devices"?
If you're getting "Account is different from the one on the device" then it's an account issue and can be solved on the i.mi website by making sure you only have one phone assigned to your account.
Y'all can check my post. Also follow the thread and you might get unlocked.
Hello
I have a problem with my RN3 SE (yes I'm sure it's SE, model "2015161" and 152mm). It all started when I uploaded the Mi-mipip rom to my phone. Initially, I uploaded Kenzo (I was convinced that I have this model) but there were symptoms that were typically associated with inappropriate rom. Initially, I did not have IMEI (no range, wi-fi etc) and constantly popping "camera error" - "can not be connected to the camera", when I was able to recover the imei, Wi-Fi returned, but unfortunately there was still a problem with the lack of range and the camera did not work . Reading many threads, it occurred to me that I uploaded a bad rom. I decided to install the appropriate rom Kate (edl mode by miflash) unfortunately when the phone turned on, only the MI logos and the loading (leaping) dots of the android were displayed (I waited over 2-3 hours and to no avail). Out of curiosity, I uploaded rom from kezno in the same way and the phone immediately woke up to life but still without range and the camera was not working. I solved the problem with the range by replacing the modem with Kate, but I still have a problem with the camera. Trying to repair the mistake I tried to upload rom miuipolska under Kate via TWRP, however, the installation stopped at 99% and did not move for over an hour so that the phone could come alive and I had to flash it again with the Kenzo room with the switched range modem. Do you have any ideas how I could deal with it?
** Warning For Those Using Latest Global Beta's 10.x.x **
Problem I Encountered:
After this morning's update to the Weekly Global ROM 8.12.13 (through stock software updater), the update went just fine and i was using my phone most of the day. As you all know i have a China phone (no root, factory recovery) with the Global ROM (bootloader unlocked always). I decided to reboot the phone later on that day, it took forever to restart, and eventually restarted with the TOUCHSCREEN not working! I mean -like it was DEAD. I loaded up TWRP in fastboot, still was dead in recovery (and took forever to boot to). I factory reset (god i hated to do that), it was still dead! I downloaded the fastboot ROM from 8.12.7 beta and flashed all the partitions.... IT WAS STILL DEAD. I fastboot flashed the 10.0.2 Stable ROM... STILL DEAD. I even plugged in a USB-C dongle from Samsung to use my logitec wireless keyboard and mouse on my phone (which worked well) and setup to enter the CIT mode for diagnostics. There was no touch screen function / logging period. Bad news, i figured my Digitizer just went bad. I was converting my backup phone (old LG G2) to use, and also figured i'd put my Mi8 back to China Factory 9.6.7 (no rollback isn't enabled yet) before locking the bootloader back and getting it RMA'd. When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either.
Conclusion:
They (Xiaomi) have something totally F***ed up in their new betas that randomly screws up firmware for the touchscreen. I'm still going to use them (i know ) because they are so much better now than before.
Soooo Many Xiaomi Questions:
What if my bootloader was locked and i couldn't have flashed back to the old MIUI ROM?
What if the Anti-Rollback actually WAS enabled and i couldn't have flashed back to the old MIUI ROM?
What the he** is in China 9.6.7 that fixed the issue that Global 10.x.x couldn't have? And WHY?
* At least we all have a solution for now..... But i hope that bug doesn't show up for anyone else....
Solution:
1.) Set you phone to Fastboot Mode (Reboot and hold down the volume-down button and power button)
2.) Connect your phone to your computer
3.) With your previously downloaded Fastboot image file of V9.6.7 China ROM, enter your choice of command
-- The command with "Flash all partitions" is recommended. ** Do Not Choose To Re-Lock Bootloader **
4.) When it finishes and reboots, your touchscreen will be functional again!
/.
boot your phone and use mouse using otg.
and try to use camera den try to vibrate...
if working... i think that is digitizer if not...
u need to flash the one partition for sensor ?
Bull****.
Sigray said:
Bull****.
Click to expand...
Click to collapse
Obviously this.
OP somehow managed to delete parts of the persist partition..or some freak accident or defective device.
I had the same experience. My device is global version, but I imported it and since I don't have un authorisation Mi store to rely on I just flashed oreo based rom with mi flash tool without knowing if ARB will trigger because I had nothing to lose. The digitizer turned on and out of curiosity I flashed 8.12.13 with the flash tool. It is working fine but for now I won't trust the updater app.
Sent from my MI 8 using XDA-Developers Legacy app
@Agimax Can confirm the issue. Faced the same problem. Followed your procedure and everything is up and running. I wonder what Xiaomi screwed up this time. Thanks a ton for the guide, was really worried for a while!
Mhm...wouldn't have thought.
Possibly something going wrong with Oreo>Pie upgrade on china devices running global roms ?
9.6.7 was the last stable release one can downgrade to on global devices and use to upgrade to pie based global beta.
I really wonder what is missing in Pie vs Oreo that the digitizer needs. I'm just worried in the future when anti-rollback is truly enabled we won't have a way to fix the issue until we find the missing/corrupted driver or file problem. Pie flashed from fastboot with all partitions should fix any issue, with files -but doesn't. That's a real problem and means they omitted something critical.
Touch Screen out of use!
Touch Screen out of use!
Same thing happened to me too. Simply after a reboot, as if the phone was initialized after the first installation (very strange) and just started, the touch no longer works.
Version Rom 8.12.13 Weekly
Agimax said:
** Warning For Those Using Latest Global Beta's 10.x.x **
Problem
After this morning's update to the Weekly Global ROM 8.12.13 (through stock software updater), the update went just fine and i was using my phone most of the day. As you all know i have a China phone (no root, factory recovery) with the Global ROM (bootloader unlocked always). I decided to reboot the phone later on that day, it took forever to restart, and eventually restarted with the TOUCHSCREEN not working! I mean -like it was DEAD. I loaded up TWRP in fastboot, still was dead in recovery (and took forever to boot to). I factory reset (god i hated to do that), it was still dead! I downloaded the fastboot ROM from 8.12.7 beta and flashed all the partitions.... IT WAS STILL DEAD. I fastboot flashed the 10.0.2 Stable ROM... STILL DEAD. I even plugged in a USB-C dongle from Samsung to use my logitec wireless keyboard and mouse on my phone (which worked well) and setup to enter the CIT mode for diagnostics. There was no touch screen function / logging period. Bad news, i figured my Digitizer just went bad. I was converting my backup phone (old LG G2) to use, and also figured i'd put my Mi8 back to China Factory 9.6.7 (no rollback isn't enabled yet) before locking the bootloader back and getting it RMA'd. When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either.
Conclusion:
They (Xiaomi) have something totally F***ed up in their new betas. I'm still going to use them (i know ) because they are so much better now than before.
Soooo Many Xiaomi Questions:
What if my bootloader was locked and i couldn't have flashed back to the old MIUI ROM?
What if the Anti-Rollback actually WAS enabled and i couldn't have flashed back to the old MIUI ROM?
What the he** is in 9.6.7 that fixed the issue that 10.x.x couldn't have? And WHY?
* At least we all have a solution for now..... But i hope that bug doesn't show up for anyone else....
Click to expand...
Click to collapse
I had same problem, from version xiaomi.eu 8.12.13...
This manual from Agimax is excellent !!! Helped me.
Many thanks.
@Agimax
hello, I have the same problem, I was in the Xiaomi eu version 8.12.7 and all good, update to version 8.12.13 and it was all good, restart the mobile and the touch stopped working, everything you mention makes, go down to another beta version, in twrp it does not work either and just take the mouse. You can tell me how to do the process, he was in the stable global version 10.0.3.0 (oeamifh) how he made this installation, it is not clear to me the antirollback, I only have the bootloader unlocked and a backup of that version through TWRP, but I'm afraid that going back to Oreo while standing generates a brick. Please your help indicating me step by step and things to keep in mind
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
Which Manual?
Which Manual? Can you post a link?
Luko69 said:
I had same problem, from version xiaomi.eu 8.12.13...
This manual from Agimax is excellent !!! Helped me.
Many thanks.
Click to expand...
Click to collapse
1MaxMar1 said:
Which Manual? Can you post a link?
Click to expand...
Click to collapse
If you read the whole paragraph of my issue, i explained the downgrade on my China phone to 9.6.7 with the Fastboot mode ROM method worked when the others didn't:
So download the china ROM 9.6.7, reboot to fastboot mode, flash the rom from your computer in fastboot, then reboot.
From OP:
"When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either."
Agimax said:
If you read the whole paragraph of my issue, i explained the downgrade on my China phone to 9.6.7 with the Fastboot mode ROM method worked when the others didn't:
So download the china ROM 9.6.7, reboot to fastboot mode, flash the rom from your computer in fastboot, then reboot.
From OP:
"When the fastboot ROM flash of 9.6.7 (Oreo) finished and rebooted, to my amazement, my digitizer / screen is fully functional again! No more super slow booting either."
Click to expand...
Click to collapse
hello, any recommendation to rollback, according to what you say the rollback protection is not active, but I do not want to take any other surprise, I have the 8.12.13 eu! regards
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
I had also 8.12.13 xiaomi.eu, (now 8.12.20), no problem with rollback after downgrade to china 9.6.7
@Agimax
hello sorry but I'm somewhat desperate, my team is global version, I'm in Xiaomi eu 8.12.13 which version I install to recover my touch ??? The truth is I'm afraid of a brick because of that antirollback !! I hope you can help me!
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
Reading is hard
Stoffl_ said:
Reading is hard
Click to expand...
Click to collapse
Sometimes i wonder why i maintain all these threads to help users......
For some reason it's especially bad with xiaomi devices. The miui forums are horrendous.
Maybe it's the user base, they are are mostly sold in Asia and India..
Agimax said:
Sometimes i wonder why i maintain all these threads to help users......
Click to expand...
Click to collapse
In my case I have read the post several times, only that I have some doubts and the truth is that I am new to the Xiaomi scene.
* I must install the Chinese version if or if or also can the global one?
* Should it be Fastboot if or if or MiFlash?
* I must install something else to avoid brick by downgrade or something from the antirollback since as you say it is not activated, it is for all devices.
I hope you understand me and before I thank you for your help, since I am desperate because I thought I would lose my cell phone.
Enviado desde mi HUAWEI NXT-AL10 mediante Tapatalk
Just few days after installing miui 12, got this problem. The phone is stuck on a boot loop. If I pattern unlock the phone, I get a toast saying "find device stopped unexpectedly". Unfortunately, I don't have a backup. :crying:
Is there any way to save my phone? or may be get a backup?
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
josinpaul said:
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
Click to expand...
Click to collapse
yeah, I am also in the same track but I am unable to make MiFlash Unlock tool to recognize my phone in fastboot mode. Adb does recognize, Mi PC Suite recognizes it but says phone software has to be updated. (Using latest MIUI 12).
Any help is much appreciated. Thanks.
Dhamo200694 said:
yeah, I am also in the same track but I am unable to make MiFlash Unlock tool to recognize my phone in fastboot mode. Adb does recognize, Mi PC Suite recognizes it but says phone software has to be updated. (Using latest MIUI 12).
Any help is much appreciated. Thanks.
Click to expand...
Click to collapse
Use an Intel pc. Amd has issues with mi flash unlock too l. Run as admin. Turn off all anti virus/ firewall applications.
Having the exact same issue on my POCO F1, recently updated to MIUI 12. It was working pretty well up until 10 mins ago.
Battery went under 5% and the device went into ultra power saving mode, then restarted. Now every time I unlock the pattern, the toast pops up "Find my device..." and it goes into bootloop.
Now there isn't even a pop up, device immediately goes into bootloop.
bro, i just now facing this.. can you help me out
Well, MIUI 12 is not going good in poco F1.
If anyone who has not updated to MIUI 12, don't update the phone. Currently there are many bugs in the update
Long story short -
Some are unable to boot up the phone, some stuck in bootloop, some unable to use their passwords, some unable to set up new password, Second space not working, etc etc ...
I also updated to MIUI 12 and was unaware of the bugs.
But the device booted up and password (both fingerprint and face unlock) was working fine but I was unable to change it. Second space was working too. So I was happy that there is not much issue.
But then come the buggy part.
I started playing COD m after update and battery drained like hell 100 to 30 in 1.5 hour. I was shocked by this.
After charging I started to play again but this time (with battery issue) screen freezing happened and then happened at regular intervals. So the gaming experience on MIUI 12 was ruined.
Then I just find MIUI 9 for it and flashed it. (Ya, factory reset in this process too ?) But it is working fine now. Got fast charging module and custom thermal for gaming and it worked.
Currently no issue at all.
But I am still finding a custom kernel for poco F1 to overclock cpu and GPU (not able to find any till now).
Nearly every kernel is ment for MIUI 11 and 10 only. So I am digging deep for now to find a kernel for MIUI 9.
At last just one message - Don't update untill mi release a stable and bug free MIUI 12 version.
If MIUI 12 is working fine on your poco F1, either you are lucky or you have not encountered a bug till yet.
Without data loss, is this method come back to normal as before for poco f1 mobile?
Without data loss, is this method come back to normal as before for poco f1 mobile?
josinpaul said:
I too experienced the same bug, i went to the official service centre to fix the issue. They reflashed the os but the same issue kept arising again and again after a day or two, the service center guys had no clue what's going on. At last I decided to unlock the bootloader and flash a custom rom. Now am using RR without any issue.
Click to expand...
Click to collapse
MIUI keeps on restarting in poco f1..
Without data loss, is this method come back to normal as before for poco f1 mobile?
arulprakash2000 said:
MIUI keeps on restarting in poco f1..
Without data loss, is this method come back to normal as before for poco f1 mobile?
Click to expand...
Click to collapse
If you don't want to loose your data, try flashing the rom using mi flash tool. But nothing can guarantee data security. You should back up your data regularly, waiting for a mishap or trusting on a single electronic device is just foolish, do make multiple copies of important data, if you want it to be secure.
I also have this problem. Updated my POCO F1 to miui 12 and it is in bootloop all the time. The bootloader is locked but I cannot unlock it now with no access to the device. How can I flash again a lower version?
If I don't mind losing the data how can I go back to previous version?
No brother, I encountered the same issues you mentioned. I stuck with MIUI logo loop after that I did a hard reset to mobile phone working condition.