Related
My Redmi 3 IDO is stuck at the startup, system process failed ;(
Sometimes it starts up after +-2 hours... today it started, I immediately went to factory reset, but nothing happened when I pushed the button...
Then I tried to install TRWP & Kingroot to root my device, but this process hangs too, I immediately get into the lock screen and touch screen doesn't work.
I had put some roms, TRWP on my SD Card to flash asap, but I cannot get to flash...
Then I installed MiPCSuite (adb drivers installed on pc), but no device found.
I also installed XiaMiFlash on my pc and tried to flash a TRWP or Rom from there, but immediately fail.
I guess that original bootloader from Xiaomi is protected or something.
How can I get over this, so that I can install a new bootloader from where I can flash customised roms ?
Don't know what to do now, flash from pc,...
Touchscreen doesn't work, it starts up in lock screen and the light goes out faster than usual.
Today it booted up once, I had turned of the lock screen, but now it is on again...
I can only put my phone in download or recover mode with that built in Chinese bootloader, but don't know if I can do something from there.
I also tried to boot without SD/Sim card so that i'm sure that nothing blocks it, but this didn't help.
I guess I used too much apps & cleaners....
Maybe i'm lucky and it will boot after 2-3 hrs, but still when i'm in my device, nothing seems to work, this really sucks
Letting the battery run out and wait a few days to turn it on won't help probably...
Theres a lot of factors to determine in this case, first of all, is it a Snapdragon model (kate/kenzo) or a Mediatek(henessy)?, what version of MIUI are you using?, and most importantly, what did you do to get the phone in that state?
But in your case the most reasonable solution is put the phone on EDL mode and flash it using MIFlash, that software is used only for flashing an original MIUI Rom, you cant install TWRP or any other rom.
Yes it's a snapdragon (also tested it with an app), it's the IDO version (Redmi Note 3 international version).
The Miui is still the original version 7.
Actually I didn't nothing special that the phone got in that state, I think I just installed too many apps which resulted in a conflict that the proces system doesn't react and hangs at startup.
It's also strange that fastboot mode does nothing, it just shows the animated figures...
I will bootup in EDL download mode and try to flash the stock rom, the only thing is that I don't know which one.
My version is the IDO version, it's not in this list, I'll try the Kenzo.
http://en.miui.com/a-234.html
Cannot receive hello packet error and it stops flashing... strange
Innovator said:
Yes it's a snapdragon (also tested it with an app), it's the IDO version (Redmi Note 3 international version).
The Miui is still the original version 7.
Actually I didn't nothing special that the phone got in that state, I think I just installed too many apps which resulted in a conflict that the proces system doesn't react and hangs at startup.
It's also strange that fastboot mode does nothing, it just shows the animated figures...
I will bootup in EDL download mode and try to flash the stock rom, the only thing is that I don't know which one.
My version is the IDO version, it's not in this list, I'll try the Kenzo.
http://en.miui.com/a-234.html
Cannot receive hello packet error and it stops flashing... strange
Click to expand...
Click to collapse
your phone is redmi 3 not redmi note 3...do not flash with redmi note 3 firmware
Innovator said:
Yes it's a snapdragon (also tested it with an app), it's the IDO version (Redmi Note 3 international version).
The Miui is still the original version 7.
Actually I didn't nothing special that the phone got in that state, I think I just installed too many apps which resulted in a conflict that the proces system doesn't react and hangs at startup.
It's also strange that fastboot mode does nothing, it just shows the animated figures...
I will bootup in EDL download mode and try to flash the stock rom, the only thing is that I don't know which one.
My version is the IDO version, it's not in this list, I'll try the Kenzo.
http://en.miui.com/a-234.html
Cannot receive hello packet error and it stops flashing... strange
Click to expand...
Click to collapse
Kenzo is codename for Redmi Note 3 and Kate is for Redmi Note 3 Special Edition (International version). Ido codename is for Redmi 3 (http://en.miui.com/download-298.html). Here is URL to Redmi 3's forum: https://forum.xda-developers.com/redmi-3
Thanks, it wasn't necessary anymore, while driving from work and waiting a few hours it suddenly started up and I quickly reseted to factory settings
ExEdd said:
Kenzo is codename for Redmi Note 3 and Kate is for Redmi Note 3 Special Edition (International version). Ido codename is for Redmi 3 (http://en.miui.com/download-298.html). Here is URL to Redmi 3's forum: https://forum.xda-developers.com/redmi-3
Click to expand...
Click to collapse
Recently I decided to install Cardinal Aosp on my Redmi Note 4 (SD) with TWRP. But when the system starts after the boot, a message appears that the Bluetooth stopped working and after a few seconds the smartphone restarts and stays in that cycle.
Can someone help me? I have already tried to install the AICP, Pixel Experience, Cardinal, download the files twice, change the version of TWRP. But nothing to fix the problem.
Sorry about my English.
Try another custom room
alwan_afif said:
Try another custom room
Click to expand...
Click to collapse
I decided to go back to the miui with fastboot, through the official website. But the same problem continues, the system starts and in the initial steps to set up google account and personal data, it restarts. It reconnects, starts the system and restarts, and it remains so infinitely. Can it be a hardware problem?
Have you try custom room based on Lineage OS? If after install Bluetooth still not working it's possible hardware problem
alwan_afif said:
Have you try custom room based on Lineage OS? If after install Bluetooth still not working it's possible hardware problem
Click to expand...
Click to collapse
No, but I have already tried to flash MIUI via fastboot in EDL mode and it remains the same. The device insists on restarting for whatever I do.
Until yesterday I had the MIUI ROM for my Redmi Note 4, however I wanted to send another two ROMS (Lineage and Resurrection Remix) to see if they would convince me.
(I clarify that I already knew the process to install Roms).
So I rebooted in Recovery mode, hize / wipe and then install Lineague, but automatically I realized that I was making an error, saying that the rom was for Mido and that my cell phone instead of mido was, literally, a point.
So I turned on the pc, use the xiaomiMiFlash tool to install a miui rom (of course, with the option of clean_all) and unpleasantly I was surprised that it restarted every 20 or 30 sec., Please I need help, because I've tried other roms and it's still the same, turn it on, exit the start menu and after a few seconds it restarts. Tell me what I can do.
What does this mean - "my cell phone instead of mido was, literally, a point"? What cellphone do you have?
rossarnie said:
What does this mean - "my cell phone instead of mido was, literally, a point"? What cellphone do you have?
Click to expand...
Click to collapse
I have a Redmi Note 4(Mido, the version with a Qualcomm CPU) and this restarts every 30 sec, I've even used MiFlash to flash the rom with the option to clean everything and even so it remains the same.
I already try with this guide: https://forum.xda-developers.com/redmi-note-4/how-to/how-to-fix-totally-dead-redmi-note-4-t3746465 and nothing, I get an error of "Sahara" with qfil
Treinor said:
Until yesterday I had the MIUI ROM for my Redmi Note 4, however I wanted to send another two ROMS (Lineage and Resurrection Remix) to see if they would convince me.
(I clarify that I already knew the process to install Roms).
So I rebooted in Recovery mode, hize / wipe and then install Lineague, but automatically I realized that I was making an error, saying that the rom was for Mido and that my cell phone instead of mido was, literally, a point.
So I turned on the pc, use the xiaomiMiFlash tool to install a miui rom (of course, with the option of clean_all) and unpleasantly I was surprised that it restarted every 20 or 30 sec., Please I need help, because I've tried other roms and it's still the same, turn it on, exit the start menu and after a few seconds it restarts. Tell me what I can do.
Click to expand...
Click to collapse
I guess you flashed a treble ROM using a non treble recovery. Use this recovery and try to flash lineage OS again.
https://drive.google.com/a/my.smccd.edu/uc?id=1I_EaHHPWERIaMyBasfGJldugLjadU13P&export=download
** 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
Hi
Today after installing the update to xiaomi.eu rom, Android 10, my touch screen just died. I tried flashing 3 various roms by MiFlash with no success. I am able to use fastboot, adb and install TRWP but no matter what I do the touchscreen is dead making the phone useless.
When I boot it up I get asked to unlock it by providing the password to my mi account, which previously worked, but currently I'm unable to use my phone.
Anybody had a similar issue? any way to fix it?
Did you choose clear all option when flashing from fastboot
Yes, with no result unfortunately.
Can you use the touchscreen while in TWRP/recovery mode? If you have a OTG cable you can connect a normal USB mouse to your phone and use that to navigate. Maybe it is just locking up at the password boot stage?
Try to flash it back to stock with stock recovery with a different build date preferably 9 and see if you can wipe it that way......
will try both ideas later today
SOLVED
I finally managed to get it back to life. It turned out that I must have damaged the touch drivers and flashing the phone by fastboot didn't help at all as the drivers are located on prevent partition (as I was told by someone)
So the thing I did was to flash a custom kernel with touch drivers. I used franco kernel kernels.franco-lnx.net. First I installed (using physical mouse) xiaomi eu android 9 rom, than I flashed the franco kernel for android 9. At that point the touch screen came back to life. Afterwards I was able to update to xiaomi eu android 10 rom with no problem.
Hope it can be helpful for anybody with similar problem.