I have a LS998, that has been bootloader unlocked, crossflashed to a US998, then back to a Sprint ROM.
earlier today, I attempted to flash the stock US998 ROM, and then manually push the modem/modemst1/modemst2 to my phone via adb shell.
rebooting after said push, i have lost wifi (the toggle just flips back to 'off' after turning on, or just stays grayed out). i have also lost 3g data, which i always had, regardless of what ROM was flashed (my phone runs on Sprint, fyi) ..
I have so far, attempted to flash the US998 Oreo KDZ onto my phone. It flashes successfully, and boots, but i have no data connection whatsoever. it seems regardless of what I flash, in what order I flash it, nothing is helping. Flashing the Sprint ROM that i have been using up until this point yields nothing as well.
I have tried starting at the beginning again- LGUP the nougat KDZ (which just gives me a bootloop for some reason), then LGUP the Oreo KDZ. again- successful flash, successful boot, but no wifi nor 3g data. no ability to edit my APN's that i can see, but at this point im so damned flustered I could be missing the blatantly obvious.
Does anyone have a fix for what ails me, please? I am in need of some serious hand holding here.
edit to add:
LGUP no longer recognizes my phone as being plugged in. i have TWRP, but regardless of what I do, it just boots back to TWRP over and over again. and again. and again.
my PC does something when i plug in my phone in download mode. my phone reacts to it.
im assuming it is a paperweight at this point?
update:
phone sat overnight, off. upon first boot, i tried download mode on my PC. this time, it was recognized, and allowed me to succesfully flash the Oreo US998 KDZ.
upon reboot, this time, i had working wifi. flashed TWRP, wiped old stuff, reinstalled my Sprint DD rom. rebooted, and had working wifi again. this allowed me to ##update# , and provision my phone for Sprint's network.
i have verified successful calls, SMS, LTE, root, etc.
i have no idea what was done differently this time around. Frankly, I dont think i did anything differently.
Consider this 'closed' but not 'solved'
Related
I'm pretty much ****ed with my phone.
First thing is, i can't update my phone, within the option menu, automatic update or manual one with dload folder doesnt work, The software upgrade mode never shows up, i have instead a very nice bootloop, i have to play with the VOL+ VOL- and POWER button untill i can finnaly boot.
Because of that, i'm stuck with Emui B130.
Wouldnt be that bad, if only my phone worked. But i can't take phone calls, nor send texts (or rarely can, almost only at my home, and if i'm lucky) When i travel i instantly doesnt have network anymore at all.
The phone detects my Sim Card, and i have some network, but i almost can't use it at all.
I tried to patch via fastboot the B100, B121 and B130 versions. All 3 have the update issue (S/W never shows up) and the network one PLUS the B121 version doesnt even allow me to insert my pin code.
So at this point i have a phone stucked in B130, which cant be updated, and i can't use it.
I tried to patch stock recovery, remove root, reinstall root, change the versions, i still can't access the S/W mode meaning i can't update the phone at all.
I just don't know what to do anymore, i've tried everything. I'm stucked.
Thanks in advance for eventual help.
Are you trying to update with root? You need to unroot first before you update. I haven't experimented with my phone yet but on my previous Huawei I always had to unroot before updating via dload/OTA
I tried both root and unroot, this doesn't change anything. :/
What happens when you press VOL+ VOL- and POWER on an honor 7?
Culdnt this be an Imei issue ?
Gosh This is so stupid, nothing works fine.
Now my phone just bootloops. I tried to flash with fastboot system.img and boot.img from B130, B100 and B121, and i can't make my phone to work, it just bootloops.
I thought i found the issue, i tried to flash the modem.img from my firmware, but couldnt manage to do it, and now i can't even make my phone to work. I'm so tired already of this phone. Everything was so simple with the Note 3.
Edit: And now i can't even try to flash some stock roms as i have a " Cannot load 'System.img' message.
I've done this more than 20 times and now for absolutely no reason, i have this.
I'm about to give up this phone. This is just madness. I just don't know what to do anymore.
I'd realy appreciate help of any kind.
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!
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?
Hello all, got a bit of a strange issue here. So I was using the 30b release from runningnak3d, https://forum.xda-developers.com/tmobile-lg-v10/development/h901-t-mobile-nougat-v30b-twrp-t3639203
I was selling my v10, so I did a reset, skipped or hit next to everything, and verified that all was working. I sold the phone and a couple days after the buyer got it, he told me it was bootlooping. I asked what he did and of course the first time he said nothing, just turned it on. After more conversation, he said when he got it it booted and after a while told him an upgrade was available. He said he accepted the upgrade, and afterwards got the bootloop.
I got the phone back today to try to fix it and give it back to him. Here's what I have found. Definitely bootlooping, stops at T-Mobile logo and reboots. It does still have the unlocked bootloader, still shows the warning right at boot. TWRP is gone! I booted to recovery, answered Yes to those 2 questions, and it did a reset instead of loading TWRP.
I really have no idea what he did, whether is was an OTA update or maybe he tried to load something on his own.
So, is there any hope of getting this thing going again? So far I was able to boot it into download mode, but it won't respond to any fastboot commands. My computer detects it, but in computer management it says LGE USB modem or something like that. When I try to regular boot, the computer does detect the phone, but it doesn't get far enough along to issue ADB commands. I'm thinking it's a paperweight at this point, so I'm game to try whatever.