My Xiaomi Redmi Note 7 (lavender), gave Brick after formatting the cell phone, which was with a Lineage ROM, but immediately the cell phone would not boot, the ROM corrupted and to make the recovery worse, the TWRP, apparently it ended up corrupting, it does not enter and hangs in the TWRP logo.
Fastboot mode still works, but I can't get any device to recognize it, nothing just happens. I've tried ADB, MI Flash and some other programs, but it ends up not working, My computer can't recognize the Note 7. I switched cables and tried different ways, using my second phone as a command prompt, but it still didn't recognize it. Just need to try another computer
I wanted to know if the problem is reversible, because if not, I have a screened brick
I think the connector may be defective but I think it's unlikely as it worked perfectly before
If any expert can help me, that would be great
Sorry for the robotic English, it's not my mother tongue
1Henryx said:
My Xiaomi Redmi Note 7 (lavender), gave Brick after formatting the cell phone, which was with a Lineage ROM, but immediately the cell phone would not boot, the ROM corrupted and to make the recovery worse, the TWRP, apparently it ended up corrupting, it does not enter and hangs in the TWRP logo.
Fastboot mode still works, but I can't get any device to recognize it, nothing just happens. I've tried ADB, MI Flash and some other programs, but it ends up not working, My computer can't recognize the Note 7. I switched cables and tried different ways, using my second phone as a command prompt, but it still didn't recognize it. Just need to try another computer
I wanted to know if the problem is reversible, because if not, I have a screened brick
I think the connector may be defective but I think it's unlikely as it worked perfectly before
If any expert can help me, that would be great
Sorry for the robotic English, it's not my mother tongue
Click to expand...
Click to collapse
For fastboot you just need to update the drivers, run the same process you did sometime, when it, firstly, worked. Remember that a corrupted device must have the drivers updated, a kind of communication lost, nothing more.
I´ll upload some screenies from the process you need to do:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Once you get it, repeat the process, i.e. boot to recovery and flash the ROM.
Related
I've probably used the LG Flash Tool 10 times the past week on both my home and work computer with no problems. Last night I flashed the KK bootloader and a stock 5.0.2 ROM (after tot'ing back to 4.4.2, rooting, etc).
It hangs at the LG logo and that's where I'm stuck. I tried going into Download Mode, but suddenly both of my computers won't see the phone and give me an error in Device Manager. I've tried uninstalling / reinstalling the drivers as well. Why in the world would that happen unless somehow Download Mode was corrupted, possibly? But it goes into Download Mode fine, and appears to look right...
I've tried getting into recovery but can't. When it should load up TWRP (after telling the G2's "stock" recovery screen I do want to reset), I get the green spinning Android (not the red exclamation) for a second, then it tries to boot up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any advice would be appreciated as I've never run into this before.
So when the green Android popped up, I tried to hit a combination of the volume and power keys and WAS able to get into recovery. Unfortunately, it appears, somehow, TWRP was overwritten by the stock recovery. I have no idea how that could've happened. Or does stock recovery technically stay in place since this is "loki'd" and not actually unlocked? And if so, is there some way to get back to TWRP that I'm unaware of?
To add to the weirdness, when I plug it in to charge, it doesn't pull up the battery like it usually does when powered off, it just tries to boot up again...
If I could just get the computers to recognize it again...
Installing the LG PC Suite got my drivers to a point where it could recognize it while in Download Mode. MTP still didn't work, but that didn't matter for Download Mode. Not sure what happened, but at least I was able to flash it back again.
I've seen this kind of problem alot here but here's my problem and why nothing helps.
Basically I wasn't updating my device I was just texting or something like that when my phone went black except the system outline(you know time, signal, wifi/net conection etc. on upper part of phone) so I forced it to shoot down and after that when I try to turn it on it's stuck at ASUS logo(I can't take picture of my phone but it's same as on the picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now I tried factory reseting it and entering the recovery mode, none of it seems to help and the problem is that my PC can't detect my zefone when I connect it(and I'm pretty sure it wasn't detectable before this problem either so I don't think those are connected issues).
Any suggestions?
nc96 said:
I've seen this kind of problem alot here but here's my problem and why nothing helps.
Basically I wasn't updating my device I was just texting or something like that when my phone went black except the system outline(you know time, signal, wifi/net conection etc. on upper part of phone) so I forced it to shoot down and after that when I try to turn it on it's stuck at ASUS logo(I can't take picture of my phone but it's same as on the picture:
Now I tried factory reseting it and entering the recovery mode, none of it seems to help and the problem is that my PC can't detect my zefone when I connect it(and I'm pretty sure it wasn't detectable before this problem either so I don't think those are connected issues).
Any suggestions?
Click to expand...
Click to collapse
are you tried flashing system via ''apply update from adb'' command of recovery
Yes, as grady_8 said, Flash update using ADB from your recovery, but you need ADB and Fastboot drivers first, then your PC will able to detect your ZF.
https://forum.xda-developers.com/zenfone-5/help/bootlooped-bricked-returning-to-stock-t3358662
try this guide
You must be downgrade first, because the lolipop firmware not support adb flash. Download firmware save at same folder with file extracted. (Version . UL_WW.2.22.40.54-user.zip. )extract it to new folder, then click shift+right mouse, open command here. Then type fastboot flash boot boot.img then' fastboot flash recovery recovery.img , then ' fastboot flash fastboot fastboot.img. after that reboot to recovery manualy, then aply update from adb . Then In CMD type ' adb sideload <the name of firmware>.zip (example = adb sideload UL_WW.2.22.40.54-user.zip ) Wait the progress. Then finish.
Hello to all who read this.
My phone only shows this two modes but does not get into recovery mode at all, it only shows the first step and then it reboots form the start:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't get into TWRP, even if I flash a new recovery with fastboot and run the boot command.
That said I can open fastboot mode and qfil mode.
The problem occurred last night I was watching youtube and in the morning the battery on the phone was fully drained and I couldn't boot into the lineageOS 16 that I'm using (had for 1 month).
The LED light in the top right corner is never lightning up, only when is fully drained then it shows the battery is empty and some blinking red light on the LED.
Well I tried :
- to install/run TWRP it couldn't let me run it
- to qfil the stock ROM and it did let me flash it but it was the same when I pressed the power button after the flashing process
- to use the "update" command in fastboot mode to update the stock ROM on to the phone and it said:
error: update package 'update.zip' has no android-info.txt
Does anyone know how to solve this?
Please help me!
All best,
Jasmin
I had the same issue with X727. Your battery is faulty and needs to be replaced. I got mine from this guy and received an original LeEco battery albeit with 2016 manufacturing date but it works well and phone does not reboot anymore.
nwaves said:
I had the same issue with X727. Your battery is faulty and needs to be replaced. I got mine from this guy and received an original LeEco battery albeit with 2016 manufacturing date but it works well and phone does not reboot anymore.
Click to expand...
Click to collapse
Okey, thanks for the replay.
Hi, Jasmin slayer!
Did that Work for you to replace the battery? If not, try to flash some bootloader and verify , If twrp Boots again after flashing. Remember you need twrp 3.3.1 for Andro Pie!
LupusC said:
Hi, Jasmin slayer!
Did that Work for you to replace the battery? If not, try to flash some bootloader and verify , If twrp Boots again after flashing. Remember you need twrp 3.3.1 for Andro Pie!
Click to expand...
Click to collapse
I have the same problem my Le pro 3 x720 device. It is in a boot loop. I wonder if changing the battery will work.
Howdy everyone...
OnePlus 7t Pro McLaren edition (International Edition **NOT T-MOBILE**)
Model: HD1913
Current Software Build: Oxygen OS 10.0.5.HD01AA (OTA update when I first unboxed).
I am having issues trying to return to stock. I rooted the phone with a combination of a couple guides found here (https://forum.xda-developers.com/7t-pro/how-to/10-0-3-patched-boot-image-oneplus-7t-pro-t3986351 and . I noticed after doing that I was missing the stock Oxygen apps and my build information was missing data. Not a huge deal, but I need to wipe the phone and start from scratch anyway, for other reasons. I decided to go back to stock if I have to redo everything anywhere.
First thing I tried, I got the stock firmwares (https://forum.xda-developers.com/7t-pro/how-to/oneplus-7t-pro-repo-oxygen-os-builds-t4003455). And this is where my issues started. My software build is weird... I have the HD1913, however my software build is HD01AA. Per that post, I should have HD01BA. I grabbed both of them for giggles, put them on my storage and booted into TWRP. Tried to flash the HD01AA (since that was what I have now), and it failed. Tried the other one, same issue. I'm getting a bunch of errors while trying to mount the system ("System unable to mount: invalid argument").
Second thing I tried, was to use the built in software update that OnePlus says to use (through the system update). It wouldn't install them (surprise).
Third attempt... Using the MsmDownloadTool (https://forum.xda-developers.com/7t-pro/how-to/op7tpro-unbrick-tool-to-restore-device-t4002909) I downloaded both versions cause I don't know which to use, and followed the instructions to get the phone into the mode. Turn the phone off, hold the vol up button and plug the cable in (very simple). It shows up connected in the software. Exactly 5 seconds later, the phone reboots and boots normally... I repeat this process aprox. 2.3 million more times. It does not matter what USB-C cable I use, the port on my computer, or how long I hold the buttons. The phone will boot into the download mode (or whatever it's called) show up as connected in MsmDownload and then reboot.
The phone works. I am still able to boot it up.... All I want to do is get this phone back to stock. I don't HAVE to, but now that it's fighting me, I have to beat it...
imgur.com/a/KhBGwao
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay - After sacrificing an iPhone to the Android God, I got it.
Instead of using the button combination to get into EDL Mode, I found an article that gave an adb command (adb reboot edl) to get to it. It did not reboot this time, and I was able to flash HD01BA to it, which matches what the phone should have...
so i took some break from android for couple of years and it seems somethings have changed since then, i had oneplusone so rooting wasn't new to me, but i got my oneplus 6t rooted it straightaway i had some issues with TWRP not sticking after i flash and had some issues were i couldn't find the directory to install roms but all that was fixed, had some other isues with using my banking app but that was sorted a swell so i was having fun.
a mouth or so ago i was wanting to get rom and my TWRP wasn't there it kept rebooting into fastboot menu, so i tried to flash TWRP again and it wasn't working so i messed up with boot img with all sorts of command lines related to flashing boot img, now my phone is dead for good i don't see how it can be fixed when the boot is corrupted i cant even boot into fastboot.
when i tired to boot into fastboot it wont work it stuck in that unlocked bootloader screen i have tried every combination available and it reboots into that. please help if you can.
please if i didn't explain my self properly ask away i just forgot what i did it been a while.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try MSM tool
As mentioned, neither Fastboot or recovery need to work for the MSMTool to work.
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Note the screen wont do anything, the phone will just be recognized by the MSMTool.
Dafelleant said:
Try MSM tool
Click to expand...
Click to collapse
you guys have no idea how great full i am its finally working from dead phone in the storage to daily driver.. again you can always rely on xda members.
Yeah, OnePlus is one of the only phones that is truly un-brickable. Even Google pixels do not have working MSM tool.