Develop Bugs

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..?

Xiaomi Redmi Note 5 Bricked, any suggestions?

Hi there,
as you all can read on the tittle, my device is softbricked (because my bad with backups and flash, sorry first time). I tried everything but open phisically the phone (that was my last option) and none of them worked. So I ask you for some ideas.
Here I´ll tell what still works on my devices, and what I´ve tried:
-When I power on the device, it appears the MI logo, then "The system has been destroyed" and at the end is shuts down again or reboot.
-I can access the recovery mode that was by default (MI Recovery 3), and I can Wipe Data (it starts, and when it´s almost 3% it shows as complete).
-I can access too fastboot, and ADB recognises it.
-I can flash TWRP (with Anti-rollback warning), but not boot it (it makes the devices to reboot, and after ~10s shows failed too many links).
-MIAssistant does not recognise my device (but the phone knows if I connect it to the computer).
-I am not able to unblock my device. It recognises my device, but at 99% makes me add my device in MIUI´s Setting > Developer options > Mi Unlock Status (I didn´t do it when my device worked, my bad).
-Tried to flash with MIFlash, but it keeps me with "flash xbl error". It recognises my devices though.
Any help would be very appreciate, and if you need any additional info, ask for it. If nothing works, I will go to a phone store to mae them open my device, so I can try one more thing.

https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780

devcon69 said:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
Click to expand...
Click to collapse
I really apreciate your help, but none of your options did something.
The MIFlash, as the previous time, showed "flash xbl error". The QPST, didn´t recogniced my port, so I couldn´t click "Download".
And yeah, my last option is to do a testpoint, but I would like to try every other option, rather than open my device.
Anyway, thanks for using your time on me.

I did not notice that you have a locked bootloader. Try MiAssistant or MiflashPro. Try flashing latest recovery rom.
https://forum.xda-developers.com/redmi-note-5-pro/how-to/tut-flashing-official-recovery-rom-t3798165
EDL is the last choice.

devcon69 said:
I did not notice that you have a locked bootloader. Try MiAssistant or MiflashPro. Try flashing latest recovery rom.
https://forum.xda-developers.com/redmi-note-5-pro/how-to/tut-flashing-official-recovery-rom-t3798165
EDL is the last choice.
Click to expand...
Click to collapse
Tanks for taking your time, but the solution propossed did not work. Every download link gave me an invalid rom (it asked for a 10.0.6.0), so I got the newest one on xiaomi website. It looked to work, but when the PC screen was at 99% and the device screen at ~50%, it suddenly finish. The device reboots, it shows the android logo too, even makes the sound where you have to enter your pincode (the device has not a SIM inserted), and eventually reboots to the recovery menu, showing on the bottom "This MIUI version can´t be installed on this device". Tried the slow mode (more pair the load, but still don´t work), tried other roms. Nothing.
At least it boots now to the revocery menu with "MIUI version..."
So I tried the testpoint to try EDL mode, and all correct but when I tried to flash the rom, everytime but the first one (with a strange log as ERROR) showed "Cannot receive hello packet". Every single rom.
So here I am, trying not to cry on my bed. I feel like **** for breaking my device in a week.

Nexus 5X lost lock pattern (fastboot found, adb not found), recovery "no command"

Nexus 5X lost lock pattern (fastboot found, adb not found), recovery "no command"
Hello !
So, I've had the same pattern to unlock my screen AND boot my phone for months.
This morning, I can't unlock : I do not remember it, I try to connect the dot "as usual" and then start to think, and now I've got my muscle memory mixed with me trying to figure out what is the pattern! So I try different combination that I think are close.
Then I reboot...
Then... there's this lock on boot time also, I tried a few different combination, and I have only 5 tries left before device WIPE !
- I have installed Android studio, the USB Driver (which I think is the right one)
- I can either boot my phone in normal mode (stuck in the dot patern lock), either in fastboot mode
- From fasboot mode, I can go to recovery, but it says "No command"
- With the SDK tools, I can list my device with "fastboot devices" (and reboot it for example), but I can't have it to appear with "adb devices"
I'll try one or two other time later when I'm tired my patern, to see if i can do it without thinking...
BUT, Can't I remove the lockscreen somehow? I'd preferably backup some files and apps data before wiping it
What do you suggest!?
Thanks in advance

