Hello,
So guys, I have been stuck at this for a while now, it happened when I unlocked bootloader and installed a custom recovery (TWRP) and after that I went ahead wiped the data through recovery. (Reason: I was going to install aroma file manager.) since then I cant boot into OS. Thought maybe I accidentally wiped all the data including OS but then through this link http://forum.xda-developers.com/showthread.php?t=3375203 I reinstalled the rom through that "system.img" he provided although it didn't work, my phone surely isn't bricked cause my pc recognizes it and I can boot into recovery,bootloader,download mode.
I still get stuck at the HTC LOGO.
What might be causing it, please help.
PS: Also TWRP says "No OS Installed", if anyone can find me a rom other than those he provided please do.
Jam3sgotya said:
Hello,
So guys, I have been stuck at this for a while now, it happened when I unlocked bootloader and installed a custom recovery (TWRP) and after that I went ahead wiped the data through recovery. (Reason: I was going to install aroma file manager.) since then I cant boot into OS. Thought maybe I accidentally wiped all the data including OS but then through this link http://forum.xda-developers.com/showthread.php?t=3375203 I reinstalled the rom through that "system.img" he provided although it didn't work, my phone surely isn't bricked cause my pc recognizes it and I can boot into recovery,bootloader,download mode.
I still get stuck at the HTC LOGO.
What might be causing it, please help.
PS: Also TWRP says "No OS Installed", if anyone can find me a rom other than those he provided please do.
Click to expand...
Click to collapse
Ok, so I finally managed to boot into OS but it is Chinese.. zzz and when I slide unlock my screen it gives a weird a message in Chinese and then reboots. Once it gets back into OS same thing again. What now guys?
this should help
http://forum.xda-developers.com/one-x9/development/rom-balla241-e56ml-dtul-2-17-400-1-twrp-t3497861
use this and you shall have you phone fixed
Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?
Hi..
I don't know exactly what's wrong with your mi5..coz you're already told that you almost tried everything..but as long the problems just softbrick i think there's nothing wrong to try this way that might be you don't try it before..
What twrp version you're using it currently..?, is it official or zcx twrp..?, if official..just try switch to zcx version first..you can find and download it from here.
After that with zcx twrp tried check and see that your partition system, data and cache are still as Ext4 file system not F2fs or you can try formatting the data partition (caution!!..this will deleting all your internal storage) to make sure everything is clear, then put it again the rom.zip then flash it again the rom but this time just try it using xiaomi.eu rom, you can try this rom
And anyway..what version XiaomiFlash tool you're using it while flashing official fastboot rom..?
Xiaomi eu dont support f2fs,i have tried it myself,the last thing to do if you already haven't do in is to flash the firmware in edl mode(i prefer to try Chinese devolep first),i think that way the phone is fully wiped and than flashed just like it came out of factory,other than good luck
wolkenjaeger said:
Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?
Click to expand...
Click to collapse
Hey guys, I will try your suggestions. In the meantime, I attached the dmesg log - it shows the kernel booting. Maybe you see something. It would be cool, if you can upload a dmesg log as well so I can compare or check if you can see anything.
Further information:
- I am using MiFlash 2016.08.30.0
- Tried it with the alternative ZCX version AND the xiaomi.eu ROM
- Formatted the data partition as well (I could create a backup of it with TWRP)
- still same situation...
- Is there a way to reset partitions or kind of "deep flash" the device?
wolkenjaeger said:
Further information:
- I am using MiFlash 2016.08.30.0
- Tried it with the alternative ZCX version AND the xiaomi.eu ROM
- Formatted the data partition as well (I could create a backup of it with TWRP)
- still same situation...
- Is there a way to reset partitions or kind of "deep flash" the device?
Click to expand...
Click to collapse
Did you try to flash in EDL mode ?
vlatko98 said:
Did you try to flash in EDL mode ?
Click to expand...
Click to collapse
Yes. No luck either. Then I tried to flash (via normal fastboot mode) an old STABLE China MIUI ROM: miui_MI5_V7.3.2.0.MAACNDD_905c2c8100_6.0.zip -> resulted in boot -> black screen. Now I can go into either fastboot nor recovery
wolkenjaeger said:
Yes. No luck either. Then I tried to flash (via normal fastboot mode) an old STABLE China MIUI ROM: miui_MI5_V7.3.2.0.MAACNDD_905c2c8100_6.0.zip -> resulted in boot -> black screen. Now I can go into either fastboot nor recovery
Click to expand...
Click to collapse
Idk what to tell you else than to search miui forum and hope for the best
wolkenjaeger said:
Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?
Click to expand...
Click to collapse
Have you got it fix yet ?
Nope. Next step is to try EDL again.
Gesendet von meinem MI 5s mit Tapatalk
wolkenjaeger said:
Nope. Next step is to try EDL again.
Gesendet von meinem MI 5s mit Tapatalk
Click to expand...
Click to collapse
Hav you got it fixed ??? Even i am facing the same issue.
please do let us know if you have fixed it.
Im using mi5 64gb
Exactly the same problem: " (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...)"
But this has happened after serious damage (car rolled over the phone) and I replaced the screen with new one. So I guess some hardware might be damaged. Flashing ROM's didn't help.
I couldn't find any solution so far
After screen replace , you got it working ?
I can't get into recovery also.
I tried many twrp versions , i can see the twrp screen but then it get stuck and phone restarts to go back to that mi logo bootloop.
I did flashed many Chinese and global ROMs via flashboot and miflash tool but all the same.
I'm so doomed...
My phone has no history of any fall or anything ..
I wonder what happened all of a sudden.
Thanks for the reply
wolkenjaeger said:
Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?
Click to expand...
Click to collapse
Okay, have you tried Mi Flash with deep flash cable ? Flash it again with deep flash cable or go to any reseller shop. They have deep flash cable. Ask them to flash it again. It'd cost you upto $10.
I retried yesterday - no success.
I flashed both stable versions: Global and Chinese, but after flashing, I again had the same problem: bootloop. I stop wasting time, until someone knows the problem. I personally think it's a problem with the hardware, as when you see the log, which I posted above (kernel log of TWRP), there are quite a lot of "errors" in it.
Any other idea?
I asked an android expert who worked in mi about it ...
He was almost sure that either battery or the motherboard is faulty.
He thinks the motherboard is of more chance for the issue.
Bummer..... then I have to wait until I get back to Hong Kong to repair (bought it there). Thanks for the update @bilalsmu.
wolkenjaeger said:
Bummer..... then I have to wait until I get back to Hong Kong to repair (bought it there). Thanks for the update @bilalsmu.
Click to expand...
Click to collapse
Your welcome...
Can you just try flashing with mi flash tool with the option 'clean all and lock'
I just tried mine, and now android is loading *fingers crossed*
Will update if it did complete..
Okay, can you tell me which MiFlash version you have been using (and which ROM?)
I am sorry brother.
Android booted up,I could log into my accounts and I left the phone for charge while it was syncing the accounts ..
When I am back after half an hour , bootloop had already started
I used miflashtool 2016 and miui 8.2.1 official global rom
Hi, I'm having troubles with a Mi 5 of my friend. Here's what I have tried:
The bootloader is unlocked. (When I power it on, it clearly says "Unlocked")
I tried restoring via fastboot with MIUI V10.2.2.0 > Everything went great, I did not get any kind of errors, but the smartphone never booted up, it stuck at Mi boot animation and didn't reboot, just booting up forever.
I tried installng TWRP 3.3.0 > Installed LineageOS 16.0-20190425-nightly > Got no error and it still didn't boot up. (same thing, the boot animation loading forever and no reboot.)
Any idea what am I missing?
chequehox said:
Hi, I'm having troubles with a Mi 5 of my friend. Here's what I have tried:
The bootloader is unlocked. (When I power it on, it clearly says "Unlocked")
I tried restoring via fastboot with MIUI V10.2.2.0 > Everything went great, I did not get any kind of errors, but the smartphone never booted up, it stuck at Mi boot animation and didn't reboot, just booting up forever.
I tried installng TWRP 3.3.0 > Installed LineageOS 16.0-20190425-nightly > Got no error and it still didn't boot up. (same thing, the boot animation loading forever and no reboot.)
Any idea what am I missing?
Click to expand...
Click to collapse
TWRP 3.3.0 ?? Mi5 latest is 3.2.3
4719 said:
TWRP 3.3.0 ?? Mi5 latest is 3.2.3
Click to expand...
Click to collapse
I'm sorry, 3.2.3, of course, but honestly it makes no difference.
Hi there!
I'm stuck in a bootloop with dm verity error message. Phone turns off and on continiously. I'm not able to get into recovery / fastboot using button combo :\.
How I got into this:
I tried unlocking my merlinx, but ... didn't want to wait 7 days with the official tool. So I used https://github.com/bkerler/mtkclient and did the "unlock bootloader" procedure. Phone booted fine, though there was dm verity error message and I had to press the power button to continue booting.
Then I followed this guide: https://forum.xda-developers.com/t/...roid-for-redmi-note-9-merlin-merlinx.4333179/
Then, I downloaded shrp recovery, crDroid rom, gapps and firmware. Booted in fastboot, did `fastboot flash recovery shrp.img` and booted to recovery. Then I took backup of IMEI, wiped the data and saw an interesting builtin zip for dm verity disabling. Flashed that, then proceeded with custom rom installation. All went smooth.
I booted the rom. There was no dm verity message, nor Redmi logo, but phone booted normally. If I remember correctly, I didn't have to press the power button to continue (there was no message about it.)
Proceeded with phone setup. Camera didn't work ... Tried rebooting, once again no Redmi logo but phone boots fine. "Ok then, I'll try a different ROM and hopefully camera works". I choose "advanced restart -> recovery" and phone turned off. Screen turned on (like you'd expect) but then turned off again. Again, no Redmi logo or dm verity message.
And now the phone does that. Screen turns on and off after ~30 seconds.
My first thought was that bootloader got locked again somehow. Using the mtkclient tool, linked above, I relocked and unlocked the bootloader.
There's still no Redmi logo present, though I can see the dm verity message again.
What have I done wrong? I know it could be the impatience with 7 day waiting, but since phone booted fine 2 times ..? Was it the recovery dm verity zip?
Does anyone know what to do here? I'm able to use mtkclient tool. Button combos for recovery and fastboot seem unresponsive ...
Thank you very much.
Hello.
I did exactly same think with my Redmi Note 9 and I can say you hard bricked your phone. But don't worry there is a way to solve it. You need to follow vagelis199's guide exactly and there should be no worries. It is not so easy but not so hard too.
Sending this from my Redmi Note 9 with android 12 R vendor.
I'm not so knowledgeable about this part of tech but crDroid guide is outdated in my opinion and it should be replaced with new one, that is a big problem and should be considered. I installed Android 12 S vendor, most recent one from my android 11 MIUI and it bootlooped, after installing with Firmware of Global MIUI it was hardbricked. So I am waiting a little and trying to install most resent crDroid with EU MIUI Firmware which very recently was published with MIUI 13 Android 12 EU. I am not sure why it didn't work because EU and Global are very similar.
Thank you, will try that.