I tried to root the device, however the custom bootloader couldn't load at all, and no attempt worked at all (Kingroot failed multiple times).
Due to the expenses of the sim unlock and the relative age of the phone, my mother decided to buy me a new phone to replace my old Nokia Lumia. Forgetting that I should have taken precautions, I did a factory reset on this one, only to get stuck on the Huawei screen. The phone is undetected by both ADB and my PC.
Can I unbrick it some way?
EDIT:
The problem got solved somehow, however I still cannot do a factory reset on my phone, which would be necessary for selling it. I try to restore the default bootloader.
shapeshiftinglizard said:
I tried to root the device, however the custom bootloader couldn't load at all, and no attempt worked at all (Kingroot failed multiple times).
Due to the expenses of the sim unlock and the relative age of the phone, my mother decided to buy me a new phone to replace my old Nokia Lumia. Forgetting that I should have taken precautions, I did a factory reset on this one, only to get stuck on the Huawei screen. The phone is undetected by both ADB and my PC.
Can I unbrick it some way?
EDIT:
The problem got solved somehow, however I still cannot do a factory reset on my phone, which would be necessary for selling it. I try to restore the default bootloader.
Click to expand...
Click to collapse
Install your default rom with twrp and do factory reset.
Ps: to root use Magisk.
.
Related
We have a number of LG G2's at work and I am in the process of swapping one to another as there screen is scratch and that would be better going to the lads on site.
Any way I backed up using pc suite. all went well. I did a soft wipe of the phone, put in my google account details and tried to carry out a restore from pc suite but i get an error saying an error occurred during restore.
This happens over and over again. Its almost as though the phone wont restart itself.
I have tried to put the phone into recovery mode to do a hard reset but it wont go in to it. It keep restarting or just boots up.
Getting these phones into recovery mode is something I have done time and time again and never had a problem doing so.
Am I looking at a faulty device do you think?
Thanks in advance for your help
Hello,
I am writing this thread for a friend of mine. He owns a Z1 - stock ROM, locked bootloader.
Today it started looping and I tried to fix it (telling him over a chat what to do). It goes through the bootanimation and then dies or while optimizing apps, or while starting them.
What we tried:
1) Wipe cache
2) Factory reset
3) adb sideload the current official CM onto it
Nothing helped, the error stays the same. We also tried this http://forum.xda-developers.com/showpost.php?p=64458076&postcount=4 but it never really recognised the phone (despite using the correct drivers and following the procedure) - it did not appear under ports (Windows 10?).
Is there any other way to unlock this goddamn phone? My Androids so far had an easily unlockable bootloader via fastboot. This would have, too, but in order to unlock the bootloader via fastboot you first have to allow this in the developer settings - which we can not reach due to the loop.
If you know some way to get a working ROM onto it, we would be very happy. In the end we will end up unlocking the bootloader and flashing another Recovery and ROM anyway. We only need some way to achieve this. I expect the way to do this will be the QPST thingy. Any ideas why it did not recognise the phone? He does not own a PC with another OS than Win10...
Thanks in advance for your help,
Moritz
EDIT: Looks like the sideload did work - after tens of reboots it finally succeeded and bootet straight into the ROM.
Took a lot of attempts, strangely.
Proceeding to unlock it
Mine does the same boot loop on CM13. After tons of different tries to fix it, i think it could have something to do with my fingerprint sensor which is not working anymore.
Maybe there is some kind of hardware malfunction and android crashes while initializing that piece of hardware.
Hi all,
This is my first post here, I'll try to include everything but please let me know if I am missing any info. I'm using Windows 10, my phone is using Stock ROM 6.0.1, carrier unlocked from Telus to Rogers but bootloader shows device is Locked.
TLDR: I'm trying to recover the photos from my soft-bricked phone before doing a factory reset. I've tried to manually flash the firmware with fastboot by following the steps in service.xml, but the commands all appear to return OKAY without errors but there's no change in the phone's behaviour.
More Info: I've spent the last 2 days reading up on here and elsewhere online to learn as much as I can. I am honestly not sure what caused it the soft-brick. I was using my phone normally yesterday morning when it froze while browsing Facebook, so I tried to power it down, but I got caught in a bootloop and it wouldn't go past the logo screen. It's part of my morning routine to run updates, and I often (though not yesterday) transfer files to/from the phone through a USB cable, so could it be an internal memory problem? Other possibilities, while I was careful ultimately I did download an apk for Pokemon Go before it was released in my country, and I did also download a battery saving app, so there's risks from both of those but the timing seems wrong...
I can get into bootloader and recovery mode, but not factory mode. Wiping the cache partition did not help. The only way to power the phone down is from bootloader, otherwise the phone goes straight to the logo screen.
I've installed ADB/Fastboot using the 15 Second ADB Installer here, and believe I have all of the correct drivers from the WinDroid install. However I did not enable USB Debugging before this happened, so the only way I can get ADB to see the devices is to go to "Apply update from ADB" in recovery mode, but running "adb devices" brings the phone up as sideload. If I'm in bootloader, "fastboot devices" sees it, "adb devices" comes back empty.
I used the file XT1563_LUX_RETCA-ROGERS_6.0.1_MPD24.107-52_cid14_subsidy-RGRCA_CFC.xml.zip from the File Factory folder, and it looks right according to the software version in the .xml files, but I'm still new to this and I'm not sure if my best guess is educated enough.
In general I'm not too squeamish about voiding the warranty and don't care about losing my apps, it's the photos that I really do not want to lose (shame on me for not backing those up!). I'm wondering if there's a way to get my photos back before unlocking or doing a factory reset, but if there's a reliable recovery software I can use after the fact I may have to bite the bullet.
TIA for any help.
An update. I chose to wipe user data (NOT including personalized content), the phone rebooted but is looking different from before. Which in and of itself is alright, but makes me wonder if I flashed the correct firmware...?
During the setup process, I was given the option to restore data from 3 days ago, which was when the soft-brick occurred. I chose to recover most of my apps, however I can't see any photos. I tried Recuva but it could not see anything, I'll be trying trying the Wondershare Dr. Fone Android Recovery program and hope it finds the photos.
Hi all. So I have a frustrating issue with my phone after having updated to the last official firmware from the Asus website. I noticed that the phone operation was very slow, so I decided to do a factory reset from recovery. Everything went well until I am somehow locked out of my phone via FRP. The weirdest thing is that instead of asking for google credentials, it's asking for a pattern, which I am correctly inputting but it refuses to recognize it. So now I'm stuck with a locked out phone. Am I SOL at this point or is there a way to get past this other than taking it to a service center?
Things I've tried that haven't worked:
1. tried to erase user config in fastboot (returned error FAILED)
2. wiped all data in recovery
3. tried to flash to an older version via asus flashtool but didn't work as the device isn't recognized
Any help would be greatly appreciated.
xenoche said:
Hi all. So I have a frustrating issue with my phone after having updated to the last official firmware from the Asus website. I noticed that the phone operation was very slow, so I decided to do a factory reset from recovery. Everything went well until I am somehow locked out of my phone via FRP. The weirdest thing is that instead of asking for google credentials, it's asking for a pattern, which I am correctly inputting but it refuses to recognize it. So now I'm stuck with a locked out phone. Am I SOL at this point or is there a way to get past this other than taking it to a service center?
Things I've tried that haven't worked:
1. tried to erase user config in fastboot (returned error FAILED)
2. wiped all data in recovery
3. tried to flash to an older version via asus flashtool but didn't work as the device isn't recognized
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Ok i had the exact problem the latest patch for the device , i manually updated to oreo 8.1, has some bug that sometimes it doesnt recognise pin or pattern after some reboots it recognized it but it's not persistent as it stopped working.
I was able to fix it by flashing an older version with sp flashtool. You need to download and properly install SPFlashtool and everything it needs then you have to search for an spflashable rom that it's compatible with the one you have.
my phone suffered a fall and its display is cracked and Xiaomi Service Centre says this cannot be repaired as replacement screens are no longer in stock and this phone is only showing up on my computer in fastboot mode and its not even switching on, so is there any way to recover my data?
svkr4u said:
my phone suffered a fall and its display is cracked and Xiaomi Service Centre says this cannot be repaired as replacement screens are no longer in stock and this phone is only showing up on my computer in fastboot mode and its not even switching on, so is there any way to recover my data?
Click to expand...
Click to collapse
I don't think you could
Even if your Bootloader was unlocked and if you had TWRP installed, and if you could reboot to TWRP, you should still use the touch screen to enter your pin/pass/pattern that TWRP could decrypt storage - only after that you would be able to use MTP from TWRP to transfer the files to your PC
Too many "ifs"- you didn't mention unlocked Bootloader and TWRP - hence I assume you never did that (unlock BL, install TWRP)
If you didn't, you cannot now (even to unlock BL) once your screen is broken
If BL was unlocked (again, you didn't mention, hence assuming not), you could disk-dump your data to PC, but as the partition img, and then it would not be possible (without the help from your phone - but no help since your screen is broken) to decrypt the files
All in all, I don't see how could you make it now
---
One must periodically transfer his photos, etc to PC and backup whatever is possible through Google and I also use Mi Cloud for backing-up
I recently had a similar case. My phone was no more booting except to the Fastboot
Screen was not broken, Bootloader was unlocked and I was able to reflash MIUI and get the phone working again
However, by Factory reset (I needed to reflash the OS), all my data were wiped from the phone
But I did not loose almost anything. I had copy of my photos on the PC, just from a couple of days before the disaster
By help of Google and Mi Cloud, I easily restored contacts, calendar, WA chats, even WiFi passwords (by Mi Cloud)
I needed one day to reset the phone, but eventually I did not loose anything essential
I managed to do this some time ago with an older phone but maybe it works, I don't remember the details but it was something along these lines:
1. Load TWRP using fastboot with `fastboot boot twrp.img`
2. Access the phone via ADB with `adb shell`
3. Pull the data with however adb pulls it (I think `adb pull <path>`)
The other option you have is searching ebay or other shops for screen replacements por Mi9T, they might be fake replacements but as long as they work good enough for you to access your phone and pull the data out they're good enough.
Also, I forgot, make sure the broken part is the screen, if the phone itself is dead then we enter the realm of forensics and I doubt it's worth your trouble (and money) to recover that data.