I finally had to wipe / factory reset.
On reboot, he asked me to unlock the phone WITH MY GOOGLE ACCOUNT.
So ... I had to wipe everything, then unlock it. Why, oh why, the boot screen does not have this option!?

Please help I got severely stuck

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)

Sorta/Kinda Brick After Attempted TWRP Install - Moto G7 Play 1952-4

Ok, so I’ve run myself off the road into a deep hole and am hoping someone can help me climb out and get back onto the correct path.
I have a Motorola Moto G7 Play 1952-4 (channel). My goal is to install TWRP, and LineageOS 18.1 with GAPPS. Root is not important at the moment.
Here’s what I did:
After successfully unlocking the bootloader (thank you Motorola), I downloaded TWRP for Chanel from the TWRP.me site. My plan was to first install TWRP, then use TWRP’s install feature for LoS 18.1 and the GAPPS.
To install TWRP recovery, I followed the instructions on the TWRP site. After starting the ADB server on my Windows 10 PC and booting the phone into the stock recovery, I used “adb boot twrp-3.5.2_10-0-channel.img” to temporarily boot into TWRP recovery. I then used ADB to push TWRP.zip onto the internal SDCARD. I used TWRP’s install feature to install "twrp-installer-3.5.2_10-0-channel.zip", presumably to both slots. To the best of my memory, everything completed correctly.
BUT . . . when I powered down the phone and attempted to boot into recovery, all I got was a black screen with a small N/A in the upper left corner instead of the familiar TWRP screens. After a while, the phone booted itself into the stock U.S. Cellular Android 10 (Hell Oh - Moe Toe). I've done several power-off/power-on cycles to no avail. I am able to get to and use the stock OS.
So, like TWRP.me suggests, I figured I’d just flash it back to stock and start over. Um, nope. I can Vol-DN/Power to the bootloader menu, but “adb devices” doesn’t see the phone, preventing me from flashing anything. USB Debugging is enabled and the phone says "USB Transfer Mode: Connected". “adb devices” sees the phone while Android 10 is running, but as soon as I boot into recovery, the phone “disappears” from ADB.
The only other thing I could think to do was to use the “Rescue” function in the Lenovo/Motorola Smart Assistant. While ADB can’t see the phone, LMSC sees it just fine and I was able to rescue/reinstall the stock OS successfully, or so LMSC said. Unfortunately, LMSC doesn’t seem to fix whatever is wrong with the recovery. Interestingly, “N/A” no longer appears after Vol-DN/Power and select Recovery Mode, the black screen now says “bad key”, followed a little while later by the Android logo with a “!” in the middle of the screen and “No command” below it.
And that’s the hole I now reside in. Despite considerable searching/reading here at XDA, I'm at a total loss for what to do next.
SOOOO, I’m hoping someone can help me:
1. Fix the N/A black screen
2. Get into a mode that ADB can see
3. Properly install TWRP
Thank you in advance,
Tenaya

Did you flash the copy-partitions.zip while in TWRP?
Maybe you could borrow some ideas from the official install instructions for LineageOS.
Install LineageOS on channel | LineageOS Wiki
wiki.lineageos.org
I had some strange intermittent USB connectivity issues with a few Moto G7 Plus devices with my main laptop, but was fine connecting on a 12 year old desktop computer. So perhaps you could check to see if adb connects on another machine. Only other idea I have is to somehow flash back to stock again with fastboot.
[Guide][Channel][Stock]Moto g7 play Factory Firmware Images
Moto g7 play Android 9 and 10 Factory Firmware Stock Images Info Updated on 23-11-2020 Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download...
forum.xda-developers.com

