Phone was updated to MIUI 11.0.2 China ROM last month. Unwanted content pops up like crazy. Run the debloat script from xda. Phone worked for a day and then start to reboot itself into recovery constantly. Locked Bootloader. Phone was registered with a xiaomi account. Do not remember if usb debug was enabled or not. Select MiAssistant from recovery, plug the usb cable to computer and "run adb devices" command list the phone as sideload status. Since I did not back up my data yet, I would like to know if there is a way I could save my data.
Here is what I have tried so far.
1) Tried to use QPST tools to save the data before I format the phone. I opened the back cover and used test point to enter edl mode. I can see the comm port (9008) but QPST tools could not make connection. It hang at recognizing the phone. So it seems I could not use QPST to save my data.
2) Tried to use MiAssistant tools to flash MIUI 11.0.2 China ROM to the phone to see if the phone can be recovered as MiAssistant can flash the recovery ROM without wipe the data. Downloaded and installed the MiAssistant 3.0 beta, and then downloaded MIUI 11.0.2 China ROM. The MiAssistant verified ROM correctly and started to flash the ROM. During flashing, while MiAssistant show progress at about 33%, the phone screen would show 90.49% and stopped increasing. The MiAssistant would keep increase till 100% and reboot phone but the phone screens stopped at 90.49%. After phone rebooted, it reboot into Mi-Recovery mode again. So flash failed. After enter MiAssistant screen again, run the Recovery pullcache command from MiAssistant tools will get the log from the phone. After went through the log files, I found the flash process stoped with error status "INSTALL_CORRUPT". Google the word "INSTALL_CORRUPT" and found no solution for the problem.
Would really appreciate if anyone can help me bring back the phone without wiping the data.
I have another whyred phone with the same version of ROM if that helps.
Thanks.
Related
Here is my issue..I have been rooted since I got the phone and actually rooted both of my EVO's. Last week I decided to go back to Fresh Rom 1.0 and inadvertently flashed a new theme at the same time. Did not flash the ROM and then go back in and flash the theme. As a result, the phone went into a continual cycle of rebooting the loading screen ( for Fresh users you know it has the little guys and says FRESSSHHH). Well that happens over and over again.
The only option I have is to take battery out and go into the bootloader mode. MY problem is this:
* Once in bootloader mode, I can't reflash because when I go into the recovery mode, the recovery says " ADB server is out date" and scrolls thru a few lines an disappears. I've tried every thing suggested to me and still have not been able to fix that.
* Cannot access root of SD card because system doesn't recognize the phone is attached.
* Tried to load PC36IMG file on the card manually and that loaded but I can't get to the restart option. It finds the file but does not give me the restart commands.
I'm at wits end right now. I tried the OTA Recovery but since I cannot connect to the computer, it won't run either.
Please help......
Restore a nandroid.
RUU start over.
I tried to do that but the computer - htc sync won't recognize the phone so I can't RUU again. When I get to the end of the process it tells me either the phone isn't connected to the USB or the USB isn't connected to the computer.
You phone says the ADB server is out of date when you boot into recovery?
It sounds like you are not completely rooted.
You should be able to volume down and power on. Then choose recovery. From there you can restore a backup. That should also give you ADB access to the phone (if you are fully rooted)
If you are not fully rooted, and you have to run some bat file on your computer to get the phone into full recovery, you may be skrewed.
No, the computer says that when I go into recovery mode and have the black screen and red triangle on it. I then go to the computer and try and run the recovery file that I've been running as I've flashed 10-12 ROMS already. The CMD screen on the computer comes up as ADB Server is out of date...and another line or two scrolls by and then it disappears, never connecting to the phone and going into the next screen where I can wipe or flash from SD..etc..
Sounds like you did not complete step 2 of the root process. You should be able to enter recovery without the use of a computer.
Reboot your computer and try again, if you still get errors then I am out of tips.
So after accidently wiping everything I had on both SD and Internal memory trying to make a custom rom work, I was stuck with a phone that only has TWRP on it, basically. Now after I've been through this guide TO THE LETTER: http://www.droidviews.com/install-stock-android-marshmallow-lg-g3-d855-using-twrp-recovery/ I can see it installed an OS but I cant seem to get my phone to load it! SO then I tried entering recovery mode and getting back to default, it didn't change anything, so I tried installing Zoe rom (https://forum.xda-developers.com/lg-g3/development/zoe-rom-v1-0-mm-6-0-stock-v30a-d855-t3402087) and It STILL ONLY LOADS TWRP even though the installation seemed to be successful!
So what do I need to do? Just flat out delete TWRP? or what? Pleas advise as I'm desperate. If needs be, redirect me to how to just completely reinstall everything from scratch to 6.0 or 7.0 (preferably). I was on 4.x.x for ages and I just wanted to update, instead destroyed my phone. Sigh.
UPDATE: Another thing I've tried is to flash it with KDZ file from the PC. I can see the phone, I can transfer files to it, but windows DOES NOT recognize in the device manage so when I tried to use the flash tool, after clicking "Start" it pops a new window which gets to 60% and then stops saying the phone is not connected to the pc.
Malkishua said:
So after accidently wiping everything I had on both SD and Internal memory trying to make a custom rom work, I was stuck with a phone that only has TWRP on it, basically. Now after I've been through this guide TO THE LETTER: http://www.droidviews.com/install-stock-android-marshmallow-lg-g3-d855-using-twrp-recovery/ I can see it installed an OS but I cant seem to get my phone to load it! SO then I tried entering recovery mode and getting back to default, it didn't change anything, so I tried installing Zoe rom (https://forum.xda-developers.com/lg-g3/development/zoe-rom-v1-0-mm-6-0-stock-v30a-d855-t3402087) and It STILL ONLY LOADS TWRP even though the installation seemed to be successful!
So what do I need to do? Just flat out delete TWRP? or what? Pleas advise as I'm desperate. If needs be, redirect me to how to just completely reinstall everything from scratch to 6.0 or 7.0 (preferably). I was on 4.x.x for ages and I just wanted to update, instead destroyed my phone. Sigh.
UPDATE: Another thing I've tried is to flash it with KDZ file from the PC. I can see the phone, I can transfer files to it, but windows DOES NOT recognize in the device manage so when I tried to use the flash tool, after clicking "Start" it pops a new window which gets to 60% and then stops saying the phone is not connected to the pc.
Click to expand...
Click to collapse
I just got over something like this this morning. First, you need to ensure you have the LG Universal drivers installed for your phone. Get them here.
Next, reboot your machine.
After this, I made sure the PC recognized all 3 modes of my phone, TWRP mode (boot to TWRP, connect), Download Mode (boot to download mode with cable) and, at least in my case, the flashing lights mode (shows up as QHUD Bulk or something).
After that, I ran the KDZ restore program successfully.
Good luck and let me know how it goes.
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.
How can I fix it without losing my data or at least make a backup
I have a question. I downloaded an update yesterday for Mi Max 3. The screen stayed black with the MI logo for hours. I tried the following but didn't work:
- Connecting to Mi PC suite, but it isn't recognizing the device.
- Downloaded many drives for the USB, but still the device is not being recognized.
- MiFlash recognize the device, but when I downloaded the Rom (both recovery and nitrogen) it is mentioned can't find file flash all.
- I tried to put some commands such as adb back up, but it informs me no device found.
- I tried to work whether on fastbot mode or without fastbot, without success.
I want to know what should I do, I don't want to lose the data on the phone.
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