I'm currently having issue with my phone, Redmi Note 3 Pro Kenzo(snapdragon 650) charged my phone overnight after completely drained it and the next morning i realized that it's on boot loop.
I tried dozens of method since the past 72 hours, none of them works. My phone run on stock miui 8 rom, didn't turn on the dev mode/debugging so basically just a pure stock out of the box phone with 0 tweaks.
It loops without the android logo below it. Just the MI logo in the middle of the screen and it reboot every 10-15 seconds or so.
I am able to run on fastboot mode (volume down+power on button) then i hook it up to my computer, used a patch to boot it on EDL mode and flash the stock fastboot rom using MiFlash and it states that i have successfully flash the rom on the phone. But when i turn it on, it loops on the MI logo again..
Tried dozens of method, flashed the emmc file and etc but none of them works.
Even mod on xiaomi forum gave up on me and ended up saying that i've roasted my logic board lol
But I read a thread on someone who had the same problem with mine but he have unlock his bootloader and get his phone back to life by flashing the twrp recovery.
When i try to hook up my phone with command prompt, running on fastboot mode it detects my phone when use the "fastboot devices" but when i use the "adb" command it stated that my computer didn't detect my device.
any thoughts?
rlly need some help here guys :/
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.
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Sounds very similar to my situation. I did end up following that guide to get mine going again. The link is broken to get the recovery tool, the 2nd one below is the "minimal" version which isn't supposed to wipe data. That is the one that worked for me. I would backup any data if you can first, no guarantee it wont wipe it. Mine wouldn't boot into the stock rom after, but at least it would get to the stock bootloader (VolDOWN + PWR). From there I was able to adb sideload the stock rom (Install from USB). This completely restored it to stock.
23santosh24 said:
Hi!
I have a OnePlus X and the year after I bought it, I flashed TWRP and installed Lineage OS. Since then, I've flashed many custom roms on my phone. A few weeks back, I decided to flash Resurrection Remix. The battery life on my phone with resurrection was pathetic so I assumed it could be fixed by flashing a custom kernel (franco kernel). I downloaded franco kernel, copied it to my SD card and powered off my phone.
Instead of pressing the VOLUME DOWN and POWER button simultaneously to enter TWRP, I pressed the VOLUME UP and POWER button by accident and went into Fastboot mode. When in Fastboot mode, I pressed the VOLUME DOWN and POWER button thinking my phone would boot into recovery, but it got stuck in a bootloop.
Now my phone can boot only into fastboot mode by pressing the volume up+power button. Any other combination of buttons and it goes into a bootloop.
All this is completely my fault and I would do anything to try and fix it.
Is my phone soft bricked or hard bricked? ( I have a feeling that it is soft bricked).
I've downloaded the android SDK and Minimal adb and fastboot on my pc. I'm able to run fastboot commands, but when I type 'fastboot oem unlock', I get an error saying
"FAILED (remote: oem unlock is disabled)". I've tried 'fastboot flashing unlock' too, but the screen just says "...". Hence, I'm not able to flash TWRP. I tried flashing even the stock recovery but it wouldn't work.
Is there any other way to unlock the bootloader?
I haven't tried the Mega unbrick guide for a hard bricked OnePlus X yet, since I'm able to boot into fastboot mode. Should I give it a shot?
And lastly, can I recover my phone from this mess or is it permanently bricked?
I would appreciate any help.
Thank you!
Click to expand...
Click to collapse
Surely your bootloader is already unlocked isn't it?
You don't actually say what happens when you try to reboot into recovery using fastboot commands. Does that fail too? What happens when you try to flash twrp again? You don't actually say.
That's what I thought too. It would just say 'recovery.img' not found or something like that. But, I followed the Mega unbrick guide and was able to install the stock ROM through the stock recovery. My OPX is alive again!
i'm stuck here. the phone does not go into recovery at all .. stuck on oneplus logo .. I don't know what to do .. any ideas?
---------- Post added at 09:20 AM ---------- Previous post was at 08:24 AM ----------
I managed to get it alive again with this guide
I replaced the broken screen on my Kenzo and now it's stuck at the Mi logo. Funny thing is the technician said when he disconnects the touch ribbon it boots normally (but obviously with no touch) and locks up with Mi logo when it's connected. I've read that the mtk and sd screens are interchangeable so I don't think that's the issue. I don't have access to another screen so I have to make do with this one anyway.
I bought the phone from Gearbest two years ago and it came with the vendor rom which I never changed. I'm suspecting the vendor rom has something to do with it and now is the perfect time to flash a new rom before I sell it. Only problem is I have no clue how to flash a rom. I can get it to the fastboot screen but that's it.
Could someone please help me but in plain laymans English? Flashing for Dummies kind of thing. I've been a member here a while but haven't grasped the lingo or their meanings yet.
Thanks in advance.
Hooow?! said:
Google miflash
And download it.
Also download the latest miui developer rom
http://bigota.d.miui.com/8.1.25/miui_HMNote3ProGlobal_8.1.25_16348801ef_6.0.zip
Search for EDL.zip from xda itself and follow the instructions to get to edl mode from fastboot mode( to see if it's in edl mode check for the red blinking status LED when connected to the pc)
Now open miflash as administrator connect your phone to the PC.
Miflash should see it as something like COM..
Now extract the developer rom and in miflash browse for the extracted direvtory
At the bottom right select clean_all lock.bat and then press flash..
After few minutes the flashing should get completed and then hold the power button on the phone until u see the mi logo.
Wait for the booting to get completed and then setup the phone..
Congratulations you bow have a working phone again.
Click to expand...
Click to collapse
Thanks for the help. Well I got it all the way to flash in edl and around 9% it gave an error message "Object reference not set to an instance of an object" or something similar. So it basically failed. What can I do? I'm almost there
Hooow?! said:
Google some fastboot commands to erase partitions...
It should be something like this
fastboot erase boot
fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
First go to fastboot mode by holding vol down and power together .
Then connect to PC and then install minimal adb and fastboot kit. Then open the shortcut in desktop and then type fastboot devices and check if u device is there or not. If yes then copy and paste the commands above and then repeat the EDL flash procedure.
Click to expand...
Click to collapse
This is depressing. I followed your instructions and used the command "fastboot format partition" as that's the only one that would work and was suggested in options. The result was "failed device locked". :crying::crying::crying:
Yep. Same result. Does the bootloader have anything to do with all this?
Any ideas why it would boot normally with the touch ribbon disconnected but bootloop when connected? I'm beginning to wonder if flashing will even work.
WELL!! My phone is suddenly working. After trying all sorts of flashing methods I put it on the charger this morning and just took it off and it's working perfectly.
What happened was I read another thread about flashing the Global rom with a locked bootloader. At the very end of the instructions and almost as an after thought, the author mentioned that you must boot the phone into recovery in order to clear the cache etc otherwise the phone will be stuck on the Mi logo. It sounded similar to my problem so I did volume up and power key together and the Mi logo came up. Thinking nothing had changed I did volume down and power and went into fastboot. Again nothing changed. So I switched it off, put it on the charger and left it for about 4 hours. I just took it off the charger 20 minutes ago and it was working perfectly.
Perhaps someone can explain what the heck happened? Meanwhile I'm selling it pronto. Lol
Twotems said:
WELL!! My phone is suddenly working. After trying all sorts of flashing methods I put it on the charger this morning and just took it off and it's working perfectly.
What happened was I read another thread about flashing the Global rom with a locked bootloader. At the very end of the instructions and almost as an after thought, the author mentioned that you must boot the phone into recovery in order to clear the cache etc otherwise the phone will be stuck on the Mi logo. It sounded similar to my problem so I did volume up and power key together and the Mi logo came up. Thinking nothing had changed I did volume down and power and went into fastboot. Again nothing changed. So I switched it off, put it on the charger and left it for about 4 hours. I just took it off the charger 20 minutes ago and it was working perfectly.
Perhaps someone can explain what the heck happened? Meanwhile I'm selling it pronto. Lol
Click to expand...
Click to collapse
Just dont sell it yet use some awesome oreo roms best is u try resurrection remix oreo its the best with agni kernel and enjoy..... Dont sell the kenzo man just enjoy the roms u can unlock bootloader unofficially which is far better and easier than official one and then flash twrp enjoy the phone
Androbots said:
Just dont sell it yet use some awesome oreo roms best is u try resurrection remix oreo its the best with agni kernel and enjoy..... Dont sell the kenzo man just enjoy the roms u can unlock bootloader unofficially which is far better and easier than official one and then flash twrp enjoy the phone
Click to expand...
Click to collapse
Lol. Nah, I already have a Mi Mix 2 which I'm loving. This old faithful has to go.
Dear Community,
I am a real noob when it comes to Android, flashing ROM, root and so on.
I got a Oneplus here where supposedly root rights are on it and another ROM.
Current problem, as soon as I turn it on it hangs when booting. (Bootloop - red dot with 2 running white dots)
I already tried it with power + volume+. Unfortunately unsuccessful.
Is it correct when I press Power + Volume- that you get into fastboot?
I can't get into the recovery mode either.
I would like to get the device running, but without root rights, OEM lock and the Oxygen OS from Oneplus.
So far my attempts to get it running have been unsuccessful.
Update: after 4h in the bootloop, it booted successfully. *yeah*
So how i can see, if the phone is rooted and how can i lock it?
I tried it with adb, i can find the phone with adb devices.
Then adb reboot fastboot, after that i tried to find it with fastboot devices but then he finds nothing more. the drivers are installed. also fastboot oem lock doesnt work, because the phone is not found.
Sooooo a while back I really screwed up my OnePlus N20 5G (CPH2459). Currently, it will turn on, but after one try at the OnePlus logo it reboots to recovery. I can get it to go into fastboot mode but ADB doesn't detect it.
It was rooted using Magisk.
My first question is, does anyone have the full firmware for CPH2459?
And...
What can I do to get ADB to recognize the phone so I can flash the firmware?
Ok yes I'm using the red cable
I was using the driver's from the website.
I was trying to use rom2box.
I tried.
ADB won't recognize it because of the problem if not booting past the logo and going straight into recovery. Fastboot didn't recognize in that mode either.
Everything leads back to my issue of needing firmware for the CPH2459 model.
I figure if I just flash stock it'll be fine, right? But I can't find full stock...
I know adb and fastboot are different. But I'm in fastboot mode right now and I can't get the phone to show up. Also when I hold only the power button, it vibrates, shows the OnePlus logo restarts on its own, vibrates again, shows the OnePlus logo again, then loads ColorOS Recovery