zpunout,
Thank you for your response.
zpunout said:
Did you flash the copy-partitions.zip while in TWRP?
Click to expand...
Click to collapse
No, I didn't know I needed to; nothing about that is mentioned by TWRP.me.
This is unknown territory for me, but your question sparks a thought for me. I wonder if 1) The stock recovery is in the "other" slot, and 2) there is some way to boot from it. That could be a way to sidestep the ADB devices problem I'm having?
zpunout said:
So perhaps you could check to see if adb connects on another machine.
Click to expand...
Click to collapse
At the moment, I have no way to do that. I don't think the USB connection is the culprit, ADB "sees" the phone just fine while the phone is in the stock OS, just not in recovery (EDL?.
zpunout said:
Only other idea I have is to somehow flash back to stock again with fastboot.
Click to expand...
Click to collapse
That's my current plan, but FASTBOOT won't flash anything while ADB devices won't/can't see the phone. I'm hoping someone has a workaround of some sort for that.
Tenaya

Hi, first of all lets set some things straight, you are experiencing a Boot Loop, in other words a software brick. (Soft Brick) now luckily these are fairly simple to fix. Sorry to break it to you but the N/A Screen won't disappear, that used to be the Blue/Yellow Motorola Splash Screen, but since you unlocked your phone it'll only show N/A but thats okay there are tools that can help you customize this and change it later on.
Now why is it on a boot loop you may ask, well that is because there is no more operating system to load in. But worry not, try to get into your bootloader, and try to connect adb through there.
Tenaya43 said:
Ok, so I’ve run myself off the road into a deep hole and am hoping someone can help me climb out and get back onto the correct path.
I have a Motorola Moto G7 Play 1952-4 (channel). My goal is to install TWRP, and LineageOS 18.1 with GAPPS. Root is not important at the moment.
Here’s what I did:
After successfully unlocking the bootloader (thank you Motorola), I downloaded TWRP for Chanel from the TWRP.me site. My plan was to first install TWRP, then use TWRP’s install feature for LoS 18.1 and the GAPPS.
To install TWRP recovery, I followed the instructions on the TWRP site. After starting the ADB server on my Windows 10 PC and booting the phone into the stock recovery, I used “adb boot twrp-3.5.2_10-0-channel.img” to temporarily boot into TWRP recovery. I then used ADB to push TWRP.zip onto the internal SDCARD. I used TWRP’s install feature to install "twrp-installer-3.5.2_10-0-channel.zip", presumably to both slots. To the best of my memory, everything completed correctly.
BUT . . . when I powered down the phone and attempted to boot into recovery, all I got was a black screen with a small N/A in the upper left corner instead of the familiar TWRP screens. After a while, the phone booted itself into the stock U.S. Cellular Android 10 (Hell Oh - Moe Toe). I've done several power-off/power-on cycles to no avail. I am able to get to and use the stock OS.
So, like TWRP.me suggests, I figured I’d just flash it back to stock and start over. Um, nope. I can Vol-DN/Power to the bootloader menu, but “adb devices” doesn’t see the phone, preventing me from flashing anything. USB Debugging is enabled and the phone says "USB Transfer Mode: Connected". “adb devices” sees the phone while Android 10 is running, but as soon as I boot into recovery, the phone “disappears” from ADB.
The only other thing I could think to do was to use the “Rescue” function in the Lenovo/Motorola Smart Assistant. While ADB can’t see the phone, LMSC sees it just fine and I was able to rescue/reinstall the stock OS successfully, or so LMSC said. Unfortunately, LMSC doesn’t seem to fix whatever is wrong with the recovery. Interestingly, “N/A” no longer appears after Vol-DN/Power and select Recovery Mode, the black screen now says “bad key”, followed a little while later by the Android logo with a “!” in the middle of the screen and “No command” below it.
And that’s the hole I now reside in. Despite considerable searching/reading here at XDA, I'm at a total loss for what to do next.
SOOOO, I’m hoping someone can help me:
1. Fix the N/A black screen
2. Get into a mode that ADB can see
3. Properly install TWRP
Thank you in advance,
Tenaya
Click to expand...
Click to collapse

