Related
Hello ladies and gents,
So I'm a total noob and I think I bricked my phone.
I got root by using the motochopper tool
then I went for custom recovery, but I think I flashed the verizon version instead of the ATT version (I was trying to install the Google Wallet fix with a custom rom)
Rebooted the phone, I get an unlock symbol and samsung custom
I can boot into recovery mode and I still have root access / command line.
The phone either boots to black screen with a oscillating blue light or if I go into the other mode it says 'downloading'
Anything I can do to get my phone back working? Did I totally brick it?
Yes, if you see anything on the screen, that would be a soft brick, you are getting the unauthorized screen, then you need another kernel for sure, lets start there...
You really should either put your device in your information screen or tell us what type of device you have, that is very important.
I can not tell you what kernel, not knowing what device has the problem.
I see you mentioned att, is it US or Canadian version?
These are a must when you are seeking help.
I have the AT&T US Version of the S4, 1337
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
TheAxman said:
Yes, if you see anything on the screen, that would be a soft brick, you are getting the unauthorized screen, then you need another kernel for sure, lets start there...
You really should either put your device in your information screen or tell us what type of device you have, that is very important.
I can not tell you what kernel, not knowing what device has the problem.
I see you mentioned att, is it US or Canadian version?
These are a must when you are seeking help.
Click to expand...
Click to collapse
Do you have any type backup? Have you tried, power off phone. hold down power button and volume up at same time, when it vibrates, let go of the power button, it should go into recovery, and lets try restoring your backup.
Your problem is you have the wrong kernel loading, flash a ATT kernel once in the recovery, it will boot.
willenglishiv said:
I have the AT&T US Version of the S4, 1337
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
Click to expand...
Click to collapse
Just ODIN flash the stock firmware for ATT I337 and re-root? That's what I would try.
blyndfyre said:
Just ODIN flash the stock firmware for ATT I337 and re-root? That's what I would try.
Click to expand...
Click to collapse
Actually Ax has the best solution if he can get to recovery... your way will work but by far to many steps for something that simple...
just saying!!
sloanster said:
Actually Ax has the best solution if he can get to recovery... your way will work but by far to many steps for something that simple...
just saying!!
Click to expand...
Click to collapse
I agree Ax's solution is simpler, but OP said that he cannot boot to recovery.
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
Click to expand...
Click to collapse
blyndfyre said:
I agree Ax's solution is simpler, but OP said that he cannot boot to recovery.
Click to expand...
Click to collapse
But he can adb so he can push the kernel onto his phone and flash in recovery
Edit: my bad, he did say he can't boot into recovery. Odin is his best bet.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
he hasn't answered the get into recovery yet, nor has he said he has a backup. I was trying a simple solution. Then we can move on to the odin back.
TheAxman said:
he hasn't answered the get into recovery yet, nor has he said he has a backup. I was trying a simple solution. Then we can move on to the odin back.
Click to expand...
Click to collapse
Hope it gets it worked out!!!
The main thing is he's got options...:angel:
So was following the guide to root with the Step Bat Files provided by
HTML:
http://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
using the Dirty Santa Guide for Unlocking the Bootloader and Rooting the device. Yes I Already know the H915 is not listed but worth a shot anyway..... to me at least. So after finally going though each step bat file multiple times and it failing several times I finally have TWRP Loaded as the Recovery on the Device I can access the Bootloader however when I check the Bootloader it does say it is locked and fastboot oem-unlock gives me the error remote: unknown command. Note that fastboot oem device-id also gives me the same error. Therefore I can't unlock he Bootloader I can reset the phone through the stock method of holding down the power button and volume down button when booting the phone after resetting it each time It boots me into TWRP I can flash all the files I have tested such as BOOT Images and new system images.... I have been working on this since the guide was posted yesterday and been up since 2 (6 Hours now) trying to get this to work today.... I would like to just get into the phone to access ADB so I can possibly revert to stock or keep trying to root. I can flash anything and wipe anything to the device throughout what I have tested I'm an idiot and did not backup the Stock H915 Files once getting into TWRP..... yes I'm Dumb IK (But I also tried rooting my H915 for a Verizon/ATT Root so what do you expect). thanks again to anyone who can help!
TheDantee said:
So was following the guide to root with the Step Bat Files provided by
HTML:
http://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
using the Dirty Santa Guide for Unlocking the Bootloader and Rooting the device. Yes I Already know the H915 is not listed but worth a shot anyway..... to me at least. So after finally going though each step bat file multiple times and it failing several times I finally have TWRP Loaded as the Recovery on the Device I can access the Bootloader however when I check the Bootloader it does say it is locked and fastboot oem-unlock gives me the error remote: unknown command. Note that fastboot oem device-id also gives me the same error. Therefore I can't unlock he Bootloader I can reset the phone through the stock method of holding down the power button and volume down button when booting the phone after resetting it each time It boots me into TWRP I can flash all the files I have tested such as BOOT Images and new system images.... I have been working on this since the guide was posted yesterday and been up since 2 (6 Hours now) trying to get this to work today.... I would like to just get into the phone to access ADB so I can possibly revert to stock or keep trying to root. I can flash anything and wipe anything to the device throughout what I have tested I'm an idiot and did not backup the Stock H915 Files once getting into TWRP..... yes I'm Dumb IK (But I also tried rooting my H915 for a Verizon/ATT Root so what do you expect). thanks again to anyone who can help!
Click to expand...
Click to collapse
Try this
Power Off
Hold Vol Down
Hold Power
When The LG Splash Screen Appears Release Power for 1 Sec then Re-Press
Answer Yes 2 times
Yep. I was having the same problem with TWRP. The above was the only fix I found and it took me a solid hour to get the button combo just right. If you still have the red triangle like myself, the button combo happens before that pops up. To clarify, so you're not wasting your time like I did. You'll try the button combo listed in the quote as soon as the LG logo pops up. If it goes past that to the red triangle, you missed your shot. Pull the battery and try again.
Also. It should be noted once you get into that separate menu and answer yes twice to wipe the phone. It will throw you back into TWRP. Dont be discouraged! In TWRP go to reboot>system.
Hope this works for you bud!
Lonewolf17a said:
Try this
Power Off
Hold Vol Down
Hold Power
When The LG Splash Screen Appears Release Power for 1 Sec then Re-Press
Answer Yes 2 times
Yep. I was having the same problem with TWRP. The above was the only fix I found and it took me a solid hour to get the button combo just right. If you still have the red triangle like myself, the button combo happens before that pops up. To clarify, so you're not wasting your time like I did. You'll try the button combo listed in the quote as soon as the LG logo pops up. If it goes past that to the red triangle, you missed your shot. Pull the battery and try again.
Also. It should be noted once you get into that separate menu and answer yes twice to wipe the phone. It will throw you back into TWRP. Dont be discouraged! In TWRP go to reboot>system.
Hope this works for you bud!
Click to expand...
Click to collapse
Already picked up another just forgot to update this post thanks for the help though
Lonewolf17a said:
Try this
Power Off
Hold Vol Down
Hold Power
When The LG Splash Screen Appears Release Power for 1 Sec then Re-Press
Answer Yes 2 times
Yep. I was having the same problem with TWRP. The above was the only fix I found and it took me a solid hour to get the button combo just right. If you still have the red triangle like myself, the button combo happens before that pops up. To clarify, so you're not wasting your time like I did. You'll try the button combo listed in the quote as soon as the LG logo pops up. If it goes past that to the red triangle, you missed your shot. Pull the battery and try again.
Also. It should be noted once you get into that separate menu and answer yes twice to wipe the phone. It will throw you back into TWRP. Dont be discouraged! In TWRP go to reboot>system.
Hope this works for you bud!
Click to expand...
Click to collapse
So is it safe to say you have an H915 successfully rooted? Are you using it with Freedom Mobile?
SHABBA JOTS said:
So is it safe to say you have an H915 successfully rooted? Are you using it with Freedom Mobile?
Click to expand...
Click to collapse
Sorry, I should have clarified my friend. I have a VS995. Deleted everything without making a backup so now I am running US996 stock deodex rom with konverged kernel.
However if your stuck in a twrp loop, the instructions in the quote is what I'd try first as I seemingly exhausted everything else to no avail. And it turned out to be the easiest of the solutions and the only one that worked haha.
SHABBA JOTS said:
So is it safe to say you have an H915 successfully rooted? Are you using it with Freedom Mobile?
Click to expand...
Click to collapse
The H915 is flashable to the H918 System Image allowing you to access things like the Bootloader and TWRP I just F**ked mine up.... if your willing to try and get super su on there go for itim sure it is possible to get a root working for it.
TheDantee said:
The H915 is flashable to the H918 System Image allowing you to access things like the Bootloader and TWRP I just F**ked mine up.... if your willing to try and get super su on there go for itim sure it is possible to get a root working for it.
Click to expand...
Click to collapse
my only issue is the cellular signal, in the dirtysanta thread, they mentioned that it worked for the h915, but that the dev was having signal issues. I'm not inclined in this sort of thing so I can't really try until someone on the same carrier can confirm.
I'm in no rush tho
SHABBA JOTS said:
my only issue is the cellular signal, in the dirtysanta thread, they mentioned that it worked for the h915, but that the dev was having signal issues. I'm not inclined in this sort of thing so I can't really try until someone on the same carrier can confirm.
I'm in no rush tho
Click to expand...
Click to collapse
Could you not just reflash a H915 modem from a backup?
TheDantee said:
Could you not just reflash a H915 modem from a backup?
Click to expand...
Click to collapse
this should theoretically work.
I know for Samsung phones that was possible.
I had a Note phone from Rogers, and flashed it with a Galaxy S modem for Wind / Tmobile and it worked to unlock the AWS signal, that was not supposed to be supported officially.
I'm hoping LG phones are similar in that way, in which files / modems / boot can be transplanted from one phone model to another.
I'm just not familiar enough yet with LG phones, first time switching away from Samsung after soooo many years.
AllGamer said:
this should theoretically work.
I know for Samsung phones that was possible.
I had a Note phone from Rogers, and flashed it with a Galaxy S modem for Wind / Tmobile and it worked to unlock the AWS signal, that was not supposed to be supported officially.
I'm hoping LG phones are similar in that way, in which files / modems / boot can be transplanted from one phone model to another.
I'm just not familiar enough yet with LG phones, first time switching away from Samsung after soooo many years.
Click to expand...
Click to collapse
LOL yeah i came from a Note 7 to a G5 to the V20 so idk much about LG Phones yet...
Is flashing the h915 modem confirmed to work? I havent seen any posts about anyone with this varient being successful, but maybe most are like me and too incompetent to take the first step lol
Sent from my LG-H915 using Tapatalk
SHABBA JOTS said:
Is flashing the h915 modem confirmed to work? I havent seen any posts about anyone with this varient being successful, but maybe most are like me and too incompetent to take the first step lol
Sent from my LG-H915 using Tapatalk
Click to expand...
Click to collapse
I took many steps and got a Working TWRP Recovery and had a bootloader however when i went to flash in the ROM and then reset the phone it failed and I got stuck and had to get the model replaced... However I do know for sure that you can get TWRP and a bootloader working on the H915 using the DirtySanta Method from there is the hard part if your willing to take those steps lol.... MAKE BACKUPS! I have not tried to root my New V20 yet... If I get around to it I will be sure to let you know, some people have confirmed it has rooted but you do need the modem all high risk for the reward lol
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Did you get it fixed?
frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm
What roms can we use with dirty santa root?
me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.
Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.
Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir
Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you
Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.
So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery
Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...
can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.
Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.
So here is the lowdown, I just updated my LG G6 H870DS using uppercut+LG UP. The phone updated successfully.
So now, the phone got stuck at the LG boot screen. And I know that updating to a new version usually requires a factory reset for the phone to boot normally.
And this part, I did not anticipate, I booted to the factory reset mode for the device, only to find out about this 'kill switch' thing.
I've flashed other phones, though not recently. So I am stuck at the boot screen, with no way getting past it. As of now, I am downloading a Nougat firmware to downgrade it, but I am worried that downgrading back to Nougat will still yield at a stuck screen with no ways of a factory reset. Now, I've learned that I need to check whatever lock I might encounter before sideflashing firmwares.
I need all the help I can get mates, I had to use my S3 because my G6 is a paper weight currently.
UPDATE: So whenever I downgrade using LG UP, it would downgrade successfully, then the kill switch prompt would appear, but the factory reset would go through, so I end up okay on a Nougat downgrade. Now, upgrading to Oreo, the firmware would flash successfully, but it would not initiate a factory reset, it would just be stuck on the kill switch screen.
I didn't know the H870DS worked with uppercut+LG UP!
When you say 'updating' do you mean official updates that you can do with LG Bridge or what?
Just curious and hoping someone knows the answer to your question.
I had the same issue after rooting for some reason from 20a on the h872
I could hold vol - , and the power button. It would force a reboot that would eventually get it to boot sometimes. (Needed that in there) I ended up having to flash another, non stock ROM to get it to start acting right.
Don't know how much that'll help you but thought I'd throw it out there just in case.
Sent from my LG-H872 using Tapatalk
bick said:
I didn't know the H870DS worked with uppercut+LG UP!
When you say 'updating' do you mean official updates that you can do with LG Bridge or what?
Just curious and hoping someone knows the answer to your question.
Click to expand...
Click to collapse
Ken C said:
I had the same issue after rooting for some reason from 20a on the h872
I could hold vol - , and the power button. It would force a reboot that would eventually get it to boot sometimes. (Needed that in there) I ended up having to flash another, non stock ROM to get it to start acting right.
Don't know how much that'll help you but thought I'd throw it out there just in case.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
I never tried LG Bridge, the download for the firmware there would take a lot of time on my connection. So I just download official/stock firmware from LG's website. If nothing else works, LG Bridge would be my last option.
I know it just needs a factory reset after the update, but I don't know how to disable that kill switch. Already tried the OEM unlock on the options, and also removing my Google account; both of which are futile. So I'm using Nougat as of now. Too bad the H870DS don't have root/UBL.
jephimax said:
I know it just needs a factory reset after the update, but I don't know how to disable that kill switch. Already tried the OEM unlock on the options, and also removing my Google account; both of which are futile. So I'm using Nougat as of now. Too bad the H870DS don't have root/UBL.
Click to expand...
Click to collapse
Ya that kill switch thing I've never seen. I thought y'all with h870ds had already achieved root?
Sent from my LG-H872 using Tapatalk
Ken C said:
Ya that kill switch thing I've never seen. I thought y'all with h870ds had already achieved root?
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
I think the H870 has root, not the H870DS. So I guess I'll be trying LG Bridge when I get my type-C cable replaced. Will report back if successful.
jephimax said:
I think the H870 has root, not the H870DS. So I guess I'll be trying LG Bridge when I get my type-C cable replaced. Will report back if successful.
Click to expand...
Click to collapse
I've noticed myself that the stock cord seems to matter. My wife has the stylo4 and the cord is thinner and I was getting connection issues for data transfer through it.
Can you get the phone into dl mode? (I'm going off my H872 experience) that's how I was able to flash completely back to stock. May be worth looking into those threads. Reinstalls everything, you'll lose root of you have it and twrp also. Overwrites everything. Research first though because I haven't paid attention to your model.
There's one specifically on using laf in lgup, but I think it may talk about more than just that. Don't know how it would apply to you work your version but it couldn't hurt.
Just passing thoughts along.
I borked the heck out of a phone the other day and after finding bits here and there and taking all day I was able to bring it back from the dead after wiping system. Boot.Img, and the bootloader. Dummy, What a nightmare that was to get back
Ken C said:
I've noticed myself that the stock cord seems to matter. My wife has the stylo4 and the cord is thinner and I was getting connection issues for data transfer through it.
Can you get the phone into dl mode? (I'm going off my H872 experience) that's how I was able to flash completely back to stock. May be worth looking into those threads. Reinstalls everything, you'll lose root of you have it and twrp also. Overwrites everything. Research first though because I haven't paid attention to your model.
There's one specifically on using laf in lgup, but I think it may talk about more than just that. Don't know how it would apply to you work your version but it couldn't hurt.
Just passing thoughts along.
I borked the heck out of a phone the other day and after finding bits here and there and taking all day I was able to bring it back from the dead after wiping system. Boot.Img, and the bootloader. Dummy, What a nightmare that was to get back
Click to expand...
Click to collapse
Cord was just replaced, I had no problems using my girlfriends cable. So I already tried LG Bridge, and it seems to be not working because it cannot find a software version for my device (H870DS). I was thinking also of putting it in download mode then trying to restore it using LG Bridge if it would download and flash the Oreo rom or not.
LG Bridge would not work, so I am stuck on Nougat for now. Tried changing regional firmwares, hoping for OTA to work, but still it prompts me that the latest version is installed. So any help would be appreciated.
So yeah, that's the title. Stupidly tried to force my US996 to take the Oreo update by flashing the stock recovery (while using a rooted system) and installing the OTA afterward (which results in an error). At this point I started screwing things up by flashing TWRP (using fastboot) immediately after that (without booting to the system again) and ended up in a loop as a result.
Screwed mine up even further later on by using a misc partition-wiping command (from here: https://forum.xda-developers.com/lg-g5/help/stuck-twrp-recovery-t3587077/post71796008#post71796008) and ended up locking the bootloader + making TWRP unusable. Now, only fastboot and download mode works, and I'm seriously out of idea at this point.
I guess there's not much that can be done, but any help would be appreciated.
Also I made a Reddit post about this before, if it helps: https://www.reddit.com/r/lgv20/comments/ac6apr/got_stuck_in_an_endless_twrp_bootloop_tried/
phamanhvu01 said:
So yeah, that's the title. Stupidly tried to force my US996 to take the Oreo update by flashing the stock recovery (while using a rooted system) and installing the OTA afterward (which results in an error). At this point I started screwing things up by flashing TWRP (using fastboot) immediately after that (without booting to the system again) and ended up in a loop as a result.
Screwed mine up even further later on by using a misc partition-wiping command (from here: https://forum.xda-developers.com/lg-g5/help/stuck-twrp-recovery-t3587077/post71796008#post71796008) and ended up locking the bootloader + making TWRP unusable. Now, only fastboot and download mode works, and I'm seriously out of idea at this point.
I guess there's not much that can be done, but any help would be appreciated.
Click to expand...
Click to collapse
Start over with lgup and the oreo.kdz
Theirs forum post on both of these here, search or look around
If you can get into download mode your phone is not bricked
Sent from my PH-1 using Tapatalk
clsA said:
Start over with lgup and the oreo.kdz
Theirs forum post on both of these here, search or look around
If you can get into download mode your phone is not bricked
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I've already tried that when I locked my bootloader accidentally, and just tried it once again - doesn't work. The phone still boots into the recovery, with the "no command" error like before. I suppose that the phone is still trying to initialize the OTA update process at this point.
If it helps, flashing using DL Partition didn't work either. Still more or less the same.
phamanhvu01 said:
I've already tried that when I locked my bootloader accidentally, and just tried it once again - doesn't work. The phone still boots into the recovery, with the "no command" error like before. I suppose that the phone is still trying to initialize the OTA update process at this point.
If it helps, flashing using DL Partition didn't work either. Still more or less the same.
Click to expand...
Click to collapse
I'm in exactly the same boat. Let me know if you figure anything out and I'll do the same. Really frustrating problem.
txenglan said:
I'm in exactly the same boat. Let me know if you figure anything out and I'll do the same. Really frustrating problem.
Click to expand...
Click to collapse
I have a potential solution for you. I'll PM you.
Have you guys tried to wipe data from recovery
Did this solution work? Can you share it?
txenglan said:
I have a potential solution for you. I'll PM you.
Click to expand...
Click to collapse
merrickville said:
Did this solution work? Can you share it?
Click to expand...
Click to collapse
Yes, what I did was religiously follow what was posted at:
https://www.reddit.com/r/lgv20/comments/8b0c44/quite_hard_bricked_what_can_i_do_now/
Try that and let me know what happens.
txenglan said:
Yes, what I did was religiously follow what was posted at:
https://www.reddit.com/r/lgv20/comments/8b0c44/quite_hard_bricked_what_can_i_do_now/
Try that and let me know what happens.
Click to expand...
Click to collapse
Already tried that. My issue is 'no command', I can boot into Download Mode, and I can flash H915, US996, they all flash if I choose the Partition DL.
No matter what I try, LGUP reports my phone as US996, even after successfully flashing H915.
I'm stuck at 'no command' (without a recovery cuz I tried to get to it) and US996 apparently.
merrickville said:
Already tried that. My issue is 'no command', I can boot into Download Mode, and I can flash H915, US996, they all flash if I choose the Partition DL.
No matter what I try, LGUP reports my phone as US996, even after successfully flashing H915.
I'm stuck at 'no command' (without a recovery cuz I tried to get to it) and US996 apparently.
Click to expand...
Click to collapse
Strange. For me, the only thing that solved the issue was to purposely flash the wrong KDZ. I don't recall which one it was exactly but that's definitely what the solution was. Flashing the right ones lead to what you are describing.
txenglan said:
Strange. For me, the only thing that solved the issue was to purposely flash the wrong KDZ. I don't recall which one it was exactly but that's definitely what the solution was. Flashing the right ones lead to what you are describing.
Click to expand...
Click to collapse
My Hardware the U.S. AT&T H910, so both the H915 & US996 are both the wrong KDZ's
Okay, I'm not relegating this to a paper weight just yet.
merrickville said:
My Hardware the U.S. AT&T H910, so both the H915 & US996 are both the wrong KDZ's
Okay, I'm not relegating this to a paper weight just yet.
Click to expand...
Click to collapse
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
I can't find it now, but I followed a post Reddit post like that, and I had to use a LGUP_Hxxxx.dll file, his instructions were for two others (which provided the DLL's for), so I stopped there, because of the missing DLL file that I can't find with a search>
My phone is stuck at US996 (even when I sucessfuly flash H915 back to it, LGUP still shows it as US99610f).
Do you think I can find a LGUP_US996.dll file anywhere? No. And this post looked promising for getting me out of the 'no command' fix I'm in.
Edit: Here is the what I tried, not Reddit, but here. But, no LGUP_US996.dll. LGUP_common.dll, no, that does not work either.
txenglan said:
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
Click to expand...
Click to collapse
txenglan said:
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
Click to expand...
Click to collapse
merrickville said:
I can't find it now, but I followed a post Reddit post like that, and I had to use a LGUP_Hxxxx.dll file, his instructions were for two others (which provided the DLL's for), so I stopped there, because of the missing DLL file that I can't find with a search>
My phone is stuck at US996 (even when I sucessfuly flash H915 back to it, LGUP still shows it as US99610f).
Do you think I can find a LGUP_US996.dll file anywhere? No. And this post looked promising for getting me out of the 'no command' fix I'm in.
Click to expand...
Click to collapse
A couple of things come to mind
First off their only one patched LGUP for the v20
it works for all versions but maybe the H918 or Sprint LS997 model.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Click to expand...
Click to collapse
After using the H915_10e.kdz you have to flash the Full H910 rom on the phone
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
your choices are the rooted 10r rom or the unrooted 10q Stock rom
I also posted a back to stock Oreo 20G rom here > https://www.androidfilehost.com/?fid=1322778262903991071
Be sure and use TWRP for Oreo to flash it
After flashing those be sure and Format Data / Clear Cache and reboot
Damn....getting the right dll was also part of what I did IIRC. It's too bad it was such a long time ago else I'd have a more clear recollection of the exact steps I took. All I can say for sure, is that if you don't give up, you'll eventually stumble on the right solution.
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
clsA said:
A couple of things come to mind
First off their only one patched LGUP for the v20
it works for all versions but maybe the H918 or Sprint LS997 model.
After using the H915_10e.kdz you have to flash the Full H910 rom on the phone
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
your choices are the rooted 10r rom or the unrooted 10q Stock rom
I also posted a back to stock Oreo 20G rom here > https://www.androidfilehost.com/?fid=1322778262903991071
Be sure and use TWRP for Oreo to flash it
After flashing those be sure and Format Data / Clear Cache and reboot
Click to expand...
Click to collapse
merrickville said:
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
Click to expand...
Click to collapse
I have never seen the screen or error you described. Having a total of 4 v20 I thought I had seen everything.. guess not
Sent from my ONEPLUS A6010 using Tapatalk
merrickville said:
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
Click to expand...
Click to collapse
I wonder if this might work for you:
https://forum.xda-developers.com/v20/how-to/9008-test-t3855777/page13
It's an annoying process to have to go through but I revived mine when it was completely bricked (I couldn't even get as far as you because the phone wouldn't even turn on).
couple of thing that may help
No command screen is stock recovery being confused.
Try doing a factory reset using the volume - and power method (hold volume -, press power until the screen turns on, then tap power repeatedly until the menu appears)