Related
Hey guys.
Tonight I rooted my phone with the hopes of everything going smooth, it didn't. It was a nightmare rooting the phone itself.
I was trying to install TWRP recovery through Goomanager but that didn't work so I did it through fast boot and terminal emulator with the commands.
After it was done I rebooted my phone and it just went to a black screen with the blue notification light. Then the phone turned off. I can't turn it on at all nor can I get it to go into download mode.
I recently just got this phone, one week ago to be exact, as an early Christmas present and I haven't really even been able to enjoy the phone because I've had the flu. I just now recovered from it and this happens.
I am in a insanely bad situation.
Is there anything at all I can do? Please help me...
dotkong said:
Hey guys.
Tonight I rooted my phone with the hopes of everything going smooth, it didn't. It was a nightmare rooting the phone itself.
I was trying to install TWRP recovery through Goomanager but that didn't work so I did it through fast boot and terminal emulator with the commands.
After it was done I rebooted my phone and it just went to a black screen with the blue notification light. Then the phone turned off. I can't turn it on at all nor can I get it to go into download mode.
I recently just got this phone, one week ago to be exact, as an early Christmas present and I haven't really even been able to enjoy the phone because I've had the flu. I just now recovered from it and this happens.
I am in a insanely bad situation.
Is there anything at all I can do? Please help me...
Click to expand...
Click to collapse
In these situations its best to provide as much information as possible. What was your Baseband? MDL? MF3? if you have no idea what any of this means....then you shouldn't be trying to flash anything on your phone, atleast not until after doing a ton of research. Your best bet is to try and get it into download mode and ODIN back to a stock image. If you can't get into download mode then unfortunately there isn't much you can do. You can try going to a best buy and see if they can flash it for you. You should know that if you're on MF3 you CANNOT flash a custom recovery other than SafeStrap. Hope some if this helps.
This phone is super special with special needs.if you can get it into DL mode than SEARCH for the Odin files that are floating around here.this phone will teach you how to read again
Sent from my ATT S4 MF3 using Tapatalk
If the phone is new like you said, its a good chance the model is MF3. The custom recovery you installed doesnt work for that model which more than likely cased or helped cause your issue. If you dont know the model and your phone won't turn on...the model number is listed on the box (assuming you still have it).
The TC mentioned he can't obtain DL mode so I'm not sure how the using odin will help him since it won't recognize his phone. I'd try best buy and go from there. If you try to have it warrentied while pleading the "I dont know what happened" card to your carrier...just be warned, if they replace it and find out it was rooted or messed with than they will charge your account the full retail cost. I've had many phones replace via manufacturers warranty and that is the first thing they tell me. It can even be an issue if the screen has a tiny scratch. Hope it works out.
brought to you by my not so sexy GS4 MF3
nash2000 said:
If the phone is new like you said, its a good chance the model is MF3. The custom recovery you installed doesnt work for that model which more than likely cased or helped cause your issue. If you dont know the model and your phone won't turn on...the model number is listed on the box (assuming you still have it).
The TC mentioned he can't obtain DL mode so I'm not sure how the using odin will help him since it won't recognize his phone. I'd try best buy and go from there. If you try to have it warrentied while pleading the "I dont know what happened" card to your carrier...just be warned, if they replace it and find out it was rooted or messed with than they will charge your account the full retail cost. I've had many phones replace via manufacturers warranty and that is the first thing they tell me. It can even be an issue if the screen has a tiny scratch. Hope it works out.
brought to you by my not so sexy GS4 MF3
Click to expand...
Click to collapse
He he can't turn it on best buy isn't going to help either. No one will be able to tell it's rooted either. Just take it back to where you got it and tell them it won't turn on. If it does turn on then you can Odin it.
dotkong said:
Hey guys.
Tonight I rooted my phone with the hopes of everything going smooth, it didn't. It was a nightmare rooting the phone itself.
I was trying to install TWRP recovery through Goomanager but that didn't work so I did it through fast boot and terminal emulator with the commands.
After it was done I rebooted my phone and it just went to a black screen with the blue notification light. Then the phone turned off. I can't turn it on at all nor can I get it to go into download mode.
I recently just got this phone, one week ago to be exact, as an early Christmas present and I haven't really even been able to enjoy the phone because I've had the flu. I just now recovered from it and this happens.
I am in a insanely bad situation.
Is there anything at all I can do? Please help me...
Click to expand...
Click to collapse
Pull the battery and wait a minute. Then replace it and see if you can use the correct key combo to get into recovery. If you fix it or get it replaced I suggest you do a lot of reading and learning before doing anything else. Good luck.
Bricked Galaxy S4
I've been there my self. The best and fastest thing to do now is go on the Wed and look up mobiletechvideo .
The guys are great. The turn around is fast.
Thread cleaned and closed.
XDA does not condone fraud in any form.
*I flashed a CM12.1 nightly on top of one that was a couple days old, and the new one had all kinds of force closes. This was through CM's internal update function, which sets a recovery script and reboots into recovery to install it (which BTW failed).
So I went into TWRP and flashed the backup I made not a couple hours earlier. But now I have kind of a bootloop. Most of the time, the LG logo shows up, then it just reboots back into recovery. One time it got stuck on the logo, and I was able to see it with ADB but it told me init.sh was missing when I tried to adb shell into it.
I have three backups I tried restoring, which had /boot, /recovery, /system and /data, plus I wiped the Dalvik cache and /cache, but nothing I've tried will kick this thing loose. I've even tried formatting it back to EXT4 from F2FS, and erasing and recreating the partitions in fastboot. It seems like there's a flag somewhere telling it to reboot into recovery, but I can't find anything pertinent online. I'm really at a loss as to how to fix it, and out of ideas now.
Have you tried using the lg support tool to bring the phone back to stock?
audit13 said:
Have you tried using the lg support tool to bring the phone back to stock?
Click to expand...
Click to collapse
Yeah, I was going to edit the OP to say I've also now tried to flash back to stock, using the 20a KDZ and the LG Flash Tool 2014. When it gets to the point where it's actually about to flash, it says "USB is not connected". I have all the latest drivers, and have tried different cords, to no avail. It has been transferring files while connected in TWRP, so I'm not sure what that's about.
What about using the lg support tool to flash stock?
LG Mobile Support Tool is what LG Flash Tool calls to actually flash the ROM (otherwise you have to depend on what LGMST decides to download). It saw the phone the last time I used it, but wouldn't show LP 5.0.2 as being an available update, even though it had been released.
This thread has the instructions I've been working off of, which was posted around the time the ROM was released. It "should" work, it just doesn't. If I'm not mistaken, there may be another tool you can use, but I haven't been able to find it.
There's one other way I suppose I could go about this, but it would be delicate. I could push all the individual IMG files from a ZIP archive I have of the KDZ, but I don't know what all the partition names are, and there are like 10 of them, including laf, aboot, etc. For example, the /data partition is actually named "userdata" when you use fastboot flash.
I didn't know about the difference between the LGMST and Flash Tool.
All I know is that the LGMST was able to download the correct LP ROM for my phone, install it, and get me back to stock after I screwed things up when trying to get root.
i have same problems , here is my solutions
- use SKR tool -> 4 .fix utility -> 5.unbrick ,
if u want go back to stock, try use TOT file to go back JB
cant use kdz way
Dễ.Thương said:
i have same problems , here is my solutions
- use SKR tool -> 4 .fix utility -> 5.unbrick ,
if u want go back to stock, try use TOT file to go back JB
cant use kdz way
Click to expand...
Click to collapse
+Thanks, I have never even heard of that. But I'll give it a try. By any chance were you using F2FS?
Though I am not sure, but I'm leaning towards some kind of hardware failure -- this is a refurbished phone, so there's no telling what it's been through inside. T-Mobile sent another one overnight, which I should have in a few hours, but I still need to clean up this one if it has to go back.
audit13 said:
I didn't know about the difference between the LGMST and Flash Tool.
All I know is that the LGMST was able to download the correct LP ROM for my phone, install it, and get me back to stock after I screwed things up when trying to get root.
Click to expand...
Click to collapse
Mine told me I had the latest version, which is peculiar. Was your phone rooted at the time? Because I could understand it refusing in that case: I ran into a soft-brick on a D800 because of an OTA once. Otherwise, I'm not sure why one would work, and the other wouldn't.
voxluna said:
+Thanks, I have never even heard of that. But I'll give it a try. By any chance were you using F2FS?
Though I am not sure, but I'm leaning towards some kind of hardware failure -- this is a refurbished phone, so there's no telling what it's been through inside. T-Mobile sent another one overnight, which I should have in a few hours, but I still need to clean up this one if it has to go back.
Click to expand...
Click to collapse
i dont use f2fs , just use SKR tool with luck but i think u need flash a stock rom first
Dễ.Thương said:
i dont use f2fs , just use SKR tool with luck but i think u need flash a stock rom first
Click to expand...
Click to collapse
The reason I ask is that I had a debate in another thread about using F2FS instead of EXT4 for the filesystem. Most people suggested it's buggy and causes problems, so I wondered if that's what happened here.
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
audit13 said:
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
Click to expand...
Click to collapse
If u can boot your phone ,try to use Tot file , lg flash tool doesnt work anymore
LGMST fixed my 802 so there was no need for a tot file.
audit13 said:
When I used lgmst, my phone was giving me boot certification errors. I played around some more with it and then it would only go to download mode.
I connect the phone in download mode and the program downloaded and installed the latest LP rom for my 802 from UAE.
Click to expand...
Click to collapse
I wish I had a D802 -- it's ubiquitous, and thus has more support on XDA, I think. I'm not sure why T-Mobile chose to have a customized model. Same goes for AT&T, since they both use the same frequencies... and I don't know what the hell Verizon was thinking with those hideous buttons. The only differences I see between most of them is the SAR.
I am not sure that all g2 phones support the same frequencies. My 802 will not connect to LTE in Canada.
audit13 said:
I am not sure that all g2 phones support the same frequencies. My 802 will not connect to LTE in Canada.
Click to expand...
Click to collapse
Well, they don't, especially Verizon and Sprint being entirely incompatible because of CDMA. I looked it up just now, and while there are several variations of your phone, it actually looks like it has a lot less frequencies than the T-Mobile device. I was under the impression it was the other way around, but I dunno exactly -- yours is supposed to be a D803 up there. It depends on the carrier/region, and which LTE bands they're using. It may be that you get LTE somewhere else eventually.
I don't know why the hell they don't just make the phone with all the bands you expect to encounter on a continent, but I'm sure it has to do with lock-in. Because the SoC should already have that stuff baked in.
I actually have an 802 (International version, unlocked) that I bought off a guy on Kijiji. It was an incredibly cheap price because it had some scratches on the screen which are not very noticeable. Once I applied a tempered glass screen protector, you could only see the scratches from an oblique angle. The guy even included an official LG flip case which wakes and sleeps the phone This phone even has a stock LP ROM.
I love the glass protectors! That gel adhesive just melts on the screen and leaves not a single bubble. And yeah, it gets into scratches and improves them, too. I'll never use film ones again. I've personally never broken a screen, but Gorilla Glass can be scratched under the right conditions. Hey, as long as it's working for you, cheap is always good. HSPA+ isn't anything to sneeze about either -- I've had some amazing speeds on T-Mobile with it, for years now. It's a great fallback for LTE.
Okay, I managed to recover the original phone!
Something in my previous build was triggering the boot loop into recovery. This happened when the CyanogenMod updater tried to flash a new nightly, so there's a possibility it set a flag that kept it looping. But it's also possible Xposed went haywire somehow, and/or a module did. I'm not really sure why it decided to fail like this, when I had been using it without issue.
All my backups did the same thing, yet those builds ran okay when I backed them up. And I don't know why I could see the COM41 port, but not use it -- the drivers were perfect, I went to a lot of trouble to uninstall and replace them. That meant no LGFlashTool, and manual restoration (ye olde commande line).
So, what I did was use fastboot to flash every partition I could get my hands on, not just the ones you can format in TWRP. I used the 20c files from here. You basically do:
fastboot erase aboot
fastboot flash aboot.img
fastboot erase laf
fastboot flash laf.img...etc. Then you format the /system partition, and flash a Cyanogenmod nightly into there. I also flashed the /data partition, but left /data/media alone, which saves the internal storage. Then I erased and flashed /recovery just for good measure.
This is a somewhat specific fix, but maybe if someone else comes across it, it can help.
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 I just picked up a clean used International 6T. Was going through the root and update (I did the Android 10 update through Oxygen Updater) process and all that, things were going great, then out of nowhere they weren't and I had a complete black screen. I've literally been up all night trying to fix this thing, then again out of nowhere it actually boots, and I was able to use the MSM tool to restore it to that earlier version, then proceeded to get back up and running again.
Thought, phew, dodged a bullet. Nope, after getting rooted and TWRP installed, transferring a bunch of files over from my old SD card and restoring apps through Titanium (again, everything was going great again), and yet now all of a sudden I'm back where it all started earlier, stuck at the 'The boot loader is unlocked and ....' boot screen, it just hangs there, I can reboot into recovery just fine, but no operating system.
I'm literally about to pull my freaking hair out and try and sell this thing if it's going to keep doing this, I've never had a phone act like this one has (prior phone was a Nokia 8, headache). I have friends/family who haven't heard from me in a couple days now because I'm out of a phone and I need to get this thing working stable.
Can anyone help or shed some light on why this has happened again? I didn't update to 10, left it on the last stable Pie (begrudgingly), didn't flash any custom rom or anything, it was restoring most of the titanium apps just fine (some just hang there, not sure what that's about) and now I can't reboot into the os. To say the least I'm beyond pissed and annoyed at how much time I've lost on this thing.
Please please please help if you can, I'm not a newb to rooting (already rooted this one twice) but I don't know what to do at this point.
Thank you in advance, let me know what/if any info is needed.
Edit: I think I know/understand partially that magisk is to blame for this and reinstalling it fixes it, though I just did that through TWRP and it's still stuck on the boot screen.
Edit: Yup, right back where I was, device now shows as HS-USB QDloader..... in device manager. What gives? I have to use the MSM tool again? Why? Why is this happening...I've never had this much trouble with a phone
Try a clean install. Don't root and don't restore the titanium apps. Install them fresh. If your problem persists then it may just be hardware. But something you are restoring may be causing the crash due to the way it is trying to restore the app data.
I had similar problems. For me it was my self-created magisk module that ran without problems under Android 9. As it seems, there are also problems with modules from the magisk repo.Could be the case with you.
Clean install of the apps, after doing another MSM restore? And trust me, I won't be installing ANY other magisk files other than just the magisk.
Is there any way to save all the work I just did though without having to start over again via MSM? I'm guessing not....sigh
Grrrr...ok before the MSM tool worked, the phone was just unresponsive. It's back at that stage where the MSM tool times out and doesn't do a darn thing to save the phone.
I swear this thing is all over the place, now I'm in the bootloader, yay. I guess I'll try a wipe in TWRP and start over.
One thing I forgot to ask, is magisk the ONLY option available for root?
The question would be, how did you root.
TWRP is not working when you don't follow the instructions which involves OldKeysFlasher.zip.
Otherwise you have to flash Magisk with a patched boot image, be sure uyou have one for OOS 10 Stable.
The correct comands are here: https://forum.xda-developers.com/showpost.php?p=80638253&postcount=2853
jgro1976 said:
(...)
I'm literally about to pull my freaking hair out and try and sell this thing if it's going to keep doing this, I've never had a phone act like this one has (prior phone was a Nokia 8, headache). I have friends/family who haven't heard from me in a couple days now because I'm out of a phone and I need to get this thing working stable. (...)
Click to expand...
Click to collapse
I hope that anger is directed towards yourself because you can't hold the device or its manufacturer responsible when you get into the flashing game.
If you had done some reading, you'd know that TWRP doesn't play well with Android 10 and upgrading from 9 takes a very specific procedure. There's a dedicated thread for it even. Happy searching. You may also want to take a peek at my posting history for some pointers.
One more thing, are you absolutely sure it's an international device and not a converted T-Mobile version? Because that can cause a major amount of troubles.
Wrapped with delicious Fajita [emoji896]
I'm well aware it's my own doing, part of the frustration is having too many sources of information all claiming they fix a 'thing'. There's the "fix it with fastboot" camp who doesn't like MSM, and there's the MSM camp that helped me the first time. Phone is currently dead/black screen, going to try MSM again, and will check out the info you provided.
And I'm sure, double sim tray, does not flash a pink tmobile screen and/or no branding of any kind on the phone related to tmobile.
jgro1976 said:
And I'm sure, double sim tray, does not flash a pink tmobile screen and/or no branding of any kind on the phone related to tmobile.
Click to expand...
Click to collapse
Just remember that dual SIM trays are easy to get and if it's been converted from TMO to international version there will be no indicators till n you try to flash A10. Best bet would be to treat it as a converted TMO, if it is the info in recovering and flashing a TMO device will work and if it's truly an international version it will work too. Best of both worlds.
I'm 99% certain, by the label on the box, etc. Regardless, I'm to the point now that I can't even get it to boot to TWRP after 'fastboot flash boot twrp.img', it just does nothing and when I try to boot to recovery it bounces right back to bootloader. I've been trying all afternoon to fix it with no luck.
Was android 8/oreo good on these phones? That was my sweet spot and I'm just gonna downgrade if possible, there's too many things I don't like about 9 and 10.