Please help I got severely stuck - Xiaomi Redmi Note 5 Pro Questions & Answers

My phone was rooted and I was on Havoc os v2.2 , I was using it for 2-3 months and os was running very great, but suddenly it started giving me problems like recent tabs were not opening, notification panel were not opening.
So I thought to install different rom, I downloaded evolution x v4.4 and to install it, I updated my twrp recovery from v3.2 to v3.4 and it got successfully updated, but when I try to open recovery it got stuck on mi logo, so I tried to flash recovery again with the help of pc, but on command prompt when I type adb devices, device doesn't appear, so I tried to open developer options but the option doesn't appear so I tap multiple times on build number, but still nothing happens.
So I tried to format my phone , but now it got stuck on mi logo, neither the device is booting even in recovery mode it stuck on mi logo.
So what are the option left for me to get out of this situation.
Edit: and in device manager it is showing as Kedacom usb device and under it is showing Android Bootloader Interface.

Nevermind I figured it out myself

If you want to flash recovery, lock/unlock bootloader or root your phone or flash a stock rom then just download this software.
Link : Tool all in one https://forum.xda-developers.com/on...ol-one-driversunlocktwrpfactory-t3398993/amp/
(Credit goes to developer @mauronofrio)

Related

[Q] galaxy nexus stuck in bootloader, not recognized by pc

hi guys,
tragedy started like that: today i decided to give miui another shot. downloaded latest miui developer rom to sd card of my galaxy nexus, rebooted into recovery and flashed miui zip and tiny kernel afterwards. stupid me i forgot to wipe cache before installing the new rom. hit reboot in cwm, which kindly told me that the new rom could make recovery unusable. here i accidentally selected the obvious wrong choice, which said "dont fix problem" or sth like that. dont know if recovery is gone now... after reboot miui was trying to boot without success (mi logo shown until you turn the phone off). so i went to fastboot by pressing volume down (my volume up is broken!). fastboot acts pretty dead: cant scroll through options by pressing volume down, cant do "normal" start by pressing power, absolute no reaction of the phone. also the phone is not recognized when connecting to pc via usb (tried the samsung original driver). phone is recognized when miui is trying to boot, but i cant send any commands via fastboot.
im thankful for any advice that lets me install a new recovery/boot into recovery/make it boot again!
fastboot mode details:
product name - tuna
variant - maguro 16gb
bootloader version - primemd04
baseband version - i9250xxlj1
carrier info - none
serial number - irrelevant
signing - production
lock state - unlocked
anyone?

Need solution of soft bricked Yureka!

I have Yureka running 5.1 thru EuphoriaOS rom (June build). I can't open TWRP, Or Bootloader at all. All I see is a black blank screen which goes away only after removing the battery! I tried Adb and fastboot on PC, Device not recognized. Though it is booting, rom is working, USB connection is also fine! Solutions?

Soft Bricked Fix needed (stuck on app optimisation)

Hi guys,
my wiley fox swift gets stuck in a continual optimising apps cycle. I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted) it worked fine yesterday and today i can't get it to work.
It's always optimising apps, if it's finished then i see the cyanogen logo and it starts optimising again shortly after.
I removed the battery and did wait about 15 minutes before putting it back in, i tried waiting (after 2 hours+ of it optimising i gave up),
i does not get recognised when i connect it to the pc (although i only used it to put stuff on the sd-card before) maybe a driver would fix this but i'm not sure which one.
I'm pretty clueless right now and i would be happy if someone can help me.
Saw the same thing on a friend's device today, used fastboot to factory reset the device. Insert USB in a powered-off device while holding vol+ then using fastboot do a "fastboot -w" to factory reset and recreate the (probably corrupted) data partitions.
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
dajohre said:
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
Click to expand...
Click to collapse
ADB needs debugging to be enabled in developer options
FASTBOOT will only work if the phone is in bootloader mode
I already said in my first post:
dajohre said:
I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted)
Click to expand...
Click to collapse
since i never changed anything in my phone I haven't enabled debugging in developer options, if I could access the bootloader mode I could reset my phone but like i said,
it enters fastboot and not the bootloader from which i could enter recovery mode
under these circumstances, can i do anything?
see here https://wiki.lineageos.org/devices/crackling/
Note they call bootloader mode Download
Ok i can access recovery mode now (it was explained wrong here)
i tried to factory reset but the problem still persits.
in recovery mode i did go to ->Wipe data/factory reset then i had the options (No/No/Yes -- delete all User data/No)
i choose the third option and it did load a short while. after a reboot it still wants to optimise apps.
what's the best option now? i can choose (Apply update\ Wipe data/factory reset\Wipe cache partition\wipe media\reboot to bootloader\View recovery logs)
Fix
Hi,
I had the same issue and wrote the Wileyfox customer support.
They provided me the following instructions to fix the issue:
Download:
* 1 - ZNH0EAS2NH
* 2 - ZNH2KAS7EB
* 3 - TOS111B
Repeat for File X in [1, 2,3] :
* Goto Recovery
* Update your phone using File X
Since this is my first post I am not allowed to post links.
Find the full document including file links here: h t t p s : / / we . tl / B1IpUP6wtB
Already after running the first update my phone booted again.
Only thing I noticed is that the UI feels a little laggy / slower than before.
Regards

