On rooted V10_H901_V20J with Xposed mods. Everything has been fine for months. Overnight it shut itself off and now will not reboot past "Your device software can't be checked for corruption". Very occasionally it will get to the boot animation, but mostly not. After this point screen goes dark. Have TWRP but can't get to recovery with hardware keys or adb. Can't enter download mode. Only thing I seem to be able to do is get to fastboot, however "fastboot devices" does not show any device and no fastboot commands work. Advice would be appreciated.
*Update* - got it to get to TWRP briefly, went to do a reset and before I could do anything, it flashed black to dead again. Not looking good.
It sounds like "G4 death" (NAND lost connection with the motherboard.
After hours of attempts, gave up and took it to T-Mobile. No idea why or how, but they very quickly said "this is a warranty issue, we'll get you a replacement device". I've had this for 18 months, would've thought warranty was over by now.
Related
as i mentioned a few days ago, i recently rooted some vibrants for a few of my friends.
one of them decided to switch me phones for a few days just to see if he liked my phone (g2) since he wants to upgrade anyways.
so i unlocked his vibrant using this hex editor method. worked like a charm. popped in my sim and at&t came up, all was well with the world.
i was going to do a nandroid backup of his phone so i used rommanager to boot into recovery.
that didn't happen.
his phone hung at the samsung vibrant screen. i figured no big deal, maybe just a hiccup. pulled the battery and attempted to start the phone again normally, but still stuck on vibrant. tried a few more reboots with no new results. next i booted the phone into download mode which worked just fine. dl mode came up normally and was recognized by odin. still feeling creative, i decided to pull the battery while it was in dl mode then undo the usb cable. put the battery back in, turned it on and voila! phone booted like normal!
i was pretty damn confused. i could get it to boot this way about 1 out of every 3 tries. i thought perhaps changing the nv_data.bin file was what screwed it up so i replaced the modified one with the original and re-locked his phone.
so the phone boots up normally, i go to rommanager, tell it to install clockwork recovery, wait for it to finish and attempt to reboot into recovery mode, this time through adb. the phone still got stuck on the vibrant screen BUT adb still recognized that the phone was attached AND in recovery mode.
still confused. i'm assuming perhaps the adb functionality was due to restoring the original nv_data.bin?
so i rebooted his phone via adb and it turned on like normal, told him not to turn the phone off. i was going to take it with me to work today, but we're generally busy on saturdays and i won't have time to mess with it. gonna take it monday and try some more stuff.
so long story short; unlocked phone, wouldn't reboot into recovery, just hung on vibrant screen. put phone in dl mode, pulled battery, attempted boot and it worked. relocked phone, reflashed cwm in rommanager, rebooted via adb, still hung on vibrant screen but recognized by adb.
anyone ever had anything similar to this happen?
This actually happened to me once. Bit once i odin'ed back to stock it fixed it and it never happened again.
Hey guys, Today I just finished downgrading to HBOOT 1.4 and got up and running fine on TWRP 1.1.1 and ViperRom's new ICS build. I wasn't having any issues at all. I started reading about TWRP2 though, and felt like checking it out. So I downloaded GooManager and searched for TWRP and got openrecovery-twrp-2.1.3.blob. I touched it to download and it immediately went into recovery to install. However, as soon as it rebooted, it came up with TWRP 1.1.1's logo and a scrolling status bar. This lasted about 2 seconds and then the phone shut off. I left it as is hoping it would come back for about 10 min but nothing. I removed the battery and put it back in and tried to reboot. Booting to system and booting to recovery give zero response and ADB controls don't seem to recognize the device when plugged into USB. Can anybody help? TWRP2 doesn't seem to have a thread here and their site has limited resources for help.
thanks.
Can you boot into the bootloader (hold power and down on startup)?
no I cannot. Phone is completely unresponsive. I didn't think trying to flash a recovery would cause complete system failure.. wth
Just to be clear, before you call it a brick, did you remover battery for 10 seconds and then try to get to the bootloader. Hold down the volume first then the power button and keep holding both until the bootloader pops up. Just making sure...
yeah I did. Pulled the battery, left it out while I went and ate something, then plugged in the HTC charger and tried to reboot and nothing. Tried putting the battery back in and doing the same thing. I guess It's time to go to sprint and beg for mercy
Same thing happened to me. My phone is completely unresponsive after I tried to update to TWRP 2.1. I was on AOKP milestone 5a. The computer responds when I connect the USB, but the phone will not boot at all.
EDIT: Computer doesn't respond either. Think I'm headed to the nearest Sprint store ASAP.
Connect your device to your computer then go into your adb directory in cmd and type. "adb reboot-bootloader" (without the quotation marks)
Are you s-off ? And does the phone show up as qhusb_dload in device manager ? If it does it is bricked. If you still have s-on it can be fixed if you are s-off i am sorry to say you have to get a new phone. I have a phone now that is s-off and bricked and i cant recover it as of now but i am working on it, if i succeed i will post how to do it.
I would recommend trying to keep the bricked phone in case there is a way to unbrick eventually then you have another phone to play with. I just claimed my insurance and told them i dropped the phone in a porta-john at work and i wasn't about to fish it out. So they told me dont worry about sending the bricked phone in and i got my new one next day.
Here's my situation, maybe someone will find it interesting or know what's going on. I was running the EOS Jelly Bean (EOS-tf201-20120728-31.zip). Everything was running pretty well for a few days, then yesterday the device simply powered off. When I rebooted it got to the splash screen then shut off before it could get any farther. I figured it was a power issue, so I plugged it in and charged it for a while but get the same response. Around this point I started to get suspicious and tried to boot into recovery. It got to "Booting Recovery Kernel Image" then powers off the same way.
So then I proceed to go into fastboot and fastboot works great no power offs. Through that I am able to flash openrecovery-twrp-2.2.1-tf201.blob and the virtuous packaged boot as per this thread http://forum.xda-developers.com/showthread.php?t=1773280 as well as factory reset. I also tried a few other boot/recovery combinations and was able to make it into recovery. In twrp recovery I was able to install the latest Virtuous rom which got me back to stock and I thought good case closed. I even made it all the way into the OS and was able to install apps, wifi worked great, run the apps etc. Eventually the screen went blank though and I was stuck back in the same shutdown on boot scenario as described above. Now I'm able to fairly consistently flash openrecovery-twrp-2.2.1-tf201.blob, reboot, get into teamwin recovery, but now even that appears to be randomly powering off.
So now I'm guessing that it may just be bricked and is probably a hardware issue since the reboots appear so random, the unit was refurbished. At the same time I'm still holding out some hope that it's simply some boot code somewhere that was corrupted and I can flash something and get things back to normal again since I can still access fastboot and occasionally ADB and recovery. I've flashed from fastboot system/recovery/boot, any other thoughts or potential combinations I could try? Also anything I can do with those tools to debug it further and get more data on what may be the root cause?
I was on my phone when suddenly it just booted off for no reason, weird right? So now it just stays on the "LG" boot up screen and now do anything. I've tried everything and done everything right (as far as I know) before I get into that let me tell you what my device can do as of now:
Devices DOES have fastboot oem unlock done
Phone was rooted as well and working perfectly (or so I thought until this happened)
ADB doesn't seem to work, but fastboot when connected to the computer does.
Ex: ADB devices (blank)
but fastboot devices (shows phone connected)
I've tried rebooting into recovery (Power + down) doesn't do anything, however, {Power + down} then finger off power then {Power + down} again takes me to "factory reset" option, if done so the phone just hangs and removing battery on way to take it back to fastboot on pc, or bootloop again.
I've done the following steps using [LG-H901] Stock .img Files (Boot, System, and Recovery)
Code:
fastboot flash system system.img
then
fastboot flash boot boot.img
and finally
fastboot flash recovery recovery.img
I've tried booting the phone and still gets me stuck on bootloop, and doing the same {Power + down} gets to the same "factory reset" option only then freezes my phone if I agree to do so.
Is there something I've done wrong or incorrect? I will provide as much info as requested.
Thanks guys!
Update: Phone booted up to lockscreen after finishing "Android is starting..." procedures, then kept bootlooping and it is now doing "Android is starting.." procedures again. I'll keep it updated if it keeps doing so or anything of the sort.
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Double0EK said:
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Click to expand...
Click to collapse
This is the weirdest thing, phone worked for a bit then shuts off and does the same thing. all files and everyhing was in tact. ANy main reason behind this? I am desperate not to delete everything because i have important photos on there that were still there when it re-started again right now.
So to recap: At the moment doing the {factory reset} got me as far as using phone for like 2 minutes before ****ting out and sending me on a bootloop yet again.
Important Questions:
On all my other devices I am able to connect via usb and read devices, but on this phone I get the message when connecting to my computer "LGE Android MTP Device: Failed" whats this about?
Is there any way to save internal photo album images other than getting this to boot up and pray it stays on long enough to transfer data?
UPDATE 2: Phone has booted up and not froze (yet)? Testing to see if it will keep working so far so good. Unfortunately all my **** was deleted which bummed me out, would have honestly prefered to lose a $600 phone than all the family, friend, ext photos I had on my phone I made the huge mistake of saving to internal memory and never backing up. Smh.
Update 3: Phone is back at it again with the bootloop. I have no idea what is wrong, I've repeated the steps twice and phone doesn't seem to let up. It's fine until I hit that restart or shutdown button then it goes into bootloop heaven. I'm guessing this phone is done for? On an unrelated note it did fall on me, but worked fine afterwards, it was just sudden when it started doing this. Unless anyone has more suggestions I'd be glad to hear them. As of right now, this phone is toast.
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Double0EK said:
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Click to expand...
Click to collapse
I am thinking the warranty route. Is there anything specific I should do before doing so? I hear having "fastboot oem unlock" {Bootloader Unlocked} voids the warranty. Is this true that you might know of? Either way thanks I appreciate the information.
Sorry so late..
But you can try to fastboot oem lock it.
I have a Verizon Ellipsis 7 tablet that is stuck in a boot loop. When I turn it on, I get the "Powered by Android" screen and then the screen goes blank but lit, and never gets to the next stage. I tried entering Factory Mode and cleared the eMMC, but after doing that I can't even get back into Factory Mode. (I spoke to a Verizon rep and he said clearing the eMMC likely cleared too much, and it now lacks the proper kernels to start up.)
I believe this whole fiasco may have started when I used the wrong charger after having not turned on the tablet for months. I stupidly ignored the warning, and the problems started soon after (although it worked perfectly normally for about a day first). I now have the correct charger and have fully charged the device overnight, but nothing's changed.
I am trying to flash the device and install TWRP, from my Mac computer. However, since I can't get the device into Factory Mode, I'm not sure how to access it from my Mac. Simply connecting the device doesn't seem to make it discoverable. Is there anything I can do, or am I SOL?