Have had my girlfriend's h910 rooted for close to a year no issues. She was pretty happy with the first rom we flashed which I think was WETA. Never flashed a custom kernel or anything so she's always covered the sensor on the boot static for a sec to get past it. Today though it won't boot past the static at all. Have gotten it to factory reset/ twrp once but it rebooted to static instead of twrp. Download mode shows the initial download mode screen for about 10 seconds then straight to perma static. ADB not recognizing phone.
Tried googling and searching through all the unbrick threads but unable to find anything.
Sent from my OnePlus 5 using XDA Labs
Do you still have fastboot? With the phone off, hold vol DOWN and plug in the USB cable.
If you do, then as long as it isn't a hardware problem, you can reflash TWRP, and then see if any of your backups are there (you did make backups right?). If you didn't you can at least flash a ROM.
If fastboot isn't available, then somehow an update got installed and you will have to flash the H915 KDZ and root all over again.
-- Brian
I actually have this exact issue. Fastboot only. Did you ever figure out a way to fix this issue?
Related
After a few days of running the annoyingly buggy CM11 nightly for the D800, I decided to flash Mahdi. I grabbed the ROM from here, and being the idiot that I am, I wiped and flashed it without first checking if I needed the baseband or anything. It installed successfully (or so it said). I reboot, and BAM. Fastboot mode. At this point, I can't boot into recovery in order to restore a backup, and I can't boot into the system. Fastboot only. I then asked for some help on Reddit's /r/lgg2, and a great user helped me get out of fastboot by flashing several of these partition images. I was so happy when I found out that it no longer went into fastboot when I tried to reboot into system. However, all it does now is stay at the LG boot screen (apologies for horrible quality). Download mode gives me this. SuperSport's method doesn't help, nor does any other method I have come across. The LG FlashTool always gives me errors about my device not being a G2, because I think it is recognized as this "B100" model that I've never heard of. I really don't want to have to bring this to an AT&T device center, because they'll probably try to charge me some absurd amount for a fix that takes them 30 seconds. However, I don't want to be stuck using my scratched up S3 that can't hold a charge.
ANY help is appreciated!
Did you try with ubuntu or linux to flash the right partitions?
Sent from my LG-D800 using Tapatalk
Yes. Got me out of fastboot, but now I can only boot into download. When I try to boot into the system, I just get the LG logo and the notification light pulses.
Anyone? AT&T apparently doesn't have the G2 stock firmware, and told me I would have to ship it off to LG.
can u screen shot the lgflashtool what error u get?
u downloaded the d800 tot file?
and the LGUP_8974.zip file?
Short version: Phone is boot looping at LG logo and when I try to volDown+power into recovery it gets to the factory reset prompt and I press power twice but nothing ever loads and the backlight just stays on. I'm guessing I no longer have a functioning download mode either because of the way these flashable bootstack zips we've been using on the VS980 ROMs mention that they disable download mode, so I probably can't use LG Flash Tool either. Bricked?
I had been on CloudyRom 1.3. I switched back to xdabbeb's VS980 ROM, the newest version with the 25B bootstack. As many people ran in to, for some reason after coming off of Cloudy, KnockOn doesn't work on other ROMs. I had tried to do this hidden menu trick to update the touch screen firmware which some people reported got the KnockOn working again. Long story short I was having trouble getting the hidden menu trick working while on the xdabbeb ROM, I went back to Cloudy ROM and tried to do it but that didn't fix it either. I saw people having success by going back to a purely stock ROM and doing the hidden menu trick from there.
Here is where I probably messed up, I had a backup from April of this year that I didn't have labelled/named well but I was certain it matched up with the last time I had probably been on a purely stock ROM when the VS980 finally got KK earlier this year, a backup I had made for the convenience of ever having to return to stock. I tried to restore this and that's where the trouble happened. At the time I figured worst case scenario would be that the baseband wouldn't match up and I wouldn't get a signal, but in hindsight I'm guessing it wasn't safe to try to restore this after updating to different bootstacks. Original KitKat rom was 24a I believe but I had just recently updated to 25B to use the newest xdabbeb ROM.
I saw a small ray of hope when I calmed down enough to remember the voldown+power sequence to get into recovery, but after reaching the factory reset prompt and pressing power twice to continue, nothing ever loads and the backlight just stays on, like my recovery is gone now too I guess.
And in a comedy of errors I'm guessing I no longer have a download mode that would allow me to use the LG Flash Tool through PC because these flashable bootstack files always mention that they disable download mode and I never worried about restoring it.
So, bootloop, can't get into recovery, probably can't get into download mode to work with LG Flash Tool.
Screwed? :crying: :crying: :crying:
Yeah, volUP + plug into PC just gets me fastboot mode.
Don't really understand why my recovery is gone, thought the button sequence to get back into recovery was the safety net to this entire thing and why I wasn't too worried. Was running TWRP.
I'm at the mercy of checking the internet when I have access to another computer because my phone was also my internet access on my home PC. Hoping someone can help. : (
So I think my Nexus 6P is hard bricked, but I just want to be sure before I issue an RMA.
I was on a plane flying over the Pyrenees and opened the camera to take a picture. The phone froze and started rebooting, which I found strange really strange as it never happened before. Since then, it wasn't able to boot again. The phone is completely stock, running 7.0, apart from the unlocked bootloader that I had unlocked the day I bought it (March/April this year). The phone shows the unlocked bootloader warning, goes to the white Google logo with the padlock below, and then goes back to the unlocked bootloader.
From here I can Power + Vol down and get to bootloader, which I thought would leave me to recover the phone somehow. I know my way around nexus devices so the first thing I tried was scrolling in the bootloader menu and boot into stock recovery. No luck, unlocked bootloader warning, white Google logo and loop. Tried "Factory" in the menu and the same thing happens.
So then I've gained access to a computer and tried downloading a twrp recovery and boot into it. Ran fastboot boot twrp.img, the phone tries to boot again, and the same thing happens. Boot loop. After that, I've downloaded the latest stock Google images and I've run a different set of things, all with no luck. Booting directly from fastboot into stock recovery doesn't work. Flashing stock recovery and trying to enter stock recovery via bootloader menu doesn't work. I've erased and flashed bootloader, radio, and all other partitions (system, boot, recovery, vendor and cache), without any luck. The fastboot commands return "OKAY" but it seems like it's doing nothing.
I am out of ideas, I always thought I would be able to recover a Nexus phone as long as I could reach bootloader mode, but I guess I'm wrong. Should I RMA, or is there anything else I should try?
Thank you.
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
vladniko said:
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
Click to expand...
Click to collapse
Done both, actually. Tried to boot directly from a fastboot command and then tried flashing the actual recovery image to the phone. No luck in both. Never able to get into twrp.
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
hubhib said:
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
Click to expand...
Click to collapse
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
eddie_gordo said:
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
Click to expand...
Click to collapse
Needed the RMA anyways. If you had an unlocked bootloader and formatted each partition and then flashed each partition with the corresponding image file from the latest factory image, it was shot. It happens from time to time. Happened to mine as well. 2 or 3 days after I finally got it (pre ordered on launch) I rebooted the phone at some point 2 or 3 days later and it just never turned back on. 100% bone stock. Not even an unlocked bootloader. Nothing would happen when I plugged it into a PC, left it on AC power for hours and hours and still nothing. Holding power 10-15 seconds, nada. RMA'd and luckily this one's been perfect ever since. Good luck with the new device!
I've had some problems with my phone. My first phone ended up getting bricked 2 weeks after i bought it.
I was lucky enough to get it replaced by the store. After that i was careful with unlocking the bootloader and rooting.
I had some issues with the rooting (i have posted this in other threads already, so i won't bring that up again) ending up with having to flash a stock version of 574 from a page with roms available.
I was happy to see that the phone was again working. But ever since i flashed the stock rom, things are becoming very strange.
I'm unable to flash TWRP. The only way to access Fastboot is by first connecting the phone to the computer. And then hold vol down and power.
I am able to access Huawei eRecovery (but only by doing like with Fastpass using the computer).
I'm not allowed to update eRecovery or run recovery from eRecovery.
If something require a reboot, i need to use the cable, fastboot, vol+ into eRecovery and then select reboot.
Today i was prompted to upgrade from 574 to 584 (OTA) and the download and installation begins normally.
Only to end up having to... you guessed it:
cable+fastboot+eRecovery.
And the update fails.
The phone is working great apart from these issues. And i do not know why.
And this is why it feels like it is in some Twilight Zone. Or Hybrid-mode. Bootloader is unlocked. Firmware is stock.
But i always need to use the cable to start the phone.
Does anyone have a clue what is going on?
What kind of error it gave when you tried to flash TWRP?
No error. When i do adb reboot the phone shuts down, but does not reboot into fastboot.
If i first go into fastboot and flash twrp everything appear to be ok. But when trying to reboot nothing happens.
So this is a weird one for me. I've been running an H910 on an LOS 16 build from I think August and Gamma kernel 3.0 (never found the time to update stuff), and a couple nights ago I had the phone completely freeze on me while switching browser tabs, wouldn't even shutdown after holding the power button for ~30 seconds, so I pulled the battery to restart it. However, when I powered it on, after the initial LG logo I just got a screen of unchanging static IDENTICAL to what this poor soul had in the third photo of his linked album. My anxiety then ramped to 10 when I tried booting to recovery and after the "are you sure you want to delete your data" prompts I was greeted by the exact same screen. Booting to download mode would show the same screen after the few seconds of the "download mode" photo, and looking back I'm pretty sure it was just booting to download mode after encountering an error when I tried booting to system or recovery.
The bootloader was A-OK though, so the first thing I tried was flashing the latest TWRP, which seemed to work. I was able to boot into the system, but it was pretty buggy (the open apps button didn't work), so I tried booting to recovery, but it still gave me the static. I booted to system and it worked again, so I went back to fastboot and flashed the recovery again, which put me back where I started, static on everything but bootloader.
At this point I came to terms that things were getting wiped and began looking up what I could do in terms of KDZ flashing. I first settled on converting to US996, so downloaded US99610f_00_1205 and after dumping my system tried flashing it with the patched LGUP using the partition DL option. When I did, it cleared up the static issue in download mode showing the "Firmware Update" header and everything beneath it, but then download mode was still what recovery and system would boot to. I could boot to fastboot, but my bootloader was now locked. I tried that a couple times, but always got the same option, and the "Upgrade" option in LGUP would always return an invalid KDZ error due to H910 -> US996. My device still showed up as version H91010v as well. I then tried flashing over the H91510e_00_VTR_CA_OP_1205 KDZ as described in this thread for getting H910 root, but this gave me the same results.
So that's where I am right now, a phone with nothing but Download mode and where using Partition DL to flash stuff doesn't seem to actually flash it. The program I've been using is the LGUP files in this thread that's always linked. Any help on what next steps to take would be greatly appreciated, thank you.