Heh, my English is apparently insufficient for a perfect title.
So there is the long story about a weary developer fiddling with screen resolutions. After sixteen hours long day, a sudden decision results in TWRP on an unlocked, rooted phone.
Then, suddenly, system.img gets erased, despite warnings for such action. Panic ensues. No good system.img files are found, so the H960A gets reflashed to an H901. At a quarted past four in the morning, sleep takes over.
Morning comes with clarity - he bloatware, the limitations, the .... what has happened to my phone kind of insight.
Since then I have failed to reset this device to H960A. Tried many of the threads that Goooooooooooogle came up with, but all the methods end up with error messages and no flashing.
Status is now a start looping device (not really boot looping), which can enter recovery mode and download mode, but which cannot finish boot
So I wish some help - what can be a workable way to reflash a H960A, which thinks it is a H901 (except in LGUP, which sees it as both).
Oh, nice title and well described.
I guess you tried LGUp with uppercut? If no. please use that. If yes, please try restoring to stock. To start with you can try nougat 30b version. if it does not work, try this http://www.aryk.tech/2017/07/how-to-unbrick-lg-v10-in-hs-usb-qdloader-9008.html
Related
If anyone can advise me here I will be very grateful. I have spent several days looking online and reading countless threads here but am still not having any joy. Am a bit of a noob so go easy on me please!
I have a rooted LG D618 running Lollipop (recently upgraded itself from Kitkat). Long story short, I was fiddling around with the bootloader trying to install a custom recovery (ahem... ) and I ended up bricking the phone. I have been trying since then to install the original firmware using LG Flash Tool 2014 and it always stops on the 4% mark whilst extracting the kdz. I have tried this about a hundred times and the same thing happens every time. The phone is completely dead, I can not switch it on and I am unable to boot it into Factory Reset mode using the keys either. But it is still being recognized by the PC (win7 x64) and can enter (what I assume is) download mode. However in Windows the phone is recognized as removable disk containing 2 folders - 'image' and 'verinfo'. Not sure if that is normal or not? I am able to start the kdz flashing process and it goes through the first couple of steps verifying connectivity etc and then stops at the aforementioned 4% during the file extraction process, sticks for a while, and then gives me an error message.
I tried a solution which I found on the forum here, which I think was for the same issue, involving the wx.dll file in C/ProgramData/LGMOBILEAX/phone but this has no effect. I thought it might be related to me installing the KitKat kdx (v10c) onto the phone but I have since tried flashing the stock Lollipop variant (v20b) also and the exact same thing happens so am guessing it is not because of the KitKat wx.dll file causing issues. I am pretty clueless here, all of this is unchartered territory for me and I am out of my depth so if any kind soul here can advise me on any possible solution I am willing to try anything before admitting defeat, and taking the phone to LG to fix under warranty and hoping they don't realize that I broke it. :laugh:
So I was having so many issues with my rooted phone crashing on jasmineRom 7.0 I thought maybe an OTA update had made it through and started downloading. No matter what I was doing the screen would turn blue and then restart. Sometimes it would crash blue again during reboot, and sometimes it would crash and then show the green demigod crash screen. So I researched flashing the .tot files to go back to stock. KDZ I didn't care for because it still showed the phone as modified software, and I wanted full stock so I could use the extended warranty with Verizon if need be. I eventually got the .tot method to work and everything was hunky dory, and showing stock. I upgraded all the way to marshmallow and decided I love every bit of it, but I couldn't figure out how to get my contacts and stuff off titanium backup without root. So I figured, "well roots not the problem if an OTA tried to download it just means I missed a setting or something". So I rooted again. No issues, I reinstalled JasmineRom 9.1 this time. Eventually it started crashing again, although this time I followed absolutely every guide I could find on disabling OTA. So I thought, "Great it's Jasmine" and I really wanted Marshmallow anyway so I followed xdabbeb's guide for getting the 35b bootstack on my phone, worked great no issues, and then I installed xdabbeb's firmware, combined with Edor's debloating zips. Everything was working great! I had no issues, I backed up just my apps, and some data, and reinstalled others and everything was great and working fine, and the phone was still official, no OTA's getting through. That was almost a full week ago. Yesterday I woke up and the phone wouldn't turn on. I took the battery out and put it back in and the phone came on, but then crashed with the blue screen again. So I thought great I guess I'll put it back to stock and use the warranty. By this time though I was having trouble getting it to load past the LG screen. I finally got it into TWRP and was able to wipe everything (except SD card) and then I stuck it in download mode and went to install the .tot files. Weeeeelllll, long story short, it crashed during download mode install with the LG Flash Tool. So now the phone gets stuck in download mode everytime I pull the battery and power it on. And crashes again every time I go to install anything. KDZ doesn't work, the flash tool says it can't communicate with the phone, because it crashes. And LG Flash Tool for the .tot files seems to crash everything it loads the modem, or consistently crashes on LAF:bin_user_mode. So I have no idea. At the moment it just looks like my phone is all funky defective, and Verizon may take it back and give me a new one so I'm going to try that. HOWEVER! If anyone has any ideas on what the issue is or what else can be done, I still want to hear it. Feel free to post
Also I've tried updated drivers for the computer, I've tried rolling back drivers, I've tried different KDZ files, I've tried the LGUP8974.dll fix where you flash that in flash tools and then flash the vs985 dll, which is what I had to do to get it back to stock the first time. I've tried everything I could find online except anything to do with fast boot and shorting the pins. Which I haven't tried because I can still access download mode it just seems to be stuck in download mode. Those methods from what I understand are for hard bricking, and for people who's phones don't turn on at all. Although if Verizon won't help I may try one of the laf recovery methods.
Thanks!
Hey,
I'm pretty new here, so don't hate on my lack of knowledge^^
Maybe I'm even in the wrong sub-forum
(I think there was a sub-forum dedicated to moto x, but this isn't a device-specific issue, so here should be fine - no?)
Got the following problem:
My moto x (2nd gen) is stuck in a loop. I get to the logo-screen, then it goes to "Encryption unsuccessful" and when I click "Reset", it restarts and fails upon trying to reset.
How I got here:
1) A while ago I wanted to encrypt the phone for the lulz (using its' own encryption-tool)
Followed the simple steps, as in having it charged up, but the encryption did not go through.
Don't remember having it to reset at first, it just booted, even though it had bugs after that:
-whenever I charged it, I had problems turning it back on after charging, had to turn off and back on for it to actually work.
-those notifications on top which one can normally open via sliding down, that sliding down did not work after that.
Eventually I did a hard-reset and it fixed the sliding-problem.
Charging also worked fine at first until it did not.
2) I ended up stuck in a boot-loop that went to the logo-screen back and forth (got to logo-screen, restarted, got to logo-screen, restarted, ...)
Tried to soft-/hard-reset using the VOL- and POWER combo.
The hard-reset itself threw some errors at me, something like "can't delete [whatever]".
Still, after a few tries it eventually went past the logo-screen to the encryption-step.
After another few failed resets and emptied cache via recovery-screen, it somehow ignored the encryption-step and turned on the phone (was a fresh version).
3) Worked fine for 1 whole evening, no crashes/glitches/anything until I had to charge it up.
Then it was back to the broken state.
Note: during 2) I tried to boot with a custom recovery-mode(TWRP), but couldn't get it running.
Then I tried to flash it, but anything I tried to install failed.
I had my suspicions, but eventually I got it straightened out: my phone isn't rooted, and the bootloader is locked.
I did get the code to root it via some steps and the motorola service, but the code did not work as it wanted me to unlock the phone first.
From what I've read, to do that I need to get into the settings and unlock/root it...
Funny thing: I can not turn on the phone to get into the settings.
So - anyone got ideas?
Warranty is gone since apparently my tinkering with the locked bootloader and unrooted phone still was visible and they voided the warranty.
Not sure I broke much/anything with that, though, since it DID work at some point after that (even if it was for a few hours before needing recharging)
Therefore I'm open to any suggestions since the alternative stop would be throwing it into the bin^^
Can I unlock the bootloader without having a working system?
Can I root it somehow without having to get into settings (since I can not turn it on in the first place)?
I did a fair share of reading, but most times the guides just assumed that I already rooted it, or forwarded me to a guide where it said "go into settings and spam the build to get advanced options, then simply root/unlock that damn thing". Tried to find a way to unlock/root it without being able to turn it on, but did not get lucky with the search.
If I could unlock and root it, I probably could go from there. Guides are pretty specific and seem to work for most.
Also, I would try the original android version first before searching for any custom systems.
(that is the smartest way to do, right? since I'm just a user and dont plan on doing more hacking/breaking)
Hope all that above wasn't too much to read
Thx for any advice in advance.
Edit:
Well, after what feels like 50 restarts it miraculously did not send me to the "Encryption unsuccessful" but instead booted like it should (as a fresh version, though - so had to backup).
Now I've turned on the thing in the settings so next time it breaks, which I expect to happen by tomorrow, I can flash that sucker.
Still - anyone knows how to enable all that stuff one normally does via settings some way that does not involve successfully booting it?
I mean, there should be a way to root/unlock it without having to turn it on first, right?
Edit2:
As expected, the flashing part was pretty easy, so I'm now sitting with a fresh android 6.0.
Two days in and it's still working fine, haven't had any complications (except battery draining faster then at the very beginning, but I think that's due to it hanging too much on the usb-cable during all those sessions of me trying to fix it - and generally I've had it charge over night a few times to often)
Still would appreciate any advice on how to unlock developer mode and usb-debugging within the bootloader or recovery-mode.
Long story short, stock phone just randomly blew up and I'm trying to re-install its stock Android OS. Phone has never been rooted before, it just started to reboot on its own and now I'm in a position where I can only access download mode.
I'm in Odin, with what I believe is the correct firmware for my device (SM-N950U1) and I just keep getting a "Secure Check Fail: system" when trying to flash. it via Odin. The Odin log says "FAIL! (auth) right after trying to write system.img.ext4 for a few minutes. The "Secure Check Fail: system" is the printout on the phone screen itself.
Any clues?
Bump! Anyone?
playbacktri said:
Bump! Anyone?
Click to expand...
Click to collapse
I see that you have not received an answer. That is upsetting. I am also struggling with this exact same issue on a g955u1. Have not found a solution. Did you end up solving your problem? If so, what did you have to do?
ap7x942 said:
I see that you have not received an answer. That is upsetting. I am also struggling with this exact same issue on a g955u1. Have not found a solution. Did you end up solving your problem? If so, what did you have to do?
Click to expand...
Click to collapse
Nope, I have not solved the problem. I've scoured the internet and other people asking the problem all have not had any answers either. My assumption is that the actual internal memory of the phone is corrupted and won't let me write past a certain point, or on certain sectors, or something and its not actually fixable via software. I think everyone else just stops at this point and its never resolved because there is no resolution hah.
Good luck, let me know if you ever figure it out...
playbacktri said:
Nope, I have not solved the problem. I've scoured the internet and other people asking the problem all have not had any answers either. My assumption is that the actual internal memory of the phone is corrupted and won't let me write past a certain point, or on certain sectors, or something and its not actually fixable via software. I think everyone else just stops at this point and its never resolved because there is no resolution hah.
Good luck, let me know if you ever figure it out...
Click to expand...
Click to collapse
This phone I am working on is for a customer of mine. Thankfully, they have given me an open ended time frame. I have been working on this for about a week trying to figure out whats going on.
The memory corruption thing you were talking about resonates with me, because prior to my customer bringing this in, they had attempted a couple factory resets trying to resolve the original issue which was all the system apps crashing. The phone would reboot like someone killed all the processes. Pretty much from the moment it reached the home screen, and it was not power related. The problem persisted after their factory resets within recovery mode. And then I hit the phone with Odin and ended up with a partial flash. Soft bricking the phone.
You saying that kinda reinforces what I was already thinking, that it might be a hardware issue. Im not sure.
5 minutes ago I was able to get odin to successfully flash BL, CP, and CSC. It even brought me back to the Samsung logo for a minute but hung there. That's the most success I have had with this thing. Ive flashed numerous firmwares and every single one of them fails on system.img.ext4. After it reboots, it boots directly into this altered version of download mode with an emergency recovery error.
I have flashed dozens of phones before without issue. This is the first time I have ever experienced this one. You could be right but I refuse to accept defeat in this case lol so im gonna keep trying and ill report back if I have success.
ap7x942 said:
This phone I am working on is for a customer of mine. Thankfully, they have given me an open ended time frame. I have been working on this for about a week trying to figure out whats going on.
The memory corruption thing you were talking about resonates with me, because prior to my customer bringing this in, they had attempted a couple factory resets trying to resolve the original issue which was all the system apps crashing. The phone would reboot like someone killed all the processes. Pretty much from the moment it reached the home screen, and it was not power related. The problem persisted after their factory resets within recovery mode. And then I hit the phone with Odin and ended up with a partial flash. Soft bricking the phone.
You saying that kinda reinforces what I was already thinking, that it might be a hardware issue. Im not sure.
5 minutes ago I was able to get odin to successfully flash BL, CP, and CSC. It even brought me back to the Samsung logo for a minute but hung there. That's the most success I have had with this thing. Ive flashed numerous firmwares and every single one of them fails on system.img.ext4. After it reboots, it boots directly into this altered version of download mode with an emergency recovery error.
I have flashed dozens of phones before without issue. This is the first time I have ever experienced this one. You could be right but I refuse to accept defeat in this case lol so im gonna keep trying and ill report back if I have success.
Click to expand...
Click to collapse
Man, that sounds very very familiar to mine. I don't know if you found my other threads where I was asking for help, but I woke up with a phone that wouldn't turn on. Finally found the key button combo to get it to soft reboot, then it would turn on and just crash in the middle of using it after anywhere from 30 seconds to 5 minutes. If i started to use the phone heavily it would just shut off instantly and reboot back up on its own.
After clearing the boot cache, then doing a factory reset, it finally just stopped turning on at all (just samsung boot logo loop)
So I hit it with odin, unsuccessfully for 2-3 days, and then out of nowhere it just finally took a successful flash. However, it still just bootlooped, so I did a factory reset again and it put it back to being toast.
Since then, not a single successful complete flash from odin. I too can do the BL, CSC and CP files but I can't flash the AP file as it is writing the most data and finally fails about 3-4 minutes into to writing the system image file.
Again...good luck, ha!
What's Happening :
When I turn on my phone, it gets stuck in pre-boot loop i.e. it gets stuck on initial mi logo(without loading sign) and stays there for (almost exactly) 10 minutes, meanwhile getting overheated, then gets restarted by vibrating & flashing the screen once, further just rinse and repeat.
It's actual state is unidentified i.e. IDK whether it's in soft brick, hard brick or broken state.
What I've Tried :
I've tried flashing the rom through fastboot mode.
I've tried flashing the rom through edl mode.
But always ended with the same result.
PS : I flashed the rom with 'clean all' option. I didn't used the 'clean all and lock' option, as unlocking the phone sometimes becomes a pain in the 'A', cause I'm pretty sure the result would've been the same.
Should I Try?
Using the 'clean all and lock' option.
Flashing another version of the miui rom.
What else to bring my phone back to life?
Final words :
On the time of writing this, I'm gonna keep troubleshooting and try some of these options as the time goes by, so I would let you guys know what I've tried.
If you guys are interested in knowing the back story a bit, LMK. I'd update the OP.
All I can say that I'm disappointed. Not a single reply and on xda, I don't have words to describe my disappointment.
Though I still didn't stopped and kept trying, whatever I thought could work. I got different errors from older versions of mi flash tools and similar errors with, newer but similar(interface) versions of the tool. The screen shots of unique errors are linked in this post. The newer versions got a similar error of 'Ping target failed (ping by firehose)' as I vaguely remember. Some newer/older versions didn't even run i.e. got error just by clicking refresh, as you can see with 2016 versions. The newer ones which didn't run were portable versions that showed this error or similar. The older ones ran some sort of installation, but you can't see them in control panel or any uninstaller (iobit in my case). So I'm gonna say they were portable as well just extracting the files. Though 2014-15 worked but 2016 one didn't.
When that didn't worked, I remembered someone saying in a mi thread that the emmc chip might be corrupted. Now I'm not a software engineer so IDK how to remove corruption at that level of software, if normal flashing doesn't work. As only the people who made that device would know the ins & outs at that level, or maybe some high level developer on xda/irl, IDK. But I didn't knew, so I went with the other route of fixing the hardware by reballing. As I'm not an expert in that either and I could've done it but it's such time consuming process and not getting a desired result after all that is an option, so I didn't wasted that much time. Only what I did is give it a heat treatment in hopes to revive it. But it din't worked it showed that blinking red led as it did before but it become somewhat of more dead. But I'm glad I tried my best.
SO THANKS FOR NOTHING GUYS.
Gurkirat_Singh said:
All I can say that I'm disappointed. Not a single reply and on xda, I don't have words to describe my disappointment.
Though I still didn't stopped and kept trying, whatever I thought could work. I got different errors from older versions of mi flash tools and similar errors with, newer but similar(interface) versions of the tool. The screen shots of unique errors are linked in this post. The newer versions got a similar error of 'Ping target failed (ping by firehose)' as I vaguely remember. Some newer/older versions didn't even run i.e. got error just by clicking refresh, as you can see with 2016 versions. The newer ones which didn't run were portable versions that showed this error or similar. The older ones ran some sort of installation, but you can't see them in control panel or any uninstaller (iobit in my case). So I'm gonna say they were portable as well just extracting the files. Though 2014-15 worked but 2016 one didn't.
When that didn't worked, I remembered someone saying in a mi thread that the emmc chip might be corrupted. Now I'm not a software engineer so IDK how to remove corruption at that level of software, if normal flashing doesn't work. As only the people who made that device would know the ins & outs at that level, or maybe some high level developer on xda/irl, IDK. But I didn't knew, so I went with the other route of fixing the hardware by reballing. As I'm not an expert in that either and I could've done it but it's such time consuming process and not getting a desired result after all that is an option, so I didn't wasted that much time. Only what I did is give it a heat treatment in hopes to revive it. But it din't worked it showed that blinking red led as it did before but it become somewhat of more dead. But I'm glad I tried my best.
SO THANKS FOR NOTHING GUYS.
Click to expand...
Click to collapse
How many times told u. Install telegram app on pc and join rn3 group chat . Xda is forum u wont get quick reply.
Rest u ur choice. Bye.
Black_Stark said:
How many times told u. Install telegram app on pc and join rn3 group chat . Xda is forum u wont get quick reply.
Rest u ur choice. Bye.
Click to expand...
Click to collapse
The device is dead, nothing can be done now. You replied, similarly someone more knowledgeable on the subject could've as well. But they didn't. Why? IDK, maybe the site doesn't promote/share topics the way they should, maybe it did and someone didn't wanna waste their time. So what's done is done, and the facts are there.
Gurkirat_Singh said:
What's Happening :
When I turn on my phone, it gets stuck in pre-boot loop i.e. it gets stuck on initial mi logo(without loading sign) and stays there for (almost exactly) 10 minutes, meanwhile getting overheated, then gets restarted by vibrating & flashing the screen once, further just rinse and repeat.
It's actual state is unidentified i.e. IDK whether it's in soft brick, hard brick or broken state.
What I've Tried :
I've tried flashing the rom through fastboot mode.
I've tried flashing the rom through edl mode.
But always ended with the same result.
PS : I flashed the rom with 'clean all' option. I didn't used the 'clean all and lock' option, as unlocking the phone sometimes becomes a pain in the 'A', cause I'm pretty sure the result would've been the same.
Should I Try?
Using the 'clean all and lock' option.
Flashing another version of the miui rom.
What else to bring my phone back to life?
Final words :
On the time of writing this, I'm gonna keep troubleshooting and try some of these options as the time goes by, so I would let you guys know what I've tried.
If you guys are interested in knowing the back story a bit, LMK. I'd update the OP.
Click to expand...
Click to collapse
Put the phone in the fridge and see if boots or not.
Or replace the battery. It seems like an hardware issue so that is the furthest possible to go.