Long story short my V521 is bricked, as far as I can tell.
Here’s what happens:
Turn on.
Shows ‘can’t detect corruption’ unlocked boot loader screen.
Shows LG screen.
Reboots.
If I attempt factory reset via hardware buttons, I get a Nougat circle that says ‘Erasing...’, then reboots into the above loop.
Download mode seems to be nonexistent, as it just never works. My PC does not recognize it as the right device for LG support tool or Uppercut to find it, despite all drivers being installed.
ADB was working until stock recovery flashing (which I thought was gonna be a fix...)
And now I don’t know what to do.
Basically, the only thing I have is an unlocked bootloader.
Someone. Please.
Help me.
:crying:
Related
Hey all
First of all, this is the first time that I'm trying to root a phone, and it didn't go well.
I have an LG G4 with Marshmallow installed on it. Found out that I needed to do, and it didn't look too hard to me, so I tried it.
I managed to unlock my phone's bootloader, and get TWRP onto it. (Which apparently was needed in order to get root access on 6.0)
I flashed the system image. Got a confirmation that everything went well, so I restarted (via the TWRP menu).
And now, my phone is stuck in the booting process. (displays the logo + "Bootloader unlocked" in the left upper corner.)
I tried a factory reset via the system recovery, didn't change anything.
Since I voided my warranty, is there a way to fix this myself? (I haven't found anything that helps me so far)
hptmdagobert said:
Hey all
First of all, this is the first time that I'm trying to root a phone, and it didn't go well.
I have an LG G4 with Marshmallow installed on it. Found out that I needed to do, and it didn't look too hard to me, so I tried it.
I managed to unlock my phone's bootloader, and get TWRP onto it. (Which apparently was needed in order to get root access on 6.0)
I flashed the system image. Got a confirmation that everything went well, so I restarted (via the TWRP menu).
And now, my phone is stuck in the booting process. (displays the logo + "Bootloader unlocked" in the left upper corner.)
I tried a factory reset via the system recovery, didn't change anything.
Since I voided my warranty, is there a way to fix this myself? (I haven't found anything that helps me so far)
Click to expand...
Click to collapse
why did you flash system image.? rootedsystem.img are used on locked bootloader..
if you unlocked bootloader and installed twrp. all you had to do was flash superus in zip format or a custom kernel.
does download mode works? turn off phone pres vol up connect usb cable.??
if so then flash stock firmware. with LG UP. you need to flash the same android version you are on.. theres antiroll back security on some phone and if you use lower android it hard bricks phne . so if you download KDZ make sure its the same you have..
What model phone (H815, H811, H812, etc) do you have and what did you flash?
Can you boot to the bootloader?
I cant get to download mode/bootloader
It's a H815
I have updated my Nexus 5x to 7.1.1 beta and after a day it powered off and I got the infamous red led during charging. I was not able to turn the phone on even after leaving the charger on for some days. I thought it is bricked and left it alone connected to my computer.
However today, out of nowhere Google logo popped up. It was bootlooping, but I was able to enter bootloader and original recovery. I wanted to flash it from bootloader, but was unable, because it was still oem locked. And I was not able to oem unlock, because I did not do the required part in the Developer Tools menu. I tried to adb sideload OTA in the original recovery, but sideloading stopped after uploading ~48% every time.
So I opted for the "VolumeUp + Power" mode flashing. Phone was recognized and I started flashing the appropriate TOT file. However at 33% on phone and 28% on the PC, progress stopped. And after a minute or so phone turned off. Currently it has no signs of life at all. Have I completely bricked it now? Is there a way to recover from interrupted "VolumeUp + Power" flashing mode?
EDIT: at first I though maybe the battery died during flashing. But interruption was not abrupt. First the progress slowed down to halt. And then after some time phone turned off.
It seems not all is lost. Have a blinking red light again after leaving it connected to computer for a day. Back to square one, but at least it is alive.
Your motherboard is dead.
And it is not your fault, mine also died while using beta 7.1 and I sent it RMA. They replaced for a new one.
But in my case i had unlocked bootloader, I flashed back 7.0 and it gave no results, still bootloop that's why I sent
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Anyway, I tried to RMA it and after giving my IMEI to the Google rep, they said that they could not find it in their system after checking US and UK store records. Also tried calling LG warranty, but they do not know of my IMEI either. I got this phone from Swappa, so I left wondering where did the original owner of this phone got it from. He claimed that he got it as a present...
BlinK_ said:
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Click to expand...
Click to collapse
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
anazhd said:
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
Click to expand...
Click to collapse
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
BlinK_ said:
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
Click to expand...
Click to collapse
For now, no way that I can think of. You could try to oem unlock it until it work, just cross your finger I guess?
I have some progress here. Since I was able to sideload various OTA images, I started doing that one by one and seeing if some of them would not bootloop. And after flashing 7.0.0 (NRD91N) from here (https://developers.google.com/android/ota) phone booted successfully and now is working. Will report if I get any problems.
i tried to install lineageos on my asus zenfone 2 ze551ml. I must confess that I really messed things up because i didnt put lineage os on it before wiping.... anyways, I cant access the bootloader, but my phone does turn on and show the asus logo and that powered by android thing, in white tho, which is since I activated bootloader. Since the Screen turns on it doesnt seem to fit the definition of hardbricked, but I cant access bootloader either so it doesnt seem to be softbricked. What can/should i do now? When holding Power and volume up it just vibrates and does nothing, but when i just press power it gets stuck in the booting screen, i can turn it off though. I dont want to make things worse since everyone seems to warn me of using hardunbrick methods when the screen still does turn on... I own the zenfone 2 ze551ml, it wasnt rooted and i recently downgraded to lollipop since otherwise i couldnt have used asus' bootloaderunlock tool.
EDIT: I now have followed some tutorials, I have used the xfstk tool and i got to the point where I can choose between normal boot, power off, recovery, and reboot to recovery. I can also detect it via cmd and fastboot devices. Now unfortunately I can't flash a ROM with the Asus flash tool because "Error #1" and I cant put anything on it in general. I've come to the point where I just decided that i will take the next opportunity that will make this stupid thing work again and that my next phone will just be a oneplus because of the far better support from customroms etc. Anyways, does anyone have a clue how to fix it? if it runs lineageos afterward or the stock rom doesnt matter anymore, but it should work afterwards. Thanks! (in cmd, when im trying to flash something it would just say (command write failed (no error)))
Hey guys,
I would have liked to get the OREO update, because it said every time is up-to-date, and I wasn't patient. because all of these already get it, and the battery life was terrible with, and I have just 30 days to cancel the phone if I'm unsatisfied with it, so it was urgent for me to update and try it.
But I didn't know enough from the newest devices, so that I need unlocked bootloader to flash STOCK ROM or ROOT or for flash RECOVERY
Mine is XT1789-06, I tried to flash first this ROM:
https://androidfilehost.com/?fid=962187416754456314
It didn't tell this is TMO. :/
This changed my baseband to TMO and my boot image to T-mobile, after I didn't have signal and the fingerprint sensor didn't work.
I wanted fix it with RETAIL ROM flashing.
I tried to flash this: https://androidfilehost.com/?w=files&flid=241773
After that my phone didn't boot, says your device is corrupt.
Cause this I tried to flash back the previous version so this: NASH_RETAIL_7.1.1_NPXS26.122-68-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
from here https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/
But no result. The baseband stucked on TMO, the phone is not start up. Fall back to fast boot mode.
After and mean while these things I tried many things.
The Motorola Device Manager isn't working at all.
The Software Upgrade Assistant what the phone want when show boot up failed message isn't working just say processing device information and isn't going further. I don't understand why the phone ask it, because that is for verizon phones.
The RSD lite says the model name is Fastboot nash S and isn't start to flash anything, when I press the start it says the phone failed to switch to fastboot mode, but it's in that.
I tried already flash more different ROMs, but didn't work one of them .
Recovery is unable, the phone isn't rooted, the bootloader is locked, however sometimes it showed ""Your device software cannot be checked for corruption. Please lock the bootloader", but I checked in the powershell and in fastboot mode I looked what phone says, so it's locked.
I was thinking maybe if I unlock it will solve the problem, but I can't turn it on, so the developer options are unavailable and I don't know maybe it won't help, if I can do it somehow.
Now if I want turn on the phone it's going to fastboot mode right away or say your device is corrupt... and after.
I can't try flash it through Qualcomm 9008 because the PC recognise the device for fastboot device.
In the device manager the computer shows Motorola ADB interface.
I try to unbrick for 3 days, please help me.
Thanks a lot in advance.
Same here, if you find anything out DM me
I already contacted with the phone, I will bring back to Repait it.
I couldn't find out nothing, I tried everything what was possible.
i think i found a solution i just dont know how it works exactly, something to do with a batch file and a full flash of the phone
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 im going to try this and let you know
Hello, has been a w hile since I was here last time. However, my moto g 5g plus gives me a hard time now. I was using it and at some point the power button stopped working. First it worked only randomly but now it is dead. Before the phone shut down i was able to test the fingerprint sensor and it worked. The last few days i noticed that the connection resets randomly from 5G to 4G to H+ and sometimes i had to restart the phone to have a working connection. I was thinking there is a firmware bug in the stock firmware that continues showing up over time. Last time i did a firmware recovery using the motorola rescue tool but that doesen't work anymore because i cant enter boot loader mode. I have seen that there is the qualcom flash tool out there and im wondering if im able to flash the device without bootloader mode as im not able to start it. And if the problem is software related or not. For the qualcom flash tool i probably need the "firehose" files, where can i find the right one for my device?
I have an update, I think it is a software problem. I have tried unlocking the bootloader and as soon I did everything worked same before. Then I flashed linageos and as as able to use it for one day until (when playing pokemon go it happened again) now the power button responds with delay. But it responds. I have tried to reflash lineage and stock using rescue assistant but nothing helps. Then I tried reboot in edl mode for blankflash but that one also doesent work. It starts the process when it sees the device but it terminates with an error. I have dumped all partitions using the recovery shell. But not sure where to search for as I don't have a dump of the stock partitions. I think there has been some corruption of one of the data in _a slot and now _b slot too. Someone knows what and where to look for? Maybe I need a dump of stock device?
It seems there is something wrong with bootloader. Now I'm not able to flash in fastboot mode. But it works when I flash the gpt.bin after restart in fastboot. I start the download on the PC and then connect the phone and power up in bootloader mode. After that I can flash as normal but after reboot everything same before, no fastboot working. And if I flash stock ROM and lock the bootloader it says no operating system found. I have tried using blankflash from lolinet but that one also doesent work. It recognises the device but then it stops. Is it possible that I have got this sort of thing ota? This is so weird. The power button works but just delayed. Is it on a different chip what is maybe broken? But that would be very strange. I have another phone I treat not as nice as this one and that works like new.
Ah I enter edl by using linage recovery
Deleted all the partitions, now it seems the device doesn't boot the stock ROM if I flash it. What are the essential partitions needed to boot the stock ROM? How can I restore the missing partitions? Thanks