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!
Related
Alright, so I did a bit of a stupid thing and I acknowledge it. Anyway, here's my steps for what I did:
1). KingRooted the phone, SuperSUme'd to remove KingRoot's stuff
2). Flashed a deodexed ROM through FlashFire for OF1 using a how to list to upgrade and keep root(This is where I think I went wrong, I should have stuck with OC1 to begin with but I was curious ), the flash was successful
3). Because one of my apps(Greenify) requires the Xposed framework for many of the useful settings, I tried flashing a version of the framework designed for non-MDK bootloaders(Arter97's unofficial TouchWiz) through FlashFire, since it seems to be the only way to flash custom stuff on 5.0+ stuff at the moment
4). After this(Just like when I tried Arter's framework with regular OC1), my phone's Google apps started their mass crashing and force closing, which I tried to combat with factory resets but no dice
Unlike before, however, something along the line in my steps disabled the ability to go to stock recovery mode(I think it was KingRoot itself but it might have been the deodexed ROM) and after a bit I couldn't factory reset. Before, I was able to simply Odin flash the stock OC1 ROM. Now, however, Odin won't work either to restore the firmware. I always get the "fail" messages(This I'm not sure why, though it happens with both OC1 and OF1 ROMs so I don't think it's a matter of downgrading). This leaves me with very few options to recover from, especially because I've even tried Verizon's repair program(Stops at 83% and disconnects) and Kies' emergency recovery(Phone isn't recognized and upon manual recovery the result is the same).
The biggest thing that grinds my gears is that my phone isn't even bricked...technically. It started, it went to the Setup Wizard, but then the Setup Wizard crashed once the Gmail portion of the setup was supposed to start in an infinite loop....a "setup loop" rather than a boot loop. I have been working for hours to try and find a solution but so far nothing is working. My phone only starts to the "Software update failed, please use the Verizon Repair etc." message now but no program can recognize it.
Is this a form of hard-bricking? Just not having any method of recovery work even if it turns on? I will admit I'm not the most advanced user but I've been flashing ROMs and custom stuff(Using guides and the like, I'm not fluent enough to go freestyle) for years through a couple of different phones so I'm not a completely new user either. This is the most FUBAR'd I've gotten a phone so far though and I honestly can't afford a new one...that's why I'm going through all the paces I possibly can. Is there any possible way to salvage this? I've been wanting to go to the LG G3 anyway(Despite the G4 being out, the G3's cheaper and still miles better than any Samsung phone, my old one got stolen) but right now it's just not possible. Any suggestions?
Edit: After switching USB ports(Mine are notoriously bad for connections being gained and lost, my memory is bad but I can't see why I didn't think this was the issue), the Verizon repair method has made the phone able to start up. Everything seems to be in order now, more or less. I will say the custom Samsung screen(The unlocked one) came up which makes me think I still have the deodexed ROM installed. If so, then cool beans.
I have been at this for about 4 days, and I've spent literally all day today trying to get this to work. I'm having an issue with my phone where the battery is draining really bad, to the point that I have less than 3 hours of screentime on a full charge. I've read about mods and different installments you can use to fix this, but you have to be rooted. I was rooted before via Stump, but since then have unrooted back to the default. I tried to simply use Stump again but it says it's patched. After some research I found that I should flash back to a previous android version ( 10b ) and root it from there using Purple Drake, THEN use TWRP to update back to 5.1.1 lollipop. I'm running into some serious trouble flashing my Andriod. And I think its because it won't go into download mode. I turn it off and hold the volume button up whilst I plug it into the computer, and it goes directly into "Firmware update " 0%. And it has a progress bar, with no progress change I have no idea why it's doing this or what's causing this. I've tried the KDZ method, and it stops during the progress saying " Connection to server failed, please try again in a moment ", which I read was fine and to wait for a Green word on my phone screen and some changes, however the phone does absolutely nothing and sits on that same screen. I've tried the Lg Flash Tool method too, and there was an error saying " Failed Previous Load ()". I'm honestly exhausted and if someone could figure this out you'd be a lifesaver. Speaking of which, I'll buy you a whole bag of the fricking things if you do.
Any help is soooo very appreciated.
Thank you
Howdy,
Are you using the flash method described here?
You don't say which bootstack you're on. If you're trying to flash back from 35b you need a different dll. (LGUP8974.zip)
What Windows OS are you using to run the LG Flash Tools from? (It seems like success / failure can be very OS / USB Device driver related.)
For my phone, I had to get the flash tool ready to go - have the phone in download mode - and then unplug / replug the USB cable briefly on the phone in order for the process to initiate.
If you have some screenshots, that might be helpful too...
I was having problems with the phone, ended up doing a full wipe, and from there decided I'd upgrade to the latest Jasmine ROM. I did the upgrade, but as a result, WiFi and Bluetooth were broken. Tried a number of solutions and none worked. Eventually tried a couple different ROMs, same problem. That said, I WAS up and running. I even flashed 35B bootloader again and tried with the ROMs. Still no luck. This was last night.
Flash forward to today, I'm trying again to flash Jasmine, and in the middle of the flashing process, screen turns off and I get the blue/green strobe light effect like when you power up normally. Oh ****. Leave phone for 45 minutes and realize it's in a loop. Responds to nothing, pull the battery, know I'm ****ed at this point.
Now, I can't get the screen to come on. Can't get into recovery or anything. Holding down the power with any combo of volume and other keys does nothing 90% of the time. About 10% of the time, I can get the phone to vibrate, then start the blue/green strobe, but nothing happens even after half an hour. I've recently discovered that if I plug into USB, I get a slow, slow flashing red light. As in the light is fully lit for three or four seconds, slowly fades out for a second or two, then slowly fades back. It doesn't appear to be communicating with the computer through USB, just drawing power.
Any suggestions? I'm 99% I'm screwed, so I'm willing to give anything a go.
The reason it happened is if you already had the 35B Bootstack (not bootloader - that's only part of the Bootstack and the 35B Bootstack actually uses the 12B Bootloader) before flashing JasmineROM v9 and you didn't flash any Bootstack after flashing the ROM (either 24B or 35B), then JasmineROM's limited selection of 24B partitions overwrote only select 35B partitions, leaving a catastrophic mix of critical 35B/24B partitions.
If you remove the battery, then put it back in and go through the motions of putting it in Download mode, even though you can't see the screen you can verify it's in Download mode by looking in Windows' Device Manager in the Port section listed as "LGE...".
If so, flash the 10B TOT and you'll be good to go, start fresh, and get in the habit of always flashing an appropriate Bootstack after either flashing a ROM or restoring a TWRP Backup.
@nyr2k2 any updates on this, did you get it fixed?
i have not yet had the opportunity to try, but between what you wrote and a pretty detailed explanation provided by @cory733 via PM, i feel pretty confident i would be able to. i ended up just going ahead and getting an s7 edge, and i haven't had the time to work on this. i do intend to give it a go and bring this thing back from the dead...it was/is a solid phone.
thx for the help.
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?
I only want my Wogiz WX40 to work properly again. It somehow got into a booting loop and I spent many hours figuring out how to flash it due to drivers acting unexpectedly, incorrect instructions for my device and so on.
I finally got it to flash with stock software I got from needrom using SP Flash Tool. However 1) none of the bottom keys work now and 2) it looks as if the resolution is set too high for the device and I think there is also some slowness when using the phone. I have tried clicking upgrade firmware and formatting the entire flash and using different versions of the software and the result is always the same - the bottom keys not working in particular makes it unusable. I tried downloading the stock rom from another location but after downloading it said I needed a password.
So what is the next thing I can try? I'm at my wit's end here and just want it to work again. Thanks for all help.
Anyone know what I should try? For example what custom RAM + firmware might I want to try? At this point I don't care what it is as long as it works. It's a MT6580 device if that helps.
God, I FINALLY got it working.
In case there's anyone else that runs into this: My mistake was getting the stockrom from needrom, every one of those roms for this phone is bad. Get the rom from shareas.us and use SP Flash Tool to flash it, and even then you have to try to get the one that isn't password protected with no password. Leave the battery in, turn the phone off, use option "format + download" in the software and click download BEFORE you connect the phone, NOW connect the phone and after a little while it will start downloading. Disconnect the phone when it's done and switch it on, it will take a REALLY long time to boot up the first time but it should then work.
That's what came from hours of trying to get it to work. The tutorials etc. online are so confusing, even some incorrect instructions like saying I should take out the battery that are completely false and I would never have gotten it to work if I paid more attention to them. I don't ever want to go through something like that again. I finally have my phone back.