Handset: Xiaomi Redmi 3 Pro.
Steps done:
1. bought on aliexpress with some suspicious bloatware preloaded.
2. was unsure if bootloader is locked, so flashed modified bootloader and TWRP as per this guide: http://en.miui.com/thread-276565-1-1.html
3. flashed latest xiaomi.eu dev build: xiaomi.eu_multi_ido_6.5.26_v7-5.1
4. boot, reboot
5. flash SuperSU via TWRP: UPDATE-SuperSU-v2.65-20151226141550.zip
6. booted and used several days, few reboots. All working fine, except apps closing in background and bluetooth earpiece losing connection. Described here: http://forum.xda-developers.com/redmi-3/help/redmi-3-pro-impressions-closing-t3397186
Where problems have started:
7. Decided to get stable xiaomi.eu release. Maybe forceclose and BT issues are resolved?
8. booted to TWRP and flashed STABLE release from xiaomi.eu: xiaomi.eu_multi_ido_V7.3.1.0.LHPCNDD_v7-5.1.zip
9. also flashed SuperSU without restart: UPDATE-SuperSU-v2.65-20151226141550.zip
10. After restart, I get boot loop.
It does very short boot attemps: when powered on, it vibrates and displays MI logo for a second, then reboots. Repeats it quickly 2 or 3 times and switches off.
Unable to go in to download mode, as volUp + Pwr will also give bootloop.
VolDn+Pwr will load fastboot after one reboot. MiFlash utility finds the phone, but throws an error on flash attempt (file not found or something).
If restarted with all VolDn+VolUp+Pwr buttons pressed, it will not turn on the screen at all, but appears on MiFlash utility and I am able to flash it. But still bootloops after that.
If I flash it with original bootloader, not the modified one as per guide (on step 2), I am able to boot in to china MIUI, and also in to bootloader menu. But of course TWRP does not work.
How do I do it with locked bootloader:
1. flash TWRP?
2. flash stable xiaomi.eu release?
3. get root?
Of course all of this is needed only until stable CM comes out.
Also, if bootloader is unlocked, is it displayed somehow? For example my old motorola would show a nasty warning during boot.
Short update. I have managed to install the latest xiaomi.eu ROM.
Unmodified bootloader is needed.
Flash TWRP via MiFlash separately, after MIUI is installed and booted.
Then flash SuperSU and you're good.
EDIT: I lost all my data since the phone was encrypted, but I recovered it flashing in fastboot mode
My Redmi 3 pro is stuck in a bootloader after trying to root it for the first time.
power off doesn't do anything.
power and volume up doesn't do anything
power and volume down shows a Fastboot logo with a cartoon, but I don't know what to do here and if it is useful.
After 1-2 minutes in fastboot logo it starts again in bootloop.
I've tried to press both volume up and down and power and keep it pressed for several bootloop cycles. It looks like the phone switched off, or at least the screen was black.
After restarting it again bootloop
I think soon the battery will drain and the phone switch off
I really don't know what to do
Related
R3 Pro (3GB/32GB, 2015817 version) came with some chinese/sellers custom ROM (and locked bootloader). It was heavy and bloated, so I decided to update it. Tried latest global stable (fastboot) ROM via miflash, flash was successful but that's was a lie - it stuck on mi logo...
Then I tried various other ROMs, global and developers, latest and older, some xiaomi.eu, manhit, etc. (for locked bootloader) and all I've got was either just a mi logo or mi logo with "powered by android" animation beneth. I left it for hours after flash and still nothing.
Then I found some ways to flash twrp, did that successfully, booted into it, wonder around in terminal and file manager, tried some recovery ROMs - but the result is the same - just logo or logo + animation.
I can get into fastboot (but it doesn't realy matters since bootloader is locked), download (EDL) mode, that Xiaomi menu (with Power and Vol+, with "shortcuts" to all the modes, hardware tests - btw. everything works there, etc.), twrp, charge battery (with some ROMs phone just gets warm and I know it's charging, there are no LED and/or animation, but in some everything works just like it should), but just can't boot into OS.
And I'm going nuts!
Here are some logs from the last ROM (i don't even know anymore which one is it) - pastebin.com/qaKVzxue and pastebin.com/dM3nEVj0
I'm not so experienced in looking at that but seems like every other thing in there, like cpu, i2c (touch/sensor), sound, battery, etc. is broken/faulty which is not true - everything was fine before update, and everything IS still fine according to inbuilt (xiaomi) hardware tests.
So somehow it seems that all the ido ROMs I tried are wrong for this device? Or am I missing something (quite possibly, I'm tired and pissed off)
Last night I did a backup of efs/nvram and then wiped internal memory/partitions, flashed latest global ROM, restored efs/nvram - phone stuck, but this time not on MI logo but freakin' penguin logo (like here en.miui.com/thread-377870-1-1.html). Same logo is for fastboot mode, no more bunny. Then flashed twrp and phone now shows mi logo with "powered by android" animation beneath, like before...
I don't know how this works with Xiaomi phones, but looks like it worked with some factory/seller special combination of ROM and bootloader. Then I did update and something stuck, maybe differences between ROM and bootloader, or some inside/hidden security mechanism that stops boot process? And because I can't find original firmware and/or bootloader is locked (maybe even updated?) it's now stuck...
Either that or some HW fault, but it would be insane that official ROM update with official tools and in factory download mode with full battery can cause such problem!
Can you go to twrp recovery?
Yes, like I said in the first post. I can do anything but boot android/MIUI. It's either because of locked bootloader or somehow official ROM installed officialy (via MiFlash in EDL mode) bricked phone, which is catastrophic bug i.e. epic design/implementation fail by Xiaomi.
Try this
https://forum.xda-developers.com/redmi-3/help/bootloop-bootloader-locked-options-t3331139
Sorry to intrude, I have pretty much the same problem.
Phone is stuck in bootloop and I can only access fastboot mode and EDL mode (but in EDL the phone does not connect to pc) and when I try to flash a stock ROM (since I know it is a software issue due to an unfortunate update) it says "locked device". So I tried to unlock it via MiUnlock... but phone cannot be verified 'cause "account not bound to this device" and obviously I cannot change any options since I cannot use my phone.
Please, help
it was happened to me about 3 days ago when i play around with the twrp & rooting thingy... tried everything from youtube to various forum solutions... just one link really works when you only have fastboot options and your phone bootloader is still unlocked. just follow the steps in the OP... key things here is downloading the tool to read your phone as mentioned in the OP i.e [TOOL]Minimal ADB and Fastboot [1-6-17]
1) Download Tool -> https://forum.xda-developers.com/showthread.php?t=2317790
2) Follow all the steps in the OP -> http://en.miui.com/thread-277276-1-1.html
3) Enjoy your phone from back from the dead.. LOL!
4) Remember here, the key is NEVER GIVE UP and PATIENT!
NOTE : The Device will start, wait till completion , it can take up to 10 Minutes. -> for me around 15-20 minutes for I have flashed the current beta rom of MIUI8 7.6.8
cheers, guys!
blx-
I had a similar situation.
Officially unlocked boot loader. Flashed TWRP using fastboot. Only got the mi logo and a boot loop on start up.
Could not turn on. Could not boot into TWRP.
When the phone was boot looping I could still get into fastboot mode by holding power+volume down.
I booted from fastboot mode into TWRP by opening the command prompts and using
"fastboot boot twrp2.img"
That got the phone available from windows explorer. I was able to move a new ROM image to the SD card and install from TWRP.
Currently running lineage 14.1 -20190112.
I lost a bunch of **** but my phone seems to turn on for the moment.
Note, I still cannot boot into TWRP using the phone only. I can only boot in from fast boot as above.
I installed stock Android 10 Q (from 9 P) via Odin on my galaxy tab s6 LTE, then i unlocked the bootloader and rooted with magisk (manager 7.5.1, zip 20.4) following the magisk git site installation instructions (which are a bit more complicated than from some third party sites.)
Everything ok, but then when i power off it reboots. It's not in a bootloop: it boots up normally, but if i can't power off then that's not good when I'm not using it. I tried patching again and checked i got the the same md5.
Eventually i found that if i booted to recovery mode and there i choose reboot, it reboots to unrooted, but it does power off.
To get root access again i start with the recovery key combination but let go at the splash screen before it enters stock recovery mode. This means that i have to reboot each time i want to either switch it off or have root (but not both.) It's good enough for now, so I'm posting this in case anything else has the same problem.
Hi everybody,
I tried to install Magisk 21.2 on my stock Oreo rom with Magisk 20.4 already installed. I've used the recommended method for installation in Magisk Manager, and I left the AVB/dm-verity option unchecked. It resulted in a bootloop.
Before updating I did a backup of the boot partition, so I could restore the previously working Magisk 20.4. Now I have two questions:
1) Is there something else I should do other than restoring the boot partition after a bootloop?
2) Is there a way to install the new Magisk or should I just dismiss the update notification?
Happened to me As well on my G6.
I had to reinstall the rom. good thing i had backup.
I've downloaded the zip file of Magisk 21.2 and flashed it with the rom after wiping almost everything, and even tried flashing a different rom with it (I'm using stock A9)., but it seems it resulted in a bootloop every time.
There is a new magisk 21.3 from yesterday, which i hope fixed those issues as i am not planning to go though that hassle again.
I tried the new 21.3, and still it causes bootloop, at least I'm glad I'm not the only one.
DannyynnaD said:
Happened to me As well on my G6.
I had to reinstall the rom. good thing i had backup.
I've downloaded the zip file of Magisk 21.2 and flashed it with the rom after wiping almost everything, and even tried flashing a different rom with it (I'm using stock A9)., but it seems it resulted in a bootloop every time.
There is a new magisk 21.3 from yesterday, which i hope fixed those issues as i am not planning to go though that hassle again.
Click to expand...
Click to collapse
It happened to me, same setup as the OP and did the direct install method from Magisk Manager. My phone is stuck in bootloop at the triangle/! scrren and I can't access TWRP via the normal buttons manner. Also, can't get any ADB to detect the phone (I am using a new PC that probably never connected to this phone despite loading ADB, drivers, etc. - I am going to resurrect the previous PC to see if can connect).
May I ask how you restored the saved boot image? via TWRP restore?
I've rooted and played with many ROMs on various android devices, but I'm no expert and this one has me stumped.
Yes, I did a backup of the boot partition before flashing Magisk and then I restored using TWRP restore. It's not the first time that a new Magisk version causes bootloops on the G5, to I was prepared this time.
By the way, if you don't have a backup, you may try to flash the Magisk Uninstaller zip, and without rebooting, the old Magisk 20.4. In theory it should do the job.
tremalnaik said:
Yes, I did a backup of the boot partition before flashing Magisk and then I restored using TWRP restore. It's not the first time that a new Magisk version causes bootloops on the G5, to I was prepared this time.
By the way, if you don't have a backup, you may try to flash the Magisk Uninstaller zip, and without rebooting, the old Magisk 20.4. In theory it should do the job.
Click to expand...
Click to collapse
Thanks, But how to access TWRP or flash the zip? I haven't found any technique to access recovery (Power+VolDn doesn't work, only allows Factory Reset screen). How to access Fastboot to use ADB (I assume that would be the technique)? I did manage to bring up some odd screen that had a two-line message about fastboot by, I believe, using Power+VolUp.
For clarification this is what I now have:
Phone off (remove battery). Insert battery. Press power button until brief vibrate (1-2 seconds). Release power button. Triangle with "!" displayed "Your device cannot be checked for corruption. Lock the bootloader. " screen displays for about 3 seconds, screen goes black a second or less. Back to the previous warning screen.
Press and hold Power button + Vol Dn acts just like the above, but if I press power + press/release/press/release... I can get the factory data reset (Yes or No(Exit) options) - I haven't accepted that.
I've tried connecting PC to the USB port and two things: as soon as I connect it, the phone powers on and does the looping again. My PC doesn't see the phone in Device Manager and ADB won't list it. I did (one time) manage to bring up the two-line fastboot message at the top of the screen.
BTW: when it first tries to power on, before the Lock the bootloader screen, there is a small, scrambled white area (text?) at the bottom of the screen.
I don't know when was the last time (if ever) I attached to the phone via USB (probably a few years ago when I initially installed TWRP). Haven't really done much other than upgrading TWRP (via TWRP), Magisk (via Magisk Manager), and the very occasional nandoid backup via TWRP (I have one from 3 months ago).
Any further assistance or info would be greatly appreciated.
To access TWRP, turn off the phone, then keep pressed Volume down+Power and once you see the LG logo release the power button and press it again. The phone should ask you if you want to reset everything: if you press yes and then confirm, you will:
1) Enter in TWRP, if you have TWRP installed, or
2) Erase the whole internal memory, if you don't have TWRP installed.
As you already have TWRP installed, it should be quite safe to go through the reset procedure, or at least that's what happens on my phone. If you don't want to take the risk, you can still use fastboot to boot a TWRP image you have on the pc, just write
Code:
fastboot boot <path_to_twrp.img_on_pc>/twrp.img
To do so, you first need to boot into fastboot: you can just turn off the phone and, keeping the Vol- pressed, connect the USB power cable to the phone. It will boot into fastboot.
One more method could be booting into download mode (Vol+ and connect the USB cable) and flashing an original firmware using LGUP, but that is way too much for a phone that already has both TWRP and fastboot accessible.
tremalnaik said:
To access TWRP, turn off the phone, then keep pressed Volume down+Power and once you see the LG logo release the power button and press it again. The phone should ask you if you want to reset everything: if you press yes and then confirm, you will:
1) Enter in TWRP, if you have TWRP installed, or
2) Erase the whole internal memory, if you don't have TWRP installed.
As you already have TWRP installed, it should be quite safe to go through the reset procedure, or at least that's what happens on my phone. If you don't want to take the risk, you can still use fastboot to boot a TWRP image you have on the pc, just write
Code:
fastboot boot <path_to_twrp.img_on_pc>/twrp.img
To do so, you first need to boot into fastboot: you can just turn off the phone and, keeping the Vol- pressed, connect the USB power cable to the phone. It will boot into fastboot.
One more method could be booting into download mode (Vol+ and connect the USB cable) and flashing an original firmware using LGUP, but that is way too much for a phone that already has both TWRP and fastboot accessible.
Click to expand...
Click to collapse
My phone never got past the bootloader screen (i.e. never got to the LG logo screen). When I booted into fastboot mode with the Vol+ button, I could issue commands like "fastboot devices" which would return that it saw my phone, but attempting to use fastboot to reload TWRP didn't work - some say the LG fastboot has been neutered.
Eventually, I had to indeed use LGUP/Uppercut and reload the stock Oreo and the phone came back up. BUT attempting to reboot into bootloader not only didn't come up in TWRP, but I got the little dead Android image. I ultimately had to downgrade to OEM nougat, jump through a few hoops, and finally got TWRP installed. Then it was just a matter of restoring a backup or reflashing a newer ROM (I ended up loading lineage 16, no gapps, with microg etc.).
Somehow the magisk upgrade really trashed my recovery partition somehow (??). I've always made sure to have at least a couple of TWRP backups, but this time I was screwed royally when I couldn't access recovery. I forgot what an ordeal it was to get TWRP & root on this phone originally.
Thanks for your help.
Here's the sequence of events. I am not rooted, bootloader locked, never flashed anything to the device. Using phone as company intended.
1. Yesterday night I turn off the device only to notice that it is bootlooping. I can't force shut down. Whatever, I do, nothing would shut down the device completely. Pressing power button for over 15 seconds or anything.
2. If I try to go to recovery, it automatically chooses reboot and goes back to bootloop. Only fastboot works.
3. I install Mi flash tool and download ROM and try to install only to get device is locked error because bootloader is locked. This happens at the "Erase Boot" stage.
4. I try this couple of times and just before giving up, I try to go to recovery again. This time however, recovery opens and it doesn't choose anything automatically.
5. I click the "Repair" option and it just boots regularly and goes in as if nothing happened. No delayed boots, no installs or anything. Just regular boot and goes in. Data is intact. I am now using the phone for a while and have not turned off again.
What should I do next? Flash current version of ROM (already have latest) through the Updater app? Anything else?
Unlock bootloader first
If u get this problem again, you can flash easily with mi flash tool (bootloader should be unlocked)
Somewhat similar thing happened when my sim reader was broken, was just restarting and even after removing (if it managed to boot) sim card it said no service thinking there is a card and would crash from what I assume is a nullptr, this phone sucks
Hi Community,
I read some posts how to fix my Problem, but i cant go to a service Point.
So I was using the Evolution X for a long Time (Installed with TWRP 3.1.0).
And now i wanted to change to the Nusantara Project (Vanilla), I did a clean Flash, everything worked i could access the System.
Than i had problems installing Play Store, so i rebooted into Recovery via the System. But now im Stuck in the Loop.
Can i Somehow connect my Phone to the PC and Reset?
Can someone tell me if i Hard/soft bricked my phone ?
Just a little advice, would be really appreciated.
Thanks a lot
Go to TWRP, wipe system, cache, data and dalvik. Now flash nusantra and whichever GApps are recommended for it (if there are no recommendations then use OpenGApps, make sure the architecture is correct). Now wipe dalvik and restart. Sometimes, certain roms begin to bootloop if you boot into the rom first, then try to install gapps later.
If you still have issues, just reflash the stock rom.
I cant access the TWRP anymore, im just stuck on the Bootloader, no matter how i turn on The Phone (Volume Up + Power ON ), (Volume Down + Power), (All 3 Buttons)
Nothing works anymore i dont understand ....
Im searching the net but i cant go to fastboot or something else, its just keeps on rebooting ...
So it's bootlooping, but you cant access recovery?
When the screen turns off, press the key combo and it should go to recovery.
Your best bet is to take it to a service centre, but if that really isn't possible for you, then wait for its battery to drain completely, then when you plug in the charger, instead of turning the phone on, press the key combo to enter the recovery. From there, wipe and flash some other OS.
I've also heard that certain versions of TWRP don't support some roms, leading to a bootloop. In that case, you'll have to use orangefox recovery to flash the rom (orangefox is flashable via twrp)
Yes its Bootlooping.
When i turn it on, on the Left Corner "Recovery Mode" blinks for one second. Than the usual Text appears:
"Orange State
Your Device has been unlocked and cant be trusted
Your Device will boot in 5 Seconds".
So after a couple of seconds (around 10-20 sec)
It turns off and immediately on again. I Just can turn it OFF when i hold all 3 Buttons.
Than i try starting it with Volume up + Power / Volume down + Power, But i cant access Recovery or TWRP.
So i should wait til the battery gets low and try it again ?
Like i said, my custom Rom (Evolutionx) and TWRP just worked fine. I dont know man ...
Well since your bootloader is unlocked, try flashing the stock rom again. Look for a tutorial and follow it.
Hi I managed to unbrick my device with this guide, and im back on a stock rom
Unbrick
i ran following commands to get to my custom rom:
I run adb reboot bootloader,
add executed following commands.
(Pitch Black recovery 3.1)
- adb reboot bootloader
- fastboot flash recovery recovery.img
-fasboot reboot recovery
It just hang up and booted after a while into the normal system.
But im not able to get to the recovery menu ?
When I restart and hold Volume up + Power, i go in a loop and the phone keeps restarting over and over again.
what have i Fu**ed up ?
Do i need another recovery tool ?
sorry guys, i appreciate your help a lot tho !
EDIT: Is my bootloader unlocked ?
I can access via "adb reboot bootloader" the phone
and on the blackscreen on the phone it is written:
oppo verfiy pass
fastboot_unlock_verify ok
Update:
So i tried some Stuff and i got Red State. No Problem i Unbricked it once again and now im on Stock Android 10.
Now im Trying to enable the bootloader again.
I downloaded the In Depth Test_Realme_6.apk but i keep getting the Error that i should update the system.
So should i update the system ?
I cant find a CURRENT Tutorial to make this work, please help...
If you cant find a tutorial for your version, why not downgrade back to a previous one if possible.