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.
Related
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
Good night everybody! my dad got this phone a while ago, after like 2 months he told me the phone was going crazy, I checked and was getting FC´s everywhere so get into recovery mode to wipe everything and there´s where problems started. I downloaded stock firmware and installed it but phone wouldn´t boot up, so my dad gave it to a guy that ``fixed it´´ but the problem came back after two weeks or so, the guy ´´fix it ´´ again but when I looked into the phone had no IMEI so didn´t recognized the sim card, the third time the guy got back the IMEI, that was long ago and today when I booted up the phone is having a weird behavior, sometimes gets stucked at the bootloader unlock warning, I restart it and after a couple of times starts the boot up animation but gets stucked at the M and like waving part.
I´ve tried getting into recovery mode but when I press any of those options boots to the warning bootloader. I got it to completley turn on when I pressed the recovery option; not expecting that to happened, but again some force close windows and decided to reboot it to see if would fix it but again to the same place stuck at the warning.
I´ve read many posts here im xda and outside but can´t find a solution. I tried to side load the firmware but looks like the pc doesnt recognize the phone´, when i got it boot up I connected it to the pc but didn´t recognized it, I installed the drivers and still the same.
Guess I need to get it recognized by the pc in order to try to side load a firmware. Sorry for the long post and any mistake, if someone can help to bring back to life this little fella.
Okay so my phone randomly rebooted 2 days ago and when it got to the LG logo screen it froze. I tried to hard reset it, i went in to the hard reset menu clicked yes once then confirmed the hard reset by selecting yes a second time and the phone froze on highlighted yes. I have pulled the battery and tried to do this multiple times to no avail. So next i went to my PC and started google searches. Often i found things such as being stuck in boot loop which my phone wasn't, it was just frozen at the LG logo screen. Regardless I like to think of myself as self educated tech savvy (which now from reading all of your posts im not, im not even a little bit, in fact im tech stupid.) I did follow post through to the LGUP tool and downloaded a stock KDZ and got my phone into download mode>firmware update screen, i was able to get al the correct drivers and get LGUP to recognize the device and i loaded the stock KDZ and tried to do a Complete wipe reinstall. The program as able to interact with my device and went through the process, i thought i had fixed my phone. After a fresh install(or what i thought was a fresh install) i rebooted after the update and went to the LG logo screen and froze. The only difference is now when my phone starts, right before the LG logo appears i get the green android robot with what looks like open working "guts" real quick before it goes to the Logo and freezes. So back to the drawing board and i wanted to attempt some of the things ive seen like TWRP recovery etc but here i am getting lost. Forgive me if im posting things that have been answered but i keep getting confused. I dont know what the difference is between fastboot boot loader recovery mode or any of that is. also i kept noticing time and time again that my phone has to be in USB debugging mode and i dont know if it is. I cant turn my phone on to get it into USB debugging mode now anyways. Im okay with my warranty being voided and im okay with rooting if thats what i have to do to make it work. I have installed ADB and fastboot and some twrp recoveries etc but im clueless. Lastly know that i never Rooted my phone or anything but i was a torrent downloader. forgive me im triyng to provide as much information as possible.
PLEASE NOTE - I had to sign up to post here obviously and i loved how it said if you have an IOS go buy an android and come back LOL
Message Tung Kick. He can get u out of any thing
Hit thnx if this helpd
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?
Hi,
So I've had a lot of trouble getting TWRP flashed to this phone. After a bunch of tries I got stuck in a bootloop but I was still able to enter fastboot and recovery. I then flashed the stock fastboot ROM which fixed it and I was able to get back into the system.
I then hooked it up to my laptop again, but when I went to turn it off to get back into fastboot mode it just doesn't do anything except bootloop. I get to see the Redmi logo for a few seconds, and then it just endlessly reboots.
I can't enter fastboot nor the recovery, otherwise this would've been an easy fix. I also can't turn off the phone. Does this mean I'm ****ed? I saw the post before me where somebody seems to have the same issue, but their phone doesn't show anything on the screen at all, which is why I'm not sure if I hard bricked it or not.
It's strange too, because I have plenty of experience flashing bootloaders and ROMs, even with other Xiaomi phones, but this one has been a pain in the ass from day one. I made sure to not use anything not meant for my region (EEA) or phone model (Camellian) so I have no clue what went wrong. Any ideas?
iamkaruna said:
Hi,
So I've had a lot of trouble getting TWRP flashed to this phone. After a bunch of tries I got stuck in a bootloop but I was still able to enter fastboot and recovery. I then flashed the stock fastboot ROM which fixed it and I was able to get back into the system.
I then hooked it up to my laptop again, but when I went to turn it off to get back into fastboot mode it just doesn't do anything except bootloop. I get to see the Redmi logo for a few seconds, and then it just endlessly reboots.
I can't enter fastboot nor the recovery, otherwise this would've been an easy fix. I also can't turn off the phone. Does this mean I'm ****ed? I saw the post before me where somebody seems to have the same issue, but their phone doesn't show anything on the screen at all, which is why I'm not sure if I hard bricked it or not.
It's strange too, because I have plenty of experience flashing bootloaders and ROMs, even with other Xiaomi phones, but this one has been a pain in the ass from day one. I made sure to not use anything not meant for my region (EEA) or phone model (Camellian) so I have no clue what went wrong. Any ideas?
Click to expand...
Click to collapse
I think you are on the wrong forum, this is for Redmi Note 10 (mojito/sunny)