HellxDo,
Thanks for the reply.
After I used LSMC to "rescue" the phone, it stopped displaying N/A" and began showing "Bad key". Different, but not better.
HellxDo said:
Now why is it on a boot loop you may ask, well that is because there is no more operating system to load in.
Click to expand...
Click to collapse
Hmmm . . . The phone currently boots into the stock rom (U.S. Cellular Android 10) if I wait a while after "Bad key" displays. If there's no more OS to load in, how do it do dat?
HellxDo said:
But worry not, try to get into your bootloader, and try to connect adb through there.
Click to expand...
Click to collapse
My (limited) understanding is that the only way to "get into" my bootloader was with the Vol-DN/PWR button combination. When I do that , I get the bootloader menu, but ADB doesn't/can't see the phone - nothing is listed when I run ADB devices and fastboot won't/can't flash anything.
Is there a different/better way to get into my bootloader?
Tenaya

And the adventure continues. Here's some more information.
While continuing to research this, I was wondering if there was another way to boot the phone into EDL mode and Google found some instructions at thecustomdroid.com for using ADB to boot the phone into EDL. I booted the phone to the stock OS and used the command adb reboot edl. The phone immediately went blank, followed shortly by the "bad key" message. After a while it again booted into the stock rom.
I still cannot use fastboot because it doesn't/can't see the phone.
I have also discovered that if i use VOL-UP/PWR, the phone boots directly to "bad key", followed by the stock rom. Another dead end.
I also used LMSC to "Rescue" the phone again and learned several things:
While LMSC is running, it boots the phone into the bootloader menu and begins to flash. If I do adb devices while LMSC is flashing, the phone STILL doesn't appear in the list.
LMSC definitely flashed the stock OS - when the phone rebooted, it was back to the stock OS Android start screen as if it had never been configured.
There is still no recovery and I still can't flash anything.
LMSC is somehow able to flash without a recovery present.
Anyone have any other ideas?
Tenaya

Tenaya43 said:
And the adventure continues. Here's some more information.
While continuing to research this, I was wondering if there was another way to boot the phone into EDL mode and Google found some instructions at thecustomdroid.com for using ADB to boot the phone into EDL. I booted the phone to the stock OS and used the command adb reboot edl. The phone immediately went blank, followed shortly by the "bad key" message. After a while it again booted into the stock rom.
I still cannot use fastboot because it doesn't/can't see the phone.
I have also discovered that if i use VOL-UP/PWR, the phone boots directly to "bad key", followed by the stock rom. Another dead end.
I also used LMSC to "Rescue" the phone again and learned several things:
While LMSC is running, it boots the phone into the bootloader menu and begins to flash. If I do adb devices while LMSC is flashing, the phone STILL doesn't appear in the list.
LMSC definitely flashed the stock OS - when the phone rebooted, it was back to the stock OS Android start screen as if it had never been configured.
There is still no recovery and I still can't flash anything.
LMSC is somehow able to flash without a recovery present.
Anyone have any other ideas?
Tenaya
Click to expand...
Click to collapse
If "fastboot devices" can't see your device while in bootloader mode, that could be the same issue I had relating to your USB compatibility with your computer. Try to borrow someone else's computer, install "platform-tools" to see if the "fastboot devices" command works.
If that works, next see if the command "fastboot getvar all" works. You should get many lines of info come up. If it gets stuck after a couple of lines, then the symptoms are the same as what I had. I have a bunch of really old laptops and a desktop sitting around with platform-tools just for this issue. I have heard others say that plugging the phone in via a USB hub sometimes gets fastboot to connect properly, but I haven't had success yet.

OK, some progress.
I found this:
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
kenzo has graciously hacked fastboot.exe to force the phone into EDL mode. Using that, the phone booted into EDL and fastboot devices can now "see" the phone. Thank you kenzo.
BTW, kenzo's fastboot-edl isn't G7 Play specific, it was originally for the Xiaomi Redme Note 3 and seems to work for some other Android phones as well.
I'm still working on getting TWRP and LoS installed, but at least fastboot can talk to the phone.
zpunout said:
I have heard others say that plugging the phone in via a USB hub sometimes gets fastboot to connect properly
Click to expand...
Click to collapse
I also had no luck with a USB hub.
I haven't tried another computer yet; I'm going to see what I can accomplish with fastboot-edl.
Tenaya

fastboot oem blankflash