Related
First off, I'd like to say my S2 is the Virgin Mobile version (model i9210) so I'm not sure if it's okay for me to post this in this forum or not. Feel free to move it where it should be, I won't be offended.
Edit: Originally had posted this in the Samsung Galaxy S2 forum, but it was nicely moved to this forum in hopes that it would be seen more~ So to clarify, my phone is the Virgin Mobile Samsung Galaxy S2, running Android 4.1.2, model number SPH-D710.
The ROM I have is BiftorROM-V8-JB-XWLSN-NoWipe.
Onward. This is my first Samsung phone AND my first Galaxy, and when I decided to root my phone, I had no idea how much different it would be from my past phones. How I didn't completely brick this phone, is nothing short of a miracle. I had trouble with some ROMs so someone eventually linked me to a Sprint stock ROM, saying it was compatible with my phone.
Since then I've been using that ROM, despite having a Virgin Mobile phone, with no problem. Recently I noticed an app I use (SD Maid) was listing my phone as unrooted. It was weird but I ignored it, because the app still worked. Even later, I noticed other apps that require root access were not working correctly, so I decided to download a root checker.
Status: Unrooted
Well, then. I'm not sure how this happened, or what's going on, but I figured again, it was no big deal because my ROM was running perfectly and I had no desire to change my ROM or anything else soon. Last night my phone started acting completely different. Lagging like crazy, and when I tried to unlock my phone, it would take a good 15 seconds just for the screen to turn on and my lock screen to start functioning normally. Then another 20 seconds or so for the screen to register my touch and actually unlock my phone. I tried disabling all lockers, but my screen would just turn black and I would still have to wait.
A friend suggested that I simply go through the process of rooting as though my phone really were unrooted and just hope that fixes it, but I'm not sure if that would be a good idea. If my phone wasn't operating so slowly this wouldn't be as big of a problem, but it is, and I'm pretty afraid that I'll mess my phone up somehow.
I once found a forum with the topic the same as mine but I haven't been able to find it since, so I'm hoping someone here could point me in the right direction. Do I go through the root process, maybe try just reflashing my current ROM? I've also thought about just doing a system restore on my phone and see if that helps. Thanks in advance.
I never thought I would be coming here for this issue. This incident is no less than surprise to me.
I tried everything to save my phone from getting hard brick like I downgraded very carefully, became choosy about kernels and custom roms I was flashing but yesterday my phone hard bricked itself magically, yes I am not a freak to make that statement but my moto e which was running fine till date got hard bricked on it's own.
I used it normally, everything was normal but yesterday night when I unlocked my phone to see time and then locked it and then unlocked it after a second to set alarm and guess what, the screen didn't turn on. I waited for a minute but no luck, then I pressed power button for 10-12 seconds expecting a restart but it didn't show up, it gave no response (also the battery was 71% I checked few minutes before) I was out of my mind and then after few minutes I decided to connect my phone to pc and the moment I connected it showed up "qhsusb_bulk" drivers installation, OMG! What the hell did just happen, I lost all of my valuable data in phone memory and also lost my phone in an instant... that too forever ?? :crying:
I spend lots of hours today trying every possible step which could bring my moto e to life but no luck again, I am still wondering what went wrong. Did this happen to anyone out there?
Can any expert on xda answer me what could have went wrong ?? and is there any solution hidden out there?
I don't think even if the Motorola company can itself answer the question.
Little bit more:
I had no internet, no wifi, bt turned on.
Running Stock 4.4.4
Just rooted and used GravityBox (it was running very smoothly till date)
Installed Es File Explorer only, nothing else.
How can it be?
I am really shocked and feeling very low, I can't see my moto e dead anymore.
PS: I found no thread of moto e magically getting hard bricked so mods plz, mercy.
Bootloader is the key.
Even if fastboot mode isn't turning on then there's no hope.
This is very unusual though.
Did you downgraded from 5.1 to 4.4.4?
No I didn't do anything but today did postmortem
-z3r0- said:
Bootloader is the key.
Even if fastboot mode isn't turning on then there's no hope.
This is very unusual though.
Did you downgraded from 5.1 to 4.4.4?
Click to expand...
Click to collapse
I did not downgrade or install some app, tweak,kernel or anything, I was on 4.4.4 since 3 months.
And I agree with you, the bootloader has corrupted itself (weird like hell) and screen won't show anything (no fastboot or anything)
Also today morning I disassembled the dead moto e to look if I could find anything but no luck, every component is working like battery, lcd, speaker and everything, except ya bootloader. So postmortem reports say that it was a suicide, the phone killed itself. The soul (bootloader) has left the body of moto e. Yes that sounds funny but that's what it is. I felt very bad for a day but now accepted the fact that some events occur without leaving a trace of cause. Moto E was the only phone I had after selling all the phones I had. Will buy new after few months but I am sure my next phone won't be from Motorola. I will remember this event.
Thread is still open to question asked in post 1 and also I ask what should I do with that dead moto e can I make few bucks out of it so that I can buy new phone soon.
Thank you everyone who came this far.
This issue had been reported on Motorola's forums a few times. Motorola's reply was "It's against forum rules to talk about unlocked phones/modding the phone."
No help from Motorola, the device wasn't meant to last more than a year or two.
Afaik the international variants of the Moto e don't have the power button issue, battery issues, or the sudden death issue.
Sent from my XT1022 using Tapatalk
DNALogic said:
I did not downgrade or install some app, tweak,kernel or anything, I was on 4.4.4 since 3 months.
And I agree with you, the bootloader has corrupted itself (weird like hell) and screen won't show anything (no fastboot or anything)
Also today morning I disassembled the dead moto e to look if I could find anything but no luck, every component is working like battery, lcd, speaker and everything, except ya bootloader. So postmortem reports say that it was a suicide, the phone killed itself. The soul (bootloader) has left the body of moto e. Yes that sounds funny but that's what it is. I felt very bad for a day but now accepted the fact that some events occur without leaving a trace of cause. Moto E was the only phone I had after selling all the phones I had. Will buy new after few months but I am sure my next phone won't be from Motorola. I will remember this event.
Thread is still open to question asked in post 1 and also I ask what should I do with that dead moto e can I make few bucks out of it so that I can buy new phone soon.
Thank you everyone who came this far.
Click to expand...
Click to collapse
Sorry to hear about the incident, but blaming motorola ain't gonna fix it. Motorola won't care if one of its phones is dead, it has a hell lot of customers buying their phones everyday. And also, motorola is right. They guarantee no life of the device after we unlock it. Still best of luck buying your next phone...:good:
Regards,
PoseidonKing
Ahish.s said:
This issue had been reported on Motorola's forums a few times. Motorola's reply was "It's against forum rules to talk about unlocked phones/modding the phone."
No help from Motorola, the device wasn't meant to last more than a year or two.
Afaik the international variants of the Moto e don't have the power button issue, battery issues, or the sudden death issue.
Sent from my XT1022 using Tapatalk
Click to expand...
Click to collapse
PoseidonKing said:
Sorry to hear about the incident, but blaming motorola ain't gonna fix it. Motorola won't care if one of its phones is dead, it has a hell lot of customers buying their phones everyday. And also, motorola is right. They guarantee no life of the device after we unlock it. Still best of luck buying your next phone...:good:
Regards,
PoseidonKing
Click to expand...
Click to collapse
Thanks for reply, And after research I have found thousands of dead moto e owners and still no support from Motorola anyways
If Motorola won't care I won't freaking care either, I am thinking of getting Xiaomi Redmi Note 3 (Snapdragon Variant) soon.
You know I use to suggest people to get Motorola and was so damn moto fan that would convince every person I met to get motorola next time but no more motoism. Goodbye Motorola.
P.S. Thread still open for people who could figure out how could I get the suicide note written by my moto e (to find cause of death/hard brick) or if you have an idea of what could have went wrong.
P.P.S. Sorry if posts are more personal and artistic and feelings are overflowing but that's the way I am .
DNALogic said:
Thanks for reply, And after research I have found thousands of dead moto e owners and still no support from Motorola anyways
If Motorola won't care I won't freaking care either, I am thinking of getting Xiaomi Redmi Note 3 (Snapdragon Variant) soon.
You know I use to suggest people to get Motorola and was so damn moto fan that would convince every person I met to get motorola next time but no more motoism. Goodbye Motorola.
P.S. Thread still open for people who could figure out how could I get the suicide note written by my moto e (to find cause of death/hard brick) or if you have an idea of what could have went wrong.
P.P.S. Sorry if posts are more personal and artistic and feelings are overflowing but that's the way I am .
Click to expand...
Click to collapse
I also used to do the same....Motofan... Moto this and moto that, but no more... I am also looking forward to buying note 3.... Which one r u buying?
32GB 3GB RAM or 16GB 2GB RAM? If it's 32GB then send me a link in a pm..
Regards,
PoseidonKing.
Kindly go through this thread http://forum.xda-developers.com/moto-e/help/blank-flash-plzzz-t3153660/post66122497#post66122497
I am also gearing up to do it. Need a donor with 5.1 to backup and upload the image
Yea, something similar just happened to my phone and it's driving me nuts. About a week ago i flashed stock 5.1 and it was working fine so far, (except for the camera that was constantly crashing for no reason when I opened it, but that didn't really bother me that much) but suddenly stopped responding when i tried unlocking it. I can't access the bootloader either...
The only response i got was from the little white led when i tried pressing the power button for a bit longer and when i unplugged it from my PC.
The only apps I had installed were the Facebook messenger, Whatsapp and Instagram. Is there any hope to save it? ;-;
That sounds like hard bricked moto e
Kaio Oliveira said:
Yea, something similar just happened to my phone and it's driving me nuts. About a week ago i flashed stock 5.1 and it was working fine so far, (except for the camera that was constantly crashing for no reason when I opened it, but that didn't really bother me that much) but suddenly stopped responding when i tried unlocking it. I can't access the bootloader either...
The only response i got was from the little white led when i tried pressing the power button for a bit longer and when i unplugged it from my PC.
The only apps I had installed were the Facebook messenger, Whatsapp and Instagram. Is there any hope to save it? ;-;
Click to expand...
Click to collapse
Sorry Bro, but by what you said I really feel like your moto e has been hard bricked. No fastboot and white LED blink when plugged into charger is pure sign of hard bricked moto e, then too you can connect to pc and if it's device manager detects it as QH-USBBULK and installs drivers then it's hard bricked for sure and no hope till now. I have been able to get just one guy who claims to bring his hard bricked moto e to life after following some tutorial. You should check this link right now. After reading 2-3 pages you can too try to get your moto e to life. Do reply there or here when you successfully unbrick it. All the best. :fingers-crossed::good:
Mine died suddenly today during a reboot, apparently there's no trace of an unlocked bootloader when it's bricked like ours, I'm gonna send it in as I'm still a few months in warranty. Has anyone got any experience regarding this?
Benzy1 said:
Mine died suddenly today during a reboot, apparently there's no trace of an unlocked bootloader when it's bricked like ours, I'm gonna send it in as I'm still a few months in warranty. Has anyone got any experience regarding this?
Click to expand...
Click to collapse
Please let us know what the service center did for this issue.
Sent from my Moto E using Tapatalk
DNALogic said:
I never thought I would be coming here for this issue. This incident is no less than surprise to me.
I tried everything to save my phone from getting hard brick like I downgraded very carefully, became choosy about kernels and custom roms I was flashing but yesterday my phone hard bricked itself magically, yes I am not a freak to make that statement but my moto e which was running fine till date got hard bricked on it's own.
I used it normally, everything was normal but yesterday night when I unlocked my phone to see time and then locked it and then unlocked it after a second to set alarm and guess what, the screen didn't turn on. I waited for a minute but no luck, then I pressed power button for 10-12 seconds expecting a restart but it didn't show up, it gave no response (also the battery was 71% I checked few minutes before) I was out of my mind and then after few minutes I decided to connect my phone to pc and the moment I connected it showed up "qhsusb_bulk" drivers installation, OMG! What the hell did just happen, I lost all of my valuable data in phone memory and also lost my phone in an instant... that too forever ?? :crying:
I spend lots of hours today trying every possible step which could bring my moto e to life but no luck again, I am still wondering what went wrong. Did this happen to anyone out there?
Can any expert on xda answer me what could have went wrong ?? and is there any solution hidden out there?
I don't think even if the Motorola company can itself answer the question.
Little bit more:
I had no internet, no wifi, bt turned on.
Running Stock 4.4.4
Just rooted and used GravityBox (it was running very smoothly till date)
Installed Es File Explorer only, nothing else.
How can it be?
I am really shocked and feeling very low, I can't see my moto e dead anymore.
PS: I found no thread of moto e magically getting hard bricked so mods plz, mercy.
Click to expand...
Click to collapse
same happened with me I was running cm14.1 with BlackMWhite logo (downloaded from here:-http://forum.xda-developers.com/moto-e/themes-apps/boot-logos-motorola-boot-logos-moto-e-t3216857)working fine from 2-3 days even rebooted several times but yesterday when I wake up it was dead (looks like hard bricked as it's not even charging) when I connect it to PC it installed some drivers and in device manager shows "RELINK HS-QDloader 9008 (COM 3)" have you tried http://www.droidsavvy.com/unbrick-qualcomm-mobiles/ ??? :crying:
My moto e is also not turning on.I think mine also got hard bricked.
Incident: I was opening shareit to share something but when I clicked on SEND my moto got switched off.This had happened with me some days before also but it was fixed by just connecting the charger but idk how it got fixed. But this time I tried everything but all is worthless.
Can anyone help me and others regarding this issue. :crying::crying:
Has anyone of you guys tried QFIL ?
What is this QFIL???
Kaymas said:
What is this QFIL???
Click to expand...
Click to collapse
Qualcomm Flash Image Loader
I have seen a mechanic un-bricking Chinese smartphones. He dis-assembles the phone, removes the battery. After couples of minutes connects the battery back. Then 'Qualcomm HS-USB Diagnostics' in PC is able to recognize the Phone.
Hi guys,
I'm stuck with my LG G5 (H850) not booting after replacing the display. I bought the phone in used condition quite a while ago, and at some point the display cracked and the touchscreen did (and does) almost not work since it is hyper-sensitive now. I figured it stays somewhat usable after putting the phone into the freezer for 2-3 minutes. (apparently heat makes it worse).
So the thing now is, I bought a new phone at some point, but thought the LG still deserves a fix since i liked it for many reasons. I bought a pretty cheap display replacement (didn't want to invest too much money anymore). It was explicitly offered for H850. After replacing it, the phone wouldn't boot anymore. I just saw the LG splash coming and going in a 5s bootloop.
So I thought "maybe a hardware replacement requires to unlock the bootloader..." I unlocked the bootloader with the official guide (which was not easy as it required me to use the old crappy display to allow OEM unlock in android) and installed TWRP at the same time, cuz i thought it could prove helpful for other potential modifications.
After switching to the new display again, the phone would boot either OS and TWRP perfectly. The new display was also looking good. In the boot process it started showing "your device can not be checked for corruption", but that seems to be normal.
I thought "nice job" and put it down for a few weeks. Trying to start the phone again yesterday, I ran into the same issue again, bootloop. After performing a hard reset, which should bring you to TWRP, it's just the bootloop again. Going back to the old display: Booting fine but hardly usable. New display: Booting fine! Waiting for one night: No chance.
I think that's pretty weird. It's not that it doesn't work at all. I'm not an expert (which is why I'm asking you), but it seems the bootloader blocks booting with the new diplay, but only after having it switched off for a while. Once the phone has started, everything is fine.
What adds up to this story is that the phone wasn't perfectly fine beforehand. The old display (before cracking) provoked regular reboots and sometimes "your device is corrupted" would show up in that case. The reboots were gone - at least in a two days test i performed after getting the new display work.
On the other hand, there is something wrong with the basic capabilities of the bootloader with the new display: Fastboot mode works fine, but download mode only appears for a moment before rebooting.
Do you see any solution to this story? Anything I'm missing? I just grew up in a tradition of repairing things, but if you say that's a waste of time, I'm almost at the point of giving up
Thanks!
oliver t said:
tl;dr
Click to expand...
Click to collapse
Its not your new display, more likely motherboard fault.
Peace
Okay, a dual question here. One specific and one general but they are both related and one will help the other. Hopefully if anyone provides good answers others will find this post useful. I have a Asus Zenfone Selfie which has begun boot-looping. The phone is rooted and has TWRP installed. Once in a while it boots up as far as the home screen, then sometimes only up to the Asus logo. I have flashed several different ROMs (stock and custom) and again, it boots up to the setup screen then only up to the Asus logo so I was assuming this must mean it's hardware related. However, I can boot into TWRP and stay there for hours with no bootlooping. If it were hardware then it should bootloop for TWRP too so it must be software related, right? One more thing: I usually flash in TWRP but many times it crashes during the flash process. Sometimes it does succeed with no issues though. On my PC I might be running some disk or RAM checking tools to see if there was a bad sector or track on my hard drive or a bad module... Yeah, I'm confused. Why is it bootlooping and what, if anything, can I do to fix it?
This leads to my general question. Over the past 20 years I have had several phones, many of which ended up bootlooping. I know the LG G4 & G5 had a hardware flaw that cased them to bootloop and I know screwy flashes can cause bootlooping. But what about all my phones? Some were new, well, only a year or two old, some were 6 or 7 years old. Some were Android, some were Windows Phone. Some were rooted, some were unrooted, some were stock, some were custom ROMs. Some had updated or recently got new apps installed, others hadn't had anything new in ages. Some were in use when they started bootlooping, some were just sitting there. Some had a full charge on the battery, some were close to empty. What can be done to prevent this? What can be done once it has started, especially with one of these newer phones that they STUPIDLY like to make with sealed in batteries. And the given button combination just reboots the phone - again. Depending on who I talk to (or where I read) they say one thing or the other. It's software related. Okay, how? Why? I know on my PC Windows will sometime crash and reboot just for the hell of it, but that's usually just MS fixing an issue with a PC that runs too smoothly. And when that happens, it can be fixed. As an aside to any software developers reading this, I know you may not want to take the time to rewrite everything to work on Linux but you could take a little bit and make your software work with WINE, just a thought guys.
Anyway, so if it's software related, what can really be done to fix it? I can understand the big companies may like it if your phone bootloops so you'll need to buy a new one, but there are tons of developers out there making great custom ROMs. I know they don't have the resources to really fix all the bugs but I assume they would do a better job than certain big companies right? And why would the software suddenly crash like that? Sometimes literally NOTHING is happening, so why the sudden desire to bootloop? What about hardware? Can't we design software to work around the flaw? I would think manufacturers would want to fix problems to make their products as good as they can be but from what we have seen, I guess not. If you read my list above, many of those phones have nothing in common except the bootlooping. So where is the error coming from? Is there really nothing that we can do?
Any ideas and explanations would be appreciated, as would any help on my more recent bootloop device the Asus Zenfone Selfie Z00UD/z00T. Just to mention, that is a newer phone. It may not be now but it bootlooped probably a little over a year ago. It takes me a while to get around to things sometimes, like writing a letter to post on a forum. I had in mind to take it to this one repair shop (they had to replace the USB charging port maybe 3 months before the bootlooping so I assumed there might be a connection) but when I finally got there they told me it was software related and wouldn't look at it. Also, I don't want to make it sound like all my phones bootloop. I have had many many phones that died due to other issues and many more that are still in use, even old ones. I just want to try to understand and grasp any common factors that cause some phones to bootloop, and to maybe use that knowledge to prevent future phones from bootlooping even if I can't repair the ones that already do.
Thanks for your time in reading this and in advance for your answers. If you googled your way here, I hope there is info here that can help you too.
Hello, I am one more carrier of an LG V60 although before it was Att, now it is no longer, it has identity problems.
My headache started a week ago when I found a guide on how to do crossflash on any device, I followed the steps but maybe I was wrong about something, I still don't know exactly what it was because I was following the steps until the computer (which didn't it's very slow) it got stuck and out of nowhere I erased all the vital partitions for the phone, when I saw that it didn't turn on I gave it up for dead and I had already stored it (with honors) in a broken cell phone drawer that I have (really, It was next to an HTC U Ultra, U11, an Iphone C and a box from a Xiaomi Redmi Note 4 that was stolen from me).
After a few hours a person answered me who said that he had managed to update an Att V60 to Android 11 but it was a very difficult motorcycle, well, I told him a little about the situation and he offered to help me, I am really grateful for the help, well I had already given up my LG for dead, but even with all the help it did not look very good, I spent many hours trying to revive it, at the end of 3 or 4 days it gave a sign of life, I threw the text of LG V60 ThinQ ( although without 5G, which is strange since I had it before) and then it had some red letters indicating that they had not been able to find the necessary documents for the boot, I kept looking until I found the solution (don't ask me how I did it, literally everything came out by following and joining steps and guides as if they were a puzzle) and I finally managed to install a KDZ and update.
Home, Android 11, keyboard and everything like new, seriously, I was filled with joy to see that everything had gone well, configure everything, install the applications that it would occupy and other things, at this point when I turned on I saw the battery 64%, I thought that it was time to move my stuff back to this phone (I have a spare V35) but after a while I noticed strange things, the first one was how hot the phone was, I thought it was because it was being turned on for the first time , Another thing I noticed was that the fingerprint sensor did not read my fingerprint (it is currently repaired) and that good among one of the things that were evident is that I had lost my Imei, I had found a person with a guide that said how to recover it but it didn't work, my QFil doesn't read the qcn I don't understand why.
When I thought that those days of headache were over and all I had to do was enjoy an excellent phone, it was not like that.
Problem list:
- Does not have imei
- Battery drains in a matter of 5 hours or less
-Fast charge missing
-It's always hot
-The CPU has about 4 cores always working at 100% for no reason, even when idle with the screen off and entering the safe mode the phone does not stop being just as hot or with the same workload
I really want you to help me, it's the only phone I've ever had so powerful and so TOP that I wouldn't want to let it die, besides that, I'm in college and the expenses are getting higher and higher and I don't have money to buy another or buy a second-hand one, I also live in latam (I also say this in case some of my words are not consistent, I know a little English and I am also studying but I still do not feel capable of formulating a whole text in English)
If anyone knows what I can do or what I can try to do I will really appreciate it, I really love this phone and I didn't want it to end like this, believe me I'm really sorry I tried to update
AngelED2000 said:
Hello, I am one more carrier of an LG V60 although before it was Att, now it is no longer, it has identity problems.
My headache started a week ago when I found a guide on how to do crossflash on any device, I followed the steps but maybe I was wrong about something, I still don't know exactly what it was because I was following the steps until the computer (which didn't it's very slow) it got stuck and out of nowhere I erased all the vital partitions for the phone, when I saw that it didn't turn on I gave it up for dead and I had already stored it (with honors) in a broken cell phone drawer that I have (really, It was next to an HTC U Ultra, U11, an Iphone C and a box from a Xiaomi Redmi Note 4 that was stolen from me).
After a few hours a person answered me who said that he had managed to update an Att V60 to Android 11 but it was a very difficult motorcycle, well, I told him a little about the situation and he offered to help me, I am really grateful for the help, well I had already given up my LG for dead, but even with all the help it did not look very good, I spent many hours trying to revive it, at the end of 3 or 4 days it gave a sign of life, I threw the text of LG V60 ThinQ ( although without 5G, which is strange since I had it before) and then it had some red letters indicating that they had not been able to find the necessary documents for the boot, I kept looking until I found the solution (don't ask me how I did it, literally everything came out by following and joining steps and guides as if they were a puzzle) and I finally managed to install a KDZ and update.
Home, Android 11, keyboard and everything like new, seriously, I was filled with joy to see that everything had gone well, configure everything, install the applications that it would occupy and other things, at this point when I turned on I saw the battery 64%, I thought that it was time to move my stuff back to this phone (I have a spare V35) but after a while I noticed strange things, the first one was how hot the phone was, I thought it was because it was being turned on for the first time , Another thing I noticed was that the fingerprint sensor did not read my fingerprint (it is currently repaired) and that good among one of the things that were evident is that I had lost my Imei, I had found a person with a guide that said how to recover it but it didn't work, my QFil doesn't read the qcn I don't understand why.
When I thought that those days of headache were over and all I had to do was enjoy an excellent phone, it was not like that.
Problem list:
- Does not have imei
- Battery drains in a matter of 5 hours or less
-Fast charge missing
-It's always hot
-The CPU has about 4 cores always working at 100% for no reason, even when idle with the screen off and entering the safe mode the phone does not stop being just as hot or with the same workload
I really want you to help me, it's the only phone I've ever had so powerful and so TOP that I wouldn't want to let it die, besides that, I'm in college and the expenses are getting higher and higher and I don't have money to buy another or buy a second-hand one, I also live in latam (I also say this in case some of my words are not consistent, I know a little English and I am also studying but I still do not feel capable of formulating a whole text in English)
If anyone knows what I can do or what I can try to do I will really appreciate it, I really love this phone and I didn't want it to end like this, believe me I'm really sorry I tried to update
Click to expand...
Click to collapse
UPDATE
I seem to have the original FTM, OP_a, OP_b, modem_a, modem_b, sid_a and sid_b files, in other words before the tragedy happened.
UPDATE 2
I think also abl_a and abl_b
Hello, I have the same problem with my LG v60, I know it's hot a lot, I know it ends Very quickly, the battery was erased, IMEI does not recognize a fingerprint, I have already flashed different versions from the original at t open Canada, European version and it is not solved, did you find any solution, any information on why the failure