Sort of bricked G4, rebooting download mode, no fastboot recognition nor TWRP

Hi all,
I have tried my luck in two different threads already and did hours of research but thus far, no success. I hope somebody can help me.
I installed the official Nougat (V29A) update and after that the Oreo AOSCP ROM. Everything went (seemingly) fine, Oreo was working. I wanted to reflash Oreo to get rid of some Google Apps, but the problem then was, that I could not reboot into TWRP. The only recovery mode is the Android recovery and I cannot reset the phone, neither use ADB sideload, nor do anything else (unknown fs_filetype error). Only thing that is working, is to enter the fastboot mode, but my laptop does not recognize the phone while in fastboot mode.
I also tried resetting the phone to factory defaults from within Android (back when it was still booting up) and now my phone is stuck in a bootloop which ends in the (useless) Android recovery mode.
At first I thought reflashing the stock kdz would not be a problem. I am able to enter download mode, but it only stays in download mode for about 15 seconds and then reboots itself. LGUP or LG flash tool, don't recognize my phone in that short amount of time.
I tried the above mentioned solutions on OS X, Windows 7, Windows 10 as well as FWUL. No system recognizes my phone.
I really am at my wit's end. Any help would be appreciated.
If any further information are needed, I am happy to provide these.
I changed following in hidden menu NT Code, changed as below NT Codes with respect to firmware region... Rebooted after confirmation "NT Code Write OK" message.
V29a Firmware NT Code:
"1","FFF,FFF,FFFFFFFF,FFFFFFFF,11"
V20h Firmware NT Code:
"1","FFF,FFF,FFFFFFFF,FFFFFFFF,51"
Checked in both above firmwares..Worked flawlessly on my h818p...No more annoying message on every boot.
Software Version in about/ settings also changed to region exp. 20h-DS2-XX to 20h-ESA-XX upon reboot.
Is DS2 appears when cust mismatch..?

unable to unlock OEM oppo Find 7A (X9006)

I don't know what to do anymore. I've been trying for months to try to install TWRP recovery on to my OPPO.
(Backstory)
I wanted to unified the storage of my OPPO Find 7A. So I uninstalled Lineage using the TWRP and I thought I could just install Colour OS and see if that could unified it. However, the moment I got Colour OS it couldn't even open the wifi and the dates are always 1970 Jan 1 at 4 pm, even if you change the dates. As soon as it is turned off and back on it will be the same. So I thought I could just use TWRP to uninstall the Colour OS and install another Custom OS. However, when I press the power button and down volume. it just restarts (Showing the WO chinese logo, it doesn't show the OPPO logo anymore) and goes directly to Colour OS.
So I figured that maybe TWRP was deleted when I was wiping everything. So I tried to install it again with the latest TWRP and ADB in fastboot mode with "fastboot devices" to check if it is connected and "fastboot flash recovery twrp.img". This time it says it is locked and can not flash or erase.
So I tried "fastboot oem unlock" it says Okay and basically restarted itself and went directly to Colour OS. When I put it to fastboot again to check with "fastboot oem device-info" it says it was still locked.
So no matter what I did nothing seems to work.
So far I've tried using different programs like
WinDroid Toolkit v3.1
Oppo_find_7_Recovery_Installer_V1.5
flash_recovery.zip
And I even tried to change to program I'm working with, such as AndroidSDKSlim, ADB-Fastboot-And-Driver-v1.4.3 and changed different TWRP versions (2.8.4.0, 3.0.2-0, 3.2.1-0)
So, now I'm thinking I might have just softbricked it and I'm trying the solution from this post
https://forum.xda-developers.com/find-7/help/how-to-debrick-unbricka-oppo-7-7a-t3717802
So far it has been 45 mins and it does not seem the program is downloading/installing anything on my phone. It's just there doing nothing after I pressed "start".
I'll try leaving it overnight and see what happens but if someone can help please do. (UPDATE: Nothing changed)
PS. the current Colour OS that is running on the phone is version 1.2.0 (it cannot be updated, I've tried using an SD card with the newer version on it to run it with "system updates", it restarts and it goes back to 1.2.0 and nothing has been done.) It is running Android version 4.3 and I have activated developer options and USB debugging but there is no OEM Unlock option under "Developer options")

Categories

Resources