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.
Related
Guys, I was an idiot about this, but I am at the end of my rope and could really use some help to try to fix things.
Here is what I did incorrectly:
Used TWRP to flash the wrong ROM
Created a backup in CWM format, not TWRP, so I can't restore it.
I have tried the three major methods on these forums multiple times to try to unbrick, with the following results:
Flashing official factory firmware with LG Launcher got hung up at the 12 s mark (when it transitioned to the "downloading software" step) for upwards of 15 min before I exited
Using the KDZ method seemed to work and actually got me really excited! But the "firmware update" progress bar on the download mode screen didn't move and a reset only ended up back at TWRP
Using the TOT method also appeared to start to work, but it failed because the build/dll didn't match. I have the VS98011A_01 version and used the TOT that I found in the thread.
Any help would be greatly appreciated.
Do you have the LG bootlogo coming up, if so try this:
(Something similar happened to mine, and I hope this will help.)\
Turn off phone, then when off, hold down power and volume down button until it reaches the LG logo and then release and hold it down again, if that doesn't work, when just hold it down until you see a screen that says something like: Hard reset/ factory reset. For me it took me to my recovery screen, where I just flashed a older ROM onto it, and you should be fine. I then later flashed a recovery file. I hope this helps, and if you need it any clearer, just reply :good:
Also from reading this, try flashing another ROM, if you have one present on the device, which will then allow you to boot-up then restore.
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. : (
Yesterday I accidentally installed the OTA update. I got stuck in TWRP and flashed a new ROM. Phone booted up fine, but now I have no cellular signal, nothing that uses video or sound works. Camera doesn't work, flashlight doesn't work.
I tried several different ROMS and nothing changes. Even the system sounds, ringtones and so on do not work. Anyone have any idea what I can do? Thanks
boot into fastboot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase misc
fastboot erase fota
fastboot erase boot
then pull battery and reboot into twrp by holding power and vol down, when lg logo appears then click the power button and re-hold it down to get into twrp.
once in twrp, check and see if system is mounted, if it wont let you mount, go to wipe and wipe everything (not ur sd of course)
System, cache, dalvik, data, internal, everything... the fastboot should have already done this but let twrp do it too..
once done, use the format option and format data also, some of these may error thats okay, just keep going..
once done reflash the full rom that matches your device.. let it flash and reboot and do its thing. this should fix the issues...
once it boots you may need to let it activate, or re-activate.
Only other suggestion would be if you have a twrp backup and you backed up your efs, its time to restore it also and see if the NV files have been damaged.
I've tried installing several different roms available on xda but that didn't resolve the issue. My phone remains in a boot loop state. Is there a way I can return to stock without compromising my ability to use the current root exploits?
Might help to know what you've got currently, are you able to get to recovery at all, etc?
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
My Solution
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
lanyueng said:
[MY FIX]
this post contains my working solution to the problem.
my problem is...
I accidentally clicked on 'install OTA update' on a rooted lg v20 t-mobile. A second after clicking it I realized that was the wrong button to press. AND so the start of the endless TWRP boot loop that allowed me to access TWRP to perform multiple tasks but couldn't boot back into my system UI where I can make phone calls.
I had this problem and spent days trying to figure how to get it back.
my solution is...
I tried everything to delete the *fota* and *misc* folders with fastboot; however none of the methods worked, until I tried the methods suggested in step#1 in "Stuck in a endless boot loop to twrp " in https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923.
So after deleting *fota* and *misc*, I had to exit the bootloop by 'reset all data option' by pressing YES twice. You read that right, you will have to agree to reset all user data by clicking YES twice. THO the effect will NOT reset all your data; it will just kick you out of TWRP recovery mode. I was pleasantly surprised to still have my data.
https://www.youtube.com/watch?v=tDq0qMbgjL4 That video shows as proof that it doesn't break things and also how to get into TWRP. You can also use the same methods to get out of TWRP.
Here's the text version:
1. hold volume down and power.
2. when lg logo shows up click power and re hold it while still holding vol down.
3. if you do it right in about 4 seconds or so it will boot to a menu, choose yes both times and you'll be back in (or out of) twrp. (yes you read that right!, don't worry you wont lose your data)
Hope this works for you as it did for me. I'm only posting because I didn't find a comprehensive solution post.
Click to expand...
Click to collapse
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
jluca98 said:
This fixed my issue. Thank you so much!
For further clarification, I had to delete all these folders that existed (I didn't have them all) using TWRP file manager. Make sure system is mounted. :
/fota
/misc
/data/fota
/cache/fota
/data/misc
/etc/fota
/system/etc/fota
Powered off after that, and then I manually booted into TWRP using the buttons method and hit reboot system and all was fixed.
Click to expand...
Click to collapse
This isn't working for me. Keeps rebooting to TWRP.
I get FAILED (remote: unknown command) with every adb command
Any ideas?
Drkphnxs2k said:
I could get into TWRP with no problem, I could flash any rom, but all would give me the same issues, no sounds, no flashlight, no cell signal. I think the OTA update messed something up. I ended up putting the phone back to stock, locking the bootloader and exchanging the phone for a new one. I got my new one today, it's on 10d, just tried to root it the same way as the last time and it keeps failing. I get the same problem as the guy on this thread https://forum.xda-developers.com/v20/development/helpt-easyrecowvery-t3543873
Click to expand...
Click to collapse
Don't use Easy Recowvery. Do it manually from the original thread. You can also google it for some sites that have cleaned the instructions up for easier reading.
I just did a H918 10d like this.
VS995 Unlocked with dirty santa, Konverged kernel, stock rom
The other day phone just randomly shut off without warning, battery was low (5%) so I figured battery just died. Went to plug phone in, got to the "device cannot be trusted" screen and to the LG screen, screen goes black, and gives me this yellow "RPM Crash" screen (see below). I can boot into fastboot just fine, and up until just a few minutes ago I was able to boot into twrp by flashing my twrp image as boot and rebooting the phone (if I use the button method it gives me the factory reset screens, goes to the lg screen, and goes back to the crash screen). I can reboot to recovery from twrp and it works just fine. Booting into download mode shows the download mode icon for a few seconds and then it goes black and to the crash screen.
Issues found/fixed so far
I saw in another thread someone had a boot.img issue so I messed with the boot1 and boot2 imgs from the dirty santa process and managed to get to a looping verizon screen with boot1 and the encryption unsuccessful screen with the boot2.img
In twrp my data and dalvik partitions were corrupted but I was able to reformat and repair them. (I found out when trying to wipe them in fastboot)
In fastboot, after working in twrp I was able to wipe and reflash all partitions except system I extracted from a kdz with no luck as far as getting past the error.
My system partition is currently wiped and I have not flashed a new system.img as fastboot won't let me flash it and I cannot get back into twrp to flash it.
I'm curious if this is more of a hardware fault than it is a software fault as download mode was also affected
Thoughts? Suggestions?
spalding1028 said:
VS995 Unlocked with dirty santa, Konverged kernel, stock rom
The other day phone just randomly shut off without warning, battery was low (5%) so I figured battery just died. Went to plug phone in, got to the "device cannot be trusted" screen and to the LG screen, screen goes black, and gives me this yellow "RPM Crash" screen (see below). I can boot into fastboot just fine, and up until just a few minutes ago I was able to boot into twrp by flashing my twrp image as boot and rebooting the phone (if I use the button method it gives me the factory reset screens, goes to the lg screen, and goes back to the crash screen). I can reboot to recovery from twrp and it works just fine. Booting into download mode shows the download mode icon for a few seconds and then it goes black and to the crash screen.
Issues found/fixed so far
I saw in another thread someone had a boot.img issue so I messed with the boot1 and boot2 imgs from the dirty santa process and managed to get to a looping verizon screen with boot1 and the encryption unsuccessful screen with the boot2.img
In twrp my data and dalvik partitions were corrupted but I was able to reformat and repair them. (I found out when trying to wipe them in fastboot)
In fastboot, after working in twrp I was able to wipe and reflash all partitions except system I extracted from a kdz with no luck as far as getting past the error.
My system partition is currently wiped and I have not flashed a new system.img as fastboot won't let me flash it and I cannot get back into twrp to flash it.
I'm curious if this is more of a hardware fault than it is a software fault as download mode was also affected
Thoughts? Suggestions?
Click to expand...
Click to collapse
I have a H910 that just received a screen replacement and I am also getting the yellow error screen. I am still able to get into Twrp though. However no matter how many times I flash a Rom, it keeps getting stuck at the yellow screen.
ozymandiasmusic said:
I have a H910 that just received a screen replacement and I am also getting the yellow error screen. I am still able to get into Twrp though. However no matter how many times I flash a Rom, it keeps getting stuck at the yellow screen.
Click to expand...
Click to collapse
Can you take a picture of of the screen, or is it identical to the one that has been posted? My guess is that you put the wrong screen on.
-- Brian
runningnak3d said:
Can you take a picture of of the screen, or is it identical to the one that has been posted? My guess is that you put the wrong screen on.
-- Brian
Click to expand...
Click to collapse
Here is the photo, sorry it's not the best quality since it's taken with a OnePlus One.
I had gotten the screen replaced by a cell phone repair shop. Luckily they still gave me the original screen. If it's a bad screen I will just get them to switch it out again...
You will have to upload a better quality picture for me to be sure, but I can tell you that you are getting an selinux failure for some reason when it is trying to load some driver. Again, I need a better picture.
-- Brian
runningnak3d said:
You will have to upload a better quality picture for me to be sure, but I can tell you that you are getting an selinux failure for some reason when it is trying to load some driver. Again, I need a better picture.
-- Brian
Click to expand...
Click to collapse
Sorry for the delay, I had the repair shop reinstall the original screen I was using. I am still getting an error screen, but I have my actual camera with me so here you go. I have tried installing a new ROM, I've tried doing "STEP3.BAT": https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 Because thought it needed a new boot.img
Still having errors. Any advice would be great. I haven't reverted back to stock because not sure how, and worried I'll lose twrp and would prevent me from actually doing anything.
I have a LG g4 that got the blue screen of death and it won't respond to anything I've tried so I'd say this is the same...........
my lg v20 started displaying this RPM crash screen two days ago. I am not certain what caused it, but it was immediately after charging it with a power bank. To boot mine, I have to plug the phone to a wall charger, once it shows charging, I press the power button and it will boot flawlessly, after that I am free to unplug it. I cant say if it wouldnt degenerate and I havent tried flashing the phone afresh. For now, I would back up my data to avoid surprises.
ozymandiasmusic said:
Sorry for the delay, I had the repair shop reinstall the original screen I was using. I am still getting an error screen, but I have my actual camera with me so here you go. I have tried installing a new ROM, I've tried doing "STEP3.BAT": https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 Because thought it needed a new boot.img
Still having errors. Any advice would be great. I haven't reverted back to stock because not sure how, and worried I'll lose twrp and would prevent me from actually doing anything.
Click to expand...
Click to collapse
did you try changing the battery?
ozymandiasmusic said:
Sorry for the delay, I had the repair shop reinstall the original screen I was using. I am still getting an error screen, but I have my actual camera with me so here you go. I have tried installing a new ROM, I've tried doing "STEP3.BAT": https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 Because thought it needed a new boot.img
Still having errors. Any advice would be great. I haven't reverted back to stock because not sure how, and worried I'll lose twrp and would prevent me from actually doing anything.
Click to expand...
Click to collapse
How do you boot into twrp? I am unable to. Are you currently able to copy your files from your internal memory to sd via twrp?
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!
Looks like you are trying hard to find a solution. I think it may be helpful if you try to manually install the o/s rather that using Wugfresh and report back any errors. See
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ At step 11 I would flash the individual image files and also follow the instructions re erasing and flashing userdata.
AFAIK you will not see an Android device when using Fastboot - Android hasn't loaded at this stage.
Thanks peterk-1. Unfortunately, this does not work. I followed the steps, with the exception of the radio file as my Nexus 10 is wi-fi only. It goes through the stock image update perfectly fine and reboots itself. At that point, it's back to the moving android at the 'erasing' screen.
One thing to note with the link you provided; no where does it indicate flashing a recovery, stock or custom. Now, I've tried flashing stock, TWRP and CWM and none seem to work. TWRP comes closest with the black/blue splash screen, but will not open further.
Any other suggestions would be appreciated.
You did go to the posted link? I quote:
Step 8: We now want to wipe the device. Use the following commands in order:
........
fastboot erase recovery
............
Step 11: We will now flash the system, boot, and recovery ..........................................
fastboot flash recovery recovery.img
Unfortunately, same result...